Bug 828518 - [RFE] Support local entitlement and update at Cloud Resource Provider in CloudForms Achitecture
[RFE] Support local entitlement and update at Cloud Resource Provider in Clou...
Status: CLOSED WONTFIX
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Subscription Management (Show other bugs)
6.0.0
Unspecified Unspecified
unspecified Severity low (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
: FutureFeature, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-04 16:19 EDT by james labocki
Modified: 2016-12-12 09:21 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-12-12 09:21:52 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description james labocki 2012-06-04 16:19:51 EDT
Currently customer's IT-security will not allow this product to be deployed inside their firewall to manage systems at Amazon: 

    Having systems connect back to inside their perimeter security is usually seen as breach of the security architecture. 

    A VPN actually makes it worse, because it moves the perimeter security to the cloud resource provider. 

This prohibits all major use-cases. Purely on-premise use-cases using RHEVM and/or VMWare may be feasible, but in my opinion for this case the RHEV-M user portal and Satellite/cobbler are more usable for now. Also, it leads to increased cost from a data transfer standpoint if data is not local within the provider.

This is a request to move to an architecture that allows update and entitlement of systems to occur in the cloud resource provider and have federation of the data into the on-premise system in a secure manner.
Comment 2 Tom McKay 2016-12-12 09:21:52 EST
Due to the age of this BZ it is not currently scheduled for implementation. If there is more info for the feature and continued customer need, please reopen. Associating with customer cases will also help in prioritization.
Thank you

Note You need to log in before you can comment on or make changes to this bug.