Ressources Management: IP Address

[fufroma]

Hello,

An idea for a new feature... :)

Regards,

Backlog

• As a hoster, I'd like to be able to add a pool of IP to my admin panel so I know which IP I can use in my network.
• As a hoster, I'd like to be able to affect a pool of IP to some user of the self service so I can limit them.
• As a user of the self service, I'd like to know about IP address availability so I can assign them freely to my VMs.
• As a hoster, I'd like to be able to see which IP is linked to which MAC address so I can have an external security soft that checks the IP address is used by the right mac address.

Use case

• Use case 1:
  I have a Web Agency who use self service of XO.
  They made a VM for some of their website.
  One of their website requires a SSL certificate (and does not want SNI), so they want to add an IP address to the server. They do not want to have to call me to know which IP they can use.
• Use case 2:
  I have a junior sysadmin. And he is not a network administrator.
  I ask him to create a VM in XO. I want him to be able to select an IP address without annoying the team.

Nota

• It does not mean that xen orchestra configure the IP address in the VM. Leave some work to the human.
• Specific TAGS on the vif interface can be a solution.
• It may be a good idea to limit pool of IP address to specific network/bridges. If a VM's vif is on a private vlan, a public IP address is a bad ID. Nota: An IP pool is not unique, it can exist several times over several network interfaces (ie 192.168.0.0/24 used on vlan24 and vlan42)

[olivierlambert]

It seems VIFs don't have tag. Also we have some questions regarding the workflow.

@julien-f can you ask those questions?

[fufroma]

No tags on the VIFs ? Ho...
An ugly hack could be a serialized object in a tag on the vm, with the needed information.

I think this issue could be an answer for the missing piece (the UI) of the issue #240

[julien-f]

Also, in your use cases (especially the second one), the junior admin is about to create the VM therefore the VIFs do not exists yet, so it's not possible to store data in the VM or VIFs concerning the available IPs :/

[fufroma]

Yeah, you're right.

I found the "other_config" field on the VIF in the documentation, but I'm not sure we can store anything in it (I found this example of implementation)

[julien-f]

We can store anything in the other_config field of an object, but the object has to exist first :)

[fufroma]

it's not possible to store data in the VM or VIFs concerning the available IPs :/

The available IP can't be stored in the VM because it change everytime someone attach an IP to a new VM.
The list of the IP, and if they are available, should be cluster-wide.

The Junior Sysadmin, when he create a VM, he affect it a lot of informations:

• name
• description
• network interface with mac and network.

IMHO, when he can specify a mac and a network, he should be able to affect the IP address. But it's only an end-user view, not a developer one...
Maybe the information could be saved in a hook post-creation, or with an delayed event? It would allow the vif to exist before attemping to affect any value to it.