On 03/07, david jhon wrote:
> Thanks for the help.
>
> Openstack commands mean some administrative commands as listed here:
>
> https://docs.openstack.org/developer/python-openstackclient/command-objects/server.html
>
> I want to identify incoming openstack server commands on controller machine
> and manipulate their execution.
>

Hi,

Are you trying to track the execution from the client to the server and
then within services?

Usually you would use the `--debug` parameter on the client (this works
not only on the openstack common client but also on individual service
clients), then you'll see what REST API entries are being called on the
server.

From there you can go and check the server logs (better if services are
in debug mode) and see the code path these are following.

If you want to follow a particular tenant/project and user it will
depend on the configured logging format, but they usually include the
project_id or project_name and the user_id or user_name.

Also, on the server side most projects have an "api" directory where all
REST API entries first hit the code (well, sometimes it's not really the
first hit, but close enough), for example in cinder we'll have
cinder/api.

Cheers,
Gorka.

>
> On Mon, Jul 3, 2017 at 1:05 AM, Maciej Kucia <[email protected]> wrote:
>
> > What is "OpenStack command"? You mean Rest API, RPC? What services?
> >
> > Maybe the following will be of help.
> > http://vmartinezdelacruz.com/in-a-nutshell-how-openstack-works/
> >
> > Regards,
> > Maciej
> >
> > 2017-07-02 15:16 GMT+02:00 david jhon <[email protected]>:
> >
> >> Hello folks,
> >>
> >> I've been digging into openstack code for quite some time, I'm wondering
> >> how to identify some specific openstack commands possibly coming from
> >> hosted tenants or projects.
> >>
> >> Where should I look into the code if I want to suspend or block their
> >> execution. OR
> >> What is the starting point or any useful resource which can help me
> >> further.
> >>
> >> Any suggestion/link/help might be great.
> >>
> >> Thanks.
> >>
> >> ____________________________________________________________
> >> ______________
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: [email protected]?subject:unsubscrib
> >> e
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: [email protected]?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >

> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [email protected]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to