Re: [openstack-dev] [Openstack-operators] [tripleo] Making containerized service deployment the default

[Shake Chen]

I think  tripleo use kolla and kolla-ansible would be perfect.

On Tue, Sep 19, 2017 at 3:47 AM, Mohammed Naser  wrote:

> On Mon, Sep 18, 2017 at 3:04 PM, Alex Schultz  wrote:
> > Hey ops & devs,
> >
> > We talked about containers extensively at the PTG and one of the items
> > that needs to be addressed is that currently we still deploy the
> > services as bare metal services via puppet. For Queens we would like
> > to switch the default to be containerized services.  With this switch
> > we would also start the deprecation process for deploying services as
> > bare metal services via puppet.  We still execute the puppet
> > configuration as part of the container configuration process so the
> > code will continue to be leveraged but we would be investing more in
> > the continual CI of the containerized deployments and reducing the
> > traditional scenario coverage.
> >
> > As we switch over to containerized services by default, we would also
> > begin to reduce installed software on the overcloud images that we
> > currently use.  We have an open item to better understand how we can
> > switch away from the golden images to a traditional software install
> > process during the deployment and make sure this is properly tested.
> > In theory it should work today by switching the default for
> > EnablePackageInstall[0] to true and configuring repositories, but this
> > is something we need to verify.
> >
> > If anyone has any objections to this default switch, please let us know.
>
> I think this is a great initiative.  It would be nice to share some of
> the TripleO experience in containerized deployments so that we can use
> Puppet for containerized deployments.  Perhaps we can work together on
> adding some classes which can help deploy and configure containerized
> services with Puppet.
>
> >
> > Thanks,
> > -Alex
> >
> > [0] https://github.com/openstack/tripleo-heat-templates/blob/
> master/puppet/services/tripleo-packages.yaml#L33-L36
> >
> > ___
> > OpenStack-operators mailing list
> > openstack-operat...@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
> __
> 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
>



-- 
Shake Chen
__
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

Re: [openstack-dev] [Openstack-operators] [tripleo] Making containerized service deployment the default

[Mohammed Naser]

On Mon, Sep 18, 2017 at 3:04 PM, Alex Schultz  wrote:
> Hey ops & devs,
>
> We talked about containers extensively at the PTG and one of the items
> that needs to be addressed is that currently we still deploy the
> services as bare metal services via puppet. For Queens we would like
> to switch the default to be containerized services.  With this switch
> we would also start the deprecation process for deploying services as
> bare metal services via puppet.  We still execute the puppet
> configuration as part of the container configuration process so the
> code will continue to be leveraged but we would be investing more in
> the continual CI of the containerized deployments and reducing the
> traditional scenario coverage.
>
> As we switch over to containerized services by default, we would also
> begin to reduce installed software on the overcloud images that we
> currently use.  We have an open item to better understand how we can
> switch away from the golden images to a traditional software install
> process during the deployment and make sure this is properly tested.
> In theory it should work today by switching the default for
> EnablePackageInstall[0] to true and configuring repositories, but this
> is something we need to verify.
>
> If anyone has any objections to this default switch, please let us know.

I think this is a great initiative.  It would be nice to share some of
the TripleO experience in containerized deployments so that we can use
Puppet for containerized deployments.  Perhaps we can work together on
adding some classes which can help deploy and configure containerized
services with Puppet.

>
> Thanks,
> -Alex
>
> [0] 
> https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/tripleo-packages.yaml#L33-L36
>
> ___
> OpenStack-operators mailing list
> openstack-operat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

__
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