Difference between revisions of "Fedcloud-tf:WorkGroups:Scenario6"

From EGIWiki
Jump to: navigation, search
(Input for blueprint)
Line 109: Line 109:
== Operative steps ==
== Operative steps ==
=== Test ActiveMQ based technologies ===

Revision as of 18:02, 30 January 2012

Main Roadmap and Innovation Technology For Users For Resource Providers Media

Workbenches: Open issues
Scenario 1
VM Management
Scenario 2
Data Management
Scenario 3
Information Systems
Scenario 4
Scenario 5
Scenario 6
Scenario 7
Federated AAI
Scenario 8
VM Image Management
Scenario 9
Scenario 10
Scenario 11

Scenario 6: VM/Resource state change notification

Leader: Peter Solagna, EGI

The scenario enables:

  • Resource providers to notify interested parties about changes in the user's VM state of a proposed state change in the VMM.
  • End user to build automated VM management and reactive workflows in user space.

Such notification system must enable automatic notification consumers and so there is the need to identify the standards to be used:

  • Standard for the payload in the notification messages
  • Standard for the messages transport

If such standards are available in the federated cloud infrastructure, the users will be able to implement monitoring/management tools for their workflows.

Steps for the scenario fulfillment

Information gathering steps

The steps I identify to have a comprehensive description of the current situation:

  1. List the notification systems adopted by the technologies currently deployed in the FedClouds testbeds.
    1. Collect requirements and use cases from the users communities.
  2. List the currently available standards available, and map them - if possible - to the technologies implemented in the testbed.
  3. Map the users requirements to the existing implementations and standards. Assess if there are missing features in the current implementations and standards.
  4. Identify if there are standards eligible to be suggested as common standards.

Operative steps

When the points above are done, I suggest the following, operative, tasks:

  1. Technology providers should provide the status change notifications through standard formats and transport protocols.
  2. User communities should test these notification mechanisms in their workflows, or implementing a client prototype.

Comments to the steps list, or about any other aspect of the scenario are more than welcome

Scenario collaborators

Role Institution Name
Scenario leader EGI.eu Peter Solagna
Collaborator OeRC Matteo Turilli

Step 1: List the notification systems currently adopted

VM Manager What is automatically notified Any standard in the message format used Message transport protocol
Open Nebula states of VM NO Users have to query explicitly the result are in XML
OpenStack Not clear yet, still at blueprint stage[1][2][3] Atom 1.0[1] PubSubHubbub (PSH)[1]
WNoDeS States of VM: RUNNING, PENDING, ABORTED, DESTROYED No Users have to query explicitly the result are in XML

Step 2: List of the standard available for notification message

Standard name Message Format/Transport Comments and information
Atom 1.0 Message Format Implemented by OpenStak
PubSubHubbub Transport Implemented by OpenStak


Input for blueprint

Description of the scenario6: Notification system

Use cases for this scenario

Operative steps

Test ActiveMQ based technologies