Page History

...

• When a user logs in, a change had to be made to add the 'api key' to the CS user object in the browser
• The load balancer exposes the URL that is used by both CloudStack and Swift calls
  • One reason for this is to make sure the Swift traffic does not go through the CS server which would create a bottleneck
  • Another reason is to be able to make AJAX calls to Swift without having issues with the Same Origin Policy
• All Swift calls are done using AJAX and the load balancer handles routing the calls to Swift
• Swift uses the HTTP PUT verb and browsers do not support the PUT verb, so the client sends the requests as POST and the LB translates to PUT
  • This means that the current implementation does not support any of the Swift API calls that require POST
  • More details on this can be found in the HAproxy config attached at the end of this document
• This functionality requires the 'mauth' middleware to be installed on Swift
• The mauth configuration points to CS (the load balancer actually) and requires the 'admin' keys (mauth requires 'listUsers' API call for all accounts)
• TODO - Important - A global variable needs to be added to CS to enable/disable the Object Store functionality
• TODO - Medium - Clean up the couple places where text is not translatable
• TODO - Nice-to-have - Find a cleaner solution when someone tries to download a folder or container (maybe I should just hide download of those)
• TODO - Nice-to-have - Make the public URL for a public object clickable (just text right now)
• TODO - Nice-to-have - Reflect the full object path in the breadcrumb when an object is in detail view
• TODO - Nice-to-have - Remember what containers and folders were open and reopen them after a new container is added (enhancement)
• TODO - Nice-to-have - When a container or folder is clicked, expand/collapse it rather than forcing the arrow to be clicked (CS treeView enhancement)

Use cases

put the relevant use case/stories to explain how the feature is going to be used/workFor now, refer to the Feature Specifications or the UI Flow sections.

Architecture and Design description

...

Most of this has already been covered.  I will add to this section as questions arise or if there is a request for more detailed descriptions of the different pieces.

Web Services APIs

list No changes to existing web services APIs and new APIs introduced with signatures and throughout documentationthe CloudStack APIs

UI flow

• either demonstrate it visually here or link to relevant mockups

...