1. Query neutron data from DB
2. Discover to which computation node it belongs

you can query port's information with neutron command.
like "neutron port-list -c id -c device_owner" and find device_owner ==
compute:* ports.

and also find compute node witch port(and instance) deployed on.

you can find "instance id" and "vm host which instance deployed on"  and
 "network that port belongs to" and "vlan id from network(if you use vlan)"

3. In that node, access internal data and compare it with one that I read
from DB

I don't know how to get internal data of neutron agent directly. but you
can get peripheral information
from compute node.

like, access vm host with ssh(sshpass) and get flow information(ex:
ovs-ofctl dump-flows br-int) and ,
meta information  from ovs-db and iptables which security group and
security group rule's
instance.



2015-02-19 0:42 GMT+09:00 Leo Y <minh...@gmail.com>:

> Hello,
>
> I am looking for a way to match information about network topology (such
> as interface+port or routing) that is stored in neutron DB vs. actual
> information that is known by the neutron agent(s) in the computation node.
>
> I like to do it in one of the following ways:
>
> Way #1:
>
> 1. Query neutron data from DB
> 2. Discover to which computation node it belongs
> 3. In that node, access internal data and compare it with one that I read
> from DB
>
> Way #2:
> 1. For each computation node, access internal data
> 2. Find this data in DB and verify that it match
>
> I don't know how I can access "internal data of neutron agent(s)" in the
> computation node. I would appreciate any help and advise.
>
> I am not sure if it is possible, to read a neutron data from DB and
> discover to which computation node it belongs. Please, advise if it is
> possible.
> --
> Regards,
>         LeonidY
> ---------------------------------------------------------
> I enjoy the massacre of ads. This sentence will slaughter ads without a
> messy bloodbath
>
> __________________________________________________________________________
> 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

Reply via email to