[openstack-dev] [fuel-library] making task "apache" idempotent

[Dmitry Bilunov]

Hello.

I am trying to pick a way of making puppet
manifest fuel-library/deployment/puppet/osnailyfacter/modular/apache/apache.pp
idempotent.
During a normal execution flow, Fuel (fuel-astute, actually) would run
"apache" task before running other tasks, which create virtual host
configuration files inside /etc/apache2/sites-enabled/.
"apache" task currently purges all configuration files, not created by it -
see https://forge.puppetlabs.com/puppetlabs/apache#purge_configs; it seems
reasonable to have this option enabled.

However, fuel-astute runs all tasks in a separate "puppet apply" processes,
which do not know anything about the state of each other. So I cannot use
the intended (by puppetlabs-apache) way of regenerating the configs after
the purge.

One way to achieve it is moving the code, generating the configs, into
apache.pp, so it will be re-run after each purge. However, it is
complicated by the need of existence of various resources: services' files,
users and packages. We cannot simply declare any of *::wsgi::apache classes
inside apache.pp due to these dependencies.

Another way is simply disabling purge_configs and purging manually
everything that we don't need (like distro's apache mpm config).

Which of these ways looks better? Are there any alternatives that I am
missing?
Thanks in advance.
__
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] [fuel-library] making task "apache" idempotent

[Aleksandr Didenko]

Hi,

I suppose disabling purge_configs is the only solution here. Running all
the configuration in a single task does not fit well into deployment
granularization philosophy.

Regards,
Alex

On Fri, Dec 11, 2015 at 12:13 PM, Dmitry Bilunov 
wrote:

> Hello.
>
> I am trying to pick a way of making puppet
> manifest fuel-library/deployment/puppet/osnailyfacter/modular/apache/apache.pp
> idempotent.
> During a normal execution flow, Fuel (fuel-astute, actually) would run
> "apache" task before running other tasks, which create virtual host
> configuration files inside /etc/apache2/sites-enabled/.
> "apache" task currently purges all configuration files, not created by it
> - see https://forge.puppetlabs.com/puppetlabs/apache#purge_configs; it
> seems reasonable to have this option enabled.
>
> However, fuel-astute runs all tasks in a separate "puppet apply"
> processes, which do not know anything about the state of each other. So I
> cannot use the intended (by puppetlabs-apache) way of regenerating the
> configs after the purge.
>
> One way to achieve it is moving the code, generating the configs, into
> apache.pp, so it will be re-run after each purge. However, it is
> complicated by the need of existence of various resources: services' files,
> users and packages. We cannot simply declare any of *::wsgi::apache classes
> inside apache.pp due to these dependencies.
>
> Another way is simply disabling purge_configs and purging manually
> everything that we don't need (like distro's apache mpm config).
>
> Which of these ways looks better? Are there any alternatives that I am
> missing?
> Thanks in advance.
>
> __
> 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