On 16 May 2017 at 08:30, Emilien Macchi <emil...@redhat.com> wrote: > On Tue, May 16, 2017 at 11:12 AM, Doug Hellmann <d...@doughellmann.com> wrote: >> Excerpts from Flavio Percoco's message of 2017-05-16 10:07:52 -0400: >>> On 16/05/17 09:45 -0400, Doug Hellmann wrote: >>> >Excerpts from Flavio Percoco's message of 2017-05-15 21:50:23 -0400: >>> >> On 15/05/17 11:49 -0700, Michał Jastrzębski wrote: >>> >> >On 15 May 2017 at 11:19, Davanum Srinivas <dava...@gmail.com> wrote: >>> >> >> Sorry for the top post, Michal, Can you please clarify a couple of >>> >> >> things: >>> >> >> >>> >> >> 1) Can folks install just one or two services for their specific >>> >> >> scenario? >>> >> > >>> >> >Yes, that's more of a kolla-ansible feature and require a little bit >>> >> >of ansible know-how, but entirely possible. Kolla-k8s is built to >>> >> >allow maximum flexibility in that space. >>> >> > >>> >> >> 2) Can the container images from kolla be run on bare docker daemon? >>> >> > >>> >> >Yes, but they need to either override our default CMD (kolla_start) or >>> >> >provide ENVs requred by it, not a huge deal >>> >> > >>> >> >> 3) Can someone take the kolla container images from say dockerhub and >>> >> >> use it without the Kolla framework? >>> >> > >>> >> >Yes, there is no such thing as kolla framework really. Our images >>> >> >follow stable ABI and they can be deployed by any deploy mechanism >>> >> >that will follow it. We have several users who wrote their own deploy >>> >> >mechanism from scratch. >>> >> > >>> >> >Containers are just blobs with binaries in it. Little things that we >>> >> >add are kolla_start script to allow our config file management and >>> >> >some custom startup scripts for things like mariadb to help with >>> >> >bootstrapping, both are entirely optional. >>> >> >>> >> Just as a bonus example, TripleO is currently using kolla images. They >>> >> used to >>> >> be vanilla and they are not anymore but only because TripleO depends on >>> >> puppet >>> >> being in the image, which has nothing to do with kolla. >>> >> >>> >> Flavio >>> >> >>> > >>> >When you say "using kolla images," what do you mean? In upstream >>> >CI tests? On contributors' dev/test systems? Production deployments? >>> >>> All of them. Note that TripleO now builds its own "kolla images" (it uses >>> the >>> kolla Dockerfiles and kolla-build) because the dependency of puppet. When I >>> said, TripleO uses kolla images was intended to answer Dims question on >>> whether >>> these images (or Dockerfiles) can be consumed by other projects. >>> >>> Flavio >>> >> >> Ah, OK. So TripleO is using the build instructions for kolla images, but >> not the binary images being produced today? > > Exactly. We have to add Puppet packaging into the list of things we > want in the binary, that's why we don't consume the binary directly.
And frankly, if we get this thing agreed on, I don't see why TripleO couldn't publish their images too. If we build technical infra in Kolla, everyone else can benefit from it. >> Doug >> >> __________________________________________________________________________ >> 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 > > > > -- > 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 __________________________________________________________________________ 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
