Hi Ignazio, Using the magnum master branch we took the publicly-available fedora atomic image and used that one with the standard templates from Magnum. I will be able to check with the team again in a while but from what I know it worked fine like this (while it did not work with any of the stable branches of magnum). Octavian. From: Ignazio Cassano <ignaziocassano@gmail.com> Sent: miercuri, 12 decembrie 2018 10:32 To: Octavian Ciuhandu <ociuhandu@cloudbasesolutions.com> Cc: OpenStack Operators <openstack-operators@lists.openstack.org> Subject: Re: Magnum Fedora atomic 27 Hello Octavian, I did not understand what you used for working fine. Did you create an image with diskimage builder ? Did you create your own templates? Seems you are not using templates generated by Magnum. ...is it correct? Thanks Ignazio Il giorno Mer 12 Dic 2018 18:57 Octavian Ciuhandu <ociuhandu@cloudbasesolutions.com<mailto:ociuhandu@cloudbasesolutions.com>> ha scritto: Hello, We never managed to get any version except the master work ok with Fedora atomic. We ended up deloying magnum from master with a queens openstack and this worked ok for us. We tried queens/pike/rocky and all of them seemed to have missing things in the templates and doing a simple diff on the template files shows huge changes. Regards, Octavian. From: Ignazio Cassano <ignaziocassano@gmail.com<mailto:ignaziocassano@gmail.com>> Sent: miercuri, 12 decembrie 2018 09:50 To: OpenStack Operators <openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>> Subject: Magnum Fedora atomic 27 Hello All, Deploying swarm cluster based on Fedora atomic cloud images, does not work fine in queens. On master node cloud init reports etcd package missing. Does anyone find this issue? Regards Ignazio

Hi Octavian, I cloned the magnum master. I saw there is a playbook for creating fedora atomic with diskimage builder but some files do not exist: MAGNUM_ELEMENTS=./openstack/magnum/magnum/drivers/common/image export ELEMENTS_PATH=$DIB_ELEMENTS:$MAGNUM_ELEMENTS $MAGNUM_ELEMENTS/fedora-atomic/install_imagebuild_deps.sh install_imagebuild_deps.sh does not exist in the master branch Regards Ignazio Il giorno mer 12 dic 2018 alle ore 19:34 Octavian Ciuhandu < ociuhandu@cloudbasesolutions.com> ha scritto:

Hi Ignazio,

Using the magnum master branch we took the publicly-available fedora atomic image and used that one with the standard templates from Magnum. I will be able to check with the team again in a while but from what I know it worked fine like this (while it did not work with any of the stable branches of magnum).

Octavian.

*From:* Ignazio Cassano <ignaziocassano@gmail.com> *Sent:* miercuri, 12 decembrie 2018 10:32 *To:* Octavian Ciuhandu <ociuhandu@cloudbasesolutions.com> *Cc:* OpenStack Operators <openstack-operators@lists.openstack.org> *Subject:* Re: Magnum Fedora atomic 27

Hello Octavian, I did not understand what you used for working fine.

Did you create an image with diskimage builder ?

Did you create your own templates?

Seems you are not using templates generated by Magnum. ...is it correct?

Thanks

Ignazio

Il giorno Mer 12 Dic 2018 18:57 Octavian Ciuhandu < ociuhandu@cloudbasesolutions.com> ha scritto:

Hello,

We never managed to get any version except the master work ok with Fedora atomic. We ended up deloying magnum from master with a queens openstack and this worked ok for us.

We tried queens/pike/rocky and all of them seemed to have missing things in the templates and doing a simple diff on the template files shows huge changes.

Regards,

Octavian.

*From:* Ignazio Cassano <ignaziocassano@gmail.com> *Sent:* miercuri, 12 decembrie 2018 09:50 *To:* OpenStack Operators <openstack-operators@lists.openstack.org> *Subject:* Magnum Fedora atomic 27

Hello All,

Deploying swarm cluster based on Fedora atomic cloud images, does not work fine in queens. On master node cloud init reports etcd package missing.

Does anyone find this issue?

Regards

Ignazio