Bug 850486

Summary:	Using RHS-C to manage RHS AMI instances
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vidya Sakar <vinaraya>
Component:	rhsc	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CANTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	knarra, mmahoney, mmccune, rhs-bugs, rwheeler, sankarshan, ssampat
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-29 15:11:29 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 Vidya Sakar 2012-08-21 16:18:58 UTC

RHS-C should be enhanced to administer RHS AMI instances. Things that we need to support include but not limited to
 - EBS management
 - Availability Zones
 - Discovery

Comment 3 Dusmant 2015-02-12 05:54:39 UTC

It will be taken after Everglades.

As per discussion with PMs and field folks, RHSC will be running on an AWS instance while managing RHS Nodes cluster running on AWS instances. For the time being, an on-prem RHSC instance will not manage the AMI gluster cluster nodes. May be later, but that's not priority.

Comment 5 Sahina Bose 2015-09-30 11:19:59 UTC

*** Bug 1159758 has been marked as a duplicate of this bug. ***

Comment 6 Sahina Bose 2018-01-29 15:11:29 UTC

Thank you for your report. This bug is filed against a component for which no further new development is being undertaken