Thanks everyone, we'll go with that option.
Cheers!
paul.an...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
-Original Message-
From: Will Stevens
Sent: 24 June 2019 16:20
To: dev@cloudstack.apache.org
Subject: Re: [VOTE][RESULT] Apa
+1 for keeping 4.11.3.0 and rereleasing...
On Mon, Jun 24, 2019, 10:38 AM Gabriel Beims Bräscher
wrote:
> +1 on keeping the release name as 4.11.3.0.
>
> Em seg, 24 de jun de 2019 às 11:27, Wei ZHOU
> escreveu:
>
> > I vote for 4.11.3.0
> >
> > -Wei
> >
> >
> >
> > Paul Angus 于2019年6月24日周一 下午3
+1 on keeping the release name as 4.11.3.0.
Em seg, 24 de jun de 2019 às 11:27, Wei ZHOU
escreveu:
> I vote for 4.11.3.0
>
> -Wei
>
>
>
> Paul Angus 于2019年6月24日周一 下午3:43写道：
>
> > Hi,
> >
> > Does anyone have any strong views on whether we should look to nullify
> > 4.11.3.0 as it was never in t
I vote for 4.11.3.0
-Wei
Paul Angus 于2019年6月24日周一 下午3:43写道：
> Hi,
>
> Does anyone have any strong views on whether we should look to nullify
> 4.11.3.0 as it was never in the wild, or should be go to 4.11.3.1 ?
>
> Many thanks
>
>
> Paul Angus
>
>
>
>
>
>
>
> paul.an...@shapeblue.com
> www.sh
Paul, a commitsgh has been published and could be used from just that mail.
I would go for a new release name. Whether that is 4.11.3.1 or something
else is of little consequence. (€0.02)
On Mon, Jun 24, 2019 at 3:43 PM Paul Angus wrote:
> Hi,
>
> Does anyone have any strong views on whether we
Hi,
Does anyone have any strong views on whether we should look to nullify 4.11.3.0
as it was never in the wild, or should be go to 4.11.3.1 ?
Many thanks
Paul Angus
paul.an...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
-Origi
Thanks for sharing Gregor. My/our bad, I was suspicious of how the templates
were setup based on your emails and did not think what you shared could be
something to do with the DB upgrade path bug.
Regards,
Rohit Yadav
Software Architect, ShapeBlue
https://www.shapeblue.com
> https://github.com/apache/cloudstack/pull/3417
>
>
> The issue only affects 4.11.2.0 users for which the upgrade path does
> not run (a noop upgrade path runs) and it does not automatically fix
> any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> mentioned workaround steps
Hi, Community
We have a environment with XenServer 7.1LTS + ACS 4.11.2, some hosts has
multiple Nividia P4 graphic cards installed.
Per business requirement, we need provision VM with passthrough GPUs. We
expect to provide users various offerings, e.g. 1GPU/VM, 2GPU/VM... but it
se
Li,
please test with Indirect.agent.lb.check.interval=60 or similar, not 0
(zero), since that means it won't reconnect - this should solve your
concern.
As for the what is in what rack, it is your responsibility to disperse
infrastructure components appropriately, i.e. across racks and such.
We
Thanks Paul, however, I've found a bug in 4.11.3.0 packages that I could only
find while upgrading my local ci-test env:
https://github.com/apache/cloudstack/pull/3417
The issue only affects 4.11.2.0 users for which the upgrade path does not run
(a noop upgrade path runs) and it does not auto
11 matches
Mail list logo
