Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-23 Thread Tony Breeds
On Sun, Apr 15, 2018 at 07:24:58PM -0700, Emilien Macchi wrote: > This patch: https://review.openstack.org/#/c/561377 is deploying Docker and > Docker Registry v2 *before* containers deployment in the docker_steps. > It's using the external_deploy_tasks interface that runs right after the >

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-23 Thread Bogdan Dobrelya
On 4/20/18 8:56 PM, Emilien Macchi wrote: So the role has proven to be useful and we're now sure that we need it to deploy a container registry before any container in the deployment, which means we can't use the puppet code anymore for this service. I propose that we move the role to

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-20 Thread Emilien Macchi
So the role has proven to be useful and we're now sure that we need it to deploy a container registry before any container in the deployment, which means we can't use the puppet code anymore for this service. I propose that we move the role to OpenStack: https://review.openstack.org/#/c/563197/

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-15 Thread Emilien Macchi
On Fri, Apr 13, 2018 at 5:58 PM, Emilien Macchi wrote: > > A bit of progress today, I prototyped an Ansible role for that purpose: > https://github.com/EmilienM/ansible-role-container-registry > > The next step is, I'm going to investigate if we can deploy Docker and > Docker

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-13 Thread Emilien Macchi
On Wed, Apr 11, 2018 at 3:38 PM, Steve Baker wrote: > > - If agreed, we'll create a new Ansible role called > ansible-role-container-registry > that for now will deploy exactly what we have in TripleO, without extra > feature. > > +1 > A bit of progress today, I prototyped an

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-12 Thread Emilien Macchi
On Thu, Apr 12, 2018 at 1:16 AM, Bogdan Dobrelya wrote: [...] > Deploy own registry as part of UC deployment or use external. For >> instance, for production use I would like to have a cluster of 3-5 >> registries with HAProxy in front to speed up 1k nodes deployments. >> >

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-12 Thread Emilien Macchi
On Thu, Apr 12, 2018 at 1:08 AM, Sergii Golovatiuk wrote: [...] > > One of the great outcomes of this blueprint is that in Rocky, the > operator > > won't have to run all the "openstack overcloud container" commands to > > prepare the container registry and upload the

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-12 Thread Bogdan Dobrelya
On 4/12/18 12:38 AM, Steve Baker wrote: On 11/04/18 12:50, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-12 Thread Bogdan Dobrelya
On 4/12/18 12:38 AM, Steve Baker wrote: On 11/04/18 12:50, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-12 Thread Bogdan Dobrelya
On 4/12/18 10:08 AM, Sergii Golovatiuk wrote: Hi, Thank you very much for brining up this topic. On Wed, Apr 11, 2018 at 2:50 AM, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-12 Thread Bogdan Dobrelya
On 4/12/18 12:38 AM, Steve Baker wrote: On 11/04/18 12:50, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-12 Thread Sergii Golovatiuk
Hi, Thank you very much for brining up this topic. On Wed, Apr 11, 2018 at 2:50 AM, Emilien Macchi wrote: > Greetings, > > Steve Baker and I had a quick chat today about the work that is being done > around containers workflow in Rocky cycle. > > If you're not familiar with

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-11 Thread Steve Baker
On 11/04/18 12:50, Emilien Macchi wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint to understand the context here:

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-11 Thread Steve Baker
On 12/04/18 00:58, Wesley Hayutin wrote: On Tue, 10 Apr 2018 at 20:51 Emilien Macchi > wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle.

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-11 Thread Ben Nemec
On 04/11/2018 07:58 AM, Wesley Hayutin wrote: On Tue, 10 Apr 2018 at 20:51 Emilien Macchi > wrote: Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle.

Re: [openstack-dev] [tripleo] roadmap on containers workflow

2018-04-11 Thread Wesley Hayutin
On Tue, 10 Apr 2018 at 20:51 Emilien Macchi wrote: > Greetings, > > Steve Baker and I had a quick chat today about the work that is being done > around containers workflow in Rocky cycle. > > If you're not familiar with the topic, I suggest to first read the > blueprint to

[openstack-dev] [tripleo] roadmap on containers workflow

2018-04-10 Thread Emilien Macchi
Greetings, Steve Baker and I had a quick chat today about the work that is being done around containers workflow in Rocky cycle. If you're not familiar with the topic, I suggest to first read the blueprint to understand the context here: