fuel-dev team mailing list archive

[David Easter <deaster@xxxxxxxxxxxx>]

Since the requirement is to develop this in its own project, perhaps we can
just use Rubick ­ both as a project and as a base to enhance.

https://wiki.openstack.org/wiki/Rubick

The mission of Rubick is "to provide OpenStack cloud operators with tools
which minimize time and effort needed to identify and fix errors in
operations maintenance phase of cloud life cycle."

Thanks,

-Dave Easter

From:  Roman Alekseenkov <ralekseenkov@xxxxxxxxxxxx>
Date:  Monday, March 24, 2014 at 8:00 PM
To:  "fuel-dev@xxxxxxxxxxxxxxxxxxx" <fuel-dev@xxxxxxxxxxxxxxxxxxx>, Sergey
Yudin <syudin@xxxxxxxxxxxx>, Pavel Zakatov <pzakatov@xxxxxxxxxxxx>
Subject:  [Fuel-dev] diagnostic snapshot v2.0 blueprint

Team,

I took some time to document my thoughts about required diagnostic tooling
here:
https://blueprints.launchpad.net/fuel/+spec/diagnostic-snapshot-v2.0
https://etherpad.openstack.org/p/openstack-diagnostics

I've seen other blueprints/documents/tools, but they are less fundamental. I
suggest to use mine as a "master" blueprint and fold the rest into it. Such
as:
* https://blueprints.launchpad.net/fuel/+spec/fuel-snapshot-additional-info
* 
* 
https://docs.google.com/a/mirantis.com/document/d/1KyVuJcKy6lln4rI1d2kEZS63N
U1ykswz0ib4MoM5bog/edit#
* 
* https://github.com/tsipa/troubleshooting
Thanks,
Roman
-- Mailing list: https://launchpad.net/~fuel-dev Post to     :
fuel-dev@xxxxxxxxxxxxxxxxxxx Unsubscribe : https://launchpad.net/~fuel-dev
More help   : https://help.launchpad.net/ListHelp