[openstack-dev] [fuel-dev][fuel-ostf] Extending networks diagnostic toolkit

Dmitriy Shulyak dshulyak at mirantis.com
Mon Apr 7 07:38:13 UTC 2014


Hi,

There is number of additional network verifications that can improve
troubleshooting experience or even cluster perfomance, like:

    1. multicast group verification for corosync messaging
    2. network connectivity with jumbo packets
    3. l3 connectivity verification
    4. some fencing verification
    5. allocated ip verification
https://bugs.launchpad.net/fuel/+bug/1275641
    6. measure network perfomance with iperf

Adding this stuff on fuel-web network tab will significantly worsen UX,
also it is not friendly enough to extend current model with additional
verifications.

Whole approach looks like networking health check for deployment, so in my
opinion it should be done as separate tab similar to ostf health check.

fuel-ostf already has necessery db and rest-api code to support such
extensions, and with some work this can be used as diagnostic tool not only
for fuel, but in tripleo as well.

In my opinion this feature should be splited in two main parts:

PART 1 - new plugin-executor for ostf, ui tab in fuel-web, extending this
plugin with existing verifications

    1. for now ostf has one plugin-executor - this plugin uses nose for
running tests, add new executor that will be named smth like distributed,
astute still will perform role of orchestartor

    2. adding new reporter to astute that will publish messages to ostf
queue

    3. add ostf amqp receiver

    4. extend current plugin with verifications listed above

    After this part of refactoring it should be possible to support rapid
extension of distributed cluster diagnostic.

PART 2 - make integration with fuel plugable, it means:

    1. remove proxy dependency from ostf, it can be done with socks
protocol that provides http proxy over ssh (it is supported by openssh
server)

    2. make integration with nailgun plugable

    3. replace astute/mcollective with custom agent or some community
solution


I will appreciate comments or suggestions, so dont hesitate to share your
thoughts
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140407/795d315c/attachment.html>


More information about the OpenStack-dev mailing list