[openstack-dev] [Puppet] Puppet OpenStack Application Module

Emilien Macchi emilien at redhat.com
Tue Aug 16 16:01:36 UTC 2016

During our weekly meeting [1] we discussed about $topic.

* Deploying a PE stack in our CI is not an option, we rely only on FOSS.

* Some FOSS deployers doing orchestration (eg mcollective-choria, etc)
do exist but it doesn't seem there is an official consensus about
which one Puppetlabs does support.

* Unless something changed recently, the actual Orchestrator is not
FOSS so we would need to pick a FOSS deployer (see previous
I find it weird that Open-Source communities (Puppet, OpenStack, etc)
would engage some efforts to replace something that Puppetlabs itself
didn't open.
In other words, why would we be developing a new module that help
deploying OpenStack in multinode with Puppet App Orchestration without
the actual help from Puppetlabs?

Unless using PE (not FOSS), there is no official way to make Puppet
multinode orchestration at this time. Before driving some work in our
community, I would like to know from Puppetlabs what is the plan here.


[1] http://eavesdrop.openstack.org/meetings/puppet_openstack/2016/puppet_openstack.2016-08-16-15.00.html

On Tue, Aug 16, 2016 at 9:39 AM, Emilien Macchi <emilien at redhat.com> wrote:
> On Mon, Aug 15, 2016 at 12:13 PM, Andrew Woodward <xarses at gmail.com> wrote:
>> I'd like to propose the creation of a puppet module to make use of Puppet
>> Application orchestrator. This would consist of a Puppet-4 compatible module
>> that would define applications that would wrap the existing modules.
>> This will allow for the establishment of a shared module that is capable of
>> expressing OpenStack applications using the new language schematics in
>> Puppet 4 [1] for multi-node application orchestration.
>> I'd expect that initial testing env would consist of deploying a PE stack,
>> and using docker containers as node primitives. This is necessary until a
>> FOSS deployer component like [2] becomes stable, at which point we can
>> switch to it and use the FOSS PM as well. Once the env is up, I plan to wrap
>> p-o-i profiles to deploy the cloud and launch tempest for functional
>> testing.
>> [1] https://docs.puppet.com/pe/latest/app_orchestration_workflow.html
>> [2] https://github.com/ripienaar/mcollective-choria
> It reminds me stackforge/puppet-openstack [1] repository that we had
> in the past and that we deprecated and removed.
> It was a failure because it was not maintained and not really used by
> our community because too much opinionated.
> Before creating such a new repository, we might want to see some PoC
> somewhere, some piece of code, so we can evaluate if we would actually
> need that thing.
> Have you already written some code around that? Can you show it?
> I just don't want to see (again) an empty repo where nobody is pushing
> code on it.
> [1] https://github.com/stackforge/puppet-openstack
> --
> Emilien Macchi

Emilien Macchi

More information about the OpenStack-dev mailing list