Re: Review Request 24313: CLOUDSTACK-7255: Fixed marvin issue related to creating random account usernames

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24313/#review49711 --- Gentle Reminder - Gaurav Aradhye On Aug. 5, 2014, 7:37 p.m., Gaur

Re: Review Request 24298: CLOUDSTACK-6873: Moved test cases that run only on simulator and those should be run serially to misc folder and also tagged them with required_hardware='simulator only'

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24298/#review49712 --- Gentle Reminder - Gaurav Aradhye On Aug. 5, 2014, 8:43 p.m., Gaur

Re: Review Request 24232: Removing invalid and unused import from test_escalations_templates.py

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24232/#review49713 --- Gentle Reminder - Gaurav Aradhye On Aug. 5, 2014, 6:28 p.m., Gaur

Re: Review Request 24302: CLOUDSTACK-7241: Fixed error in test_escalations_ipaddresses.py

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24302/#review49714 --- Gentle Reminder - Gaurav Aradhye On Aug. 5, 2014, 5:34 p.m., Gaur

Build failed in Jenkins: simulator-singlerun #62

See -- [...truncated 7278 lines...] [INFO] [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (default) @ cloud-developer --- [WARNING] Ignoring missing properties file:

Build failed in Jenkins: simulator-hotfix-trigger #14

See Changes: [Daan Hoogland] README: some sections from the prior version copied back in. -- [...truncated 7093 lines...] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-che

[ACS44] release 4.4.1

People, Since there are some problems in 4.4.0 I am planning a bugfix release. I created a wiki page for it. This only contains dates so far. I am offline starting the 16th so I want to have it out by the 14th, optimist that I am. For this to happen a successful RC must be available by the 10th.

Re: Locking Down Hypervisor

On 08/05/2014 11:51 PM, mo wrote: Hello, Is it permutable to install SSH keys on the hypervisor. Does Cloudstack speak often to the hypervisor, as I have ALL in one, KVM Centos 6.5 No problem. The management server doesn't require SSH access into the hypervisor after installation. Wido

Re: Review Request 24313: CLOUDSTACK-7255: Fixed marvin issue related to creating random account usernames

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24313/ --- (Updated Aug. 6, 2014, 3:19 p.m.) Review request for cloudstack and Santhosh Ed

Jenkins build is unstable: simulator-singlerun #63

See

Re: Review Request 24302: CLOUDSTACK-7241: Fixed error in test_escalations_ipaddresses.py

> On Aug. 6, 2014, 7:09 a.m., Gaurav Aradhye wrote: > > Gentle Reminder Pushed to master.dda2820..adcfdf2 master -> master - Santhosh --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24302/#r

Re: Review Request 24302: CLOUDSTACK-7241: Fixed error in test_escalations_ipaddresses.py

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24302/#review49720 --- Commit adcfdf2547ffccced8bcb06a627274bbb0664d7c in cloudstack's bran

Re: Review Request 24298: CLOUDSTACK-6873: Moved test cases that run only on simulator and those should be run serially to misc folder and also tagged them with required_hardware='simulator only'

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24298/#review49721 --- test/integration/smoke/misc/test_deploy_vm.py

Re: Review Request 24232: Removing invalid and unused import from test_escalations_templates.py

> On Aug. 6, 2014, 7:09 a.m., Gaurav Aradhye wrote: > > Gentle Reminder adcfdf2..c38a15f master -> master - Santhosh --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24232/#review49713 -

[DB-CHANGE] Infrastructure tab fails to load with db exception

I remember we used to follow the practice of informing others in case db changes are committed, but we do not do it anymore. In case you are on dev setup on master branch post the following commit : commit b9d834e83854009483f6d061f9996e5ffaa9b883 Author: Nitin Mehta Date: Tue Aug 5 17:29:34 201

Review Request 24378: CLOUDSTACK-7268: Ignore "already exists" error in createEgressFirewallRule

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24378/ --- Review request for cloudstack and Santhosh Edukulla. Bugs: CLOUDSTACK-7268

Re: Locking Down Hypervisor

Awesome, thank you! Sent from my iPhone > On Aug 6, 2014, at 5:08 AM, Wido den Hollander wrote: > > > >> On 08/05/2014 11:51 PM, mo wrote: >> Hello, >> >> Is it permutable to install SSH keys on the hypervisor. Does Cloudstack >> speak often to the hypervisor, as I have ALL in one, KVM Cent

Re: Review Request 24313: CLOUDSTACK-7255: Fixed marvin issue related to creating random account usernames

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24313/#review49724 --- Commit 0a7af329f5386fa5fb2a2f9ebc02a2ca38bb9b17 in cloudstack's bran

How to config linux native bridge to forward vxlan encapsulated pkts

Does anyone meet this issue: Create VM using vxlan for isolation guest network, both brvx-139 and vxlan139 is created, tcpdump can see the pkts has been encapsulated and forward to cloudbr1, but cloudbr1 does not forward pkts out from eth1, is there some special configuration on eth1, cloudbr1 o

Jenkins build is still unstable: simulator-singlerun #64

See

Re: master branch will be frozen for direct commits on 7 Aug 2014

Since we have seen some activity and -1s on the [vote thread], I planning to postpone this activity until we agree. [vote thread] http://markmail.org/message/3qq7ihq6pg3ii7bu ~Rajani On 05-Aug-2014, at 3:59 pm, Rajani Karuturi mailto:rajani.karut...@citrix.com>> wrote: I deleted the develop

Re: MonkeyMan-1.0.0

+ Dev ML This is great thanks for Sharing Vladimir! On 05-Aug-2014, at 10:48 pm, Vladimir Melnik wrote: > Dear colleagues, > > The 1.0.0 version has been released, the development branch has been merged > to the stable one. > > Now you can use bin/makesnapshots.pl to automatically create snaps

jenkins changes post git-flow shift

Hi all, post git flow related branching changes, we need to change the jenkins jobs which run on master to the new unstable branch(develop) everything under master tab @ http://jenkins.buildacloud.org/ should change to the new branch. looking for volunteers who can help with this. Anyone? -- ~R

Re: jenkins changes post git-flow shift

On Wed, Aug 6, 2014 at 1:39 PM, Rajani Karuturi wrote: > Hi all, > post git flow related branching changes, we need to change the jenkins jobs > which run on master to the new unstable branch(develop) > > everything under master tab @ http://jenkins.buildacloud.org/ should > change > to the new b

Re: [ACS44] release 4.4.1

On Wed, Aug 6, 2014 at 10:54 AM, Daan Hoogland wrote: > People, > > Since there are some problems in 4.4.0 I am planning a bugfix release. > > I created a wiki page for it. This only contains dates so far. I am > offline starting the 16th so I want to have it out by the 14th, > optimist that I am

Re: jenkins changes post git-flow shift

I’ll configure a new develop branch pipeline and configure jobs to check feature and hotfix branches both with the simulator and the regular builds when we create the develop branch. We don’t need to change the master build, just add another pipeline for develop. Cheers, Hugo On 6 aug. 2014

Re: DashBoard Stats

Do you look for something like the Resources tab under : Infrastructure-> Zones-> zonename -> Resources ? *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts 420 rue Guy *|* Montreal *|*

Re: jenkins changes post git-flow shift

Thanks Erik and Hugo. coverity job should be moved to develop branch. Rest all can exist both on master and develop. On Wed, Aug 6, 2014 at 5:38 PM, Hugo Trippaers wrote: > I’ll configure a new develop branch pipeline and configure jobs to check > feature and hotfix branches both with the simul

Build failed in Jenkins: simulator-singlerun #65

See Changes: [santhosh.edukulla] CLOUDSTACK-7255: Fixed marvin issue related to creating random account usernames -- [...truncated 7294 lines...] main: [INFO] Executed tasks [INFO] [INF

RE: [DB-CHANGE] Infrastructure tab fails to load with db exception

Thanks Saksham. This fixed the initial issue. But I noticed a new one, after destroying the last VR if you select the infra view it again results in exception. Not sure if anything else needs to be fixed. -Original Message- From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com]

Re: Review Request 24298: CLOUDSTACK-6873: Moved test cases that run only on simulator and those should be run serially to misc folder and also tagged them with required_hardware='simulator only'

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24298/ --- (Updated Aug. 6, 2014, 6:03 p.m.) Review request for cloudstack and Santhosh Ed

Re: Review Request 24298: CLOUDSTACK-6873: Moved test cases that run only on simulator and those should be run serially to misc folder and also tagged them with required_hardware='simulator only'

> On Aug. 6, 2014, 3:31 p.m., Santhosh Edukulla wrote: > > test/integration/smoke/misc/test_deploy_vm.py, line 85 > > > > > > why we need a new tag? Removed the new tag and assigned "simulator only" value to required_h

branch hotfix/coverity-fixes

Heya, How about we name the branches for coverity fixes after the relevant CID? Something like /hotfix/CID-xx. That would make it very easy for everyone to track which coverity fixes are tracked where and who is working on which CID. The name hotfix coverity fix is a bit too generic and w

Re: branch hotfix/coverity-fixes

Hi Hugo, +1 On a totally different issue, if we’re going to adopt git-flow let’s not use bug fix branch names with the prefix “hotfix/“ because as the per convention it’s for already released versions and for serious production issues. Instead, I recommend that we can either go with “feature/C

Re: branch hotfix/coverity-fixes

On 6 aug. 2014, at 15:06, Rohit Yadav wrote: > Hi Hugo, > > +1 > > On a totally different issue, if we’re going to adopt git-flow let’s not use > bug fix branch names with the prefix “hotfix/“ because as the per convention > it’s for already released versions and for serious production issue

Re: branch hotfix/coverity-fixes

Hey, On 06-Aug-2014, at 3:10 pm, Hugo Trippaers wrote: > > On 6 aug. 2014, at 15:06, Rohit Yadav wrote: > >> Hi Hugo, >> >> +1 >> >> On a totally different issue, if we’re going to adopt git-flow let’s not use >> bug fix branch names with the prefix “hotfix/“ because as the per convention >>

Re: branch hotfix/coverity-fixes

On 6 aug. 2014, at 15:15, Rohit Yadav wrote: > Hey, > > On 06-Aug-2014, at 3:10 pm, Hugo Trippaers wrote: > >> >> On 6 aug. 2014, at 15:06, Rohit Yadav wrote: >> >>> Hi Hugo, >>> >>> +1 >>> >>> On a totally different issue, if we’re going to adopt git-flow let’s not >>> use bug fix bran

Re: Review Request 24298: CLOUDSTACK-6873: Moved test cases that run only on simulator and those should be run serially to misc folder and also tagged them with required_hardware='simulator only'

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24298/#review49732 --- test/integration/smoke/misc/test_deploy_vm.py

Usage: Network deletion causes IP address entry to be permanently removed

Hi, When public IP range or a shared network is removed, we found that the ip address DB entries were getting permanently removed instead of being marked as released/removed. The issue is that the usage server still holds reference to these resources (ip address in this case) and listing of usa

Re: branch hotfix/coverity-fixes

Let's consider gitflow and the number of prefixes it suppprts. biligual spelling checker used.read at your own risk Op 6 aug. 2014 15:18 schreef "Hugo Trippaers" : > > On 6 aug. 2014, at 15:15, Rohit Yadav wrote: > > > Hey, > > > > On 06-Aug-2014, at 3:10 pm, Hugo Trippaers wrote: > > > >> > >>

Jenkins build is unstable: simulator-singlerun #66

See

Re: [VOTE] git workflow

Hi, Comments in-line; On 05-Aug-2014, at 10:45 pm, Alena Prokharchyk wrote: > Rayees, > > I think you have the same misunderstanding as a lot of other folks > (including myself) had in the beginning - seeing develop branch as a trunk > branch that gets merged into master on a regular basis aft

Re: How to config linux native bridge to forward vxlan encapsulated pkts

Do u turned neteork forward on? Sysctl -p can tell you the configuration On Aug 6, 2014 7:09 PM, "Michael Li" wrote: > Does anyone meet this issue: > Create VM using vxlan for isolation guest network, > both brvx-139 and vxlan139 is created, > tcpdump can see the pkts has been encapsulated and f

Re: [VOTE] git workflow

I think the core difference between your implementations is that #1 assumes that BVT/CI will catch 100% of errors, resulting in a stable master branch with no problems. Or that development changes can be blindly merged if they pass CI. The goal of git-flow is to allow a stream of development change

Re: [VOTE] git workflow

On Wed, Aug 6, 2014 at 9:41 AM, Rohit Yadav wrote: > > Hi, > > Comments in-line; > > On 05-Aug-2014, at 10:45 pm, Alena Prokharchyk > wrote: > > > Rayees, > > > > I think you have the same misunderstanding as a lot of other folks > > (including myself) had in the beginning - seeing develop branc

Build failed in Jenkins: simulator-hotfix-trigger #15

See -- [...truncated 7428 lines...] main: [INFO] Executed tasks [INFO] [INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer >>> [INFO] [INFO] --- maven-check

Re: Review Request 23982: CLOUDSTACK-7192: Skip tests on Hyper-V which don't apply

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/23982/ --- (Updated Aug. 6, 2014, 2:41 p.m.) Review request for cloudstack, sanjeev n and

Re: [VOTE] git workflow

To me this pretty much ties in to the discussion about the simulator and the BVT/CI suite. This works very neatly with the work Alex has been doing and his proposal on how to deal with the BVT test suite. His original proposal was about constantly checking master and reverting any commits that

Re: [VOTE] git workflow

Hi David, On 06-Aug-2014, at 4:10 pm, David Nalley wrote: > On Wed, Aug 6, 2014 at 9:41 AM, Rohit Yadav wrote: >> >> Hi, >> >> Comments in-line; >> >> On 05-Aug-2014, at 10:45 pm, Alena Prokharchyk >> wrote: >> >>> Rayees, >>> >>> I think you have the same misunderstanding as a lot of other f

Review Request 24383: CLOUDSTACK-7271: Accept any hypervisor in error message for integration.smoke.test_deploy_vm_root_resize.TestDeployVM.test_00_deploy_vm_root_resize

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24383/ --- Review request for cloudstack and Santhosh Edukulla. Bugs: CLOUDSTACK-7271

Re: Review Request 24378: CLOUDSTACK-7268: Ignore "already exists" error in createEgressFirewallRule

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24378/ --- (Updated Aug. 6, 2014, 2:58 p.m.) Review request for cloudstack and Santhosh Ed

Re: [VOTE] git workflow

On Wed, Aug 6, 2014 at 10:53 AM, Hugo Trippaers wrote: > To me this pretty much ties in to the discussion about the simulator and the > BVT/CI suite. This works very neatly with the work Alex has been doing and > his proposal on how to deal with the BVT test suite. > > His original proposal was

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

Thanks for sending this out! These can be really helpful. On Wed, Aug 6, 2014 at 4:06 AM, Saksham Srivastava < saksham.srivast...@citrix.com> wrote: > I remember we used to follow the practice of informing others in case db > changes are committed, but we do not do it anymore. > In case you are

Build failed in Jenkins: simulator-singlerun #67

See Changes: [kishan.kavala] CLOUDSTACK-7237 : Added TAR image processor for templates with tar extension -- [...truncated 7273 lines...] [INFO] --

Re: [VOTE] git workflow

Rohit, addressing the following comment: "IMO We “should" remove the release branches when done. Instead there is a support workflow with git-flow (see support http://yakiloo.com/getting-started-git-flow/) and also in the tooling (git flow support etc. though experimental).” If we remove the rele

Re: Review Request 24298: CLOUDSTACK-6873: Moved test cases that run only on simulator and those should be run serially to misc folder and also tagged them with required_hardware='simulator only'

> On Aug. 6, 2014, 1:19 p.m., Doug Clark wrote: > > test/integration/smoke/misc/test_deploy_vm.py, line 1 > > > > > > Generally, how does putting these test in a separate directory help? > > Doesn't nosetests recursive

Re: [VOTE] git workflow

Why implement something that doesn¹t serve any practical purpose for CS?? We should adopt only things that would address current CS problems - regressions, unstable releases, etc. That would mean - running the automation (CI, BVT) on *develop branch, cut the *fix branches for hot fixes/critical/fea

Re: implementing git workflow

Agree with Daan. The first vote was needed to get the peoples opinions on whether we need to change our current git model (we certainly do as there are so many problems in the current flow), and the article was just the point of reference on how other people do it on the field. Now we have to see w

Re: [VOTE] git workflow

On 06-Aug-2014, at 6:58 pm, Alena Prokharchyk wrote: > Why implement something that doesn¹t serve any practical purpose for CS?? > We should adopt only things that would address current CS problems - > regressions, unstable releases, etc. That would mean - running the > automation (CI, BVT) on

Re: [VOTE] git workflow

Rohit, thank you for the explanation. So we cut the maintenance release from the master branch, not *develop as opposed to the major release branch. One more open question. Its clear that we cut the maintenance release from the master branch, but what would be the right way to merge it back if thi

Re: Review Request 24314: CLOUDSTACK-6695: UI: Added support for uploading a chain of certificates

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24314/#review49757 --- I tested the flow and it looks good to me. I did review the code but

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

This should be automated. We can't rely on the good intentions of dev. All we need is a script which checks changes in the schema/java Upgrade files and to sends a notification to the dev list. Filed a bug for this - https://issues.apache.org/jira/browse/CLOUDSTACK-7273 Thanks, -Nitin On 06/08/1

Re: [VOTE] git workflow

Hi, On 06-Aug-2014, at 7:30 pm, Alena Prokharchyk wrote: > Rohit, thank you for the explanation. So we cut the maintenance release > from the master branch, not *develop as opposed to the major release > branch. > > One more open question. Its clear that we cut the maintenance release from > th

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

Thank you, Nitin. I think we should add one more item to the things that the script checks: modifications to the older upgrade paths shouldn¹t be allowed. If we already released 4.4, db upgrade changes should be accepted only to 4.4-4.5 scripts. If someone makes the changes to, say 4.3-4.4, the mai

Re: [VOTE] git workflow

Rohit, whatever you say below, just proves our original worry about handling the maintenance minor releases (see my comments below). We can’t possibly adopt the way where release branches get removed since we always support maintenance releases for multiple versions at a time: 4.2.1, 4.3.1, 4.4.1.

Re: [VOTE] git workflow

On Wed, Aug 6, 2014 at 2:06 PM, Rohit Yadav wrote: > Hi, > > On 06-Aug-2014, at 7:30 pm, Alena Prokharchyk > wrote: > >> Rohit, thank you for the explanation. So we cut the maintenance release >> from the master branch, not *develop as opposed to the major release >> branch. >> >> One more open

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

Agreed. Added that information in the bug. On 06/08/14 11:08 AM, "Alena Prokharchyk" wrote: >Thank you, Nitin. I think we should add one more item to the things that >the script checks: modifications to the older upgrade paths shouldn¹t be >allowed. If we already released 4.4, db upgrade changes

Re: [VOTE] git workflow

On 8/6/14, 11:22 AM, "David Nalley" wrote: >On Wed, Aug 6, 2014 at 2:06 PM, Rohit Yadav >wrote: >> Hi, >> >> On 06-Aug-2014, at 7:30 pm, Alena Prokharchyk >> wrote: >> >>> Rohit, thank you for the explanation. So we cut the maintenance release >>> from the master branch, not *develop as oppose

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

What about the details for updating your DB? If we just receive a general e-mail notification, then each dev will independently have to examine the DB changes to come up with a workaround to keep his/her current env running properly after a code update. On Wednesday, August 6, 2014, Nitin Mehta

Getting "Refusing to design this network, the physical isolation type is not MIDO" while deploying a VM with new network from UI

Hi, I am getting this error while deploying a VM on XENSERVER : 2014-08-06 21:42:22,774 DEBUG [c.c.a.ApiServlet] (catalina-exec-2:ctx-6c894fdd) ===START=== 10.144.7.6 -- GET command=createNetwork&response=json&sessionkey=IyiV1YiWuFVSGa7GynZv5T12nLk%3D&networkOfferingId=94cef53e-49ec-4a9f-a0f

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

I doubt we can fully automate this one, Mike, for the case when data migration/modification is involved (.java file is modified in this case). Only for the changes to .sql files we can automate the instructions. For data modification, the developer who’s made the changes, still needs to provide

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

Mike - I agree that automation might not resolve the issue completely but will better devs lives. I think for schema file changes just the diffs published should do. For Java files it might sometimes require some more analysis and manual input from dev. Nevertheless it will always send a notificati

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

Yep, I agree. I guess my point was that a manually created e-mail should still be issued by the developer. On Wednesday, August 6, 2014, Alena Prokharchyk < alena.prokharc...@citrix.com> wrote: > I doubt we can fully automate this one, Mike, for the case when data > migration/modification is in

Re: [VOTE] git workflow

Hi, If it was not clear, let me re-state — just because I’m participating in this thread does not mean I fully support git-flow, or I am here to defend it. The proposal thread warriors Rajani, Daan, Leo and others can comment and advise? I like couple of good ideas in it, and I think it’s bett

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

If you care, why not self-police use git hooks: http://markmail.org/message/h5yb27jy6qrrw4dh Cheers. On 06-Aug-2014, at 8:51 pm, Mike Tutkowski wrote: > Yep, I agree. > > I guess my point was that a manually created e-mail should still be issued > by the developer. > > On Wednesday, August 6, 2

Re: Getting "Refusing to design this network, the physical isolation type is not MIDO" while deploying a VM with new network from UI

Since you turned in DEBUG logging, the “Refusing to design” messages are normally expected. The code steps through all registered network gurus, and only those with the right type you requested will design the network. All others will produce the “refusing” statement. KC On Aug 6, 2014, at 1

Re: [VOTE] git workflow

Agree with you, Rohit. The changes to the git model we use, are needed indeed. But we should address only the problems that CS faces, and the main problem - quality control. The proposal should be limited just to the changes that are really needed for the CS, and that will work with the current CS

Re: [VOTE] git workflow

On Wed, Aug 6, 2014 at 7:30 PM, Alena Prokharchyk < alena.prokharc...@citrix.com> wrote: > Rohit, thank you for the explanation. So we cut the maintenance release > from the master branch, not *develop as opposed to the major release > branch. > > Here's what happens if you want to create a suppor

Re: [VOTE] git workflow

"Once you merge release branch it on master/stable branch, you don’t lose commit if you delete it. It’s like removing a feature branch once it’s merged on master/target branch." Correct. At t his point your "release" is in master. If you need to bug fix, you checkout that tag from master. Also, a

Re: [VOTE] git workflow

On Wed, Aug 6, 2014 at 9:21 PM, Alena Prokharchyk < alena.prokharc...@citrix.com> wrote: > Agree with you, Rohit. The changes to the git model we use, are needed > indeed. But we should address only the problems that CS faces, and the > main problem - quality control. The proposal should be limite

Re: [VOTE] git workflow

On 8/6/14, 12:52 PM, "Erik Weber" wrote: >On Wed, Aug 6, 2014 at 9:21 PM, Alena Prokharchyk < >alena.prokharc...@citrix.com> wrote: > >> Agree with you, Rohit. The changes to the git model we use, are needed >> indeed. But we should address only the problems that CS faces, and the >> main probl

Re: Review Request 24420: vGPU Test Automation ( Check for Drivers)

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24420/ --- (Updated Aug. 6, 2014, 8:37 p.m.) Review request for cloudstack, Doug Clark and

Re: Review Request 24420: vGPU Test Automation ( Check for Drivers)

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24420/ --- (Updated Aug. 6, 2014, 8:41 p.m.) Review request for cloudstack, Doug Clark and

Review Request 24425: vGPU Automation : VM Lifecycle Tests

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24425/ --- Review request for cloudstack, Doug Clark, Sanjay Tripathi, and Santhosh Edukull

Re: Getting "Refusing to design this network, the physical isolation type is not MIDO" while deploying a VM with new network from UI

This seems to be your issue [c.c.r.ResourceManagerImpl] (API-Job-Executor-2:ctx-e92d4da4 job-420 ctx-8546dbd9 FirstFitRoutingAllocator) Host ID: 1 does not have GPU device available 2014-08-06 21:42:23,493 INFO [c.c.a.m.a.i.FirstFitAllocator] (API-Job-Executor-2:ctx-e92d4da4 job-420 ctx-8546dbd9

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

Here you go, modify and install in your git repositories: https://github.com/apache/cloudstack/blob/master/tools/git/db-police It will audaciously alert you, on OSX using ‘say’ and on GNU/Linux using ‘festival’ (if installed). I was not sure about Windows, so if anyone can cover that case? Cheer

Re: [VOTE] git workflow

Alena, I think this is a matter of semantics. If you call the latest version that got through the CI a pre-release and add them as releases in the git-flow way of working on master you've got what you envision. In spite of my mail this morning I am not a warrior (though I like the compliment, Roh

Re: [DB-CHANGE] Infrastructure tab fails to load with db exception

H, I got a review that I should remove the update to 4.3 system templates from the 4.4 upgrade path when I added the 4.4 upgrade. Shouldn't I have done that? It seems in contradiction with what you said in this thread. Maybe it is a special case as the upgrade will fail if you don't have them, bu

RE: [VOTE] git workflow

> -Original Message- > From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com] > Sent: Wednesday, August 06, 2014 12:59 PM > To: dev@cloudstack.apache.org > Subject: Re: [VOTE] git workflow > > > > On 8/6/14, 12:52 PM, "Erik Weber" wrote: > > >On Wed, Aug 6, 2014 at 9:21 PM, Al

Re: [VOTE] git workflow

Daan, thank you for the summary. See my answers below. On 8/6/14, 1:59 PM, "Daan Hoogland" wrote: >Alena, > >I think this is a matter of semantics. If you call the latest version >that got through the CI a pre-release and add them as releases in the >git-flow way of working on master you've go

Re: [VOTE] git workflow

Edison, thank you for raising the concern about the BVT/CI. Somebody mentioned earlier that we should separate git workflow implementation from the CI effort, but I do think we have to do in in conjunction. Otherwise what is the point in introducing staging/develop branch? If there is no daily auto

Jenkins build is unstable: simulator-singlerun #68

See

RE: [VOTE] git workflow

>Edison, thank you for raising the concern about the BVT/CI. Somebody mentioned >earlier that we should separate git workflow implementation from the CI >effort, but I do think we have to do in in conjunction. Otherwise what is the >point in introducing staging/develop branch? If there is no da

Re: [VOTE] git workflow

[top posting, apologies in advance] I am on vacation, so I will go straight to it :) This all discussion is not about gitflow specifically, it is about modifying our git workflow and our commit practices to something more standard that can: - ultimately help improve quality (in itself it won't

Re: [VOTE] git workflow

On Aug 6, 2014, at 6:13 PM, Prachi Damle wrote: > >> Edison, thank you for raising the concern about the BVT/CI. Somebody >> mentioned earlier that we should separate git workflow implementation from >> the CI effort, but I do think we have to do in in conjunction. Otherwise >> what is the p

Re: [VOTE] git workflow

On 8/6/14, 3:18 PM, "Sebastien Goasguen" wrote: >[top posting, apologies in advance] > >I am on vacation, so I will go straight to it :) > >This all discussion is not about gitflow specifically, it is about >modifying our git workflow and our commit practices to something more >standard that ca

RE: [VOTE] git workflow

-Original Message- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: Wednesday, August 06, 2014 3:23 PM To: dev@cloudstack.apache.org Cc: Edison Su Subject: Re: [VOTE] git workflow On Aug 6, 2014, at 6:13 PM, Prachi Damle wrote: > >> Edison, thank you for raising the concern

Jenkins build is still unstable: simulator-singlerun #69

See

RE: [VOTE] git workflow

> -Original Message- > From: Sebastien Goasguen [mailto:run...@gmail.com] > Sent: Wednesday, August 06, 2014 3:19 PM > To: dev@cloudstack.apache.org > Subject: Re: [VOTE] git workflow > > [top posting, apologies in advance] > > I am on vacation, so I will go straight to it :) > > This

Re: [VOTE] git workflow

On Wed, Aug 6, 2014 at 5:36 PM, Alena Prokharchyk wrote: > Edison, thank you for raising the concern about the BVT/CI. Somebody > mentioned earlier that we should separate git workflow implementation from > the CI effort, but I do think we have to do in in conjunction. Otherwise > what is the poin

  1   2   >