Difference between revisions of "Federated Cloud IntraCloud Networking"
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
= Scope = | = Scope = | ||
''This is a fresh activity, please understand that solutions for this scenario are not yet available. They are mostly in design or development stage.'' | |||
The IntraCloud Networking Scenario deals with virtual machine networking '''within the environment of a single provider''' (hence the ''intra'' prefix). It focuses on achieving two main goals: | |||
# Being able to list available networks, pick one and connect virtual machines to it. | |||
# Being able to create new [private] networks, even with non-trivial topologies. | |||
= Members= | = Members= |
Revision as of 11:34, 18 May 2015
Overview | For users | For resource providers | Infrastructure status | Site-specific configuration | Architecture |
Scenarios: | • Federated AAI | • Accounting | • VM Image Management | • Brokering | • IntraCloud Networking |
• Monitoring | • VM Management | • Data Management | • Information Discovery | • Security |
Scope
This is a fresh activity, please understand that solutions for this scenario are not yet available. They are mostly in design or development stage.
The IntraCloud Networking Scenario deals with virtual machine networking within the environment of a single provider (hence the intra prefix). It focuses on achieving two main goals:
# Being able to list available networks, pick one and connect virtual machines to it. # Being able to create new [private] networks, even with non-trivial topologies.
Members
Role | Institution | Name |
---|---|---|
Scenario leader | CESNET | Zdenek Sustr |
Collaborator | CESNET | Boris Parak |
Collaborator | ||
Collaborator |