Open Stack

I was about to reply, but Anne covered it up perfectly :) (as usual)

Nuage & Co - Razique Mahroua 
razique.mahroua at gmail.com



Le 15 nov. 2012 à 20:49, Anne Gentle <anne at openstack.org> a écrit :

> On Thu, Nov 15, 2012 at 1:40 PM, Ahmed Al-Mehdi <ahmed at coraid.com> wrote:
>> 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.
> 
> Specific to that guide, the controller node also contains
> nova-compute. Any node with that service (nova-compute) can act as a
> Compute node and launch VMs.
> 
> This all-services-on-one-node setup on the controller node is not a
> typical deployment for large-scale clouds (public or private).
> 
>> 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?
> 
> The services installed do define its abilities, yes. Often a
> "Controller node" contains items like databases (such as MySQL),
> messaging queues (such as Rabbit-MQ), identity, images, all
> nova-services minus nova-compute, volumes, and the dashboard. Often a
> "Compute node" offers the hypervisor, nova-compute, the API metadata
> service (nova-api-metadata) and possibly the networking services,
> either nova-network or Quantum.
> 
> You could also review the "Basic install guide" at
> https://review.openstack.org/#/c/16096/ which outlines it quite
> prescriptively.
> 
> In your environment you may have reasons for splitting out services
> differently, how that division is done depends on your use case. The
> "Controller" and "Compute" nodes are an easy nomenclature and pattern
> for many cases.
> 
> Hope this helps,
> Anne
> 
>> Regards,
>> Ahmed.
>> 
>> 
>> From: Pengjun Pan <panpengjun at gmail.com>
>> Date: Thursday, November 15, 2012 11:58 AM
>> To: Ahmed Al-Mehdi <ahmed at coraid.com>
>> Cc: "openstack at lists.launchpad.net" <openstack at 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 <ahmed at 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 at lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>> 
>> 
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121115/a394171a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NUAGECO-LOGO-Fblan_petit.jpg
Type: image/jpeg
Size: 10122 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121115/a394171a/attachment.jpg>