perfsonar-announce - [perfsonar-announce] Upcoming Limit Configuration Changes in perfSONAR 5.0
Subject: perfSONAR Announcements
[perfsonar-announce] Upcoming Limit Configuration Changes in perfSONAR 5.0
- From: Mark Feit <>
- To: "" <>, "" <>
- Subject: [perfsonar-announce] Upcoming Limit Configuration Changes in perfSONAR 5.0
- Date: Tue, 31 May 2022 16:48:58 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=BYWewj99JrdecffFjFWnvf5IyYd8/gQojEjOO07UW5I=; b=QrqiFtdKr0y+xujEZK3IACHyC1Hep63Y9mp6HQVwBR6Vim1lkFISYJ4SAfaUYjiLV9L4fDKKnQAWrg4tt4vFr5flAKNAqit7DnZdds34LlAbTnuSLJeo7GPAw91Wkam1PQfIvCjJENaTv0Ul2Ne5kf6Z1EguuuO9neEn3z3Gk8tA8t79jKH2DcUEDZNJg3XG6kvjQQGDE+yJitjEDGiKcqtP5STrM8WMa4TltxtOynuxmnId8P0ucP4ScHi0MT2J7oy94nFL1KZ9/e2jjrjFt8Ci0Z+q2nv05pRIQJP6Bvidlnqy169um1i0jtvjsFL0W1kJZWwEp11k+k5opocLDw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RjYH7w4ytEvoBFsUORwegYjrvtRo0bjPGw6WlpW/3zDi0oJxNrlK7Vaw/iKfH1OAhEZbsmBFaXdLDeKtSt3f+hvKRqzaDzb07U6grehRRStRxmDwNo4eaRm9XL9I8JQrqOCx3kaqASY3OYgY6ugMe79p6+FZuIAr8Za8KniLfSYS8fh5YXbMfk7V9fux18ImaghCEvO594jte+VtGmL3SUqpEIr5FECjGX4KqW6Le34Oxs5xDzEhsIaqymVTGbnU3Dk1Yo+lhSeRObvq9wz8zzqUj//2V3ATqzLfF3fY/6R1kmdoIFIzYkqBWkq3VrTUaknn+uI0+5h3HMJ3l3pSEQ==
Now that perfSONAR 5.0 is in beta, this is an important notice for those using a customized pScheduler limit configuration file (/etc/pscheduler/limits.conf):
In perfSONAR 4.4, we deprecated the “test” limit type in favor of the “jq” limit type. In 5.0, all support for the “test” limit type has been removed. If you are using a custom limit configuration that uses the “test” limit (either because it was based on the configuration shipped with an earlier version the toolkit or you wrote one yourself), its use must be discontinued prior to upgrading to 5.0. Failure to do so will cause your perfSONAR nodes to stop working when the software is upgraded.
If you are running the perfSONAR Toolkit bundle and have not customized the limit configuration, no action is required. The upgrade to 5.0 will install a compatible limit configuration.
If your limit configuration is based on the one that shipped with the toolkit, there have been three changes made since the last release that should be incorporated:
Any other customizations using the “test” limit must be changed to use the “jq” limit with a jq script that provides the equivalent behavior. Here are some useful links If you are unfamiliar with the “jq” limit or jq itself:
Finally, because changes to eliminate deprecated limits are compatible with the current production release, there is no need to wait until 5.0 is released. We strongly recommend making, testing and deploying these changes beforehand to reduce or eliminate any related problems.
If you have questions, please post to the user list at .
- [perfsonar-announce] Upcoming Limit Configuration Changes in perfSONAR 5.0, Mark Feit, 05/31/2022
Archive powered by MHonArc 2.6.24.