Open Stack

But does the controller speak the same to any compute node, regardless of the underlying hypervisor, or is there something special for KVM vs Xen, for example?  What I'm trying to do is not configure qemu if I don't need to.

From: Remo Mattei [mailto:Remo at italy1.com]
Sent: Friday, June 13, 2014 9:15 AM
To: O'Reilly, Dan
Cc: openstack at lists.openstack.org
Subject: Re: [Openstack] Compute servers configuration - best practices

Nope the controller does not care where it runs. AZ allows you to select the dest and its' pretty nice since you can have a sever with SSD or VMware etc...


On Jun 13, 2014, at 8:12, O'Reilly, Dan <Daniel.OReilly at dish.com<mailto:Daniel.OReilly at dish.com>> wrote:


Right.  So, to do that, do I have to use something like qemu, or does the controller care?  Which is another way of asking, does the controller need to know that 1 node is Xen, one is KVM and one is VMware?  And if so, how is that configured?

From: Remo Mattei [mailto:Remo at italy1.com]
Sent: Friday, June 13, 2014 9:11 AM
To: O'Reilly, Dan
Cc: openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Subject: Re: [Openstack] Compute servers configuration - best practices

No,
you need to configure your nova.conf file on each node so then you are set.


On Jun 13, 2014, at 8:10, O'Reilly, Dan <Daniel.OReilly at dish.com<mailto:Daniel.OReilly at dish.com>> wrote:



Ah, yes.  But does that still affect how Openstack (specifically, the controller and compute nodes) must be configured to use Xen/KVM/VMware?

Thanks!

From: Remo Mattei [mailto:Remo at italy1.com]
Sent: Friday, June 13, 2014 9:08 AM
To: O'Reilly, Dan
Cc: openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Subject: Re: [Openstack] Compute servers configuration - best practices

Availability Zone.


On Jun 13, 2014, at 8:03, O'Reilly, Dan <Daniel.OReilly at dish.com<mailto:Daniel.OReilly at dish.com>> wrote:




AZ?

From: Remo Mattei [mailto:Remo at italy1.com]
Sent: Friday, June 13, 2014 9:00 AM
To: O'Reilly, Dan
Cc: openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Subject: Re: [Openstack] Compute servers configuration - best practices

Why don't you use AZ for this. So you can select where you want to run a specific VM. Then you have VM on KVM, XEN etc.. based on the AZ.

Remo

On Jun 13, 2014, at 7:41, O'Reilly, Dan <Daniel.OReilly at dish.com<mailto:Daniel.OReilly at dish.com>> wrote:





I realize there have been some discussions on this in the recent past, but it has become somewhat difficult to follow.  So, I would like to take a fresh approach with  a fresh question.

I have the following configuration:

-          Controller with identity, dashboard, orchestration, image, telemetry
-          Network box with neutron
-          3 compute nodes (1 with LVM, 1 with Xen, 1 with VMware)
-          1 volume node with cinder block storage (this will soon become 1 proxy server and 5 storage servers for swift object store)

As you can see, I would like to have 3 common flavors of hypervisors so I can pick best of breed.  From what I've read, qemu is the best (only) approach for this.  At this point, I have all the necessary packages installed and working on everything but the compute nodes.  What I need to do is to build an KVM node and a Xen node first, then worry about VMware later.

So, I need a definitive build cookbook for bringing up LVM and Xen nodes using qemu.  Right now when I try to launch instances they just get funky errors and die.  Can I pick any/all the brains of you out n OpenStack land?

Thanks!

Dan O'Reilly
UNIX Systems Administration
<image001.jpg>
9601 S. Meridian Blvd.
Englewood, CO 80112
720-514-6293


_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack






!DSPAM:1,539b146137022110585333!

!DSPAM:1,539b14f539603055582541!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140613/bd401190/attachment.html>