Request #4401
Assign VNET to Host/Cluster
| Status: | Closed | Start date: | 04/11/2016 | |
|---|---|---|---|---|
| Priority: | High | Due date: | 05/01/2016 | |
| Assignee: | - | % Done: | 0% | |
| Category: | Drivers - Network | Estimated time: | 2.00 hours | |
| Target version: | - | |||
| Pull request: |
Description
In order to support multi-host environment when a VLAN is not available (A scenario where each host has an individual subnet)
History
#1
Updated by Jonathan Philipos about 5 years ago
Currently we have a template that we would like to add specific hosts to it, however since each host has it's own VNET we cannot specify/link the VNET to the Host in order to avoid deploying a VM inside a host with a vnet that isn't configured with that host.
In order to fix this, being able to assign a 'VNET' -> 'HOST' will allow us to select all the relevant hosts/vnets and OpenNebula deploys the VM in a host with an assigned network to that host.
Does OpenNebula currently support this scenario? If not - can we add this support?
#2
Updated by Jonathan Philipos about 5 years ago
Seems like you can assign Clusters to VNET's - but you cannot assign hosts to clusters. Can we support that in case each host is independent.
#3
Updated by Ruben S. Montero about 5 years ago
Hi
A cluster is a set of hosts, vnets and datastores that can work together. Regarding your question:
1.- In 5.0 we have included multi-cluster support for VNETs
2- Network driver has been moved to the VirtualNetwork, so each VNET can be implemented with a different driver.
For OpenNebula 4.14 maybe you can use the cluster concept and the VLAN attribute, so a VNET with VLAN=NO will not implement any VLAN although the host has a vlan driver.
#4
Updated by Ruben S. Montero about 5 years ago
- Tracker changed from Feature to Request
- Status changed from Pending to Closed
I'm closing this because it seems we have all the features needed, will reopen if needed.