On 23/07/14 4:32 AM, "Silvano Nogueira Buback" <silv...@corp.globo.com> wrote:
>@All > When I acquire new IP in shared network the same IP of vms are given >To the users. When you create a shared network, a range of IP address need to be given. IP addresses are allocated from this range for the VM's in the shared network. Are you saying that even acquire new IP is allocating an IP from the IP range given for shared network? If so it seems like a bug. > I would like to change "Acquired New Ip" mechanism to ask the >network guru to decide which ip must be given to the users. Network guru >is >the only one that need to understand how network is implemented, so it >must >decide which IP must be associate. So, my idea is to create a new method >in >Network Guru named allocate, but with only with Network as argument. For >the Network Guru existing, the rule is the same, but any new guru subclass >(like mine) can change the behavior if it want. Basically, the command >associateIpAddress only need to verify permission, ask >networkguru.allocate >and mark the IP as allocated in database. What do you think? If everyone >agrees I can create the design document and start this development. Works >for my guru, and I guess keeps clean the code to allocate IP address. Network guru's already does IPAM (ip address management of what IP a VM should get from the network CIDR) for both isolated & shared networks. But allocating a public IP from the zone public IP pool does not seem to fit into the function of network guru's IMO. Perhaps if you can share the fix you have done that should give idea how network guru allocating public IP fit into the network subsystem. > >[]'s, > >Silvano Buback >
