CEPH filesystem development
 help / color / mirror / Atom feed
From: Owen Synge <osynge@suse.com>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: python-ceph-cfg a ceph deployment library
Date: Mon, 30 May 2016 17:31:33 +0200	[thread overview]
Message-ID: <574C5CD5.7060801@suse.com> (raw)

Dear all,

I have created a stand alone local library for deploying ceph.

	https://github.com/oms4suse/python-ceph-cfg

Already it provides much of the functionality of ceph-deploy.

Front ends:

This library already has a salt front end as an execution module:

	https://github.com/oms4suse/sesceph

I intend to provide a CLI front end for this library if people are
interested, this would provide an alternative to ceph-deploy for zero
infrastructure installs.

Currently it handles keyrings, mon osd, rgw and mds entities, and runs
on SUSE SLE12, and OpenSUSE LEAP as well as Centos/Scientific Linux 7.

Potential CLI front end:

If I develop the CLI front end I am considering that it would differ
from ceph deploy in 4 main ways:

(0) Target reuse as a non interactive installer.

(1) It would configure ceph based on a configuration rather than command
line arguments.

(2) Configure the cluster in one operation.

(3) be run on each node, rather than doing remote operations, outside
the remote operations that are provided by ceph CLI tools.

But lets not get ahead of ourselves talking about a CLI front end to
python-ceph-cfg.

Current status of my work:

This library is a spin off from my work on salt. I am working on a long
term project to make a ceph deployment and management framework for
salt, where we hope to manage day to day operations as well as just
deployment. Currently we have only have salt based deployment of ceph
using this library, but this simple file will allow a complete cluster
to be deployed:

	https://github.com/oms4suse/sesceph/blob/master/examples/cluster_buildup.sls

My bosses are keen for me to upstream my work to the ceph project rather
than the salt project, and so for a first stage I am hoping to put this
library into the ceph project.

What are the stages to achieve moving this repo into the ceph project?

Best regards

Owen

-- 
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG
Nürnberg)

Maxfeldstraße 5

90409 Nürnberg

Germany
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

                 reply	other threads:[~2016-05-30 15:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=574C5CD5.7060801@suse.com \
    --to=osynge@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox