Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Current secondary storage is at zone level. S3 like is object-store or integration with other object-stores(like Hadoop) is required to move data across Regions. Each Region should have object store and the data within it should be available to all zones within the region. Utility to move data across Regions should be supported. Templates and Snapshots will be stored in this object store. Requirements for  S3 based secondary storage.  This is tracked in ticket CLOUDSTACK-714 separately

ELB

ELB will be elevated to Region level. ToDo: Add ELB FS Jira ticket CLOUDSTACK-653

EIP

ToDo: Add EIP FS linkEIP enhancements CLOUDSTACK-652

Authentication Service

 An authentication service will available for components like object-store to authenticate and get account information using getUser API

...

Object Store: This feature assumes that S3 like object store is available. Either implemented in CloudStack or through integrations

Limitations

To be added

Usage

Usage records will be generated by each Region separately. Portal layer above CS should combine usage across Regions into a consolidated invoice.

...

The same applies for Domains.

Create: For any resource created in Region A, MS is Region A  will send API requests to peer Regions along with external Id of the resource. API requests are sent to the peer Regions using the end_point of each Region

Update/Remove: Request is forwarded to the source region. After updating the resource locally, source region sends API requests to peer regions with ispropogate flag set to true.

Authentication

Once logged in User should be able to switch from one Region to another without providing credentials again (Single sign-on?)

...

  • createAccount 
    1. New parameters
      1. accountid : External Id for the Account. Could be UUID or domainpath + username or any string unique across Regions
      2. userid: External Id for the User. 
      3. regionid: Id of the source Region where Account creation request was initiated
  • deleteAccount, updateAccount, disableAccount, enableAccount
    1. New parameters
      1. ispropagate: Boolean flag which indicated if the API call is being propagated from another Region

Limitations

1. Since all update/delete operations are forwarded to the source region (i.e the region where the resource was initially created), if the source region is down, these operations will fail

Upgrade

During upgrade, flexibility will be provided to move existing zones into any Region.

...