[tickets] [opensaf:tickets] #643 IMM: API that replaces SaNameT with SaStringT and SA_IMM_ATTR_DN
- Description has changed: Diff: --- old +++ new @@ -14,9 +14,16 @@ having SaStringT and SA_IMM_ATTR_DN combined with SA_IMM_ATTR_RDN would also indicate that this is an association class. -SA_IMM_ATTR_NO_DANGLING. Currently (OpenSAF 4.4) will only be allowed +SA_IMM_ATTR_NO_DANGLING. Currently (OpenSAF 4.5) is only allowed on attributes of type SaNameT, but will of course be allowed also on -attributes of type SaStringT if the SA_IMM_ATTR_DN flag is also set. +attributes of type SaStringT if the SA_IMM_ATTR_DN flag is also set. +The exception is the RDN attribute which still can not have the +SA_IMM_ATTR_NO_DANGLING set. The reason is that the RDN atribute, +even if defined on SaNameT, or on SaStringT with SA_IMM_ATTR_DN flag, +actually does not contain a simple DN value. The RDN attribute of an +association object contains a value on the form X=Y where the right hand +side is a DN. Strictly speaking the logical type of an RDN attribute +is never a simple DN/reference, even if the type is SaNameT. All the other flags may also be used in combination with SA_IMM_ATTR_DN, with the normal meaning. --- ** [tickets:#643] IMM: API that replaces SaNameT with SaStringT and SA_IMM_ATTR_DN** **Status:** accepted **Milestone:** 4.6.FC **Created:** Thu Nov 28, 2013 05:00 PM UTC by Anders Bjornerstedt **Last Updated:** Tue Mar 03, 2015 12:50 PM UTC **Owner:** Zoran Milinkovic The IMM service should provide an updated API where all use of the troublesome SaNameT type is replaced by the SaStringT type or the SaConstStringT type #625. Also needed is a new flag value for attribute definitions: SA_IMM_ATTR_DN. Defining an attribute in an IMM class definition on the SaStringT type and also setting the flag SA_IMM_ATTR_DN, will mean that the attribute is intended to hold a value that should be a DN. Other flags that make sense to also set on such an attribute definition where applicable are: SA_IMM_ATTR_RDN if this is the RDN attribute. Just as having SaNameT the type of an RDN attribute indicates that the class is an association class, having SaStringT and SA_IMM_ATTR_DN combined with SA_IMM_ATTR_RDN would also indicate that this is an association class. SA_IMM_ATTR_NO_DANGLING. Currently (OpenSAF 4.5) is only allowed on attributes of type SaNameT, but will of course be allowed also on attributes of type SaStringT if the SA_IMM_ATTR_DN flag is also set. The exception is the RDN attribute which still can not have the SA_IMM_ATTR_NO_DANGLING set. The reason is that the RDN atribute, even if defined on SaNameT, or on SaStringT with SA_IMM_ATTR_DN flag, actually does not contain a simple DN value. The RDN attribute of an association object contains a value on the form X=Y where the right hand side is a DN. Strictly speaking the logical type of an RDN attribute is never a simple DN/reference, even if the type is SaNameT. All the other flags may also be used in combination with SA_IMM_ATTR_DN, with the normal meaning. --- 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.-- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1046 unlock of si fails after fault and one SI is only partially assigned
Version-2 published. --- ** [tickets:#1046] unlock of si fails after fault and one SI is only partially assigned** **Status:** review **Milestone:** 4.4.2 **Created:** Thu Sep 04, 2014 11:16 AM UTC by surender khetavath **Last Updated:** Fri Feb 13, 2015 06:15 AM UTC **Owner:** Praveen changeset : 5697 model : 2n configuration : 1App,1SG,5SUs with 3comps each, 5SIs with 3CSIs each si-si deps configured as SI1-SI2-SI3-SI4. SU1 is active, SU2 is standby. SU1 is mapped to SC-1 and SU2 to SC-2,SU3 to PL-3 and SU4,5 to PL-4 saAmfSGAutoRepair=1(True) SuFailover=1(True) Test: lock SI1 reject in the remove cbk unlock SI1 Unlock of Si times out su admin repair also times out. safSi=TWONSI1,safApp=TWONAPP saAmfSIAdminState=LOCKED(2) saAmfSIAssignmentState=UNASSIGNED(1) safSi=TWONSI5,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3) safSi=TWONSI3,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=UNASSIGNED(1) safSi=TWONSI4,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=UNASSIGNED(1) safSi=TWONSI2,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=UNASSIGNED(1) safSu=SU1,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=UNINSTANTIATED(1) saAmfSUReadinessState=OUT-OF-SERVICE(1) safSu=SU2,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) safSu=SU3,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) safSu=SU4,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) safSu=SU5,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP saAmfSISUHAState=STANDBY(2) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP saAmfSISUHAState=STANDBY(2) safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP saAmfSISUHAState=ACTIVE(1) --- 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.-- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1259 amfd: Quiesced is not sent, if comp fails in handling quiescing state during SU shutdown op
--- ** [tickets:#1259] amfd: Quiesced is not sent, if comp fails in handling quiescing state during SU shutdown op** **Status:** unassigned **Milestone:** 4.6.FC **Created:** Thu Mar 05, 2015 04:37 AM UTC by Praveen **Last Updated:** Thu Mar 05, 2015 04:37 AM UTC **Owner:** nobody Configuration: 2N model with one SI having 2 CSIs. 2 SUs with 2 comps in each SU. Each component will get one CSI. Recovery policy component-failover. Steps to reproduce: 1)Bring model up on 2 controllers. 2)Issue shutdown operation on active SU. 3)Kill one of the components before it responds for quiescing callback. 4)AMFD does not send quiesced assignments. Instead, it sends removal of assignments for this failed SU. After successful removal,AMFD performs fail-over successfully by making standby assignment active. Attached are configuration and traces. --- 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.-- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #896 immpbe: imm.db.XXXXXX temp files should managed in pbe subdirectory
- **status**: assigned -- review --- ** [tickets:#896] immpbe: imm.db.XX temp files should managed in pbe subdirectory** **Status:** review **Milestone:** future **Labels:** PBE **Created:** Fri May 09, 2014 02:00 PM UTC by Anders Bjornerstedt **Last Updated:** Mon Mar 02, 2015 06:38 AM UTC **Owner:** Hung Nguyen The PBE generates the imm.db file in what should be a local tmp directory. This is set by the configuration variable IMMSV_PBE_TMP_DIR in the immnd.conf configuration file. By default it is /tmp. The PBE should create a sub-directory to IMMSV_PBE_TMP_DIR where it creates all temporary files. This will reduce the risk of interference with other services and applications sharing the tmp directory. It will also facilitate the safe cleanup of all such files by a PBE that is restarted after having crashed. --- 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.-- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1154 smf: defects detected by Coverity tool should be fixed
33 defects pointed out by Coverity Tool for SMF in default branch. 7 defects ignored since those were not relevant. 26 defects fixed by the scope of this ticket. Coverity tool doesn't show any defects for SMF in default branch at the moment. --- ** [tickets:#1154] smf: defects detected by Coverity tool should be fixed** **Status:** fixed **Milestone:** 4.6.FC **Created:** Mon Oct 06, 2014 11:38 AM UTC by Robert Apanowicz **Last Updated:** Thu Feb 26, 2015 12:24 PM UTC **Owner:** Robert Apanowicz This ticket is the placeholder for all the defects of SMF which are detected by Coverity tool. --- 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.-- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1208 IMM: Update README clarifying that augmented CCBs must be kept pure
- **status**: accepted -- review --- ** [tickets:#1208] IMM: Update README clarifying that augmented CCBs must be kept pure** **Status:** review **Milestone:** 4.4.2 **Created:** Tue Nov 11, 2014 12:42 PM UTC by Anders Bjornerstedt **Last Updated:** Wed Feb 25, 2015 12:30 PM UTC **Owner:** Anders Bjornerstedt When a ccb augmentation is started by an OI, the IMM server will disable the OI timer that is normally monitoring an OI callback. The reason for this is that the OI doing a ccb-augmentation is in eseence an om-client. The purpose of the OI timeout is to detect if an OI gets hung for some reson that does not involve the imm itself. While the OI is doing augment operations it is using the OM-API that is itself monitored by the IMMA_SYNCR_TIMEOUT. So the OI can not hang indefinitely on any such ccb augment downcalls. But it must be clarified in the README that an OI performing an augmentation must avoid doing other things than the augmentation operations. It should stay pure and not interleave augmentation operations with other tasks. Finally there is also a problem in that after an augmentation is completed, but before the OI callback returns, then no OI timer is restored. So an OI that hangs on some other operation inside the callback, but after the ccb-augmentation has been closed, will hang for an indefinite time period. In practice until the either the user closes the handle or the ccb gets aborted due to an imm-.sync. So in addition to the OI keeping the augmentation pure, the OI implementer should try to do other tasks befor an augmentation, i.e. avoid doing anything after an augmentation. This last problem of an OI callback not being timer monitored after the close of an augmentation is complex/expensive to fix. A fix for this will be done as an enhancement and tracked by a spearate ticket. --- 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.-- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
