Open Stack

Here's a simple workflow on how nova components are working together.

End user --> nova(Shell) --> python-nova-client --> nova-api service -->
nova-XXX services

all the nova-XXX services are started in the corresponding script files
located at
https://github.com/openstack/nova/tree/master/nova/cmd
along with the nova/nova-manage CLI interfaces.

The nova client source code is located at
https://github.com/openstack/python-novaclient

hope this will help.

btw, i also send my replies back to the mailing list.


On Wed, Oct 9, 2013 at 1:08 PM, Aparna Datt <aparna.cloud at gmail.com> wrote:

> hi....thanks for ur reply.  Actually i have already searched on google
> with various options.
> currently i am reading the code from github for nova. i can understand the
> code but the prob is that i am not able to gather that , when an end user
> enters nova what are the files that are executed first.
>
>
> On Wed, Oct 9, 2013 at 8:03 AM, Li Ma <skywalker.nick at gmail.com> wrote:
>
>> Right now, the guideline for developers is not that sufficient.
>> Nova has lots of components. I always learn it by debugging a certain
>> component
>> to see how it works.
>>
>> Here's several useful links:
>> https://github.com/openstack/nova/tree/master/doc
>> http://docs.openstack.org/developer/nova/
>>
>> You can also google "OpenStack Nova Architecture" or something else to
>> find your answers.
>>
>> Besides, here's a wonderful blog for introducing nova architecture:
>> http://ken.pepple.info/openstack/2011/04/22/openstack-nova-architecture/
>>
>> Cheers,
>>
>> --
>>
>> Li Ma (Nick)
>>
>> Architect of Stackinsider
>>
>> Email: skywalker.nick at gmail.com
>>
>
>


-- 

Li Ma (Nick)

Architect of Stackinsider

Email: skywalker.nick at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131009/ae4180f7/attachment.html>