rum is informally monitored as time permits and should not be used
for priority messages to the Spectrum Scale (GPFS) team.
From: IBM Spectrum Scale/Poughkeepsie/IBM
To: gpfsug main discussion list
Date: 10/10/2017 10:48 AM
Subject: Re: [gpfsug-discuss] changing defaul
mally monitored as time permits and should not be used
for priority messages to the Spectrum Scale (GPFS) team.
From: "Simon Thompson (IT Research Support)"
To: gpfsug main discussion list
Date: 10/10/2017 08:36 AM
Subject: Re: [gpfsug-discuss]
s I've always had
>>>>with
>>>> mmconfig..
>>>>
>>>> If I have a cluster to which new nodes will eventually be added, OR, I
>>>> have standard I always wish to apply, there is no way to say "all
>>>>FUTURE"
>>>
If so,excellent. Thanks
>>
>>
>> Original Message
>> From: s.j.thomp...@bham.ac.uk
>> Sent: October 10, 2017 8:02 AM
>> To: gpfsug-discuss@spectrumscale.org
>> Reply-to: gpfsug-discuss@spectrumscale.org
>> Subject: Re: [gpfsug-discuss] changing de
excellent. Thanks
>
>
> Original Message
>From: s.j.thomp...@bham.ac.uk
>Sent: October 10, 2017 8:02 AM
>To: gpfsug-discuss@spectrumscale.org
>Reply-to: gpfsug-discuss@spectrumscale.org
>Subject: Re: [gpfsug-discuss] changing default configuration values
>
>Use mmchc
Yes, this is exactly what we do for our LROC enabled nodes. Add them to the
node class and you're all set.
Bob Oesterlin
Sr Principal Storage Engineer, Nuance
On 10/10/17, 7:03 AM, "gpfsug-discuss-boun...@spectrumscale.org on behalf of
Simon Thompson (IT Research Support)" wrote:
Appl
to extended the
>changes in as new nodes are brought into the cluster.
>
>Is there a way to accomplish this?
>Thanks
>
> Original Message
>From: aaron.s.knis...@nasa.gov
>Sent: October 9, 2017 2:56 PM
>To: gpfsug-discuss@spectrumscale.org
>Reply-to: gpfsug-discus
nodes are brought into the cluster.
>
>Is there a way to accomplish this?
>Thanks
>
> Original Message
>From: aaron.s.knis...@nasa.gov
>Sent: October 9, 2017 2:56 PM
>To: gpfsug-discuss@spectrumscale.org
>Reply-to: gpfsug-discuss@spectrumscale.org
>Subject: Re: [gpfsug
>
> From: Aaron Knister
> To: gpfsug main discussion list
> Date: 10/06/2017 06:30 PM
> Subject: [gpfsug-discuss] changing default configuration values
> Sent by: gpfsug-discuss-boun...@spectrumscale.org
>
>
:30:20 PM---Is there a way to change the default value
of a configuration option without overriding any overrid
From: Aaron Knister
To: gpfsug main discussion list
Date: 10/06/2017 06:30 PM
Subject: [gpfsug-discuss] changing default configuration values
Sent by: gpfsug-discuss-boun
scussion list
*Cc:* gpfsug-discuss-boun...@spectrumscale.org
*Subject:* Re: [gpfsug-discuss] changing default configuration values
Hi Aaron,
The default value applies to all nodes in the cluster. Thus changing it
will change all nodes in the cluster. You need to run mmchconfig to
customize
...@spectrumscale.org] On Behalf Of IBM Spectrum
Scale
Sent: Saturday, October 07, 2017 5:07 AM
To: gpfsug main discussion list
Cc: gpfsug-discuss-boun...@spectrumscale.org
Subject: Re: [gpfsug-discuss] changing default configuration values
Hi Aaron,
The default value applies to all nodes in the cluster. Thus
used
for priority messages to the Spectrum Scale (GPFS) team.
From: Aaron Knister
To: gpfsug main discussion list
Date: 10/06/2017 06:30 PM
Subject:[gpfsug-discuss] changing default configuration values
Sent by:gpfsug-discuss-boun...@spectrumscale.org
Is there a way to
Is there a way to change the default value of a configuration option
without overriding any overrides in place?
Take the following situation:
- I set parameter foo=bar for all nodes (mmchconfig foo=bar)
- I set parameter foo to baz for a few nodes (mmchconfig foo=baz -N
n001,n002)
Is there a
14 matches
Mail list logo
