From jschmid at suse.de  Thu Feb  2 07:24:13 2017
From: jschmid at suse.de (Joshua Schmid)
Date: Thu, 2 Feb 2017 15:24:13 +0100
Subject: [Deepsea-users] Installing SES4 with Salt
In-Reply-To: <19AADEB379BD6F42B71731B0D5A6602C52A18F@NWBXMB01.microfocus.com>
References: <19AADEB379BD6F42B71731B0D5A6602C52A18F@NWBXMB01.microfocus.com>
Message-ID: <c122af95-67e5-0b30-263f-e7293a0a60c2@suse.de>

Hey Thomas,

On 02/02/2017 03:18 PM, Thomas Graetz wrote:
> Hi,
> 
> I try to install SES4 with Salt but when I run "salt-run state.orch ceph.stage.3" the following error message shows up:
> 
> Any ideas?

looks very much like this: github.com/SUSE/DeepSea/issues/50

fix for this is here: https://github.com/SUSE/DeepSea/pull/51

what's your salt version?

> 
> 
> [ERROR   ] Rendering exception occurred: Jinja error: runner() got multiple values for keyword argument 'name'
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>     output = template.render(**decoded_context)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>     return self.environment.handle_exception(exc_info, True)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>     reraise(exc_type, exc_value, tb)
>   File "<template>", line 4, in top-level template code
> TypeError: runner() got multiple values for keyword argument 'name'
> 
> ; line 4
> 
> ---
> 
> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 'True') %}
> 
> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
> ready check failed:
>   salt.state:
>     - name: "Fail on Warning is True"
>     - tgt: {{ salt['pillar.get']('master_minion') }}
>     - failhard: True
> [...]
> ---
> [CRITICAL] Rendering SLS 'base:ceph.stage.3.default' failed: Jinja error: runner() got multiple values for keyword argument 'name'
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>     output = template.render(**decoded_context)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>     return self.environment.handle_exception(exc_info, True)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>     reraise(exc_type, exc_value, tb)
>   File "<template>", line 4, in top-level template code
> TypeError: runner() got multiple values for keyword argument 'name'
> 
> ; line 4
> 
> ---
> 
> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 'True') %}
> 
> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
> ready check failed:
>   salt.state:
>     - name: "Fail on Warning is True"
>     - tgt: {{ salt['pillar.get']('master_minion') }}
>     - failhard: True
> [...]
> ---
> salt.site.tld_master:
>     Data failed to compile:
> ----------
>     Rendering SLS 'base:ceph.stage.3.default' failed: Jinja error: runner() got multiple values for keyword argument 'name'
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>     output = template.render(**decoded_context)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>     return self.environment.handle_exception(exc_info, True)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>     reraise(exc_type, exc_value, tb)
>   File "<template>", line 4, in top-level template code
> TypeError: runner() got multiple values for keyword argument 'name'
> 
> ; line 4
> 
> ---
> 
> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 'True') %}
> 
> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
> ready check failed:
>   salt.state:
>     - name: "Fail on Warning is True"
>     - tgt: {{ salt['pillar.get']('master_minion') }}
>     - failhard: True
> [...]
> ---
> 
> 
> 
> _______________________________________________
> Deepsea-users mailing list
> Deepsea-users at lists.suse.com
> http://lists.suse.com/mailman/listinfo/deepsea-users
> 

-- 
Freundliche Gr??e - Kind regards,
Joshua Schmid
SUSE Enterprise Storage
SUSE Linux GmbH - Maxfeldstr. 5 - 90409 N?rnberg
--------------------------------------------------------------------------------------------------------------------
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard,
Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg)
--------------------------------------------------------------------------------------------------------------------

From thomas.graetz at suse.com  Thu Feb  2 07:53:50 2017
From: thomas.graetz at suse.com (Thomas Graetz)
Date: Thu, 2 Feb 2017 14:53:50 +0000
Subject: [Deepsea-users] Installing SES4 with Salt
In-Reply-To: <c122af95-67e5-0b30-263f-e7293a0a60c2@suse.de>
References: <19AADEB379BD6F42B71731B0D5A6602C52A18F@NWBXMB01.microfocus.com>
	<c122af95-67e5-0b30-263f-e7293a0a60c2@suse.de>
Message-ID: <19AADEB379BD6F42B71731B0D5A6602C52A26B@NWBXMB01.microfocus.com>

Hi,

the version we are using is 2015.8.12

-----Urspr?ngliche Nachricht-----
Von: deepsea-users-bounces at lists.suse.com [mailto:deepsea-users-bounces at lists.suse.com] Im Auftrag von Joshua Schmid
Gesendet: Donnerstag, 2. Februar 2017 15:24
An: deepsea-users at lists.suse.com
Betreff: Re: [Deepsea-users] Installing SES4 with Salt

Hey Thomas,

On 02/02/2017 03:18 PM, Thomas Graetz wrote:
> Hi,
> 
> I try to install SES4 with Salt but when I run "salt-run state.orch ceph.stage.3" the following error message shows up:
> 
> Any ideas?

looks very much like this: github.com/SUSE/DeepSea/issues/50

fix for this is here: https://github.com/SUSE/DeepSea/pull/51

what's your salt version?

> 
> 
> [ERROR   ] Rendering exception occurred: Jinja error: runner() got multiple values for keyword argument 'name'
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>     output = template.render(**decoded_context)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>     return self.environment.handle_exception(exc_info, True)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>     reraise(exc_type, exc_value, tb)
>   File "<template>", line 4, in top-level template code
> TypeError: runner() got multiple values for keyword argument 'name'
> 
> ; line 4
> 
> ---
> 
> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 'True') 
> %}
> 
> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
> ready check failed:
>   salt.state:
>     - name: "Fail on Warning is True"
>     - tgt: {{ salt['pillar.get']('master_minion') }}
>     - failhard: True
> [...]
> ---
> [CRITICAL] Rendering SLS 'base:ceph.stage.3.default' failed: Jinja error: runner() got multiple values for keyword argument 'name'
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>     output = template.render(**decoded_context)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>     return self.environment.handle_exception(exc_info, True)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>     reraise(exc_type, exc_value, tb)
>   File "<template>", line 4, in top-level template code
> TypeError: runner() got multiple values for keyword argument 'name'
> 
> ; line 4
> 
> ---
> 
> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 'True') 
> %}
> 
> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
> ready check failed:
>   salt.state:
>     - name: "Fail on Warning is True"
>     - tgt: {{ salt['pillar.get']('master_minion') }}
>     - failhard: True
> [...]
> ---
> salt.site.tld_master:
>     Data failed to compile:
> ----------
>     Rendering SLS 'base:ceph.stage.3.default' failed: Jinja error: runner() got multiple values for keyword argument 'name'
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>     output = template.render(**decoded_context)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>     return self.environment.handle_exception(exc_info, True)
>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>     reraise(exc_type, exc_value, tb)
>   File "<template>", line 4, in top-level template code
> TypeError: runner() got multiple values for keyword argument 'name'
> 
> ; line 4
> 
> ---
> 
> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 'True') 
> %}
> 
> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
> ready check failed:
>   salt.state:
>     - name: "Fail on Warning is True"
>     - tgt: {{ salt['pillar.get']('master_minion') }}
>     - failhard: True
> [...]
> ---
> 
> 
> 
> _______________________________________________
> Deepsea-users mailing list
> Deepsea-users at lists.suse.com
> http://lists.suse.com/mailman/listinfo/deepsea-users
> 

--
Freundliche Gr??e - Kind regards,
Joshua Schmid
SUSE Enterprise Storage
SUSE Linux GmbH - Maxfeldstr. 5 - 90409 N?rnberg
--------------------------------------------------------------------------------------------------------------------
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg)
--------------------------------------------------------------------------------------------------------------------
_______________________________________________
Deepsea-users mailing list
Deepsea-users at lists.suse.com
http://lists.suse.com/mailman/listinfo/deepsea-users

From jfajerski at suse.com  Thu Feb  2 08:02:23 2017
From: jfajerski at suse.com (Jan Fajerski)
Date: Thu, 2 Feb 2017 16:02:23 +0100
Subject: [Deepsea-users] Installing SES4 with Salt
In-Reply-To: <19AADEB379BD6F42B71731B0D5A6602C52A26B@NWBXMB01.microfocus.com>
References: <19AADEB379BD6F42B71731B0D5A6602C52A18F@NWBXMB01.microfocus.com>
	<c122af95-67e5-0b30-263f-e7293a0a60c2@suse.de>
	<19AADEB379BD6F42B71731B0D5A6602C52A26B@NWBXMB01.microfocus.com>
Message-ID: <20170202150223.pioc3o3vslrc6nzm@jf_suse_laptop>

On Thu, Feb 02, 2017 at 02:53:50PM +0000, Thomas Graetz wrote:
>Hi,
>
>the version we are using is 2015.8.12

Assuming you have an older version of DeepSea, this salt version trigger this.  
The latest release carries this fix. To be found here:
https://build.opensuse.org/package/show/home:swiftgist/deepsea
>
>-----Urspr?ngliche Nachricht-----
>Von: deepsea-users-bounces at lists.suse.com [mailto:deepsea-users-bounces at lists.suse.com] Im Auftrag von Joshua Schmid
>Gesendet: Donnerstag, 2. Februar 2017 15:24
>An: deepsea-users at lists.suse.com
>Betreff: Re: [Deepsea-users] Installing SES4 with Salt
>
>Hey Thomas,
>
>On 02/02/2017 03:18 PM, Thomas Graetz wrote:
>> Hi,
>>
>> I try to install SES4 with Salt but when I run "salt-run state.orch ceph.stage.3" the following error message shows up:
>>
>> Any ideas?
>
>looks very much like this: github.com/SUSE/DeepSea/issues/50
>
>fix for this is here: https://github.com/SUSE/DeepSea/pull/51
>
>what's your salt version?
>
>>
>>
>> [ERROR   ] Rendering exception occurred: Jinja error: runner() got multiple values for keyword argument 'name'
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>>     output = template.render(**decoded_context)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>>     return self.environment.handle_exception(exc_info, True)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>>     reraise(exc_type, exc_value, tb)
>>   File "<template>", line 4, in top-level template code
>> TypeError: runner() got multiple values for keyword argument 'name'
>>
>> ; line 4
>>
>> ---
>>
>> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 'True')
>> %}
>>
>> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
>> ready check failed:
>>   salt.state:
>>     - name: "Fail on Warning is True"
>>     - tgt: {{ salt['pillar.get']('master_minion') }}
>>     - failhard: True
>> [...]
>> ---
>> [CRITICAL] Rendering SLS 'base:ceph.stage.3.default' failed: Jinja error: runner() got multiple values for keyword argument 'name'
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>>     output = template.render(**decoded_context)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>>     return self.environment.handle_exception(exc_info, True)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>>     reraise(exc_type, exc_value, tb)
>>   File "<template>", line 4, in top-level template code
>> TypeError: runner() got multiple values for keyword argument 'name'
>>
>> ; line 4
>>
>> ---
>>
>> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 'True')
>> %}
>>
>> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
>> ready check failed:
>>   salt.state:
>>     - name: "Fail on Warning is True"
>>     - tgt: {{ salt['pillar.get']('master_minion') }}
>>     - failhard: True
>> [...]
>> ---
>> salt.site.tld_master:
>>     Data failed to compile:
>> ----------
>>     Rendering SLS 'base:ceph.stage.3.default' failed: Jinja error: runner() got multiple values for keyword argument 'name'
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>>     output = template.render(**decoded_context)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>>     return self.environment.handle_exception(exc_info, True)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>>     reraise(exc_type, exc_value, tb)
>>   File "<template>", line 4, in top-level template code
>> TypeError: runner() got multiple values for keyword argument 'name'
>>
>> ; line 4
>>
>> ---
>>
>> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 'True')
>> %}
>>
>> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
>> ready check failed:
>>   salt.state:
>>     - name: "Fail on Warning is True"
>>     - tgt: {{ salt['pillar.get']('master_minion') }}
>>     - failhard: True
>> [...]
>> ---
>>
>>
>>
>> _______________________________________________
>> Deepsea-users mailing list
>> Deepsea-users at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/deepsea-users
>>
>
>--
>Freundliche Gr??e - Kind regards,
>Joshua Schmid
>SUSE Enterprise Storage
>SUSE Linux GmbH - Maxfeldstr. 5 - 90409 N?rnberg
>--------------------------------------------------------------------------------------------------------------------
>SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg)
>--------------------------------------------------------------------------------------------------------------------
>_______________________________________________
>Deepsea-users mailing list
>Deepsea-users at lists.suse.com
>http://lists.suse.com/mailman/listinfo/deepsea-users
>_______________________________________________
>Deepsea-users mailing list
>Deepsea-users at lists.suse.com
>http://lists.suse.com/mailman/listinfo/deepsea-users

-- 
Jan Fajerski
Engineer Enterprise Storage
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton,
HRB 21284 (AG N?rnberg)

From thomas.graetz at suse.com  Thu Feb  2 08:21:39 2017
From: thomas.graetz at suse.com (Thomas Graetz)
Date: Thu, 2 Feb 2017 15:21:39 +0000
Subject: [Deepsea-users] Installing SES4 with Salt
In-Reply-To: <20170202150223.pioc3o3vslrc6nzm@jf_suse_laptop>
References: <19AADEB379BD6F42B71731B0D5A6602C52A18F@NWBXMB01.microfocus.com>
	<c122af95-67e5-0b30-263f-e7293a0a60c2@suse.de>
	<19AADEB379BD6F42B71731B0D5A6602C52A26B@NWBXMB01.microfocus.com>
	<20170202150223.pioc3o3vslrc6nzm@jf_suse_laptop>
Message-ID: <19AADEB379BD6F42B71731B0D5A6602C52A2D8@NWBXMB01.microfocus.com>

Hi,

after I changed the three mentioned files I ran Step 3 again, the following error appeared:

firewall                 : disabled
fsid                     : valid
public_network           : valid
public_interface         : valid
cluster_network          : valid
cluster_interface        : valid
monitors                 : valid
storage                  : valid
master_role              : valid
mon_host                 : valid
mon_initial_members      : valid
fqdn                     : valid
time_server              : ['salt.site.tld 127.0.0.2 no UCST response after 1 seconds']
[ERROR   ] No highstate or sls specified, no execution made
salt.site.tld_master:
----------
          ID: validate failed
    Function: salt.state
        Name: just.exit
      Result: False
     Comment: No highstate or sls specified, no execution made
     Started: 15:13:36.816912
    Duration: 0.551 ms
     Changes:

Summary for salt.site.tld_master
------------
Succeeded: 0
Failed:    1
------------
Total states run:     1
Total run time:   0.551 ms

-----Urspr?ngliche Nachricht-----
Von: deepsea-users-bounces at lists.suse.com [mailto:deepsea-users-bounces at lists.suse.com] Im Auftrag von Jan Fajerski
Gesendet: Donnerstag, 2. Februar 2017 16:02
An: deepsea-users at lists.suse.com
Betreff: Re: [Deepsea-users] Installing SES4 with Salt

On Thu, Feb 02, 2017 at 02:53:50PM +0000, Thomas Graetz wrote:
>Hi,
>
>the version we are using is 2015.8.12

Assuming you have an older version of DeepSea, this salt version trigger this.  
The latest release carries this fix. To be found here:
https://build.opensuse.org/package/show/home:swiftgist/deepsea
>
>-----Urspr?ngliche Nachricht-----
>Von: deepsea-users-bounces at lists.suse.com 
>[mailto:deepsea-users-bounces at lists.suse.com] Im Auftrag von Joshua 
>Schmid
>Gesendet: Donnerstag, 2. Februar 2017 15:24
>An: deepsea-users at lists.suse.com
>Betreff: Re: [Deepsea-users] Installing SES4 with Salt
>
>Hey Thomas,
>
>On 02/02/2017 03:18 PM, Thomas Graetz wrote:
>> Hi,
>>
>> I try to install SES4 with Salt but when I run "salt-run state.orch ceph.stage.3" the following error message shows up:
>>
>> Any ideas?
>
>looks very much like this: github.com/SUSE/DeepSea/issues/50
>
>fix for this is here: https://github.com/SUSE/DeepSea/pull/51
>
>what's your salt version?
>
>>
>>
>> [ERROR   ] Rendering exception occurred: Jinja error: runner() got multiple values for keyword argument 'name'
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>>     output = template.render(**decoded_context)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>>     return self.environment.handle_exception(exc_info, True)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>>     reraise(exc_type, exc_value, tb)
>>   File "<template>", line 4, in top-level template code
>> TypeError: runner() got multiple values for keyword argument 'name'
>>
>> ; line 4
>>
>> ---
>>
>> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 
>> 'True') %}
>>
>> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
>> ready check failed:
>>   salt.state:
>>     - name: "Fail on Warning is True"
>>     - tgt: {{ salt['pillar.get']('master_minion') }}
>>     - failhard: True
>> [...]
>> ---
>> [CRITICAL] Rendering SLS 'base:ceph.stage.3.default' failed: Jinja error: runner() got multiple values for keyword argument 'name'
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>>     output = template.render(**decoded_context)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>>     return self.environment.handle_exception(exc_info, True)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>>     reraise(exc_type, exc_value, tb)
>>   File "<template>", line 4, in top-level template code
>> TypeError: runner() got multiple values for keyword argument 'name'
>>
>> ; line 4
>>
>> ---
>>
>> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 
>> 'True') %}
>>
>> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
>> ready check failed:
>>   salt.state:
>>     - name: "Fail on Warning is True"
>>     - tgt: {{ salt['pillar.get']('master_minion') }}
>>     - failhard: True
>> [...]
>> ---
>> salt.site.tld_master:
>>     Data failed to compile:
>> ----------
>>     Rendering SLS 'base:ceph.stage.3.default' failed: Jinja error: runner() got multiple values for keyword argument 'name'
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/salt/utils/templates.py", line 368, in render_jinja_tmpl
>>     output = template.render(**decoded_context)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 989, in render
>>     return self.environment.handle_exception(exc_info, True)
>>   File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 754, in handle_exception
>>     reraise(exc_type, exc_value, tb)
>>   File "<template>", line 4, in top-level template code
>> TypeError: runner() got multiple values for keyword argument 'name'
>>
>> ; line 4
>>
>> ---
>>
>> {% set FAIL_ON_WARNING = salt['pillar.get']('FAIL_ON_WARNING', 
>> 'True') %}
>>
>> {% if salt['saltutil.runner']('ready.check', name='ceph', fail_on_warning=FAIL_ON_WARNING)  == False %}    <======================
>> ready check failed:
>>   salt.state:
>>     - name: "Fail on Warning is True"
>>     - tgt: {{ salt['pillar.get']('master_minion') }}
>>     - failhard: True
>> [...]
>> ---
>>
>>
>>
>> _______________________________________________
>> Deepsea-users mailing list
>> Deepsea-users at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/deepsea-users
>>
>
>--
>Freundliche Gr??e - Kind regards,
>Joshua Schmid
>SUSE Enterprise Storage
>SUSE Linux GmbH - Maxfeldstr. 5 - 90409 N?rnberg
>-----------------------------------------------------------------------
>---------------------------------------------
>SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Jennifer Guild, 
>Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg)
>-----------------------------------------------------------------------
>---------------------------------------------
>_______________________________________________
>Deepsea-users mailing list
>Deepsea-users at lists.suse.com
>http://lists.suse.com/mailman/listinfo/deepsea-users
>_______________________________________________
>Deepsea-users mailing list
>Deepsea-users at lists.suse.com
>http://lists.suse.com/mailman/listinfo/deepsea-users

--
Jan Fajerski
Engineer Enterprise Storage
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) _______________________________________________
Deepsea-users mailing list
Deepsea-users at lists.suse.com
http://lists.suse.com/mailman/listinfo/deepsea-users

From Robert.Grosschopff at suse.com  Fri Feb  3 05:55:00 2017
From: Robert.Grosschopff at suse.com (Robert Grosschopff)
Date: Fri, 3 Feb 2017 12:55:00 +0000
Subject: [Deepsea-users] Salt: Cluster Network
Message-ID: <5D4E8032-EBD0-45F1-AC0C-EC19CB1E749F@suse.com>

Hi ,

how does deepsea find out which is the cluster network ?

Thanks
Robert 


From Robert.Grosschopff at suse.com  Fri Feb  3 06:13:37 2017
From: Robert.Grosschopff at suse.com (Robert Grosschopff)
Date: Fri, 3 Feb 2017 13:13:37 +0000
Subject: [Deepsea-users] Salt: Cluster Network
Message-ID: <E2C47258-3761-4022-8BBB-C5EB253F7429@suse.com>

OK. It creates an entry in /srv/pillar/ceph/stack/default/ceph/cluster.yml
that can be overridden by entries in /srv/pillar/ceph/stack/ceph/cluster.yml

I wonder why we keep getting the following errors:

cluster_interface	: [?minion osd02.site.tld missing address on cluster network 192.168.151.0/24 ?]
[ERROR     	] No highstate or sls specified, no execution made


Any hints ?
Robert



On 03/02/2017, 13:55, "deepsea-users-bounces at lists.suse.com on behalf of Robert Grosschopff" <deepsea-users-bounces at lists.suse.com on behalf of Robert.Grosschopff at suse.com> wrote:

    Hi ,
    
    how does deepsea find out which is the cluster network ?
    
    Thanks
    Robert 
    
    _______________________________________________
    Deepsea-users mailing list
    Deepsea-users at lists.suse.com
    http://lists.suse.com/mailman/listinfo/deepsea-users
    


From ejackson at suse.com  Fri Feb  3 06:35:01 2017
From: ejackson at suse.com (Eric Jackson)
Date: Fri, 03 Feb 2017 08:35:01 -0500
Subject: [Deepsea-users] Salt: Cluster Network
In-Reply-To: <E2C47258-3761-4022-8BBB-C5EB253F7429@suse.com>
References: <E2C47258-3761-4022-8BBB-C5EB253F7429@suse.com>
Message-ID: <7068089.S8V07MWthF@ruby>

Hi Robert,

On Friday, February 03, 2017 01:13:37 PM Robert Grosschopff wrote:
> OK. It creates an entry in /srv/pillar/ceph/stack/default/ceph/cluster.yml
> that can be overridden by entries in
> /srv/pillar/ceph/stack/ceph/cluster.yml

Correct.  The short answer is that the code guesses what is the most likely 
private ipv4 network shared by all hosts.  If there is more than one, then 
pick the top two (knowing this won't work for everyone, but I haven't heard as 
many complaints as anticipated.)
 
> I wonder why we keep getting the following errors:
> 
> cluster_interface	: [?minion osd02.site.tld missing address on cluster
> network 192.168.151.0/24 ?]
 [ERROR     	] No highstate or sls specified,
> no execution made

It's a sanity check.  All ceph nodes need an interface on the public network.  
All storage nodes need an interface on the cluster network.  So, first 
question:  is 192.168.151.0/24 a suitable cluster network?  If so, the query 
to Salt about osd02 seems to think that no address in that subnet is assigned 
to any interface on that minion.

Take a look at 

salt 'osd02*' grains.items

Reconcile that output (you'll notice a few stanzas related to addresses) 
against ifconfig/ip.

Hope that helps.

Eric
> 
> 
> Any hints ?
> Robert
> 
> 
> 
> On 03/02/2017, 13:55, "deepsea-users-bounces at lists.suse.com on behalf of
> Robert Grosschopff" <deepsea-users-bounces at lists.suse.com on behalf of
> Robert.Grosschopff at suse.com> wrote:
 
>     Hi ,
>     
>     how does deepsea find out which is the cluster network ?
>     
>     Thanks
>     Robert 
>     
>     _______________________________________________
>     Deepsea-users mailing list
>     Deepsea-users at lists.suse.com
>     http://lists.suse.com/mailman/listinfo/deepsea-users
>     
> 
> _______________________________________________
> Deepsea-users mailing list
> Deepsea-users at lists.suse.com
> http://lists.suse.com/mailman/listinfo/deepsea-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.suse.com/pipermail/deepsea-users/attachments/20170203/43280217/attachment.sig>

From loic.devulder at mpsa.com  Fri Feb 10 06:44:01 2017
From: loic.devulder at mpsa.com (LOIC DEVULDER - U329683)
Date: Fri, 10 Feb 2017 13:44:01 +0000
Subject: [Deepsea-users] NTP configuration
References: <3CBFA7CC2505A74B9C172B35128B88637EDAD27E@YLAV4460.INETPSA.com>
	<55002178.YIbAjLZtEa@ruby>  
Message-ID: <HE1PR0801MB13241C3E5D824F4146C36AE980440@HE1PR0801MB1324.eurprd08.prod.outlook.com>

Hi all,

Just an up of this mail because I don't have seen any answers regarding my last question (yes there's a question in all these words!).

Regards,

Loic

> -----Message d'origine-----
> De?: LOIC DEVULDER - U329683
> Envoy??: lundi 23 janvier 2017 16:40
> ??: 'Discussions about the DeepSea management framework for Ceph'
> <deepsea-users at lists.suse.com>
> Objet?: RE: [Deepsea-users] NTP configuration
> 
> Hi again,
> 
> After reading the validate.py file I found another method to disable NTP
> configuration from DeepSea: I can set time_service to disable in
> global.yml file:
> ylal8020:/srv/pillar/ceph/proposals # cat config/stack/default/global.yml
> time_service: disabled
> 
> It's better because I can see that time_server is disabled when I run the
> stage 3 but I have an error whith sntp. DeepSea tries to execute a sntp
> command with no hostname and so it fails:
> ylal8020:/srv/pillar/ceph/proposals # salt-run state.orch
> ceph.stage.deploy [WARNING ] Although 'dmidecode' was found in path, the
> current user cannot execute it. Grains output might not be accurate.
> [WARNING ] Although 'dmidecode' was found in path, the current user cannot
> execute it. Grains output might not be accurate.
> [WARNING ] Although 'dmidecode' was found in path, the current user cannot
> execute it. Grains output might not be accurate.
> firewall                 : disabled
> [WARNING ] Although 'dmidecode' was found in path, the current user cannot
> execute it. Grains output might not be accurate.
> fsid                     : valid
> public_network           : valid
> public_interface         : valid
> cluster_network          : valid
> cluster_interface        : valid
> monitors                 : valid
> storage                  : valid
> master_role              : valid
> mon_host                 : valid
> mon_initial_members      : valid
> time_server              : disabled
> fqdn                     : valid
> [ERROR   ] Run failed on minions: ylxl0080.inetpsa.com,
> ylal8300.inetpsa.com, ylxl0050.inetpsa.com, ylal8020.inetpsa.com,
> ylal8290.inetpsa.com, ylxl0060.inetpsa.com, ylxl0070.inetpsa.com,
> ylal8030.inetpsa.com
> Failures:
>     ylxl0080.inetpsa.com:
>       Name: ntp - Function: pkg.installed - Result: Clean Started: -
> 15:48:10.924640 Duration: 711.651 ms
>     ----------
>               ID: sync time
>         Function: cmd.run
>             Name: sntp -S -c
>           Result: False
>          Comment: Command "sntp -S -c " run
>          Started: 15:48:11.637698
>         Duration: 59.368 ms
>          Changes:
>                   ----------
>                   pid:
>                       16982
>                   retcode:
>                       1
>                   stderr:
>                       /usr/sbin/sntp: The 'concurrent' option requires an
> argument.
>                       sntp - standard Simple Network Time Protocol client
> program - Ver. 4.2.8p9
>                       Usage:  sntp [ -<flag> [<val>] | --<name>[{=|
> }<val>] ]... \
>                                 [ hostname-or-IP ...]
>                       Try 'sntp --help' for more information.
>                   stdout:
> 
>     Summary for ylxl0080.inetpsa.com
>     ------------
>     Succeeded: 1 (changed=1)
>     Failed:    1
>     ------------
>     Total states run:     2
>     Total run time: 771.019 ms
>     ylal8300.inetpsa.com:
>       Name: ntp - Function: pkg.installed - Result: Clean Started: -
> 15:48:10.856634 Duration: 817.354 ms
>     ----------
>               ID: sync time
>         Function: cmd.run
>             Name: sntp -S -c
>           Result: False
>          Comment: Command "sntp -S -c " run
>          Started: 15:48:11.675171
>         Duration: 55.126 ms
>          Changes:
>                   ----------
>                   pid:
>                       2658
>                   retcode:
>                       1
>                   stderr:
>                       /usr/sbin/sntp: The 'concurrent' option requires an
> argument.
>                       sntp - standard Simple Network Time Protocol client
> program - Ver. 4.2.8p9
>                       Usage:  sntp [ -<flag> [<val>] | --<name>[{=|
> }<val>] ]... \
>                                 [ hostname-or-IP ...]
>                       Try 'sntp --help' for more information.
>                   stdout:
> 
> We can see that time_service has disappeared and have been replaced by
> "time_server: disabled". According to validate.py the time_server value is
> set to disabled when time_service is disabled, so it's seems to be normal.
> 
> I try to find how DeepSea executes this cmd.run but my Salt's knowledge
> seems to low :-(
> 
> I was able to bypass this error with Eric's informations from the wiki. I
> added the disabled.sls file and "time_init: disabled" in the
> /srv/pillar/ceph/proposals/config/stack/default/global.yml file and it
> works.
> 
> Is there a way to add a test that not execute this cmd.run when
> time_service/time_server is/are set to disable? It's not a big deal if
> this is not possible, as adding the disabled.sls file is not too
> complicated but it could be easier from a sysadmin point of view :-)
> 
> Regards / Cordialement,
> ___________________________________________________________________
> PSA Groupe
> Lo?c Devulder (loic.devulder at mpsa.com)
> Senior Linux System Engineer / Linux HPC Specialist DF/DDCE/ISTA/DSEP/ULES
> - Linux Team BESSONCOURT / EXTENSION RIVE DROITE / B19 Internal postal
> address: SX.BES.15 Phone Incident - Level 3: 22 94 39 Phone Incident -
> Level 4: 22 92 40
> Office: +33 (0)9 66 66 69 06 (27 69 06)
> Mobile: +33 (0)6 87 72 47 31
> ___________________________________________________________________
> 
> This message may contain confidential information. If you are not the
> intended recipient, please advise the sender immediately and delete this
> message. For further information on confidentiality and the risks inherent
> in electronic communication see http://disclaimer.psa-peugeot-citroen.com.
> 
> 
> > -----Message d'origine-----
> > De?: LOIC DEVULDER - U329683
> > Envoy??: lundi 23 janvier 2017 09:14
> > ??: Discussions about the DeepSea management framework for Ceph
> > <deepsea- users at lists.suse.com> Objet?: RE: [Deepsea-users] NTP
> > configuration
> >
> > Hi,
> >
> > Thanks Eric, that's what I need!
> >
> > Maybe could it be a good idea to add this wiki link at the beginning
> > of the DeepSea installation method paragraph in the SES documentation,
> > to avoid this kind of dumb question :-)
> >
> >
> > Regards / Cordialement,
> > ___________________________________________________________________
> > PSA Groupe
> > Lo?c Devulder (loic.devulder at mpsa.com) Senior Linux System Engineer /
> > Linux HPC Specialist DF/DDCE/ISTA/DSEP/ULES - Linux Team BESSONCOURT /
> > EXTENSION RIVE DROITE / B19 Internal postal
> > address: SX.BES.15 Phone Incident - Level 3: 22 94 39 Phone Incident -
> > Level 4: 22 92 40
> > Office: +33 (0)9 66 66 69 06 (27 69 06)
> > Mobile: +33 (0)6 87 72 47 31
> > ___________________________________________________________________
> >
> > This message may contain confidential information. If you are not the
> > intended recipient, please advise the sender immediately and delete
> > this message. For further information on confidentiality and the risks
> > inherent in electronic communication see http://disclaimer.psa-peugeot-
> citroen.com.
> >
> > > -----Message d'origine-----
> > > De?: deepsea-users-bounces at lists.suse.com [mailto:deepsea-users-
> > > bounces at lists.suse.com] De la part de Eric Jackson Envoy??: vendredi
> > > 20 janvier 2017 20:53 ??: Discussions about the DeepSea management
> > > framework for Ceph <deepsea- users at lists.suse.com> Objet?: Re:
> > > [Deepsea-users] NTP configuration
> > >
> > > >>> Real sender address / Reelle adresse d expedition :
> > > >>> deepsea-users-bounces at lists.suse.com <<<
> > >
> > > ********************************************************************
> > > **
> > > Hi Loic,
> > >   The short answer is to tell DeepSea to do something else which
> > > includes "do nothing".  Check the first example here
> > > https://github.com/SUSE/DeepSea/wiki/customize.  I used ntp.
> > >
> > >   Salt is not fond of absence or empty configurations.  As many
> > > defaults as we tried to put in, state files need at least a no-op.
> > > The strategy throughout DeepSea is everything can be overridden
> > > since I cannot predict what would need to be customized at a site.
> > >
> > > Eric
> > >
> > >
> > > On Friday, January 20, 2017 03:16:13 PM LOIC DEVULDER wrote:
> > > > Hi,
> > > >
> > > > During my tests with DeepSea I ran into a little problem: I can't
> > > > be able to remove the NTP configuration.
> > > >
> > > > Ok I know: why should I want to do this? Simply because I already
> > > > have NTP configured on my servers (we have a custom NTP config in
> > > > my
> > > company).
> > > >
> > > > I try to remove these lines from the
> > > > /srv/pillar/ceph/proposals/config/stack/default/global.yml file:
> > > > ylal8020:/srv/pillar # cat
> > > > ceph/proposals/config/stack/default/global.yml
> > > > time_server: '{{ pillar.get("master_minion") }}'
> > > > time_service: ntp
> > > >
> > > > But I ran into a weird issue while trying to execute the
> > > > configuration
> > > > stage: ylal8020:/srv/pillar # salt-run state.orch
> > > > ceph.stage.configure [WARNING ] Although 'dmidecode' was found in
> > > > path, the current user cannot execute it. Grains output might not
> > > > be accurate. [WARNING ] Although 'dmidecode' was found in path,
> > > > the current user cannot execute it. Grains output might not be
> accurate.
> > > > [WARNING ] Although 'dmidecode' was found in path, the current
> > > > user
> > cannot execute it.
> > > > Grains output might not be accurate. [WARNING ] Although 'dmidecode'
> > > > was found in path, the current user cannot execute it. Grains
> > > > output
> > > might not be accurate.
> > > > ylal8020.inetpsa.com_master:
> > > >   Name: push.proposal - Function: salt.runner - Result: Changed
> > > > Started: -
> > > > 15:53:58.352226 Duration: 563.82 ms Name: refresh_pillar1 -
> Function:
> > > > salt.state - Result: Changed Started: - 15:53:58.916733 Duration:
> > > > 589.218 ms Name: configure.cluster - Function: salt.runner - Result:
> > > > Changed
> > > > Started: - 15:53:59.506662 Duration: 1003.844 ms Name:
> > > > refresh_pillar2
> > > > -
> > > > Function: salt.state - Result: Changed Started: - 15:54:00.511544
> > > Duration:
> > > > 662.566 ms Name: admin key - Function: salt.state - Result: Clean
> > > Started:
> > > > - 15:54:01.174305 Duration: 455.286 ms Name: mon key - Function:
> > > > salt.state
> > > > - Result: Clean Started: - 15:54:01.629844 Duration: 396.696 ms
> Name:
> > > > osd key - Function: salt.state - Result: Clean Started: -
> > > > 15:54:02.026768
> > > > Duration: 391.508 ms Name: igw key - Function: salt.state - Result:
> > > > Clean
> > > > Started: - 15:54:02.418500 Duration: 1192.624 ms Name: mds key -
> > > Function:
> > > > salt.state - Result: Clean Started: - 15:54:03.611366 Duration:
> > > > 1172.492 ms
> > > > Name: rgw key - Function: salt.state - Result: Clean Started: -
> > > > 15:54:04.784086 Duration: 1193.912 ms Name: openattic key -
> Function:
> > > > salt.state - Result: Clean Started: - 15:54:05.978226 Duration:
> > > > 393.879 ms
> > > > Name: igw config - Function: salt.state - Result: Clean Started: -
> > > > 15:54:06.372340 Duration: 1183.398 ms
> > > >
> > > > Summary for ylal8020.inetpsa.com_master
> > > > -------------
> > > > Succeeded: 12 (changed=4)
> > > > Failed:     0
> > > > -------------
> > > > Total states run:     12
> > > > Total run time:    9.199 s
> > > >
> > > > Ok I know there is no direct error but the pillar.items is not
> > > > good, some items are missing: ylal8020:/srv/pillar # salt '*'
> > > > pillar.items
> > > > ylal8300.inetpsa.com:
> > > >     ----------
> > > >     benchmark:
> > > >         ----------
> > > >         default-collection:
> > > >             simple.yml
> > > >         job-file-directory:
> > > >             /run/cephfs_bench_jobs
> > > >         log-file-directory:
> > > >             /var/log/cephfs_bench_logs
> > > >         work-directory:
> > > >             /run/cephfs_bench
> > > >     cluster:
> > > >         ceph
> > > >     master_minion:
> > > >         ylal8020.inetpsa.com
> > > >     mon_host:
> > > >     mon_initial_members:
> > > >         - ylal8290
> > > >         - ylal8030
> > > >         - ylal8300
> > > >     roles:
> > > >         - mon
> > > > ylal8030.inetpsa.com:
> > > >     ----------
> > > >     benchmark:
> > > >         ----------
> > > >         default-collection:
> > > >             simple.yml
> > > >         job-file-directory:
> > > >             /run/cephfs_bench_jobs
> > > >         log-file-directory:
> > > >             /var/log/cephfs_bench_logs
> > > >         work-directory:
> > > >             /run/cephfs_bench
> > > >     cluster:
> > > >         ceph
> > > >     master_minion:
> > > >         ylal8020.inetpsa.com
> > > >     mon_host:
> > > >     mon_initial_members:
> > > >         - ylal8290
> > > >         - ylal8030
> > > >         - ylal8300
> > > >     roles:
> > > >         - mon
> > > > ylal8020.inetpsa.com:
> > > >     ----------
> > > >     benchmark:
> > > >         ----------
> > > >         default-collection:
> > > >             simple.yml
> > > >         job-file-directory:
> > > >             /run/cephfs_bench_jobs
> > > >         log-file-directory:
> > > >             /var/log/cephfs_bench_logs
> > > >         work-directory:
> > > >             /run/cephfs_bench
> > > >     cluster:
> > > >         ceph
> > > >     master_minion:
> > > >         ylal8020.inetpsa.com
> > > >     mon_host:
> > > >     mon_initial_members:
> > > >         - ylal8290
> > > >         - ylal8030
> > > >         - ylal8300
> > > >     roles:
> > > >         - master
> > > >         - admin
> > > > ylxl0060.inetpsa.com:
> > > >     ----------
> > > >     benchmark:
> > > >         ----------
> > > >         default-collection:
> > > >             simple.yml
> > > >         job-file-directory:
> > > >             /run/cephfs_bench_jobs
> > > >         log-file-directory:
> > > >             /var/log/cephfs_bench_logs
> > > >         work-directory:
> > > >             /run/cephfs_bench
> > > >     cluster:
> > > >         ceph
> > > >     master_minion:
> > > >         ylal8020.inetpsa.com
> > > >     mon_host:
> > > >     mon_initial_members:
> > > >         - ylal8290
> > > >         - ylal8030
> > > >         - ylal8300
> > > >     roles:
> > > >         - storage
> > > > ylxl0050.inetpsa.com:
> > > >     ----------
> > > >     benchmark:
> > > >         ----------
> > > >         default-collection:
> > > >             simple.yml
> > > >         job-file-directory:
> > > >             /run/cephfs_bench_jobs
> > > >         log-file-directory:
> > > >             /var/log/cephfs_bench_logs
> > > >         work-directory:
> > > >             /run/cephfs_bench
> > > >     cluster:
> > > >         ceph
> > > >     master_minion:
> > > >         ylal8020.inetpsa.com
> > > >     mon_host:
> > > >     mon_initial_members:
> > > >         - ylal8290
> > > >         - ylal8030
> > > >         - ylal8300
> > > >     roles:
> > > >         - storage
> > > > ylal8290.inetpsa.com:
> > > >     ----------
> > > >     benchmark:
> > > >         ----------
> > > >         default-collection:
> > > >             simple.yml
> > > >         job-file-directory:
> > > >             /run/cephfs_bench_jobs
> > > >         log-file-directory:
> > > >             /var/log/cephfs_bench_logs
> > > >         work-directory:
> > > >             /run/cephfs_bench
> > > >     cluster:
> > > >         ceph
> > > >     master_minion:
> > > >         ylal8020.inetpsa.com
> > > >     mon_host:
> > > >     mon_initial_members:
> > > >         - ylal8290
> > > >         - ylal8030
> > > >         - ylal8300
> > > >     roles:
> > > >         - mon
> > > > ylxl0080.inetpsa.com:
> > > >     ----------
> > > >     benchmark:
> > > >         ----------
> > > >         default-collection:
> > > >             simple.yml
> > > >         job-file-directory:
> > > >             /run/cephfs_bench_jobs
> > > >         log-file-directory:
> > > >             /var/log/cephfs_bench_logs
> > > >         work-directory:
> > > >             /run/cephfs_bench
> > > >     cluster:
> > > >         ceph
> > > >     master_minion:
> > > >         ylal8020.inetpsa.com
> > > >     mon_host:
> > > >     mon_initial_members:
> > > >         - ylal8290
> > > >         - ylal8030
> > > >         - ylal8300
> > > >     roles:
> > > >         - storage
> > > > ylxl0070.inetpsa.com:
> > > >     ----------
> > > >     benchmark:
> > > >         ----------
> > > >         default-collection:
> > > >             simple.yml
> > > >         job-file-directory:
> > > >             /run/cephfs_bench_jobs
> > > >         log-file-directory:
> > > >             /var/log/cephfs_bench_logs
> > > >         work-directory:
> > > >             /run/cephfs_bench
> > > >     cluster:
> > > >         ceph
> > > >     master_minion:
> > > >         ylal8020.inetpsa.com
> > > >     mon_host:
> > > >     mon_initial_members:
> > > >         - ylal8290
> > > >         - ylal8030
> > > >         - ylal8300
> > > >     roles:
> > > >         - storage
> > > >
> > > > So my "simple" question is: how I can configure global.yml to not
> > > > let DeepSea configure NTP?
> > > >
> > > > Regards / Cordialement,
> > > > __________________________________________________________________
> > > > _
> > > > PSA Groupe
> > > > Lo?c Devulder (loic.devulder at mpsa.com) Senior Linux System
> > > > Engineer / Linux HPC Specialist DF/DDCE/ISTA/DSEP/ULES - Linux
> > > > Team BESSONCOURT / EXTENSION RIVE DROITE / B19 Internal postal
> address:
> > > > SX.BES.15 Phone Incident - Level 3: 22 94 39 Phone Incident -
> > > > Level
> > > > 4: 22 92 40
> > > > Office: +33 (0)9 66 66 69 06 (27 69 06)
> > > > Mobile: +33 (0)6 87 72 47 31
> > > > __________________________________________________________________
> > > > _
> > > >
> > > > This message may contain confidential information. If you are not
> > > > the intended recipient, please advise the sender immediately and
> > > > delete this message. For further information on confidentiality
> > > > and the risks inherent in electronic communication see
> > > > http://disclaimer.psa-peugeot-
> > > citroen.com.
> > > >
> > > > _______________________________________________
> > > > Deepsea-users mailing list
> > > > Deepsea-users at lists.suse.com
> > > > http://lists.suse.com/mailman/listinfo/deepsea-users

From loic.devulder at mpsa.com  Fri Feb 10 09:00:04 2017
From: loic.devulder at mpsa.com (LOIC DEVULDER - U329683)
Date: Fri, 10 Feb 2017 16:00:04 +0000
Subject: [Deepsea-users] NTP configuration
In-Reply-To: <8061244.DQdEEpx1UV@ruby>
References: <3CBFA7CC2505A74B9C172B35128B88637EDAD27E@YLAV4460.INETPSA.com>
	<55002178.YIbAjLZtEa@ruby>
	<HE1PR0801MB13241C3E5D824F4146C36AE980440@HE1PR0801MB1324.eurprd08.prod.outlook.com>
	<8061244.DQdEEpx1UV@ruby>
Message-ID: <HE1PR0801MB13247A6AA142D258214EAED480440@HE1PR0801MB1324.eurprd08.prod.outlook.com>

Cool this is exactly what I want :-)

I'll try to test this when SES4 packages will be available.

Thanks.

> -----Message d'origine-----
> De?: deepsea-users-bounces at lists.suse.com [mailto:deepsea-users- 
> bounces at lists.suse.com] De la part de Eric Jackson Envoy??: vendredi 
> 10 f?vrier 2017 15:41 ??: Discussions about the DeepSea management 
> framework for Ceph <deepsea- users at lists.suse.com> Objet?: Re: 
> [Deepsea-users] NTP configuration
> 
> >>> Real sender address / Reelle adresse d expedition :
> >>> deepsea-users-bounces at lists.suse.com <<<
> 
> **********************************************************************
> Hi Loic,
> 
> On Friday, February 10, 2017 01:44:01 PM LOIC DEVULDER - U329683 wrote:
> > Hi all,
> >
> > Just an up of this mail because I don't have seen any answers 
> > regarding my last question (yes there's a question in all these words!).
> >
> > Regards,
> >
> > Loic
> >
> > > > > >
> > > > > > So my "simple" question is: how I can configure global.yml 
> > > > > > to not let DeepSea configure NTP?
> 
>   As you found, you can set time_service: disabled in 
> /srv/pillar/ceph/stack/global.yml.  However, there was a bug that's 
> just been merged to master: https://github.com/SUSE/DeepSea/pull/103
> 
>   It is not yet packaged.
> 
> Eric
> 
> >
> > _______________________________________________
> > Deepsea-users mailing list
> > Deepsea-users at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/deepsea-users

From dbyte at suse.com  Tue Feb 14 12:33:41 2017
From: dbyte at suse.com (David Byte)
Date: Tue, 14 Feb 2017 19:33:41 +0000
Subject: [Deepsea-users] Example configurations for policy.cfg and disk
 configurations?
In-Reply-To: <58A35F850200001C002D0F56@prv-mh.provo.novell.com>
References: <58A35F850200001C002D0F56@prv-mh.provo.novell.com>
Message-ID: <1F8D9599-9242-48EA-9368-85B53CA3BA90@suse.com>

There is a policy config in this doc from the Apollo Cluster I have in provo.

David Byte
Sr. Technology Strategist
Alliances and SUSE Embedded
dbyte at suse.com
918.528.4422

From: <deepsea-users-bounces at lists.suse.com> on behalf of Martin Weiss <Martin.Weiss at suse.com>
Reply-To: Discussions about the DeepSea management framework for Ceph <deepsea-users at lists.suse.com>
Date: Tuesday, February 14, 2017 at 12:50 PM
To: "deepsea-users at lists.suse.com" <deepsea-users at lists.suse.com>
Subject: [Deepsea-users] Example configurations for policy.cfg and disk configurations?

Hi *.

I tried to understand the way how the policy.cfg needs to be filled and how the disk configuration should be configured - but it seems I am missing something and need help and an example to understand this ;-).

Maybe someone can create and share a policy.cfg and some examples for the disk configuration for me that matches somehow my scenario?

My scenario:
----
5 servers: ses-4-admin, ses-4-1,ses-4-2, ses-4-3, ses-4-4

ses-4-admin should get openAttic

ses-4-{1..3} should be a "MON"

ses-4-{1,3} should be a "iSCSI Gateway" where the iSCSI gateway IP is the third IP on each host (separate interface)

ses-4-{2,4} should be two hosts for the same "Rados Gateway"

ses-4-{2..4} should be "MDS"

ses-4-{1..4} should be OSD host

Each OSD host has 24 disks. 4 SSDs (sd{a..d}) and 20 SAS (sd{e..x}).
Always 5 OSDs should get the journal on one SSD - i.e. sde/sdf/sdg/sdh/sdj should get 20 GB journals on sda.
----

So what exactly do I need in my policy.cfg and how do I configure the disks properly?

P.S. I also want to create some pools (replicated and erasure), setup cache tiering, create RBDs and configure them with the iSCSI gateways... do I get it right that this is not yet available in DeepSea?

Thanks for any help,
Martin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/deepsea-users/attachments/20170214/68a96e19/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Apollo Implementation Guide - SES 4.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 1822527 bytes
Desc: Apollo Implementation Guide - SES 4.docx
URL: <http://lists.suse.com/pipermail/deepsea-users/attachments/20170214/68a96e19/attachment.bin>

From dbyte at suse.com  Tue Feb 14 12:34:37 2017
From: dbyte at suse.com (David Byte)
Date: Tue, 14 Feb 2017 19:34:37 +0000
Subject: [Deepsea-users] Example configurations for policy.cfg and disk
 configurations?
In-Reply-To: <1F8D9599-9242-48EA-9368-85B53CA3BA90@suse.com>
References: <58A35F850200001C002D0F56@prv-mh.provo.novell.com>
	<1F8D9599-9242-48EA-9368-85B53CA3BA90@suse.com>
Message-ID: <BCA87DDE-6B47-43F0-98AD-D532939619AA@suse.com>

Sorry for the list posting.  I didn?t catch the wide response until after I hit send.

David Byte
Sr. Technology Strategist
Alliances and SUSE Embedded
dbyte at suse.com
918.528.4422

From: <deepsea-users-bounces at lists.suse.com> on behalf of David Byte <dbyte at suse.com>
Reply-To: Discussions about the DeepSea management framework for Ceph <deepsea-users at lists.suse.com>
Date: Tuesday, February 14, 2017 at 1:33 PM
To: Discussions about the DeepSea management framework for Ceph <deepsea-users at lists.suse.com>
Subject: Re: [Deepsea-users] Example configurations for policy.cfg and disk configurations?

There is a policy config in this doc from the Apollo Cluster I have in provo.

David Byte
Sr. Technology Strategist
Alliances and SUSE Embedded
dbyte at suse.com
918.528.4422

From: <deepsea-users-bounces at lists.suse.com> on behalf of Martin Weiss <Martin.Weiss at suse.com>
Reply-To: Discussions about the DeepSea management framework for Ceph <deepsea-users at lists.suse.com>
Date: Tuesday, February 14, 2017 at 12:50 PM
To: "deepsea-users at lists.suse.com" <deepsea-users at lists.suse.com>
Subject: [Deepsea-users] Example configurations for policy.cfg and disk configurations?

Hi *.

I tried to understand the way how the policy.cfg needs to be filled and how the disk configuration should be configured - but it seems I am missing something and need help and an example to understand this ;-).

Maybe someone can create and share a policy.cfg and some examples for the disk configuration for me that matches somehow my scenario?

My scenario:
----
5 servers: ses-4-admin, ses-4-1,ses-4-2, ses-4-3, ses-4-4

ses-4-admin should get openAttic

ses-4-{1..3} should be a "MON"

ses-4-{1,3} should be a "iSCSI Gateway" where the iSCSI gateway IP is the third IP on each host (separate interface)

ses-4-{2,4} should be two hosts for the same "Rados Gateway"

ses-4-{2..4} should be "MDS"

ses-4-{1..4} should be OSD host

Each OSD host has 24 disks. 4 SSDs (sd{a..d}) and 20 SAS (sd{e..x}).
Always 5 OSDs should get the journal on one SSD - i.e. sde/sdf/sdg/sdh/sdj should get 20 GB journals on sda.
----

So what exactly do I need in my policy.cfg and how do I configure the disks properly?

P.S. I also want to create some pools (replicated and erasure), setup cache tiering, create RBDs and configure them with the iSCSI gateways... do I get it right that this is not yet available in DeepSea?

Thanks for any help,
Martin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/deepsea-users/attachments/20170214/9ba19cde/attachment.htm>

From jschmid at suse.de  Wed Feb 15 02:20:09 2017
From: jschmid at suse.de (Joshua Schmid)
Date: Wed, 15 Feb 2017 10:20:09 +0100
Subject: [Deepsea-users] Antw: Re: Example configurations for policy.cfg
 and disk configurations?
In-Reply-To: <58A36FFF0200001C002D10CF@prv-mh.provo.novell.com>
References: <58A35F850200001C002D0F56@prv-mh.provo.novell.com>
	<1F8D9599-9242-48EA-9368-85B53CA3BA90@suse.com>
	<58A36FFF0200001C002D10CF@prv-mh.provo.novell.com>
Message-ID: <30fe8b77-b993-2642-7ede-d6901b074910@suse.de>

Hey, Martin

[..]

> 
> But I still have some more questions - maybe you can help?
> 
> What adjustments were done in the global.yml / cluster.yml?
> 

You can find more information in the wiki:

https://github.com/SUSE/DeepSea/wiki

> What is the adjustments you have done in these role assignments:
>> role-mon/stack/default/ceph/minions/monnode*.yml
>> role-igw/stack/default/ceph/minions/igwnode*.suse.lab.yml
> (how did you configure separate IP addresses for each of the iSCSI gateways?)
> 
> Do you also have some details about the Hardware profile configuration to achieve the OSD / disk setup required?
> -> What exactly do I have to do to get the 5:1 SSD <-> SAS setup for journals and have each of the journals 20 GB in size?
>

Deepsea tries to find a nice ratio for you SSD<->HDD. In you case (
20sas/5ssd ), it will create the 5:1 ratio.

You can verify if deepsea guessed correctly by looking in:

/srv/pillar/ceph/proposals/profile-*/stack/default/ceph/minions/<host>.yml

the section: `data+journals` should reflect this.

There is currently a ongoing effort to allow custom ratios/profiles.
-> https://github.com/SUSE/DeepSea/issues/76



> Thanks
> Martin 
> 
> 
> 
>> There is a policy config in this doc from the Apollo Cluster I have in provo.
>  
> David Byte
> Sr. Technology Strategist
> Alliances and SUSE Embedded
> dbyte at suse.com
> 918.528.4422
>  
> From: <deepsea-users-bounces at lists.suse.com> on behalf of Martin Weiss <Martin.Weiss at suse.com>
> Reply-To: Discussions about the DeepSea management framework for Ceph <deepsea-users at lists.suse.com>
> Date: Tuesday, February 14, 2017 at 12:50 PM
> To: "deepsea-users at lists.suse.com" <deepsea-users at lists.suse.com>
> Subject: [Deepsea-users] Example configurations for policy.cfg and disk configurations?
>  
> Hi *.
>  
> I tried to understand the way how the policy.cfg needs to be filled and how the disk configuration should be configured - but it seems I am missing something and need help and an example to understand this ;-).
>  
> Maybe someone can create and share a policy.cfg and some examples for the disk configuration for me that matches somehow my scenario?
>  
> My scenario:
> ----
> 5 servers: ses-4-admin, ses-4-1,ses-4-2, ses-4-3, ses-4-4
>  
> ses-4-admin should get openAttic
>  
> ses-4-{1..3} should be a "MON"
>  
> ses-4-{1,3} should be a "iSCSI Gateway" where the iSCSI gateway IP is the third IP on each host (separate interface)
>  
> ses-4-{2,4} should be two hosts for the same "Rados Gateway"
>  
> ses-4-{2..4} should be "MDS"
>  
> ses-4-{1..4} should be OSD host
>  
> Each OSD host has 24 disks. 4 SSDs (sd{a..d}) and 20 SAS (sd{e..x}).
> Always 5 OSDs should get the journal on one SSD - i.e. sde/sdf/sdg/sdh/sdj should get 20 GB journals on sda.
> ----
>  
> So what exactly do I need in my policy.cfg and how do I configure the disks properly?
>  
> P.S. I also want to create some pools (replicated and erasure), setup cache tiering, create RBDs and configure them with the iSCSI gateways... do I get it right that this is not yet available in DeepSea?
>  
> Thanks for any help,
> Martin
>  
> 
> 
> 
> _______________________________________________
> Deepsea-users mailing list
> Deepsea-users at lists.suse.com
> http://lists.suse.com/mailman/listinfo/deepsea-users
> 

-- 
Freundliche Gr??e - Kind regards,
Joshua Schmid
SUSE Enterprise Storage
SUSE Linux GmbH - Maxfeldstr. 5 - 90409 N?rnberg
--------------------------------------------------------------------------------------------------------------------
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard,
Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg)
--------------------------------------------------------------------------------------------------------------------

From rdias at suse.com  Thu Feb 16 01:24:28 2017
From: rdias at suse.com (Ricardo Dias)
Date: Thu, 16 Feb 2017 08:24:28 +0000
Subject: [Deepsea-users] Multiple Public Networks Support?
In-Reply-To: <58A560010200001C002D176B@prv-mh.provo.novell.com>
References: <58A560010200001C002D176B@prv-mh.provo.novell.com>
Message-ID: <a67a1ff7-04f7-d341-97df-765cf901c59f@suse.com>

Hi Martin,

Short answer is no, but it will soon.

We have a pending PR to add the support for multiple public/cluster networks.
https://github.com/SUSE/DeepSea/pull/96

Ricardo Dias

On 16-02-2017 07:17, Martin Weiss wrote:
> Hi *,
> 
> as we have learned that for stretched clusters over two data-centers we need to
> put one monitor to a third data-center it is required to support multiple public
> networks for deployment.
> (the third monitor might not be in the same layer 2 network as the other MONs
> and the OSDs..)
> 
> Does deepSea support that already?
> 
> Thanks,
> Martin
> 
> 
> _______________________________________________
> Deepsea-users mailing list
> Deepsea-users at lists.suse.com
> http://lists.suse.com/mailman/listinfo/deepsea-users
> 

-- 
Ricardo Dias
Senior Software Engineer - Storage Team
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284
(AG N?rnberg)

From lgrimmer at suse.com  Thu Feb 16 01:35:59 2017
From: lgrimmer at suse.com (Lenz Grimmer)
Date: Thu, 16 Feb 2017 09:35:59 +0100
Subject: [Deepsea-users] How does the Salt REST-API handle long-running
	requests?
Message-ID: <ee2425a9-99db-992c-a8e0-5a4fb7d7e526@suse.com>

Hi,

$TOPIC basically says it all - I'm wondering how the API deals with
long-running requests, as this has an impact on how it can be used from
a WebUI.

Does it always return immediately and one has to query the state of the
request in a queue? This is something we need to keep in mind when
implementing the UI part in openATTIC - we have a generic task queue
implementation there already, that could be used to schedule these requests.

Lenz

-- 
SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany)
GF:Felix Imend?rffer,Jane Smithard,Graham Norton,HRB 21284 (AG N?rnberg)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.suse.com/pipermail/deepsea-users/attachments/20170216/e3f6c528/attachment.sig>

From Supriti.Singh at suse.com  Mon Feb 20 01:53:26 2017
From: Supriti.Singh at suse.com (Supriti Singh)
Date: Mon, 20 Feb 2017 09:53:26 +0100
Subject: [Deepsea-users] DeepSea 0.7.4
In-Reply-To: <5243645.HYzUpFhoD8@ruby>
References: <5243645.HYzUpFhoD8@ruby>
Message-ID: <58AABC9602000042001C5154@smtp.nue.novell.com>

Adding to Eric's comment: 

The documentation for nfs-ganesha is present at Deepsea wiki: https://github.com/SUSE/DeepSea/wiki/NFS-Ganesha 


------
Supriti Singh??SUSE Linux GmbH, GF: Felix Imend??rffer, Jane Smithard, Graham Norton,
HRB 21284 (AG N??rnberg)
 



>>> Eric Jackson <ejackson at suse.com> 02/17/17 9:36 PM >>>
Hello all,
  DeepSea 0.7.4 has been released.  Few changes, but one significant milestone:

- Add missing import
- Add kernel.replace 
  Only applies to SUSE and systems running the minimal kernel-default-base,
  but supports other systems.  This also generalizes the update step to use 
  Salt primitives and not call zypper specifically.
- Add Ganesha

  Before explaining some caveats, DeepSea 0.7.4 is tested against Ceph 11.1 
with Ganesha 2.5.  Ganesha 2.4 does not support certain features (e.g. no 
admin keyring required for cephfs FSAL)

  The rpm is available from
https://build.opensuse.org/package/show/home:swiftgist/deepsea

-------------------------------------------------------------
The remainder of this announcement is for those wanting quick hints about 
Ganesha.  The documentation is in progress.


* What is Ganesha?
  Ganesha is an NFS frontend to a variety of backends.  For Ceph, two backends 
are supported: cephfs and rgw.

* Why would I use Ganesha?  What about CephFS?
  If your clients support CephFS directly, then use CephFS.  However, a Linux 
host that does not have CephFS support can still connect to the same filesystem 
using NFS.

  For Rados Gateway, several S3 clients exist, but some users are more 
comfortable and familiar with a filesystem interface.  With NFS, the buckets 
and contents are presented as directories with files.

* How does this work in DeepSea?
  By default, assign the ganesha role to the minions in your policy.cfg.  
Also, include either cephfs (mds), radosgw (rgw) or both assignments in your 
policy.cfg.  For rgw, uncomment the example left in 
/srv/pillar/ceph/stack/ceph/cluster.yml for new installations.  

  Run Stages 2-4 as you normally would.  From an NFS client, run

mount ganesha1:/cephfs /mnt1
mount ganesha1:/demo /mnt2

  where ganesha1 is the name of the ganesha host and demo is the rgw user.

* Caveats:
  The mounts should work immediately.  If you get an error, raise the debug 
level of your ganesha server (e.g. /etc/sysconfig/ganesha, systemctl restart 
nfs-ganesha).
  If the first write results in an ENOMEM, check that your VM on your monitor 
has enough RAM.  If the first write hangs, check that 

default.rgw.buckets.index
default.rgw.buckets.data

  are created.  (In a slow enough VM, this may take a moment.)  These seem to 
be the most common initial obstacles.

  WARNING: While both cephfs and rgw mounts work, the rgw mounts do not show 
up under 'df', but do appear in the mount command.  

  Custom ganesha roles are supported.  This needs documentation, but is 
currently working. (Rather than using the label ganesha, create any labels 
needed with customized configurations.  c.f. ganesha_configurations)

  Lastly, using tools such as s3 from the libs3-2 package for creating buckets 
and placing objects will result in different permissions and ownership than 
using the NFS mount with the normal filesystem operations (e.g. root vs. 
nobody).

Eric

  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/deepsea-users/attachments/20170220/c490610c/attachment.htm>