Lei,
Comments inline ...
Hi, Sayan,
Thank you for the answer, it makes me much clear now. Since IfSv is an OpenSAF
complementary service, so it has no dependency on SAF compliant service AMF. We
have to define our own trigger points for invoking IfSv APIs when we need to do
so. Am I right?
[SS] Yes. Examples of trigger pints could include the receipt of a message,
reading a bit in a check-point or shared-memory etc. that signifies that the
node which was using the ip address will no longer be using it and it can be
moved.
Sayan
Best Regards,
Qiao Lei
while(1){
Problem *newProblem = new Problem();
solveProblem(newProblem);
cout<<"This is the life!"<<endl;
}
尽力而为还不够，得竭尽全力才行。
-----邮件原件-----
发件人: Saha Sayandeb-G19428 [mailto:[EMAIL PROTECTED]
发送时间: 2007年11月13日 1:54
收件人: Qiao, Lei (TSG-GDCC-CMEP/SH)
抄送: [email protected]
主题: RE: [Users] Can a non-SA-aware,non-proxied local component utilize the
OpenSAF interface serviceIfSv ?
Lei,
Comments inline ...
Hi, all,
I'd like to describe the requirement below:
1. A non-SA-aware, non-proxied local component is modeled in AMF; 2. It wants
to utilize the OpenSAF interface service IfSv.
Can this requirement be satisfied by OpenSAF? I am a little confused here: For
non-proxied, non-SA-aware local components, the role of the AMF is limited to
the management of the component life cycle. So I think AMF cannot: assign
workloads to the component/ remove workloads from the component/assign the HA
state to the component for each workload to it; AMF can do this for a SA-aware
component. But in the IfSv documentation, it says that the application on
obtaining a new active Component Service Instance (CSI) assignment will call
the NCS_IFSV_REQ_VIP_INSTALL with the IP address; In case of a switchover, when
an active application gets a CSI assignment QUIESCED, it must call
NCS_IFSV_REQ_VIP_FREE. So my question is:"Can a non-SA-aware, non-proxied local
component utilize the OpenSAF interface service IfSv ?"
[SS] I think the documentation is merely describing a scenario with trigger
points for making IFSv API invocations which are relevant for SA-Aware
components only. This doesn't mean that these same APIs can't be invoked for
non-SA_Aware components as far as you have other trigger points that you can
understand and make those API invocations appropriately.
Thanks
Sayan
I need someone to confirm this. Thanks for your time and thinking obout this.
Best Regards,
Qiao Lei
while(1){
Problem *newProblem = new Problem();
solveProblem(newProblem);
cout<<"This is the life!"<<endl;
}
尽力而为还不够，得竭尽全力才行。
_______________________________________________
Users mailing list
[email protected]
http://list.opensaf.org/maillist/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://list.opensaf.org/maillist/listinfo/users
