The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Federated Cloud IntraCloud Networking"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
''This is a fresh activity, please understand that solutions for this scenario are not yet available. They are mostly in design or development stage.'' | ''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. | |||
The | The scenario is also looking at other services that could be provided: | ||
# Useful '''appliances''' (virtual network elements such as NAT/DHCP, FlowMon, …) | |||
# | # '''Recommendations''' (tools?) for VM images to make them better prepared for different properties of networks in federated environments | ||
# '''Security''' groups / profiles to allow owners to restrict the behavior of their VMs in networks. | |||
= Members= | = Members= | ||
Revision as of 12:38, 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.
The scenario is also looking at other services that could be provided:
- Useful appliances (virtual network elements such as NAT/DHCP, FlowMon, …)
- Recommendations (tools?) for VM images to make them better prepared for different properties of networks in federated environments
- Security groups / profiles to allow owners to restrict the behavior of their VMs in networks.
Members
| Role | Institution | Name |
|---|---|---|
| Scenario leader | CESNET | Zdenek Sustr |
| Collaborator | CESNET | Boris Parak |
| Collaborator | ||
| Collaborator |