[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules

2017-07-21 Thread Anders Widell via Opensaf-tickets 



---

** [tickets:#2533] pyosaf: Make pyosaf:::immom::initialize() consistent with 
other modules**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Fri Jul 21, 2017 01:09 PM UTC by Anders Widell
**Last Updated:** Fri Jul 21, 2017 01:09 PM UTC
**Owner:** nobody


The module pyosaf/utils/immom has a method with the name initialize(), which is 
called automatically when the module is implemented. This is inconsistent with 
other pyosaf modules under utils, which don't call the initialize method 
automatically when the module is imported. Also, the initialize method in immom 
has a preceding underscore character, which should be removed to make the 
method name consistent with the other modules.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #70 AMF support for Container and contained components

2017-07-21 Thread Praveen via Opensaf-tickets 
Created branch  ticket-70  and pushed some initial patches in repo:
git://git.code.sf.net/u/praveenmalviya/review.


---

** [tickets:#70] AMF support for Container and contained components**

**Status:** assigned
**Milestone:** future
**Created:** Mon May 13, 2013 04:14 AM UTC by Nagendra Kumar
**Last Updated:** Wed Jul 19, 2017 08:31 AM UTC
**Owner:** Praveen


Migrated from http://devel.opensaf.org/ticket/1436:

Current implementation of AMF doesn't support Container and Contained 
components.

Concept of container and contained component was introduced in B.03.01 spec. 
Because of this support,
there were series of changes and new additions in different sections of the 
spec. Also a new chapeter 6 is fully dedicated to conatiner and contained 
components. 

What follows is summary of conatiner and contained components concept collected 
from different sections of the B.04.01 spec with reference to particular 
sections and page no.

**A)Section  3.1.2.1.1 page 45 talks about use case related to containter**
 ** and contained component concept:**
"
The concept of container and contained components allows the Availability 
Management
Framework to integrate components that are not executed directly by the
operating system, but rather in a controlled environment running on top of the 
operating
system. Widespread environments are runtime environments, virtual machines,
or component frameworks.
"
AMF directly manages life cycle of container component but not of containted 
component.
A container component cooperates with AMF for managing life cycle of contained 
component.
If a container comp1 manages life cycle of a contained comp2 then comp1 is 
termed
as assciated container component of comp2 and comp2 is termed as associated 
contained
component of comp1. If there is one more component say comp3 for which 
associated
container component is same comp1 then comp3 and comp2 are referred as
collocated contained components. (3.1.2.1.1 Container and Contained Components 
page 45)

**B)Configuration:**
-Container and contained components are local SA-aware components.
 (6.1.2 Component Category page 221)
-User can configure attribute "saAmfCtCompCategory" of class "SaAmfCompType" 
with
 following values to declare component of this CompType is a container or
 contained component (Section7.4.8 SaAmfCompCategoryT page 258):

 \ #define SA_AMF_COMP_CONTAINER 0x0010
  \#define SA_AMF_COMP_CONTAINED 0x0020

-A single container component acts as container component for many contained
 conponents.(6.2.2 Assignment of the Container CSI page 224).
-Container and its contained components must be hosted on same AMF Node.
-A containter component can be part of SG of only N-Way Acitve model.
 (6.1.6 Redundancy Models Page 222)
-A contained component can be part of SG of any redundancy model.
 (6.1.6 Redundancy Models Page 223)
-A SU cannot contain any other types/categories of components if a container 
component is
 present in it. ( 3.1.4 Service Unit page 52).
-A SU cannot contain both container components and contained components.
 (6.1.5 Container and Contained Components in Service Units and Service Groups 
page 221)
-A SU that contains a contained component can only contain collocated contained
components.(6.1.5 Container and Contained Components in Service Units and 
Service Groups page 221)
-SUs containing contained components and SUs containing container components
 must belong to different SGs.
(6.1.5 Container and Contained Components in Service Units and Service Groups 
page 222)
-Since a container component can be associated with many contained components 
and also there
 can be many container components in a SU, a user has to specify a CSI name in
 saAmfCompContainerCsi in Comp class to declare indirectly its associated 
container component.
 The component which will receive this container CSI will act as container 
component
 for this contained component on same node.(3.1.3 Component Service Instance 
page 51)
-A SI containing a container CSI cannot have any other CSI.
(6.1.5 Container and Contained Components in Service Units and Service Groups 
page 222)
-A container component can recieve multiple CSI assignments based on 
configuration. Among
 these CSIs, one or more can be for handling contained components and others 
can be
 for providing other services. (3.1.3 Component Service Instance page 51)
-If a SU contains contained components then they should have a common 
associated container
 component. This can be ensured by configuring same container CSI.( 3.1.4 
Service Unit page 52)
-Rank of container SI should be higher than the rank of contained SI.
 (3.6.1.4 Considerations when Configuring Redundancy page 121) and
 (6.1.5 Container and Contained Components in Service Units and Service Groups 
Page 222)
-There should not be any conflict while hosting container SUs and contained SUs
 on nodes and node group as both container and its associated contained 
components
 should reside on the same node.

[tickets] [opensaf:tickets] #2532 mds: SVC_UP event is not received after subscribing

2017-07-21 Thread Hung Nguyen via Opensaf-tickets 



---

** [tickets:#2532] mds: SVC_UP event is not received after subscribing**

**Status:** unassigned
**Milestone:** 5.17.08
**Created:** Fri Jul 21, 2017 05:59 AM UTC by Hung Nguyen
**Last Updated:** Fri Jul 21, 2017 05:59 AM UTC
**Owner:** nobody
**Attachments:**

- 
[logs_n_traces.tgz](https://sourceforge.net/p/opensaf/tickets/2532/attachment/logs_n_traces.tgz)
 (1.5 MB; application/x-compressed)


MDS is successfully installed on IMMA and IMMA subscribed to IMMD successfully.
IMMND also received IMMA SVC_UP event but IMMA didn't receive SVC_UP event for 
IMMND.

~~~
<142>1 2017-07-20T13:00:36.072773+02:00 PL-4 immomtest 278 mds.log [meta 
sequenceId="14043"] MCM:API: svc_id = IMMA_OM(26) on VDEST id = 65535, 
SVC_PVT_VER = 0 Install Successfull
> ...
<142>1 2017-07-20T13:00:36.073091+02:00 PL-4 immomtest 278 mds.log [meta 
sequenceId="14074"] MCM:API: svc_subscribe :svc_id = IMMA_OM(26) on VDEST id = 
65535 Subscription to svc_id = IMMND(25) Successful
> ...
<142>1 2017-07-20T13:00:36.073904+02:00 PL-4 osafimmnd 177 mds.log [meta 
sequenceId="96185"] MCM:API: svc_up : svc_id = IMMND(25) on DEST id = 65535 got 
UP for svc_id = IMMA_OM(26) on Adest = , 
rem_svc_pvt_ver=0, rem_svc_archword=10
~~~


IMMA waited for the SVC_UP event for 30 sec but didn't receive anything.
~~~
Jul 20 13:00:36.071465 imma [278:278:src/imm/agent/imma_init.cc:0263] >> 
imma_startup 
Jul 20 13:00:36.071474 imma [278:278:src/imm/agent/imma_init.cc:0273] TR use 
count 0
Jul 20 13:00:36.071484 imma [278:278:src/base/ncs_main_pub.c:0220] TR 
NCS:PROCESS_ID=278
Jul 20 13:00:36.071494 imma [278:278:src/base/sysf_def.c:0089] TR INITIALIZING 
LEAP ENVIRONMENT
Jul 20 13:00:36.071584 imma [278:278:src/base/sysf_def.c:0124] TR DONE 
INITIALIZING LEAP ENVIRONMENT
Jul 20 13:00:36.071832 imma [278:278:src/base/ncs_main_pub.c:0757] TR 
NCS:NODE_ID=0x0002040F
Jul 20 13:00:36.072329 imma [278:278:src/mbc/mbcsv_dl_api.c:0059] >> 
mbcsv_lib_req 
Jul 20 13:00:36.072350 imma [278:278:src/mbc/mbcsv_dl_api.c:0096] >> 
mbcsv_lib_init 
Jul 20 13:00:36.072378 imma [278:278:src/mbc/mbcsv_mbx.c:0174] >> 
mbcsv_initialize_mbx_list 
Jul 20 13:00:36.072389 imma [278:278:src/mbc/mbcsv_mbx.c:0189] << 
mbcsv_initialize_mbx_list 
Jul 20 13:00:36.072399 imma [278:278:src/mbc/mbcsv_pwe_anc.c:0158] >> 
mbcsv_initialize_peer_list 
Jul 20 13:00:36.072409 imma [278:278:src/mbc/mbcsv_pwe_anc.c:0173] << 
mbcsv_initialize_peer_list 
Jul 20 13:00:36.072419 imma [278:278:src/mbc/mbcsv_dl_api.c:0075] << 
mbcsv_lib_req 
Jul 20 13:00:36.072440 imma [278:278:src/base/ncs_main_pub.c:0389] TR 
MBCSV:MBCA:ON
Jul 20 13:00:36.073104 imma [278:278:src/imm/agent/imma_init.cc:0063] >> 
imma_sync_with_immnd 
Jul 20 13:00:36.073114 imma [278:278:src/imm/agent/imma_init.cc:0071] TR 
Blocking first client
Jul 20 13:01:06.102156 imma [278:278:src/imm/agent/imma_init.cc:0081] TR 
Blocking wait released
Jul 20 13:01:06.102375 imma [278:278:src/imm/agent/imma_init.cc:0091] << 
imma_sync_with_immnd 
Jul 20 13:01:06.102413 imma [278:278:src/imm/agent/imma_init.cc:0179] TR Client 
agent successfully initialized
Jul 20 13:01:06.102427 imma [278:278:src/imm/agent/imma_init.cc:0296] << 
imma_startup: use count 1
~~~


Attached is traces and logs.




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets