Version is 4.3.1.

1)  Create a 2N service group
2)  Create a "No Redundancy" service group
3)  Have one of the "No Redundancy" SIs depend on the 2N SI
4)  start opensaf
5)  The "No Redundancy" SI will get instantiated, but not get an assignment.

Alex

On 03/05/2014 01:46 AM, praveen malviya wrote:
> Please specify which version of OpenSAF is being used.
> Also please tell the steps performed.
>
> Thanks,
> Praveen
>
>
>
> On 04-Mar-14 5:40 PM, Alex Jones wrote:
>> Hello All,
>>
>>       I'm seeing a problem with SaAmfSIDependency when it is used 
>> between
>> SIs in different SGs of different types.
>>
>>           <object class="SaAmfSIDependency">
>> <dn>safDepend=safSi=Management-2N\,safApp=ManagementApp,safSi=Management-NoRed2,safApp=ManagementApp</dn>
>>  
>>
>>           </object>
>>
>>       In this declaration "Management-NoRed2" is in a "No Redundancy"
>> service group, and "Management-2N" is in a 2N service group. With this
>> declaration "Management-NoRed2" will never get an assignment. It gets
>> instantiated, but never gets an assignment.
>>
>>       If I remove this declaration, "Management-NoRed2" gets its
>> assignment, but obviously the dependency isn't satisfied.
>>
>>       If the dependency is between SIs of the same service group 
>> type, it
>> works fine.
>>
>>       <object class="SaAmfSIDependency">
>> <dn>safDepend=safSi=Management-2N\,safApp=ManagementApp,safSi=FaultManagement-2N,safApp=FaultManagementApp</dn>
>>  
>>
>>           </object>
>>
>>       In this example, these two SIs are in different SGs, but they are
>> both 2N.  This case works as expected, and the dependency is satisfied.
>>
>>       Is there a bug here, or am I missing some configuration?
>> Alex
>>
>>
>> ------------------------------------------------------------------------------
>>  
>>
>> Subversion Kills Productivity. Get off Subversion & Make the Move to 
>> Perforce.
>> With Perforce, you get hassle-free workflows. Merge that actually works.
>> Faster operations. Version large binaries.  Built-in WAN optimization 
>> and the
>> freedom to use Git, Perforce or both. Make the move to Perforce.
>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk 
>>
>> _______________________________________________
>> Opensaf-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/opensaf-devel
>
>



------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to