[Openais] Problems with OpenAis version 0.81

Steven Dake sdake at redhat.com
Thu Sep 13 13:28:24 PDT 2007


On Thu, 2007-09-13 at 10:15 +0300, Cohen-Sason Daniel-BDC021 wrote:
> Thanks Steve!
> It seems to be working! (The amf-example1)
> 
> Now we need to upgrade our code to support AMF_B.
> 
> My question is:
> Assume there are 2 components on each node. Both components should be
> running and functioning in order for a node to be considered "good".
> All 4 components (lets call them: A1, B1, A2, B2) can be active at the
> same time, and when one of the components breaks, its correspondent node
> should give up its SU.
> 
> When we used AMF_A, we registered to each component from each node. The
> component name was declared in the groups.conf file as a simple string.
> I understand that in AMF_B, it's a bit different. The full "path" of a
> component (including its SG, SU, APP, COMP) is the "name" of that
> component - Is it correct? Should my code now register to the "full"
> path?

No - register with just the component name identified in the
configuration file, not the DN name.  When the CSI is assigned it will
get a DN of the full sg/su/csi.

> 
> My second question is: Does Aisexec is the one that *must* instantiate
> our A and B services? This is want I understand from the provided
> example... or maybe this is just an example?
> 

yes aisexec forks and execs the AMF applications and runs them.  There
is no other way for the AMF apps to be started in the latest AMF code.
This is actually required of the AMF B specifications but wasn't defined
too well in the A specifications.

> Does the explanation "run the example on a cluster with 2 nodes" (from
> README.AMF) describe our system? 
> 

mostly except the example is designed to run one CSI as active and one
CSI as standby.

> Can you try to provide us a sample configuration for the example above?
> 

Well first the best way to come up with a config is to define what you
want.

First it sounds like you want 2n (which is modeled in openais via the n
+m model).  Second it sounds like you have one SG with two redundant SUs
on seperate nodes.  You want both those SUs to have 1 active CSI
(component service instantiation) for each of the two components of the
SU with no standby csi in the system?

Is that correct?

> Thank you very much.
> 
> Daniel.
> 
> P.S
> Is there a document with detailed explanation on the AMF.CONF file? I
> couldn't find it at the web.
> 

Take a look at the AMF information model in saiOverview.B0301.pdf.  We
pretty closely match that model section 5.5 page 76.

The AMF document itself explains what most of the variables do.

There is also the not so complete amf.conf man page.

Regards
-steve


> Thanks again, Daniel
> 
> 
> 
> -----Original Message-----
> From: Steven Dake [mailto:sdake at redhat.com] 
> Sent: Thursday, September 13, 2007 4:37 AM
> To: Cohen-Sason Daniel-BDC021
> Cc: openais at lists.osdl.org
> Subject: RE: [Openais] Problems with OpenAis version 0.81
> 
> few extra notes:
> 
> make sure to change your hostname in the config file back to CENTOS
> 
> Whatever the command "hostname" returns is what you want in that field
> 
> Regards
> -steve
> 
> On Wed, 2007-09-12 at 18:29 -0700, Steven Dake wrote:
> > Daniel,
> > 
> > Try this amf.conf file and clc_cli_script.
> > 
> > Essentially the healthcheck keys for the default configuration file
> are
> > invalid and also the path to clc_cli_script do not execute
> > openais-instantiate.
> > 
> > With these files 0.81 instantiates the components for me and works as
> > expected.
> > 
> > Regards
> > -steve
> > 
> > On Thu, 2007-09-13 at 00:50 +0300, Cohen-Sason Daniel-BDC021 wrote:
> > > Hi Steve.
> > > 
> > > Thanks for the quick response!
> > > I'm sorry, but I forgot to attach the log I generated.
> > > 
> > > My hostname is CENTOS, and I set this name at the saAmfNodeClmNode
> > > directive (Should it be at the safAmfNode?)
> > > 
> > > I'm also logged in as root with root group.
> > > 
> > > I verified and all the 3 files are executables with 755.
> > > 
> > > I tried to change the timeouts to 5000 and it didn't help.
> > > 
> > > Attached please find the fixed configuration files and the log.
> > > 
> > > Hope this will be help you to find out the problem.
> > > 
> > > Thanks,
> > > 
> > > Daniel.
> > > 
> > > 
> > > -----Original Message-----
> > > From: Steven Dake [mailto:sdake at redhat.com] 
> > > Sent: Wednesday, September 12, 2007 9:14 PM
> > > To: Cohen-Sason Daniel-BDC021
> > > Cc: openais at lists.osdl.org
> > > Subject: Re: [Openais] Problems with OpenAis version 0.81
> > > 
> > > Without logs it is difficult to tell what went wrong.
> > > 
> > > I would verify the following things:
> > > 
> > > You a node that has name service resolution to CENTOS.  That is
> required
> > > by the "safAmfNode = AMF1" directive.  If this doesn't match,
> testamf1
> > > will never be started.  Put some kind of log output in testamf1 to
> > > verify it is actually started by AMF.  If it isn't started, this is
> > > likely the cause of the problem.
> > > 
> > > verify:
> > > you have mode 755 clc_cli_script in /tmp/aisexample
> > > you have mode 755 openais-instantiate in /tmp/aisexample
> > > you have mode 755 testamf1 in /tmp/aisexample
> > > 
> > > I have noticed sometimes the default time values shipped in amf.conf
> do
> > > not work very well with some applications resulting in false
> positive
> > > failure detections.  Try changing them as follows:
> > > 
> > >                              saAmfCompDefaultClcCliTimeout = 5000
> > >                              saAmfCompDefaultCallbackTimeOut = 5000
> 
> > >                              saAmfHealthcheckPeriod = 5000
> > > 
> > > please send the log file generated by AIS.
> > > 
> > > Regards
> > > -steve
> > > 
> > > On Wed, 2007-09-12 at 08:45 +0300, Cohen-Sason Daniel-BDC021 wrote:
> > > > Hello
> > > > 
> > > > 
> > > >  
> > > > 
> > > > We, at Motorola, are trying to upgrade to Ver 0.81 from Ver 0.70.
> > > > 
> > > >  
> > > > 
> > > > The reason why we do it is because we encounter an unstable
> behavior
> > > > with 0.70, and hope that 0.81 will be better.
> > > > 
> > > >  
> > > > 
> > > > I first started by trying to run the "amfexample1", but for some
> > > > reason, the readiness states of the components are always becoming
> > > > OUT_OF_SERVICE (after I run: ./aisexec -f).
> > > > 
> > > >  
> > > > 
> > > > I followed the steps which are described in README.AMF.
> > > > 
> > > >  
> > > > 
> > > > I also noticed the bindnetaddr should be set, or the instantiation
> > > > won't even start.
> > > > 
> > > >  
> > > > 
> > > > Attached please find the log and the configuration files
> > > > from /tmp/aisexample folder.
> > > > 
> > > >  
> > > > 
> > > > I really hope you can help us.
> > > > 
> > > >  
> > > > 
> > > > Please advice,
> > > > 
> > > >  
> > > > 
> > > > Daniel
> > > > 
> > > > ________________
> > > > Daniel Cohen-Sason
> > > > MCIL, Design Center, Public Safety.
> > > > Multi-Net-Mobility (MNM).
> > > > Office:  +972-3-5658548 
> > > > Private: +972-57-5658548 (8548)
> > > > 
> > > > Daniel.Cohen at motorola.com
> > > > "The significant problems we have cannot be solved at the same
> level
> > > > of thinking with which we created them." [Albert Einstein]
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Openais mailing list
> > > > Openais at lists.linux-foundation.org
> > > > https://lists.linux-foundation.org/mailman/listinfo/openais
> > > 
> > _______________________________________________
> > Openais mailing list
> > Openais at lists.linux-foundation.org
> > https://lists.linux-foundation.org/mailman/listinfo/openais
> 



More information about the Openais mailing list