perfsonar-user - Re: [perfsonar-user] Direct upgrade from 4.0 to 4.2
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Brian Candler <>
- To: Mark Feit <>, "" <>
- Subject: Re: [perfsonar-user] Direct upgrade from 4.0 to 4.2
- Date: Sun, 1 Sep 2019 18:53:44 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject:to :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sasl; b=Ntq1SM ut38st8uUh1h9hCw2NIhICXoF1vOBfveostxrvCGvCobFFp624KZYtD09WMQ4wwz MfY8yzkV0/1pvYIKT+v3QGYe8BaGJllRBZwl9HYUrF6oo92KR0nl7aIRiRKHsNPy k3fKfdDzwg3wE5/vECBkNMRnpWgmWO9ZQXfBI=
On 31/08/2019 18:05, Mark Feit wrote:
That should be no problem. pScheduler can self-upgrade from the earliest
release and pSConfig should take over your old MeshConfig setup.
(I realise that I'll lose the bwctl backward compatibility - so nodes
upgraded to 4.2 won't be able to talk to remaining 4.0 nodes in the
interim. I can cope with that)
Anything 4.0 and later runs pScheduler, so all you will lose in 4.2 is the
ability to talk to 3.x systems. We stopped installing BWCTL by default in
4.1. Just make sure any ACLs you have ahead of your old nodes are configured
per our guidelines and you shouldn't notice the difference.
Excellent - thank you!
- Re: [perfsonar-user] Direct upgrade from 4.0 to 4.2, Brian Candler, 09/01/2019
Archive powered by MHonArc 2.6.19.