Iteration 4 of the Cloud Provisioning Environment Prototype.

Scope

• Create a baseline set of documentation for OOI construction, as part of the CEI subsystem documentation
• Revise architecture and models for consistency and leave a comprehensive, accessible set of artifacts behind for other (subsystem) teams to look at.
• Support CEI subsystem risk/architecture report.
• Integration work at ANL and at UCSD

Tasks

• Create and agree on a common glossary of terms
• Identify architecture elements, their names and their connection
• Identify necessary interaction protocol and message formats (content and representation/encoding)
• Develop CPE prototype according to architecture and interaction specifications
• Deploy using EC2 and a Nimbus installation

Topics

• CPE Team Meetings
• Glossary of Terms
• Architecture Elements
• A basic Worker AMI design to test the elastic provisioning environment
• Collect Reference and Source Materials

Design

The following figure shows the high level architecture of the Cloud Provisioning Environment Prototype.

 
This prototype makes use of the Messaging Service, represented by a RabbitMQ AMQP Broker. The Magnet framework provides the messaging client for each process to adapt to the Messaging Service. Note that the number of process instances in the above figure merely illustrates the possible existence of multiple instances.

Multiple instances subscribed to an Exchange Point can interact using the "work queue" pattern, realizing load balancing by feeding off the queue as they have resource availability. This avoids overprovisioning need. They can also filter on specific messages in the queue and thus split the work. A combination of both patterns is possible as well. This is application architecture.