Bug 795901

I think the best way to document the difference between the two is to call one "pre-defined"/"provider-defined" (under "Cloud Resource Providers" and the other as "user-defined" (under "Content").

Any additional thoughts?

no no no..

typically referred to as front end and back end clusters or realms..

Cloud Resource Clusters' under Cloud Resource Providers shows ALL the available clusters for a provider

Cloud Resource Clusters' under content shows what the user has mapped for their use from the available clusters..

confusing yes
crappy use of language .. yes..

I suspect this is already documented, if not please contact dev for specifics.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
CloudForms Cloud Engine contains locations for two different sets of Cloud Resource Cluster information. This might cause confusion about the different types of Cloud Resource Clusters.

Please note the difference between the two locations:

* Under Cloud Resource Providers, Cloud Resource Cluster shows all available clusters for a provider. 

* Under Content, Cloud Resource Clusters shows the user-defined mappings from the available clusters.

CloudForms Cloud Engine users select the appropriate Cloud Resource Cluster section based upon this distinction.

Didn't we agree to change the language of the "back end/provider" clusters to "Provider Realms"?

If I'm remembering this correctly, under Content you'll see Cloud Resource Clusters and under Cloud Resource Providers you'll see Provider Realm. We wanted to use different terms to make the distinction clearer. A  Provider realm is a list of provider-specific entities that generally specifies a notion of "locale", but the meaning is different per-provider. We use the term 'realm' because that's the Deltacloud term for it, and everything to the providers goes via the Deltacloud API. For RHEV these are clusters, for ec2 they're availability zones.

On the other hand, the Cloud Resource Cluster is a "front end" concept, defined by a Cloud Engine admin that allows the admin to map a Cluster to _either_ one or more Cloud Resource Providers _or_ one or more Provider Realms. In both cases this allows the admin to give the user a way to more directly influence where an application will be launched. The difference is that mapping to a Provider (or providers) results in the instances being launched in one of the mapped providers without any further realm-scoping at the deltacloud level. By mapping to one or more provider realms, not only are the instances launched in one of the providers represented by the chosen realm, but they're launched in that particular realm.

For example, if the Cloud Resource Cluster is mapped to a single RHEV provider (datacenter), then the application will be launched in that datacenter without specifying a particular cluster (the default cluster will be used). If it's mapped to a RHEV realm (cluster), then the application will launch not only on that provider (datacenter) but in the specific provider realm (RHEV cluster) specified.

Created attachment 569281 [details]
Screenshot of Cloud Resource Clusters section under Cloud Resource Providers

> Didn't we agree to change the language of the "back end/provider" clusters to
> "Provider Realms"?

AFAIR, there was the name change from "Realm" to "Cloud Resource Cluster" across all of Conductor, but I hadn't heard of any changes of the back-end "Cloud Resource Clusters" to "Provider Realms".

Having said that, I totally agree there should be some distinctive naming between the two. 

> If I'm remembering this correctly, under Content you'll see Cloud Resource
> Clusters and under Cloud Resource Providers you'll see Provider Realm.

I've checked my build of Cloud Engine (0.8.0-41.el6) and it still says "Cloud Resource Clusters" under "Cloud Resource Providers" (see attachment). Is this correct or should it be "Provider Realm"?



It would be great to call the back-end clusters/realms something distinctive from the front-end/user-defined clusters/realms, which is something I'll document in greater details for the 1.1 guides. However, for 1.0's release notes, does the text in "Technical Notes" suit as a basic description of the difference between the back-end and front-end concepts?

Doc update will occur for 1.1. Release note to occur for 1.0.

LKB

Rel note added in CloudForms Cloud Engine section.

Back to assigned for doc update.

LKB

Added Docs Text to 1.1 docs

Referring to 

http://documentation-devel.engineering.redhat.com/docs/en-US/CloudForms/1.1/html-single/Cloud_Engine_User_Guide/index.html#sect-Cloud_Resource_Clusters


Section 4.4.1. Cloud Resource Clusters

CloudForms Cloud Engine contains locations for two different sets of Cloud Resource Cluster information. Please note the difference between the two locations.

    Under Cloud Resource Providers, Cloud Resource Cluster shows all available clusters for a provider.

    Under Content, Cloud Resource Clusters shows the user-defined mappings from the available clusters. 

CloudForms Cloud Engine users select the appropriate Cloud Resource Cluster section based upon this distinction. 
=======================================================

Under Cloud Resource Provider , Cloud Resource cluster is renamed to Provider Realms . Please change that.

Created attachment 627788 [details]
Provider realms

Created attachment 631667 [details]
Provider Realms added

https://documentation-devel.engineering.redhat.com/docs/en-US/CloudForms/1.1/html/Cloud_Engine_User_Guide/sect-Cloud_Resource_Clusters.html

This documentation has now been dropped to translation ahead of publication. For any further issues, please open a new a bug.

LKB

This document is now publicly available on access.redhat.com. For any further issues, please raise a new bug.

LKB