Bug 1056112

Summary:	[RFE][tripleo]: Deploying different architecture topologies with Tuskar
Product:	[Community] RDO	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-tripleo	Assignee:	Keith Basil <kbasil>
Status:	CLOSED EOL	QA Contact:	Shai Revivo <srevivo>
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	chris.brown, kbasil, markmc, srevivo, ukalifon
Target Milestone:	---	Keywords:	FutureFeature, Triaged, Upstream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/tripleo/+spec/tripleo-tuskar-deployment-scaling-topologies
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_approved
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-18 06:33:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-01-21 14:26:29 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/tripleo/+spec/tripleo-tuskar-deployment-scaling-topologies.

Description:

Tuskar should allow an admin to deploy overclouds based on different topologies.  Examples are overclouds with multiple compute nodes, 
cinder nodes, neutron network nodes, etc.  Deploying different numbers of each node type should also be supported.

Specification URL (additional information):

https://etherpad.openstack.org/p/tripleo-deployment-scaling-topologies

Comment 3 Christopher Brown 2017-06-17 16:54:53 UTC

Tuskar is long gone so should be closed or updated for tripleo-ui if still relevant (I have no idea, don't use it).