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
wrote:
> On Tue, Dec 9, 2014 at 9:48 AM, Rajani Karuturi wrote:
> >>
> >> > Or make this configurable and update it in the docs
On Tue, Dec 9, 2014 at 9:48 AM, Rajani Karuturi 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 responsibilty to t
>
> > 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
mobile dev with bilingual spelling checker used (read at your own risk)
Op 9 dec. 2014 05:43 schreef "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 relea
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 docs
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 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 PM, Daan Hoogland wr
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 PM, Daan Hoogland wrote:
> 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
> MinVRVersio
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 wrote:
> In 4.3 it's defined as _minVRVersion. For each major ACS version such as ACS
> 4.4.x, this val
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
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 wrote:
> This should probably happen in 4.5 branch as well I guess?
>
> --
> Erik
>
> On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland
> wr
This should probably happen in 4.5 branch as well I guess?
--
Erik
On Mon, Dec 8, 2014 at 2:51 PM, Daan Hoogland
wrote:
> 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 ver
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 branch
12 matches
Mail list logo
