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

From EGIWiki
Jump to: navigation, search
Line 4: Line 4:
  
 
<font color="red">Leader: Peter Solagna, EGI</font>
 
<font color="red">Leader: Peter Solagna, EGI</font>
 +
 +
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.
 +
 +
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.
 +
2) List the currently available standards available, and map them - if possible - to the technologies implemented in the testbeds.
 +
3) Assess if there are missing features in the current implementations and standards. User Communities requirements needed.
 +
4) Identify if there are standards eligible to be suggested as common standards.
 +
 +
 +
When the points above are done, I suggest the following, operative, tasks:
 +
# Technology providers should provide the status change notifications through standard formats and transport protocols
 +
# 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'''
 +
 +
I would need also to know who is willing to collaborate directly to
 +
this scenario.

Revision as of 16:54, 14 November 2011

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
Accounting
Scenario 5
Monitoring
Scenario 6
Notification
Scenario 7
Federated AAI
Scenario 8
VM Image Management
Scenario 9
Brokering
Scenario 10
Contextualisation
Scenario 11
Security



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.

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. 2) List the currently available standards available, and map them - if possible - to the technologies implemented in the testbeds. 3) Assess if there are missing features in the current implementations and standards. User Communities requirements needed. 4) Identify if there are standards eligible to be suggested as common standards.


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

I would need also to know who is willing to collaborate directly to this scenario.