Virtual Router as an OpenNebula resource
|Category:||Core & System|
|Target version:||Release 5.0|
This issue is to redesign the virtual router.
The main goal is to integrate the virtual router as a new OpenNebula resource, to create and manage virtual routers from the opennebula interfaces.
Feature #4215: VRs have NICs defined
VRs can request vnet leases. If a vm template has a
VROUTER_ID, the NICs from that VR are merged into
the template. If the VR NIC has a floating IP, it
is added as VROUTER_IP.
Feature #4215: Hide vrouter VMs in topology, show IPs in VR tooltip
Plus new 'fit viewport' button, and more style tweaks
Feature #4215: Reverse NETWORK and NETWORK_ID priority
When requesting a vnet, NETWORK had priority over _ID.
If the NIC was taken from the VR, the NETWORK was set
but the _UNAME or _UID was not. In this case, VR
instantiate only worked for the owner of the VNet.
The priority of IMAGE and IMAGE_ID for disks is also
reversed, for consistency
feature #4215: Simplify interface for util::gsub. Decouple Request methods to
better support static request actions.
feature #4215: Add decorator interface for Quota class. Implement a
Virtual Router decorator for QuotaNetwork
feature #4215: Remove public Marketplaces, even if they have images.
Associated apps are also removed.
feature #4215: add dummy pre and reconfigure drivers
For drivers azure, ec2, softlayer and xen
feature #4215: Generate context before a restore action. Context is
regenerated whenever a it is needed to capture VNET and NIC updates
feature #4215: Update marketapps from external marketplaces when MD5 or