Re: [users] Max timeout limit problem in the "headless cluster" feature

[Hung Nguyen]

Yes, it will be pushed to all branches, including 5.1.

Regards,


Hung Nguyen - DEK Technologies



From: Jianfeng Dong jd...@juniper.net
Sent: Thursday, October 20, 2016 6:17PM
To: Hung Nguyen, Opensaf-users
 hung.d.ngu...@dektech.com.au, opensaf-users@lists.sourceforge.net
Cc:
 
Subject: RE: [users] Max timeout limit problem in the "headless cluster" feature


Much appreciate!

I notice the milestone is 5.0.2, but the fix code of this ticket will go 
into 5.1.0 as well, right?

Regards,

Jianfeng

*From:*Hung Nguyen [mailto:hung.d.ngu...@dektech.com.au]
*Sent:* Thursday, October 20, 2016 6:48 PM
*To:* Jianfeng Dong ; opensaf-users@lists.sourceforge.net
*Subject:* Re: [users] Max timeout limit problem in the "headless 
cluster" feature

Hi,

I opened a defect ticket for this.

https://sourceforge.net/p/opensaf/tickets/2130/

Regards,

Hung Nguyen - DEK Technologies



From: Jianfeng dongjd...@juniper.net 

Sent: Tuesday, October 18, 2016 11:47PM

To: Opensaf-users

 opensaf-users@lists.sourceforge.net 


Cc: Jianfeng Dong

 jd...@juniper.net 

Subject: [users] Max timeout limit problem in the "headless cluster" feature

Hi,

Now we are trying to apply OpenSAF's new feature "headless cluster" in our 
product, but we find out "IMMSV_SC_ABSENCE_ALLOWED"(saved in a 16 bit unsigned 
variable) can be set no more than 65535 which means only 18 hours. We think 
it's too short for our product in some special cases, in those cases we want 
payload card to work as long as possible in "headless" mode. We checked OpenSAF 
source code and find this 16 bit unsigned variable should be able to change to 
32bit unsigned type, with this change we can prevent payload from 
auto-rebooting for a enough long time till the controller come back, and this 
change should be not much risky .

So, could you please change to save "IMMSV_SC_ABSENCE_ALLOWED" into a 32bit 
unsigned variable to keep payload continue running more than 18 hours in 
"headless" mode? Thanks!

Much appreciate to any comment!

Regards,

Jianfeng Dong

--

Check out the vibrant tech community on one of the world's most

engaging tech sites, SlashDot.org!http://sdm.link/slashdot

___

Opensaf-users mailing list

Opensaf-users@lists.sourceforge.net 


https://lists.sourceforge.net/lists/listinfo/opensaf-users


--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users

Re: [users] Max timeout limit problem in the "headless cluster" feature

[Jianfeng Dong]

Much appreciate!

I notice the milestone is 5.0.2, but the fix code of this ticket will go into 
5.1.0 as well, right?

Regards,
Jianfeng

From: Hung Nguyen [mailto:hung.d.ngu...@dektech.com.au]
Sent: Thursday, October 20, 2016 6:48 PM
To: Jianfeng Dong ; opensaf-users@lists.sourceforge.net
Subject: Re: [users] Max timeout limit problem in the "headless cluster" feature


Hi,



I opened a defect ticket for this.

https://sourceforge.net/p/opensaf/tickets/2130/



Regards,

Hung Nguyen - DEK Technologies




From: Jianfeng Dong jd...@juniper.net

Sent: Tuesday, October 18, 2016 11:47PM

To: Opensaf-users


opensaf-users@lists.sourceforge.net

Cc: Jianfeng Dong

jd...@juniper.net

Subject: [users] Max timeout limit problem in the "headless cluster" feature





Hi,



Now we are trying to apply OpenSAF's new feature "headless cluster" in our 
product, but we find out "IMMSV_SC_ABSENCE_ALLOWED"(saved in a 16 bit unsigned 
variable) can be set no more than 65535 which means only 18 hours. We think 
it's too short for our product in some special cases, in those cases we want 
payload card to work as long as possible in "headless" mode. We checked OpenSAF 
source code and find this 16 bit unsigned variable should be able to change to 
32bit unsigned type, with this change we can prevent payload from 
auto-rebooting for a enough long time till the controller come back, and this 
change should be not much risky .



So, could you please change to save "IMMSV_SC_ABSENCE_ALLOWED" into a 32bit 
unsigned variable to keep payload continue running more than 18 hours in 
"headless" mode? Thanks!



Much appreciate to any comment!



Regards,

Jianfeng Dong

--

Check out the vibrant tech community on one of the world's most

engaging tech sites, SlashDot.org! http://sdm.link/slashdot

___

Opensaf-users mailing list

Opensaf-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/opensaf-users

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users

Re: [users] Max timeout limit problem in the "headless cluster" feature

[Hung Nguyen]

Hi,

I opened a defect ticket for this.
https://sourceforge.net/p/opensaf/tickets/2130/

Regards,

Hung Nguyen - DEK Technologies



From: Jianfeng Dong jd...@juniper.net
Sent: Tuesday, October 18, 2016 11:47PM
To: Opensaf-users
 opensaf-users@lists.sourceforge.net
Cc: Jianfeng Dong
 jd...@juniper.net
Subject: [users] Max timeout limit problem in the "headless cluster" feature


Hi,

Now we are trying to apply OpenSAF's new feature "headless cluster" in our 
product, but we find out "IMMSV_SC_ABSENCE_ALLOWED"(saved in a 16 bit unsigned 
variable) can be set no more than 65535 which means only 18 hours. We think 
it's too short for our product in some special cases, in those cases we want 
payload card to work as long as possible in "headless" mode. We checked OpenSAF 
source code and find this 16 bit unsigned variable should be able to change to 
32bit unsigned type, with this change we can prevent payload from 
auto-rebooting for a enough long time till the controller come back, and this 
change should be not much risky .

So, could you please change to save "IMMSV_SC_ABSENCE_ALLOWED" into a 32bit 
unsigned variable to keep payload continue running more than 18 hours in 
"headless" mode? Thanks!

Much appreciate to any comment!

Regards,
Jianfeng Dong
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users


--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Opensaf-users mailing list
Opensaf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-users