On April 29, 2014, 12:29 p.m., Santhosh Edukulla wrote:
Ship It!
Santhosh Edukulla wrote:
If we don't have any review issues pending, can some body with commit
rights push this patch?
Santhosh Edukulla wrote:
Saurav,
Please update BugId and Branch fields. This
H,
I tried merging 4.4-forward back into 4.4. This leaves us with a grand
big conflict. I have calculated that the number of not cherry-picked
not reverted commits is 185. I will start cherry-picking them at
moments $dayjob allows. and then send a mail again.
don't forget to read up on the
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23805/
---
(Updated July 28, 2014, 10:11 a.m.)
Review request for cloudstack, Alena
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23805/
---
(Updated July 28, 2014, 10:12 a.m.)
Review request for cloudstack, Alena
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23976/
---
Review request for cloudstack and Santhosh Edukulla.
Bugs: CLOUDSTACK-7190
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23976/#review48837
---
Ship it!
Ship It!
- sanjeev n
On July 28, 2014, 10:34 a.m.,
H,
I see a lot of commits happening directly on the master branch. Yet
there were no counter arguments against the proposed gitflow and the
discussion around it. This leaves me with the idea that the thread is
largely ignored by the community. It is my understanding that we
agreed never to commit
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23976/#review48839
---
Commit 57ee142dede5be035a4501dcfb0816c9bfb8ddaa in cloudstack's
Please see virtualbox forums for support with this.
https://forums.virtualbox.org/viewtopic.php?f=6t=62615start=75
On 28 July 2014 04:48, Priyanka Deepala priyanka.deepal...@gmail.com
wrote:
Hello
I'm trying to install virtualbox in windows7 but while running the
virtualbox it is
On Mon, Jul 28, 2014 at 1:22 PM, Daan Hoogland daan.hoogl...@gmail.com
wrote:
H,
I see a lot of commits happening directly on the master branch. Yet
there were no counter arguments against the proposed gitflow and the
discussion around it. This leaves me with the idea that the thread is
+1 to what Erik said.
On 28 July 2014 13:04, Erik Weber terbol...@gmail.com wrote:
On Mon, Jul 28, 2014 at 1:22 PM, Daan Hoogland daan.hoogl...@gmail.com
wrote:
H,
I see a lot of commits happening directly on the master branch. Yet
there were no counter arguments against the proposed
Don't be to sure Ian,
There is about 180 changes in 4.4-forward that did not go in 4.4 yet
On Mon, Jul 28, 2014 at 2:05 PM, Ian Duffy i...@ianduffy.ie wrote:
I believe no, atleast the latest changes under master or 4.4-forward.
Alright, Thanks. I believe all changes for it within 4.4-forward
I wonder if we need to move this to its own release as we did with cloudmonkey?
--David
On Mon, Jul 28, 2014 at 8:05 AM, Ian Duffy i...@ianduffy.ie wrote:
I believe no, atleast the latest changes under master or 4.4-forward.
Alright, Thanks. I believe all changes for it within 4.4-forward
Hi,
I think since the Marvin package tightly depends on CloudStack, it's
release can happen along with CloudStack release.
@Prasanna -- Can you add couple of people as owner/admins to the
cloudstack-marvin pypi package?
Regards.
David Nalley wrote:
I wonder if we need to move this to its own
Before we start with Marvin releases we should discuss versioning i think.
At the moment all marvin packages are shipped with version 1.0, if we want to
take marvin releases serious we need to start with versions whenever the
something in marvin changes.
Cheers.
Hugo
On 28 jul. 2014, at
Agreed, this kind of important decisions should be made by a vote.
Sebastien, Daan, can one of you kick of the vote thread? Preferably with a
condensed summary of the thread?
Cheers,
Hugo
On 28 jul. 2014, at 14:07, Ian Duffy i...@ianduffy.ie wrote:
+1 to what Erik said.
On 28 July
Hi Hugo,
Does it make sense to simply use the same version as CloudStack from
next Marvin releases? This is because with each CloudStack release and
possible API changes, the Marvin cloudstackAPI python module will
change. Other than that there are couple of API marshaling/unmarshaling,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23805/#review48842
---
Looks good, let me get my office lab to work and then I can test.
+1 to use same version number for Marvin package as Cloudstack release.
-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
Sent: Monday, July 28, 2014 5:34 AM
To: dev@cloudstack.apache.org
Cc: Prasanna Santhanam
Subject: Re: Marvin Package?
Hi Hugo,
Does it make
Sounds good to me.
Cheers,
Hugo
On 28 jul. 2014, at 14:33, Rohit Yadav rohit.ya...@shapeblue.com wrote:
Hi Hugo,
Does it make sense to simply use the same version as CloudStack from
next Marvin releases? This is because with each CloudStack release and
possible API changes, the Marvin
GitHub user terbolous opened a pull request:
https://github.com/apache/cloudstack-docs-install/pull/18
Updated systemvm template paths
The referenced systemvm paths are old, and contain heartbleed.
Updated with newer, but still 4.3, templates.
You can merge this pull
On July 28, 2014, 12:43 p.m., Rohit Yadav wrote:
api/src/org/apache/cloudstack/api/command/user/address/ListPublicIpAddressesCmd.java,
lines 205-207
https://reviews.apache.org/r/23805/diff/1/?file=639247#file639247line205
This was removed.
I deleted it because it's not being
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23879/#review48850
---
Commit d5220a88a085385ebc4b783a40f27d128ea7d28f in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23606/#review48847
---
Commit 843e60475798a2cb06daeaa00708c816fb819650 in cloudstack's
Yeah, I was under the impression this decision would require a vote and
formal announcement, if it passes.
On Monday, July 28, 2014, Hugo Trippaers h...@trippaers.nl wrote:
Agreed, this kind of important decisions should be made by a vote.
Sebastien, Daan, can one of you kick of the vote
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23882/#review48849
---
Commit 724c8dc7c98574dcdf669c0c2d7549981667ab77 in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23608/#review48848
---
Commit e9d658e16edbe55a380aefa779c89d690b368d24 in cloudstack's
104 commits did not pick cleanly after applying the folowing:
for i in $(../commitsToPick.lst)
do
git cherry-pick -x --allow-empty $i || ( echo $i ../failed.picks
git cherry-pick --abort )
done
4a85e2226436c62e781db3449d262cb385b977c1
66f8e0e1b5c81cbfde926c0c65c4d5969767cab9
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23982/
---
Review request for cloudstack, sanjeev n and Santhosh Edukulla.
Bugs:
Let me explain a little more about this lat mail of mine.
I was assuming a lot of context that most people may not have.
We want to start working differently with respect to our release
procedure and branching habits. The proposals that are out there and
about to be voted for are going to require
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/20701/#review48855
---
Commit 8fb89cdc8e2dff60d49fecd3e51a9bf997061035 in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23195/#review48856
---
Commit 75d2a331ee5876c3c456c8a3c12258c3b8f07f00 in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22614/#review48857
---
Commit 8c37e46807b92ac32c63cd36d33ca5d68bb75f30 in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/22554/#review48858
---
Commit 2fdf789a28ce01571eabd5ccb8edfea72624ea3c in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23613/#review48859
---
Commit e33d4a5732e81f590489f37b7fbcc947d2929de6 in cloudstack's
commited three or so by hand and ran my script again.
now 77 are still missing from 4.4
will do some more later this week.
4f1f182cba5579da2fc7ce1f02019a0afa00efeb
9bba24812e4f58e6c503010823533b8e0047ea2a
948b81fb51206b516caf1ff92a1a3dddc9f67a9b
18367b3a8614d39d6323f140fc50875230bb060a
Hi
I've had it wrong in the release-notes for system vm templates. used and
old outdated ones.
Also the Install guide point to outdated templates. I'll fix documentations
today hopefully, although, Which one should I used ?
Should we refer to those ones:
Hi,
It took me sometime to go through all the 58 emails on this thread.
I suggest we need to adapt gitflow to our git workflow. I liked the
summary Rajani suggested here: http://markmail.org/message/2642ilfajkpshnfn
Let's continue the discussion in the new thread now:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23985/
---
Review request for cloudstack.
Repository: cloudstack-git
Description
Hi Daan,
We've a page on Git [1] and recommended workflow for committers and
non-committers, should we update the workflow we want for committers
there and start a separate vote thread?
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Git
Regards.
Daan Hoogland wrote:
Let me
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23986/
---
Review request for cloudstack, Doug Clark, Raja Pullela, Rayees Namathponnan,
I am +1 on the principle.
--
Stephen Turner
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: 28 July 2014 16:08
To: dev
Subject: Re: [DISCUSS] git commit proces
Let me explain a little more about this lat mail of mine.
I was assuming a lot of context that
+1 on same version, makes sense to me.
On 28 July 2014 13:55, Hugo Trippaers h...@trippaers.nl wrote:
Sounds good to me.
Cheers,
Hugo
On 28 jul. 2014, at 14:33, Rohit Yadav rohit.ya...@shapeblue.com wrote:
Hi Hugo,
Does it make sense to simply use the same version as CloudStack
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23884/#review48880
---
Commit f1039b782e5fdef8129088929c42fdf2f2909b5a in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23884/#review48881
---
Ship it!
Ship It!
- Jessica Wang
On July 24, 2014, 11:51 a.m.,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23991/
---
Review request for cloudstack.
Bugs: CLOUDSTACK-7195
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23922/#review48886
---
Commit 32e8fda965252322eccda01e14f854051d665ed0 in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23922/#review48887
---
Ship it!
Ship It!
- Jessica Wang
On July 25, 2014, 9:58 a.m.,
Hello,
I had setup cloudstack 4.4 environment which was running fine.
I recently did a git pull to get the updates after which when I tried to mvn
-Pdeveloper -pl developer -Ddeploydb I was encountering with the following
error.
[ERROR] Failed to execute goal
See http://jenkins.buildacloud.org/job/build-master-noredist/3173/changes
Changes:
[anthony.xu] completed the new vmsync TODOs in the code.
--
[...truncated 5892 lines...]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
Will,
this is a bug due to our upgrade scheme: we have not yet implemented
it so it is missing. We need to implement some (possibly empty)
upgrade path to make sure this will still work for 4.4.1.
On Mon, Jul 28, 2014 at 9:46 PM, Will Stevens wstev...@cloudops.com wrote:
I am guessing this is a
Rohit,
Let's change the howto-use-git page after the vote.
On Mon, Jul 28, 2014 at 6:47 PM, Stephen Turner
stephen.tur...@citrix.com wrote:
I am +1 on the principle.
--
Stephen Turner
-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: 28 July 2014
If there is documentation for how to do this somewhere, I could implement
an empty upgrade path. Do we know if there are database changes needed for
the 4.4.1 upgrade from 4.4.0? How would that requirement be captured?
Cheers,
Will
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud
Hi Jaya,
Which branch are you on? It's a bug we'll fix it by placing an empty
upgrade path for 4.4.1 version.
The upgrade paths are available only between released versions only, so
it fails as there is no upgrade path for 4.4.1-SNAPSHOT.
Regards.
Elapavuluri, Jaya wrote:
Hello,
I had
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/20659/#review48899
---
Commit 4a99cf851966512ae90633b7ed7d7954b6d0ac9a in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23677/#review48901
---
Commit f055ec52d9d751df86e42aeb6a2aace2ceea4567 in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23611/#review48900
---
Commit 6b66fe92ca89633ec64397cedb0d1572d0089c93 in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23793/#review48902
---
Commit 1ca9abd6dc8013dd1dc4e4f9ca1eabb71785cc37 in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23885/#review48904
---
Commit 2025f359c4fbff6b24132d39e8cf587315a2a981 in cloudstack's
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23814/#review48903
---
Commit 58987452994f1abc621a2f8f7fcdd24b443cf0e9 in cloudstack's
Hi,
Adding upgrade paths is simple (you may add/update a wiki page on it):
- You add a upgrade path class under com.cloud.upgrade.dao, something
like UpgradeVERAtoVERb, in our case Upgrade440to441 which should
implement the interface DbUpgrade. If there is some complex migration
you need to do
The upgrade path should also be merged to master branch. Where btw I
already see an upgrade path from 4.4 to 4.5 implemented. Should we change
it to 4.4.1-4.5?
-Alena.
On 7/28/14, 2:54 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
Hi,
Adding upgrade paths is simple (you may add/update a
Hi Alena,
I've changed the upgrade path from 4.4.1 to 4.5.0, please verify at your
end especially the DatabaseUpgradeChecker since there are too many list
of upgrade path class changes.
On master: d42e20429d1e238816a07edd865567c06a4914d3
Regards.
Alena Prokharchyk wrote:
The upgrade path
Will do, thank you, Rohit.
-Alena.
On 7/28/14, 3:23 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote:
Hi Alena,
I've changed the upgrade path from 4.4.1 to 4.5.0, please verify at your
end especially the DatabaseUpgradeChecker since there are too many list
of upgrade path class changes.
On
See http://jenkins.buildacloud.org/job/build-master-noredist/3174/changes
Changes:
[Alena Prokharchyk] DB upgrade - added a path from 4.4.0 to 4.4.5
[Alena Prokharchyk] listNetworks: moved pagination post processing to
StringUtils class
[Alena Prokharchyk] CS-19072: fixed broken pagination
See http://jenkins.buildacloud.org/job/build-master-noredist/3175/changes
Changes:
[Rohit Yadav] schema: add upgrade path from 4.4.0 to 4.5.0 via 4.4.1
[Alena Prokharchyk] CS-19072: fixed broken pagination and count in listVpcs
--
[...truncated 5892
Just one thing was missing - upgrade path from 4.4.1-4.5, I’ve added it
to DataBaseUpgradeChecker:
_upgradeMap.put(4.4.1, new DbUpgrade[] { new Upgrade441to450() });
-Alena.
On 7/28/14, 3:26 PM, Alena Prokharchyk alena.prokharc...@citrix.com
wrote:
Will do, thank you, Rohit.
-Alena.
On
Hi,
I am working on 4.4 branch.
-Original Message-
From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
Sent: Monday, July 28, 2014 5:10 PM
To: dev@cloudstack.apache.org
Subject: Re: building cloudstack
Hi Jaya,
Which branch are you on? It's a bug we'll fix it by placing an empty
See http://jenkins.buildacloud.org/job/build-master-noredist/3176/
--
[...truncated 5892 lines...]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
cloud-plugin-network-vsp ---
[debug] execute contextualize
[INFO] Using 'UTF-8'
See http://jenkins.buildacloud.org/job/build-master-noredist/3177/changes
Changes:
[Alena Prokharchyk] Added upgrade path from 4.4.1 to 4.5
[sheng.yang] CLOUDSTACK-7186: Revert CLOUDSTACK-7182: NPE while trying to
deploy VMs in parallel in isolated network
Tried helping Soeren Malchow on irc today, with a new ACS44 installation.
The docs referenced ACS43 system templates from January, but even by using
the late June ones that got uploaded after the heartbleed incident it still
does not work.
The error message is: Unsupported major.minor version
See http://jenkins.buildacloud.org/job/build-master-noredist/3178/changes
Daan,
4.4-forward should contain all the commits for 4.4. So 4.4-forward itself
should be able to make as 4.4, without merge back to 4.4?
That's what we want to have a 4.4-forward for 4.4. future release. It's
superset of current 4.4 branch.
Well, probably result in a force-overwrite. But I
This is my thinking, as well.
In theory, 4.4-forward should be a superset of 4.4.
I don't think merging is required.
On Mon, Jul 28, 2014 at 7:28 PM, Sheng Yang sh...@yasker.org wrote:
Daan,
4.4-forward should contain all the commits for 4.4. So 4.4-forward itself
should be able to make
Github user pdion891 commented on the pull request:
https://github.com/apache/cloudstack-docs-install/pull/14#issuecomment-50424672
PR completed but github is not yet sync.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user pdion891 commented on the pull request:
https://github.com/apache/cloudstack-docs-install/pull/18#issuecomment-50424664
PR completed but github is not yet sync.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Hi,
My student for GSoC, Seif, was interested in adding this control to
CloudStack's GUI codebase:
http://loopj.com/jquery-tokeninput/
He's already written a new API command that retrieves a list of storage
tags (in addition to other work for GSoC).
Ideally he would be able to augment a couple
Just to add a bit more detail:
Seif is looking to create a new dialog that can utilize this control. One
could access this new dialog - perhaps - by clicking on a new button to the
right of the Storage Tags text field (ex. in the Add Primary Storage
dialog). This new dialog would utilize the new
there is 2 hyper-V systemvm template availables: .vhd, .vhd.zip at
http://cloudstack.apt-get.eu/systemvm/4.4/
So, I've download both, but it turn out that the template .vhd file don't
have the same size at the end of the process in both cases. Please see the
cutpaste result.
Yes that's how I did for 4.2 and 4.3
Sent from my iPhone
On Jul 28, 2014, at 6:28 PM, Sheng Yang
sh...@yasker.orgmailto:sh...@yasker.org wrote:
Daan,
4.4-forward should contain all the commits for 4.4. So 4.4-forward itself
should be able to make as 4.4, without merge back to 4.4?
That's
Sorry guys, I haven't followed up the thread. But I think we probably jump
to conclusion too quickly. I found the discussion mostly took place later
last week. I'm afraid not enough people aware of what's happening.
I am trying to catch up, by reading the thread and checking what's gitflow
etc,
I don't like the idea. release (candidates) are on 4.4
On Tue, Jul 29, 2014 at 5:43 AM, Animesh Chaturvedi
animesh.chaturv...@citrix.com wrote:
Yes that's how I did for 4.2 and 4.3
Sent from my iPhone
On Jul 28, 2014, at 6:28 PM, Sheng Yang sh...@yasker.org wrote:
Daan,
4.4-forward
Every commit in 4.4 is from 4.4-forward, that's why we create 4.4-forward I
think?
--Sheng
On Mon, Jul 28, 2014 at 9:44 PM, Daan Hoogland daan.hoogl...@gmail.com
wrote:
I don't like the idea. release (candidates) are on 4.4
On Tue, Jul 29, 2014 at 5:43 AM, Animesh Chaturvedi
Then what about all fixes that went into 4.4-forward if they don't get picked
up that contribution will not be used at all.
Sent from my iPhone
On Jul 28, 2014, at 9:45 PM, Daan Hoogland daan.hoogl...@gmail.com wrote:
I don't like the idea. release (candidates) are on 4.4
On Tue, Jul 29,
84 matches
Mail list logo
