Opened 15 years ago
Closed 10 years ago
#5 closed enhancement (fixed)
Allow arbitrarily nested containers/allocations
Reported by: | Kris Deugau | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 3.0 |
Version: | Keywords: | ||
Cc: |
Description
Current allocation structure is a little too limiting, need to expand it to support deeper suballocation structures
Change History (40)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
comment:3 by , 12 years ago
comment:4 by , 12 years ago
comment:5 by , 12 years ago
comment:6 by , 12 years ago
comment:7 by , 12 years ago
comment:8 by , 12 years ago
comment:9 by , 12 years ago
comment:10 by , 12 years ago
comment:11 by , 12 years ago
comment:12 by , 12 years ago
comment:13 by , 12 years ago
comment:14 by , 12 years ago
comment:15 by , 12 years ago
comment:16 by , 12 years ago
comment:17 by , 12 years ago
comment:18 by , 12 years ago
comment:19 by , 12 years ago
comment:20 by , 12 years ago
comment:21 by , 12 years ago
comment:22 by , 12 years ago
(In [577]) /trunk
Work in progress, see #5:
Update templates and calling code for allocation delete to pass
and use rdepth
Start adding support for reparented netblocks; when a reparented
block is deleted, link back not only to the parent it was living
in, but the "true" parent the free space was merged with.
comment:23 by , 12 years ago
comment:24 by , 12 years ago
Milestone: | → 3.0 |
---|
comment:25 by , 10 years ago
/trunk
rdepth got too hairy and stupid. Redesigned allocation structure so that:
- All netblock allocations are in the allocations table
- Usage netblocks can be assigned directly under a master, instead of needing an extra "routed block" container
- Underlying data structure supports assigning the same IP/block in different VRFs. Not sure it really makes sense to actually allow this for publicly-routeable IPs and in any case the UI still won't gel.
- Data structure also allows for "reparenting" a block from deep in the tree up higher, or even across to a different branch (to represent real routing structures). "All" you need to do is change the parent ID.
comment:26 by , 10 years ago
comment:27 by , 10 years ago
comment:28 by , 10 years ago
comment:29 by , 10 years ago
comment:30 by , 10 years ago
comment:31 by , 10 years ago
comment:32 by , 10 years ago
comment:33 by , 10 years ago
comment:34 by , 10 years ago
comment:35 by , 10 years ago
comment:36 by , 10 years ago
comment:37 by , 10 years ago
comment:38 by , 10 years ago
comment:39 by , 10 years ago
comment:40 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Closing this ticket. The new data structure is working, and allows for flexibility not yet in the UI.
(In [554]) /trunk