Requesting Updates, Additions, or Changes to Your Cloud

As you use your cloud, you may want to add resources or make other changes to expand its capabilities. You can make many changes on your own using the Dashboard, command-line interface (CLI) or API, such as adding instances, networks, and projects. Some additions to your cloud require the help of Metacloud Support, such as the following:

  • virtual LANs (VLANs)
  • provider networks
  • floating IP addresses
  • a new storage backend, such as Pure or SolidFire
  • Dashboard branding
  • LDAP server

To request these types of changes, submit a P4 Support request in this site. 

Expediting Your Request for Changes

When creating a request, make sure to use the appropriate priority level. Unless the resource is necessary to prevent or stop a serious disruption of your operations, a P4 level is usually sufficient. See the section on setting priority in the solution Expediting Your Support Case with Important Information.

Note: Do not use the Build Request priority for one of these types of changes. Build requests are for changes to the Metacloud build, such as a new AZ, additional hypervisors, or the replacement or upgrade of Metacloud Control Planes (MCPs).

As with any Support request, include as much relevant information as you can. The fewer follow-up questions the Support team will need to ask, the sooner they can provide the resources you need. The following examples provide some suggestions:

VLANs

When requesting additional VLANs, specify available subnets and IDs for the new VLANs. For information about VLAN IDs, see, the section Default VLAN IDs in Open Network Ports (Step 6) in the Metacloud Controller Bundle Design and Implementation Guide.

Provider Networks

When requesting a new provider network, provide the following information:

  • available VLAN ID 
  • project ID
  • IP address range
  • any addresses that you don't want DHCP to provide, such as for routers 
  • gateway IP address 

Floating IP Addresses

For an additional floating IP subnet allocation, indicate the following:

  • IP address range
  • any IP addresses that need to be reserved for use by other network devices in the subnet, such as two IP addresses for Hot Standby Router Protocol (HSRP).
  • gateway IP address

Also, to prevent any issues with the provision of the subnet, make sure it is routed via the external IP address of the Cisco Aggregated Services Router (ASR), so that your "upstream" router can send packets to the ASR for the specified subnet.

Storage Back-end Solution

To add a supported storage back-end solution, such as Pure or SolidFire, indicate the following:

  • storage host name*
  • system requirements, such as disk size*
  • administrative credentials and other pertinent login information for the storage solution*
  • management virtual IP (MVIP) address*
  • storage virtual IP (SVIP) address (for SolidFire)*
  • IP addresses reserved for storage nodes
  • VLAN ID for the network to which the node will be added
  • subnet
  • project ID
  • contact information for the administrator of the storage solution.

*If you don't have this information, consult the administrator of the storage solution.

Dashboard Branding

Attach the logo file for branding the Dashboard to the request. The supported formats are PNG and JPEG, and the dimensions should be 127 by 68 pixels.

LDAP Server

If you want to authenticate Metacloud users via an existing LDAP/AD infrastructure, indicate the following information for the LDAP server:

  • IP address and port number
  • principle name
  • distinguished name (DN) structure details, including organizational unit (OU) and domain component (DC)
  • contact information for the server administrator

Note: A fixed DN structure is required; nested OUs are not supported.

 

 

Have more questions? Submit a request
Powered by Zendesk