Hi,

Some more answers (to add on top of ingvar's response):

> just lock SU, or node? What will be the proper order going through the

Typically starting with the controllers first and proceeding to the payloads.

> nodes? Will OpenSAF tolerate newer version in some nodes, old version
> in other nodes?

Upgradeability is a requirement for all OpenSAF releases in 4.* stream.
So, during the course of an upgrade path say from 4.4 to 4.5, there would 
ofcourse be a transient phase when one node is running 4.5 and another 4.4
versions. 

Thanks,
Mathi.

----- [email protected] wrote:

> Hi,
> first you must create a swBundle which contain the new version of the
> software you want to update on the nodes. In your case the OpenSAF
> software.
> A software bundle contain commands which will be invoked by SMF on the
> node where the swBundle shall be installed. 
> OpenSAF software requires to be restarted so I always use a rolling
> upgrade where the nodes are rebooted after installation of the
> swBundle.
> A software bundle which requires reboot to be activated must install
> itself on the node when the offLineInstall command is invoked from
> SMF.
> SMF will reboot the node if any bundle listed to be installed by the
> procedure have the saSmfBundleInstallOfflineScope set to value 4
> (Execution environment).
> 
> The new component version type must be defined and AMF model updated.
> 
> Look in the
> opensaf-staging/samples/smfsv/campaigns/campaign_rolling_nodes.xml 
> 
> In this sample campaign the "bundleA" requires reboot to install and
> the AMF model is maintained for this component.
> When upgrading OpenSAF there are a lot more components needed to be
> listed in the campaign.
> 
> opensaf-staging/samples/smfsv/README contain some information. I don't
> know if the samples still work, you may have to adjust some component
> revisions from e.g. 4.0.0 to 1.
> 
> I think you can also upgrade OpenSAF manually without using SMF by
> just stopping OpenSAF, install new rpm's and start OpenSAF. Node by
> node.
> The UML directory shall always be created at
> opensaf-staging/tools/cluster_sim_uml
> 
> Thanks
> Ingvar
> 
> -----Original Message-----
> From: Shu Wang [mailto:[email protected]] 
> Sent: den 7 april 2015 23:10
> To: Shu Wang; [email protected]
> Subject: Re: [users] How to upgrade OpenSAF
> 
> Is there anybody who had done live upgrade on OpenSAF before? Can you
> share some experience? I have an OpenSAF cluster, I want to upgrade
> OpenSAF to a newer version while keep the cluster up and running.
> Thank you!
> 
> Shu Wang | Senior Analyst | +1(407)708-5117 or x3917|
> www.NetCracker.com Proven Partner to Communications Service Providers
> 
> From: Shu Wang
> Sent: Friday, April 03, 2015 10:02 AM
> To: '[email protected]'
> Subject: How to upgrade OpenSAF
> 
> How do I upgrade OpenSAF from one OpenSAF release to another while
> keep the cluster up and running?
> 
> 1. Can I use SMF upgrade campaign? If yes, is there a sample campaign
> file provided by OpenSAF? Is it one of the sample files in
> samples/smfsv? If yes, which one?
> 2. Is it possible doing the upgrade without using SMF framework? If I
> do it node by node, do I have to stop OpenSAF on the node or I can
> just lock SU, or node? What will be the proper order going through the
> nodes? Will OpenSAF tolerate newer version in some nodes, old version
> in other nodes?
> 3. The sample files in samples/smfsv refer to UML environment. But I
> can't find tools/cluster_sim_uml directory. Is it part of OpenSAF
> package? Is there any flag required to get this directory when I
> configure and build OpenSAF?
> 
> Thank you!
> 
> 
> Shu Wang | Senior Analyst | +1(407)708-5117 or x3917|
> www.NetCracker.com<http://www.NetCracker.com>
> Proven Partner to Communications Service Providers
> 
> 
> 
> 
> ________________________________
> The information transmitted herein is intended only for the person or
> entity to which it is addressed and may contain confidential,
> proprietary and/or privileged material. Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance
> upon, this information by persons or entities other than the intended
> recipient is prohibited. If you received this in error, please contact
> the sender and delete the material from any computer.
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop
> your own process in accordance with the BPMN 2 standard Learn Process
> modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Opensaf-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensaf-users
> 
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Opensaf-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensaf-users

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users

Reply via email to