[
https://issues.apache.org/jira/browse/LIBCLOUD-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hutson Betts updated LIBCLOUD-122:
----------------------------------
Attachment: updated-network.diff
I'm attaching an updated network diff to account for PEP8 compliance.
> Unified Virtual Network Support
> -------------------------------
>
> Key: LIBCLOUD-122
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-122
> Project: Libcloud
> Issue Type: Improvement
> Affects Versions: 0.6.0
> Reporter: Hutson Betts
> Labels: api-change, features
> Attachments: network.diff, updated-network.diff
>
>
> A project I am currently working on involves the management of virtual
> networks using OpenNebula's OCCI API. These virtual networks are necessary to
> facilitate what Amazon calls "Virtual Private Clouds". Basically, I deploy a
> set of virtual machines, interconnected by a set of virtual networks, vnets,
> and using ebtables, isolate those virtual networks from one another. This
> effectively creates a virtual private cloud within my cloud infrastructure.
> However, there is no support in libcloud to orchestrate virtual private
> networks. I know OpenNebula's OCCI supports virtual networks and there is
> documentation for Amazon's VPC (Docs: Amazon Virtual Private Cloud (API
> Version 2011-07-15))
> Would a new, fourth, component to libcloud be required? Say: "Virtual
> Networks - services such as Amazon VPC and OCCI
> (libcloud.network.*)"
> Therefore I wanted to propose the creation of a new networking library to
> unify the creation and management of virtual networks across cloud providers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
