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

Bug 1108651

Summary:	RFE: In the services menu in a new deployment flow - services should be aggregated
Product:	Red Hat OpenStack	Reporter:	lpeer <lpeer>
Component:	rubygem-staypuft	Assignee:	Scott Seago <sseago>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Omri Hochman <ohochman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0 (RHEL 7)	CC:	aberezin, hbrock, mburns, morazi, nyechiel, oblaut, rhos-maint, sseago, yeylon
Target Milestone:	ga	Keywords:	FutureFeature
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1108611
Clones:	1108662 (view as bug list)		Environment:
Last Closed:	2014-08-05 19:51:37 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:
Bug Depends On:	1108611
Bug Blocks:

Comment 1 Scott Seago 2014-06-12 14:04:09 UTC

I'd rather group them in the other way (by node first, then services on the node) since we have metadata for that. Doing it this way would require us to maintain a separate set of relationships that we're not currently tracking.

Comment 2 Mike Burns 2014-06-12 15:36:43 UTC

We want that as dynamic as possible.  Eventually, we'll want to let people pick and choose what should be on each host.

Comment 3 Arthur Berezin 2014-06-16 13:15:48 UTC

At this sage we should make the list reflect openstack related services

ie 

Neutron Network Node (instead of "networker")
--L3 Agent
--DHCP Agent

Controller
--Neutron Service
--Keystone Service
--Nova-API
--etc'

Comment 4 Scott Seago 2014-06-18 20:03:27 UTC

I think this bug needs to be reconsidered in light of the ongoing wizard redesign.

I think the simplified/smaller list of services in the wizard (where params don't map directly to puppet classes) may solve this bug already -- the puppet-level service listing will still show up in a couple places (the list of services active per node, and the "advanced" view/configuration summary screen where the low-level config details show up), but the "services" listed in the new deployment workflow where the commonly-used parameters are set will already list the services at the Openstack level.

In any case, what Arthur suggests in comment 3 is how the puppet-level service listing is currently organized (although there are other bugs open relating to specific details that may need to change).

Comment 6 Mike Burns 2014-08-05 19:51:37 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.