support many components using apache mod_wsgi

Bug #1348732 reported by Richard Megginson on 2014-07-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Packstack
Undecided
Unassigned

Bug Description

More openstack components may be moving to use apache mod_wsgi, not just horizon. Each component that uses apache should have the following:

  class { '::apache': purge_configs => false }

so as not to overwrite any configuration created by another component.

However, this requires that the framework (in this case, packstack) must do the initial

  include ::apache

to initialize the configuration.

Thanks for this hint we will do some testing and see if we could manage to make it work without troubles.

Cheers,
Francesco

> On 25 Jul 2014, at 19:30, Richard Megginson <email address hidden> wrote:
>
> Public bug reported:
>
> More openstack components may be moving to use apache mod_wsgi, not just
> horizon. Each component that uses apache should have the following:
>
> class { '::apache': purge_configs => false }
>
> so as not to overwrite any configuration created by another component.
>
> However, this requires that the framework (in this case, packstack) must
> do the initial
>
> include ::apache
>
> to initialize the configuration.
>
> ** Affects: packstack
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Packstack
> Core, which is subscribed to Packstack.
> https://bugs.launchpad.net/bugs/1348732
>
> Title:
> support many components using apache mod_wsgi
>
> Status in Packstack:
> New
>
> Bug description:
> More openstack components may be moving to use apache mod_wsgi, not
> just horizon. Each component that uses apache should have the
> following:
>
> class { '::apache': purge_configs => false }
>
> so as not to overwrite any configuration created by another component.
>
> However, this requires that the framework (in this case, packstack)
> must do the initial
>
> include ::apache
>
> to initialize the configuration.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/packstack/+bug/1348732/+subscriptions

Richard Megginson (rmeggins) wrote :

I've got some patches for puppet-keystone, puppet-horizon, and packstack which will be submitted shortly

Reviewed: https://review.openstack.org/109678
Committed: https://git.openstack.org/cgit/stackforge/packstack/commit/?id=f47d6501f62661a35d554e73f1ce931603a15d2f
Submitter: Jenkins
Branch: master

commit f47d6501f62661a35d554e73f1ce931603a15d2f
Author: Rich Megginson <email address hidden>
Date: Thu Jul 17 16:23:35 2014 -0600

    support other components using apache mod_wsgi

    Keystone is moving to use apache mod_wsgi instead of standalone
    eventlet daemon. Packstack should support deployment of keystone
    using this model. A new command line switch --keystone-service-name
    is added, and a new config parameter CONFIG_KEYSTONE_SERVICE_NAME
    is added. If this is set to 'httpd', keystone will be set up to use
    apache mod_wsgi, otherwise, it will be a standalone eventlet service.

    There is some common apache configuration that must be done by
    every module that uses apache. There is a new class in packstack
    called packstack::apache_common. Each component that uses apache
    must call "include packstack::apache_common". This ensures that
    a subsequent component manifest will not wipe out apache
    configuration created by a previous component manifest or the initial
    apache configuration created by prescript.pp.

    Change-Id: I73b853507dffb2540638182f3072e65e4d7ad485
    Closes-Bug: #1348732

Changed in packstack:
status: New → Fix Committed

Reviewed: https://review.openstack.org/136415
Committed: https://git.openstack.org/cgit/stackforge/packstack/commit/?id=2014442e51a60772144508f187ef992225a712c5
Submitter: Jenkins
Branch: icehouse

commit 2014442e51a60772144508f187ef992225a712c5
Author: Rich Megginson <email address hidden>
Date: Thu Jul 17 16:23:35 2014 -0600

    support other components using apache mod_wsgi

    Keystone is moving to use apache mod_wsgi instead of standalone
    eventlet daemon. Packstack should support deployment of keystone
    using this model. A new command line switch --keystone-service-name
    is added, and a new config parameter CONFIG_KEYSTONE_SERVICE_NAME
    is added. If this is set to 'httpd', keystone will be set up to use
    apache mod_wsgi, otherwise, it will be a standalone eventlet service.

    There is some common apache configuration that must be done by
    every module that uses apache. There is a new class in packstack
    called packstack::apache_common. Each component that uses apache
    must call "include packstack::apache_common". This ensures that
    a subsequent component manifest will not wipe out apache
    configuration created by a previous component manifest or the initial
    apache configuration created by prescript.pp.

    Closes-Bug: #1348732
    (cherry picked from commit f47d6501f62661a35d554e73f1ce931603a15d2f)

    Conflicts:
     packstack/puppet/templates/keystone.pp

    Change-Id: Ic7bf908ed03461e1e42991d89b6ae7c2ac57e348

The status of this bug report was changed automatically.

Changed in packstack:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers