<div dir="ltr">Hi,<div><br></div><div>To boot minions or master from volume, I use the following labels:</div><div><br></div><div>boot_volume_size = 20 </div><div>boot_volume_type = ssd </div><div>availability_zone = nova
                                   <br></div><div><br></div><div>volume type and zone might differ on your setup.</div><div><br></div><div>                  <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 15, 2020 at 11:23 AM Tony Pearce <<a href="mailto:tonyppe@gmail.com">tonyppe@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Hi Feilong, I hope you are keeping well. </div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Thank you for sticking with me on this issue to try and help me here. I really appreciate it! <br><br>I tried creating a new flavour like you suggested and using 10GB for root volume [1]. The cluster does start to be created (no error about 0mb disk) but while being created, I can check the compute node and see that the instance disk is being provisioned on the compute node [2]. I assume that this is the 10GB root volume that is specified in the flavour. </div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">When I list the volumes which have been created, I do not see the 10GB disk allocated on the compute node, but I do see the iSCSI network volume that has been created and attached to the instance (eg master) [3]. This is 15GB volume and this 15GB is coming from the kubernetes cluster template, under "Docker Volume Size (GB)" in the "node spec" section. There is very little data written to this volume at the time of master instance booted. </div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Eventually, kube cluster failed to create with error "Status</div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Create_Failed: Resource CREATE failed: Error: resources.kube_minions.resources[0].resources.node_config_deployment: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1". I'll try and find the root cause of this later.  </div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">What are your thoughts on this outcome? Is it possible to avoid consuming compute node disk? I require it because it cannot scale.</div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">[1] <a href="http://paste.openstack.org/show/797862/" style="font-family:Arial,Helvetica,sans-serif" target="_blank">http://paste.openstack.org/show/797862/</a></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">[2] <a href="http://paste.openstack.org/show/797865/" style="font-family:Arial,Helvetica,sans-serif" target="_blank">http://paste.openstack.org/show/797865/</a></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">[3] <a href="http://paste.openstack.org/show/797863/" style="font-family:Arial,Helvetica,sans-serif" target="_blank">http://paste.openstack.org/show/797863/</a></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Kind regards,</div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Tony</div><div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br></div><div><div dir="ltr"><div dir="ltr">Tony Pearce<br><br></div></div></div><br></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 14 Sep 2020 at 17:44, feilong <<a href="mailto:feilong@catalyst.net.nz" target="_blank">feilong@catalyst.net.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div>
    <p>Hi Tony,</p>
    <p>Does your Magnum support this config <a href="https://github.com/openstack/magnum/blob/master/magnum/conf/cinder.py#L47" target="_blank">https://github.com/openstack/magnum/blob/master/magnum/conf/cinder.py#L47</a>
      can you try to change it from 0 to 10? 10 means the root disk
      volume size for the k8s node. By default the 0 means the node will
      be based on image instead of volume. <br>
    </p>
    <p><br>
    </p>
    <div>On 14/09/20 9:37 pm, Tony Pearce wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="auto">Hi Feilong, sure. The flavour I used has 2 CPU and
        2GB memory. All other values either unset or 0mb. 
        <div dir="auto">I also used the same fedora 27 image that is
          being used for the kubernetes cluster. </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Thank you</div>
        <div dir="auto">Tony</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, 14 Sep 2020, 17:20
          feilong, <<a href="mailto:feilong@catalyst.net.nz" target="_blank">feilong@catalyst.net.nz</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>
            <p>Hi Tony,</p>
            <p>Could you please let me know  your flavor details? I
              would like to test it in my devstack environment (based on
              LVM). Thanks.</p>
            <p><br>
            </p>
            <div>On 14/09/20 8:27 pm, Tony Pearce wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">
                <div dir="ltr">
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Hi feilong,
                    hope you are keeping well. Thank you for the info!  </div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                  </div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">For
                    issue 1. Maybe this should be with the
                    kayobe/kolla-ansible team. Thanks for the insight
                    :) </div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                  </div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">For
                    the 2nd one, I was able to run the HOT template in
                    your link. There's no issues at all running that
                    multiple times concurrently while using the 0MB disk
                    flavour. I tried four times with the last three
                    executing one after the other so that they ran
                    parallelly.  All were successful and completed and
                    did not complain about the 0MB disk issue. </div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                  </div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Does
                    this conclude that the error and create-failed issue
                    relates to Magnum or could you suggest other steps
                    to test on my side? </div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                  </div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Best
                    regards,</div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                  </div>
                  <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif">Tony
                      Pearce</span><br>
                  </div>
                  <div>
                    <div dir="ltr">
                      <div dir="ltr"><br>
                        <br>
                      </div>
                    </div>
                  </div>
                  <br>
                </div>
              </div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Thu, 10 Sep 2020 at
                  16:01, feilong <<a href="mailto:feilong@catalyst.net.nz" rel="noreferrer" target="_blank">feilong@catalyst.net.nz</a>>
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                  <div>
                    <p>Hi Tony,</p>
                    <p>Sorry for the late response for your thread. <br>
                    </p>
                    <p>For you HTTPS issue, we (Catalyst Cloud) are
                      using Magnum with HTTPS and it works.<br>
                    </p>
                    <p>For the 2nd issue, I think we were
                      misunderstanding the nodes disk capacity. I was
                      assuming you're talking about the k8s nodes, but
                      seems you're talking about the physical compute
                      host. I still don't think it's a Magnum issue
                      because a k8s master/worker nodes are just normal
                      Nova instances and managed by Heat. So I would
                      suggest you use a simple HOT to test it, you can
                      use this <a href="https://gist.github.com/openstacker/26e31c9715d52cc502397b65d3cebab6" rel="noreferrer" target="_blank">https://gist.github.com/openstacker/26e31c9715d52cc502397b65d3cebab6</a></p>
                    <p>Most of the cloud providers or organizations who
                      have adopted Magnum are using Ceph as far as I
                      know, just FYI.</p>
                    <p><br>
                    </p>
                    <div>On 10/09/20 4:35 pm, Tony Pearce wrote:<br>
                    </div>
                    <blockquote type="cite">
                      <div dir="ltr">
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Hi
                          all, hope you are all keeping safe and well. I
                          am looking for information on the following
                          two issues that I have which surrounds Magnum
                          project:</div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                        </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">1.
                          Magnum does not support Openstack API with
                          HTTPS</div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">2.
                          Magnum forces compute nodes to consume disk
                          capacity for instance data<br>
                        </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                        </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">My
                          environment: Openstack Train deployed using
                          Kayobe (Kolla-ansible). </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                        </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">With
                          regards to the HTTPS issue, Magnum stops
                          working after enabling HTTPS because the
                          certificate / CA certificate is not trusted by
                          Magnum. The certificate which I am using is
                          one that was purchased from GoDaddy and is
                          trusted in web browsers (and is valid), just
                          not trusted by the Magnum component. </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                        </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Regarding
                          compute node disk consumption issue - I'm at a
                          loss with regards to this and so I'm looking
                          for more information about why this is being
                          done and is there any way that I could avoid
                          it?  I have storage provided by a Cinder
                          integration and so the consumption of compute
                          node disk for instance data I need to avoid. </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                        </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Any
                          information the community could provide to me
                          with regards to the above would be much
                          appreciated. I would very much like to use the
                          Magnum project in this deployment for
                          Kubernetes deployment within projects. </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                        </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Thanks
                          in advance, </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                        </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Regards,</div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)"><br>
                        </div>
                        <div class="gmail_default" style="font-family:verdana,sans-serif;color:rgb(102,102,102)">Tony</div>
                      </div>
                    </blockquote>
                    <pre cols="72">-- 
Cheers & Best regards,
Feilong Wang (王飞龙)
------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: <a href="mailto:flwang@catalyst.net.nz" rel="noreferrer" target="_blank">flwang@catalyst.net.nz</a>
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
------------------------------------------------------ </pre>
                  </div>
                </blockquote>
              </div>
            </blockquote>
            <pre cols="72">-- 
Cheers & Best regards,
Feilong Wang (王飞龙)
------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: <a href="mailto:flwang@catalyst.net.nz" rel="noreferrer" target="_blank">flwang@catalyst.net.nz</a>
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
------------------------------------------------------ </pre>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <pre cols="72">-- 
Cheers & Best regards,
Feilong Wang (王飞龙)
------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: <a href="mailto:flwang@catalyst.net.nz" target="_blank">flwang@catalyst.net.nz</a>
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
------------------------------------------------------ </pre>
  </div>

</blockquote></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Ionut Biru - <a href="https://fleio.com" target="_blank">https://fleio.com</a><br></div></div>