Feature #602
Improve Ranged/Fixed Network definition
| Status: | Closed | Start date: | 04/29/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 3.2 - Beta1 | |||
| Resolution: | fixed | Pull request: |
Description
This came up from a thread in a user mailing list. The proposal from Lars Kellogg-Stedman will address the following use-case:
I think that RANGED networks are ultimately easier to manage than a
FIXED network. I would like, for example, to create several small
"networks" out of a larger block of addresses...for example, taking
10.10.10.0/24 and dividing it up into:- 10.10.10.10 - 10.10.10.30
- 10.10.10.31 - 10.10.10.100
- etc...
...
This would require the ability to specify a base address for each
"network", as well as the the number of addresses to provision. So
something like this:NAME=cloud
TYPE=RANGED
BRIDIGE=br619
NETWORK_BASE=10.10.10.10
NETWORK_SIZE=30
Defining a network with its base address an netmask is equivalent to the current address and size attributes.
Alternatively, we could define such a network using FIXED and extending it with ranged leases:
NAME=cloud TYPE=FIXED BRIDIGE=br619 LEASES=[IP_START=10.10.10.10, IP_END=10.10.10.40]
The benefit of this approach is to define a network consisting in non-continuous sets of ranged of IP's.
This issue will be used to decide upon this issue and implement it.
Related issues
Associated revisions
Feature #602: Refactor Ranged VNets to store first and last IP of the range
Feature #602: Make Network size definition more flexible. The netmask is generated from the given size
The Network size can be defined as: * NETWORK_ADDRESS attribute: 19.2168.30.0/24 * SIZE: Letter (a,b,c) or number of hosts * NETWORK_MASK: 255.255.255.0 creates a network of 254 hosts
Feature #602: Show RANGE/IP_START and RANGE/IP_END in 'onevnet show'
Feature #602: Refactorin of the Range creation code. New method RangedLeases::process_template
Feature #602: Add support for IP_START and IP_END redefinition in Ranged networks
Feature #602: Add error checks in Ranged network creation
Feature #602: Small bugfixes
Feature #602: Fix tests
Feature #602: Add tests for range definition
Feature #602: onevnet release returns error if a Lease is not used, this achieves the same behaviour for fixed and ranged networks
Feature #602: Add VNet hold and release methods in Java OCA
Feature #602: Change onevnet show format to separate used, free and 'on hold' leases
feature #602: Moved size to get the default if needed
Task #864, Feature #602: Improve leases support in Sunstone and new vnet operations in Sunstone
This commit includes:
- Support for ip_start, ip_end parameters when creating ranged vnetworks.
- Removal of the add lease/remove lease dialogs.
- Renewal of the representation of leases pool in the "extended information" windows. The list of leases is represented so that it is clearly visible those leases which are free, on hold (reserved), or used by a VM. Right on the list, leases can be added, updated or deleted.
Task #864, Feature #602: Improve leases support in Sunstone and new vnet operations in Sunstone
This commit includes:
- Support for ip_start, ip_end parameters when creating ranged vnetworks.
- Removal of the add lease/remove lease dialogs.
- Renewal of the representation of leases pool in the "extended information" windows. The list of leases is represented so that it is clearly visible those leases which are free, on hold (reserved), or used by a VM. Right on the list, leases can be added, updated or deleted.
(cherry picked from commit eccae0e73126d5571cd138a782d5ba0e58aa0e22)
feature #602: Include bullets to install file
History
#1
Updated by Ruben S. Montero almost 10 years ago
- Target version set to Release 3.4
#2
Updated by Ruben S. Montero almost 10 years ago
- Category set to Core & System
#3
Updated by Ruben S. Montero over 9 years ago
- Target version changed from Release 3.4 to Release 3.2 - S1
#4
Updated by Ruben S. Montero over 9 years ago
- Target version changed from Release 3.2 - S1 to Release 3.2 - Beta1
#5
Updated by Ruben S. Montero over 9 years ago
- translation missing: en.field_story_points set to 0
#6
Updated by Ruben S. Montero over 9 years ago
- Status changed from New to Closed
- Assignee set to Carlos Martín
- Resolution set to fixed