Re: [VOTE] git workflow

Good morning, I have some difficulty believing having to type 'git checkout develop' is enough reason for an apache committer to veto a change like this, especially after the extensive discussions we had and all the docs we wrote. I think people are seeing bigger problems or haven't quite under

Re: [VOTE] git workflow

Exactly Rajani, and other solutions are possible. The issue is not how branches are called ;) On Wed, Aug 6, 2014 at 8:29 AM, Rajani Karuturi wrote: > I am just wondering if the shift to a new develop branch is causing the > problems. Its a simple branch shift and should be no different from the

Build failed in Jenkins: simulator-singlerun #61

See Changes: [santhosh.edukulla] Fixed coverity reported concurrency issue -- [...truncated 7290 lines...] [INFO] [

Re: [VOTE] git workflow

I am just wondering if the shift to a new develop branch is causing the problems. Its a simple branch shift and should be no different from the current master. may be we should leave the master as is and create a ‘stable' branch which would act like master in git-flow ? ie) ACS master -> deve

Re: implementing git workflow

I added a pre push hook to the [wiki page] which rejects any commits which doesn’t start with ‘Merge branch’ on master [wiki page] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Git#Git-githooks ~Rajani On 05-Aug-2014, at 6:48 pm, Daan Hoogland mailto:daan.hoogl...@gmail.com>> wro

Re: implementing git workflow

I don't think we should hold on improving our way of working just because it is not perfect yet. Some things are unclear so we can't do those. Other things are perfectly clear and need to wait for nothing else. That doesn't mean that a second vote isn't needed. It is if not for anything else then f

Re: [VOTE] git workflow

Hello devs and especially committters, I see some -1s coming by, days after the vote was closed. That is disturbing as it means we accepted a proposal that will not be supported by the community. So let me try to find that support in hindsight; The argument of Animesh that we are shifting the bur

Re: Review Request 24308: Enable Password Strength check for all users

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24308/ --- (Updated Aug. 6, 2014, 4:58 a.m.) Review request for cloudstack and Darren Shep

Re: implementing git workflow

For a proposal which got all +1’s[1] what are the next steps to do?? It was made clear on the voting thread that required branching changes would be done if the vote passes[2] Though the content in the document changed, the original proposal hasn’t changed. Its still the same. It is explained i

Build failed in Jenkins: simulator-singlerun #60

See Changes: [nitin.mehta] CLOUDSTACK-4200: listSystemVMs API and listRouters API should return hypervisor property since dynamic scaling is not enabled for all the hypervisors and that action can be showed only for the hypervi

Build failed in Jenkins: simulator-singlerun #59

See Changes: [anthony.xu] added more log -- [...truncated 7273 lines...] [INFO] [INFO] Building Apache CloudStack D

Re: [VOTE] git workflow

On Tue, Aug 5, 2014 at 7:44 PM, Erik Weber wrote: > On Wed, Aug 6, 2014 at 12:55 AM, Prachi Damle > wrote: > > > I fail to understand how will this model help us with the maintenance > > releases? > > > > > That's what gitflow support branches is for. > I find this quite descriptive: > > https:/

Jenkins build is still unstable: simulator-hotfix-trigger #13

See

Re: Wants to contribute to the Cloudstack code

Which parts of CloudStack are of most interest and/or most applicable to your experience? At a high level, it's divided into compute (hypervisors/bare metal), networking, and storage. You might want to start by creating an account on JIRA (our defect/enhancement-tracking tool) and picking a bug t

Re: [VOTE] git workflow

On Wed, Aug 6, 2014 at 12:55 AM, Prachi Damle wrote: > I fail to understand how will this model help us with the maintenance > releases? > > That's what gitflow support branches is for. I find this quite descriptive: https://groups.google.com/forum/#!msg/gitflow-users/I9sErOSzYzE/AwVH06CuKT0J

Re: [VOTE] git workflow

Agree with Prachi and Alena here. As a developer, I am more towards having "developer" branch as a staging area to periodically merge into master when CI pass on it, this is the simplest way to make master branch stable, if that is the original intention of this proposal. Also, before we figure ou

Jenkins build is unstable: simulator-hotfix-trigger #12

See

RE: [VOTE] git workflow

I fail to understand how will this model help us with the maintenance releases? For CloudStack we also keep working on prior releases and ship out maintenance releases. I suppose we will be cutting the maintenance releases from the release branches? So we will have to keep around the release br

FreeBSD 64-Bit

Hello, I have been talking to folks on user@ and they suggested I post here. I am wondering as to why this version of CloudStack 4.4 does not permit FreeBSD to boot (via 64-bit format). I was able to boot / install 32bit, but I would much rather go the route of 64-bit. Any suggestions, or advi

Re: [VOTE] git workflow

On Aug 5, 2014, at 2:33 PM, Jessica Wang wrote: > Exactly. This just shifts pain from one branch to another. > I don't see any gains from this, either. > I vote "-1". > It is much more than shifting pains, the wiki page is not discussion the workflow quite extensively, with several pointers

Locking Down Hypervisor

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  Please advise. - Maurice

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

See -- [...truncated 7091 lines...] [INFO] [INFO] Building Apache CloudStack Developer Mode 4.4.1-SNAPSHOT [INFO] -

Re: [VOTE] git workflow

I’ll get back to you on this thread tomorrow, late night here o/ Cheers. On 05-Aug-2014, at 11:11 pm, Alena Prokharchyk wrote: > Rohit, can you help us to figure out the advantages of implementation #2 > (git workflow way of maintaining master branch) over implementation #1? As > per your word

Re: [VOTE] git workflow

Rohit, can you help us to figure out the advantages of implementation #2 (git workflow way of maintaining master branch) over implementation #1? As per your words from other email "I was skeptic too and explored every bit of the workflow and usage of git and I think it’s a good model” you might hav

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/ --- (Updated Aug. 5, 2014, 10:03 p.m.) Review request for cloudstack, Brian Federle

Re: [VOTE] git workflow

Hi, Sorry to see -1s, I was skeptic too and explored every bit of the workflow and usage of git and I think it’s a good model. TL;DR? I hear you and the wiki is changing a lot, so just go through the cheatsheet and come back to this email: http://danielkummer.github.io/git-flow-cheatsheet If y

Re: [VOTE] git workflow

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 after the BVT/CI tests pass. So the master branch reflects the develop branch minus changes

Build failed in Jenkins: simulator-singlerun #58

See Changes: [nitin.mehta] test_06_destroy_vm in test/integration/smoke/test_vm_life_cycle.py fails because the expunge parameter is set to true, this also cause tests that execute in test_vm_life_cycle.py after this test to f

RE: [VOTE] git workflow

How frequent we can planning to merge from develop to master ? during release ? Regards, Rayees -Original Message- From: Prachi Damle [mailto:prachi.da...@citrix.com] Sent: Tuesday, August 05, 2014 11:51 AM To: dev@cloudstack.apache.org Subject: RE: [VOTE] git workflow Sorry if t

Wants to contribute to the Cloudstack code

Hi, I'm interested in contributing to cloudstack's code. I have already installed cloudstack on my ubuntu machine. However i'm a python developer, can someone please advice me, as to which part of the code i can contribute to. Thanks in advance.

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

See Changes: [Daan Hoogland] remove update to 4.3 templates for 4.4 -- [...truncated 7102 lines...] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-developer -

Re: implementing git workflow

On Tue, Aug 5, 2014 at 2:51 PM, Alena Prokharchyk wrote: > I think we should hold on with the git workflow implementation till all > the decisions on the items written by Leo, are discussed and finalized. > > The very beginning of ³git workflow vote² shows that the vote was just to > get people op

RE: [VOTE] git workflow

Sorry if this is already discussed, but few areas that are unclear to me with this process are: - does every fix, however minor it be(say a signle line), needs to be developed in a separate branch? And then we have to merge these individual branches to develop for every fix? - In that case will

Re: implementing git workflow

I think we should hold on with the git workflow implementation till all the decisions on the items written by Leo, are discussed and finalized. The very beginning of ³git workflow vote² shows that the vote was just to get people opinion on the proposal. Before adopting it and cutting the develop b

RE: [VOTE] git workflow

Exactly. This just shifts pain from one branch to another. I don't see any gains from this, either. I vote "-1". Jessica -Original Message- From: Min Chen [mailto:min.c...@citrix.com] Sent: Tuesday, August 05, 2014 11:27 AM To: dev@cloudstack.apache.org Subject: Re: [VOTE] git workflow

Re: [VOTE] git workflow

Agree with Animesh. Didn't see any gains from this, we just shift pain from one branch to another, so vote -1. -min On 8/2/14 9:50 PM, "Animesh Chaturvedi" wrote: >+0 > >While this protects master with only commits which are merges from >release branch and keeps it clean but the issues that we

Build failed in Jenkins: simulator-singlerun #57

See Changes: [Rohit Yadav] README: Import README sections from 4.4 branch into master [Rohit Yadav] CLOUDSTACK-7159 Added "state" parameter to the "listPublicIpAddresses" API call [Rohit Yadav] server: use scoped variable in p

Re: implementing git workflow

> > we have two open questions to answer before that: > > 1. Can we enable a git hook to prevent the commits to master post the > > switch? > > It’s possible theoretically but to do that in less than 48 hours could be a > challenge, you can open a ticket on JIRA/ASF-infra or contact the fine folk

[ACS441] Hotfix merge request

Hi Daan, Can you please merge hotfix/4.4-7257 into 4.4, that fixes CLOUDSTACK-7257. Thanks, Amogh

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

See -- [...truncated 7107 lines...] Audit done. [INFO] [INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer <<< [INFO] [INFO] --- exec-maven-plugin:1.2.1:java

DashBoard Stats

Hello, Could someone please tell me, how I can obtain latest stats to be included in % for Secondary Storage | Primary Storage. It shows what I have used so far, but not the precent, like the others.

Re: Review Request 23805: Added "state" parameter to the "listPublicIpAddresses" API call

> On Aug. 5, 2014, 4:12 p.m., Rohit Yadav wrote: > > Ship It! Thanks for the git formatted patch, tested to build. Merged on master: commit 07f916dfc6fb30dc928b258beeaa761253e43ab9 Author: Ilia Shakitko Date: Tue Aug 5 17:58:46 2014 +0200 CLOUDSTACK-7159 Added "state" parameter to the "

Build failed in Jenkins: simulator-singlerun #56

See -- [...truncated 7274 lines...] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- properties-

Re: Review Request 23805: Added "state" parameter to the "listPublicIpAddresses" API call

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/23805/#review49608 --- Ship it! Ship It! - Rohit Yadav On Aug. 5, 2014, 4:02 p.m., Ilia

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/ --- Review request for cloudstack, Brian Federle, Jessica Wang, and Nitin Mehta. Re

Re: Review Request 23805: Added "state" parameter to the "listPublicIpAddresses" API call

> On July 29, 2014, 10:20 a.m., Rohit Yadav wrote: > > Looks fine, we still need to test it before we land it on master. I > > unfortunately don't have my hardware (and some parts) setup will try with > > DevCloud or hope someone else would review, test and ship it :) > > Ilia Shakitko wrote:

Re: Review Request 23805: Added "state" parameter to the "listPublicIpAddresses" API call

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/23805/ --- (Updated Aug. 5, 2014, 4:02 p.m.) Review request for cloudstack, Alena Prokharc

Build failed in Jenkins: simulator-singlerun #55

See Changes: [Rohit Yadav] README: Give CloudStack its much deserved readme file [Rohit Yadav] README: Fix links for viewing on Github -- [...truncated 7284 lines...] main: [INFO] Execut

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. 5, 2014, 8:43 p.m.) Review request for cloudstack and Santhosh Ed

Re: Adding README file

On Tue, Aug 5, 2014 at 4:19 PM, Rohit Yadav wrote: > Daan, if you want this in 4.4 branch? > Sure, I'll have a read and see if it is worth picking -- Daan

Adding README file

Added a README file for users and developers landing on Github or going thorough freshly downloaded repo: https://github.com/apache/cloudstack/blob/master/README.md Feel free to edit/fix the file as needed. Daan, if you want this in 4.4 branch? Regards, Rohit Yadav Software Architect, ShapeBlue

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/ --- Review request for cloudstack and Santhosh Edukulla. Bugs: CLOUDSTACK-7255

[ACS44] jira tag for release 4.4.1

people, I have created a tag in jira for marking issues as affecting or solved in 4.4.1 Please make abundant use of it. thanks -- Daan

Re: [acs441] planning?

Pierre-Luc, I will make a tag in Jira. The branch will remain 4.4. The release is not yet planned. I will have to do some work still on the template update issue. The silence around the other issues so far leaves me to believe that 4.4.1 will not be a significant improvement if we plan it now. I w

Build failed in Jenkins: simulator-singlerun #54

See Changes: [jayapal] CLOUDSTACK-2694: Able to configure duplicate firewall rule with protocol and no ports -- [...truncated 7299 lines...] main: [INFO] Executed tasks [INFO] [INFO] >>

[acs441] planning?

Hi, I'm willing to work on the release-notes and tests of 4.4.1. I'd like to know what is the planning of this release. - there is no version 4.4.1 in jira to follow bug fixes, - git branch = 4.4 - how can we know what would be targeted bug fixes for this release? - I thing Daan is the Release Ma

Re: implementing git workflow

That sound good to me On Tue, Aug 5, 2014 at 2:15 PM, Rajani Karuturi wrote: > > On 05-Aug-2014, at 4:47 pm, Daan Hoogland wrote: > >> On Tue, Aug 5, 2014 at 12:45 PM, Rohit Yadav >> wrote: 1. Can we enable a git hook to prevent the commits to master post the switch? >>> >>> It’s po

Re: Review Request 24229: upgrade system templates in 4.4.x

Pierre-Luc, I plan to apply Kishan's comment and add it to 4.4.1 On Tue, Aug 5, 2014 at 2:13 PM, Pierre-Luc Dion wrote: > Will this be part of 4.4.1 ? if so, we will have to update Release-notes for > upgrade steps from 4.2.x to 4.4 which for the moment use the template named > systemvm--4.3. > >

Build failed in Jenkins: simulator-singlerun #53

See Changes: [santhosh.edukulla] Fixed a coverity reported concurrency issue [santhosh.edukulla] CLOUDSTACK-7240: Fixed expunge VM issue in test_persistent_networks.py -- [...truncated 7

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/ --- (Updated Aug. 5, 2014, 6:28 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'

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

Re: Review Request 23805: Added "state" parameter to the "listPublicIpAddresses" API call

> On July 29, 2014, 10:20 a.m., Rohit Yadav wrote: > > Looks fine, we still need to test it before we land it on master. I > > unfortunately don't have my hardware (and some parts) setup will try with > > DevCloud or hope someone else would review, test and ship it :) > > Ilia Shakitko wrote:

Re: Review Request 24306: Review request for CLOUDSTACK-2694 - [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports

Hi Namita, The patch is applied on master. Please close the review ticket. Thanks, Jayapal On 05-Aug-2014, at 5:57 PM, Jayapal Reddy mailto:jayapalreddy.ur...@citrix.com>> wrote: This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24306/ Ship it! Ship I

Re: Review Request 24306: Review request for CLOUDSTACK-2694 - [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports

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

Re: Review Request 24306: Review request for CLOUDSTACK-2694 - [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24306/#review49593 --- Ship it! Ship It! - Jayapal Reddy On Aug. 5, 2014, 10 a.m., Nami

Re: implementing git workflow

On 05-Aug-2014, at 4:47 pm, Daan Hoogland wrote: > On Tue, Aug 5, 2014 at 12:45 PM, Rohit Yadav > wrote: >>> 1. Can we enable a git hook to prevent the commits to master post the >>> switch? >> >> It’s possible theoretically but to do that in less than 48 hours could be a >> challenge, you

Re: implementing git workflow

~Rajani On 05-Aug-2014, at 4:15 pm, Rohit Yadav wrote: > Hi Rajani, > > On 05-Aug-2014, at 12:35 pm, Rajani Karuturi > wrote: > >> The switch to the new git flow is postponed to 7th aug. > > Thanks for that, this means you’ll do it again on 7th August 00:00UTC? I am planning to do this

Re: Review Request 24229: upgrade system templates in 4.4.x

Will this be part of 4.4.1 ? if so, we will have to update Release-notes for upgrade steps from 4.2.x to 4.4 which for the moment use the template named systemvm--4.3. Thanks, *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire

Build failed in Jenkins: simulator-singlerun #52

See Changes: [santhosh.edukulla] Fixed Marvin Issue: Hypervisor value was hardcoded to XenServer while deploying VM if not specified [kishan.kavala] CLOUDSTACK-7087: Latest OS X VPN client not working Downgrading openswan vers

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/ --- (Updated Aug. 5, 2014, 5:34 p.m.) Review request for cloudstack and Santhosh Ed

Re: Review Request 24305: CLOUDSTACK-7240: Fixed expunge VM issue in test_persistent_networks.py

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

Re: Review Request 24305: CLOUDSTACK-7240: Fixed expunge VM issue in test_persistent_networks.py

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

Re: Review Request 24305: CLOUDSTACK-7240: Fixed expunge VM issue in test_persistent_networks.py

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24305/#review49589 --- Ship it! Ship It! - Santhosh Edukulla On Aug. 5, 2014, 9:45 a.m.

Re: Review Request 24305: CLOUDSTACK-7240: Fixed expunge VM issue in test_persistent_networks.py

> On Aug. 5, 2014, 12:01 p.m., Santhosh Edukulla wrote: > > Ship It! Please change the branch to master, its still open for commits, pushed to master. 64b9ca0..c76302c master -> master - Santhosh --- This is an automatically generated

Re: implementing git workflow

On Tue, Aug 5, 2014 at 12:45 PM, Rohit Yadav wrote: >> 1. Can we enable a git hook to prevent the commits to master post the switch? > > It’s possible theoretically but to do that in less than 48 hours could be a > challenge, you can open a ticket on JIRA/ASF-infra or contact the fine folks > on

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

See Changes: [htrippaers] It's the template that has the simulator type, not the deploy target. -- [...truncated 7393 lines...] [INFO]

Review Request 24308: Enable Password Strength check for all users

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24308/ --- Review request for cloudstack and Darren Shepherd. Bugs: https://issues.apache.

Re: implementing git workflow

Hi Rajani, On 05-Aug-2014, at 12:35 pm, Rajani Karuturi wrote: > The switch to the new git flow is postponed to 7th aug. Thanks for that, this means you’ll do it again on 7th August 00:00UTC? Meanwhile this means we’re to follow our normal workflow and commit on master. > we have two open que

Re: Review Request 24229: upgrade system templates in 4.4.x

> On Aug. 5, 2014, 4:12 p.m., Kishan Kavala wrote: > > Daan, > > This looks good to me. > > Can you also please remove template upgrade code in Upgrade421to430.java. > > Otherwise upgrades from 4.2 will fail complaining that > > systemvm-xenserver-4.3 is not available. I mean systemvm--4.3 te

Re: Review Request 24229: upgrade system templates in 4.4.x

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24229/#review49584 --- Daan, This looks good to me. Can you also please remove template up

Re: Review Request 24301: CLOUDSTACK-7247: Fixed Marvin Issue: Hypervisor value was hardcoded to XenServer while deploying VM if not specified

> On Aug. 5, 2014, 10:41 a.m., Santhosh Edukulla wrote: > > Ship It! dfa607f..2109418 master -> master - Santhosh --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24301/#review49582 -

Re: implementing git workflow

ad 1. Git hooks in the central repo require assistence of apache infra. I think all committers should be able to do this. If people don't comply their work should be reverted. ad 2. We shouldn't need an RM. The gitflow model implies that committers share the load of RM. On Tue, Aug 5, 2014 at 12:3

Re: Review Request 24301: CLOUDSTACK-7247: Fixed Marvin Issue: Hypervisor value was hardcoded to XenServer while deploying VM if not specified

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24301/#review49582 --- Ship it! Ship It! - Santhosh Edukulla On Aug. 5, 2014, 10:02 a.m

Re: implementing git workflow

Santhosh, Though in principle you are right I hardly think this can be called suddenly. On Tue, Aug 5, 2014 at 11:52 AM, Santhosh Edukulla wrote: > Post the proposal vote, we should have given some time buffer, or prior > intimation of a day or two before this switch i believe. There were still

Re: Review Request 23837: CLOUDSTACK-7087: Downgrade openswan to previous version for VPN services to fix OSX client

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/23837/#review49581 --- Commit 2dfd278625a5d569a5cce2fec5ccb0d7c515c9e8 in cloudstack's bran

Re: implementing git workflow

The switch to the new git flow is postponed to 7th aug. we have two open questions to answer before that: 1. Can we enable a git hook to prevent the commits to master post the switch? 2. should we create the release branch as well or wait for RM to do it? ~Rajani On 05-Aug-2014, at 3:16 pm, R

Re: NO commits to master

Rajani, I think you did great work. The fact that more communication could have helped is in no way on you. There is a wiki page with a proposal that has been voted on. No -1! Having said that let's put down a time line. One thing in there is, in my opinion that as of now no one should commit to m

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

I deleted the develop branch and will be recreating it in 48hrs. As per the new git flow which we agreed, all the next release work should move to develop branch and there shouldn’t be any direct commits on master. Please make sure you go through wiki @ https://cwiki.apache.org/confluence/displ

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

See Changes: [htrippaers] Improve the error message to see what is going on -- [...truncated 7381 lines...] > Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker [INFO

Re: NO commits to master

Its not any simpler. Its going to be the same work. I am not convinced that delay is going to help. But, I am going to abandon the develop branch and create one 48hrs later. ~Rajani On 05-Aug-2014, at 3:46 pm, Koushik Das wrote: > Why not cut out a new develop branch after the 24/48 hrs

RE: NO commits to master

Why not cut out a new develop branch after the 24/48 hrs window and discard the current develop branch. That is much more simpler. -Original Message- From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] Sent: Tuesday, 5 August 2014 3:20 PM To: dev@cloudstack.apache.org Subject: Re: NO co

Re: NO commits to master

we had enough time since the vote passed. But, I agree we should have decided on dates. master/develop are in sync right now. So, it should be a simple branch switch to develop and push. some automated things like jenkins may need changes. other than that, I don’t see any issues. A git hook i

Re: Review Request 24301: CLOUDSTACK-7247: Fixed Marvin Issue: Hypervisor value was hardcoded to XenServer while deploying VM if not specified

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

Review Request 24306: Review request for CLOUDSTACK-2694 - [Firewall Rule] Able to configure duplicate firewall rule with protocol and no ports

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24306/ --- Review request for cloudstack and Jayapal Reddy. Bugs: CLOUDSTACK-2694 and http

RE: implementing git workflow

Post the proposal vote, we should have given some time buffer, or prior intimation of a day or two before this switch i believe. There were still people using master till today for their development purpose, holding on it at sudden may not be appropriate. Regards, Santhosh _

Re: NO commits to master

Hi Rajani, Thanks for taking the initiative, people may still keep pushing onto master, so please give them a window of 24-48 hours so that everyone is informed, or alternatively you may sync commits from master to develop but I hope we don’t end up in branch based split-brain where some folks

Re: implementing git workflow

Hi Daan, I created develop branch on commit cc725e53e304781148a6bf077e05d844fe88207c and pushed it. I am trying to create the 4.5 branch. For this, I need to change the version number in develop branch. Release Procedure wiki mention a script to change to version number. [1] Is it safe to jus

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/ --- (Updated Aug. 5, 2014, 3:15 p.m.) Review request for cloudstack and Santhosh Ed

Re: Review Request 24305: CLOUDSTACK-7240: Fixed expunge VM issue in test_persistent_networks.py

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

Re: NO commits to master

develop branch is created as of commit cc725e53e304781148a6bf077e05d844fe88207c Please do not commit anything to master and use the respective branches. Please go through the detailed wiki by Leo @ https://cwiki.apache.org/confluence/display/CLOUDSTACK/Git ~Rajani On 05-Aug-2014, at 3:08 p

  1   2   >