Requirements for the Cloud Controller and the Controller Node

early release

  • You can add one or more Controller Nodes to the Cloud Controller. But, at least one Controller Node must always be running in order to turn on and turn off the cloud MediaAgent.
  • Do not use a power management enabled cloud MediaAgent as a Controller Node.
  • For a cloud MediaAgent that is deployed in Azure Resource Manager (ARM), create an ARM virtual client.

    For more information, see Adding a Microsoft Azure Hypervisor.

  • When you create the virtual client for the Cloud Controller, do the following:
    • For Azure, configure an Azure application ID that is assigned to the Contributor role during the virtual client creation. Also, create a Cloud Controller that is within the same subscription as the cloud MediaAgent.

      For more information about Azure user permissions, consult the Azure documentation.

    • For Amazon, configure an Amazon user account with the "ec2:StartInstances", "ec2:StopInstances", "ec2:DescribeRegions", "ec2:DescribeAvailabilityZones" and "ec2:DescribeInstances" permissions during the virtual client creation.

      If the user account has IAM role, then the first Controller Node should be on Amazon and owned by the same user account. The Controller Node must be online always to perform power management operation.

      For more information about Amazon user permissions and roles, consult the Amazon documentation.

    • For VMware vCenter Hypervisor, configure an user account with the Power Off and the Power Off permissions during the virtual client creation.

      For more information about VMware vCenter user permissions, see Virtual Machine - Interaction Permissions.

Last modified: 9/12/2018 2:49:53 PM