- **status**: fixed --> assigned
- **assigned_to**: Hung Nguyen --> Zoran Milinkovic
- **Comment**:
The changeset:
changeset: 6274:f3eaf7730729
user: Hung Nguyen [email protected]
date: Tue Feb 10 13:20:57 2015 +0700
summary: imm: Add OPENSAF_IMM_FLAG_PRT47_ALLOW value for noStdFlags [#969]
adds the new IMMNd protocol flag OPENSAF_IMM_FLAG_PRT47_ALLOW.
The suffix PRT47 was apparently chosen based on the relation to the
yet to be added imm API version A.2.15 (added by enhancement #643
currently under review for OepnsaF 4.6).
But these protocol flags are needed in not only to manage new protocols
added due to new API versions, but more generally to manage the addition
of *any* kind of new inter IMMND cluster protocol added in a particular
OpenSAF *version*. This ticket in itself is an example of just that.
We also want to have at most *one* such imm flag per OpenSAF release to
allow the upgrade to the new release to switch on ALL new imm cluster
protocols added by the release. That is we dont want several flags
per release (e.g. one per protocol) since that just adds unnecessary
complexity and unwanted options.
So the protocol flag for OpenSAF 4.6 must be labeled:
OPENSAF_IMM_FLAG_PRT46_ALLOW.
---
** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and
messages**
**Status:** assigned
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Feb 10, 2015 01:03 PM UTC
**Owner:** Zoran Milinkovic
All usage of SaNameT should be purged from the IMM server side code.
For message types we need backwards compatibility.
But new versions should be defined for all messages that currently use
SaNameT and the new message version should be used in the release where this
ticket is fixed, subject to the protocolXXAllowed bit in noStdFlags.
The message packing unpacking code should on the server side transform
to the new message type as part of unpacking.
On the IMMA client side, usage of SaNameT should be confined to only the
very top layer of the old API, when enhancement #643 is fixed.
http://sourceforge.net/p/opensaf/tickets/643/
---
Sent from sourceforge.net because [email protected] 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
