Re: [HTCondor-users] persistency of generic ClassAds

[Thomas Hartmann <thomas.hartmann@xxxxxxx>]

Hi again,

a related question:

The lifetime of an added ClassAds is ruled by CLASSAD_LIFETIME /
UPDATE_INTERVAL afais. Can I couple a ClassAds lifetime with another,
i.e., to keep a ad around as long as node's master or so updates another
ad / contacts the collector?
Or would it be reasonable just to check for absent ads as well?


From doc v8.5/3.10.2
> "If True, the machine ClassAd will be saved in a persistent manner and
be marked as absent;..."
I would assume, that absent ClassAds are written to disk. Thus, they
would also survive a reboot of the collector - I guess - or? (answering
the second one of my previous questions)

Cheers and thanks,
  Thomas

On 2016-07-27 12:32, Thomas Hartmann wrote:
> Hi all,
> 
> I some questions about their persistency
> 
>  - afais ClassAd key:value pairs cannot be updated individually but the
> whole set has to be rewritten, or?
>    I.e., after I set some generic ClassAds [1,2], I updated(?) the
> generic set setting only one key-value-pair and followingly all
> previously set but not mentioned again ClassAds became undefined [3,4]
> 
>  - how persistent are generic ClassAds? Will they survive a reboot of
> the Collector, i.e., are they written to disk somewhere?
> 
>  - can I start with default values set by a node?
>    I.e., Since I found no matching hits in a quick google search, I
> already tried (without success), if one can set ClassAds similar to
> adding daemon attributes [5]?
>    - would that make actually sense? Or would any manually set ClassAd
> be overwritten again the next time a node's master speaks with the
> collector?
> 
> Cheers and thanks,
>   Thomas
> 
> [1]
>> test_batch0930.ad
> MyType = "Generic"
> TestKernel = "2.3.5"
> TestDoStuff = True
> TestStatusThing = "bar"
> Name = "batch0930.desy.de"
> Machine = "batch0930.desy.de"
> 
> [2]
>> condor_status -generic -constraint 'regexp(".*batch0930.*", Name)' -long
> LastHeardFrom = 1469614306
> AuthenticatedIdentity = "unauthenticated@unmapped"
> MyAddress = "<131.169.56.33:0>"
> UpdatesHistory = "00000000000000000000000000000000"
> UpdatesLost = 0
> UpdatesSequenced = 0
> TestStatusThing = "bar"
> Machine = "batch0930.desy.de"
> TestDoStuff = true
> TestKernel = "2.3.5"
> UpdatesTotal = 6
> Name = "batch0930.desy.de"
> MyType = "Generic"
> 
> [3]
>> test_batch0930_2.ad
> MyType = "Generic"
> TestStatusThing = "ALERT"
> Name = "batch0930.desy.de"
> Machine = "batch0930.desy.de"
> 
> 
> [4]
>> condor_status -generic -constraint 'regexp(".*batch0930.*\.desy\.de",
> Name)' -af name TestStatusThing TestDoStuff TestKernel
> batch0930.desy.de ALERT undefined undefined
> 
> 
> [5] # (GENERIC_ATTRS certainly wrong...)
>> /etc/condor/config.d/99test.conf
> GENERIC_TestKernel = False
> GENERIC_TestDoStuff = False
> GENERIC_TestStatusThing = False
> TestKernel = False
> TestDoStuff = False
> TestStatusThing = False
> GENERIC_ATTRS = TestKernel, TestDoStuff, TestStatusThing, $(GENERIC_ATTRS)
> GENERIC.SETTABLE_ATTRS_ADMINISTRATOR = TestKernel, TestDoStuff,
> TestStatusThing, $(GENERIC.SETTABLE_ATTRS_ADMINISTRATOR)
> 
> 
> 
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> 
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature