<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi Spyros,<br>
    </p>
    <p>Thanks for posting the discussion output. I'm not sure I can
      follow the idea of <font face="arial, helvetica, sans-serif">simplifying
        CNI configuration. Though we have both calico and flannel for
        k8s, but if we put both of them into single one config script.
        The script could be very complex. That's why I think we should
        define some naming and logging rules/policies for those scripts
        for long term maintenance to make our life easier. Thoughts? <br>
      </font></p>
    <br>
    <div class="moz-cite-prefix">On 25/06/18 19:20, Spyros Trigazis
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAB9QTQaukkCnvpe3e2mx9otQmT24wSuH5vWpSh4LFGL0jgiBDg@mail.gmail.com">
      <div dir="ltr"><font face="arial, helvetica, sans-serif">Hello
          again,<br>
          <br>
          After Thursday's meeting I want to summarize what we discussed
          and add some pointers.<br>
          <br>
          <ul>
            <li>Work on using the out-of-tree cloud provider and move to
              the new model of defining it<br>
              <a
                href="https://storyboard.openstack.org/#%21/story/1762743"
                target="_blank" moz-do-not-send="true">https://storyboard.openstack.org/#!/story/1762743</a><br>
              <a href="https://review.openstack.org/#/c/577477/"
                target="_blank" moz-do-not-send="true">https://review.openstack.org/#/c/577477/</a></li>
            <li>Configure kubelet and kube-proxy on master nodes<br>
              This story of the master node label can be extened <a
                href="https://storyboard.openstack.org/#%21/story/2002618"
                target="_blank" moz-do-not-send="true">https://storyboard.openstack.org/#!/story/2002618</a><br>
              or we can add a new one</li>
            <li>Simplify CNI configuration, we have calico and flannel.
              Ideally we should a single config script for each<br>
              one. We could move flannel to the kubernetes hosted
              version that uses kubernetes objects for storage.<br>
              (it is the recommended way by flannel and how it is done
              with kubeadm)</li>
            <li>magum support in gophercloud <a
                href="https://github.com/gophercloud/gophercloud/issues/1003"
                target="_blank" moz-do-not-send="true">https://github.com/gophercloud/gophercloud/issues/1003</a><br>
            </li>
            <li><b>needs discussion </b>update version of heat
              templates (pike or queens) This need its own tread</li>
            <li>Post deployment scripts for clusters, I have this since
              some time for my but doing it in<br>
              heat is slightly (not a lot) complicated. Most magnum
              users favor  the simpler solution<br>
              of passing a url of a manifest or script to the cluster
              (at least let's add sha512sum).</li>
            <li>Simplify addition of custom labels/parameters. To avoid
              patcing magnum, it would be<br>
              more ops friendly to have a generic field of custom
              parameters<br>
            </li>
          </ul>
          Not discussed in the last meeting but we should in the next
          ones:<br>
          <ul>
            <li>Allow cluster scaling from different users in the same
              project<br>
              <a
                href="https://storyboard.openstack.org/#%21/story/2002648"
                moz-do-not-send="true">https://storyboard.openstack.org/#!/story/2002648</a><br>
            </li>
            <li>Add the option to remove node from a resource group for
              swarm clusters like<br>
              in kubernetes<br>
              <a
                href="https://storyboard.openstack.org/#%21/story/2002677"
                moz-do-not-send="true">https://storyboard.openstack.org/#!/story/2002677</a><br>
            </li>
          </ul>
        </font><span style="font-family:arial,helvetica,sans-serif">Let's
          follow these up in the coming meetings, Tuesday 1000UTC and
          Thursday 1700UTC.</span>
        <div><span style="font-family:arial,helvetica,sans-serif"><br>
            You can always consult this page [1] for future meetings.<br>
            <br>
            Cheers,<br>
            Spyros</span></div>
        <div><span style="font-family:arial,helvetica,sans-serif"><br>
            [1] </span><font face="arial, helvetica, sans-serif"><a
              href="https://wiki.openstack.org/wiki/Meetings/Containers"
              target="_blank" moz-do-not-send="true">https://wiki.openstack.org/wiki/Meetings/Containers</a><br>
          </font></div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">On Wed, 20 Jun 2018 at 18:05, Spyros Trigazis
          <<a href="mailto:strigazi@gmail.com" target="_blank"
            moz-do-not-send="true">strigazi@gmail.com</a>> wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div dir="ltr">Hello list,<br>
            <br>
            We are going to have a second weekly meeting for magnum for
            3 weeks<br>
            as a test to reach out to contributors in the Americas.<br>
            <br>
            You can join us tomorrow (or today for some?) at 1700UTC in
            #openstack-containers .<br>
            <br>
            Cheers,<br>
            Spyros<br>
            <br>
            <br>
          </div>
        </blockquote>
      </div>
      <!--'"--><br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Cheers & Best regards,
Feilong Wang (王飞龙)
--------------------------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: <a class="moz-txt-link-abbreviated" href="mailto:flwang@catalyst.net.nz">flwang@catalyst.net.nz</a>
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
-------------------------------------------------------------------------- </pre>
  </body>
</html>