Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-04-07 Thread Emilien Macchi
On Fri, Apr 7, 2017 at 2:27 PM, Andreas Jaeger wrote: > On 2017-04-07 18:55, Emilien Macchi wrote: >> os-cloud-config has been retired in Infra and in the repo. >> RDO packaging has also been updated. >> Now waiting for final approval in Governance: >>

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-04-07 Thread Andreas Jaeger
On 2017-04-07 18:55, Emilien Macchi wrote: > os-cloud-config has been retired in Infra and in the repo. > RDO packaging has also been updated. > Now waiting for final approval in Governance: > https://review.openstack.org/#/c/451096/ > > If bug fixes has to happen, please submit to stable

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-04-07 Thread Emilien Macchi
os-cloud-config has been retired in Infra and in the repo. RDO packaging has also been updated. Now waiting for final approval in Governance: https://review.openstack.org/#/c/451096/ If bug fixes has to happen, please submit to stable branches directly and let us know on #rdo, we'll update the

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-04-03 Thread Emilien Macchi
The retirement patch is ready whenever you are: https://review.openstack.org/#/c/450946/ Please review. Thanks, On Mon, Apr 3, 2017 at 3:53 AM, Bogdan Dobrelya wrote: > On 31.03.2017 13:58, Jiří Stránský wrote: >> On 30.3.2017 17:39, Juan Antonio Osorio wrote: >>> Why not

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-04-03 Thread Bogdan Dobrelya
On 31.03.2017 13:58, Jiří Stránský wrote: > On 30.3.2017 17:39, Juan Antonio Osorio wrote: >> Why not drive the post-config with something like shade over ansible? >> Similar to what the kolla-ansible community is doing. > > We could use those perhaps, if they bring enough benefit to add them to

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-03-31 Thread Jiří Stránský
On 30.3.2017 17:39, Juan Antonio Osorio wrote: Why not drive the post-config with something like shade over ansible? Similar to what the kolla-ansible community is doing. We could use those perhaps, if they bring enough benefit to add them to the container image(s) (i think we'd still want to

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-03-30 Thread Jiří Stránský
On 30.3.2017 18:02, Bogdan Dobrelya wrote: On 30.03.2017 15:40, Jiří Stránský wrote: What might be interesting is solving the keystone init within containers along with our container entrypoint situation. We've talked earlier that we may have to build our custom entrypoints into the images as

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-03-30 Thread Bogdan Dobrelya
On 30.03.2017 15:40, Jiří Stránský wrote: > > What might be interesting is solving the keystone init within containers > along with our container entrypoint situation. We've talked earlier that > we may have to build our custom entrypoints into the images as we > sometimes need to do things that

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-03-30 Thread Alex Schultz
On Thu, Mar 30, 2017 at 6:58 AM, Dan Prince wrote: > There is one case that I was thinking about reusing this piece of code > within a container to help initialize keystone endpoints. It would > require some changes and updates (to match how puppet-* configures > endpoints). >

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-03-30 Thread Juan Antonio Osorio
Why not drive the post-config with something like shade over ansible? Similar to what the kolla-ansible community is doing. On 30 Mar 2017 16:42, "Jiří Stránský" wrote: > On 30.3.2017 14:58, Dan Prince wrote: > >> There is one case that I was thinking about reusing this piece

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-03-30 Thread Jiří Stránský
On 30.3.2017 14:58, Dan Prince wrote: There is one case that I was thinking about reusing this piece of code within a container to help initialize keystone endpoints. It would require some changes and updates (to match how puppet-* configures endpoints). For TripleO containers we use various

Re: [openstack-dev] [tripleo] os-cloud-config retirement

2017-03-30 Thread Dan Prince
There is one case that I was thinking about reusing this piece of code within a container to help initialize keystone endpoints. It would require some changes and updates (to match how puppet-* configures endpoints). For TripleO containers we use various puppet modules (along with hiera) to drive

[openstack-dev] [tripleo] os-cloud-config retirement

2017-03-30 Thread Emilien Macchi
Hi, os-cloud-config was deprecated in the Ocata release and is going to be removed in Pike. TripleO project doesn't need it anymore and after some investigation in codesearch.openstack.org, nobody is using it in OpenStack. I'm working on the removal this cycle, please let us know any concern.