Hi,
Seems like it is proper now.
To confirm if it is proper below is the briefing.
1) SU states
Run the command "amf-state su" on any opensaf running node. you
should see this.
safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
2) Comp state :
Run the command "amf-state comp" on any opensaf running node. You should
see this.
safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
saAmfCompOperState=ENABLED(1)
saAmfCompPresenceState=INSTANTIATED(3)
saAmfCompReadinessState=IN-SERVICE(2)
safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
saAmfCompOperState=ENABLED(1)
saAmfCompPresenceState=INSTANTIATED(3)
saAmfCompReadinessState=IN-SERVICE(2)
If you see the above states in your system, that means AMF has spawned a
process of your application properly.
If the states are looking as above and still you don't see a process in
the 'ps -e | grep amf_demo', this means that the script
'/opt/amf_demo_script' was successfully invoked and the exit status of
the script is '0/zero/true'. But the reason for not seeing a process
depends on your application now. Please debug your application.
Thanks
surender.
On Saturday 10 January 2015 05:21 AM, Johnson, Charles wrote:
> I was looking in the wrong node, after looking in SC-1 and SC-2 I saw
> this in /var/log/messages:
> Jan 9 10:02:06 metabox-fedora19-dl365g3-7 osafimmnd[11809]: NO Ccb 2
> COMMITTED (immcfg_metabox-fedora19-dl365g3-7.u.hpl.hp.com_15370)
> Jan 9 10:04:02 metabox-fedora19-dl365g3-7 osafamfnd[11915]: NO
> 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Presence State
> UNINSTANTIATED => INSTANTIATING
> Jan 9 10:04:02 metabox-fedora19-dl365g3-7 amf_demo[15566]:
> 'safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' started
> Jan 9 10:04:02 metabox-fedora19-dl365g3-7 osafamfnd[11915]: NO
> 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING
> => INSTANTIATED
> Jan 9 10:04:02 metabox-fedora19-dl365g3-7 amf_demo[15566]: Registered
> with AMF and HC started
> Jan 9 10:04:48 metabox-fedora19-dl365g3-7 osafamfnd[11915]: NO
> Assigning 'safSi=AmfDemo,safApp=AmfDemo1' STANDBY to
> 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
> Jan 9 10:04:48 metabox-fedora19-dl365g3-7 amf_demo[15566]: CSI Set -
> add 'safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1' HAState Standby
> Jan 9 10:04:48 metabox-fedora19-dl365g3-7 osafamfnd[11915]: NO
> Assigned 'safSi=AmfDemo,safApp=AmfDemo1' STANDBY to
> 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
> Jan 9 10:06:38 metabox-fedora19-dl365g3-7 osafimmnd[11809]: NO Ccb 3
> COMMITTED (immcfg_metabox-fedora19-dl365g3-7.u.hpl.hp.com_15798)
> Jan 9 10:07:28 metabox-fedora19-dl365g3-7 osafimmnd[11809]: NO
> Implementer connected: 20
> (safSmfCampaign=campaign_single_node,safApp=safSmfService) <0, 2080f>
> Jan 9 10:07:28 metabox-fedora19-dl365g3-7 osafimmnd[11809]: NO
> Implementer connected: 21 (safSmfProc=SingleStepComp) <0, 2080f>
> Jan 9 10:07:28 metabox-fedora19-dl365g3-7 osafimmnd[11809]: NO
> Implementer disconnected 21 <0, 2080f> (safSmfProc=SingleStepComp)
> Jan 9 10:07:28 metabox-fedora19-dl365g3-7 osafimmnd[11809]: NO
> Implementer disconnected 20 <0, 2080f>
> (safSmfCampaign=campaign_single_node,safApp=safSmfService)
> I don’t know if this is right, but at least there is something going on.
> Charlie …
> _____________________________________________
> *From:* Johnson, Charles
> *Sent:* Friday, January 09, 2015 1:40 PM
> *To:* 'surender'; [email protected]
> *Subject:* RE: [users] FW: smf on opensaf-4.4.0 ...
> After doing a "sudo yum install rsh.x86_64" and trying again, I got
> this out of your command sequence from /var/log/messages:
> Jan 9 03:37:35 metabox-fedora19-dl365g3-4 osafimmnd[25208]: NO Ccb 2
> COMMITTED (immcfg_metabox-fedora19-dl365g3-4.u.hpl.hp.com_26994)
> Jan 9 03:41:37 metabox-fedora19-dl365g3-4 osafimmnd[25208]: NO Ccb 3
> COMMITTED (immcfg_metabox-fedora19-dl365g3-4.u.hpl.hp.com_27401)
> Jan 9 03:41:49 metabox-fedora19-dl365g3-4 osafimmnd[25208]: NO
> Implementer connected: 20
> (safSmfCampaign=campaign_single_node,safApp=safSmfService) <0, 2080f>
> Jan 9 03:41:49 metabox-fedora19-dl365g3-4 osafimmnd[25208]: NO
> Implementer connected: 21 (safSmfProc=SingleStepComp) <0, 2080f>
> Jan 9 03:41:49 metabox-fedora19-dl365g3-4 osafimmnd[25208]: NO
> Implementer disconnected 21 <0, 2080f> (safSmfProc=SingleStepComp)
> Jan 9 03:41:49 metabox-fedora19-dl365g3-4 osafimmnd[25208]: NO
> Implementer disconnected 20 <0, 2080f>
> (safSmfCampaign=campaign_single_node,safApp=safSmfService)
> I noticed that when you do "ps -ef | grep amf_demo" in step seven, you
> get a line from the "amf_demo" in the grep process command (in any
> system), so I changed that to a "ps -e | grep amf_demo" (I hope that
> is right.)
> Using that command I didn't see anything running.
> Charlie …
> -----Original Message-----
> From: surender [_mailto:[email protected]_]
> Sent: Thursday, January 08, 2015 3:26 AM
> To: Johnson, Charles; [email protected]_
> <mailto:[email protected]>
> Subject: FW: [users] FW: smf on opensaf-4.4.0 ...
> Hi,
> This is not proper. The distro/OS which you are running doesn't have
> rsh,rlogin,rcp commands available.
> The file '/usr/lib64/opensaf/smf-backup-create' uses these linux
> commands. Unavailability of these has also been reported in community too.
> To get it work you have three options
> 1) Install the package 'rsh' for your distro. For suse, the package
> name is 'rsh-0.17-706.18.1'
> or
> 2)
> export RSH=`which ssh`
> export RCP=`which scp`
> or
> 3) replace 'rsh,rcp' with available commands within the script '
> /usr/lib64/opensaf/smf-backup-create' with 'ssh,scp' respectively.
> i.e at line no 96 replace the below lines as
> rsh=${RSH:-rsh}
> rcp=${RCP:-rcp}
> to
> rsh=${RSH:-ssh}
> rcp=${RCP:-scp}
> Note : Preferred is to install the package Thanks surender
> -----Original Message-----
> From: Johnson, Charles [mailto:[email protected]]
> Sent: Thursday, January 08, 2015 1:07 AM
> To: surender; [email protected]
> <mailto:[email protected]>
> Subject: Re: [users] FW: smf on opensaf-4.4.0 ...
> What I got from this in /var/log/messages was:
> Jan 7 11:10:34 metabox-fedora19-dl365g3-7 osafimmnd[9357]: NO Ccb 2
> COMMITTED (immcfg_metabox-fedora19-dl365g3-7.u.hpl.hp.com_10421)
> Jan 7 11:11:13 metabox-fedora19-dl365g3-7 osafamfnd[9465]: NO
> 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Presence State
> UNINSTANTIATED => INSTANTIATING Jan 7 11:11:13
> metabox-fedora19-dl365g3-7 amf_demo[10501]:
> 'safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' started Jan
> 7 11:11:13 metabox-fedora19-dl365g3-7 osafamfnd[9465]: NO
> 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING
> => INSTANTIATED Jan 7 11:11:13 metabox-fedora19-dl365g3-7
> amf_demo[10501]: Registered with AMF and HC started Jan 7 11:11:26
> metabox-fedora19-dl365g3-7 osafamfnd[9465]: NO Assigning
> 'safSi=AmfDemo,safApp=AmfDemo1' STANDBY to
> 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
> Jan 7 11:11:26 metabox-fedora19-dl365g3-7 amf_demo[10501]: CSI Set -
> add 'safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1' HAState Standby
> Jan 7 11:11:26 metabox-fedora19-dl365g3-7 osafamfnd[9465]: NO
> Assigned 'safSi=AmfDemo,safApp=AmfDemo1' STANDBY to
> 'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
> Jan 7 11:11:37 metabox-fedora19-dl365g3-7 osafimmnd[9357]: NO Ccb 3
> COMMITTED (immcfg_metabox-fedora19-dl365g3-7.u.hpl.hp.com_10545)
> Jan 7 11:11:52 metabox-fedora19-dl365g3-7 osafimmnd[9357]: NO
> Implementer connected: 20
> (safSmfCampaign=campaign_single_node,safApp=safSmfService) <614,
> 2070f> Jan 7 11:11:52 metabox-fedora19-dl365g3-7 osafsmfd[9502]: NO
> CAMP: Wait for RDA role to be Active Jan 7 11:11:52
> metabox-fedora19-dl365g3-7 osafsmfd[9502]: NO CAMP: The RDA role is
> now Active, continue campaign Jan 7 11:11:52
> metabox-fedora19-dl365g3-7 osafimmnd[9357]: NO Implementer connected:
> 21 (safSmfProc=SingleStepComp) <615, 2070f> Jan 7 11:11:52
> metabox-fedora19-dl365g3-7 osafsmfd[9502]: NO
> SmfProcedureThread::getImmProcedure, IMM data for procedure
> safSmfProc=SingleStepComp,safSmfCampaign=campaign_single_node,safApp=safSmfService
>
> not found Jan 7 11:11:52 metabox-fedora19-dl365g3-7 osafsmfd[9502]:
> NO CAMP: Start upgrade campaign safSmfCampaign=campaign_single_comp
> Jan 7 11:11:52 metabox-fedora19-dl365g3-7 osafsmfd[9502]: NO CAMP:
> Check SMF repository safSmfCampaign=campaign_single_comp
> Jan 7 11:11:52 metabox-fedora19-dl365g3-7 osafsmfd[9502]: NO CAMP:
> Check bundles to install and remove.
> Jan 7 11:11:52 metabox-fedora19-dl365g3-7 osafsmfd[9502]: NO CAMP:
> Calling configured smfBundleCheckCmd for each bundle existing in IMM,
> to be installed or removed by the campaign Jan 7 11:11:52
> metabox-fedora19-dl365g3-7 osafsmfd[9502]: NO CAMP: executed
> callbackAtBackup successfully in the campaign
> safSmfCampaign=campaign_single_comp
> Jan 7 11:11:52 metabox-fedora19-dl365g3-7 osafsmfd[9502]: NO CAMP:
> Create system backup safSmfCampaign=campaign_single_comp
> Jan 7 11:11:52 metabox-fedora19-dl365g3-7 smf-backup-create: ERROR
> (): Not found [rsh] Jan 7 11:11:52 metabox-fedora19-dl365g3-7
> osafsmfd[9502]: NO CAMP: Backup create command
> /usr/local/lib/opensaf/smf-backup-create failed 1 Jan 7 11:11:52
> metabox-fedora19-dl365g3-7 osafimmnd[9357]: NO Implementer
> disconnected 21 <615, 2070f> (safSmfProc=SingleStepComp) Jan 7
> 11:11:52 metabox-fedora19-dl365g3-7 osafimmnd[9357]: NO Implementer
> disconnected 20 <614, 2070f>
> (safSmfCampaign=campaign_single_node,safApp=safSmfService)
> Does this look like it worked properly?
> -----Original Message-----
> From: surender [mailto:[email protected]]
> Sent: Friday, December 19, 2014 2:41 AM
> To: Johnson, Charles; [email protected]
> <mailto:[email protected]>
> Subject: Fwd: FW: [users] smf on opensaf-4.4.0 ...
> Hi,
> The below briefs you to run a sample without using UML environment.
> Pre-requisites w.r.t smf:
> Min two nodes ( preferably SC-1 and SC-2 ) with opensaf running.
> 1) mkdir /hostfs ( this directory is mandatory )
> 2) edit /hostfs/smf.rc and include below lines
> REPOSITORY=/hostfs/repo
> SMF_BACKUP_DIR=/hostfs/smfbackup
> SMFREPOSITORY=/hostfs
> ( Note : to know what the above variables mean, read
> /usr/lib64/opensaf/smf-* files )
> 3) Install the samples using rpm package or make install( you might
> have already figured it out ).
> The samples usually get installed, for rpm pkg, in directory
> /usr/share/opensaf/samples
> 4) cd /usr/share/opensaf/samples/ ; ./bootstrap ; ./configure; make ;
> make install. This should install the amf demo file in /opt/amf_demo
> 5) cd /usr/share/opensaf/samples/amf/sa_aware ; immcfg -f
> AppConfig-2N.xml ;
> 6) amf-adm unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1; amf-adm
> unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
> 7) amf-adm unlock-in safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1; amf-adm
> unlock safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
> You should see a process running i.e amf_demo application ( ps -ef |
> grep amf_demo ). SMF will upgrade this demo to new version. The below
> explains how.
> 8) cp
> /usr/share/opensaf/samples/smfsv/campaigns/campaign_single_node.xml
> /hostfs/
> 9) cd /usr/share/opensaf/samples/smfsv/; cp offline_* online_* /hostfs
> 10) One edit has to be done in xml file
> /hostfs/campaign_single_node.xml to work.
> Replace all "safVersion=4.0.0" to "safVersion=1" in this file.
> Replace will happen in two places.
> 11) Now Ready for execution
> a) Create object ( taken from description in xml/campaign file )
> immcfg -c SaSmfCampaign -a
> saSmfCmpgFileUri=/hostfs/campaign_single_node.xml
> safSmfCampaign=campaign_single_node,safApp=safSmfService
> b) Execute as
> immadm -o 1 safSmfCampaign=campaign_single_node,safApp=safSmfService
> Note : Put a tail -f on syslog to see the progress.
> Thanks
> surender.
> -----Original Message-----
> From: Johnson, Charles [mailto:[email protected]]
> Sent: 19 December 2014 01:44
> To: [email protected]
> <mailto:[email protected]>
> Subject: [users] smf on opensaf-4.4.0 ...
> I have had success getting opensaf to install and run reliably on both
> rhel 5&6 and fedora19 on various sizes of native clusters (thanks to
> the details present in the opensaf README and 00-README.conf files ...
> Thank you!)
> We got a fault tolerant service to work and take over in manner
> similar to the VLCKvm demo I got from Jonas Arndt (Thank you, Jonas et
> al!)
> Our system has many fault tolerant components in it and hacking the
> imm.xml each time seemed not to be a good plan for deploying software
> on multiple clusters in multiple configurations.
> It was thought that smf would be the best way, by layering in
> campaign.xml files in order into the installing perl script.
> I could not seem to get the smf samples to install or run on native
> systems, they build, but the installation is a bit of a mystery (the
> README there doesn't give hints about $REPOSITORY and the like: what
> these things are and how to set them up.)
> I reached out through Jonas to find out if anyone knew how to install
> the smf samples and get things working.
> An educator he knows suggested seeing if installing the UML simulator
> demo would be instructive.
> I noticed it had been removed from the tools directory in the release
> tarball: when I found this to be the case for the opensaf tests, I
> went to the mercurial archive and grabbed the snapshot of the same
> release that had the tests present, but after installing, building and
> trying to get them working, I found out from Jonas that they had
> fallen into disrepair and no longer worked ... so they had been
> removed from the release tarball for that reason.
> So, I tried again and took the 4.4.0 release snapshot from the
> mercurial archive that had the UML demo in it and installed that:
> after getting that to build successfully on fedora19, I went to run
> it, following the instructions carefully and setting all the variables
> appropriately ... but it came up in five windows each looping through
> the service command to start opensafd over and over as if they were
> autistic and not talking to each other.
> I thought maybe some kind of vlan was missing and ran the one from
> libvirt and qemu/kvm ... nothing.
> So, I should ask, have the UML tools also fallen into disrepair, and
> that's why they are not in the release tarball?
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from
> Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration &
> more Get technology previously reserved for billion-dollar
> corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> Opensaf-users mailing list
> [email protected]
> <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/opensaf-users
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media,
> is your hub for all things parallel software development, from weekly
> thought leadership blogs to news, videos, case studies, tutorials and
> more. Take a look and join the conversation now.
> http://goparallel.sourceforge.net
> _______________________________________________
> Opensaf-users mailing list
> [email protected]
> <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/opensaf-users
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
vanity: www.gigenet.com
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
