OpenStack Compute (nova)

Several questions about Nova

Asked by Laurent Borensky

Hello,

I have several general questions to better understand Nova :

1) Does OpenStack manage configuration inside created VMs to customize hostname and IPs ? If yes, for which VMs kinds ?

2) Does OpenStack manage VMs snapshots /rollbacks ? If yes, for which hypervisors is it supported ?

3) What is the principle for the publication of VMs on internet ? Do all VMs have public addresses ? When is a public address allocated by OpenStack ? Is there a hook that can enable to call 3rd party external component in charge of configuring NAT or FireWall equipments ?

4) Can you clarify fixed Ips vs Floating IPs management ? Must VMs be configured in DHCP ?

5) Is OpenStack already able to configure two VMware hypervisors so that VMs can communicate inter-hypervisors ? If not, is it in the roadmap ?

Regards,

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
Laurent Borensky
Solved:
Last query:
Last reply:
Revision history for this message
Armando Migliaccio (armando-migliaccio) said : 		#1

Hi,

AFAIK, snapshotting is supported by XenServer/XCP via the OpenStack API so far.

On a more general note, I think it may be useful to break this question down into several ones.

Cheers,
Armando

Revision history for this message
Laurent Borensky (laurent-borensky) said : 		#2

Hi Armando,

To be more explicit, I'll create a ticket for each question. But why always Xen, XenServer or XCP and not KVM for the choice of hypervisor ? Moreover, is it easy to use OpenVZ or LXC OS virtualization ?

Regards

Revision history for this message
Ewan Mellor (ewanmellor) said : 		#3

XenServer is superior to all other hypervisors in all possible ways. You should always choose XenServer.

Cheers,

Ewan Mellor,
XenServer Engineering, Citrix.

Revision history for this message
Armando Migliaccio (armando-migliaccio) said : 		#4

Hi Laurent, thanks!

The only reason why I proposed to break this question down is that a shorter one is likely to be answered quicker :)

Moreover, all your points might not be addressed by the same contributor, and by keeping all the comments in one thread makes it harder to read within the lines.

Hope this help!
Cheers,
Armando

Revision history for this message
Laurent Borensky (laurent-borensky) said : 		#5

Thanks