Open Stack

Please don't take conversations off-list as others may benefit from your
questions and I don't have all the answers. Adding openstack as the list as
this is not an openstack-dev discussion about the future of OpenStack. More
below.


On Fri, Aug 22, 2014 at 4:31 AM, Sharath V <vsharathis at gmail.com> wrote:

> Hi Anne ,
>
> Thanks a lot for your help,
>
> I have small doubts mentioned below.
>
> 1. Why we need to separate controller,Compute and Network node .
>

For scalability, performance, availability and probably other reasons
related to keeping the cloud running day after day. The diagrams in the
install guide are examples to get you started. The first is using
nova-network the second offers an example with neutron.
http://docs.openstack.org/icehouse/install-guide/install/apt/content/ch_overview.html#example-architecture-with-neutron-networking


> 2) As per above diagram, why we need network interface for each
> controller, may i know the what is the use of it ?
>

I believe it's to connect the external network to the internal network
(between VMs). Also you may want to provide separate endpoints for admin
API actions hence the management interface. These descriptions are for when
you consider operating a cloud for many users. For a proof of concept you
don't have to worry about a management network interface, for instance.


>
> 3) When i reading document about controller node , their i found below
> mentioned statement
> "Optionally, the controller node also runs portions of Block Storage,
> Object Storage,
> Database Service, Orchestration, and Telemetry. These components provide
> additional
> features for your environment."
>
> may i know whats mean by *"Portion" *services ? then where complete
> services will run ?
>

Portions means "parts" or "pieces" here. For reliability, security,
availability and other reasons you run some daemons and services on
different nodes.

You would consider your users needs and determine which services they want.
You can find more examples of what architectures and designs are for
different clouds in the Architecture Design Guide. Here are prescriptive
examples:
http://docs.openstack.org/arch-design/content/prescriptive-example-online-classifieds.html

http://docs.openstack.org/arch-design/content/prescriptive-example-compute-focus.html

http://docs.openstack.org/arch-design/content/prescriptive-example-storage-focus.html

http://docs.openstack.org/arch-design/content/prescriptive-example-large-scale-web-app.html

http://docs.openstack.org/arch-design/content/prescriptive-example-multisite.html

http://docs.openstack.org/arch-design/content/prescriptive-examples-multi-cloud.html

http://docs.openstack.org/arch-design/content/massively_scalable.html

http://docs.openstack.org/arch-design/content/specialized.html

You should figure out what your goals are and then choose an architecture.
If it's a proof-of-concept and you have the hardware, the install guide
should meet the needs. If you need an all-in-one to try out, see RDO
(packstack), stackgeek, or devstack.


>
> if its a client and server how communication will happen between the
> services ?
>
>
Communication happens over RPC with remote procedure calls and other ways
such as reading/writing database information.


> may i know your IRC ?
>

We have established support channels in http://ask.openstack.org and the
OpenStack mailing list so you don't need to reach out to me directly.

Anne


>
> Thanks in advance.
>
> BR,
> Sharath
>
>
>
>
>
> On Fri, Aug 22, 2014 at 9:21 AM, Anne Gentle <anne at openstack.org> wrote:
>
>>
>>
>>
>> On Thu, Aug 21, 2014 at 2:11 AM, Sharath V <vsharathis at gmail.com> wrote:
>>
>>> Dear Friends,  Have an doubt, please clarify me .!!  When i start
>>> understanding openstack , There are three nodes a) controller node
>>> b)Compute node c) Network node
>>> i) as my understanding controller node contains all the components like
>>> nova,neutron cinder,glance,swift,Horizon etc
>>>
>>> ii) Compute node is nova and neutron but not all components.
>>>
>>> iii) Network node is nova and neutron.
>>>
>>>
>> This three node description is for the install guide, where our goal is
>> to get you to be able to launch an instance or store an object for example.
>> For running a real production cloud there are many more considerations. I'd
>> suggest reading the Operations Guide first, such as
>> http://docs.openstack.org/openstack-ops/content/cloud_controller_design.html
>> which says that the cloud controller is just a simplification.
>>
>>
>>> when i reading doc , they said like openstack compute (Controller
>>> Services) , openstack network services (Cloud controller) , can you please
>>> clarify is each and every component of openstack has controller and client?
>>> [like Nova Service(Controller) - Nova Client, Neutron Service (Controller)
>>> - neutron client, cinder controller - cinder client ] or (nova controller
>>> for compute , nova-network for cloud controller),
>>>
>>
>> There's a much more detailed description of each service in
>> http://docs.openstack.org/admin-guide-cloud/content/compute-service.html
>>
>>
>>
>>>  Is Nova only controller , if nova is only a controller it must be act
>>> as orchestration right? if yes then why we have to use heat for
>>> orchestration ?
>>>
>>
>> The nova project works on launching instances, scheduling which host it
>> launches to, providing the REST API service, allocating network and storage
>> resources to VMs. I have seen orchestration used for these collective
>> activities. When you want to orchestrate several cloud resources in order
>> to run an application such as WordPress on a virtual platform, then you
>> orchestrate the application with the heat project. Read more here:
>> http://docs.openstack.org/admin-guide-cloud/content/orchestration-service.html
>>
>> Hope this helps you dig deeper into the documentation.
>>
>> Anne
>>
>>
>>>
>>>
>>> If any thing wrong , please clarify me,
>>>
>>> if you have any document or guide please route to me.
>>>
>>> Thank you in advance,
>>>
>>> --
>>> Best Regards,
>>> Sharath
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best Regards,
> Sharath
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140824/82f9d711/attachment.html>