Is your statement based on the setup noted in the "OpenStack Install and Deploy Manual"? I am question was more specific to the setup covered in the afore mentioned document.
In general, does the answer not depend on what services are installed on the controller node, to give it "ability" to be a compute node also? Regards, Ahmed. From: Pengjun Pan <panpeng...@gmail.com<mailto:panpeng...@gmail.com>> Date: Thursday, November 15, 2012 11:58 AM To: Ahmed Al-Mehdi <ah...@coraid.com<mailto:ah...@coraid.com>> Cc: "openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>" <openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>> Subject: Re: [Openstack] Controller node vs. compute node terminology The controller node can not host vms. But an All-in-one node can, because it is a combination of controller and compute. On Thu, Nov 15, 2012 at 12:53 PM, Ahmed Al-Mehdi <ah...@coraid.com<mailto:ah...@coraid.com>> wrote: Hello, I am following the document "OpenStack Deploy and Install Guide" to bring up a OpenStack setup. Per the instructions in the document, is the controller node also acting as the compute node. By that I mean when a VM is created, it created on the controller node. Is that right? And then there are steps to create additional (sole) compute nodes. Is that a correct view of looking at the setup described in the document. Server 1 : Controller node / Compute node Server 2: Compute node If so, is that the usual deployment scenario? Any thoughts would be highly appreciated. Regards, Ahmed. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net> Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
