Only one table will be affected.
On 16-Nov-2014, at 3:14 am, Amogh Vasekar amogh.vase...@citrix.com wrote:
Question - What happens to the already existing VMs with entries in the
DB? Do we keep it NULL?
NULL will be and not useful. I think it should be okay to have a db migration
path that
TL;DR: Devcloud 4 cleaned up a bit, chef attributes no longer hidden,
further user customisation allowed, Testers wanted.
** advanced zone on 4.4.* isn't supported due to a change on some API param
for setting tags on interfaces **
Hi All,
Hi All,
Just out of interest, is there some reason we don't include the users
mailing list within vote threads for feedback around product stability?
From what I've seen a lot of them have test labs. It would be nice to get
their feedback before releasing rather than after...
Thanks,
Ian
+1
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
From: Ian Duffy i...@ianduffy.ie
To: CloudStack Dev dev@cloudstack.apache.org
Sent: Sunday, 16 November, 2014 16:20:55
Subject: [QUESTION] How come we don't include Users@ in vote threads?
I'm not sure about adding users@ into the vote since it's more dev@
related. But, I agree it would be nice to notify users@ that we have an RC
it would potentially involved more people in the test phases.
On Sun, Nov 16, 2014 at 12:56 PM, Rohit Yadav rohit.ya...@shapeblue.com
wrote:
On
I think the general problem here is that for each voting candidate adding
users@ML would be only useful if we also build a deb/rpm repo for them to
test the voting candidate so everyone won’t have to build their own
CloudStack. My suggestion is to do that, and I think we can have the
testing
Hi Ian,
I'm trying it as it seams quite strait forward. although, the instruction
to install cloudstack [1]: I should run that in the management VM right,
not locally ? does IPs are hardcoded somewhere?
Thanks, that's awesome to have a local cloudstack running without effort.
I'm testing this on
Hi Pierre,
So advanced and basic are running from code on the host machine. Only a
NFS, MySQL and hypervisor box is supplied.
Testing is for binary-installation-advanced and binary-installation-basic.
On 16 November 2014 19:44, Pierre-Luc Dion pd...@cloudops.com wrote:
Hi Ian,
I'm trying it
Den søndag 16. november 2014 skrev Pierre-Luc Dion pdion...@apache.org
følgende:
I'm not sure about adding users@ into the vote since it's more dev@
related. But, I agree it would be nice to notify users@ that we have an RC
it would potentially involved more people in the test phases.
I must
I agree that more tests are welcome, we have to try then :)
Afaik non-pmc's aren't binding and any votes would merely be an
indication,
or do i misunderstand?
All votes are important [1] and count as indicator, who ever vote mean
something, It also show that the community members did some
I'm trying to build 4.4.2 from 4.4 branch. I'm having the db deployment
error that schema-441to442.sql does not exist. Could it be the cause of the
problem you are seeing too ?
On Fri, Nov 14, 2014 at 8:57 AM, Daan Hoogland daan.hoogl...@gmail.com
wrote:
I run into a strange exception during
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/28114/
---
Review request for cloudstack and Kishan Kavala.
Bugs: CLOUDSTACK-7923
On Sun, Nov 16, 2014 at 11:44 PM, Pierre-Luc Dion pdion...@apache.org
wrote:
I agree that more tests are welcome, we have to try then :)
On the other side, how many devs can say that they really like to do
thorough release testing? My guess is that it's a rather small number.
By adding users,
My suggestions and comments;
- Build a rpm/deb repository before you start voting (we can use
packages.shapeblue.com/cloudstack/testing)
- Tag each Voting Candidate (using a -vc or -rc suffix followed by the round
number, for example 4.4.2-rc-01) and we build rpm/deb repo using tags.
- This
14 matches
Mail list logo
