Feature #2858
Extend Network Model
| Status: | Closed | Start date: | 04/29/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Documentation | |||
| Target version: | Release 4.8 | |||
| Resolution: | fixed | Pull request: |
Description
This is a meta-issue to group multiple networking features. All of them will be develop in the same branch.
In order to accommodate all the requests made to improve the OpenNebula networking flow we'll re-design the data model. Basically, it'll extend the definition of a lease to get rid of the FIXED vs RANGED types.
A network will have any number of address ranges that may even provide specific configuration (e.g. VLAN_ID) or context (e.g. GATEWAY) attributes. The new address ranges could be of any type (Ethernet, IP, IPv6, Dual IPv4+6).
This will effectively decouple the network implementation (e.g. BRIDGE, VLAN...) from the address management, so making possible a self-service model for virtual network provisioning.
The following issues will be addressed:
- #2740: Virtual Networks should be able to select the IP version for addresses
- #2545: Decorrelate networks TYPE and IP management
- #1818: Support for IP reservations
- #1773: Add network groups
- #2818: Let specify IPv6 (apart from MAC and IPv4) addresses for Fixed leases
- #1945: Tag Virtual Network as IPv6 enabled.
Related issues
Associated revisions
feature #2858: Convert to unsigned int from vector attributes
feature #2858: Implementation of Address Range class
feature #2858: Allocate addresses by MAC or IP
feature #2858: Work on AddressRange class
feature #2858. Clear and to_xml on streams for VectorAttributes
feature #2858: First version of AddressRangePool
feature #2858: Integrate AddressRangePool with VirtualNetwork: persistency & initialization
feature #2858: Allocate & free functions for the address range pool
feature #2858: Integrate Address Ranges with VirtualNetwork and VirtualMachine
feature #2858: Adds lease usage information to XML descriptions
feature #2858: Update onevm and onevnet command line tools
feature #2858: Support for Address Range attributes in context
feature #2858: Hold first matching lease if no address range is specified
feature #2858: Hold and Release for IP/MAC addresses in all Address Ranges. Keep compatibility with 4.6 interface
feature #2858: Updated OCA interface for VirtualNetwork objects. Added option to select an address range to hold/release an IP address
feature #2858: Add support for MAC addresses at OCA and CLI
feature #2858: Remove old code
feature #2858: onevnet: do not fail on empty address range pool
feature #2858: Fix error message
feature #2858: Add and remove methods for Address Ranges. Core, OCA and CLI
feature #2858: Update ARs. Core, OCA and CLI. Needs to implement attribute removal
feature #2858: Better update for Address Range.
feature #2858: Fix minor issues in Address Range management
feature #2858: Fix VLAN attribute in address range
feature #2858: Sanitize VLAN attribute defined in Address Range
feature #2858: Add umask to Request attributes
feature #2858: First version of VNET reservation. VNET is created, addresses allocated. Needs to set free addr methods upon reservation removal.
feature #2858: Check quotas for reserve addresses. Update AR on reservation
feature #2858: Look for continous address ranges
Feature #2858: Start redesing of sunstone vnet tab
Feature #2858: Better placement for vnet leases panel
feature #2858: Update parent vnet on removal
feature #2858: Reserve by AR_ID, fix DB storage of reservations
feature #2858: Fix minor memory leaks
feature #2858: Better check for class types. Single AR addtion to prevent out-of-sync NETs
Feature #2858: rm_ar button in sunstone
Feature #2858: New vnet methods in sunstone api
Feature #2858: Add AR creation to vnet wizard
Feature #2858: Add AR wizard
feature #2858: Reserve by IP & MAC
Feature #2858: fix vnet wizard
Feature #2858: fix used leases counter
feature #2858: free by owner returns the number of addressses freed
feature #2858: Update quotas when freeing reserved IPs
Feature #2858: Separate vnet wizard into steps
Feature #2858: Add first AR on pop up
feature #2858: one.vn.[update, update_ar, add_ar, rm_ar] require ADMIN rights
feature #2858: Add reservations to an exisiting network. VNETs are labeled with the PARENT_NETWORK_ID if any. Just one PARENT VNET is allowed
feature #2858: Solve bugs in onevnet reserve. Minor changes in one.vn.reserve
feature #2858: Add free_ar to free a previously reserved address range. Operation needs MANAGE permission on the reservation VNET (rm_ar is ADMIN)
Feature #2858: Individual panel for AR, with a datatable
Feature #2858: improve add AR modal
Feature #2858: Add custom attributes to each AR
Feature #2858: add a progress bar to leases usage
feature #2858: Free address ranges on VNET
feature #2858: Add check in free addr
feature #2858: Fix permission check when adding a reservation to an existing reservation. Quotas always account for the reservation owner
feature #2858: Adjust quotas on VNET chown
Feature #2858: Update AR wizard
feature #2858: Do not allow to make double reservations
feature #2858: Fix AR update on empty allocated addresses
Feature #2858: Remove TYPE column in vnet table
Feature #2858: Remove TYPE column from secondary vnet tables
Feature #2858: Add new vnet AR sub-tab to yaml files
Feature #2858: show reserved vnet id in leases list
Feature #2858: clean leases attribute from table
feature #2858: Do not allow to reserve on the same VNET
Feature #2858: Basic dialog to reserve IPs
Feature #2858: Filter "child" vnet reservations in wizard
feature #2858: Should prevent deadlocks in address reservations
Feature #2858: Show vnet/ar reservation parent
Feature #2858: Advanced options for reservation dialog
Feature #2858: Show vnet leases as a progress bar
Feature #2858: Add the vnet "reservation" column
Feature #2858: VNetTableSelect uses the columns defined in the yaml files
Feature #2858: Enable the Reserve button only for "parent" networks
Feature #2858: fix syntax bug
Feature #2858: Add tooltips to vnet wizard
Feature #2858: Disable ar reservation update. Disable fixed inputs in ar update
Feature #2858: Return error for wrong AR update actions. Do not allow to update a reservation SIZE
Feature #2858: Improve onevnet updatear command
Feature #2858: Use foundation abide to set required inputs in vnet wizard
Feature #2858: Clear vnet cache after a reservation is made or cancelled
Feature #2858: Set mandatory inputs for AR
Feature #2858: Add actions to manage vnet reservations in user.yaml
Feature #2858: Move inputs from General to Context section
Feature #2858: Add onedb upgrade script
Feature #2858: Free leases even if the VM/NIC does not have AR_ID
This way VMs created in ONE < 4.8 will correctly free the IPs
Feature #2858: Remove leases fixes from fsck
Feature #2858: Rename NIC/IP6_SITE to _ULA in onedb upgrade
Feature #2858: Fix IP6 formatting in sunstone
Feature #2858: Fix onevnet cli columns
(cherry picked from commit 0d14b64e484c9f02249fec4df0a6dbbb349a2c3f)
Feature #2858: Update Java OCA
History
#1
Updated by Ruben S. Montero about 7 years ago
- Related to Feature #2740: Virtual Networks should be able to select the IP version for addresses added
#2
Updated by Ruben S. Montero about 7 years ago
- Related to Feature #2545: Decorrelate networks TYPE and IP management added
#3
Updated by Ruben S. Montero about 7 years ago
- Related to Feature #1818: Support for IP reservations added
#4
Updated by Ruben S. Montero about 7 years ago
- Related to Feature #1773: Add network groups added
#5
Updated by Ruben S. Montero about 7 years ago
- Related to Feature #2818: Let specify IPv6 (apart from MAC and IPv4) addresses for Fixed leases added
#6
Updated by Ruben S. Montero about 7 years ago
- Related to Feature #1945: Tag Virtual Network as IPv6 enabled. added
#7
Updated by Ruben S. Montero about 7 years ago
- Description updated (diff)
#8
Updated by Ruben S. Montero almost 7 years ago
- Target version changed from Release 4.8 to Release 4.8 - Beta 1
#9
Updated by Ruben S. Montero almost 7 years ago
- Category changed from Core & System to Documentation
#10
Updated by Ruben S. Montero almost 7 years ago
- Assignee set to Ruben S. Montero
#11
Updated by Valerio Schiavoni almost 7 years ago
Will this feature break existing VNET deployments (in particular those where the VNET has specified either FIXED or RANGED addresses) ?
#12
Updated by Javi Fontan almost 7 years ago
- Target version changed from Release 4.8 - Beta 1 to Release 4.8
#13
Updated by Ruben S. Montero almost 7 years ago
Valerio Schiavoni wrote:
Will this feature break existing VNET deployments (in particular those where the VNET has specified either FIXED or RANGED addresses) ?
The upgrade process automatically transforms the old VNETs to the new ones. There should not be (bugs apart) any problem
#14
Updated by Javi Fontan almost 7 years ago
Ruben S. Montero wrote:
Valerio Schiavoni wrote:
Will this feature break existing VNET deployments (in particular those where the VNET has specified either FIXED or RANGED addresses) ?
The upgrade process automatically transforms the old VNETs to the new ones. There should not be (bugs apart) any problem
Also, there is an emulation layer in Ruby OCA and CLI so old add/rmleases work the same way as with <= 4.6:
#15
Updated by Ruben S. Montero almost 7 years ago
- Status changed from New to Closed
- Resolution set to fixed