SI-SI Dependency Nagendra Kumar Senior Software Engineer, Emerson Network Power, Embedded Computing. nagendra.kumar@emerson.com June 3rd, 2009

Introduction of SI-SI Dependency Feature Examples Explored Presentation Outline Introduction of SI-SI Dependency Feature Examples Explored Tips Telecast Configuration Concepts References

Presentation Outline Introduction of SI-SI Dependency Feature Examples Explored Tips Telecast Configuration Concepts References

Introduction of SI-SI Dependency Feature When Introduced? Implemented in OpenSAF 3.0.0 release. AMF Feature compliance with B.01.01. Overall objective: With OpenSAF we want to define the de-facto standard in HA middleware which we expect to be widely adopted by our Telco customers. ECC USP: With Avantellis we will offer a fully integrated and validated „Application Ready“ platform to our customers ensuring the portability, flexibility and vendor independence only OpenSource environments can ensure. Competitors: GoAhead is a proprietary HA middleware application which use in commercial high volume deployments is absolutely no longer in the sense of our Tier1 customers. SUN Netra High Availability (HA) Suite Software also fall under this category. OpenClovis is based on a dual licensing model whereby for commercial use the license is not OpenSource but a royalty bearing proprietary version.

Introduction of SI-SI Dependency Feature What is it? One Service Instance (SI) can depend on another Service Instance (SI) Depend for what? For getting ACTIVE assignment. Not for getting STANDBY assignment.

Introduction of SI-SI Dependency Feature Few Terminologies: If SI1 depend upon SI2, then SI1 is called “Dependent SI” and SI2 is called “Sponsor SI”. SI is “Assigned” means: It has either of ACTIVE or QUIESCING assignment for at least an SU. SI is “Unassigned” means: It has either QUIESCED or STANDBY HA State or doesn’t have HA state assigned.

Introduction of SI-SI Dependency Feature Administrative Unlock Administrative Lock Sponsor SI ACTIVE STDBY Depends on SU1 SU2 Tolerance Timer Running Tolerance Timer Expired Dependent SI ACTIVE STDBY SU3 SU4 SU1 and SU2 Belong to SG1 – 2N Red SU3 and SU4 Belong to SG2 – 2N Red

Introduction of SI-SI Dependency Feature Few Points: Dependent SI and Sponsor SI can belong to same/different Service Group. Service Group may be across different nodes. Means SI-SI dependency across cluster.

Introduction of SI-SI Dependency Feature Few Points Contd… : Beyond Cluster also supported ?? SI of a cluster SG. SI of an External SU’s SG. Means SI-SI Dependency can be configured between Cluster SG and External SU’s SG. Not for SIs across two clusters.

Introduction of SI-SI Dependency Feature Few Points Contd… : A “dependent SI” can depend upon more than one “Sponsor SI”. Sponsor SI 1 Dependent SI 1 Sponsor SI 2

Introduction of SI-SI Dependency Feature Few Points Contd… : A “Sponsor SI” can sponsor more than one “Dependent SI”. Dependent SI 1 Sponsor SI 1 Dependent SI 2 There should not be any “Cyclic Dependency”.

Introduction of SI-SI Dependency Feature Cyclic Dependency: SI1 depends on SI2. SI2 depends on SI1. SI1 SI2

Introduction of SI-SI Dependency Feature Cyclic Dependency contd…. : AMF can detect cyclic dependency configuration. Cyclic dependency configuration will be rejected.

Presentation Outline Introduction of SI-SI Dependency Feature Examples Explored Tips Telecast Configuration Concepts References

Examples Explored DHCP : Module1: Holds IP address pool. Module2: Gets IP addresses from Module1 and sends back to Clients. Module2 depends on Module1. If Module1 SI is removed, Module2 SI should also be removed.

Presentation Outline Introduction of SI-SI Dependency Feature Examples Explored Tips Telecast Configuration Concepts References

Tips Telecast Few Tips: Keep in mind, SI Ξ Work Load Configure SI-SI Dependency based on Work Dependency. Configure SI-SI Dependency based on Work flow.

Configure SI-SI Dependency based on Work Dependency. Tips Telecast Few Tips Contd…: Configure SI-SI Dependency based on Work Dependency. Work 2 Depends on Work 1 Work 1 Work 2

Configure SI-SI Dependency based on Work flow. Tips Telecast Few Tips Contd…: Configure SI-SI Dependency based on Work flow. Work 2 Depends on Work 1 Work 3 Depends on Work 2 Work 1 Work 2 Work 3

Presentation Outline Introduction of SI-SI Dependency Feature Examples Explored Tips Telecast Configuration Concepts References

Configuration Concepts AMF Configuration Interfaces: Two Options: Static Configuration: AppConfig.xml/NCSSystemBOM.xml. Dynamic Configuration: Management Interface (SNMP, CLI).

Configuration Concepts Option 1: Static Configuration Configuration Attributes : <SIInstance name="safSi=Si_Dependent"> ------------- <SIDepList> <SIDep name="safSi=Si_Sponsor" tolTime="500000" /> </SIDepList> --------------- </SIInstance>

Configuration Concepts Option 1: Dynamic Configuration Configuration Attributes (SAF-AMF-MIB): SaAmfSISIDepTableEntry ::= SEQUENCE { saAmfSISIDepSIName SnmpAdminString, saAmfSISIDepDepndSIName SnmpAdminString, saAmfSISIDepToltime SafTimeStamp, saAmfSISIDepRowStatus RowStatus }

Presentation Outline Introduction of SI-SI Dependency Feature Examples Explored Tips Telecast Configuration Concepts References

References SAF AIS Application Management Framework Specifications (SAI-AIS-AMF-B.01.01) OpenSAF Availability Service Release 3 Programmer's Reference.

Questions ?

Thank You! For queries, please post it to User mailing List [users@list.opensaf.org] Nagendra Kumar [nagendra.kumar@emerson.com]