They do, but ... I don't know what happens to a running node if its then added to a nodeclass. Ie.. Would it apply the options it can immediately, or only once the node is recycled?
Pass... Making an mmchconfig change to the node class after its a member would work as expected. Simon On 10/10/2017, 13:32, "[email protected] on behalf of Aaron Knister" <[email protected] on behalf of [email protected]> wrote: >Simon, > >Does that mean node classes don't work the way individual node names do >with the "-i/-I" options? > >-Aaron > >On 10/10/17 8:30 AM, Simon Thompson (IT Research Support) wrote: >> Yes, but obviously only when you recycle mmfsd on the node after adding >>it >> to the node class, e.g. page pool cannot be changed online. >> >> We do this all the time, e.g. We have nodes with different IB >> fabrics/cards in clusters, so use mlx4_0/... And mlx5/... And have >>classes >> for (e.g.) "FDR" and "EDR" nodes. (different fabric numbers in different >> DCs etc) >> >> Simon >> >> On 10/10/2017, 13:04, "[email protected] on >>behalf >> of [email protected]" <[email protected] on >> behalf of [email protected]> wrote: >> >>> So when a node is added to the node class, my defaults" will be >>>applied? >>> If so,excellent. Thanks >>> >>> >>> Original Message >>> From: [email protected] >>> Sent: October 10, 2017 8:02 AM >>> To: [email protected] >>> Reply-to: [email protected] >>> Subject: Re: [gpfsug-discuss] changing default configuration values >>> >>> Use mmchconfig and change the defaults, and then have a node class for >>> "not the defaults"? >>> >>> Apply settings to a node class and add all new clients to the node >>>class? >>> >>> Note there was some version of Scale where node classes were enumerated >>> when the config was set for the node class, but in (4.2.3 at least), >>>this >>> works as expected, I.e. The node class is not expanded when doing >>> mmchconfig -N <nodeclass> >>> >>> Simon >>> >>> On 10/10/2017, 10:49, "[email protected] on >>>behalf >>> of [email protected]" <[email protected] >>>on >>> behalf of [email protected]> wrote: >>> >>>> So, I think brings up one of the slight frustrations 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" >>>> nodes need to have my defaults.. I just have to remember to extended >>>>the >>>> changes in as new nodes are brought into the cluster. >>>> >>>> Is there a way to accomplish this? >>>> Thanks >>>> >>>> Original Message >>>> From: [email protected] >>>> Sent: October 9, 2017 2:56 PM >>>> To: [email protected] >>>> Reply-to: [email protected] >>>> Subject: Re: [gpfsug-discuss] changing default configuration values >>>> >>>> Thanks! Good to know. >>>> >>>> On 10/6/17 11:06 PM, IBM Spectrum Scale wrote: >>>>> 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 the node override again. >>>>> >>>>> >>>>> Regards, The Spectrum Scale (GPFS) team >>>>> >>>>> >>>>> >>>>>---------------------------------------------------------------------- >>>>>-- >>>>> - >>>>> ----------------------------------------- >>>>> If you feel that your question can benefit other users of Spectrum >>>>> Scale >>>>> (GPFS), then please post it to the public IBM developerWroks Forum at >>>>> >>>>> >>>>>https://www.ibm.com/developerworks/community/forums/html/forum?id=1111 >>>>>11 >>>>> 1 >>>>> 1-0000-0000-0000-000000000479. >>>>> >>>>> >>>>> If your query concerns a potential software error in Spectrum Scale >>>>> (GPFS) and you have an IBM software maintenance contract please >>>>>contact >>>>> 1-800-237-5511 in the United States or your local IBM Service Center >>>>>in >>>>> other countries. >>>>> >>>>> The forum is informally monitored as time permits and should not be >>>>> used >>>>> for priority messages to the Spectrum Scale (GPFS) team. >>>>> >>>>> Inactive hide details for Aaron Knister ---10/06/2017 06:30:20 >>>>>PM---Is >>>>> there a way to change the default value of a configuratiAaron Knister >>>>> ---10/06/2017 06:30:20 PM---Is there a way to change the default >>>>>value >>>>> of a configuration option without overriding any overrid >>>>> >>>>> From: Aaron Knister <[email protected]> >>>>> To: gpfsug main discussion list <[email protected]> >>>>> Date: 10/06/2017 06:30 PM >>>>> Subject: [gpfsug-discuss] changing default configuration values >>>>> Sent by: [email protected] >>>>> >>>>> >>>>> >>>>>---------------------------------------------------------------------- >>>>>-- >>>>> >>>>> >>>>> >>>>> 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 way to then set the default value of foo to qux without >>>>> changing the value of foo for nodes n001 and n002? >>>>> >>>>> -Aaron >>>>> >>>>> -- >>>>> Aaron Knister >>>>> NASA Center for Climate Simulation (Code 606.2) >>>>> Goddard Space Flight Center >>>>> (301) 286-2776 >>>>> _______________________________________________ >>>>> gpfsug-discuss mailing list >>>>> gpfsug-discuss at spectrumscale.org >>>>> >>>>> >>>>>https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman >>>>>_l >>>>> i >>>>> >>>>>stinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=IbxtjdkPAM >>>>>2S >>>>> b >>>>> >>>>>on4Lbbi4w&m=PvuGmTBHKi7CNLU4X2GzUXkHzzezwTSrL4EdgwI0wrk&s=ma-IogZTBRL1 >>>>>1_ >>>>> 4 >>>>> zp2l8JqWmpHajoLXubAPSIS3K7GY&e= >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> gpfsug-discuss mailing list >>>>> gpfsug-discuss at spectrumscale.org >>>>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss >>>>> >>>> >>>> -- >>>> Aaron Knister >>>> NASA Center for Climate Simulation (Code 606.2) >>>> Goddard Space Flight Center >>>> (301) 286-2776 >>>> _______________________________________________ >>>> gpfsug-discuss mailing list >>>> gpfsug-discuss at spectrumscale.org >>>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss >>>> _______________________________________________ >>>> gpfsug-discuss mailing list >>>> gpfsug-discuss at spectrumscale.org >>>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss >>> >>> _______________________________________________ >>> gpfsug-discuss mailing list >>> gpfsug-discuss at spectrumscale.org >>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss >>> _______________________________________________ >>> gpfsug-discuss mailing list >>> gpfsug-discuss at spectrumscale.org >>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss >> >> _______________________________________________ >> gpfsug-discuss mailing list >> gpfsug-discuss at spectrumscale.org >> http://gpfsug.org/mailman/listinfo/gpfsug-discuss >> > >-- >Aaron Knister >NASA Center for Climate Simulation (Code 606.2) >Goddard Space Flight Center >(301) 286-2776 >_______________________________________________ >gpfsug-discuss mailing list >gpfsug-discuss at spectrumscale.org >http://gpfsug.org/mailman/listinfo/gpfsug-discuss _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
