Re: [ACS44] router upgrade issue

2014-12-09 Thread Rajani Karuturi
Or make this configurable and update it in the docs to use the latest template version? Configurable sound allright but the config action must be the same as the sysvm install action or we are shifting our responsibilty to the user. The advantage I see with this is we need not do a patch

Re: [ACS44] router upgrade issue

2014-12-09 Thread Daan Hoogland
On Tue, Dec 9, 2014 at 9:48 AM, Rajani Karuturi raj...@apache.org wrote: Or make this configurable and update it in the docs to use the latest template version? Configurable sound allright but the config action must be the same as the sysvm install action or we are shifting our

Re: [ACS44] router upgrade issue

2014-12-09 Thread Rajani Karuturi
I understand the problem now and agree that configurable isnt an option here. Thanks for sharing your thoughts. ~Rajani On Tue, Dec 9, 2014 at 3:03 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: On Tue, Dec 9, 2014 at 9:48 AM, Rajani Karuturi raj...@apache.org wrote: Or make this

[ACS44] router upgrade issue

2014-12-08 Thread Daan Hoogland
H, I investigated an issue some colleagues noticed and it turns out that in the update procedure the flag VirtualNetworkApplianceService.MinVRVersion is not set for versions 4.4.0-4.4.2 I have no workaround other then rebooting the routers instead of upgading/updating them. I will patch the

Re: [ACS44] router upgrade issue

2014-12-08 Thread Erik Weber
This should probably happen in 4.5 branch as well I guess? -- Erik On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: H, I investigated an issue some colleagues noticed and it turns out that in the update procedure the flag

Re: [ACS44] router upgrade issue

2014-12-08 Thread Daan Hoogland
I am looking if the value 4.4.1 is applicable there or whether it should be higher, as we mail. will update you all. On Mon, Dec 8, 2014 at 3:12 PM, Erik Weber terbol...@gmail.com wrote: This should probably happen in 4.5 branch as well I guess? -- Erik On Mon, Dec 8, 2014 at 2:51 PM, Daan

Re: [ACS44] router upgrade issue

2014-12-08 Thread Rohit Yadav
In 4.3 it's defined as _minVRVersion. For each major ACS version such as ACS 4.4.x, this value should be 4.4.0 unless we want to use higher templates such as 4.4.1 or 4.4.2. For 4.5, it should be 4.5.0. This is assuming that ACS templates are compatible with future bugfix releases and we don't

Re: [ACS44] router upgrade issue

2014-12-08 Thread Daan Hoogland
Rohit, in 4.4 there was a problem with the templates in 4.4.0 so it must be 4.4.1. I don't see the underscore but a capital M in MinVRVersion in 4.4! On Mon, Dec 8, 2014 at 3:31 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote: In 4.3 it's defined as _minVRVersion. For each major ACS version such

Re: [ACS44] router upgrade issue

2014-12-08 Thread Daan Hoogland
I see some changes that make me want to put 4.5.0 in there for the 4.5 branch. proceding On Mon, Dec 8, 2014 at 3:35 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: Also I don't think we need to let users go through a sysvm upgrade procedure if it is not needed. On Mon, Dec 8, 2014 at 3:34

Re: [ACS44] router upgrade issue

2014-12-08 Thread Rajani Karuturi
This looks like recurring problem we are going to face again in the future version. Especially given that its so deep in a java file, its very easy to slip it for a release. Can we use the max version of a 'completed' step from the version table? Or make this configurable and update it in the

Re: [ACS44] router upgrade issue

2014-12-08 Thread Daan Hoogland
mobile dev with bilingual spelling checker used (read at your own risk) Op 9 dec. 2014 05:43 schreef Rajani Karuturi raj...@apache.org: This looks like recurring problem we are going to face again in the future version. Especially given that its so deep in a java file, its very easy to slip it