Bug 1296146 - [RFE] specify the AMQP server IP address for Openstack providers
Summary: [RFE] specify the AMQP server IP address for Openstack providers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Julian Cheal
QA Contact: Marius Cornea
URL:
Whiteboard: openstack
: 1103965 1255324 (view as bug list)
Depends On:
Blocks: 1326509
TreeView+ depends on / blocked
 
Reported: 2016-01-06 13:08 UTC by Marius Cornea
Modified: 2019-11-14 07:17 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1310114 (view as bug list)
Environment:
Last Closed: 2016-09-08 14:09:06 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marius Cornea 2016-01-06 13:08:18 UTC 
Description of problem:
We're not able to specify the AMQP server IP address for Openstack providers. When deploying an undercloud with SSL enabled the Keystone endpoints are set on a different IP address than the one RabbitMQ uses to bind. Thus the RabbitMQ server can't be reached from Cloudforms side.
Comment 3 Tzach Shefi 2016-02-04 13:13:09 UTC 
Also need to support Staypuft installed Openstack, in my case an old Juno HA deployment, Rabbit is running at port 35672. 

I've installed it a while back, don't remember (or think) I had done any custom rabbit port settings. Other than port issue, Rabbit only listens on internal staypuft IP's  (192.168.0.X) this is another problem not related, probably  could be fixed on Staypuft installer's side. 

Tested with CFME 5.5.2.4.20160127105142_395c086
Comment 4 Greg Blomquist 2016-02-18 21:35:39 UTC 
Julian, this is dependent on the multi-endpoint work you're working on.
Comment 5 Greg Blomquist 2016-02-19 21:39:48 UTC 
*** Bug 1255324 has been marked as a duplicate of this bug. ***
Comment 6 Greg Blomquist 2016-02-19 22:59:00 UTC 
*** Bug 1103965 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.