Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1441208

Summary:	placement api apache configuration does not align with documentation, ensure system does not work
Product:	[Community] RDO	Reporter:	Chris Dent <cdent>
Component:	openstack-nova	Assignee:	nlevinki <nlevinki>
Status:	CLOSED DUPLICATE	QA Contact:	Prasanth Anbalagan <panbalag>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	trunk	CC:	berrange, cdent, dasmith, eglynn, pkovar, rbryant, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone:	---	Flags:	cdent: needinfo-
Target Release:	trunk
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-12 14:15:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Dent 2017-04-11 12:37:56 UTC

Description of problem:

The openstack official documentation creates a service catalog entry for the placement service at http://controller/placement. The RDO package defines an apache configuration that is not aligned with this: https://github.com/rdo-packages/nova-distgit/blob/rpm-master/nova-placement-api.conf

See the entries for Alias and Location. These are not /placement, as required by the docs. The result is that if someone installs from RDO packages using the openstack official docs, nova will not be able to schedule any hosts because it will not be able to register any resource providers.

Comment 1 Stephen Gordon 2017-04-12 14:02:19 UTC

The official docs basically just copy from the way the Ubuntu packaging works, it's increasingly unclear to us whether this actually means it's correct as - for example - it also suggests having Apache expose /usr/bin. 

Does the Nova project provide clear guidance on how it expects placement to be set up w.r.t. Apache configuration?

See also:

Bug # 1430540
https://review.rdoproject.org/r/#/c/5954/

Comment 2 Stephen Gordon 2017-04-12 14:05:28 UTC

Looking at http://git.openstack.org/cgit/openstack-dev/devstack/tree/files/apache-placement-api.template:

* I do see placement in use as the endpoint.
* I do not see this stanza present in the Ubuntu packaging and the docs:

<Directory /usr/bin>
   <IfVersion >= 2.4>
      Require all granted
   </IfVersion>
   <IfVersion < 2.4>
      Order allow,deny
      Allow from all
   </IfVersion>
</Directory>

Comment 3 Stephen Gordon 2017-04-12 14:08:02 UTC

(In reply to Stephen Gordon from comment #2)
> * I do not see this stanza present in the Ubuntu packaging and the docs:

For clarity:

* I do not see this stanza in the DevStack config.
* I do see it in the Ubuntu packaging and the docs.

Comment 4 Sahid Ferdjaoui 2017-04-12 14:15:53 UTC


*** This bug has been marked as a duplicate of bug 1441200 ***

Comment 5 Chris Dent 2017-04-12 14:20:33 UTC

(In reply to Stephen Gordon from comment #3)
> (In reply to Stephen Gordon from comment #2)
> > * I do not see this stanza present in the Ubuntu packaging and the docs:
> 
> For clarity:
> 
> * I do not see this stanza in the DevStack config.

That's because if using mod wsgi is turned on, then keystone will use mod-wsgi and keystone adds that Directory stanza, globally. The missing Directory stanza has been reported to Ubuntu as a bug as well and it also has been explained to multiple parties that making that change is not ideal and really the wsgi-script should go somewhere else, but...?

At the moment nova does not provide much in the way of concrete info on a canonical deployment structure. There is some info here but is very hand wavey: https://docs.openstack.org/developer/nova/placement.html

I agree that it is all a bit messed up and there's as yet no clear definition of how things could be. I created this bug report in response to helping someone who was trying to use RDO packages with the "official" docs. There's of course nothing wrong with having the location be /nova-placement-api [1] but that will only work if the service catalog has the corresponding entry, and the docs do not.


[1] Though: since the expectation is that placement will eventually be extracted from nova and be a service that is used by lots of openstack projects, settling on the name nova-* doesn't seem very future proof.