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

Bug 1108647

Summary: RFE: The 'Neutron Networker' is missing the list of services running in the network node
Product: Red Hat OpenStack Reporter: lpeer <lpeer>
Component: rubygem-staypuftAssignee: Scott Seago <sseago>
Status: CLOSED CURRENTRELEASE QA Contact: Omri Hochman <ohochman>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0 (RHEL 7)CC: mburns, morazi, nyechiel, rhos-maint, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1108580 Environment:
Last Closed: 2014-08-05 19:51:56 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:
Attachments:
Description Flags
screenshot none

Description lpeer 2014-06-12 11:27:22 UTC
Created attachment 908085 [details]
screenshot

Description of problem:

In 'New Deployment' in 'Host Groups & Available Services' the Neutron Networker box currently includes a single label that says 'Neutron Networker', instead it should include the services running on the Network Node:

1. DHCP agent
2. L3 Agent
3. Metadata Proxy


I recommend to either create a separate service tab for Horizon or change the name of the Neutron(control) service to Controller(Neutron) and include all controller related configuration in that tab.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Mike Burns 2014-06-12 13:20:00 UTC
Scott, if this is a quick fix, then lets get it in, if not, let's defer.

Comment 2 Scott Seago 2014-06-12 14:02:22 UTC
So we had a bug previously to consolidate some of this stuff. This bug is asking us to pull it out again. I'd rather not go back to hard-coding these params, if there's some possibility of handling this on the puppet side -- if this should be 3 separate services, can we look into the work needed to separate the services at the puppet level first, rather than going to the hard-coded param-to-service mapping we're doing for non-HA controollers (which we're trying to go away from)

Comment 3 Scott Seago 2014-06-12 17:04:51 UTC
Mike: here's the bug I mentioned: https://bugzilla.redhat.com/show_bug.cgi?id=1093414

That bug is ON_QA, and it requested we do the opposite of what this bug requests -- i.e. that bug said "consolidate the 3 Neutron Networker services into one service tab", while this bug calls to split them out again.

Comment 4 Mike Burns 2014-08-05 19:51:56 UTC
This bug was handled or obsoleted during the GA2 redesign work.  If you believe that this still applies to the current UI, please re-open this bug.