Feature #3306
Import vCenter Networks as OpenNebula VNETs
| Status: | Closed | Start date: | 11/06/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Tino Vázquez | % Done: | 0% | |
| Category: | vCenter | |||
| Target version: | Release 4.10.2 | |||
| Resolution: | Pull request: |
Description
VNETs will be created potentially using as BRIDGE the vCenter name of the Network. OpenNebula needs to allocate an address to each VM in the VNET, for vCenter VNETs we may require a dummy AR without address or simply use ETHER ARs to control MAC assignment.
Related issues
Associated revisions
Feature #3306: Add import vnet from vcenter functionality
Feature #3306: Add Distributed Network support for vCenter
Add VLAN retrieval
Feature #3306: Add size to network importing
Feature #3306: Add IPv4, IPv6 support for vCenter networks
Feature #3306: Fix wrong AR template creation
feature #3306: Fix vcenter network layout
Feature #3306: Add model aliases
feature #3306: Fix bug in vcenter driver
Feature #3306: Add Distributed Network support for vCenter
Add VLAN retrieval
Feature #3306: Add size to network importing
Feature #3306: Add IPv4, IPv6 support for vCenter networks
Feature #3306: Fix wrong AR template creation
feature #3306: Fix vcenter network layout
Feature #3306: Add model aliases
feature #3306: Fix bug in vcenter driver
feature #3306: Fix template-tab.js merge
History
#1
Updated by Ruben S. Montero over 6 years ago
- Blocks Feature #3307: Attach/Detach NIC operations for vCenter added
#2
Updated by Ruben S. Montero over 6 years ago
- Status changed from Pending to New
#3
Updated by Ignacio M. Llorente over 6 years ago
- Assignee set to Tino Vázquez
#4
Updated by Ruben S. Montero over 6 years ago
- Target version changed from Release 4.12 to Release 4.10.2
#5
Updated by Tino Vázquez over 6 years ago
- Status changed from New to Closed
Code in branch and documentation updated