Re: [openstack-dev] Tracing a request (NOVA)

[Akira Yoshiyama]

You may like below:
https://gist.github.com/yosshy/5da0c2d6af1b446088bc

Akira

> Hi,
>
> I'm trying to trace a request made for an instance and looking at the flow
> in the code.
> I'm just trying to understand better how the request goes from the
> dashboard to the nova-api , to the other internal components of nova and to
> the scheduler and back with a suitable host and launching of the instance.
>
> i just want to understand as to how the request goes from the api-call to
> the nova-api and so on after that.
> I have understood the nova-scheduler and in that, the filter_scheduler
> receives something called request_spec that is the specifications of the
> request that is made, and I want to see where this comes from. I was not
> very successful in reverse engineering this.
>
> I could use some help as I want to implement a scheduling algorithm of my
> own but for that I need to understand how and where the requests come in
> and how the flow works.
>
> If someone could guide me as to where i can find help or point in some
> direction then it would be of great help.
>
> --
> Dhvanan Shah
>


-- 
吉山あきら 
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Tracing a request (NOVA)

[Alexis Lee]

Vedsar Kushwaha said on Sat, Aug 29, 2015 at 09:30:05AM +0530:
> *i just want to understand as to how the request goes from the api-call to
> the nova-api and so on after that.*

For a code-level walkthrough:

http://docs-draft.openstack.org/67/210467/7/check/gate-nova-docs/51ee4c9//doc/build/html/trace.html

Unfortunately this code path is changing a lot at the moment but it's
only a few days out of date so far.


Alexis (lxsli)
-- 
Nova developer, Hewlett-Packard Limited.
Registered Office: Cain Road, Bracknell, Berkshire RG12 1HN.
Registered Number: 00690597 England
VAT number: GB 314 1496 79

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Tracing a request (NOVA)

[Vedsar Kushwaha]

*i just want to understand as to how the request goes from the api-call to
the nova-api and so on after that.*
To answer so on after that, in addition to josh answer, you can also look
into
http://ilearnstack.com/2013/04/26/request-flow-for-provisioning-instance-in-openstack/
.

Now to answer first part, i just want to understand as to how the request
goes from the api-call to the nova-api:
You can look into *http://developer.openstack.org/api-ref.html
http://developer.openstack.org/api-ref.html*, particularly in
*http://developer.openstack.org/api-ref-compute-v2.1.html
http://developer.openstack.org/api-ref-compute-v2.1.html*


On Sat, Aug 29, 2015 at 8:39 AM, Joshua Harlow harlo...@outlook.com wrote:

 I made the following some time ago,

 https://wiki.openstack.org/wiki/RunInstanceWorkflows

 https://wiki.openstack.org/w/images/a/a9/Curr-run-instance.png

 That may be useful for u, (it may also not be that up to date),

 Cheers,

 Josh

 Dhvanan Shah wrote:

 Hi,

 I'm trying to trace a request made for an instance and looking at the
 flow in the code.
 I'm just trying to understand better how the request goes from the
 dashboard to the nova-api , to the other internal components of nova and
 to the scheduler and back with a suitable host and launching of the
 instance.

 i just want to understand as to how the request goes from the api-call
 to the nova-api and so on after that.
 I have understood the nova-scheduler and in that, the filter_scheduler
 receives something called request_spec that is the specifications of the
 request that is made, and I want to see where this comes from. I was not
 very successful in reverse engineering this.

 I could use some help as I want to implement a scheduling algorithm of
 my own but for that I need to understand how and where the requests come
 in and how the flow works.

 If someone could guide me as to where i can find help or point in some
 direction then it would be of great help.
 --
 Dhvanan Shah

 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 
Vedsar Kushwaha
SDE@Amazon Development Center
Past - Indian Institute of Science
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Tracing a request (NOVA)

[Joshua Harlow]

I made the following some time ago,

https://wiki.openstack.org/wiki/RunInstanceWorkflows

https://wiki.openstack.org/w/images/a/a9/Curr-run-instance.png

That may be useful for u, (it may also not be that up to date),

Cheers,

Josh

Dhvanan Shah wrote:

Hi,

I'm trying to trace a request made for an instance and looking at the
flow in the code.
I'm just trying to understand better how the request goes from the
dashboard to the nova-api , to the other internal components of nova and
to the scheduler and back with a suitable host and launching of the
instance.

i just want to understand as to how the request goes from the api-call
to the nova-api and so on after that.
I have understood the nova-scheduler and in that, the filter_scheduler
receives something called request_spec that is the specifications of the
request that is made, and I want to see where this comes from. I was not
very successful in reverse engineering this.

I could use some help as I want to implement a scheduling algorithm of
my own but for that I need to understand how and where the requests come
in and how the flow works.

If someone could guide me as to where i can find help or point in some
direction then it would be of great help.
--
Dhvanan Shah

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Tracing a request (NOVA)

[Dhvanan Shah]

Hi,

I'm trying to trace a request made for an instance and looking at the flow
in the code.
I'm just trying to understand better how the request goes from the
dashboard to the nova-api , to the other internal components of nova and to
the scheduler and back with a suitable host and launching of the instance.

i just want to understand as to how the request goes from the api-call to
the nova-api and so on after that.
I have understood the nova-scheduler and in that, the filter_scheduler
receives something called request_spec that is the specifications of the
request that is made, and I want to see where this comes from. I was not
very successful in reverse engineering this.

I could use some help as I want to implement a scheduling algorithm of my
own but for that I need to understand how and where the requests come in
and how the flow works.

If someone could guide me as to where i can find help or point in some
direction then it would be of great help.

-- 
Dhvanan Shah
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev