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
