Open Stack

On 01/28/2016 10:14 AM, Matt Fischer wrote:
> The way I'd recommend is to write your own manifests that include the
> openstack modules. I'd use roles and profiles which make it easy to move
> things around, but two simple manifests will also work. As Emilien once
> said we give you the ingredients but don't cook for you. If you want to
> just do two manifests, the integration tests you found are a good start
> but you will have to maintain them on your own.

Having a multi-node scenario is something in our roadmap:
https://etherpad.openstack.org/p/HND-puppet-ci

In Tokyo Summit we wanted to start looking at multi-node jobs where
compute services would be separated.
Unfortunately, nothing is really in place at the moment on our side.

We're currently having design discussions around our integration jobs:
https://etherpad.openstack.org/p/puppet-openstack-integration-scenarios

Feel free to participate and eventually contribute back.

Regarding your need, Matt is right.
We don't "cook" for you, just because our Puppet modules are so flexible
that you can define your own architecture for any OpenStack service -
which is not something you can entirely do with OpenStack Ansible as a
comparison.
The manifests on puppet-openstack-integration are useful for our
upstream CI but also for all-in-one testing. They don't aim for
production deployments, and we expect our community skilled enough in
Puppet to know how to write a manifest.
Though we're doing our best to provide some documentation and examples.
For example in puppet-nova:
https://github.com/openstack/puppet-nova/blob/master/README.md

There are 2 kind of Puppet OpenStack users at this time:

* Installer folks: they take our modules and write an interface to
compose layers with different backends, drivers, configurations support.
The 2 most popular installers using our modules are Fuel & TripleO.

* People who compose their own manifests (that's your case right now I
guess?) - You'll need to take time to read our modules/manifests and
understand how we split services and configure them.
I can provide you an example at how we compose in TripleO:
https://github.com/openstack/tripleo-heat-templates/tree/master/puppet/manifests

I hope all of this helps, and feel free to bring any feedback or ask for
more informations,


> Don't use the openstack module, it's abadonded and should be
> removed/deleted, IMHO.

Let me clear this sentence to avoid any confusion:
https://forge.puppetlabs.com/puppetlabs/openstack is a Puppet module
that is now outdated and I'm not sure it's maintained anymore.
It was an effort out of OpenStack community, led by Puppetlabs.

> On Jan 28, 2016 6:56 AM, "Ptacek, MichalX" <michalx.ptacek at intel.com
> <mailto:michalx.ptacek at intel.com>> wrote:
> 
>     Hi All,____
> 
>     __ __
> 
>     I have one very general question, ____
> 
>     we would like to deploy role-separated (compute & controller)
>     openstack via puppet modules.____
> 
>     Unfortunately puppet-openstack-integration supports only
>     “all-in-one” scenarios.____
> 
>     https://github.com/openstack/puppet-openstack-integration____
> 
>     __ __
> 
>     this project looks like continuation of former____
> 
>     https://forge.puppetlabs.com/puppetlabs/openstack____
> 
>     which is supporting that,  but ended it’s support with Juno release
>     ….____
> 
>     __ __
> 
>     we are targeting liberty deployments and would like to use puppet
>     modules,____
> 
>     what is the easiest way how to deploy role separated openstack based
>     on puppet modules (except fuel) ?____
> 
>     __ __
> 
>     I miss this info in https://wiki.openstack.org/wiki/Puppet____
> 
>     __ __
> 
>     thanks,____
> 
>     Michal____
> 
>     __ __
> 
>     __ __
> 
>     __ __
> 
>     --------------------------------------------------------------
>     Intel Research and Development Ireland Limited
>     Registered in Ireland
>     Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
>     Registered Number: 308263
> 
>     This e-mail and any attachments may contain confidential material
>     for the sole use of the intended recipient(s). Any review or
>     distribution by others is strictly prohibited. If you are not the
>     intended recipient, please contact the sender and delete all copies.
> 
> 
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

-- 
Emilien Macchi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160128/f066041a/attachment.pgp>