You need to upgrade relevant parts of the AMF schema (imm-classes).
But that should not be a problem.
/AndersBj
________________________________
From: Hans Feldt [mailto:[email protected]]
Sent: den 23 oktober 2013 17:09
To: [opensaf:tickets]
Subject: [opensaf:tickets] #49 IMM: Support reference integrity checking
This feature makes it possible to remove logic from AMF!
________________________________
[tickets:#49]<http://sourceforge.net/p/opensaf/tickets/49/> IMM: Support
reference integrity checking
Status: accepted
Created: Wed May 08, 2013 07:52 AM UTC by Anders Bjornerstedt
Last Updated: Tue Sep 17, 2013 08:23 AM UTC
Owner: Zoran Milinkovic
Migrated from:
http://devel.opensaf.org/ticket/3122
Add a new flag for object attributes, defined as follows:
define SA_IMM_ATTR_NO_DANGLING 0x0000000004000000
The SA_IMM_ATTR_NO_DANGLING attribute is only meaningful for configuration
attributes of type SA_IMM_ATTR_SANAMET. Setting it for runtime attributes or
configuration attributes of other types is not allowed and generates an error.
The IMM service will guarantee that the value(s) of an attribute with the
SA_IMM_ATTR_NO_DANGLING flag, when set, contains the distinguished name of an
existing IMM object. IMM will reject attempts to set it to anything that is not
the distinguished name of an existing object, and it will reject attempts to
delete objects that are referenced by such an attribute. This validation is
performed when the CCB is applied, which means that it will take into account
all changes performed within the CCB.
Optionally, it is also possible to restrict the type of objects that an
attribute with the flag SA_IMM_ATTR_NO_DANGLING is allowed to reference. If the
attribute name contains the colon character (ASCII value 58), then the part of
the attribute name following the colon specifies the class name that referenced
object must be an instance of. The IMM service will reject attempts to set the
attribute to the distinguished name of an object that is not an instance of
this class.
________________________________
In addition, besides checking that the attribute value to be assigned is the DN
of an
existing object, the imm service will check that the object is persistent, i.e.
either
the DN of a config object or the DN of a persistent runtime object.
References to non persistent runtime objects can not be allowed since a cluster
restart would automatically cause such references to become dangling.
(Peristent runtime objects should of course never be used, but since they are
used
heavily by services such as smfsv, it would be strange not to support
referential integrity
covering references to such objects.
References from one PRTO to another PRTO would not be allowed according to the
above rules,
so this addition concerns only references from config objects to runtime
objects.
________________________________
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/opensaf/tickets/49/
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
---
** [tickets:#49] IMM: Support reference integrity checking**
**Status:** accepted
**Created:** Wed May 08, 2013 07:52 AM UTC by Anders Bjornerstedt
**Last Updated:** Wed Oct 23, 2013 03:08 PM UTC
**Owner:** Zoran Milinkovic
Migrated from:
http://devel.opensaf.org/ticket/3122
Add a new flag for object attributes, defined as follows:
#define SA_IMM_ATTR_NO_DANGLING 0x0000000004000000
The SA_IMM_ATTR_NO_DANGLING attribute is only meaningful for configuration
attributes of type SA_IMM_ATTR_SANAMET. Setting it for runtime attributes or
configuration attributes of other types is not allowed and generates an error.
The IMM service will guarantee that the value(s) of an attribute with the
SA_IMM_ATTR_NO_DANGLING flag, when set, contains the distinguished name of an
existing IMM object. IMM will reject attempts to set it to anything that is not
the distinguished name of an existing object, and it will reject attempts to
delete objects that are referenced by such an attribute. This validation is
performed when the CCB is applied, which means that it will take into account
all changes performed within the CCB.
Optionally, it is also possible to restrict the type of objects that an
attribute with the flag SA_IMM_ATTR_NO_DANGLING is allowed to reference. If the
attribute name contains the colon character (ASCII value 58), then the part of
the attribute name following the colon specifies the class name that referenced
object must be an instance of. The IMM service will reject attempts to set the
attribute to the distinguished name of an object that is not an instance of
this class.
-----------------------------------------------------------------
In addition, besides checking that the attribute value to be assigned is the DN
of an
existing object, the imm service will check that the object is persistent, i.e.
either
the DN of a config object or the DN of a persistent runtime object.
References to non persistent runtime objects can not be allowed since a cluster
restart would automatically cause such references to become dangling.
(Peristent runtime objects should of course never be used, but since they *are*
used
heavily by services such as smfsv, it would be strange not to support
referential integrity
covering references to such objects.
References from one PRTO to another PRTO would not be allowed according to the
above rules,
so this addition concerns only references from config objects to runtime
objects.
---
Sent from sourceforge.net because [email protected] is
subscribed to http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
