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

From EGIWiki
Jump to: navigation, search
Line 15: Line 15:
 
If such standards are available in the federated cloud infrastructure, the users will be able to implement monitoring/management tools for their workflows.
 
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  
+
== Steps for the scenario fulfillment ==
 
=== Information gathering steps ===
 
=== Information gathering steps ===
 
The steps I identify to have a comprehensive description of the current situation:
 
The steps I identify to have a comprehensive description of the current situation:
Line 21: Line 21:
 
## Collect requirements and use cases from the users communities.
 
## Collect requirements and use cases from the users communities.
 
# List the currently available standards available, and map them - if possible - to the technologies implemented in the testbed.
 
# List the currently available standards available, and map them - if possible - to the technologies implemented in the testbed.
# Map the users requirements to the existing implementations. Assess if there are missing features in the current implementations and standards.  
+
# Map the users requirements to the existing implementations and standards. Assess if there are missing features in the current implementations and standards.  
 
# Identify if there are standards eligible to be suggested as common standards.
 
# 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:
 
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
 
# Technology providers should provide the status change notifications through standard formats and transport protocols
Line 32: Line 32:
 
'''Comments to the steps list, or about any other aspect of the scenario are more than welcome'''
 
'''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
+
== Scenario collaborators ==
this scenario.
 

Revision as of 17:07, 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.

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