On Thu, Apr 12, 2018 at 1:08 AM, Sergii Golovatiuk <sgolo...@redhat.com> 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 containers. Indeed, it'll > be > > driven by Heat and Mistral mostly. > > I am trying to think as operator and it's very similar to 'openstack > container' which is swift. So it might be confusing I guess. "openstack overcloud container" was already in Pike, Queens for your information. [...] > > - We need a tool to update containers from this registry and *before* > > deploying them. We already have this tool in place in our CI for the > > overcloud (see [3] and [4]). Now we need a similar thing for the > undercloud. > > I would use external registry in this case. Quay.io might be a good > choice to have rock solid simplicity. It might not be good for CI as > requires very strong connectivity but it should be sufficient for > developers. > No. We'll use docker-distribution for now, and will consider more support in the future but what we want right now is parity. [...] -- Emilien Macchi
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
