cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

CloudCenter Core Fundamentals: Brownfield Considerations (v4.8)

532
Views
0
Helpful
0
Comments

Cloud Support

  1. VMware
  2. AWS
  3. Azure RM
  4. OpenStack


NOTE: Do NOT attempt to import any virtual machines that are functionally required for CloudCenter to operate (CCO, AMQ, Monitor, etc). Doing so will cause service interruption to the CloudCenter platform.


RBAC


  1. Only those users who “own” the cloud account can view Unmanaged Virtual Machines
    1. Root Tenant -> Root Tenant Owner -> AWS Cloud Account (owner) -> Access to Unmanaged [AWS Cloud Only]
    2. Root Tenant -> Root Tenant Admin -> VMware Cloud Account (owner) -> Access to Unmanaged [VMware Cloud Only]
    3. Root Tenant -> Root Tenant Owner -> GCE Cloud Account (owner) -> No Access to Unmanaged [Unsupported Cloud]
    4. Sub-Tenant of Root -> Sub-Tenant Owner -> AWS Cloud Account (owner) -> Access to Unmanaged [AWS Cloud Only]
  2. Once the Unmanaged VM is imported by the cloud account owner, they can be shared to other users
  3. The import requires either privileged user credentials or an SSH key
  4. The access control options displays during the import process, allowing the owner to “Share” the virtual machines with other users/groups
  5. The cloud account owner has special ownership privileges over the imported virtual machine


Metering

  1. Metering costs starts immediately after the VM is successfully imported
  2. Metered accounting happens hourly and applies to both greenfield and brownfield
  3. Metered accounting only applies when a virtual machine is active (in a running/powered on state)


Process


  1. During import, CloudCenter will find an “Instance Type” that is symmetric to the hardware specifications of the virtual machine
    1. In public clouds and OpenStack based clouds, the instance sizes/flavors are standardized so this process is seamless
  2. The exception occurs when a virtual machine is imported into a VMware cloud
    1. In this case, if there are no matching Instance Types, CloudCenter will automatically create a new Instance Type and place it in the Cloud Region
    2. This new Instance Type will be created if and only if the user importing the virtual machine has ownership of the cloud account and has management privileges over the Cloud Region
    3. The new Instance Type will have a zero dollar price, so when it is imported by default it will only display the runtime and not the cost
    4. The new Instance Type will not automatically map to any Image definitions, so it will not affect the user deployment experience
  3. The import does not automatically inject the CloudCenter agent into the VM, this is a separate task to perform
  4. Once a virtual machine is imported and becomes a Managed VM it qualifies as a target for actions from the Actions Library - be they of the platform (OOB) or custom variety
    1. To qualify as a target for actions that require in-guest execution of commands/scripts, the imported virtual machine must also have the CloudCenter agent installed
  5. Batch execution of certain actions from the library can be performed when multiple VMs are selected from the list of Managed virtual machines
  6. Search function does not apply to all fields and accept alpha numeric input


Display


  1. The Managed VM list displays the number of active virtual machines
    1. If a virtual machine was imported 60 days ago and was powered on for 27 days and is currently powered off, it would appear in the 60D filter but would not appear in the 30D filter
  2. Brownfield (imported) virtual machines differ from greenfield (provisioned) ones, so the filtered display of VMs may differ because of that
  3. Actions from the Actions Library are contextual, they depend on the cloud in which the VM runs, the current state and the RBAC privileges on the VM
CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards
This widget could not be displayed.