[tickets] [opensaf:tickets] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-08-25 Thread Anders Widell
- **Milestone**: 4.7.FC --> never



---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** wontfix
**Milestone:** never
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Aug 25, 2015 04:08 PM UTC
**Owner:** Hung Nguyen


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 protocol46Allowed 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 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.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-05-08 Thread Anders Bjornerstedt
- **status**: review --> wontfix
- **Comment**:

It seems we can not reach an agreement on how to solve this problem.

I hvae therefore decided to close this ticket and gice up on the goal
of  ridding the imm server from the SaNameT type.

It was simply a too complex task to acheive with reasonable effort.





---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** wontfix
**Milestone:** 4.7-Tentative
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Mon Apr 20, 2015 05:36 AM UTC
**Owner:** Hung Nguyen

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 protocol46Allowed 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 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.--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-04-19 Thread Hung Nguyen
- **status**: assigned --> review



---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** review
**Milestone:** 4.7-Tentative
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Thu Mar 26, 2015 12:30 PM UTC
**Owner:** Hung Nguyen

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 protocol46Allowed 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 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.--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-03-26 Thread Anders Bjornerstedt
- **status**: fixed --> assigned
- **Milestone**: 4.6.FC --> 4.7-Tentative



---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** assigned
**Milestone:** 4.7-Tentative
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Mon Mar 16, 2015 05:31 PM UTC
**Owner:** Hung Nguyen

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 protocol46Allowed 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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-03-16 Thread Mathi Naickan
- **Comment**:

Any pending bugs in this topic can be tracked with a new ticket with milestone 
as 4.6.RC1



---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** fixed
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Mon Mar 16, 2015 05:30 PM UTC
**Owner:** Hung Nguyen

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 protocol46Allowed 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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-03-16 Thread Mathi Naickan
- **status**: assigned --> fixed



---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** fixed
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Fri Mar 13, 2015 03:32 PM UTC
**Owner:** Hung Nguyen

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 protocol46Allowed 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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-03-13 Thread Zoran Milinkovic
- **assigned_to**: Zoran Milinkovic --> Hung Nguyen



---

** [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:** Fri Mar 13, 2015 01:52 PM UTC
**Owner:** Hung Nguyen

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 protocol46Allowed 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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-03-13 Thread Neelakanta Reddy
Introduce a new message type IMMND_EVT_A2ND_CCB_OBJ_DELETE_RSP_3 and add the 
changes for removing SaNameT, by introducing OI version check for RSP_3 
callback and keep the original IMMND_EVT_A2ND_CCB_OBJ_DELETE_RSP messaging 
without change.



---

** [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:** Fri Mar 13, 2015 01:36 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 protocol46Allowed 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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-03-13 Thread Neelakanta Reddy
- **status**: fixed --> assigned
- **Comment**:

diff --git a/osaf/libs/common/immsv/include/immsv_evt_model.h 
b/osaf/libs/common/immsv/include/immsv_evt_model.h
--- a/osaf/libs/common/immsv/include/immsv_evt_model.h
+++ b/osaf/libs/common/immsv/include/immsv_evt_model.h
@@ -288,7 +288,7 @@ extern "C" {
SaUint32T implId;
SaUint32T inv;
SaAisErrorT result;
-   SaNameT name;
+   IMMSV_OCTET_STRING name;
IMMSV_OCTET_STRING errorString;
} IMMSV_OI_CCB_UPCALL_RSP;
 
The above modification is not backward compatible.

particularly when sending IMMND_EVT_A2ND_CCB_OBJ_DELETE_RSP either from 4.5 to 
4.6 or from 4.6 to 4.5



---

** [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:** Fri Mar 13, 2015 10:29 AM 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 protocol46Allowed 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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-03-13 Thread Anders Bjornerstedt
- Description has changed:

Diff:



--- old
+++ new
@@ -3,7 +3,7 @@
 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.
+ticket is fixed, subject to the protocol46Allowed bit in noStdFlags.
 The message packing unpacking code should on the server side transform
 to the new message type as part of unpacking.
 






---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** fixed
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Fri Feb 27, 2015 01:33 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 protocol46Allowed 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 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


Re: [tickets] [opensaf:tickets] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-03-02 Thread Neelakanta Reddy

Hi zoran,

forget the comment below, I am testing #643 patch that is the reason i 
got the following compilation error.


/Neel.
On Monday 02 March 2015 03:55 PM, Neelakanta Reddy wrote:

Hi zoran,

The default is not compiling.

The following changes are missed in ImmModel.cc for protocol47 to 
protoco46 for the following functions:


ImmModel.cc: In member function ‘SaAisErrorT 
ImmModel::ccbObjectCreate(ImmsvOmCcbObjectCreate*, SaUint32T*, 
unsigned int*, SaUint32T*, SaUint32T*, unsigned int*, std::string&, 
bool*)’:
ImmModel.cc:6736:31: error: ‘protocol47Allowed’ was not declared in 
this scope

 if(!protocol47Allowed()) {
   ^
ImmModel.cc: In member function ‘SaAisErrorT 
ImmModel::rtObjectCreate(ImmsvOmCcbObjectCreate*, SaUint32T, unsigned 
int, SaUint32T*, SaUint32T*, unsigned int*, SaUint32T*, SaUint32T*)’:
ImmModel.cc:13996:31: error: ‘protocol47Allowed’ was not declared in 
this scope

 if(!protocol47Allowed()) {

/Neel.

On Friday 27 February 2015 07:03 PM, Zoran Milinkovic wrote:


  * *status*: assigned --> fixed
  * *Comment*:

default(4.6):

changeset: 6289:cf6044a98dfb
tag: tip
user: Zoran Milinkovic zoran.milinko...@ericsson.com 


date: Wed Feb 25 13:41:32 2015 +0100
summary: imm: change protocol 47 to protocol 46 [#969] 





*[tickets:#969]  IMM: 
remove all use of SaNameT from IMM server side and messages*


*Status:* fixed
*Milestone:* 4.6.FC
*Created:* Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
*Last Updated:* Tue Feb 24, 2015 09:59 AM 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 
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




--
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


--
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


Re: [tickets] [opensaf:tickets] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-03-02 Thread Neelakanta Reddy

Hi zoran,

The default is not compiling.

The following changes are missed in ImmModel.cc for protocol47 to 
protoco46 for the following functions:


ImmModel.cc: In member function ‘SaAisErrorT 
ImmModel::ccbObjectCreate(ImmsvOmCcbObjectCreate*, SaUint32T*, unsigned 
int*, SaUint32T*, SaUint32T*, unsigned int*, std::string&, bool*)’:
ImmModel.cc:6736:31: error: ‘protocol47Allowed’ was not declared in this 
scope

 if(!protocol47Allowed()) {
   ^
ImmModel.cc: In member function ‘SaAisErrorT 
ImmModel::rtObjectCreate(ImmsvOmCcbObjectCreate*, SaUint32T, unsigned 
int, SaUint32T*, SaUint32T*, unsigned int*, SaUint32T*, SaUint32T*)’:
ImmModel.cc:13996:31: error: ‘protocol47Allowed’ was not declared in 
this scope

 if(!protocol47Allowed()) {

/Neel.

On Friday 27 February 2015 07:03 PM, Zoran Milinkovic wrote:


  * *status*: assigned --> fixed
  * *Comment*:

default(4.6):

changeset: 6289:cf6044a98dfb
tag: tip
user: Zoran Milinkovic zoran.milinko...@ericsson.com 


date: Wed Feb 25 13:41:32 2015 +0100
summary: imm: change protocol 47 to protocol 46 [#969] 





*[tickets:#969]  IMM: 
remove all use of SaNameT from IMM server side and messages*


*Status:* fixed
*Milestone:* 4.6.FC
*Created:* Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
*Last Updated:* Tue Feb 24, 2015 09:59 AM 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 
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


--
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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-02-27 Thread Zoran Milinkovic
- **status**: assigned --> fixed
- **Comment**:

default(4.6):

changeset:   6289:cf6044a98dfb
tag: tip
user:Zoran Milinkovic 
date:Wed Feb 25 13:41:32 2015 +0100
summary: imm: change protocol 47 to protocol 46 [#969]



---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** fixed
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Tue Feb 24, 2015 09:59 AM 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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-02-25 Thread Anders Bjornerstedt
- **status**: fixed --> assigned
- **assigned_to**: Hung Nguyen --> Zoran Milinkovic
- **Comment**:

The changeset:

changeset: 6274:f3eaf7730729
user: Hung Nguyen hung.d.ngu...@dektech.com.au
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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-02-10 Thread Zoran Milinkovic
- **status**: review --> fixed
- **Comment**:

default(4.6):

changeset:   6273:02dab97f8843
user:Hung Nguyen 
date:Thu Dec 11 11:08:05 2014 +0700
summary: imm: Remove SaNameT from IMMND event handling routines [#969]

changeset:   6274:f3eaf7730729
user:Hung Nguyen 
date:Tue Feb 10 13:20:57 2015 +0700
summary: imm: Add OPENSAF_IMM_FLAG_PRT47_ALLOW value for noStdFlags [#969]

changeset:   6275:db3ee7b2aa3b
user:Hung Nguyen 
date:Tue Feb 10 13:41:15 2015 +0700
summary: imm: Remove use of SaNameT from IMMSV_OM_ADMIN_OWNER_INITIALIZE 
[#969]

changeset:   6276:b8d1304bb46e
tag: tip
user:Hung Nguyen 
date:Thu Dec 18 14:27:24 2014 +0700
summary: imm: Remove use of SaNameT from IMMSV_OI_CCB_UPCALL_RSP [#969]




---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** fixed
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Thu Feb 05, 2015 12:19 PM UTC
**Owner:** Hung Nguyen

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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2015-02-05 Thread Anders Bjornerstedt
Could someone update the status of this ticket.
It appears to be iunder review since december 2014.


---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** review
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Fri Dec 19, 2014 08:56 AM UTC
**Owner:** Hung Nguyen

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 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] #969 IMM: remove all use of SaNameT from IMM server side and messages

2014-12-19 Thread Hung Nguyen
- **status**: accepted --> review



---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** review
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Mon Dec 08, 2014 09:42 AM UTC
**Owner:** Hung Nguyen

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 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.--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #969 IMM: remove all use of SaNameT from IMM server side and messages

2014-12-08 Thread Hung Nguyen
- **status**: unassigned --> accepted
- **assigned_to**: Hung Nguyen



---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** accepted
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Thu Jul 24, 2014 01:59 PM UTC
**Owner:** Hung Nguyen

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 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.--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #969 IMM: remove all use of SaNameT from IMM server side and messages

2014-07-24 Thread Anders Bjornerstedt



---

** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and 
messages**

**Status:** unassigned
**Milestone:** 4.6.FC
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Thu Jul 24, 2014 01:59 PM UTC
**Owner:** nobody

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 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.--
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets