Hi Loic,
On 08.11.2013 00:19, Loic Dachary wrote:
On 08/11/2013 04:57, Kyle Bader wrote:
I think this is a great idea. One of the big questions users have is
"what kind of hardware should I buy." An easy way for users to publish
information about their setup (hardware, software versions, use-case,
performance) when they have successful deployments would be very valuable.
Maybe a section of wiki?
It would be interesting to a site where a Ceph admin can download an
API key/package that could be optionally installed and report
configuration information to a community API. The admin could then
supplement/correct that base information. Having much of the data
collection be automated lowers the barrier for contribution. Bonus
points if this could be extended to SMART and failed drives so we
could have a community generated report similar to Google's disk
population study they presented at FAST'07.
Would this be something like http://wiki.ceph.com/01Planning/02Blueprints/Firefly/Ceph-Brag ?
It seems that all eyes are looking in the same or very close directions
:-)
Sage initially said wiki page per reference setup - outlined overview of
the context, specifics (e.g. defaults overrides and their reasoning),
possibly essential notes on some regular maintenance activities, etc. In
summary: the minimal "readme" or "receipt" enough for an admin to adapt
and replicate a proven setup.
Publishing of few concrete deployments in this form doesn't need any
development and will generate positive effect immediately - "I'm doing
setup based on {wiki-page} with ... (differences), but ..."
You (Loic) are developing on the practical basis for scaling all of this
at large: Convenient ceph-brag tool and online service - collecting of
detailed snapshot of the setup as it is visible from a Ceph node.
Kyle combines the two, saying: application of the collecting tool
followed by handcrafted shaping, linking and annotations before/after
publishing.
Personally, I most like Kyle's workflow - iterations of: tool based
collection - results in new version in the "tool branch"; applying fixes
trough the web editor - merging handcrafted defs branch;
publishing/communication.
Once the working prototype goes live, various derivatives could be
considered, e.g.:
* Nice, possibly interactive diagrams (visual documentation) of the
setup.
* "Standard" reports with anchors for referencing in the mails.
* Side projects for "build" and "maintenance" artifacts generation for
various management platforms - ceph-deploy or different (of course
assuming rejoining-back the private bits)
* View/Report aiming extracting the essentials, roughly equivalent to
the handcrafted Ceph setup receipt for the context.
Regards,
Alek
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
