Re: Fast way to rebuild the GUI?

hi mike, mvn -P developer -*pl* :cloud-client-ui -DskipTests=true i guess running this command only builds the cloud-client-ui package, ie client/target/cloud-client-ui-4.4.0-SNAPSHOT.war but it won't be extracted to client/target/cloud-client-ui-4.4.0-SNAPSHOT hence the new changes will not be

Re: Fast way to rebuild the GUI?

I should clarify that that command runs successfully, but the GUI does not incorporate the new changes from running that command anymore. On Sat, Aug 9, 2014 at 12:12 AM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > I could be wrong, but I thought we compressed JS files now. > > This

Re: Fast way to rebuild the GUI?

I could be wrong, but I thought we compressed JS files now. This used to work: mvn -P developer -pl :cloud-client-ui -DskipTests=true Unfortunately it no longer does. On Sat, Aug 9, 2014 at 12:08 AM, Punith S wrote: > hi mike, > > you can just replace the js file in > cloudstack-management/w

Re: Fast way to rebuild the GUI?

hi mike, you can just replace the js file in cloudstack-management/webapps/client/scripts/ folder and reload the browser, js file will be reloaded in the cloudstack ui. thanks. On Sat, Aug 9, 2014 at 11:32 AM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > Hi, > > When you change a Ja

Fast way to rebuild the GUI?

Hi, When you change a JavaScript file for the GUI, is there a fast way to update the management server with this file short of having to rebuild the entire codebase? Thanks! -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advanci

Re: Import Template: qcow2

hi mo, you can put your centos qcow2 template in webapps/client directory and give the registration url as http://xx.xx.xx.243:8080/client/ a22ed0a2-9285-42da-bc34-fc4e71d48910.qcow2 while registering the template or you can create a simple python web server in centos and upload the template. be s

Jenkins build is still unstable: simulator-singlerun #93

See

Jenkins build is still unstable: simulator-singlerun #92

See

Re: [VOTE] git workflow

Rohit, Thank you to bring this to a end. Finally handling multiple maintenance release is recognized as an issue in this model. --Sheng On Fri, Aug 8, 2014 at 4:28 AM, Rohit Yadav wrote: > Hi, > > Vincent (nvie) has allowed me to share his email publicly, here you go: > > " > Hi Rohit, > > Th

Jenkins build is still unstable: simulator-singlerun #91

See

Re: [ACS44] committing to 4.4

Hi Daan, May I suggest if we can take the next week to test 4.4 branch rigorously and fix bugs, also get some participation from dev and QA folks in the community, 4.4.0 release IMO could have found some more attention from the community. I just request to do it right this time. In case you’re

Jenkins build is still unstable: simulator-singlerun #90

See

Re: [ACS44] committing to 4.4

That's alright, and it turned out all right. I'm just nervous whether I can make a 4.4.1 on sunday. On Fri, Aug 8, 2014 at 11:11 PM, Rohit Yadav wrote: > Hi Daan, > > Sorry about that, my frivolous fix broke the systemvm build job and that led > series of brute force fixes. > > On 08-Aug-2014, a

Re: [ACS44] committing to 4.4

Hi Daan, Sorry about that, my frivolous fix broke the systemvm build job and that led series of brute force fixes. On 08-Aug-2014, at 10:26 pm, Daan Hoogland wrote: > H, > > Please stop committing to 4.4 the coming time. If there are things to > make a branch with the following name structure:

Jenkins build is still unstable: simulator-singlerun #89

See

[ACS44] committing to 4.4

H, Please stop committing to 4.4 the coming time. If there are things to make a branch with the following name structure: hotfix/4.4- This is not to be instructive or corrective for anyone's good work over the last day, just to make sure we keep a solid state on 4.4 I will do any merge that is

Re: [ACS441] systemvm template for XenServer

ok, i will check in a versioned version on branch 4.4 if the rc passes so jenkins builds a good versioned one after vote before upping the version to 4.4.2, and upload that one. great On Fri, Aug 8, 2014 at 8:54 PM, Pierre-Luc Dion wrote: > Hi Daan, > > I've test 4.4.1 with the systemvm from bac

Re: git commit: updated refs/heads/master to ffe0f2f

Thanks On Fri, Aug 8, 2014 at 7:22 PM, wrote: > Repository: cloudstack > Updated Branches: > refs/heads/master d33278250 -> ffe0f2f60 > > > appliance: use the right way to get git branch name > > Taken from Junio C Hamano's blog [1], git's maintainer, he must not be wrong > :) > > [1] > http

[ACS441] upgrading tests from 4.2.1 to 4.4.1

Upgrade tests from 4.2.1 to 4.4.1 with xenserver did upgrade smoothly as it should :-) upgrade instruction will be simple. Cluster settings are also visible after the upgrade which is great ! Thanks !!! so rc1 = +1 ;-) Pierre-Luc

Import Template: qcow2

Hello, Question, I previously saved a CentOS 6.5 template (e.g. downloaded) and I got the file: a22ed0a2-9285-42da-bc34-fc4e71d48910.qcow2 on my local machine. I then uploaded it to my new install of CloudStack 4.4, but it won’t boot, it hangs at ‘Booting from Hard drive’, when I registered the

Jenkins build is still unstable: simulator-singlerun #88

See

[ACS441] systemvm template for XenServer

Hi Daan, I've test 4.4.1 with the systemvm from bac.o[1] on xenserver and it's working better than 4.4.0 so far. no more pause issue, version is correct, java as well. [1] http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/87/ Pierre-Luc

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/#review50062 --- Commit d0ff6cd461d9169133a7782850c93c9a3e994ba8 in cloudstack's bran

Jenkins build is still unstable: simulator-singlerun #87

See

Re: Unable to add ISO

See if the wiki helps https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Sec ondary+storage+troubleshooting On 08/08/14 10:40 AM, "Elapavuluri, Jaya" wrote: >Hello, > >I am trying to register an iso under the template-> iso section of >cloudstack. I have given proper url li

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/#review50054 --- Commit 57f611df16c48419e582f41c1e630faa739c11c5 in cloudstack's bran

RE: issues remaining for 4.4.1

> -Original Message- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Thursday, August 07, 2014 1:53 AM > To: dev > Subject: issues remaining for 4.4.1 > > H, > > have a look at https://issues.apache.org/jira/browse/CLOUDSTACK- > 6358?filter=12328007 > > It is a disappoin

[DISCUSS] Removing template URL format checking logic

Hi, With reference to https://issues.apache.org/jira/browse/CLOUDSTACK-5512 Marcus and I think we should remove the template URL format checking logic because: - It does not handle pre-signed URL (say something that does not end with .vhd etc, but has bunch of http params) - One can game the sy

Unable to add ISO

Hello, I am trying to register an iso under the template-> iso section of cloudstack. I have given proper url link for the ISO. However, when I click on the iso, the Ready state: NO and the Status is not showing the download percentage. Any insight on this matter?

Re: git commit: updated refs/heads/4.4 to 00265fb

wat? http://people.apache.org/~bhaisaab/wat.jpg That should have worked, let me try again; probably bash issue? I used $() instead of ``. Will fix it. Cheers. On 08-Aug-2014, at 6:17 pm, Daan Hoogland wrote: > well, that one didn't work out: > systemvm64template-HEAD-2014-08-08-kvm.qcow2.bz2

Re: Review Request 22939: CLOUDSTACK-6460 - CLVM primary storage migration fails due to incorrect identification of source format.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22939/ --- (Updated Aug. 8, 2014, 4:51 p.m.) Review request for cloudstack, edison su and

Re: git commit: updated refs/heads/4.4 to 00265fb

well, that one didn't work out: systemvm64template-HEAD-2014-08-08-kvm.qcow2.bz2290.03 MB view systemvm64template-HEAD-2014-08-08-vmware.ova278.88 MB view systemvm64template-HEAD-2014-08-08-vmware.vmdk.bz2241.25 MB view systemvm64template-HEAD-2014-08-08-xen.vhd.bz2241.11 MB view s/HEAD/4.4/ was wh

Re: List APIs Behavior

Gaurav, "Ideally, when we search by Id, then exception should be thrown and when We expect by passing account/domainid/projectid/networkid etc, then Noneshould be returned. Do all List APIs follow a similar guideline?² Yes, all of CS APIs follow this behavior. If non-existing Id is passed in, the

Re: What is the behaviour of VPC Reset?

"But, I do not see any code that makes a call to delete the rules and reapplies it. If it reapplies how does it get the information for each tier to reapply the ACLs. I see that just shutdownVpc() API call is made and VPCVRElement just invokes destroyRouter…” If you look further, you should see

Jenkins build is still unstable: simulator-singlerun #86

See

Review Request 24504: CLOUDSTACK-7293: UI: Fixed localization issues on the login page

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24504/ --- Review request for cloudstack, Brian Federle and Jessica Wang. Repository: clou

Jenkins build is still unstable: simulator-singlerun #85

See

Re: git commit: updated refs/heads/4.4 to 00265fb

On Fri, Aug 8, 2014 at 3:23 PM, wrote: > Repository: cloudstack > Updated Branches: > refs/heads/4.4 e77da80e0 -> 00265fba3 > > > did git change it output format since this script was made? > That's just ugly, to get branch why not do: git rev-parse --abbrev-ref HEAD I'll fix it on both mast

Jenkins build is still unstable: simulator-singlerun #84

See

Re: abount usage-server config

Hi, Was the issue resolved? Can you send all the records in usage_job? On Thu, Aug 7, 2014 at 12:47 PM, 李栋 wrote: > cloudstack version is 4.2.1 > > 于 2014/8/7 15:02, 李栋 写道: > > *hi all:* > > *We followed the document > (http://docs.cloudstack.apache.org/projects/cloudstack-administration/e

Re: Review Request 24502: CLOUDSTACK-7292: Fixed issue in test_deploy_vm_root_resize.py

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

Re: Review Request 24502: CLOUDSTACK-7292: Fixed issue in test_deploy_vm_root_resize.py

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24502/#review50029 --- Ship it! Ship It! - Santhosh Edukulla On Aug. 8, 2014, 12:32 p.m

Review Request 24502: CLOUDSTACK-7292: Fixed issue in test_deploy_vm_root_resize.py

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

Re: [jira] [Closed] (CLOUDSTACK-6323) GetUser API always returns admin info

right On Fri, Aug 8, 2014 at 2:17 PM, Pierre-Luc Dion wrote: > I'll update the Release-note accordingly. > it only affect GetUser API call right ? > > > Pierre-Luc DION > Architecte de Solution Cloud | Cloud Solutions Architect > t 855.652.5683 > > CloudOps Votre partenaire infonuagique | Cloud

Re: [VOTE] git workflow

This sounds like an end goal that we shouldn't try to reach in one go. Let's take baby steps. On Fri, Aug 8, 2014 at 1:28 PM, Rohit Yadav wrote: > Hi, > > Vincent (nvie) has allowed me to share his email publicly, here you go: > > " > Hi Rohit, > > Thanks for reaching out. I don't think git-flow

Re: [jira] [Closed] (CLOUDSTACK-6323) GetUser API always returns admin info

I'll update the Release-note accordingly. it only affect GetUser API call right ? *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 *|* Quebec *|* H3J 1S6 w clou

Jenkins build is still unstable: simulator-singlerun #83

See

Re: [VOTE] git workflow

Hi, Vincent (nvie) has allowed me to share his email publicly, here you go: " Hi Rohit, Thanks for reaching out. I don't think git-flow suits your use case very well. Git flow was mainly optimized as a set of rules to help bring forth "forward-only" releases, and does not support multiple conc

Re: Review Request 21696: CLOUDSTACK-6716: /usr volume is to small on SVMs. Reshuffling some space to fix that.

> On Aug. 8, 2014, 10:59 a.m., daan Hoogland wrote: > > b8deb6ba3f72d7da1944c47ee60db3ff4127da6c on master We'll keep an eye on the systemvm build and test the systemvms (I'll do for KVM, do I hear anyone else for XEN?) and if does not work revert; else we can cherry-pick on 4.4 as well. - R

Re: [jira] [Closed] (CLOUDSTACK-6323) GetUser API always returns admin info

On 08-Aug-2014, at 1:11 pm, Daan Hoogland wrote: > No, dumb question of mine (the only type of question that is really > dumb is one for a known answer) > > It seems unlikely that it could have worked with a parameter with a > conflicting name. If it didn't work at all before, we are fine. In th

Re: [jira] [Closed] (CLOUDSTACK-6323) GetUser API always returns admin info

No, dumb question of mine (the only type of question that is really dumb is one for a known answer) It seems unlikely that it could have worked with a parameter with a conflicting name. If it didn't work at all before, we are fine. In the unlikely otherwise, we should make the api still accept the

Re: Review Request 21696: CLOUDSTACK-6716: /usr volume is to small on SVMs. Reshuffling some space to fix that.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/21696/#review50026 --- Ship it! b8deb6ba3f72d7da1944c47ee60db3ff4127da6c on master - daan

Re: must read

On Fri, Aug 8, 2014 at 12:27 PM, Rohit Yadav wrote: > Hi Daan, > > On 08-Aug-2014, at 12:05 pm, Daan Hoogland wrote: > >> Rohit, >> >> A remark and a question: ... >> Why insist on fast-forward? (In the git-flow document it is emphasised >> that --no-ff should be used at all times) > > So, in my

Re: must read

Hi Daan, On 08-Aug-2014, at 12:05 pm, Daan Hoogland wrote: > Rohit, > > A remark and a question: > I would say merge and if not applicable cherry-pick. (to be sure that > the optimal solution is used) +1 > Why insist on fast-forward? (In the git-flow document it is emphasised > that --no-ff sh

Re: must read (git.git workflow)

git.git workflow is a logical superset of gitflow with shorter branch names. All the basic practices are the same. Unsurprisingly, perhaps :-) The key difference is the use of long lived stable branches rather than per-release stable branches that wither & die off. I would guess it’s a little e

Re: must read

Rohit, A remark and a question: I would say merge and if not applicable cherry-pick. (to be sure that the optimal solution is used) Why insist on fast-forward? (In the git-flow document it is emphasised that --no-ff should be used at all times) thanks, and thanks for seeing the first step to free

Re: must read

Another note on this blog/workflow/idea: Say I’ve a bug for multiple ACS releases, the way our workflow should be to fix it on the earliest ACS release branch we want to support and then to the next ones, finally on master and then feature/personal branches. Example, you fix on 4.1, then cherry

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

See -- [...truncated 7101 lines...] [WARNING] The requested profile "simulator" could not be activated because it does not exist. [simulator-hotfix-trigger] $ mvn -P developer -pl developer -

Re: must read

Hi Daan, On 08-Aug-2014, at 10:25 am, Daan Hoogland wrote: > And another thank you: > > > Long-running release branches for long-term support > > What are the main long-running branches in this model? > > We have a master branch – which in Subversion (SVN) terms you would > call trunk – that is

Regarding CLOUDSTACK-6169

Hi, I was going through the 4.4 issue list and came across an issue https://issues.apache.org/jira/browse/CLOUDSTACK-6169 ​I tried reproducing the issue and moved a VM between accounts via 'assignVirtualMachine' and observed that the resource_tags table in the database is not getting updated. The

Re: [CLOUDSTACK-6114][GSoC] End of second term approaching

Ian, This is terrific. I hope folks will take time to check all the scenarios you have covered. This will make testing cloudstack super easy as well as remove the need for devcloud (which tends to break in the latest releases). Great work, -sebastien On Aug 7, 2014, at 4:58 PM, Ian Duffy wr

Re: [GSoC] End of second term approaching

Great job Darren, I am excited to see VPC support in ec2stack and equally excited to see gcloud compatibility with stack (in addition to gcutil). You are in the last stretch, getting snapshots in ec2stack would be great. -sebastien On Aug 7, 2014, at 3:23 PM, Darren Brogan wrote: > Hi all, >

Re: List APIs Behavior

Thanks Daan. I will update the page. Regards, Gaurav On Fri, Aug 8, 2014 at 2:20 PM, Daan Hoogland wrote: > Gaurav, > > I think you are now pointing at one of the qualities of our API that > need to be addressed in 5.0 [1]. I may be wrong but I don't think a > standard behavior in these cases

Re: List APIs Behavior

Gaurav, I think you are now pointing at one of the qualities of our API that need to be addressed in 5.0 [1]. I may be wrong but I don't think a standard behavior in these cases is defined and every list api has a choice of several conventions to folow. Feel free to define what the behavior should

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

Ah Mike, I now see what you where commenting on. It seemed strange that you would urge to send out a mail in the actual thread that was send out as you so desire. 8} On Fri, Aug 8, 2014 at 10:33 AM, Saksham Srivastava wrote: > Agree, we should be using the same tag. > https://cwiki.apache.org/con

Re: List APIs Behavior

Hello, Can somebody please address this query? Regards, Gaurav On Thu, Aug 7, 2014 at 10:23 PM, Gaurav Aradhye wrote: > I want to understand the output of the list APIs when the entity is not > present / deleted. Suppose I create an account, create a network within it > and acquire a public I

Re: Review Request 22939: CLOUDSTACK-6460 - CLVM primary storage migration fails due to incorrect identification of source format.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22939/#review50024 --- seems fine except for the trailing whitespace. branch hotfix/4.4-646

Re: issues remaining for 4.4.1

I have created hotfix/4.4-6460 and am running a validation build on it, if no feedback before sunday night I will merge and include it. On Thu, Aug 7, 2014 at 10:27 PM, Daan Hoogland wrote: > Marcus, Edison, > > Can you have a look? It looks alright by me, but I have no time/env to test. > > than

Re: Review Request 22939: CLOUDSTACK-6460 - CLVM primary storage migration fails due to incorrect identification of source format.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22939/#review50023 --- Commit 536ec0578111cf85e93122deaf9a95270d66f778 in cloudstack's bran

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

Agree, we should be using the same tag. https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other -Original Message- From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] Sent: Thursday, August 7, 2014 11:29 PM To: dev@cloudstack.apache.org Cc: Alena

Re: must read

And another thank you: Long-running release branches for long-term support What are the main long-running branches in this model? We have a master branch – which in Subversion (SVN) terms you would call trunk – that is stable-ish. It is in a alpha/RC state. We have stable release branches for e

must read

thanks Rohit, I had missed this one. It contains obligatory release management knowledge for every keyboard toucher that is allowed to use git: https://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html I think if we all read this and then study a bit we don't need to discuss or branchin

Re: [VOTE] git workflow

Rohit, this is not a git-flow or gitflow discussion. It seems to be at times but it is not. It is a discussion about how to branch in our repository. That discussion should not end, but maybe so in this thread. On Fri, Aug 8, 2014 at 9:19 AM, Rohit Yadav wrote: > Hi all, > > Let’s end this discus

Re: [VOTE] git workflow

3 it should be made in a hotfix/4.4- branch and reviewed and merged from there On Fri, Aug 8, 2014 at 9:16 AM, Rajani Karuturi wrote: > A git workflow change will not solve the quality problems we have. They > have to be dealt with independently. Just because we are changing the way > we commit t

Re: [VOTE] git workflow

Hi all, Let’s end this discussion thread. I asked Vincent (nvie) and some friends from google and facebook on this and all of them recommended that this is not for us; then I read the whole thread again without prejudice or ego and I think it’s not for us though we should pick up couple of goo

Re: [VOTE] git workflow

I see a lot of confusion around the fact that the name of gitflow is being used. What was proposed was a model that could be supported by the tool gitflow, not a workflow exactly as gitflow 'prescribes' it. If we forget about gitflow for a moment and look at the branching model that we want we all

Re: [VOTE] git workflow

A git workflow change will not solve the quality problems we have. They have to be dealt with independently. Just because we are changing the way we commit the code doesnt mean we wont have any quality issues introduced by the commits. It just ensures that issues/fixes are properly transferred to t