...

2       Requirements

• Admin should be able to install a management server for a Region and then connect to management servers in other Regions. Each Management Server in each region should know about all other regions and their management servers.
  • Connect To Region
  Admin should be able to create multiple Regions within a CloudStack cloud. I.e., CloudStack should manage multiple regions within a cloud. The following operations should be supported:
  • Create Region
  • Delete Region
  • Update Region
  • List Regions
• Admin should be able to create multiple zones with a Region. Management server cluster manages all the zones within the region. Following Zone operations should be supported on per region basis:
  • Create Zone
  • Delete Zone
  • Update Zone
  • List Zones
• Management Server cluster for each region should only control the infrastructure within that region. In other words, if a management server cluster fails, then only the region managed by that server cluster should be inaccessible for admin and users. It should not have any impact on the other Regions in the cloud
• Each Region should have access to an object store. The object store should be common to all Zones within the Region. I.e., any object stored from a Zone should be visible across all the other zones within the region
• EIP function should be available across both basic zones and across advance Zones within a Region
• ELB function should be available across both basic zones and across advance Zones within a Region
• The administrative hierarchy  (Users, Accounts, Domains, Projects) - should be valid across all the regions. I.e., if admins create domains, accounts and users etc. in one region it should be reflected in other regions as well.
• Authentication credentials – username, password, keys – should be valid across all regions
• Switching between Regions should not require the user to sign-on again (SSO should be supported).
• Resource management should be extended to Region level
  • Available compute, storage, network (IPs, VLANs etc.) resources that are currently tracked should be aggregated and displayed at region level
  • Appropriate global parameters should be available at Region level while the remaining would be available at Zone level
• Usage: All the (per account) usage records should be aggregated to Regions level
• Global Configurations: All of the administrative hierarchy (Domains, Accounts, Users, Projects) related Global Configurations should have consistent values across all regions and has to be propagated when a user modifies a configuration on one of the region.
• Each region should maintain a list of all other regions and their region endpoints.

...

• Users should be required to deploy all the Management Servers of a particular region in one zone.
• Sync of User data can be made optional. If sync of user data is not supported, make sure necessary events are published for a customer to write their own tool to sync user data.

3       UI / UX Requirements

...

• Management Server limited to per Zone can be done in a future release.
• EIP and ELB functions across zones are only supported when both zones are either basic or advance. It is not required to support EIP or ELB across basic and advanced zones
• It is not required to display a dashboard/reports that are aggregated across Regions

6       Bugs

http://bugs.cloud.com/show_bug.cgi?id=2465Regions JIRA Issue

7       Open Items:

• None