Open Stack

Dan,

I see your point about throughput and I/O, but if you have a multi-core 
server, greater than say 4 cores, and thus likely you would have 
multiple NICs, 2 or More, your assumptions fall apart about the cpu 
usage and I/o.  For example, using XEN or Qemu or in the older systems 
where this concept originated - VMS OS (from Digital Equipment Corp. - 
see Galaxy product and similar) you can assign affinity to CPUs or even 
dedicate CPU's to tasks or VM's.  In addition, using Cisco networking or 
similar you can dedicated I/O paths, and within a system, you can even 
dedicated a NIC Card or Port to a path.  So the deployment of OpenStack 
on one physical server or several should not even be a consideration 
except to the installer and their budget; and whether or not High 
Availability is a concern.  What I think is important is the consistency 
of the network design, I/O design for multiple VM's and the related load 
and intended usage of the individual cores of a server.  But the most 
important consistency is having installation guides that work over and 
over for installations on different hardware and OS's.

Myself, if I can get past my current nova and horizon issues, I will 
then be in a position to contribute in this and many other areas....

Regards,
Robert



On 11/8/12 4:06 PM, Skible OpenStack wrote:
> Thank you Dan for shedding light on this matter. However, there is 
> something concerns me and a lot of other people trying to deploy 
> OpenStack is that most Servers has 2 NICs which creates a problem 
> because your Demo is a great one but the necessary hardware is just 
> not always met !
>
> I have been struggling to find a solution out of it, can you suggest 
> some please ?
> Le 08/11/2012 21:38, Dan Wendlandt a écrit :
>> Hi,
>>
>> The Quantum Admin Guide indicates that you can choose to combine all 
>> services onto a single node, or have separate nodes: 
>> http://docs.openstack.org/trunk/openstack-network/admin/content/services.html
>>
>> I will update the text to indicate that that the main reason to use a 
>> dedicated network gateway node is if you plan on having VMs send 
>> substantial amounts of traffic through that node, and thus would not 
>> want that CPU usage to conflict with other openstack services running 
>> on your controller node.
>>
>> dan
>>
>> On Thu, Nov 8, 2012 at 11:06 AM, Skible OpenStack 
>> <skible.openstack at gmail.com <mailto:skible.openstack at gmail.com>> wrote:
>>
>>     Can someone please enlighten us about the goods of having a
>>     separated network node ?
>>     I honestly work in production envirnoments (over 30 nodes) and i
>>     really give computing resources more credit than networking ones !
>>
>>     Am i doing it the wrong way here ?
>>
>>     Le 08/11/2012 18:49, balaji patnala a écrit :
>>>     Hi Openers,
>>>     One doubt i have is like, as we see in the demo setup in the
>>>     Quantum Admin guide available in openstack.org
>>>     <http://openstack.org>, we have Network Node as a seperate
>>>     physical node connected to Controller Node and Compute Node.
>>>     But i see that the openstack community who is actively using
>>>     Folsom is not discussing more on this kind of setup.
>>>     Not sure if iam missing any key information on this like that
>>>     the Network Node setup may not be widely used in current
>>>     deployment scenarios or it is too early to use Network Node as a
>>>     seperate physical host for openstack.
>>>     Open comments on this will be more helpful for openstack
>>>     community to understand better on the features of folsom.
>>>     regards,
>>>     balaji
>>>
>>>
>>>     On Thu, Nov 8, 2012 at 7:09 PM, Skible OpenStack
>>>     <skible.openstack at gmail.com <mailto:skible.openstack at gmail.com>>
>>>     wrote:
>>>
>>>         OpenStack Folsom install guide
>>>         <https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst>
>>>
>>>
>>>         You will find what you want and even more ;)
>>>
>>>         Le 08/11/2012 14:30, Veera Reddy a écrit :
>>>>         Hi Skible,
>>>>
>>>>         Can you please send me below configuration files of three
>>>>         setups you have mentioned.
>>>>
>>>>           * ovs_quantum_plugin.ini (For controller and node)
>>>>           * nova.conf (For controller and node)
>>>>
>>>>         Thanks in advance
>>>>
>>>>
>>>>         Regards,
>>>>         Veera.
>>>>
>>>>         On Thu, Nov 8, 2012 at 2:57 PM, Skible OpenStack
>>>>         <skible.openstack at gmail.com
>>>>         <mailto:skible.openstack at gmail.com>> wrote:
>>>>
>>>>             Hello Stackers !
>>>>
>>>>             I am currently trying to create pictures of my
>>>>             OpenStack deployment architecture as a part of my
>>>>             OpenStack Folsom install guide
>>>>             <https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst>
>>>>             and i would like to ask a favorite.
>>>>
>>>>             Could you be kind and please take a look at these Pics
>>>>             below and report back if there is a missing or wrong thing.
>>>>
>>>>             Thank you.
>>>>
>>>>
>>>>             ==========Quantum  on VLAN + 3 NICs on controller
>>>>             node============
>>>>             http://i.imgur.com/Ueh5Z.jpg
>>>>             ===================================================
>>>>
>>>>             ==========Quantum  on VLAN + 2 NICs on controller
>>>>             node============
>>>>             http://i.imgur.com/RK6X7.jpg
>>>>             ===================================================
>>>>
>>>>             ==========Quantum  on GRE-tunneling + 3 NICs on
>>>>             controller node=======
>>>>             http://i.imgur.com/1jCFC.jpg
>>>>             ===================================================
>>>>
>>>>
>>>>             To make of OpenStack, the IT project of the century
>>>>
>>>>             Best regards
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>             _______________________________________________
>>>>             Mailing list: https://launchpad.net/~openstack
>>>>             <https://launchpad.net/%7Eopenstack>
>>>>             Post to     : openstack at lists.launchpad.net
>>>>             <mailto:openstack at lists.launchpad.net>
>>>>             Unsubscribe : https://launchpad.net/~openstack
>>>>             <https://launchpad.net/%7Eopenstack>
>>>>             More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>>
>>>>
>>>>         -- 
>>>>         Regards,
>>>>         VeeraReddy.B
>>>>         9959236555.
>>>
>>>
>>>         _______________________________________________
>>>         Mailing list: https://launchpad.net/~openstack
>>>         <https://launchpad.net/%7Eopenstack>
>>>         Post to     : openstack at lists.launchpad.net
>>>         <mailto:openstack at lists.launchpad.net>
>>>         Unsubscribe : https://launchpad.net/~openstack
>>>         <https://launchpad.net/%7Eopenstack>
>>>         More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>>     _______________________________________________
>>     Mailing list: https://launchpad.net/~openstack
>>     <https://launchpad.net/%7Eopenstack>
>>     Post to     : openstack at lists.launchpad.net
>>     <mailto:openstack at lists.launchpad.net>
>>     Unsubscribe : https://launchpad.net/~openstack
>>     <https://launchpad.net/%7Eopenstack>
>>     More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>>
>> -- 
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Dan Wendlandt
>> Nicira, Inc: www.nicira.com <http://www.nicira.com>
>> twitter: danwendlandt
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>
>
>
> _______________________________________________
> 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/20121108/975fcc62/attachment.html>