forked from uncloud/uncloud
++ network ideas
This commit is contained in:
parent
1a76150d4d
commit
583bbe34bc
1 changed files with 23 additions and 0 deletions
|
@ -112,9 +112,32 @@ Flow for using and creating networks:
|
|||
--> attention, ip -6 link ... id XXX expects DECIMAL input
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
If we also supply IPAM:
|
||||
|
||||
- ipam needs to be created *after* the network is created
|
||||
- ipam is likely to be coupled to netbox (?)
|
||||
--> we need a "get next /64 prefix" function
|
||||
- when an ipam service is created in etcd, we need to create a new
|
||||
radvd instance on all routers (this will be a different service on
|
||||
BSDs)
|
||||
- we will need to create a new vxlan device on the routers
|
||||
- we need to create a new / modify radvd.conf
|
||||
- only after all of the routers reloaded radvd the ipam service is
|
||||
available!
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
If the user requests an IPv4 VM:
|
||||
|
||||
- we need to get the next free IPv4 address (again, netbox?)
|
||||
- we need to create a mapping entry on the routers for NAT64
|
||||
--> this requires the VM to be in a network with IPAM
|
||||
--> we always assume that the VM embeds itself using EUI64
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
mac address handling!
|
||||
|
||||
Example
|
||||
|
||||
|
|
Loading…
Reference in a new issue