[CS 4.1.0] Unable Migrate Volume From FC-SAN With ESXI 5.0.0 Hypervisor
Hi,
I'm working on a cloudstack 4.1.0 vmware cluster, after detach a data
volume of vm, migrate to another primary FC-SAN primary storage, exception
occured
But other commands works fine, snapshot, volume create or destroy , etc.
BYW, my volume to be migrated is 40G, and NFS based secondary has 100
capacity
DEBUG [agent.transport.Request] (AgentManager-Handler-13:) Seq
25-529272254: Processing: { Ans: , MgmtId: 203178712092966, via: 25, Ver:
v1, Flags: 110,
[{storage.CopyVolumeAnswer:{result:false,details:CopyVolumeCommand
failed due to exception: java.lang.Exception: Unable to finish the whole
process to package as a OVA
file\ncom.cloud.hypervisor.vmware.mo.VirtualMachineMO.exportVm(VirtualMachineMO.java:1336)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.exportVolumeToSecondaryStroage(VmwareStorageManagerImpl.java:758)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyVolumeToSecStorage(VmwareStorageManagerImpl.java:841)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:343)\ncom.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.execute(VmwareSecondaryStorageResourceHandler.java:137)\ncom.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:77)\ncom.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:54)\ncom.cloud.agent.Agent.processRequest(Agent.java:525)\ncom.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\ncom.cloud.utils.nio.Task.run(Task.java:83)\njava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)\njava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)\njava.lang.Thread.run(Thread.java:662)\n,wait:0}}]
}
DEBUG [agent.transport.Request] (Job-Executor-39:job-577) Seq 25-529272254:
Received: { Ans: , MgmtId: 203178712092966, via: 25, Ver: v1, Flags: 110,
{ CopyVolumeAnswer } }
DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-13:) Seq
25-529272254: No more commands found
ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-39:job-577)
Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to copy the volume
from the source primary storage pool to secondary storage.
at
com.cloud.storage.StorageManagerImpl.migrateVolumes(StorageManagerImpl.java:3263)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.storage.StorageManagerImpl.migrateVolume(StorageManagerImpl.java:3209)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd.execute(MigrateVolumeCmd.java:95)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-39:job-577) Complete
async job-577, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error
text: Failed to copy the volume from the source primary storage pool to
secondary storage.
---
Thanks,
Yitao(依涛 姜)
jiangyt.github.io
Jenkins build is still unstable: simulator-singlerun #248
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Jenkins build is still unstable: simulator-singlerun #249
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Re: Review Request 25145: CLOUDSTACK-7425: Fixed Failed to create network offering due to invalid service Lb
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25145/#review51971 --- Ship it! Ship It! - Raja Pullela On Aug. 28, 2014, 9:42 a.m., Gaurav Aradhye wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25145/ --- (Updated Aug. 28, 2014, 9:42 a.m.) Review request for cloudstack, sanjeev n, Santhosh Edukulla, and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7425 https://issues.apache.org/jira/browse/CLOUDSTACK-7425 Repository: cloudstack-git Description --- Network Offering creation failed because of a space in network offering config data. Fixed it. Diffs - tools/marvin/marvin/config/test_data.py ade8657 Diff: https://reviews.apache.org/r/25145/diff/ Testing --- Yes. Log: test_cleanup_persistent_network_1_true (test_persistent_networks.TestRestartPersistentNetwork) ... === TestName: test_cleanup_persistent_network_1_true | Status : SUCCESS === ok -- Ran 1 test in 456.489s OK Thanks, Gaurav Aradhye
Re: Review Request 25144: CLOUDSTACK-7439: Fix Unable to find VM issue in test_tags.py
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25144/#review51973 --- Ship it! Ship It! - Raja Pullela On Aug. 28, 2014, 9:33 a.m., Gaurav Aradhye wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25144/ --- (Updated Aug. 28, 2014, 9:33 a.m.) Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7439 https://issues.apache.org/jira/browse/CLOUDSTACK-7439 Repository: cloudstack-git Description --- The tag creation failed because the VM was expunged. Passed expunge=False while destroying VM so that tag is created on destroyed VM. Diffs - test/integration/component/test_tags.py 1e99ac1 Diff: https://reviews.apache.org/r/25144/diff/ Testing --- Yes. Log: Test creation of tag on stopped vm. ... === TestName: test_22_create_tag_destroyed_vm | Status : SUCCESS === ok -- Ran 1 test in 316.500s OK Thanks, Gaurav Aradhye
Re: [DISCUSS] Prevent force push on release and master branches
I worry that disabling force push will inhibit moving tags and deleting branches, two thing I definately want to keep on doing. On Sat, Aug 30, 2014 at 3:15 AM, David Nalley da...@gnsa.us wrote: Projects do not have the ability to specify their own hooks. You essentially get the same set as every other project in the Foundation using git. The reasons behind this are that essentially projects would have an incredibly divergent set of hooks, they would be unmaintainable long term. Infra has had experiences in the past where commit (or pre-commit) hooks were configurable and ended up causing massive performance impacts; and were incredibly difficult to trace down. Most hook functionality (though not in the case) can be accomplished with gitpubsub, which is what a majority of folks do who want hook-like functionality. You can ask/make the recommendation that the foundation disable force pushes across all branches of all repositories at the foundation. That may actually make a lot of sense. But I don't know that everyone will agree. (I tend to concur, I can't think of a good reason one would do a force push). --David On Fri, Aug 29, 2014 at 3:13 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote: Hi David, On 29-Aug-2014, at 6:59 pm, David Nalley da...@gnsa.us wrote: force pushes on master are already prohibited. The other branches allow that though. We already know this. The discussion is; 1. Should we put git hooks to prevent force pushes on all branches? (people would be still able to delete any remote branches though, which is another issue IMO that you can delete any remote branch other than master) 2. Any reason we should not do that, for example if anyone has a good reason to use force push? Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Build http://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Support http://shapeblue.com/cloudstack-infrastructure-support/ CloudStack Bootcamp Training Courses http://shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark. -- Daan
Re: [ACS44][DISCUSS]release 4.4.1
Hey Mike, You guys are not supposed to add random red holidays to your calendars. You're the commy bashers. May 1st not enough for ya'll? On Mon, Sep 1, 2014 at 12:00 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just an FYI that it's Labor Day Weekend in the U.S., so you might not get many, if any, replies until Tuesday. On Sat, Aug 30, 2014 at 2:06 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: On 2014-08-30, 4:01 PM, Daan Hoogland wrote: H, How is the felling on list about 4.4.1? Do we have a stable enough branch 4.4 at this moment? Especially the answer on this of KVM saffy people is appreciated. I am running on 4.4.1 since a week now. I did hit couple small bugs, but no real blocker. We also try to fix the SSL offload code to work with projects. We would really really like to get this feature in 4.4.1. FG -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™* -- Daan
Re: Review Request 24991: CLOUDSTACK-6697: BigSwitchVns plugin update
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24991/#review51976 --- KC, Thanks for submitting this review, looking forward to seeing the updated version of the bigswitch plugin in CloudStack. You replace all the existing VNS code with BCF code, is there a need to deal with users that want to upgrade from VNS to the new system? As part of our focus on more and better testing, could you include a functional test that we could use to verify correct behaviour of the plugin? It is OK if it only works if you hve the hardware/software available but we ned some way to integrate that test in our CI systems. Have a look at the test/integration/ directory in the CloudStack source for some ideas. Could you add the following to the pom.xml? This will help us verify license issues. plugins plugin groupIdcom.mycila/groupId artifactIdlicense-maven-plugin/artifactId executions execution idcloudstack-checklicence/id phaseprocess-classes/phase goals goalcheck/goal /goals /execution /executions /plugin As part of the review i'll be running both findbugs and PMD checks as well. I'll update the review if i find any issues there. Cheers, Hugo setup/db/create-schema.sql https://reviews.apache.org/r/24991/#comment90693 Please don't make any change to this file. setup/db/db/schema-307to410.sql https://reviews.apache.org/r/24991/#comment90694 No need to modify the schemas for any release except the current release. - Hugo Trippaers On Aug. 22, 2014, 11:06 p.m., Kuang-Ching Wang wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24991/ --- (Updated Aug. 22, 2014, 11:06 p.m.) Review request for cloudstack, Chiradeep Vittal, David Nalley, Sebastien Goasguen, and Hugo Trippaers. Repository: cloudstack-git Description --- CLOUDSTACK-6697: BigSwitchVns plugin update This patch updates the BigSwitch network plugin in the following ways: - provides compatibility with Big Switch's Big Cloud Fabric controller - provides L2 Connectivity service - uses HTTPS with sticky/trust-always certificate handling - Updates plugin terminology in package name, code, and GUI to BigSwitchBCF with isolation method referred to as BCF_SEGMENT Diffs - api/src/com/cloud/network/Network.java 55502df669dcc454f061a9a9e9940a09be2d5916 api/src/com/cloud/network/PhysicalNetwork.java 7c9349d932771fdbecc4a0b1ae4cad28b3d67857 client/WEB-INF/classes/resources/messages.properties 475fe6c95f1fc67ea86a731512c522c70091af34 client/WEB-INF/classes/resources/messages_fr_FR.properties 004187f69b4f8449c88214ff3b047ef603ad65dc client/WEB-INF/classes/resources/messages_ja_JP.properties ed6a1b1a0ba3cdac5fccb456617238b541fa55a5 client/WEB-INF/classes/resources/messages_ko_KR.properties ce79d2e5b27d861960c8ee1fd4b1e099ed883ef3 client/WEB-INF/classes/resources/messages_nl_NL.properties 89ef828a3c157228680b90adbcb76b182f342638 client/WEB-INF/classes/resources/messages_pt_BR.properties 8ee08ba3cbbfa3285b7ad728b8b119ee9e379c65 client/WEB-INF/classes/resources/messages_ru_RU.properties ff68668e6ff75546236a11d29e37d8d4ad1f58f1 client/WEB-INF/classes/resources/messages_zh_CN.properties 2c497bc893e50ac3132d91e9b7147c4efa911aea client/pom.xml d87fc4573ab305a564cb246f7cd5aa8eaef28340 client/tomcatconf/commands.properties.in 3191bbf41b25d49f258e2504063882761e6909ca engine/schema/src/com/cloud/user/dao/VmDiskStatisticsDaoImpl.java e1136d3cf567b73fd1198181aea4d6995df6b78a plugins/network-elements/bigswitch-vns/findbugsExcludeFilter.xml d37285017e89a74b14f0f171c2bc3e86af4c3e4d plugins/network-elements/bigswitch-vns/pom.xml 6665454e4190f1d10fe91dfa62828e456758d0d8 plugins/network-elements/bigswitch-vns/resources/META-INF/cloudstack/vns/module.properties 5783d38e5cb78be0d418c80981246d721d18b62a plugins/network-elements/bigswitch-vns/resources/META-INF/cloudstack/vns/spring-vns-context.xml d5bb92afe3d3051dbdd4b4d49698c313c77d255f plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/CreateVnsNetworkAnswer.java e950abe3bed85b75a20be2b8c4537a2fbd6be39e plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/CreateVnsNetworkCommand.java 534bb7f9f9154a652a20310fe020bddc4249ef54 plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/CreateVnsPortAnswer.java 82c2fe90d63e0148bca8de9ce8612e4dd53cf735 plugins/network-elements/bigswitch-vns/src/com/cloud/agent/api/CreateVnsPortCommand.java
Re: [DISCUSS] Prevent force push on release and master branches
On 01-Sep-2014, at 9:55 am, Daan Hoogland daan.hoogl...@gmail.com wrote: I worry that disabling force push will inhibit moving tags and deleting branches, two thing I definately want to keep on doing. I’ve worked on git hooks before, and you can still be able to delete tags and branches if we were to disable force pushes. This is technically possible. On Sat, Aug 30, 2014 at 3:15 AM, David Nalley da...@gnsa.us wrote: Projects do not have the ability to specify their own hooks. You essentially get the same set as every other project in the Foundation using git. The reasons behind this are that essentially projects would have an incredibly divergent set of hooks, they would be unmaintainable long term. Infra has had experiences in the past where commit (or pre-commit) hooks were configurable and ended up causing massive performance impacts; and were incredibly difficult to trace down. Most hook functionality (though not in the case) can be accomplished with gitpubsub, which is what a majority of folks do who want hook-like functionality. You can ask/make the recommendation that the foundation disable force pushes across all branches of all repositories at the foundation. That may actually make a lot of sense. But I don't know that everyone will agree. (I tend to concur, I can't think of a good reason one would do a force push). --David On Fri, Aug 29, 2014 at 3:13 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote: Hi David, On 29-Aug-2014, at 6:59 pm, David Nalley da...@gnsa.us wrote: force pushes on master are already prohibited. The other branches allow that though. We already know this. The discussion is; 1. Should we put git hooks to prevent force pushes on all branches? (people would be still able to delete any remote branches though, which is another issue IMO that you can delete any remote branch other than master) 2. Any reason we should not do that, for example if anyone has a good reason to use force push? Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Build http://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Support http://shapeblue.com/cloudstack-infrastructure-support/ CloudStack Bootcamp Training Courses http://shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark. -- Daan Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Supporthttp://shapeblue.com/cloudstack-infrastructure-support/ CloudStack Bootcamp Training Courseshttp://shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue
Jenkins build is still unstable: simulator-singlerun #250
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
RE: [ACS44][DISCUSS]release 4.4.1
Interestingly, the reason Labour Day is on May 1 in the rest of the world is the same reason it's not in May in the US and Canada, to do with communists and anarchists commemorating a riot in Chicago. See http://en.wikipedia.org/wiki/Labor_Day http://en.wikipedia.org/wiki/Haymarket_affair -- Stephen Turner -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 01 September 2014 09:05 To: dev; Mike Tutkowski Cc: Francois Gaudreault Subject: Re: [ACS44][DISCUSS]release 4.4.1 Hey Mike, You guys are not supposed to add random red holidays to your calendars. You're the commy bashers. May 1st not enough for ya'll? On Mon, Sep 1, 2014 at 12:00 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just an FYI that it's Labor Day Weekend in the U.S., so you might not get many, if any, replies until Tuesday. On Sat, Aug 30, 2014 at 2:06 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: On 2014-08-30, 4:01 PM, Daan Hoogland wrote: H, How is the felling on list about 4.4.1? Do we have a stable enough branch 4.4 at this moment? Especially the answer on this of KVM saffy people is appreciated. I am running on 4.4.1 since a week now. I did hit couple small bugs, but no real blocker. We also try to fix the SSL offload code to work with projects. We would really really like to get this feature in 4.4.1. FG -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™* -- Daan
Jenkins build is still unstable: simulator-singlerun #251
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Re: [DISCUSS] Prevent force push on release and master branches
If force push is disabled, feature branches wont be able to rebase on master directly unless they create a temp branch or do a merge.[1] Moving tags aren't recommended. see discussion on Re-tagging in git-tag man page [2] [1] http://stackoverflow.com/questions/8939977/git-push-rejected-after-feature-branch-rebase [2] https://www.kernel.org/pub/software/scm/git/docs/git-tag.html ~Rajani On Mon, Sep 1, 2014 at 1:45 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote: On 01-Sep-2014, at 9:55 am, Daan Hoogland daan.hoogl...@gmail.com wrote: I worry that disabling force push will inhibit moving tags and deleting branches, two thing I definately want to keep on doing. I’ve worked on git hooks before, and you can still be able to delete tags and branches if we were to disable force pushes. This is technically possible. On Sat, Aug 30, 2014 at 3:15 AM, David Nalley da...@gnsa.us wrote: Projects do not have the ability to specify their own hooks. You essentially get the same set as every other project in the Foundation using git. The reasons behind this are that essentially projects would have an incredibly divergent set of hooks, they would be unmaintainable long term. Infra has had experiences in the past where commit (or pre-commit) hooks were configurable and ended up causing massive performance impacts; and were incredibly difficult to trace down. Most hook functionality (though not in the case) can be accomplished with gitpubsub, which is what a majority of folks do who want hook-like functionality. You can ask/make the recommendation that the foundation disable force pushes across all branches of all repositories at the foundation. That may actually make a lot of sense. But I don't know that everyone will agree. (I tend to concur, I can't think of a good reason one would do a force push). --David On Fri, Aug 29, 2014 at 3:13 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote: Hi David, On 29-Aug-2014, at 6:59 pm, David Nalley da...@gnsa.us wrote: force pushes on master are already prohibited. The other branches allow that though. We already know this. The discussion is; 1. Should we put git hooks to prevent force pushes on all branches? (people would be still able to delete any remote branches though, which is another issue IMO that you can delete any remote branch other than master) 2. Any reason we should not do that, for example if anyone has a good reason to use force push? Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Build http://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment framework http://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Support http://shapeblue.com/cloudstack-infrastructure-support/ CloudStack Bootcamp Training Courses http://shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark. -- Daan Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Build http://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Support http://shapeblue.com/cloudstack-infrastructure-support/ CloudStack Bootcamp Training Courses http://shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not
Re: [DISCUSS] Prevent force push on release and master branches
Rajani, I agree that moving tags is not best practice but with our release candidate custom it is better then not tagging until certain. On Mon, Sep 1, 2014 at 11:25 AM, Rajani Karuturi raj...@apache.org wrote: If force push is disabled, feature branches wont be able to rebase on master directly unless they create a temp branch or do a merge.[1] Moving tags aren't recommended. see discussion on Re-tagging in git-tag man page [2] [1] http://stackoverflow.com/questions/8939977/git-push-rejected-after-feature-branch-rebase [2] https://www.kernel.org/pub/software/scm/git/docs/git-tag.html ~Rajani On Mon, Sep 1, 2014 at 1:45 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote: On 01-Sep-2014, at 9:55 am, Daan Hoogland daan.hoogl...@gmail.com wrote: I worry that disabling force push will inhibit moving tags and deleting branches, two thing I definately want to keep on doing. I’ve worked on git hooks before, and you can still be able to delete tags and branches if we were to disable force pushes. This is technically possible. On Sat, Aug 30, 2014 at 3:15 AM, David Nalley da...@gnsa.us wrote: Projects do not have the ability to specify their own hooks. You essentially get the same set as every other project in the Foundation using git. The reasons behind this are that essentially projects would have an incredibly divergent set of hooks, they would be unmaintainable long term. Infra has had experiences in the past where commit (or pre-commit) hooks were configurable and ended up causing massive performance impacts; and were incredibly difficult to trace down. Most hook functionality (though not in the case) can be accomplished with gitpubsub, which is what a majority of folks do who want hook-like functionality. You can ask/make the recommendation that the foundation disable force pushes across all branches of all repositories at the foundation. That may actually make a lot of sense. But I don't know that everyone will agree. (I tend to concur, I can't think of a good reason one would do a force push). --David On Fri, Aug 29, 2014 at 3:13 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote: Hi David, On 29-Aug-2014, at 6:59 pm, David Nalley da...@gnsa.us wrote: force pushes on master are already prohibited. The other branches allow that though. We already know this. The discussion is; 1. Should we put git hooks to prevent force pushes on all branches? (people would be still able to delete any remote branches though, which is another issue IMO that you can delete any remote branch other than master) 2. Any reason we should not do that, for example if anyone has a good reason to use force push? Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Build http://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment framework http://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Support http://shapeblue.com/cloudstack-infrastructure-support/ CloudStack Bootcamp Training Courses http://shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark. -- Daan Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Build http://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Support
Jenkins build is still unstable: simulator-singlerun #252
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Re: Review Request 25097: Test script to verify vm deployment with two networks in SG enabled advanced zone
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25097/#review51984 --- test/integration/component/test_advancedsg_networks.py https://reviews.apache.org/r/25097/#comment90696 Please add addtional check to make sure deployed vm is actually getting ip from additional subnet range or not. get ip from current deployed vm and check this ip is with in new subnet ip range list or not. or Also before calling virtualmachine.create(for vm2) ,check the current ip range is full. Use listCapcity API with type =8 as paraameter to cross check the Ip capacity check - suresh sadhu On Aug. 27, 2014, 1:14 p.m., sanjeev n wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25097/ --- (Updated Aug. 27, 2014, 1:14 p.m.) Review request for cloudstack, suresh sadhu, Santhosh Edukulla, and SrikanteswaraRao Talluri. Repository: cloudstack-git Description --- Test script to verify vm deployment with two networks in SG enabled advanced zone. Involves following steps: 1.Deploy SG enabled advanced zone with only 4 ip addresses in guest ip range using simulator 2.Deploy one guest vm in the default shared guest network so that all the IP addresses will be consumed 3.Add another guest network in the zone created at step1 4.Deploy vm without passing the network id. It should pick the network with sufficient resources Diffs - test/integration/component/test_advancedsg_networks.py 85ab697 tools/marvin/marvin/config/test_data.cfg 5a3d8aa Diff: https://reviews.apache.org/r/25097/diff/ Testing --- @Desc: VM Cannot deploy to second network in advanced SG network ... === TestName: test_34_DeployVM_in_SecondSGNetwork | Status : SUCCESS === ok -- Ran 1 test in 357.750s OK Thanks, sanjeev n
Build failed in Jenkins: build-master #1513
See http://jenkins.buildacloud.org/job/build-master/1513/changes Changes: [Ian Duffy] Fix RAT issue -- [...truncated 3885 lines...] [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/md5/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ cloud-plugin-user-authenticator-md5 --- [INFO] Compiling 1 source file to http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/md5/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-plugin-user-authenticator-md5 --- [INFO] Surefire report directory: http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/md5/target/surefire-reports --- T E S T S --- Running com.cloud.server.auth.MD5UserAuthenticatorTest log4j:WARN No appenders could be found for logger (com.cloud.server.auth.MD5UserAuthenticator). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.756 sec Results : Tests run: 4, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] [INFO] Building Apache CloudStack Plugin - User Authenticator Plain Text 4.5.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloud-plugin-user-authenticator-plaintext --- [INFO] Deleting http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/plain-text/target (includes = [**/*], excludes = []) [INFO] Deleting http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/plain-text (includes = [target, dist], excludes = []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-plugin-user-authenticator-plaintext --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-plugin-user-authenticator-plaintext --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-plugin-user-authenticator-plaintext --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-plugin-user-authenticator-plaintext --- [INFO] Compiling 1 source file to http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/plain-text/target/classes [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ cloud-plugin-user-authenticator-plaintext --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/plain-text/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ cloud-plugin-user-authenticator-plaintext --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-plugin-user-authenticator-plaintext --- [INFO] Surefire report directory: http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/plain-text/target/surefire-reports --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] [INFO] Building Apache CloudStack Plugin - User Authenticator SAML2 4.5.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloud-plugin-user-authenticator-saml2 --- [INFO] Deleting http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/saml2/target (includes = [**/*], excludes = []) [INFO] Deleting http://jenkins.buildacloud.org/job/build-master/ws/plugins/user-authenticators/saml2 (includes = [target, dist], excludes = []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-plugin-user-authenticator-saml2 --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-plugin-user-authenticator-saml2 --- [INFO] [INFO] ---
Jenkins build is still unstable: simulator-singlerun #253
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Re: Review Request 24420: vGPU Test Automation ( Check for vGPU resources VM lifecycle tests)
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24420/#review51988 --- Commited the changes @ Repository: cloudstack Updated Branches: refs/heads/master e16ab59c5 - 615c070c0 vgpu lifecycle test cases with review comments Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/615c070c Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/615c070c Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/615c070c Branch: refs/heads/master Commit: 615c070c0a1b86c00b7b878ac32a183bcd8b1ab1 Parents: e16ab59 Author: Abhinav Roy abhinav@citrix.com Authored: Thu Aug 21 13:24:54 2014 +0530 Committer: sailajamada sailaja.m...@citrix.com Committed: Mon Sep 1 14:13:39 2014 +0530 -- .../component/test_deploy_vgpu_vm.py| 321 +++ 1 file changed, 264 insertions(+), 57 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/615c070c/test/integration/component/test_deploy_vgpu_vm.py - sailaja mada On Aug. 22, 2014, 2:09 p.m., abhinav roy wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24420/ --- (Updated Aug. 22, 2014, 2:09 p.m.) Review request for cloudstack, Doug Clark, John Dilley, sailaja mada, and Sanjay Tripathi. Repository: cloudstack-git Description --- This Diff includes vGPU VM lifecycle tests as well as a function to validate the vGPU resources present in a vGPU VM deployed on CS. It has the following tests : 1. A function to validate vGPU resources in a VM. It does validation on both the host as well as on CS. It includes following lifecycle tests. 2. Deploy VM 3. Stop VM 4. Start VM 5. Restore VM 6. Reboot VM 7. Destroy VM 8. Recover VM NOTE : VM lifecycle test cases were included in this script after the 1st rouund of review with Doug. We decided to include those tests here just to remove the overhead of registering template again. so, now there is no use of this review request https://reviews.apache.org/r/24425/ Diffs - test/integration/component/test_deploy_vgpu_vm.py fd3f374 Diff: https://reviews.apache.org/r/24420/diff/ Testing --- Testing : 1. Executed the script on non GPU test setup and ensured tests being skipped. 2. Executed on K2 GPU drivers installed setup and ensured all lifecycle test cases are working fine and the function is checking for the vGPU resources in a vGPU VM. Thanks, abhinav roy
Re: Review Request 24420: vGPU Test Automation ( Check for vGPU resources VM lifecycle tests)
On Aug. 26, 2014, 2:41 p.m., John Dilley wrote: Ship It! Repository: cloudstack Updated Branches: refs/heads/master e16ab59c5 - 615c070c0 vgpu lifecycle test cases with review comments Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/615c070c Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/615c070c Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/615c070c Branch: refs/heads/master Commit: 615c070c0a1b86c00b7b878ac32a183bcd8b1ab1 Parents: e16ab59 Author: Abhinav Roy abhinav@citrix.com Authored: Thu Aug 21 13:24:54 2014 +0530 Committer: sailajamada sailaja.m...@citrix.com Committed: Mon Sep 1 14:13:39 2014 +0530 -- .../component/test_deploy_vgpu_vm.py| 321 +++ 1 file changed, 264 insertions(+), 57 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/615c070c/test/integration/component/test_deploy_vgpu_vm.py - sailaja --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24420/#review51527 --- On Aug. 22, 2014, 2:09 p.m., abhinav roy wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/24420/ --- (Updated Aug. 22, 2014, 2:09 p.m.) Review request for cloudstack, Doug Clark, John Dilley, sailaja mada, and Sanjay Tripathi. Repository: cloudstack-git Description --- This Diff includes vGPU VM lifecycle tests as well as a function to validate the vGPU resources present in a vGPU VM deployed on CS. It has the following tests : 1. A function to validate vGPU resources in a VM. It does validation on both the host as well as on CS. It includes following lifecycle tests. 2. Deploy VM 3. Stop VM 4. Start VM 5. Restore VM 6. Reboot VM 7. Destroy VM 8. Recover VM NOTE : VM lifecycle test cases were included in this script after the 1st rouund of review with Doug. We decided to include those tests here just to remove the overhead of registering template again. so, now there is no use of this review request https://reviews.apache.org/r/24425/ Diffs - test/integration/component/test_deploy_vgpu_vm.py fd3f374 Diff: https://reviews.apache.org/r/24420/diff/ Testing --- Testing : 1. Executed the script on non GPU test setup and ensured tests being skipped. 2. Executed on K2 GPU drivers installed setup and ensured all lifecycle test cases are working fine and the function is checking for the vGPU resources in a vGPU VM. Thanks, abhinav roy
Re: [DISCUSS] Prevent force push on release and master branches
On Aug 30, 2014, at 3:15 AM, David Nalley da...@gnsa.us wrote: You can ask/make the recommendation that the foundation disable force pushes across all branches of all repositories at the foundation. That may actually make a lot of sense. But I don't know that everyone will agree. (I tend to concur, I can't think of a good reason one would do a force push). You know I am a little surprised force push is allowed. When Paul first looked into setting up r/w git, a major foundation concern was getting a sufficiently auditable revision history (a strong point of svn), and IIRC quite some effort was spent locking things down [1]. The fact it _isn’t_ fully locked down right now is a deviation from the original plan. Seems pretty likely to me there was a use case that required opening it up. I would guess tag moving to be a major argument, which I _think_ requires forcing. cheers, Leo [1] http://apache.markmail.org/thread/7ztq2pwm6456zqmy
Jenkins build is still unstable: simulator-singlerun #254
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Jenkins build is back to normal : build-master #1514
See http://jenkins.buildacloud.org/job/build-master/1514/changes
Review Request 25228: hitting java.lang.reflect.InvocationTargetException while starting usage server
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25228/ --- Review request for cloudstack, Frank Zhang and Rayees Namathponnan. Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-7316 https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-7316 Repository: cloudstack-git Description --- Usage server is failing to start when we install Usage server on the management server with DB encryption enabled. Usage is server is unable to get key file from the classpath. Diffs - packaging/centos63/cloud.spec 790f57b Diff: https://reviews.apache.org/r/25228/diff/ Testing --- Tested on centos 6.3 and rhel 7 Thanks, Damodar Reddy Talakanti
RE: jsonObj is not defined. UI development problem.
Can somebody help me in that? I’ve tried to contact Jessica Wang (main changer
in that ui part, but haven’t got an answer yet)
Kind regards,
Ilia Shakitko
Innovation Engineer
LeaseWeb Technologies B.V.
T: +31 20 316 0235
E: i.shaki...@tech.leaseweb.com
W: www.leaseweb.comhttp://www.leaseweb.com
Luttenbergweg 8, 1101 EC Amsterdam, The Netherlands
From: Ilia Shakitko
Sent: woensdag, 27 augustus, 2014 11:54
To: dev@cloudstack.apache.org
Subject: jsonObj is not defined. UI development problem.
I am working on some ui changes in cloudstack. And I am adding some lines (to
display tags for SecurityGroupRules) in network.js: line #4670 (before actions:
{ destroy: { … on line #4814):
tags: cloudStack.api.tags({
resourceType: 'SecurityGroupRule',
contextId: 'multiRule'
}),
I made it 1 to 1 with FirewallRule. But it doesn’t work. I spend quite a lot of
time on trying to figure out why. It renders the window, but without anything:
http://clip2net.com/s/iO0mAh (http://clip2net.com/s/iO0mWk)
So as I understood debugging the code, it runs in issues in sharedFunctions.js
file when it tries to read “jsonObj” but it’s empty
(http://clip2net.com/s/iO0lwy). I couldn’t figure out why is it empty and where
do I fill it with data from “context”…
Could you help me with correct direction? What am I missing? ☺
Kind regards,
Ilia Shakitko
Innovation Engineer
LeaseWeb Technologies B.V.
T: +31 20 316 0235
E: i.shaki...@tech.leaseweb.commailto:i.shaki...@tech.leaseweb.com
W: www.leaseweb.comhttp://www.leaseweb.com
Luttenbergweg 8, 1101 EC Amsterdam, The Netherlands
Re: [DISCUSS] Prevent force push on release and master branches
I think you could still delete remote tag and retag and push, instead of doing a force push? But yeah, if this is needed we should keep things as it is. I just wanted to bring this issue to everyone and see if we should do something about it. On 01-Sep-2014, at 2:04 pm, Leo Simons lsim...@schubergphilis.com wrote: On Aug 30, 2014, at 3:15 AM, David Nalley da...@gnsa.us wrote: You can ask/make the recommendation that the foundation disable force pushes across all branches of all repositories at the foundation. That may actually make a lot of sense. But I don't know that everyone will agree. (I tend to concur, I can't think of a good reason one would do a force push). You know I am a little surprised force push is allowed. When Paul first looked into setting up r/w git, a major foundation concern was getting a sufficiently auditable revision history (a strong point of svn), and IIRC quite some effort was spent locking things down [1]. The fact it _isn’t_ fully locked down right now is a deviation from the original plan. Seems pretty likely to me there was a use case that required opening it up. I would guess tag moving to be a major argument, which I _think_ requires forcing. cheers, Leo [1] http://apache.markmail.org/thread/7ztq2pwm6456zqmy Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Supporthttp://shapeblue.com/cloudstack-infrastructure-support/ CloudStack Bootcamp Training Courseshttp://shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Unable to start a VM due to insufficient capacity
Hello, I have installed cs 4.3 on Ubuntu 14.04 LTS. Created the usual infra, registered a couple of ISO's, and tried to created a instance using the ISO, via the gui. Comes out with some error. Any ideas on how to fix this? Thanks Regards, Giri 2014-09-01 17:21:26,551 DEBUG [c.c.a.ApiServlet] (catalina-exec-6:ctx-703486f7 ctx-ee65bd67) ===END=== XXX.XXX.XXX.5 -- GET command=queryAsyncJobResultjobId=1b7d53c6-256a-4721-b69c-d68c1f6d7d42response=jsonsessionkey=e6F89zbOUS4dR2%2FmrkznQBxeQ%2BM%3D_=1409572286355 2014-09-01 17:21:26,733 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-6:ctx-d1e72afb) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to insufficient capacity at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:605) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy169.startVirtualMachine(Unknown Source) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|ubuntu-12-04-64bit-admin-Instance]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:921) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:601)
Jenkins build is still unstable: simulator-singlerun #255
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Re: Unable to start a VM due to insufficient capacity
Give us more of the logs. Preferably everything from the moment you press launch until the exception occurs. -- Erik On Mon, Sep 1, 2014 at 3:18 PM, Giri Prasad g_p...@yahoo.com.invalid wrote: Hello, I have installed cs 4.3 on Ubuntu 14.04 LTS. Created the usual infra, registered a couple of ISO's, and tried to created a instance using the ISO, via the gui. Comes out with some error. Any ideas on how to fix this? Thanks Regards, Giri 2014-09-01 17:21:26,551 DEBUG [c.c.a.ApiServlet] (catalina-exec-6:ctx-703486f7 ctx-ee65bd67) ===END=== XXX.XXX.XXX.5 -- GET command=queryAsyncJobResultjobId=1b7d53c6-256a-4721-b69c-d68c1f6d7d42response=jsonsessionkey=e6F89zbOUS4dR2%2FmrkznQBxeQ%2BM%3D_=1409572286355 2014-09-01 17:21:26,733 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-6:ctx-d1e72afb) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to insufficient capacity at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:605) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy169.startVirtualMachine(Unknown Source) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|ubuntu-12-04-64bit-admin-Instance]Scope=interface com.cloud.dc.DataCenter; id=1 at
Re: [BLOCKED] Unable to connect to management server on current master builds
I don't have access to that Jenkins instance beyond the public access to know what it's actually running etc. Could you send a separate email requesting for access to the instance's jobs? There's two levels of access and providing access to configure new jobs and administer from the UI is easy enough. Permitting key based access to the instance can also be done based on needs and discretion of the project. There's no strict rules around it afaik.
Re: Integration Tests on TravisCI
Sorry for the late reply, was away for some time.. On 21 aug. 2014, at 19:40, Edison Su edison...@citrix.com wrote: -Original Message- From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers Sent: Thursday, August 21, 2014 5:10 AM To: dev@cloudstack.apache.org Subject: Re: Integration Tests on TravisCI Hey guys, Just to make sure we are all on the same page on this. There are several initiatives to bolster our CI capabilities and some of them are overlapping. * There are ongoing discussion to push for a CI environment at the ASF * There are a number of companies donating hardware/cloud instances to beef up jenkins.buildacloud.org Sorry for my ignorance, I don't know the situation yet. Can't wait for it to happen. Jenkins.buildacloud.org is already being supported by multiple companies and individuals, like Citrix, Schuberg Philis and the company Erik Weber is working for. David donated some space in his own private cloud as well. So we have quite decent resources already. We just need some more specialized equipment like F5, netscaler etc. * Edison is doing CI builds on Amazon i believe * There is this TravisCI initiative While they are all very good, overlapping effort means we are wasting somebodies time somewhere. With a delicate a subject as CI we should try to avoid that i think. I'll happily stop working on the CI stuff in jenkins.buildacloud.org for example and focus my efforts on Travis. So i just want to know where we want to put our effort. I don't think jenkins.buildacloud.org will go away. IMHO, the free TravisCI is good for simulator test, the hosted TravisCI Is expensive. Nevertheless, we need hosted CI to test against real hardware, that's jenkins.buildacloud.orgcan help. Cheers, Hugo On 21 aug. 2014, at 14:02, Ian Duffy i...@ianduffy.ie wrote: Santosh, What command/flags did you use for the above test output? On 14 August 2014 17:22, Santhosh Edukulla santhosh.eduku...@citrix.com wrote: Ian, I just installed latest marvin after cloudstack build on master, and ran tests against the simulator from smoke folder, below are the results. All passed, except one, i believe that as well could be some global param or some config issue. I hope you want to install, use latest marvin and test suites from master. === TestName: test_DeployVmAntiAffinityGroup | Status : SUCCESS === === TestName: test_deployvm_firstfit | Status : SUCCESS === === TestName: test_deployvm_userconcentrated | Status : SUCCESS === === TestName: test_deployvm_userdispersing | Status : SUCCESS === === TestName: test_01_create_disk_offering | Status : SUCCESS === === TestName: test_02_create_sparse_type_disk_offering | Status : SUCCESS === === TestName: test_04_create_fat_type_disk_offering | Status : SUCCESS === === TestName: test_02_edit_disk_offering | Status : SUCCESS === === TestName: test_03_delete_disk_offering | Status : SUCCESS === === TestName: test_UpdateConfigParamWithScope | Status : SUCCESS === === TestName: test_dedicateGuestVlanRange | Status : SUCCESS === === TestName: test_01_create_iso | Status : SUCCESS === === TestName: test_02_edit_iso | Status : SUCCESS === === TestName: test_03_delete_iso | Status : SUCCESS === === TestName: test_05_iso_permissions | Status : SUCCESS === === TestName: test_nic_secondaryip_add_remove | Status : SUCCESS === === TestName: test_delete_account | Status : SUCCESS === === TestName: test_public_ip_admin_account | Status : SUCCESS === === TestName: test_public_ip_user_account | Status : SUCCESS === === TestName: test_releaseIP | Status : SUCCESS === === TestName: test_extendPhysicalNetworkVlan | Status : SUCCESS === === TestName: test_UpdateStorageOverProvisioningFactor | Status : SUCCESS === === TestName: test_createPortablePublicIPAcquire | Status : SUCCESS === === TestName: test_createPortablePublicIPRange | Status : SUCCESS === === TestName: test_01_primary_storage_nfs | Status : SUCCESS === === TestName: test_privategw_acl | Status : SUCCESS === === TestName: test_dedicatePublicIpRange | Status : SUCCESS === === TestName: test_create_pvlan_network | Status : SUCCESS === === TestName: test_createRegion | Status : SUCCESS === === TestName: test_01_reset_vm_on_reboot | Status : SUCCESS === === TestName: test_01_updatevolumedetail | Status : SUCCESS === === TestName: test_03_restart_network_cleanup | Status : SUCCESS === === TestName: test_05_router_basic | Status : SUCCESS === === TestName: test_06_router_advanced | Status : SUCCESS === === TestName: test_07_stop_router | Status : SUCCESS === === TestName: test_08_start_router | Status : SUCCESS === === TestName: test_09_reboot_router | Status : SUCCESS === === TestName: test_01_sys_vm_start | Status : SUCCESS === === TestName: test_02_sys_template_ready | Status : SUCCESS === === TestName:
Fwd: [CS 4.1.0] Unable Migrate Volume From FC-SAN With ESXI 5.0.0 Hypervisor
Do you hava any ideas ?
---
Thanks,
Yitao(依涛 姜)
jiangyt.github.io
-- Forwarded message --
From: Yitao Jiang willier...@gmail.com
Date: Mon, Sep 1, 2014 at 2:00 PM
Subject: [CS 4.1.0] Unable Migrate Volume From FC-SAN With ESXI 5.0.0
Hypervisor
To: dev@cloudstack.apache.org dev@cloudstack.apache.org
Hi,
I'm working on a cloudstack 4.1.0 vmware cluster, after detach a data
volume of vm, migrate to another primary FC-SAN primary storage, exception
occured
But other commands works fine, snapshot, volume create or destroy , etc.
BYW, my volume to be migrated is 40G, and NFS based secondary has 100
capacity
DEBUG [agent.transport.Request] (AgentManager-Handler-13:) Seq
25-529272254: Processing: { Ans: , MgmtId: 203178712092966, via: 25, Ver:
v1, Flags: 110,
[{storage.CopyVolumeAnswer:{result:false,details:CopyVolumeCommand
failed due to exception: java.lang.Exception: Unable to finish the whole
process to package as a OVA
file\ncom.cloud.hypervisor.vmware.mo.VirtualMachineMO.exportVm(VirtualMachineMO.java:1336)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.exportVolumeToSecondaryStroage(VmwareStorageManagerImpl.java:758)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyVolumeToSecStorage(VmwareStorageManagerImpl.java:841)\ncom.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:343)\ncom.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.execute(VmwareSecondaryStorageResourceHandler.java:137)\ncom.cloud.storage.resource.VmwareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:77)\ncom.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:54)\ncom.cloud.agent.Agent.processRequest(Agent.java:525)\ncom.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\ncom.cloud.utils.nio.Task.run(Task.java:83)\njava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)\njava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)\njava.lang.Thread.run(Thread.java:662)\n,wait:0}}]
}
DEBUG [agent.transport.Request] (Job-Executor-39:job-577) Seq 25-529272254:
Received: { Ans: , MgmtId: 203178712092966, via: 25, Ver: v1, Flags: 110,
{ CopyVolumeAnswer } }
DEBUG [agent.manager.AgentAttache] (AgentManager-Handler-13:) Seq
25-529272254: No more commands found
ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-39:job-577)
Unexpected exception while executing
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to copy the volume
from the source primary storage pool to secondary storage.
at
com.cloud.storage.StorageManagerImpl.migrateVolumes(StorageManagerImpl.java:3263)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.storage.StorageManagerImpl.migrateVolume(StorageManagerImpl.java:3209)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd.execute(MigrateVolumeCmd.java:95)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:162)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-39:job-577) Complete
async job-577, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error
text: Failed to copy the volume from the source primary storage pool to
secondary storage.
---
Thanks,
Yitao(依涛 姜)
jiangyt.github.io
Re: Integration Tests on TravisCI
Hi Hugo, Just to be clear this was just an investigation to see if people were interested. Travis will give all forks of Cloudstack CI for free which is why it was interesting. Just cause its enabled/there doesn't mean it has to be used but it does give us another option should we wish to explore it. I made a commit to master this morning that would enable build jobs to execute over there (all notification emails are disabled): https://travis-ci.org/apache/cloudstack/builds/34096969 The test results are mimicking that of jenkins, we get a failure on test_09_expunge_vm. On 1 September 2014 14:41, Hugo Trippaers h...@trippaers.nl wrote: Sorry for the late reply, was away for some time.. On 21 aug. 2014, at 19:40, Edison Su edison...@citrix.com wrote: -Original Message- From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers Sent: Thursday, August 21, 2014 5:10 AM To: dev@cloudstack.apache.org Subject: Re: Integration Tests on TravisCI Hey guys, Just to make sure we are all on the same page on this. There are several initiatives to bolster our CI capabilities and some of them are overlapping. * There are ongoing discussion to push for a CI environment at the ASF * There are a number of companies donating hardware/cloud instances to beef up jenkins.buildacloud.org Sorry for my ignorance, I don't know the situation yet. Can't wait for it to happen. Jenkins.buildacloud.org is already being supported by multiple companies and individuals, like Citrix, Schuberg Philis and the company Erik Weber is working for. David donated some space in his own private cloud as well. So we have quite decent resources already. We just need some more specialized equipment like F5, netscaler etc. * Edison is doing CI builds on Amazon i believe * There is this TravisCI initiative While they are all very good, overlapping effort means we are wasting somebodies time somewhere. With a delicate a subject as CI we should try to avoid that i think. I'll happily stop working on the CI stuff in jenkins.buildacloud.org for example and focus my efforts on Travis. So i just want to know where we want to put our effort. I don't think jenkins.buildacloud.org will go away. IMHO, the free TravisCI is good for simulator test, the hosted TravisCI Is expensive. Nevertheless, we need hosted CI to test against real hardware, that's jenkins.buildacloud.orgcan help. Cheers, Hugo On 21 aug. 2014, at 14:02, Ian Duffy i...@ianduffy.ie wrote: Santosh, What command/flags did you use for the above test output? On 14 August 2014 17:22, Santhosh Edukulla santhosh.eduku...@citrix.com wrote: Ian, I just installed latest marvin after cloudstack build on master, and ran tests against the simulator from smoke folder, below are the results. All passed, except one, i believe that as well could be some global param or some config issue. I hope you want to install, use latest marvin and test suites from master. === TestName: test_DeployVmAntiAffinityGroup | Status : SUCCESS === === TestName: test_deployvm_firstfit | Status : SUCCESS === === TestName: test_deployvm_userconcentrated | Status : SUCCESS === === TestName: test_deployvm_userdispersing | Status : SUCCESS === === TestName: test_01_create_disk_offering | Status : SUCCESS === === TestName: test_02_create_sparse_type_disk_offering | Status : SUCCESS === === TestName: test_04_create_fat_type_disk_offering | Status : SUCCESS === === TestName: test_02_edit_disk_offering | Status : SUCCESS === === TestName: test_03_delete_disk_offering | Status : SUCCESS === === TestName: test_UpdateConfigParamWithScope | Status : SUCCESS === === TestName: test_dedicateGuestVlanRange | Status : SUCCESS === === TestName: test_01_create_iso | Status : SUCCESS === === TestName: test_02_edit_iso | Status : SUCCESS === === TestName: test_03_delete_iso | Status : SUCCESS === === TestName: test_05_iso_permissions | Status : SUCCESS === === TestName: test_nic_secondaryip_add_remove | Status : SUCCESS === === TestName: test_delete_account | Status : SUCCESS === === TestName: test_public_ip_admin_account | Status : SUCCESS === === TestName: test_public_ip_user_account | Status : SUCCESS === === TestName: test_releaseIP | Status : SUCCESS === === TestName: test_extendPhysicalNetworkVlan | Status : SUCCESS === === TestName: test_UpdateStorageOverProvisioningFactor | Status : SUCCESS === === TestName: test_createPortablePublicIPAcquire | Status : SUCCESS === === TestName: test_createPortablePublicIPRange | Status : SUCCESS === === TestName: test_01_primary_storage_nfs | Status : SUCCESS === === TestName: test_privategw_acl | Status : SUCCESS === === TestName: test_dedicatePublicIpRange | Status : SUCCESS === === TestName: test_create_pvlan_network | Status :
Re: Integration Tests on TravisCI
Hey Ian, I know, and i really like the effort. I just doubt if spending effort on two things to achieve the same goal is worthwhile. If we want to run the simulator tests on Travis thats fine, but then don’t waste time and resources on running them on the jenkins.b.o. as well. If we focus our scarce resources in one direction we can do so much more i think. That said, it is a job well done to get our stuff running on Travis. :D Cheers, Hugo On 1 sep. 2014, at 16:07, Ian Duffy i...@ianduffy.ie wrote: Hi Hugo, Just to be clear this was just an investigation to see if people were interested. Travis will give all forks of Cloudstack CI for free which is why it was interesting. Just cause its enabled/there doesn't mean it has to be used but it does give us another option should we wish to explore it. I made a commit to master this morning that would enable build jobs to execute over there (all notification emails are disabled): https://travis-ci.org/apache/cloudstack/builds/34096969 The test results are mimicking that of jenkins, we get a failure on test_09_expunge_vm. On 1 September 2014 14:41, Hugo Trippaers h...@trippaers.nl wrote: Sorry for the late reply, was away for some time.. On 21 aug. 2014, at 19:40, Edison Su edison...@citrix.com wrote: -Original Message- From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers Sent: Thursday, August 21, 2014 5:10 AM To: dev@cloudstack.apache.org Subject: Re: Integration Tests on TravisCI Hey guys, Just to make sure we are all on the same page on this. There are several initiatives to bolster our CI capabilities and some of them are overlapping. * There are ongoing discussion to push for a CI environment at the ASF * There are a number of companies donating hardware/cloud instances to beef up jenkins.buildacloud.org Sorry for my ignorance, I don't know the situation yet. Can't wait for it to happen. Jenkins.buildacloud.org is already being supported by multiple companies and individuals, like Citrix, Schuberg Philis and the company Erik Weber is working for. David donated some space in his own private cloud as well. So we have quite decent resources already. We just need some more specialized equipment like F5, netscaler etc. * Edison is doing CI builds on Amazon i believe * There is this TravisCI initiative While they are all very good, overlapping effort means we are wasting somebodies time somewhere. With a delicate a subject as CI we should try to avoid that i think. I'll happily stop working on the CI stuff in jenkins.buildacloud.org for example and focus my efforts on Travis. So i just want to know where we want to put our effort. I don't think jenkins.buildacloud.org will go away. IMHO, the free TravisCI is good for simulator test, the hosted TravisCI Is expensive. Nevertheless, we need hosted CI to test against real hardware, that's jenkins.buildacloud.orgcan help. Cheers, Hugo On 21 aug. 2014, at 14:02, Ian Duffy i...@ianduffy.ie wrote: Santosh, What command/flags did you use for the above test output? On 14 August 2014 17:22, Santhosh Edukulla santhosh.eduku...@citrix.com wrote: Ian, I just installed latest marvin after cloudstack build on master, and ran tests against the simulator from smoke folder, below are the results. All passed, except one, i believe that as well could be some global param or some config issue. I hope you want to install, use latest marvin and test suites from master. === TestName: test_DeployVmAntiAffinityGroup | Status : SUCCESS === === TestName: test_deployvm_firstfit | Status : SUCCESS === === TestName: test_deployvm_userconcentrated | Status : SUCCESS === === TestName: test_deployvm_userdispersing | Status : SUCCESS === === TestName: test_01_create_disk_offering | Status : SUCCESS === === TestName: test_02_create_sparse_type_disk_offering | Status : SUCCESS === === TestName: test_04_create_fat_type_disk_offering | Status : SUCCESS === === TestName: test_02_edit_disk_offering | Status : SUCCESS === === TestName: test_03_delete_disk_offering | Status : SUCCESS === === TestName: test_UpdateConfigParamWithScope | Status : SUCCESS === === TestName: test_dedicateGuestVlanRange | Status : SUCCESS === === TestName: test_01_create_iso | Status : SUCCESS === === TestName: test_02_edit_iso | Status : SUCCESS === === TestName: test_03_delete_iso | Status : SUCCESS === === TestName: test_05_iso_permissions | Status : SUCCESS === === TestName: test_nic_secondaryip_add_remove | Status : SUCCESS === === TestName: test_delete_account | Status : SUCCESS === === TestName: test_public_ip_admin_account | Status : SUCCESS === === TestName: test_public_ip_user_account | Status : SUCCESS === === TestName: test_releaseIP | Status : SUCCESS === === TestName: test_extendPhysicalNetworkVlan | Status : SUCCESS === ===
Re: [ACS44][DISCUSS]release 4.4.1
SO May 1st and 1st manday in september are both due to may 4th... Nice read Stephen. Now back to 4.4.x I would like to create a new release if people feel we have something to release. How is the general population of this list thinking about that? Is there still focus on the 4.4 branch? Are all major issues from the 4.4.0 release solved? thanks for any (encouraging) responds, Daan On Mon, Sep 1, 2014 at 10:33 AM, Stephen Turner stephen.tur...@citrix.com wrote: Interestingly, the reason Labour Day is on May 1 in the rest of the world is the same reason it's not in May in the US and Canada, to do with communists and anarchists commemorating a riot in Chicago. See http://en.wikipedia.org/wiki/Labor_Day http://en.wikipedia.org/wiki/Haymarket_affair -- Stephen Turner -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 01 September 2014 09:05 To: dev; Mike Tutkowski Cc: Francois Gaudreault Subject: Re: [ACS44][DISCUSS]release 4.4.1 Hey Mike, You guys are not supposed to add random red holidays to your calendars. You're the commy bashers. May 1st not enough for ya'll? On Mon, Sep 1, 2014 at 12:00 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just an FYI that it's Labor Day Weekend in the U.S., so you might not get many, if any, replies until Tuesday. On Sat, Aug 30, 2014 at 2:06 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: On 2014-08-30, 4:01 PM, Daan Hoogland wrote: H, How is the felling on list about 4.4.1? Do we have a stable enough branch 4.4 at this moment? Especially the answer on this of KVM saffy people is appreciated. I am running on 4.4.1 since a week now. I did hit couple small bugs, but no real blocker. We also try to fix the SSL offload code to work with projects. We would really really like to get this feature in 4.4.1. FG -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™* -- Daan -- Daan
Jenkins build is still unstable: simulator-singlerun #256
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Re: [ACS44][DISCUSS]release 4.4.1
On 09/01/2014 04:20 PM, Daan Hoogland wrote: SO May 1st and 1st manday in september are both due to may 4th... Nice read Stephen. Now back to 4.4.x I would like to create a new release if people feel we have something to release. How is the general population of this list thinking about that? Is there still focus on the 4.4 branch? Are all major issues from the 4.4.0 release solved? Would I say all issues? I don't know. I do know however that all issues that I encountered have been fixed in 4.4.1 Wido thanks for any (encouraging) responds, Daan On Mon, Sep 1, 2014 at 10:33 AM, Stephen Turner stephen.tur...@citrix.com wrote: Interestingly, the reason Labour Day is on May 1 in the rest of the world is the same reason it's not in May in the US and Canada, to do with communists and anarchists commemorating a riot in Chicago. See http://en.wikipedia.org/wiki/Labor_Day http://en.wikipedia.org/wiki/Haymarket_affair -- Stephen Turner -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 01 September 2014 09:05 To: dev; Mike Tutkowski Cc: Francois Gaudreault Subject: Re: [ACS44][DISCUSS]release 4.4.1 Hey Mike, You guys are not supposed to add random red holidays to your calendars. You're the commy bashers. May 1st not enough for ya'll? On Mon, Sep 1, 2014 at 12:00 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just an FYI that it's Labor Day Weekend in the U.S., so you might not get many, if any, replies until Tuesday. On Sat, Aug 30, 2014 at 2:06 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: On 2014-08-30, 4:01 PM, Daan Hoogland wrote: H, How is the felling on list about 4.4.1? Do we have a stable enough branch 4.4 at this moment? Especially the answer on this of KVM saffy people is appreciated. I am running on 4.4.1 since a week now. I did hit couple small bugs, but no real blocker. We also try to fix the SSL offload code to work with projects. We would really really like to get this feature in 4.4.1. FG -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™* -- Daan
Re: [ACS44][DISCUSS]release 4.4.1
Thanks Wido, I ask no more of you ;) On Mon, Sep 1, 2014 at 4:30 PM, Wido den Hollander w...@widodh.nl wrote: On 09/01/2014 04:20 PM, Daan Hoogland wrote: SO May 1st and 1st manday in september are both due to may 4th... Nice read Stephen. Now back to 4.4.x I would like to create a new release if people feel we have something to release. How is the general population of this list thinking about that? Is there still focus on the 4.4 branch? Are all major issues from the 4.4.0 release solved? Would I say all issues? I don't know. I do know however that all issues that I encountered have been fixed in 4.4.1 Wido thanks for any (encouraging) responds, Daan On Mon, Sep 1, 2014 at 10:33 AM, Stephen Turner stephen.tur...@citrix.com wrote: Interestingly, the reason Labour Day is on May 1 in the rest of the world is the same reason it's not in May in the US and Canada, to do with communists and anarchists commemorating a riot in Chicago. See http://en.wikipedia.org/wiki/Labor_Day http://en.wikipedia.org/wiki/Haymarket_affair -- Stephen Turner -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 01 September 2014 09:05 To: dev; Mike Tutkowski Cc: Francois Gaudreault Subject: Re: [ACS44][DISCUSS]release 4.4.1 Hey Mike, You guys are not supposed to add random red holidays to your calendars. You're the commy bashers. May 1st not enough for ya'll? On Mon, Sep 1, 2014 at 12:00 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just an FYI that it's Labor Day Weekend in the U.S., so you might not get many, if any, replies until Tuesday. On Sat, Aug 30, 2014 at 2:06 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: On 2014-08-30, 4:01 PM, Daan Hoogland wrote: H, How is the felling on list about 4.4.1? Do we have a stable enough branch 4.4 at this moment? Especially the answer on this of KVM saffy people is appreciated. I am running on 4.4.1 since a week now. I did hit couple small bugs, but no real blocker. We also try to fix the SSL offload code to work with projects. We would really really like to get this feature in 4.4.1. FG -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™* -- Daan -- Daan
Re: [ACS44][DISCUSS]release 4.4.1
Daan, We are working on fixing SSL offload for projects. Any chance we can slide that in 4.4.1 or should we target 4.5? Assuming we have the code working later this week... FG On 2014-09-01, 10:30 AM, Wido den Hollander wrote: On 09/01/2014 04:20 PM, Daan Hoogland wrote: SO May 1st and 1st manday in september are both due to may 4th... Nice read Stephen. Now back to 4.4.x I would like to create a new release if people feel we have something to release. How is the general population of this list thinking about that? Is there still focus on the 4.4 branch? Are all major issues from the 4.4.0 release solved? Would I say all issues? I don't know. I do know however that all issues that I encountered have been fixed in 4.4.1 Wido thanks for any (encouraging) responds, Daan On Mon, Sep 1, 2014 at 10:33 AM, Stephen Turner stephen.tur...@citrix.com wrote: Interestingly, the reason Labour Day is on May 1 in the rest of the world is the same reason it's not in May in the US and Canada, to do with communists and anarchists commemorating a riot in Chicago. See http://en.wikipedia.org/wiki/Labor_Day http://en.wikipedia.org/wiki/Haymarket_affair -- Stephen Turner -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 01 September 2014 09:05 To: dev; Mike Tutkowski Cc: Francois Gaudreault Subject: Re: [ACS44][DISCUSS]release 4.4.1 Hey Mike, You guys are not supposed to add random red holidays to your calendars. You're the commy bashers. May 1st not enough for ya'll? On Mon, Sep 1, 2014 at 12:00 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just an FYI that it's Labor Day Weekend in the U.S., so you might not get many, if any, replies until Tuesday. On Sat, Aug 30, 2014 at 2:06 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: On 2014-08-30, 4:01 PM, Daan Hoogland wrote: H, How is the felling on list about 4.4.1? Do we have a stable enough branch 4.4 at this moment? Especially the answer on this of KVM saffy people is appreciated. I am running on 4.4.1 since a week now. I did hit couple small bugs, but no real blocker. We also try to fix the SSL offload code to work with projects. We would really really like to get this feature in 4.4.1. FG -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™* -- Daan -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_
Re: [ACS44][DISCUSS]release 4.4.1
I will start some basic testing myself and have some unrelated $dayjob so an ATA of end of workweek is fine by me. Daan On Mon, Sep 1, 2014 at 4:39 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: Daan, We are working on fixing SSL offload for projects. Any chance we can slide that in 4.4.1 or should we target 4.5? Assuming we have the code working later this week... FG On 2014-09-01, 10:30 AM, Wido den Hollander wrote: On 09/01/2014 04:20 PM, Daan Hoogland wrote: SO May 1st and 1st manday in september are both due to may 4th... Nice read Stephen. Now back to 4.4.x I would like to create a new release if people feel we have something to release. How is the general population of this list thinking about that? Is there still focus on the 4.4 branch? Are all major issues from the 4.4.0 release solved? Would I say all issues? I don't know. I do know however that all issues that I encountered have been fixed in 4.4.1 Wido thanks for any (encouraging) responds, Daan On Mon, Sep 1, 2014 at 10:33 AM, Stephen Turner stephen.tur...@citrix.com wrote: Interestingly, the reason Labour Day is on May 1 in the rest of the world is the same reason it's not in May in the US and Canada, to do with communists and anarchists commemorating a riot in Chicago. See http://en.wikipedia.org/wiki/Labor_Day http://en.wikipedia.org/wiki/Haymarket_affair -- Stephen Turner -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 01 September 2014 09:05 To: dev; Mike Tutkowski Cc: Francois Gaudreault Subject: Re: [ACS44][DISCUSS]release 4.4.1 Hey Mike, You guys are not supposed to add random red holidays to your calendars. You're the commy bashers. May 1st not enough for ya'll? On Mon, Sep 1, 2014 at 12:00 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just an FYI that it's Labor Day Weekend in the U.S., so you might not get many, if any, replies until Tuesday. On Sat, Aug 30, 2014 at 2:06 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: On 2014-08-30, 4:01 PM, Daan Hoogland wrote: H, How is the felling on list about 4.4.1? Do we have a stable enough branch 4.4 at this moment? Especially the answer on this of KVM saffy people is appreciated. I am running on 4.4.1 since a week now. I did hit couple small bugs, but no real blocker. We also try to fix the SSL offload code to work with projects. We would really really like to get this feature in 4.4.1. FG -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™* -- Daan -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- Daan
old branches
By my possibly slightly incorrect count we now have 158 branches in our repo. Those include master and old release branches but also a lot of obsolete ones. Should we clean? (+1 implied) Should an RM be responsible of fix branches? (I feel I am, so don't hesitate to say yes on that one) Should those responsible for a merge be made responsible for deleting the merged branch? (+1 implied) -- Daan
RE: jsonObj is not defined. UI development problem.
Hi Ilia,
I looked into this and although I did not try to make the changes myself, it
turned out that the error you are getting is already there on the ACL rules tab.
I raised a Jira ticket for investigation. It seems to me that your solution
should work as is, once the issue with data: args.jsonObj.tags is fixed.
I have not taken further steps but you are more than welcome to investigate
this :)
I have filed the following bug for now:
https://issues.apache.org/jira/browse/CLOUDSTACK-7462
Cheers,
Gabor
-Original Message-
From: Ilia Shakitko [mailto:i.shaki...@tech.leaseweb.com]
Sent: 01 September 2014 13:52
To: dev@cloudstack.apache.org
Subject: RE: jsonObj is not defined. UI development problem.
Can somebody help me in that? I’ve tried to contact Jessica Wang (main changer
in that ui part, but haven’t got an answer yet)
Kind regards,
Ilia Shakitko
Innovation Engineer
LeaseWeb Technologies B.V.
T: +31 20 316 0235
E: i.shaki...@tech.leaseweb.com
W: www.leaseweb.comhttp://www.leaseweb.com
Luttenbergweg 8, 1101 EC Amsterdam, The Netherlands
From: Ilia Shakitko
Sent: woensdag, 27 augustus, 2014 11:54
To: dev@cloudstack.apache.org
Subject: jsonObj is not defined. UI development problem.
I am working on some ui changes in cloudstack. And I am adding some lines (to
display tags for SecurityGroupRules) in network.js: line #4670 (before actions:
{ destroy: { … on line #4814):
tags: cloudStack.api.tags({
resourceType: 'SecurityGroupRule',
contextId: 'multiRule'
}),
I made it 1 to 1 with FirewallRule. But it doesn’t work. I spend quite a lot of
time on trying to figure out why. It renders the window, but without anything:
http://clip2net.com/s/iO0mAh (http://clip2net.com/s/iO0mWk) So as I understood
debugging the code, it runs in issues in sharedFunctions.js file when it tries
to read “jsonObj” but it’s empty (http://clip2net.com/s/iO0lwy). I couldn’t
figure out why is it empty and where do I fill it with data from “context”…
Could you help me with correct direction? What am I missing? ☺
Kind regards,
Ilia Shakitko
Innovation Engineer
LeaseWeb Technologies B.V.
T: +31 20 316 0235
E: i.shaki...@tech.leaseweb.commailto:i.shaki...@tech.leaseweb.com
W: www.leaseweb.comhttp://www.leaseweb.com
Luttenbergweg 8, 1101 EC Amsterdam, The Netherlands
Re: [ACS44][DISCUSS]release 4.4.1
:) Well, the government doesn't mandate the holiday (unless you work for the government, it's up to your company to honor the holiday or not). For example, I fully expect Starbucks to be open when I drive over there today. On Mon, Sep 1, 2014 at 2:04 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: Hey Mike, You guys are not supposed to add random red holidays to your calendars. You're the commy bashers. May 1st not enough for ya'll? On Mon, Sep 1, 2014 at 12:00 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just an FYI that it's Labor Day Weekend in the U.S., so you might not get many, if any, replies until Tuesday. On Sat, Aug 30, 2014 at 2:06 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: On 2014-08-30, 4:01 PM, Daan Hoogland wrote: H, How is the felling on list about 4.4.1? Do we have a stable enough branch 4.4 at this moment? Especially the answer on this of KVM saffy people is appreciated. I am running on 4.4.1 since a week now. I did hit couple small bugs, but no real blocker. We also try to fix the SSL offload code to work with projects. We would really really like to get this feature in 4.4.1. FG -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™* -- Daan -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™*
Re: Unable to start a VM due to insufficient capacity
You may want to review entire flow for job-27, which is related to this deployment failure. There are multiple possibilities for this insufficient capacity error. Sent from my iPhone On 1 Sep 2014, at 6:49 pm, Giri Prasad g_p...@yahoo.com.INVALID wrote: Hello, I have installed cs 4.3 on Ubuntu 14.04 LTS. Created the usual infra, registered a couple of ISO's, and tried to created a instance using the ISO, via the gui. Comes out with some error. Any ideas on how to fix this? Thanks Regards, Giri 2014-09-01 17:21:26,551 DEBUG [c.c.a.ApiServlet] (catalina-exec-6:ctx-703486f7 ctx-ee65bd67) ===END=== XXX.XXX.XXX.5 -- GET command=queryAsyncJobResultjobId=1b7d53c6-256a-4721-b69c-d68c1f6d7d42response=jsonsessionkey=e6F89zbOUS4dR2%2FmrkznQBxeQ%2BM%3D_=1409572286355 2014-09-01 17:21:26,733 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-6:ctx-d1e72afb) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to insufficient capacity at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:605) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy169.startVirtualMachine(Unknown Source) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|ubuntu-12-04-64bit-admin-Instance]Scope=interface
Review Request 25235: vGPU service offering upgrade test automation
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25235/ --- Review request for cloudstack, Doug Clark, John Dilley, and Sanjay Tripathi. Repository: cloudstack-git Description --- vGPU service offering upgrade test automation Diffs - test/integration/component/test_deploy_vgpu_vm.py 534a7e3 Diff: https://reviews.apache.org/r/25235/diff/ Testing --- Yes. All the testcases are passed with XenServer. Thanks, sailaja mada
Jenkins build is still unstable: simulator-singlerun #257
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
ShapeBlue Webinar: Apache CloudStack Demo - in portuguese
Hello community, please, propagate this webinar! ShapeBlue Brazil will promote an Apache CloudStack Demo in September 16, 2014 5:00 PM - 6:00 PM BRT. See a demonstration of ShapeBlue about that the Apache CloudStack provides an integrated software solution for delivering a true cloud IaaS - delivering all essential components used to build, deploy and manage multi-tier applications and multi-tenant resources allowing delivery and provision of service compute, network and storage. Follow the link to registry: https://attendee.gotowebinar.com/register/6894968509404786433 Best regards, Marco Sinhoreli Consultant Manager Phone: +55 21 2586 6390 | Fax: +55 21 2586 6002 | Mobile: +55 21 98276 3636 | Mobile: +55 21 99711 4645 Praia de Botafogo 501, bloco 1 - sala 101, Botafogo, Rio de Janeiro, RJ - Brazil - CEP 22250-040 marco.sinhor...@shapeblue.commailto:marco.sinhor...@shapeblue.com | www.shapeblue.comhttp://www.shapeblue.com/ | Twitter:@shapeBluehttps://twitter.com/#!/shapeblue Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge - rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack Infrastructure Supporthttp://shapeblue.com/cloudstack-infrastructure-support/ CloudStack Bootcamp Training Courseshttp://shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Jenkins build is still unstable: simulator-singlerun #258
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Re: [ACS44][DISCUSS]release 4.4.1
Thanks, Daan. In terms of timing for a media announcement, early in the week is best. If you're ready to go on Monday 8th September, I can definitely work around that. Just let me know how you're progressing and when you have in mind in terms of getting the word out. On standby, Sally From: Daan Hoogland daan.hoogl...@gmail.com To: dev dev@cloudstack.apache.org; Francois Gaudreault fgaudrea...@cloudops.com Cc: Sally Khudairi s...@apache.org Sent: Monday, 1 September 2014, 10:42 Subject: Re: [ACS44][DISCUSS]release 4.4.1 I will start some basic testing myself and have some unrelated $dayjob so an ATA of end of workweek is fine by me. Daan On Mon, Sep 1, 2014 at 4:39 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: Daan, We are working on fixing SSL offload for projects. Any chance we can slide that in 4.4.1 or should we target 4.5? Assuming we have the code working later this week... FG On 2014-09-01, 10:30 AM, Wido den Hollander wrote: On 09/01/2014 04:20 PM, Daan Hoogland wrote: SO May 1st and 1st manday in september are both due to may 4th... Nice read Stephen. Now back to 4.4.x I would like to create a new release if people feel we have something to release. How is the general population of this list thinking about that? Is there still focus on the 4.4 branch? Are all major issues from the 4.4.0 release solved? Would I say all issues? I don't know. I do know however that all issues that I encountered have been fixed in 4.4.1 Wido thanks for any (encouraging) responds, Daan On Mon, Sep 1, 2014 at 10:33 AM, Stephen Turner stephen.tur...@citrix.com wrote: Interestingly, the reason Labour Day is on May 1 in the rest of the world is the same reason it's not in May in the US and Canada, to do with communists and anarchists commemorating a riot in Chicago. See http://en.wikipedia.org/wiki/Labor_Day http://en.wikipedia.org/wiki/Haymarket_affair -- Stephen Turner -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 01 September 2014 09:05 To: dev; Mike Tutkowski Cc: Francois Gaudreault Subject: Re: [ACS44][DISCUSS]release 4.4.1 Hey Mike, You guys are not supposed to add random red holidays to your calendars. You're the commy bashers. May 1st not enough for ya'll? On Mon, Sep 1, 2014 at 12:00 AM, Mike Tutkowski mike.tutkow...@solidfire.com wrote: Just an FYI that it's Labor Day Weekend in the U.S., so you might not get many, if any, replies until Tuesday. On Sat, Aug 30, 2014 at 2:06 PM, Francois Gaudreault fgaudrea...@cloudops.com wrote: On 2014-08-30, 4:01 PM, Daan Hoogland wrote: H, How is the felling on list about 4.4.1? Do we have a stable enough branch 4.4 at this moment? Especially the answer on this of KVM saffy people is appreciated. I am running on 4.4.1 since a week now. I did hit couple small bugs, but no real blocker. We also try to fix the SSL offload code to work with projects. We would really really like to get this feature in 4.4.1. FG -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud http://solidfire.com/solution/overview/?video=play*™* -- Daan -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Experts 420 rue Guy | Montreal | Quebec | H3J 1S6 w: cloudops.com | tw: @CloudOps_ -- Daan
Build failed in Jenkins: simulator-singlerun #259
See http://jenkins.buildacloud.org/job/simulator-singlerun/259/changes Changes: [Rohit Yadav] server: Add event bus bean as commented xml in META-INF core -- [...truncated 8862 lines...] [INFO] Installing http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 23.134s [INFO] Finished at: Mon Sep 01 16:02:31 EDT 2014 [INFO] Final Memory: 43M/190M [INFO] [simulator-singlerun] $ /bin/bash -x /tmp/hudson7337635692017744369.sh + jps -l + grep -q Launcher + rm -f xunit.xml + rm -rf /tmp/MarvinLogs + echo Check for initialization of the management server Check for initialization of the management server + COUNTER=0 + SERVER_PID=17961 + mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run + '[' 0 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=1 + '[' 1 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=2 + '[' 2 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=3 + '[' 3 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=4 + '[' 4 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=5 + '[' 5 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=6 + '[' 6 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=7 + '[' 7 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=8 + '[' 8 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=9 + '[' 9 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=10 + '[' 10 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=11 + '[' 11 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=12 + '[' 12 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=13 + '[' 13 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=14 + '[' 14 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=15 + '[' 15 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=16 + '[' 16 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=17 + '[' 17 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=18 + '[' 18 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=19 + '[' 19 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=20 + '[' 20 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=21 + '[' 21 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=22 + '[' 22 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=23 + '[' 23 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=24 + '[' 24 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=25 + '[' 25 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=26 + '[' 26 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=27 + '[' 27 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=28 + '[' 28 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=29 + '[' 29 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=30 + '[' 30 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=31 + '[' 31 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=32 + '[' 32 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=33 + '[' 33 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=34 + '[' 34 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out
Build failed in Jenkins: simulator-singlerun #260
See http://jenkins.buildacloud.org/job/simulator-singlerun/260/ -- [...truncated 8864 lines...] [INFO] Installing http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.5.0-SNAPSHOT/cloud-developer-4.5.0-SNAPSHOT.pom [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 27.253s [INFO] Finished at: Mon Sep 01 16:25:15 EDT 2014 [INFO] Final Memory: 40M/180M [INFO] [simulator-singlerun] $ /bin/bash -x /tmp/hudson7367620576929748776.sh + jps -l + grep -q Launcher + rm -f xunit.xml + rm -rf /tmp/MarvinLogs + echo Check for initialization of the management server Check for initialization of the management server + COUNTER=0 + SERVER_PID=24472 + mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run + '[' 0 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=1 + '[' 1 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=2 + '[' 2 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=3 + '[' 3 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=4 + '[' 4 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=5 + '[' 5 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=6 + '[' 6 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=7 + '[' 7 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=8 + '[' 8 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=9 + '[' 9 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=10 + '[' 10 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=11 + '[' 11 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=12 + '[' 12 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=13 + '[' 13 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=14 + '[' 14 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=15 + '[' 15 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=16 + '[' 16 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=17 + '[' 17 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=18 + '[' 18 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=19 + '[' 19 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=20 + '[' 20 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=21 + '[' 21 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=22 + '[' 22 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=23 + '[' 23 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=24 + '[' 24 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=25 + '[' 25 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=26 + '[' 26 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=27 + '[' 27 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=28 + '[' 28 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=29 + '[' 29 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=30 + '[' 30 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=31 + '[' 31 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=32 + '[' 32 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=33 + '[' 33 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=34 + '[' 34 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=35 + '[' 35 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is
[GitHub] cloudstack pull request: IGNORE: Testing that travis-ci runs on pu...
GitHub user imduffy15 opened a pull request: https://github.com/apache/cloudstack/pull/13 IGNORE: Testing that travis-ci runs on pull requests and reports a status. Remove a failing test form .travis.yml. This commit should be ignored. I am doing this as a pull request to see if the travis-ci status appears on github. You can merge this pull request into a Git repository by running: $ git pull https://github.com/imduffy15/cloudstack master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/13.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #13 commit 04945364efa7aeb19e87bf171ef1134bc90033e3 Author: Ian Duffy i...@ianduffy.ie Date: 2014-09-01T23:39:52Z Remove a test from .travis.yml Remove a failing test form .travis.yml. This commit should be ignored. I am doing this as a pull request to see if the travis-ci status appears on github. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Integration Tests on TravisCI
Just for anybody interest. They are working to give a result on a pull request on github before merging. Example: https://github.com/apache/cloudstack/pull/13 On 1 September 2014 15:13, Hugo Trippaers h...@trippaers.nl wrote: Hey Ian, I know, and i really like the effort. I just doubt if spending effort on two things to achieve the same goal is worthwhile. If we want to run the simulator tests on Travis thats fine, but then don’t waste time and resources on running them on the jenkins.b.o. as well. If we focus our scarce resources in one direction we can do so much more i think. That said, it is a job well done to get our stuff running on Travis. :D Cheers, Hugo On 1 sep. 2014, at 16:07, Ian Duffy i...@ianduffy.ie wrote: Hi Hugo, Just to be clear this was just an investigation to see if people were interested. Travis will give all forks of Cloudstack CI for free which is why it was interesting. Just cause its enabled/there doesn't mean it has to be used but it does give us another option should we wish to explore it. I made a commit to master this morning that would enable build jobs to execute over there (all notification emails are disabled): https://travis-ci.org/apache/cloudstack/builds/34096969 The test results are mimicking that of jenkins, we get a failure on test_09_expunge_vm. On 1 September 2014 14:41, Hugo Trippaers h...@trippaers.nl wrote: Sorry for the late reply, was away for some time.. On 21 aug. 2014, at 19:40, Edison Su edison...@citrix.com wrote: -Original Message- From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers Sent: Thursday, August 21, 2014 5:10 AM To: dev@cloudstack.apache.org Subject: Re: Integration Tests on TravisCI Hey guys, Just to make sure we are all on the same page on this. There are several initiatives to bolster our CI capabilities and some of them are overlapping. * There are ongoing discussion to push for a CI environment at the ASF * There are a number of companies donating hardware/cloud instances to beef up jenkins.buildacloud.org Sorry for my ignorance, I don't know the situation yet. Can't wait for it to happen. Jenkins.buildacloud.org is already being supported by multiple companies and individuals, like Citrix, Schuberg Philis and the company Erik Weber is working for. David donated some space in his own private cloud as well. So we have quite decent resources already. We just need some more specialized equipment like F5, netscaler etc. * Edison is doing CI builds on Amazon i believe * There is this TravisCI initiative While they are all very good, overlapping effort means we are wasting somebodies time somewhere. With a delicate a subject as CI we should try to avoid that i think. I'll happily stop working on the CI stuff in jenkins.buildacloud.org for example and focus my efforts on Travis. So i just want to know where we want to put our effort. I don't think jenkins.buildacloud.org will go away. IMHO, the free TravisCI is good for simulator test, the hosted TravisCI Is expensive. Nevertheless, we need hosted CI to test against real hardware, that's jenkins.buildacloud.orgcan help. Cheers, Hugo On 21 aug. 2014, at 14:02, Ian Duffy i...@ianduffy.ie wrote: Santosh, What command/flags did you use for the above test output? On 14 August 2014 17:22, Santhosh Edukulla santhosh.eduku...@citrix.com wrote: Ian, I just installed latest marvin after cloudstack build on master, and ran tests against the simulator from smoke folder, below are the results. All passed, except one, i believe that as well could be some global param or some config issue. I hope you want to install, use latest marvin and test suites from master. === TestName: test_DeployVmAntiAffinityGroup | Status : SUCCESS === === TestName: test_deployvm_firstfit | Status : SUCCESS === === TestName: test_deployvm_userconcentrated | Status : SUCCESS === === TestName: test_deployvm_userdispersing | Status : SUCCESS === === TestName: test_01_create_disk_offering | Status : SUCCESS === === TestName: test_02_create_sparse_type_disk_offering | Status : SUCCESS === === TestName: test_04_create_fat_type_disk_offering | Status : SUCCESS === === TestName: test_02_edit_disk_offering | Status : SUCCESS === === TestName: test_03_delete_disk_offering | Status : SUCCESS === === TestName: test_UpdateConfigParamWithScope | Status : SUCCESS === === TestName: test_dedicateGuestVlanRange | Status : SUCCESS === === TestName: test_01_create_iso | Status : SUCCESS === === TestName: test_02_edit_iso | Status : SUCCESS === === TestName: test_03_delete_iso | Status : SUCCESS === === TestName: test_05_iso_permissions | Status : SUCCESS === === TestName: test_nic_secondaryip_add_remove | Status : SUCCESS === ===
Re: Review Request 25228: hitting java.lang.reflect.InvocationTargetException while starting usage server
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25228/ --- (Updated Sept. 2, 2014, 4:08 a.m.) Review request for cloudstack, Kishan Kavala and Rayees Namathponnan. Changes --- Added kishan to the list Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-7316 https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-7316 Repository: cloudstack-git Description --- Usage server is failing to start when we install Usage server on the management server with DB encryption enabled. Usage is server is unable to get key file from the classpath. Diffs - packaging/centos63/cloud.spec 790f57b Diff: https://reviews.apache.org/r/25228/diff/ Testing --- Tested on centos 6.3 and rhel 7 Thanks, Damodar Reddy Talakanti
Re: Unable to start a VM due to insufficient capacity
Thanks. The error occurs at line 20400th line in the management server log. Please let me know, where I can upload these 20400 lines (or a few 1000 lines before the error message) from the log. Btw, I have a cs 4.1 on ubuntu 12.04 LTS, which is on a different hdd partition, on the same hardware, working without any problem. Regards, From: Erik Weber terbol...@gmail.com To: dev dev@cloudstack.apache.org; Giri Prasad g_p...@yahoo.com Sent: Monday, 1 September 2014 7:01 PM Subject: Re: Unable to start a VM due to insufficient capacity Give us more of the logs. Preferably everything from the moment you press launch until the exception occurs. -- Erik On Mon, Sep 1, 2014 at 3:18 PM, Giri Prasad g_p...@yahoo.com.invalid wrote: Hello, I have installed cs 4.3 on Ubuntu 14.04 LTS. Created the usual infra, registered a couple of ISO's, and tried to created a instance using the ISO, via the gui. Comes out with some error. Any ideas on how to fix this? Thanks Regards, Giri 2014-09-01 17:21:26,551 DEBUG [c.c.a.ApiServlet] (catalina-exec-6:ctx-703486f7 ctx-ee65bd67) ===END=== XXX.XXX.XXX.5 -- GET command=queryAsyncJobResultjobId=1b7d53c6-256a-4721-b69c-d68c1f6d7d42response=jsonsessionkey=e6F89zbOUS4dR2%2FmrkznQBxeQ%2BM%3D_=1409572286355 2014-09-01 17:21:26,733 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-6:ctx-d1e72afb) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.DeployVMCmd com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due to insufficient capacity at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:605) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3161) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3147) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy169.startVirtualMachine(Unknown Source) at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:443) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:509) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at
