<html><head></head><body><div class="gmail_quote">On May 25, 2017 12:48:50 PM GMT+02:00, Tim Serong <tserong@suse.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi All,<br /><br />We want DeepSea to be able to "import" existing ceph clusters, for<br />example if you've used ceph-deploy in the past, and want to migrate to<br />DeepSea. I've implemented what you might call a rough outline of this<br />functionality at <a href="https://github.com/SUSE/DeepSea/commit/7a60715">https://github.com/SUSE/DeepSea/commit/7a60715</a> (i.e.<br />the implementation is incomplete), and would appreciate feedback on the<br />approach in general.<br /><br />There's more detail in the commit, but essentially you use it like so:<br /><br />1) Install salt on every ceph node.<br />2) Run the first two DeepSea stages, plus my extra importer bit.<br />3) The importer checks what ceph services are running on all the minions<br />(mon, mds, osd, rgw), and generates a policy.cfg reflecting the<br />currently running cluser.<br />4) Now you can keep using DeepSea as usual.<br /><br />WARNING: Do *NOT* try step 4 with the current code. You WILL BREAK YOUR<br />CLUSTER. I'm just trying to get feedback on whether there's any large<br />holes in the general shape of this thing (I had an earlier experiment<br />where I was interrogating ceph.conf to find the MONs, then realised I'd<br />end up having to talk to the cluster to ask it where the OSDs were, so I<br />decided that checking for running services was going to be simpler).<br /><br />Thanks,<br /><br />Tim</pre></blockquote></div><br clear="all">Oh, this looks very promising. Eric was quite worried that we wouldn't have enough time and too many other priorities to get to this. Thanks for looking into it, Tim.<br>
<br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>