Re: Review Request 15932: Add support for Primary Storage on Gluster using the libvirt backend
On Feb. 19, 2014, 1:35 p.m., Wido den Hollander wrote: It seems good to me. Applies cleanly to master and builds just fine. Code-wise it's simple but effective, should allow us to support Gluster. Wido den Hollander wrote: I just merged it into master and pushed. So gluster is in master right now! Niels, can I ask you to test it all again? Just to make sure the code all works like you intended. Niels de Vos wrote: Thanks Wido! This seems to be working OK for me. Note that the UI modification (https://reviews.apache.org/r/15933/) have not been reviewed/merged yet. Without these, it's rather difficult for users to configure Primary Storage on Gluster. Also, I've got asked about the dependencies and configuration. I'll add that here for now, and I'll try figure out how to get it added to the documentation: In /etc/glusterfs/glusterd.vol, allow unprivileged ports to contact the 'management' volume to get the volume configuration: option rpc-auth-allow-insecure on After changing the glusterd.vol file, restart the glusterd service to apply the changes. Per volume, allow unprivileged ports to access the brick processes (glusterfsd): # gluster volume set volname server.allow-insecure on # gluster volume stop volume # gluster volume start volume Per volume make sure that the kvm user (uid=36) and kvm group (gid=36) can access the images on the volume: # gluster volume set volname storage.owner-uid 36 # gluster volume set volname storage.owner-gid 36 Other dependencies: * libvirt version 1.0.1 (gluster protocol/network disk support) * qemu version 1.3 (gluster block backend support) Note that RHEL-6.5 and derived distributions contain backports that add sufficient functionality too. Niels de Vos wrote: Some further testing showed that there can be some issues with starting virtual machines which have disks on Gluster. https://reviews.apache.org/r/18412/ contains a solution for that. Wido, could you check that this is in 4.4, 4.5 and master and if not commit it ? trying to clean review board a bit. thanks - Sebastien --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15932/#review34859 --- On Feb. 19, 2014, 8:24 a.m., Niels de Vos wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/15932/ --- (Updated Feb. 19, 2014, 8:24 a.m.) Review request for cloudstack. Repository: cloudstack-git Description --- The support for Gluster as Primary Storage is mostly based on the implementation for NFS. Like NFS, libvirt can address a Gluster environment through the 'netfs' pool-type. Diffs - api/src/com/cloud/storage/Storage.java ff83dfc plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java d63b643 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtStoragePoolDef.java dbe5d4b plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtStoragePoolXMLParser.java a6186f6 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java ff75d61 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java 8cdecd8 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/LibvirtStorageAdaptor.java a5f33eb plugins/storage/volume/default/src/org/apache/cloudstack/storage/datastore/lifecycle/CloudStackPrimaryDataStoreLifeCycleImpl.java b90d5fc Diff: https://reviews.apache.org/r/15932/diff/ Testing --- See http://blog.nixpanic.net/2013/12/using-gluster-as-primary-storage-in.html Thanks, Niels de Vos
Re: Review Request 18412: Gluster should store disk images in qcow2 format
On Feb. 25, 2014, 10:21 a.m., Wido den Hollander wrote: Ship It! This is present in 4.4, 4.5 and master - Sebastien --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/18412/#review35381 --- On Feb. 23, 2014, 7:20 p.m., Niels de Vos wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/18412/ --- (Updated Feb. 23, 2014, 7:20 p.m.) Review request for cloudstack and Wido den Hollander. Repository: cloudstack-git Description --- By default all network disks are in RAW format. Gluster works fine with QCOW2 which has some advantages. Disks are by default in QCOW2 format. It is possible to run into a mismatch, where the disk is in QCOW2 format, but QEMU gets started with format=raw. This causes the virtual machines to lockup on boot. Failures to start a virtual machine can be verified by checking the log of the virtual machine, and compare the output of 'qemu-img info'. In /var/log/libvirt/qemu/VM.log find the URL for the drive: -drive file=gluster+tcp://...,format=raw,.. Compare this with the 'qemu-img info' output of the same file, mounted under /mnt/pool-uuid/img-uuid: # qemu-img info /mnt/pool-uuid/img-uuid ... file format: qcow2 ... This change makes passes the format when creating a disk located on RBD (RAW only) and Gluster (QCOW2). Diffs - plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java c986855 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtDomainXMLParser.java 9cf6a90 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVMDef.java 290c5a9 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java 1c37607 Diff: https://reviews.apache.org/r/18412/diff/ Testing --- Test results described with this setup: http://blog.nixpanic.net/2014_02_23_archive.html Thanks, Niels de Vos
Review Request 28523: CLOUDSTACK-7991: test_security_groups.py - Move config data to test_data.py and fix pep8 issues
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28523/ --- Review request for cloudstack and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7991 https://issues.apache.org/jira/browse/CLOUDSTACK-7991 Repository: cloudstack-git Description --- Moving the config data in the test case to test_data.py Keeping host credentails in configurableData section. Fixing pep8 issues. Diffs - test/integration/component/test_security_groups.py eb242c7 tools/marvin/marvin/config/test_data.py f0802a5 Diff: https://reviews.apache.org/r/28523/diff/ Testing --- Yes. Two test cases failing for different reason. Log: Test authorize ingress rule ... === TestName: test_01_authorizeIngressRule | Status : SUCCESS === ok Test deploy VM in default security group ... === TestName: test_01_deployVM_InDefaultSecurityGroup | Status : SUCCESS === ok Test list security groups for admin account ... === TestName: test_02_listSecurityGroups | Status : SUCCESS === ok Test access in default security group ... === TestName: test_03_accessInDefaultSecurityGroup | Status : SUCCESS === ok Test delete security group with running VM ... === TestName: test_01_delete_security_grp_running_vm | Status : SUCCESS === ok Test delete security group without running VM ... === TestName: test_02_delete_security_grp_withoout_running_vm | Status : SUCCESS === ok Test router services for user account ... === TestName: test_01_dhcpOnlyRouter | Status : SUCCESS === ok Test delete security group with running VM ... === TestName: test_01_authorizeIngressRule_AfterDeployVM | Status : SUCCESS === ok Test Revoke ingress rule after deploy VM ... === TestName: test_02_revokeIngressRule_AfterDeployVM | Status : FAILED === FAIL Test Start/Stop VM and Verify ingress rule ... === TestName: test_03_stopStartVM_verifyIngressAccess | Status : SUCCESS === ok Test revoke ingress rule ... === TestName: test_01_revokeIngressRule | Status : FAILED === FAIL Test Deploy VM with User data ... === TestName: test_01_deployVMWithUserData | Status : SUCCESS === ok Thanks, Gaurav Aradhye
Re: A secure way to reset VMs password
On Thu, Nov 27, 2014 at 3:54 PM, Alireza Eskandari astro.alir...@yahoo.com.invalid wrote: HiI viewed the bash script that resets Linux password ( http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in)It seems that it doesn't use a secure way for transferring password string to instance.Instances on a shared network can sniff password requests and export requested password of other instances.I suggest to use SSL (https) instead of plan text.Regards I like the idea, but there's a couple of obstacles to overcome, namely which SSL certificates to use. - certificates need a subject name, ie. IP or hostname for web pages, you could solve this by making the mgmt server a CA and have each VR get a signed certificate by it, but it's complicated - if the community bundle a pre generated certificate it is commonly known and not to be trusted, also not sure how to handle subject name - assuming everyone to supply a valid certificate is quite complicated (CA must be on VR etc), and makes it considerably harder to get a working setup - using self signed causes issues with validation Don't get me wrong, I love the idea, but it's not just to flip a switch and have (proper) SSL in place. -- Erik
review board cleanup
Hi folks, I pinged a few of you to try to get cleanup review board. there is 120 open reviews there. Since github is working nicely and folks are starting to migrate to this, it's time to clean up RB. A lot of reviews have actually been dealt with but not closed. So if you don't know what to do in the coming days, spending 30 minutes on review board and closing/updating a few reviews would be great. Cheers, -Sebastien
Re: review board cleanup
Is there a way to 'force' close a review if its already submitted? ~Rajani On Fri, Nov 28, 2014 at 2:34 PM, sebgoa run...@gmail.com wrote: Hi folks, I pinged a few of you to try to get cleanup review board. there is 120 open reviews there. Since github is working nicely and folks are starting to migrate to this, it's time to clean up RB. A lot of reviews have actually been dealt with but not closed. So if you don't know what to do in the coming days, spending 30 minutes on review board and closing/updating a few reviews would be great. Cheers, -Sebastien
Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)
merci, mon ami On Fri, Nov 28, 2014 at 2:48 AM, Pierre-Luc Dion pd...@cloudops.com wrote: sorry for the late response, I've tested following upgrade: 4.4.0 - 4.4.1 - 4.4.2 4.4.0 - 4.4.2 so far all work fine, but from frest 4.4.0 , manual alter table in MySQL is require. I'll update the Release Notes... PL On Wed, Nov 26, 2014 at 12:42 PM, Nux! n...@li.nux.ro wrote: What is your setup and zone type? Some logs might help, too. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Pierre-Luc Dion pd...@cloudops.com To: dev@cloudstack.apache.org Sent: Wednesday, 26 November, 2014 17:20:24 Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2) ok, then, I will test 4.4.0 - 4.4.1 - 4.4.2.while doing 4.4.0 to 4.4.2 I've endup behing unable to create network because the systemvm template was not mark as ready, although, ssvm and cpvm as been upgraded to 4.4.1 system-vm template without issue. also still need the manual mysql query... On Wed, Nov 26, 2014 at 12:14 PM, Nux! n...@li.nux.ro wrote: I tried from 4.4.1; what problems are you seeing? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Pierre-Luc Dion pd...@cloudops.com To: dev@cloudstack.apache.org Sent: Wednesday, 26 November, 2014 17:11:10 Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2) Did anyone try an upgrade from a fresh 4.4.0 to 4.4.2? so far I did not had too much success but before do a negative vote I want to make sure my test env, is ok. thanks, PL On Wed, Nov 26, 2014 at 3:46 AM, Nux! n...@li.nux.ro wrote: Pierre, In my case it did not, everything worked well, but do note I manually patched the sysvm tmpl for CLOUDSTACK-7781. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Pierre-Luc Dion pdion...@apache.org To: dev@cloudstack.apache.org Sent: Tuesday, 25 November, 2014 23:43:41 Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2) Does 4.4.2 require new set of systemvm compare to 4.4.1 ? On Tue, Nov 25, 2014 at 11:15 AM, Tomasz Zięba t.a.zi...@gmail.com wrote: +1 for: http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-package-rpm/ -- build 317 http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/ -- build 171 Regards Tom 2014-11-21 3:59 GMT+01:00 Daan Hoogland daan.hoogl...@gmail.com : Hi All, I've created a 4.4.2 release, with the following artifacts up for a vote: Git Branch and Commit SH: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.4 Commit: e0420a6fec738d728bc59ba65bc5e12809bde0eb List of changes: `CLOUDSTACK-7887 https://issues.apache.org/jira/browse/CLOUDSTACK-7887`_ fail to push snapshot to secondary storage if using multipart using swift... `CLOUDSTACK-7883 https://issues.apache.org/jira/browse/CLOUDSTACK-7883`_ Allow infrastructure to handle delete of volume from DB... `CLOUDSTACK-7871 https://issues.apache.org/jira/browse/CLOUDSTACK-7871`_ Fix update VirtualMachine/Template API to allow nic/disk controller details for ... `CLOUDSTACK-7855 https://issues.apache.org/jira/browse/CLOUDSTACK-7855`_ Sec storage/network MTU should be on nic3 and not nic1... `CLOUDSTACK-7826 https://issues.apache.org/jira/browse/CLOUDSTACK-7826`_ UI - dialog widget - dependent dropdown field (dependsOn property specified) - f... `CLOUDSTACK-7822 https://issues.apache.org/jira/browse/CLOUDSTACK-7822`_ test SSL cert expired... `CLOUDSTACK-7752 https://issues.apache.org/jira/browse/CLOUDSTACK-7752`_ Management Server goes in infinite loop while creating a vm with tagged local da... `CLOUDSTACK-7722 https://issues.apache.org/jira/browse/CLOUDSTACK-7722`_ add.label: Add button for tags show the label not Add text... `CLOUDSTACK-7246 https://issues.apache.org/jira/browse/CLOUDSTACK-7246`_ VM deployment failed due to wrong in script name createipalias.sh... Source release (checksums and signatures are available at the same location): https://dist.apache.org/repos/dist/dev/cloudstack/4.4.2 PGP release keys (signed using 4096R/AA4736F3): https://dist.apache.org/repos/dist/release/cloudstack/KEYS Vote will be open for 72 hours. For sanity in tallying the vote, can PMC members please be sure to indicate (binding) with their vote? [ ] +1 approve
Re: [QUESTION] @ReflectionUse
Are we going to (and can we) add functionality to make the code quality tools recognise it? (or is it just there to ignore? On Fri, Nov 28, 2014 at 5:00 AM, Rajani Karuturi raj...@apache.org wrote: It came in through the discussion on this thread http://markmail.org/message/j7ird7yzb3pvszbw ~Rajani On Thu, Nov 27, 2014 at 11:28 PM, Min Chen min.c...@citrix.com wrote: If I understand this clearly, this annotation was introduced by Kelven to prevent people from mistakenly removing those annotated methods if they find from IDE that those methods are not explicitly called anywhere. These methods are actually invoked through reflection. Thanks -min On Nov 27, 2014, at 3:21 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: H Kelven (or others), What are the plans with this annotation, ReflectionUse. Is there to be an implementation or folow up or is it maybe just there to ignore? -- Daan -- Daan
Re: review board cleanup
On Fri, Nov 28, 2014 at 10:13 AM, Rajani Karuturi raj...@apache.org wrote: Is there a way to 'force' close a review if its already submitted? some of us can, I for one. David got me the rights to that. I will give it a look coming days. ~Rajani On Fri, Nov 28, 2014 at 2:34 PM, sebgoa run...@gmail.com wrote: Hi folks, I pinged a few of you to try to get cleanup review board. there is 120 open reviews there. Since github is working nicely and folks are starting to migrate to this, it's time to clean up RB. A lot of reviews have actually been dealt with but not closed. So if you don't know what to do in the coming days, spending 30 minutes on review board and closing/updating a few reviews would be great. Cheers, -Sebastien -- Daan
Re: A secure way to reset VMs password
Another point to note is all the vms in production has to update with the new cloud-set-guest-password scripts because of the new password reset method. Thanks, Jayapal On 28-Nov-2014, at 2:28 PM, Erik Weber terbol...@gmail.com wrote: On Thu, Nov 27, 2014 at 3:54 PM, Alireza Eskandari astro.alir...@yahoo.com.invalid wrote: HiI viewed the bash script that resets Linux password ( http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in)It seems that it doesn't use a secure way for transferring password string to instance.Instances on a shared network can sniff password requests and export requested password of other instances.I suggest to use SSL (https) instead of plan text.Regards I like the idea, but there's a couple of obstacles to overcome, namely which SSL certificates to use. - certificates need a subject name, ie. IP or hostname for web pages, you could solve this by making the mgmt server a CA and have each VR get a signed certificate by it, but it's complicated - if the community bundle a pre generated certificate it is commonly known and not to be trusted, also not sure how to handle subject name - assuming everyone to supply a valid certificate is quite complicated (CA must be on VR etc), and makes it considerably harder to get a working setup - using self signed causes issues with validation Don't get me wrong, I love the idea, but it's not just to flip a switch and have (proper) SSL in place. -- Erik
Re: review board cleanup
U can get the karma by asking asf infra team. They have a hipchat channel, i just got karma right now -Sebastien On 28 Nov 2014, at 10:13, Rajani Karuturi raj...@apache.org wrote: Is there a way to 'force' close a review if its already submitted? ~Rajani On Fri, Nov 28, 2014 at 2:34 PM, sebgoa run...@gmail.com wrote: Hi folks, I pinged a few of you to try to get cleanup review board. there is 120 open reviews there. Since github is working nicely and folks are starting to migrate to this, it's time to clean up RB. A lot of reviews have actually been dealt with but not closed. So if you don't know what to do in the coming days, spending 30 minutes on review board and closing/updating a few reviews would be great. Cheers, -Sebastien
Re: review board cleanup
On 28-Nov-2014, at 2:43 pm, Rajani Karuturi raj...@apache.org wrote: Is there a way to 'force' close a review if its already submitted? Some of us can do it. I went through some of them yesterday and closed a few. There are many review requests on it which are too old and lack information. I’m not sure what to do with them. I’ll try to close a few more today. Regards, Rohit Yadav Software Architect, ShapeBlue M. +91 88 262 30892 | 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 Software Engineeringhttp://shapeblue.com/cloudstack-software-engineering/ 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.
Re: [DISCUSS] LTS Releases
Hey hey, Ooh, interesting topic. I'm going to top-post because I want to focus on the big picture! * Apache HTTPD provides 8+ years of support for old releases. * Tomcat provides 6+ years of support for N-2 release. * Ant provides 12+ years of backward compatiblity, so far. (details below) I think this is great and when I was proud of apache it was usually because of stuff like that. Every now and then I get a support enquiry about code that has been in the attic for many many years, and I always take the time to answer it, even if I've almost forgotten about collections pre java 1.2. This lng term support happens because the people that work on those projects want it to happen and do the work to make it happen. Since in this case, you want it to happen, and signed up to do the work, cloudstack its support window (for 4.3) grows. The more people do that, the bigger the support window will get. The 4.3 branch should live as long as people want to work on it and there's enough people to vote to release it. No-one should stop you, and I'd be a little upset if someone tried. This can happen naturally: it doesn't actually *need* a model or a discussion, just people to do the work and enough people to vote to release that work. You see a need here, you're stepping in to fill that need, so, thanks for volunteering (no sarcasm). I personally believe such explicit support models and commitments can hurt for 'upstreams' (*). If you look at the httpd download page, it doesn't say we'll support this for 8 years to come, it just says 'download here'. Users are expected and trusted to evaluate whether the community support is enough, and if it isn't, or they can't figure that out, they should go seek a downstream that provides the support (and typically, warranty and guarantee and indemnification and SLA and ...) that you don't get from an open source project. Ubuntu is a differently shaped project from cloudstack. Ubuntu is a (more unstable...) downstream of debian, where the httpd package is a downstream of httpd.apache.org. The key value of ubuntu LTS is in the tested _aggregation_ of many mutually compatible versions. IMHO. But hey, agreement is absolutely not required! I applaud you for doing what you think is right for your customers and for talking openly about it here. Customers these days tend to be pretty good at spotting who is listening to what they need, so as long as you understood that correctly, I'm sure it's a sound commercial decision for ShapeBlue too :-D cheers, Leo (*) I think in the lng term that quality improvement is best focused on master/tip. Well, at least up to about 80% unit test coverage or so :). My advice would be to ditch all 4.3 work, ditch any further 4.4 work, and invest all that effort into /testing/ for 4.5. Once you have high code velocity, trustable continuous integration and continuous delivery, etc, compatibilitystability are just more things to testmeasure, and they only go up. -- HTTPD * 2002-02-06 first release of apache httpd 2.0 * 2002-02-03 last release of apache httpd 1.3 That's a history of 8 years of support for N-1 major releases. * 2005-11-30 first release of apache httpd 2.2 * 2012-02-19 first release of apache httpd 2.4 * 2013-07-02 last release of apache httpd 2.0 That's a history of 8 years of support for N-1 minor releases. * 2.2 and 2.4 currently still being supported So so far that's 9 years of support for the current N-1 minor release. Of course httpd 2.4 is ~99% backward compatible with httpd 2.0, so that's 12+ years of backwards compatibility. Tomcat * 2004-08-29 first releaes of tomcat 5 * 2006-10-21 first release of tomcat 6 (still supported) * 2011-03-05 first release of tomcat 7 (still supported) * 2012-10-09 last release of tomcat 5 * 2014-02-02 first release of tomcat 8 So that's a history of 6 years of support for N-2 major releases. Ant * 2003-08-12 first release of ant 1.5 (1.5.2) * 2014-04-30 current release of ant (1.9.4) Ant's been ~99% backward compatible from about ant 1.4, but I can't find a timestamp for ant 1.4. So that's a history of 12 years of backward compatibility.
Random placing of Snapshots on multiple Secondary Storages
Hi I have a Cloudstack 4.2 setup running in my Lab.. 1 Zone with 1 XenServer 6.1 host and 1 Secondary Storage (NFS).. The space on this secondary storage is approx 60 GB.. I am planning to add a second Secondary Storage to the Zone (NFS : 200GB) and want to dedicate this new Sec Store as the default place to store the volume snapshots of my instances.. Cloudstack however places snapshots on both the Sec Stores randomly, so my question is that can this randomness be changed?? If yes, then where and how?? Regards, Yohan
Re: review board cleanup
Thanks sebastien. got mine. If anybody else is interested, it would be better to give a consolidated list to asfinfra. ~Rajani On Fri, Nov 28, 2014 at 3:08 PM, Sebastien Goasguen run...@gmail.com wrote: U can get the karma by asking asf infra team. They have a hipchat channel, i just got karma right now -Sebastien On 28 Nov 2014, at 10:13, Rajani Karuturi raj...@apache.org wrote: Is there a way to 'force' close a review if its already submitted? ~Rajani On Fri, Nov 28, 2014 at 2:34 PM, sebgoa run...@gmail.com wrote: Hi folks, I pinged a few of you to try to get cleanup review board. there is 120 open reviews there. Since github is working nicely and folks are starting to migrate to this, it's time to clean up RB. A lot of reviews have actually been dealt with but not closed. So if you don't know what to do in the coming days, spending 30 minutes on review board and closing/updating a few reviews would be great. Cheers, -Sebastien
Build failed in Jenkins: build-master-noredist #3873
See http://jenkins.buildacloud.org/job/build-master-noredist/3873/changes Changes: [Rohit Yadav] CLOUDSTACK-7989: Ignore Auth API calls in unauthenticated HTTP handlers [Rohit Yadav] packaging: add license to missing cloud.limits -- [...truncated 30109 lines...] [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-engine-network --- [INFO] Installing http://jenkins.buildacloud.org/job/build-master-noredist/ws/engine/network/target/cloud-engine-network-4.6.0-SNAPSHOT.jar to /jenkins/.m2/repository/org/apache/cloudstack/cloud-engine-network/4.6.0-SNAPSHOT/cloud-engine-network-4.6.0-SNAPSHOT.jar [INFO] Installing http://jenkins.buildacloud.org/job/build-master-noredist/ws/engine/network/pom.xml to /jenkins/.m2/repository/org/apache/cloudstack/cloud-engine-network/4.6.0-SNAPSHOT/cloud-engine-network-4.6.0-SNAPSHOT.pom [INFO] [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-agent --- [INFO] Surefire report directory: http://jenkins.buildacloud.org/job/build-master-noredist/ws/agent/target/surefire-reports --- T E S T S --- Running com.cloud.agent.AgentShellTest log4j:WARN No appenders could be found for logger (com.cloud.agent.AgentShell). 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: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.251 sec Running com.cloud.agent.dao.impl.PropertiesStorageTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.073 sec Results : Tests run: 4, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ cloud-agent --- [INFO] Building jar: http://jenkins.buildacloud.org/job/build-master-noredist/ws/agent/target/cloud-agent-4.6.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-agent --- [INFO] [INFO] --- maven-dependency-plugin:2.5.1:copy-dependencies (copy-dependencies) @ cloud-agent --- Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom 2/2 KB Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-10/doxia-sink-api-1.0-alpha-10.pom (2 KB at 41.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom 4/9 KB 8/9 KB 9/9 KB Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-10/doxia-1.0-alpha-10.pom (9 KB at 344.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom 4/5 KB 5/5 KB Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.5/maven-reporting-impl-2.0.5.pom (5 KB at 152.7 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.pom 3/3 KB Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.pom (3 KB at 83.5 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.5.7/plexus-utils-1.5.7.pom 4/8 KB 8/8 KB 8/8 KB Downloaded: http://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.5.7/plexus-utils-1.5.7.pom (8 KB at 254.0 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.pom 4/5 KB 5/5 KB Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.pom (5 KB at 160.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sitetools/1.0/doxia-sitetools-1.0.pom 4/10 KB 8/10 KB 10/10 KB Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sitetools/1.0/doxia-sitetools-1.0.pom (10 KB at 360.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.pom 4/4 KB Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.pom (4 KB at 93.3 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.pom 3/3 KB Downloaded: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.pom (3 KB at 78.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-modules/1.0/doxia-modules-1.0.pom 3/3 KB Downloaded:
Jenkins build is back to normal : build-master-noredist #3874
See http://jenkins.buildacloud.org/job/build-master-noredist/3874/
[GitHub] cloudstack pull request: CLOUDSTACK-7986 [F5 LB] Failed to execute...
GitHub user sudhansu7 opened a pull request: https://github.com/apache/cloudstack/pull/47 CLOUDSTACK-7986 [F5 LB] Failed to execute IPAssocCommand due to com.clou... added 3 new method to strip partition information from VirtualServer, LBPool, VLAN api response. With BigIP V11.x VirtualServer, LBPool, VLAN api response has been modified. Now BigIP returns resource name with user partition information ex: if vlanname is vlan-100 then the get_list() will return /Common/vlan-100 (/Common - Suer portition) This method will strip the partition information and only returns a list with vlan name (vlan-100) You can merge this pull request into a Git repository by running: $ git pull https://github.com/sudhansu7/cloudstack CLOUDSTACK-7986 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/47.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 #47 commit 7ed6909246d55c63e89a419a82af03b6080af340 Author: Sudhansu sudhansu.s...@citrix.com Date: 2014-11-28T11:01:08Z CLOUDSTACK-7986 [F5 LB] Failed to execute IPAssocCommand due to com.cloud.utils.exception.ExecutionException: Exception caught in Networking::urn:iControl:Networking/VLAN::create() added 3 new method to strip partition information from VirtualServer, LBPool, VLAN api response. With BigIP V11.x VirtualServer, LBPool, VLAN api response has been modified. Now BigIP returns resource name with user partition information ex: if vlanname is vlan-100 then the get_list() will return /Common/vlan-100 (/Common - Suer portition) This method will strip the partition information and only returns a list with vlan name (vlan-100) --- 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: A secure way to reset VMs password
For me personaly, this Cloudstack feature is used only during damn I forgot my password and during deploying new VM from template. After I get access to VM - the password should be really changed anyway. I agree it's unsecure, but again you are supposed to change it - and not hope that the passwrod generated by third party tool (not yourself) is safe or not stored anywhere else... On 28 November 2014 at 10:34, Jayapal Reddy Uradi jayapalreddy.ur...@citrix.com wrote: Another point to note is all the vms in production has to update with the new cloud-set-guest-password scripts because of the new password reset method. Thanks, Jayapal On 28-Nov-2014, at 2:28 PM, Erik Weber terbol...@gmail.com wrote: On Thu, Nov 27, 2014 at 3:54 PM, Alireza Eskandari astro.alir...@yahoo.com.invalid wrote: HiI viewed the bash script that resets Linux password ( http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in)It seems that it doesn't use a secure way for transferring password string to instance.Instances on a shared network can sniff password requests and export requested password of other instances.I suggest to use SSL (https) instead of plan text.Regards I like the idea, but there's a couple of obstacles to overcome, namely which SSL certificates to use. - certificates need a subject name, ie. IP or hostname for web pages, you could solve this by making the mgmt server a CA and have each VR get a signed certificate by it, but it's complicated - if the community bundle a pre generated certificate it is commonly known and not to be trusted, also not sure how to handle subject name - assuming everyone to supply a valid certificate is quite complicated (CA must be on VR etc), and makes it considerably harder to get a working setup - using self signed causes issues with validation Don't get me wrong, I love the idea, but it's not just to flip a switch and have (proper) SSL in place. -- Erik -- Andrija Panić
Jenkins build is still unstable: simulator-singlerun #714
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Fwd: NFS mount options hardcoded or not ?
Hi guys, just wanted to know if NFS mount options for Primary Storage are hardcoded in the source, or do we let OS use it's default... ? It seems to me it is not hardcoded, but I would really like confirmation pls. Thanks, - Andrija Panić
Re: Fwd: NFS mount options hardcoded or not ?
On 11/28/2014 01:37 PM, Andrija Panic wrote: Hi guys, just wanted to know if NFS mount options for Primary Storage are hardcoded in the source, or do we let OS use it's default... ? They come from libvirt, it's not done by CloudStack. You can change them in /etc/nfsmount.conf, see man nfsmount.conf Wido It seems to me it is not hardcoded, but I would really like confirmation pls. Thanks, - Andrija Panić
Re: Fwd: NFS mount options hardcoded or not ?
thx Wido... On 28 November 2014 at 15:07, Wido den Hollander w...@widodh.nl wrote: On 11/28/2014 01:37 PM, Andrija Panic wrote: Hi guys, just wanted to know if NFS mount options for Primary Storage are hardcoded in the source, or do we let OS use it's default... ? They come from libvirt, it's not done by CloudStack. You can change them in /etc/nfsmount.conf, see man nfsmount.conf Wido It seems to me it is not hardcoded, but I would really like confirmation pls. Thanks, - Andrija Panić -- Andrija Panić
Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)
Hi guys, Tests results for ACS 4.4.2. I will also do the same tests, but using a dump from our betacloud database. Cheers, Wilder Environment: * XenServer host running on Betacloud (ACS 4.3.0 VMWare zone) * Management server running on MacBook Pro * MySQL Database running on MacBook Pro * System VM: jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/ Test Accounts Test Create Account and user for that account ... === TestName: test_01_create_account | Status : SUCCESS === ok Test Sub domain allowed to launch VM when a Domain level zone is created ... === TestName: test_01_add_vm_to_subdomain | Status : SUCCESS === ok Test delete domain without force option ... === TestName: test_DeleteDomain | Status : SUCCESS === ok Test delete domain with force option ... === TestName: test_forceDeleteDomain | Status : SUCCESS === ok Test update admin details ... === TestName: test_updateAdminDetails | Status : SUCCESS === ok Test update domain admin details ... === TestName: test_updateDomainAdminDetails | Status : SUCCESS === ok Test user update API ... === TestName: test_updateUserDetails | Status : SUCCESS === ok Test login API with domain ... === TestName: test_LoginApiDomain | Status : SUCCESS === ok Test if Login API does not return UUID's ... === TestName: test_LoginApiUuidResponse | Status : SUCCESS === ok -- Ran 9 tests in 780.740s OK Test VM Life Cycle Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status : SUCCESS === ok Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS === ok Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status : SUCCESS === ok Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS === ok Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS === ok Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS === ok Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS === ok Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS === ok Test migrate VM ... SKIP: At least two hosts should be present in the zone for migration Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status : SUCCESS === ok -- Ran 10 tests in 741.803s OK (SKIP=1) Test Create Service Offerings [VMS are also created] Test to create service offering ... === TestName: test_01_create_service_offering | Status : SUCCESS === ok Test to update existing service offering ... === TestName: test_02_edit_service_offering | Status : SUCCESS === ok Test to delete service offering ... === TestName: test_03_delete_service_offering | Status : SUCCESS === ok -- Ran 3 tests in 136.911s OK Test Private GW ACLs test_privategw_acl (ekholabs.acs.tests.test_privategw_acl.TestPrivateGwACL) ... === TestName: test_privategw_acl | Status : SUCCESS === ok -- Ran 1 test in 81.119s OK Test Routers Test router internal advanced zone ... SKIP: Marvin configuration has no host credentials to check router services Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS === ok Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS === ok Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS === ok Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS === ok Test start router ... === TestName: test_08_start_router | Status : SUCCESS === ok Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS === ok -- Ran 7 tests in 313.247s OK (SKIP=1) Test Reset VM on Reboot Test reset virtual machine on reboot ... === TestName: test_01_reset_vm_on_reboot | Status : SUCCESS === ok -- Ran 1 test in 156.888s OK Test VPC Routers Test start/stop of router after addition of one guest network ... === TestName: test_01_start_stop_router_after_addition_of_one_guest_network | Status : SUCCESS === ok Test reboot of router after addition of one guest network ... === TestName: test_02_reboot_router_after_addition_of_one_guest_network | Status : SUCCESS === ok Test to change service offering of router after addition of one guest network ... === TestName: test_04_chg_srv_off_router_after_addition_of_one_guest_network | Status : SUCCESS === ok Test destroy of router after addition of one guest network ... === TestName:
Re: [JENKINS] Added CentOS 7 slaves
Jenkins does not support Azure, yet. Well, at least not compute. There are some folks working on this support, but, it's not there yet. --David On Wed, Nov 26, 2014 at 10:50 AM, Hugo Trippaers h...@trippaers.nl wrote: Good point, i’ll need to check if jclouds supports azure but a few dynamic slaves could be nice. Cheers, Hugo On 26 nov. 2014, at 16:39, Ian Duffy i...@ianduffy.ie wrote: Just throwing this out there All committers have access to a msdn subscription that gives 125eur worth of azure credits. You can get a decent VM for that. On 26 Nov 2014 15:37, Pierre-Luc Dion pd...@cloudops.com wrote: does it only require to run jenkins as slave? or their is any other particular requirements? *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Wed, Nov 26, 2014 at 10:25 AM, Hugo Trippaers h...@trippaers.nl wrote: If any one needs something build or tested on CentOS 7 let me know or create a build tagged for cloudstack-buildslave-centos7 Cheers, Hugo P.S. Still looking for people willing to add slaves to jenkins. What we need are one or two fast machines capable of running the simulator tests.
Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2)
great Wilder, sound like we're all green :-) On Fri, Nov 28, 2014 at 3:34 PM, Wilder Rodrigues wrodrig...@schubergphilis.com wrote: Hi guys, Tests results for ACS 4.4.2. I will also do the same tests, but using a dump from our betacloud database. Cheers, Wilder Environment: * XenServer host running on Betacloud (ACS 4.3.0 VMWare zone) * Management server running on MacBook Pro * MySQL Database running on MacBook Pro * System VM: jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/ Test Accounts Test Create Account and user for that account ... === TestName: test_01_create_account | Status : SUCCESS === ok Test Sub domain allowed to launch VM when a Domain level zone is created ... === TestName: test_01_add_vm_to_subdomain | Status : SUCCESS === ok Test delete domain without force option ... === TestName: test_DeleteDomain | Status : SUCCESS === ok Test delete domain with force option ... === TestName: test_forceDeleteDomain | Status : SUCCESS === ok Test update admin details ... === TestName: test_updateAdminDetails | Status : SUCCESS === ok Test update domain admin details ... === TestName: test_updateDomainAdminDetails | Status : SUCCESS === ok Test user update API ... === TestName: test_updateUserDetails | Status : SUCCESS === ok Test login API with domain ... === TestName: test_LoginApiDomain | Status : SUCCESS === ok Test if Login API does not return UUID's ... === TestName: test_LoginApiUuidResponse | Status : SUCCESS === ok -- Ran 9 tests in 780.740s OK Test VM Life Cycle Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status : SUCCESS === ok Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS === ok Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status : SUCCESS === ok Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS === ok Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS === ok Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS === ok Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS === ok Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS === ok Test migrate VM ... SKIP: At least two hosts should be present in the zone for migration Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status : SUCCESS === ok -- Ran 10 tests in 741.803s OK (SKIP=1) Test Create Service Offerings [VMS are also created] Test to create service offering ... === TestName: test_01_create_service_offering | Status : SUCCESS === ok Test to update existing service offering ... === TestName: test_02_edit_service_offering | Status : SUCCESS === ok Test to delete service offering ... === TestName: test_03_delete_service_offering | Status : SUCCESS === ok -- Ran 3 tests in 136.911s OK Test Private GW ACLs test_privategw_acl (ekholabs.acs.tests.test_privategw_acl.TestPrivateGwACL) ... === TestName: test_privategw_acl | Status : SUCCESS === ok -- Ran 1 test in 81.119s OK Test Routers Test router internal advanced zone ... SKIP: Marvin configuration has no host credentials to check router services Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS === ok Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS === ok Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS === ok Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS === ok Test start router ... === TestName: test_08_start_router | Status : SUCCESS === ok Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS === ok -- Ran 7 tests in 313.247s OK (SKIP=1) Test Reset VM on Reboot Test reset virtual machine on reboot ... === TestName: test_01_reset_vm_on_reboot | Status : SUCCESS === ok -- Ran 1 test in 156.888s OK Test VPC Routers Test start/stop of router after addition of one guest network ... === TestName: test_01_start_stop_router_after_addition_of_one_guest_network | Status : SUCCESS === ok Test reboot of router after addition of one guest network ... === TestName: test_02_reboot_router_after_addition_of_one_guest_network | Status : SUCCESS === ok Test to change service
[GitHub] cloudstack pull request: CLOUDSTACK-7908: Add user_id column to vm...
GitHub user bhaisaab opened a pull request: https://github.com/apache/cloudstack/pull/48 CLOUDSTACK-7908: Add user_id column to vm_instance table - Adds column to VMInstance DAO - Adds column in vm_instance table - Adds column in the UserVMJoinVO - Adds default admin user which has UID = 2 - Adds migration path that sets user_id to first user of the accountId that owns the vm in vm_instance table - Add arg on list VMs API to query by userId, add support in query layer - Refactor VMInstanceVO and child classes to accept userId - Add code to let service layer pass userId if loggedIn user belongs to same account as the owner executing an API call or use first user from owner account - In case of CPVM and SSVM use system user ID - Fix unit tests and spring injections Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/cloudstack useraccount-refactoring Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/48.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 #48 commit 1e25886bd229a3b7b7aecafe2dc7eaeede47982e Author: Rohit Yadav rohit.ya...@shapeblue.com Date: 2014-11-28T11:37:02Z CLOUDSTACK-7908: Add user_id column to vm_instance table - Adds column to VMInstance DAO - Adds column in vm_instance table - Adds column in the UserVMJoinVO - Adds default admin user which has UID = 2 - Adds migration path that sets user_id to first user of the accountId that owns the vm in vm_instance table - Add arg on list VMs API to query by userId, add support in query layer - Refactor VMInstanceVO and child classes to accept userId - Add code to let service layer pass userId if loggedIn user belongs to same account as the owner executing an API call or use first user from owner account - In case of CPVM and SSVM use system user ID - Fix unit tests and spring injections Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com --- 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. ---
cloudmonkey release
Rohit et al, Can cloudmonkey 5.2.0 be archived or is this release still being maintained? (i.e. is a 5.2.1 to be expected now that 5.3.0 is out?) thanks -- Daan
Re: Review Request 17941: CLOUDSTACK-6075: Increase the ram size for router service offering
Rohit, is this really needed in 4.3? We are throwing away our agreed policies on db changes here. When talking on customers that kind of masquerades the upgrade dilemma they have with a minor version in a tiny version. @Hari I'll find some time to add the 442to443 path On Fri, Nov 28, 2014 at 6:59 AM, Harikrishna Patnala harikrishna.patn...@citrix.com wrote: Hi, This patch was only intended to put in 4.5 and master and later it was back ported to 4.3. If you can help me adding the upgrade path from 4.4.2 to 4.4.3, I’ll put the PR for back porting to 4.4.3 Thanks, Harikrishna On 27-Nov-2014, at 8:59 pm, Rohit Yadav bhais...@apache.org wrote: Hi Rajani, I've already started a thread on user/dev ML around LTS releases, we should have discussion there. On Thu, Nov 27, 2014 at 6:26 PM, Rajani Karuturi raj...@apache.org wrote: I dont like the idea of release manager cherry-picking/backporting the fixes to the release branches. As a community we are supporting past two releases. ie) at this point we have to support 4.3 and 4.4 As a developer/contributor, if I feel a bug is relevant for 4.3 I should be committing it to all the 4.3+ releases. Otherwise it would be a nightmare for people trying to upgrade later. If and when a release is required, we should release from that branch. +1 that's the ideal case and everyone should do it but since I had to backport more than 90 fixes from 4.4/4.5/master to 4.3 many of us were clearly not doing that. In many opensource projects such as Linux, it's common to see different people maintaining a certain branch or major release. I want to do the same for 4.3 until a stable 4.5.x or 4.6.x is out that is fairly tested and used in the wild. Everyone is welcome to do it for any branches they do. Regards. ~Rajani On Thu, Nov 27, 2014 at 6:13 PM, Rohit Yadav bhais...@apache.org wrote: On Thu, Nov 27, 2014 at 5:30 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: ok, so that would go in 442to443? Yes, but do you plan to do a 4.4.3? The whole debate around maintaining 4.3 vs 4.4 comes down to stakeholder's interests, you've shared that you may not want to put a lot of efforts on 4.4 branch since 4.5.0 is around but if I'm mistaken and since you're the release manager you should backport changes applicable on 4.4 and do a 4.4.3 release. That would be great for 4.4.x users. Before the patch could be ported, Hari will need to use an empty upgrade path from 4.4.2 to 4.4.3 and change versions in pom files etc. Hari let me know if you can do that in your backport or if Daan or I need to add that for you. Thanks. On Thu, Nov 27, 2014 at 12:52 PM, Rohit Yadav bhais...@apache.org wrote: Daan, On Thu, Nov 27, 2014 at 4:17 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: If this contains db upgrade code, where did this go in 4.3? In the review request I see changes to 442to450 upgrade files so this should not go in 4.3 or 4.4. What am I missing? For 4.3, the upgrade path (it's just data migration no schema changes so easily backportable) is from 4.3.1 to 4.3.2 in Upgrade431to432 class. The fix simply goes through existing VRs and updates their RAM size, no schema changes here only data migrations. Regards. -- Daan -- Daan
Re: A secure way to reset VMs password
Andrija, Don't think like that if you run a public offering. Convenience will always win, the customer will not change the password. :) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Andrija Panic andrija.pa...@gmail.com To: dev@cloudstack.apache.org Cc: Alireza Eskandari astro.alir...@yahoo.com Sent: Friday, 28 November, 2014 12:05:53 Subject: Re: A secure way to reset VMs password For me personaly, this Cloudstack feature is used only during damn I forgot my password and during deploying new VM from template. After I get access to VM - the password should be really changed anyway. I agree it's unsecure, but again you are supposed to change it - and not hope that the passwrod generated by third party tool (not yourself) is safe or not stored anywhere else... On 28 November 2014 at 10:34, Jayapal Reddy Uradi jayapalreddy.ur...@citrix.com wrote: Another point to note is all the vms in production has to update with the new cloud-set-guest-password scripts because of the new password reset method. Thanks, Jayapal On 28-Nov-2014, at 2:28 PM, Erik Weber terbol...@gmail.com wrote: On Thu, Nov 27, 2014 at 3:54 PM, Alireza Eskandari astro.alir...@yahoo.com.invalid wrote: HiI viewed the bash script that resets Linux password ( http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in)It seems that it doesn't use a secure way for transferring password string to instance.Instances on a shared network can sniff password requests and export requested password of other instances.I suggest to use SSL (https) instead of plan text.Regards I like the idea, but there's a couple of obstacles to overcome, namely which SSL certificates to use. - certificates need a subject name, ie. IP or hostname for web pages, you could solve this by making the mgmt server a CA and have each VR get a signed certificate by it, but it's complicated - if the community bundle a pre generated certificate it is commonly known and not to be trusted, also not sure how to handle subject name - assuming everyone to supply a valid certificate is quite complicated (CA must be on VR etc), and makes it considerably harder to get a working setup - using self signed causes issues with validation Don't get me wrong, I love the idea, but it's not just to flip a switch and have (proper) SSL in place. -- Erik -- Andrija Panić
Re: A secure way to reset VMs password
Jayapal, Not necesarily, one could run stunnel or nginx as SSL proxy on some other port (8443?), this way SSL and non-SSL connections will still work and give you plenty of time to update your templates, if you so wish. Am I missing any important bits here? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Jayapal Reddy Uradi jayapalreddy.ur...@citrix.com To: dev@cloudstack.apache.org dev@cloudstack.apache.org Cc: Alireza Eskandari astro.alir...@yahoo.com Sent: Friday, 28 November, 2014 09:34:02 Subject: Re: A secure way to reset VMs password Another point to note is all the vms in production has to update with the new cloud-set-guest-password scripts because of the new password reset method. Thanks, Jayapal On 28-Nov-2014, at 2:28 PM, Erik Weber terbol...@gmail.com wrote: On Thu, Nov 27, 2014 at 3:54 PM, Alireza Eskandari astro.alir...@yahoo.com.invalid wrote: HiI viewed the bash script that resets Linux password ( http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in)It seems that it doesn't use a secure way for transferring password string to instance.Instances on a shared network can sniff password requests and export requested password of other instances.I suggest to use SSL (https) instead of plan text.Regards I like the idea, but there's a couple of obstacles to overcome, namely which SSL certificates to use. - certificates need a subject name, ie. IP or hostname for web pages, you could solve this by making the mgmt server a CA and have each VR get a signed certificate by it, but it's complicated - if the community bundle a pre generated certificate it is commonly known and not to be trusted, also not sure how to handle subject name - assuming everyone to supply a valid certificate is quite complicated (CA must be on VR etc), and makes it considerably harder to get a working setup - using self signed causes issues with validation Don't get me wrong, I love the idea, but it's not just to flip a switch and have (proper) SSL in place. -- Erik
root resize support in the UI
Hello, Wonder if someone can help me with the $subject. I remember at some point (4.2?) a new feature showed up accidentally in the UI instance creation dialogues, it was concerning root size, had a small box where the number in GB would be introduced. I'd like to take advantage of that now that this feature actually works, even if only in KVM. I'd love it if someone could point me to that piece of code (prolly just javascript). In addition to that, now that root resize works, can any one suggest how I might put a resize button in the Volumes section for the ROOT disks? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: root resize support in the UI
For root disks, is it possible to just follow the existing resize pattern we have established in the UI for data disks? On Friday, November 28, 2014, Nux! n...@li.nux.ro wrote: Hello, Wonder if someone can help me with the $subject. I remember at some point (4.2?) a new feature showed up accidentally in the UI instance creation dialogues, it was concerning root size, had a small box where the number in GB would be introduced. I'd like to take advantage of that now that this feature actually works, even if only in KVM. I'd love it if someone could point me to that piece of code (prolly just javascript). In addition to that, now that root resize works, can any one suggest how I might put a resize button in the Volumes section for the ROOT disks? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro -- *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: [jira] [Commented] (CLOUDSTACK-6181) Root resize
I think we should protect from this in code. On Friday, November 28, 2014, Nux (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/CLOUDSTACK-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228496#comment-14228496 ] Nux commented on CLOUDSTACK-6181: - Managed to corrupt a VM's disk today by live resizing it; it was a just a test VM. Wonder if this is something we wished to prevent in the code or just make people aware of it? It may not be obvious to everyone resizing it on the fly while the VM is running will cause corruption. Root resize --- Key: CLOUDSTACK-6181 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, Storage Controller, UI Affects Versions: 4.4.0 Environment: KVM/libvirt/CentOS, Xenserver Reporter: Nux Labels: disk, resize, template Fix For: 4.4.0 Rationale: Currently the root size of an instance is locked to that of the template. This creates unnecessary template duplicates, prevents the creation of a market place, wastes time and disk space and generally makes work more complicated. Real life example - a small VPS provider might want to offer the following sizes (in GB): 10,20,40,80,160,240,320,480,620 That's 9 offerings. The template selection could look like this, including real disk space used: Windows 2008 ~10GB Windows 2008+Plesk ~15GB Windows 2008+MSSQL ~15GB Windows 2012 ~10GB Windows 2012+Plesk ~15GB Windows 2012+MSSQL ~15GB CentOS ~1GB CentOS+CPanel ~3GB CentOS+Virtualmin ~3GB CentOS+Zimbra ~3GB CentOS+Docker ~2GB Debian ~1GB Ubuntu LTS ~1GB In this case the total disk space used by templates will be 828 GB, that's almost 1 TB. If your storage is expensive and limited SSD this can get painful! If the root resize feature is enabled we can reduce this to under 100 GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332) -- *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: Review Request 17941: CLOUDSTACK-6075: Increase the ram size for router service offering
On Sat, Nov 29, 2014 at 12:49 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: Rohit, is this really needed in 4.3? We are throwing away our agreed policies on db changes here. When talking on customers that kind of masquerades the upgrade dilemma they have with a minor version in a tiny version. Yes, there is no db schema change, only data migration and updates. Talk is cheap, go see the code: https://github.com/apache/cloudstack/commit/6d31aca25cd5848272aaa190581f1f7c2bc00729 @Hari I'll find some time to add the 442to443 path On Fri, Nov 28, 2014 at 6:59 AM, Harikrishna Patnala harikrishna.patn...@citrix.com wrote: Hi, This patch was only intended to put in 4.5 and master and later it was back ported to 4.3. If you can help me adding the upgrade path from 4.4.2 to 4.4.3, I'll put the PR for back porting to 4.4.3 Thanks, Harikrishna On 27-Nov-2014, at 8:59 pm, Rohit Yadav bhais...@apache.org wrote: Hi Rajani, I've already started a thread on user/dev ML around LTS releases, we should have discussion there. On Thu, Nov 27, 2014 at 6:26 PM, Rajani Karuturi raj...@apache.org wrote: I dont like the idea of release manager cherry-picking/backporting the fixes to the release branches. As a community we are supporting past two releases. ie) at this point we have to support 4.3 and 4.4 As a developer/contributor, if I feel a bug is relevant for 4.3 I should be committing it to all the 4.3+ releases. Otherwise it would be a nightmare for people trying to upgrade later. If and when a release is required, we should release from that branch. +1 that's the ideal case and everyone should do it but since I had to backport more than 90 fixes from 4.4/4.5/master to 4.3 many of us were clearly not doing that. In many opensource projects such as Linux, it's common to see different people maintaining a certain branch or major release. I want to do the same for 4.3 until a stable 4.5.x or 4.6.x is out that is fairly tested and used in the wild. Everyone is welcome to do it for any branches they do. Regards. ~Rajani On Thu, Nov 27, 2014 at 6:13 PM, Rohit Yadav bhais...@apache.org wrote: On Thu, Nov 27, 2014 at 5:30 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: ok, so that would go in 442to443? Yes, but do you plan to do a 4.4.3? The whole debate around maintaining 4.3 vs 4.4 comes down to stakeholder's interests, you've shared that you may not want to put a lot of efforts on 4.4 branch since 4.5.0 is around but if I'm mistaken and since you're the release manager you should backport changes applicable on 4.4 and do a 4.4.3 release. That would be great for 4.4.x users. Before the patch could be ported, Hari will need to use an empty upgrade path from 4.4.2 to 4.4.3 and change versions in pom files etc. Hari let me know if you can do that in your backport or if Daan or I need to add that for you. Thanks. On Thu, Nov 27, 2014 at 12:52 PM, Rohit Yadav bhais...@apache.org wrote: Daan, On Thu, Nov 27, 2014 at 4:17 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: If this contains db upgrade code, where did this go in 4.3? In the review request I see changes to 442to450 upgrade files so this should not go in 4.3 or 4.4. What am I missing? For 4.3, the upgrade path (it's just data migration no schema changes so easily backportable) is from 4.3.1 to 4.3.2 in Upgrade431to432 class. The fix simply goes through existing VRs and updates their RAM size, no schema changes here only data migrations. Regards. -- Daan -- Daan
Re: cloudmonkey release
Hi Daan, yes please go ahead if you're archiving release artifacts. 5.3.0 is latest, I'll work on a bugfix release 5.3.1 soon. Regards. Sent from OWA on Android From: Daan Hoogland daan.hoogl...@gmail.com Sent: Saturday, November 29, 2014 12:40:34 AM To: dev; Rohit Yadav Subject: cloudmonkey release Rohit et al, Can cloudmonkey 5.2.0 be archived or is this release still being maintained? (i.e. is a 5.2.1 to be expected now that 5.3.0 is out?) thanks -- Daan 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 Software Engineeringhttp://shapeblue.com/cloudstack-software-engineering/ 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.
Re: [QUESTION] @ReflectionUse
Hi, How about declaring those methods package protected? With that it is still not considered a public api, but findbugs does not detect it as a bug. Also, it would be nice to have some javadoc on these methods on how they are used, what calls them, etc... On Fri, Nov 28, 2014 at 10:14 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: Are we going to (and can we) add functionality to make the code quality tools recognise it? (or is it just there to ignore? On Fri, Nov 28, 2014 at 5:00 AM, Rajani Karuturi raj...@apache.org wrote: It came in through the discussion on this thread http://markmail.org/message/j7ird7yzb3pvszbw ~Rajani On Thu, Nov 27, 2014 at 11:28 PM, Min Chen min.c...@citrix.com wrote: If I understand this clearly, this annotation was introduced by Kelven to prevent people from mistakenly removing those annotated methods if they find from IDE that those methods are not explicitly called anywhere. These methods are actually invoked through reflection. Thanks -min On Nov 27, 2014, at 3:21 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: H Kelven (or others), What are the plans with this annotation, ReflectionUse. Is there to be an implementation or folow up or is it maybe just there to ignore? -- Daan -- Daan -- EOF
Re: Review Request 17941: CLOUDSTACK-6075: Increase the ram size for router service offering
Hari, I added the 443 upgrade path, feel free to commit on the 4.4 branch. On Fri, Nov 28, 2014 at 9:17 PM, Rohit Yadav bhais...@apache.org wrote: On Sat, Nov 29, 2014 at 12:49 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: Rohit, is this really needed in 4.3? We are throwing away our agreed policies on db changes here. When talking on customers that kind of masquerades the upgrade dilemma they have with a minor version in a tiny version. Yes, there is no db schema change, only data migration and updates. Talk is cheap, go see the code: https://github.com/apache/cloudstack/commit/6d31aca25cd5848272aaa190581f1f7c2bc00729 @Hari I'll find some time to add the 442to443 path On Fri, Nov 28, 2014 at 6:59 AM, Harikrishna Patnala harikrishna.patn...@citrix.com wrote: Hi, This patch was only intended to put in 4.5 and master and later it was back ported to 4.3. If you can help me adding the upgrade path from 4.4.2 to 4.4.3, I’ll put the PR for back porting to 4.4.3 Thanks, Harikrishna On 27-Nov-2014, at 8:59 pm, Rohit Yadav bhais...@apache.org wrote: Hi Rajani, I've already started a thread on user/dev ML around LTS releases, we should have discussion there. On Thu, Nov 27, 2014 at 6:26 PM, Rajani Karuturi raj...@apache.org wrote: I dont like the idea of release manager cherry-picking/backporting the fixes to the release branches. As a community we are supporting past two releases. ie) at this point we have to support 4.3 and 4.4 As a developer/contributor, if I feel a bug is relevant for 4.3 I should be committing it to all the 4.3+ releases. Otherwise it would be a nightmare for people trying to upgrade later. If and when a release is required, we should release from that branch. +1 that's the ideal case and everyone should do it but since I had to backport more than 90 fixes from 4.4/4.5/master to 4.3 many of us were clearly not doing that. In many opensource projects such as Linux, it's common to see different people maintaining a certain branch or major release. I want to do the same for 4.3 until a stable 4.5.x or 4.6.x is out that is fairly tested and used in the wild. Everyone is welcome to do it for any branches they do. Regards. ~Rajani On Thu, Nov 27, 2014 at 6:13 PM, Rohit Yadav bhais...@apache.org wrote: On Thu, Nov 27, 2014 at 5:30 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: ok, so that would go in 442to443? Yes, but do you plan to do a 4.4.3? The whole debate around maintaining 4.3 vs 4.4 comes down to stakeholder's interests, you've shared that you may not want to put a lot of efforts on 4.4 branch since 4.5.0 is around but if I'm mistaken and since you're the release manager you should backport changes applicable on 4.4 and do a 4.4.3 release. That would be great for 4.4.x users. Before the patch could be ported, Hari will need to use an empty upgrade path from 4.4.2 to 4.4.3 and change versions in pom files etc. Hari let me know if you can do that in your backport or if Daan or I need to add that for you. Thanks. On Thu, Nov 27, 2014 at 12:52 PM, Rohit Yadav bhais...@apache.org wrote: Daan, On Thu, Nov 27, 2014 at 4:17 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: If this contains db upgrade code, where did this go in 4.3? In the review request I see changes to 442to450 upgrade files so this should not go in 4.3 or 4.4. What am I missing? For 4.3, the upgrade path (it's just data migration no schema changes so easily backportable) is from 4.3.1 to 4.3.2 in Upgrade431to432 class. The fix simply goes through existing VRs and updates their RAM size, no schema changes here only data migrations. Regards. -- Daan -- Daan -- Daan
Re: root resize support in the UI
Yeah, I was thinking of that, if it works for DATA, it should work for ROOT. But I am not a dev. Thoughts? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org Sent: Friday, 28 November, 2014 19:57:27 Subject: Re: root resize support in the UI For root disks, is it possible to just follow the existing resize pattern we have established in the UI for data disks? On Friday, November 28, 2014, Nux! n...@li.nux.ro wrote: Hello, Wonder if someone can help me with the $subject. I remember at some point (4.2?) a new feature showed up accidentally in the UI instance creation dialogues, it was concerning root size, had a small box where the number in GB would be introduced. I'd like to take advantage of that now that this feature actually works, even if only in KVM. I'd love it if someone could point me to that piece of code (prolly just javascript). In addition to that, now that root resize works, can any one suggest how I might put a resize button in the Volumes section for the ROOT disks? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro -- *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*™*
ApacheCon EU videos
Hi, Were there videos taken of the discussions? Have they been uploaded anywhere? Would probably like to watch some of that. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: ApacheCon EU videos
I don't know about videos from ApacheCon, but they were videoing the CloudStack Collab Conf presentations. These videos typically have taken about a month or so to show up on YouTube. On Fri, Nov 28, 2014 at 4:49 PM, Nux! n...@li.nux.ro wrote: Hi, Were there videos taken of the discussions? Have they been uploaded anywhere? Would probably like to watch some of that. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro -- *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: root resize support in the UI
Have you logged a JIRA ticket for this? Maybe Brian or one of the GUI people could pick up on it. On Fri, Nov 28, 2014 at 4:32 PM, Nux! n...@li.nux.ro wrote: Yeah, I was thinking of that, if it works for DATA, it should work for ROOT. But I am not a dev. Thoughts? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org Sent: Friday, 28 November, 2014 19:57:27 Subject: Re: root resize support in the UI For root disks, is it possible to just follow the existing resize pattern we have established in the UI for data disks? On Friday, November 28, 2014, Nux! n...@li.nux.ro wrote: Hello, Wonder if someone can help me with the $subject. I remember at some point (4.2?) a new feature showed up accidentally in the UI instance creation dialogues, it was concerning root size, had a small box where the number in GB would be introduced. I'd like to take advantage of that now that this feature actually works, even if only in KVM. I'd love it if someone could point me to that piece of code (prolly just javascript). In addition to that, now that root resize works, can any one suggest how I might put a resize button in the Volumes section for the ROOT disks? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro -- *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*™* -- *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: root resize support in the UI
Was thinking to just patch my local installation. Devs might not go too crazy over this idea since root resize is not supported across all hypervisors (KVM only atm). But if you think this has a chance to go official, I will open an issue. Thanks, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org, Brian Federle brian.fede...@citrix.com Sent: Saturday, 29 November, 2014 00:27:14 Subject: Re: root resize support in the UI Have you logged a JIRA ticket for this? Maybe Brian or one of the GUI people could pick up on it. On Fri, Nov 28, 2014 at 4:32 PM, Nux! n...@li.nux.ro wrote: Yeah, I was thinking of that, if it works for DATA, it should work for ROOT. But I am not a dev. Thoughts? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org Sent: Friday, 28 November, 2014 19:57:27 Subject: Re: root resize support in the UI For root disks, is it possible to just follow the existing resize pattern we have established in the UI for data disks? On Friday, November 28, 2014, Nux! n...@li.nux.ro wrote: Hello, Wonder if someone can help me with the $subject. I remember at some point (4.2?) a new feature showed up accidentally in the UI instance creation dialogues, it was concerning root size, had a small box where the number in GB would be introduced. I'd like to take advantage of that now that this feature actually works, even if only in KVM. I'd love it if someone could point me to that piece of code (prolly just javascript). In addition to that, now that root resize works, can any one suggest how I might put a resize button in the Volumes section for the ROOT disks? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro -- *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*™* -- *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: ApacheCon EU videos
Thanks, so there's hope. :-) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org Sent: Saturday, 29 November, 2014 00:25:35 Subject: Re: ApacheCon EU videos I don't know about videos from ApacheCon, but they were videoing the CloudStack Collab Conf presentations. These videos typically have taken about a month or so to show up on YouTube. On Fri, Nov 28, 2014 at 4:49 PM, Nux! n...@li.nux.ro wrote: Hi, Were there videos taken of the discussions? Have they been uploaded anywhere? Would probably like to watch some of that. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro -- *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: root resize support in the UI
Well...I don't know...we kind of have features all over the place that work for one hypervisor and not for another. If we're cool with that approach, this would be just one more area where we have this kind of hypervisor-specific behavior (perhaps all hypervisors support such an action in the future). On Fri, Nov 28, 2014 at 5:41 PM, Nux! n...@li.nux.ro wrote: Was thinking to just patch my local installation. Devs might not go too crazy over this idea since root resize is not supported across all hypervisors (KVM only atm). But if you think this has a chance to go official, I will open an issue. Thanks, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org, Brian Federle brian.fede...@citrix.com Sent: Saturday, 29 November, 2014 00:27:14 Subject: Re: root resize support in the UI Have you logged a JIRA ticket for this? Maybe Brian or one of the GUI people could pick up on it. On Fri, Nov 28, 2014 at 4:32 PM, Nux! n...@li.nux.ro wrote: Yeah, I was thinking of that, if it works for DATA, it should work for ROOT. But I am not a dev. Thoughts? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org Sent: Friday, 28 November, 2014 19:57:27 Subject: Re: root resize support in the UI For root disks, is it possible to just follow the existing resize pattern we have established in the UI for data disks? On Friday, November 28, 2014, Nux! n...@li.nux.ro wrote: Hello, Wonder if someone can help me with the $subject. I remember at some point (4.2?) a new feature showed up accidentally in the UI instance creation dialogues, it was concerning root size, had a small box where the number in GB would be introduced. I'd like to take advantage of that now that this feature actually works, even if only in KVM. I'd love it if someone could point me to that piece of code (prolly just javascript). In addition to that, now that root resize works, can any one suggest how I might put a resize button in the Volumes section for the ROOT disks? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro -- *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*™* -- *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*™* -- *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: root resize support in the UI
Yes, you have a point. Opened https://issues.apache.org/jira/browse/CLOUDSTACK-7992 -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org Cc: Brian Federle brian.fede...@citrix.com Sent: Saturday, 29 November, 2014 00:48:03 Subject: Re: root resize support in the UI Well...I don't know...we kind of have features all over the place that work for one hypervisor and not for another. If we're cool with that approach, this would be just one more area where we have this kind of hypervisor-specific behavior (perhaps all hypervisors support such an action in the future). On Fri, Nov 28, 2014 at 5:41 PM, Nux! n...@li.nux.ro wrote: Was thinking to just patch my local installation. Devs might not go too crazy over this idea since root resize is not supported across all hypervisors (KVM only atm). But if you think this has a chance to go official, I will open an issue. Thanks, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org, Brian Federle brian.fede...@citrix.com Sent: Saturday, 29 November, 2014 00:27:14 Subject: Re: root resize support in the UI Have you logged a JIRA ticket for this? Maybe Brian or one of the GUI people could pick up on it. On Fri, Nov 28, 2014 at 4:32 PM, Nux! n...@li.nux.ro wrote: Yeah, I was thinking of that, if it works for DATA, it should work for ROOT. But I am not a dev. Thoughts? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Mike Tutkowski mike.tutkow...@solidfire.com To: dev@cloudstack.apache.org Sent: Friday, 28 November, 2014 19:57:27 Subject: Re: root resize support in the UI For root disks, is it possible to just follow the existing resize pattern we have established in the UI for data disks? On Friday, November 28, 2014, Nux! n...@li.nux.ro wrote: Hello, Wonder if someone can help me with the $subject. I remember at some point (4.2?) a new feature showed up accidentally in the UI instance creation dialogues, it was concerning root size, had a small box where the number in GB would be introduced. I'd like to take advantage of that now that this feature actually works, even if only in KVM. I'd love it if someone could point me to that piece of code (prolly just javascript). In addition to that, now that root resize works, can any one suggest how I might put a resize button in the Volumes section for the ROOT disks? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro -- *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*™* -- *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*™* -- *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*™*
