Re: [users] Procedure to Update OpenSAF Binary(/ies) on a Live Running System

2018-03-13 Thread Anders Widell

Hi!

I suppose the standard procedure for upgrades is a rolling upgrade over 
nodes using SMF. I.e. upgrade the nodes in the cluster one at a time. 
For each node, do something like this:


1. If it is a system controller node, make sure that it is note the 
active controller. If it is, perform an si-swap to make it standby.


2. Lock the node.

3. Stop the OpenSAF service

4. Upgrade the OpenSAF binaries (recommended to use RPM)

5. Reboot the node (recommended, but not strictly necessary)

6. Start the OpenSAF service (if not already started due to reboot)

7. Unlock the node.

regards,

Anders Widell


On 03/13/2018 06:01 AM, Saurabh Pandey wrote:

Can anyone check and let us know if there is any standard procedure available 
for patching?

Regards,
Saurabh

From: Kapil Gokhale
Sent: Monday, March 12, 2018 4:38 PM
To: opensaf-users@lists.sourceforge.net
Cc: Nivrutti Kale ; Saurabh Pandey 

Subject: Procedure to Update OpenSAF Binary(/ies) on a Live Running System

Hi All

Query:
How to update OpenSAF binary/binaries in a live running system with minimal 
hindrance(downtime).
What steps to follow for such an update to be foolproof?

Scenario:
We have openSAF 4.5.0 deployed at customer site. An issue related to Ticket 
[#1475] has been observed.
This ticket has been fixed in 4.5.2 however we do not want to upgrade system to 
4.5.2, instead want to apply patch related to Ticket [#1475].
Since patched binaries have to be updated finally at customer site, we need a 
foolproof procedure which also guarantees minimal downtime.

A general answer (irrespective of specific Ticket #1475) is welcome too.

Regards
Kapil Gokhale


This e-mail message may contain confidential or proprietary information of 
Mavenir Systems, Inc. or its affiliates and is intended solely for the use of 
the intended recipient(s). If you are not the intended recipient of this 
message, you are hereby notified that any review, use or distribution of this 
information is absolutely prohibited and we request that you delete all copies 
in your control and contact us by e-mailing to secur...@mavenir.com. This 
message contains the views of its author and may not necessarily reflect the 
views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor 
email messages, but make no representation that such messages are authorized, 
secure, uncompromised, or free from computer viruses, malware, or other 
defects. Thank You
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users


Re: [users] Procedure to Update OpenSAF Binary(/ies) on a Live Running System

2018-03-13 Thread Saurabh Pandey
Can anyone check and let us know if there is any standard procedure available 
for patching?

Regards,
Saurabh

From: Kapil Gokhale
Sent: Monday, March 12, 2018 4:38 PM
To: opensaf-users@lists.sourceforge.net
Cc: Nivrutti Kale ; Saurabh Pandey 

Subject: Procedure to Update OpenSAF Binary(/ies) on a Live Running System

Hi All

Query:
How to update OpenSAF binary/binaries in a live running system with minimal 
hindrance(downtime).
What steps to follow for such an update to be foolproof?

Scenario:
We have openSAF 4.5.0 deployed at customer site. An issue related to Ticket 
[#1475] has been observed.
This ticket has been fixed in 4.5.2 however we do not want to upgrade system to 
4.5.2, instead want to apply patch related to Ticket [#1475].
Since patched binaries have to be updated finally at customer site, we need a 
foolproof procedure which also guarantees minimal downtime.

A general answer (irrespective of specific Ticket #1475) is welcome too.

Regards
Kapil Gokhale


This e-mail message may contain confidential or proprietary information of 
Mavenir Systems, Inc. or its affiliates and is intended solely for the use of 
the intended recipient(s). If you are not the intended recipient of this 
message, you are hereby notified that any review, use or distribution of this 
information is absolutely prohibited and we request that you delete all copies 
in your control and contact us by e-mailing to secur...@mavenir.com. This 
message contains the views of its author and may not necessarily reflect the 
views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor 
email messages, but make no representation that such messages are authorized, 
secure, uncompromised, or free from computer viruses, malware, or other 
defects. Thank You
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users