[Deepsea-users] osd and journal profile inquiries

Jose Betancourt jose.betancourt at suse.com
Tue Jan 24 13:35:57 MST 2017

Hi Eric,

As a point of education for everyone;

1. Does the listing order matters? - Meaning, should I have a data, journal, data, journal pattern?
2. And assuming one journal for multiple OSDs, should I just use the same data, journal pattern?



-----Original Message-----
From: deepsea-users-bounces at lists.suse.com [mailto:deepsea-users-bounces at lists.suse.com] On Behalf Of Eric Jackson
Sent: Tuesday, January 24, 2017 3:22 PM
To: Discussions about the DeepSea management framework for Ceph <deepsea-users at lists.suse.com>
Subject: Re: [Deepsea-users] osd and journal profile inquiries

Hi José,
  The file would look like this:

  - /dev/disk/by-id/ata-ST1000LM014-1EJ164_W771X1G9: 
  osds: []

  For some notes: I didn't plan on usb journals so I skip removable media.  
(Nothing like have a usb stick or drive attached to server which is suddenly discovered and added to your Ceph cluster.)  In your scenario, this is a little painful to go and edit all six files.

  Another note: We do have a card on the list
https://github.com/SUSE/DeepSea/projects/2 to allow custom profiles which could be run after Stage 1.  The original idea here was to allow custom hardware profiles that are not recommended (e.g. 10:1 ratio for instance for a single SSD journal).  I may have to have an option for removable media. :)

  Last note: there is nothing special about the hardware profile name.  The name is simply chosen in hopes that you, the administrator, can identify which hardware is which.  Stage 1 will not overwrite the sls and yml files under proposals.  However, you can still create your own profile rather than edit the existing one.  Either 'rsync -a' or 'cp -rp' from any of the profile directories to a name of your own choosing.  Edit as you wish.  Include your directory in your policy.cfg.

  Hope that helps.


On Tuesday, January 24, 2017 07:43:27 PM Jose Betancourt wrote:
> Hello Everyone,
> Working on my own mini-lab performing an SES installation with DeepSea 
> and Salt per 
> https://www.suse.com/documentation/ses-4/book_storage_admin/data/ceph_
> insta
> ll_stack.html
> I have six identical Intel NUCs.  From a storage configuration:
> ·        M.2 250GB for the OS
> ·        1TB HDD to be used as SSD
> ·        64GB USB stick to be used as "journal"
> I successfully used that configuration in the past using ceph-deploy.
> I completed ceph.stage.0 and ceph.stage.1 successfully.
> When stage 1 completes, I have the osd proposal (for lack of a better 
> word) under 
> /srv/pillar/ceph/proposals/profile-*/stack/default/ceph/minions as a yml file.
> Using one of the nodes as an example [physical machine is called: 
> phynode22]
> storage:
>   data+journals: []
>  osds:
>   - /dev/disk/by-id/ata-ST1000LM014-1EJ164_W771X1G9
> The OSD entry accurately selected the 1TB drive by-id.
> The question is:  How do I add a different disk for the journal?  In 
> my particular case, I would like to add
> /dev/disk/by-id/usb-SanDisk_Ultra_Fit_4C530001060612116591-0:0
> What is the correct syntax?  And is there something that I can do 
> prior to executing ceph.stage.0 and ceph.stage.1 to properly identify 
> the different drives?
> Best,
> José Betancourt
> Linux Architecture - IHV Alliances & Embedded Systems 
> jose.betancourt at suse.com<mailto:jose.betancourt at suse.com>
> +1.908.672.2719

More information about the Deepsea-users mailing list