Review Request 26866: VM Snapshot - Support only for vm revert cases that will not result in VM state change
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26866/ --- Review request for cloudstack, anthony xu and Devdeep Singh. Bugs: CLOUDSTACK-7747 https://issues.apache.org/jira/browse/CLOUDSTACK-7747 Repository: cloudstack-git Description --- Currently we extend support for all the possible combinations .In cases were the Vm start changes from “Stopped” to “Running”, CS does not account for this VM’s capacity and VM start does not use our allocators. Following will be the only configuration we would have to support: 1.Revert a Running VM to a Disk and Memory Snapshot ( with and without quiesce option). 2.Revert a Stopped VM to a Disk Snapshot ( with and without quiesce option). Diffs - server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.java f85f6c8 Diff: https://reviews.apache.org/r/26866/diff/ Testing --- tested that VM snapshot revert not allowed for running VM to disk type VM snapshot and stopped VM to disk and memory type snapshot. Thanks, Anshul Gangwar
Primary Storage Allocated issue
Hello CloudStack community,
Could you please take a look to following issue. The similar was described it
that topic http://comments.gmane.org/gmane.comp.apache.cloudstack.user/13848
but looks like wasn't resolved.
In my environment I have:
CloudStack v. 4.2.1
VMware v. 5.1
Recently I have found that CloudStack UI provide following information for SATA
storage:
Disk Total 5.00 TB
Disk Allocated7.26 TB
I have looked to VMware side and found absolutely different data:
Capacity:5.00 TB
Provisioned Space:4.27 TB
As you can see CloudStack show allocated disk space on 3 TB more.
My Global Settings that could be helpful for investigation:
storage.overprovisioning.factor = 4
storage.cleanup.enabled = true
storage.cleanup.interval = 86400
storage.stats.interval = 6
capacity.check.period = 6
expunge.delay=60
expunge.interval=86400
expunge.workers=10
I have looked to CloudStack database and found that some Volumes state in
'Destroy' but also I have found a lot of in 'Expunged':
mysql select v.state, sum(v.size) from volumes v, vm_instance vm,
vm_root_disk_tags d where v.instance_id=vm.id and d.vm_id=vm.id and
d.root_disk_tag like 'sata' group by v.state;
+---+---+
| state | sum(v.size) |
+---+---+
| Destroy | 664646189056 |
| Expunged | 526388544 |
| Expunging |2147483648 |
| Ready | 3833258311680 |
+---+---+
4 rows in set (0.00 sec)
And a lot of VMs that have state=Expunged (in volume table) still present in
VMware and on storage. For example all these VMs still present in VMware:
mysql select vm.name,vm.instance_name,vm.state AS VM_state,v.id,v.size,v.state
AS VOLUME_state,v.removed,d.root_disk_tag from volumes v, vm_instance vm,
vm_root_disk_tags d where v.instance_id=vm.id and d.vm_id=vm.id and v.state
like 'Expunged' and d.root_disk_tag like 'sata'; (Names have been changed)
+--+---+---+---+--+--+-+---+
| name | instance_name |VM_state |id |size
| VOLUME_state | removed | root_disk_tag |
+--+---+---+---+--+--+-+---+
| name1| i-43-2147-VM | Expunging | 2195 | 53687091200 | Expunged
| 2014-10-16 08:12:04 | sata |
| name2| i-17-2123-VM | Expunging | 2173 | 10737418240 | Expunged
| 2014-10-15 19:14:30 | sata |
| name3| i-43-2052-VM | Expunging | 2098 | 10737418240 | Expunged
| 2014-10-07 11:57:49 | sata |
| name4| i-191-1954-VM | Expunging | 2000 | 42949672960 | Expunged
| 2014-10-01 15:15:04 | sata |
| name5| i-132-1966-VM | Expunging | 2012 | 21474836480 | Expunged
| 2014-09-29 20:33:12 | sata |
| name6| i-132-1967-VM | Expunging | 2013 | 21474836480 | Expunged
| 2014-09-29 20:33:12 | sata |
| name7| i-132-1962-VM | Expunging | 2008 | 10737418240 | Expunged
| 2014-09-29 20:33:11 | sata |
| name8| i-132-1964-VM | Expunging | 2010 | 10737418240 | Expunged
| 2014-09-29 20:33:11 | sata |
Not all VMs with 'Expunged' state still present in VMware but a lot of from
them still weren't removed!
mysql select
id,uuid,name,status,capacity_bytes,capacity_iops,tag,disk_used_capacity,disk_reserved_capacity
from storage_pool_view;
++--+---+-++---+--+++
| id | uuid
| name | status | capacity_bytes | capacity_iops | tag |
disk_used_capacity | disk_reserved_capacity |
++--+---+-++---+--+++
| 2 | 096b3b6e-481d-33b4-9b34-7178612a2535 | SATA | Up |
5497289703424 | NULL | sata | 7913594810761 |
0 |
++--+---+-++---+--+++
5 rows in set (0.02 sec)
Also I have found that Expunged volumes have 'chain_info' field:
mysql select name,removed,state,chain_info from volumes where id=2112 \G
*** 1. row ***
name: ROOT-2066
removed: 2014-10-09 11:57:52
state: Expunged
chain_info: {diskDeviceBusName:scsi0:0,diskChain:[[SATA1]
i-238-2066-VM/ROOT-2066.vmdk]}
1 row in set (0.00 sec)
BUT Destroyed VMs don't have it:
mysql select name,removed,state,chain_info
Re: master broken
I repaired master by reinserting most of Franks work. works on my laptop :s The merge exercise was not flawless but I still want to repeat it today. I saw double commits again but those should be coming in without problem as empty commits. I will certainly make sure travis-ci passes before pushing. On Thu, Oct 16, 2014 at 11:43 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: On Thu, Oct 16, 2014 at 11:37 PM, Frank Zhang frank.zh...@citrix.com wrote: Do you know what part of baremetal causes the issue? No it is due to the merge back of the 4.5 branch I built master on Wed and didn't see any issue. I will give it a try right now. I probably resolved some conflict the wrong way. I cannot find BaremetalProvisionDoneNotificationCmd in any of the commits. But this is only one of problems I think. -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: Thursday, October 16, 2014 2:28 PM To: dev; Frank Zhang Subject: Re: master broken I can't seem to get it working by reverting, neither the merge commit nor individual related commits. @Frank: can we disable baremetal all together until you are done? On Thu, Oct 16, 2014 at 9:43 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: I found some culprits, it is in partly reverted code that was committed before the cut of master and 4.5. All to do with Baremetal. I am having a look. On Thu, Oct 16, 2014 at 8:54 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: On Thu, Oct 16, 2014 at 8:17 PM, Marcus shadow...@gmail.com wrote: I mean as they are ordered in the log. The commits before and after the merge are both working points. We are talking about a merge of master and 4.5, so I am now trying 4.5 to see if the errors are in there as well. If they are I will fix there and merge forward. If not I will revert and morn. -- Daan -- Daan -- Daan -- Daan -- Daan
Review Request 26868: CLOUDSTACK-7728: Adding steps to existing test case to identify product issue
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26868/ --- Review request for cloudstack, Jayapal Reddy and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7728 https://issues.apache.org/jira/browse/CLOUDSTACK-7728 Repository: cloudstack-git Description --- Adding steps to verify a recently fixed product issue. Steps already present: 1. Create isolated network with egress policy allow 2. Deploy VM in network 3. Check egress traffic from VM, it should be allowed Steps added: Reboot router and then verify egress traffic. Egress traffic should still be allowed. Diffs - test/integration/component/test_egress_fw_rules.py 12bade4 Diff: https://reviews.apache.org/r/26868/diff/ Testing --- Not tested. Thanks, Gaurav Aradhye
Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316
Hi, On 16-Oct-2014, at 6:57 pm, Daan Hoogland daan.hoogl...@gmail.com wrote: The trick part is that it is a hot upgrade. A helper table especially for sysvm upgrades could do the trick. This could be a generic upgrade function for anytoany version: check the table - if non processed entries update the sysvm templates - mark the entries as processed. A process that would run on any upgrade. We could add a check in the Upgradextoy to ensure if sysvm upgrade are needed that entries are added. sorry if I cut corners in my rant. I don't think this will be in 4.4.1 If we go with this, then in case anyone wants to upgrade from 4.3.1 to say 4.5.0; they would require to upload a 4.4.0 template so that the upgrade path 440to441 won’t break for them. This would be unnecessary for such an upgrade in future from any version before 4.4.1 to any version after it. If possible if we should fix this. Sorry I don’t have a concrete solution as I don’ t know why we are upgrading systemvm template in the db upgrade path (any background/context would be great). Thanks. 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 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.
merged again
H, I just did a merge as follows: \\ebi\daan:~/cloudstack-4.5/cloudstack (master) git merge --no-commit --stat --verbose --progress --strategy ours 4.5 Automatic merge went well; stopped before committing as requested \\ebi\daan:~/cloudstack-4.5/cloudstack (master|MERGING) git diff \\ebi\daan:~/cloudstack-4.5/cloudstack (master|MERGING) git commit [master 48f0b7b] Merge branch '4.5' As it didn't result in anything I won't push. I will repeat this practice over the coming days so ask of all to only put fixes in 4.5 (and earlier branches). Some have been applying the same patch to both 4.5 and master. This is not needed with the above approach and the payoff is that there is a link in the git metadata showing that the exact same patch is in both branches. I cannot tell for sure how merge-back of features in master and conflict resolution of that is going to be. Hopefully it won't be as bad as last nights efforts. -- Daan
Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316
You guys need to econimize on your mail signatures... On Fri, Oct 17, 2014 at 11:37 AM, Rohit Yadav rohit.ya...@shapeblue.com wrote: Hi, On 16-Oct-2014, at 6:57 pm, Daan Hoogland daan.hoogl...@gmail.com wrote: The trick part is that it is a hot upgrade. A helper table especially for sysvm upgrades could do the trick. This could be a generic upgrade function for anytoany version: check the table - if non processed entries update the sysvm templates - mark the entries as processed. A process that would run on any upgrade. We could add a check in the Upgradextoy to ensure if sysvm upgrade are needed that entries are added. sorry if I cut corners in my rant. I don't think this will be in 4.4.1 If we go with this, then in case anyone wants to upgrade from 4.3.1 to say 4.5.0; they would require to upload a 4.4.0 template so that the upgrade path 440to441 won’t break for them. This would be unnecessary for such an upgrade in future from any version before 4.4.1 to any version after it. If possible if we should fix this. I don't think an upgrade from 4.4.0 or earlier should have to pass along 4.4.1. We can change that path. This solution isn't structural of course. Sorry I don’t have a concrete solution as I don’ t know why we are upgrading systemvm template in the db upgrade path (any background/context would be great). Thanks. Me neither. My take is that it due to lack of an api command to do so.
Review Request 26493: CLOUDSTACK-7692: Fixed template register issue in test_project_usage.py
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26493/ --- Review request for cloudstack and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7692 https://issues.apache.org/jira/browse/CLOUDSTACK-7692 Repository: cloudstack-git Description --- Template needs to be registered with api client of project owner account. Diffs - test/integration/component/test_project_usage.py 3262e40 Diff: https://reviews.apache.org/r/26493/diff/ Testing --- Tested for syntax and import errors. Thanks, Gaurav Aradhye
Review Request 26492: CLOUDSTACK-7691: Fixed 'Exception not raised' issue in test_project_limits.py
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26492/ --- Review request for cloudstack and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7691 https://issues.apache.org/jira/browse/CLOUDSTACK-7691 Repository: cloudstack-git Description --- Reason of failure: The test case is failing while checking the template limits of the project because the template is not registered with the api client of the project owner account and it is registered with api client of the root admin account. Changes: 1. Registered template with correct account 2. Removed import * and included specific imports Diffs - test/integration/component/test_project_limits.py 5f33ad8 Diff: https://reviews.apache.org/r/26492/diff/ Testing --- Tested for syntax and import errors. Thanks, Gaurav Aradhye
Review Request 26439: CLOUDSTACK-7684: Fixed Exception not raised issue in secondary storage limits test suite test_ss_max_limits.py
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26439/ --- Review request for cloudstack and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7684 https://issues.apache.org/jira/browse/CLOUDSTACK-7684 Repository: cloudstack-git Description --- Test case failed because api client of project owner account is not used (Instead of root admin api client). Diffs - test/integration/component/test_ss_max_limits.py ba886e8 Diff: https://reviews.apache.org/r/26439/diff/ Testing --- Tested for syntax and import errors. Thanks, Gaurav Aradhye
Review Request 26438: CLOUDSTACK-7682: Fixed usage event issue. Used api client of account for which we are checking the usage
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26438/ --- Review request for cloudstack and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7682 https://issues.apache.org/jira/browse/CLOUDSTACK-7682 Repository: cloudstack-git Description --- The events TEMPLATE.CREATE and TEMPLATE.DELETE does not exist in usage event table against that particular account because the template is not created using the api client of the account and hence the template belongs to the root admin account. Changes: Use the api client of the account against which we are checking the usage while creating and deleting the template. Have not addressed the pep8 issues already present in the file because that will mask the changes to fix the issue. I will be happy to add a separate patch for it if required. Considering that many files need pep8 fixes, a separate task for this should be created and addressed. Diffs - test/integration/component/test_usage.py 81cce48 Diff: https://reviews.apache.org/r/26438/diff/ Testing --- Tested for syntax and import errors. Thanks, Gaurav Aradhye
Re: Using Cloudstack API from PHP issue
He says his code does the same as the other PHP libs, decided to research how come cloudmonkey never fails. I am hopeful. :) Thanks, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: David Nalley da...@gnsa.us To: dev@cloudstack.apache.org Sent: Friday, 17 October, 2014 00:43:47 Subject: Re: Using Cloudstack API from PHP issue You might also look at the various CloudStack PHP libraries on github. There are several of them there, that are known to work . --David On Wed, Oct 15, 2014 at 2:58 PM, Prachi Damle prachi.da...@citrix.com wrote: Here are the steps documented to sign an API request for CloudStack: https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.2/html/API_Developers_Guide/signing-api-requests.html I guess, you need to add sorting of query parameters. Prachi -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Wednesday, October 15, 2014 7:22 AM To: dev Subject: Using Cloudstack API from PHP issue Hi, A PHP developer colleague is trying to make some calls to the ACS API; some work (like deploy virtualmachine), but some fail, like authorize securitygroup: 401 unable to verify user credentials and/or request signature This is his code for generating the signature, is there anything obviously wrong with it? http://fpaste.org/142102/33827661/raw/ Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
[ANNOUNCE] New PMC Member: Rajani Karuturi
The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
Re: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congrats Rajani! On 17-Oct-2014, at 3:51 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
Re: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congrats Rajani! On 17-Oct-2014, at 3:51 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
Re: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congratulations Rajani :) -Harikrishna On 17-Oct-2014, at 3:59 pm, Koushik Das koushik@citrix.com wrote: Congrats Rajani! On 17-Oct-2014, at 3:51 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
RE: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congrats Rajani. Regards, Devdeep -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: Friday, October 17, 2014 3:52 PM To: dev Subject: [ANNOUNCE] New PMC Member: Rajani Karuturi The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
Re: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congrats Rajani! I guess we’ll have more binding votes on important proposals now :) On 17-Oct-2014, at 3:51 pm, Daan Hoogland daan.hoogl...@gmail.com wrote: The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan 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 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: [ANNOUNCE] New PMC Member: Rajani Karuturi
congrats rajani From: Devdeep Singh [devdeep.si...@citrix.com] Sent: Friday, October 17, 2014 4:18 PM To: dev@cloudstack.apache.org Subject: RE: [ANNOUNCE] New PMC Member: Rajani Karuturi Congrats Rajani. Regards, Devdeep -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: Friday, October 17, 2014 3:52 PM To: dev Subject: [ANNOUNCE] New PMC Member: Rajani Karuturi The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
Re: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congratulations, Rajani :-) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Daan Hoogland daan.hoogl...@gmail.com To: dev dev@cloudstack.apache.org Sent: Friday, 17 October, 2014 11:21:33 Subject: [ANNOUNCE] New PMC Member: Rajani Karuturi The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316
Hi Rohit, The doc in /latest is not the 4.4.1 latest, the correct documentation is in /4.4.1 it should have been corrected for the behavior describe and also contain correct url for sysvm ( not jenkins.bac.o). Once the 4.4.1 is released ill change the defaut url and update issues lists in the RN. Le jeudi 16 octobre 2014, Rohit Yadav rohit.ya...@shapeblue.com a écrit : Hi, -0 Upgraded from 4.3.1 to 4.4.1, following the docs ( http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgrade-4.3.html) it worked and usual VM lifecycle (create, start, stop, reboot etc), networking etc in basic zone. The issue is that, the upgrade docs ask you to pre-register/install a 4.4.0 template before we upgrade to 4.4.x which works. But if I upgraded from 4.3.1 using a 4.4.1 template the upgrade path 4.4.0-4.4.1 fails because in Upgrade440to441 in updateSystemVmTemplates() we are using hardcoded checksums as the 4.4.1 templates I used from jenkins.b.o had different checksums which resulted in failure of the DB migration and CloudStack mgmt server got stuck. To summarize; - Hardcoded systemvm template names in Upgrade440to441 :: updateSystemVmTemplates - Harcoded checksums and restricted to 4.4.0 templates in Upgrade440to441; if someone upgrades from pre-4.4.0 should we allow them to use latest 4.4.1 templates? I understand this is tricky as 4.4.1 is not released yet should we find a way we can not hardcode this? Repo: http://packages.bhaisaab.org/cloudstack/main/debian/4.4/ http://packages.bhaisaab.org/cloudstack/main/centos/ Lastly, I tested and found that the previous Cluster settings UI/API blocker issue is not seen anymore (reported by Geoff and Pierre in previous voting round). On 15-Oct-2014, at 2:53 am, Daan Hoogland daan.hoogl...@gmail.com javascript:; wrote: Hi All, As all open blocking issues were reported fixed today, I've created a 4.4.1 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-RC20141014T2316 Commit: 8db506b536f3139250d33df571c98c1c3fa83650 List of changes: http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/ Source release (checksums and signatures are available at the same location): https://dist.apache.org/repos/dist/dev/cloudstack/4.4.1/ 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 [ ] +0 no opinion [ ] -1 disapprove (and reason why) may for(tun/c)e be with us, -- Daan Regards, Rohit Yadav Software Architect, ShapeBlue M. +91 88 262 30892 | rohit.ya...@shapeblue.com javascript:; 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. -- *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_
Re: [ANNOUNCE] New PMC Member: Rajani Karuturi
On Fri, Oct 17, 2014 at 12:21 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. Congratulations! -- Erik
Re: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congrat Rajani! Le vendredi 17 octobre 2014, Nux! n...@li.nux.ro a écrit : Congratulations, Rajani :-) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Daan Hoogland daan.hoogl...@gmail.com javascript:; To: dev dev@cloudstack.apache.org javascript:; Sent: Friday, 17 October, 2014 11:21:33 Subject: [ANNOUNCE] New PMC Member: Rajani Karuturi The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan -- *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_
RE: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congratulations, Rajani!! Thanks, Vaibhav -Original Message- From: Suresh Sadhu [mailto:suresh.sa...@citrix.com] Sent: 17 October 2014 16:28 To: dev@cloudstack.apache.org Subject: RE: [ANNOUNCE] New PMC Member: Rajani Karuturi congrats rajani From: Devdeep Singh [devdeep.si...@citrix.com] Sent: Friday, October 17, 2014 4:18 PM To: dev@cloudstack.apache.org Subject: RE: [ANNOUNCE] New PMC Member: Rajani Karuturi Congrats Rajani. Regards, Devdeep -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: Friday, October 17, 2014 3:52 PM To: dev Subject: [ANNOUNCE] New PMC Member: Rajani Karuturi The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
RE: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congrats Rajani. -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: 17 October 2014 15:52 To: dev Subject: [ANNOUNCE] New PMC Member: Rajani Karuturi The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- Daan
Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316
Hi Pierre, On 17-Oct-2014, at 4:42 pm, Pierre-Luc Dion pd...@cloudops.com wrote: Hi Rohit, The doc in /latest is not the 4.4.1 latest, the correct documentation is in /4.4.1 it should have been corrected for the behavior describe and also contain correct url for sysvm ( not jenkins.bac.o). Once the 4.4.1 is released ill change the defaut url and update issues lists in the RN. Thanks, that would be much needed. The issue is not that docs have those links, but that the Java class (440to441, the upgrade path) that upgrades CloudStack db has hard coded URL and MD5 checksums of 4.4.0 template. The real issue is when a user tries to upgrade from any prior version of CloudStack to 4.4.1 or later version, they would be required to register a 4.4.0-6 template (from Wido’s repo) before the upgrade which is something they skip or forget to do it which would result in messed up upgraded DB. For example, if I’m on 4.2.1 and I want to upgrade to 4.4.1 or later (say 4.5.0 in future) if I don’t follow the docs (i.e. register 4.4.0-06 template, that too not any 4.4.0 template, but the specific one from Wido’s repo or some other url) my upgrade will fail. 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 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.
Review Request 26871: CLOUDSTACK-7748: Cloudstack version number is missing in system vm template.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/ --- Review request for cloudstack and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7748 https://issues.apache.org/jira/browse/CLOUDSTACK-7748 Repository: cloudstack-git Description --- CLOUDSTACK-7748: Cloudstack version number is missing in system vm template. /etc/cloudstack-release in system vm does not have version number which leads in vm deployment failure while checking router version Diffs - tools/appliance/build.sh 8bf78b1 Diff: https://reviews.apache.org/r/26871/diff/ Testing --- Thanks, Harikrishna Patnala
Re: Primary Storage Allocated issue
Hi Denis, I think, it should be calculated disk size also from 'Expunged' volumes. Try to update expunge.interval in cloudstack global settings. There is no need to push manually to remove expunged volumes. Thank You. Gopalakrishnan.S Cloud Consultant. - Original Message - From: Denis Finko denis.fi...@ecommerce.com To: dev@cloudstack.apache.org; us...@cloudstack.apache.org Sent: Friday, October 17, 2014 1:47 PM Subject: Primary Storage Allocated issue Hello CloudStack community, Could you please take a look to following issue. The similar was described it that topic http://comments.gmane.org/gmane.comp.apache.cloudstack.user/13848 but looks like wasn't resolved. In my environment I have: CloudStack v. 4.2.1 VMware v. 5.1 Recently I have found that CloudStack UI provide following information for SATA storage: Disk Total 5.00 TB Disk Allocated7.26 TB I have looked to VMware side and found absolutely different data: Capacity:5.00 TB Provisioned Space:4.27 TB As you can see CloudStack show allocated disk space on 3 TB more. My Global Settings that could be helpful for investigation: storage.overprovisioning.factor = 4 storage.cleanup.enabled = true storage.cleanup.interval = 86400 storage.stats.interval = 6 capacity.check.period = 6 expunge.delay=60 expunge.interval=86400 expunge.workers=10 I have looked to CloudStack database and found that some Volumes state in 'Destroy' but also I have found a lot of in 'Expunged': mysql select v.state, sum(v.size) from volumes v, vm_instance vm, vm_root_disk_tags d where v.instance_id=vm.id and d.vm_id=vm.id and d.root_disk_tag like 'sata' group by v.state; +---+---+ | state | sum(v.size) | +---+---+ | Destroy | 664646189056 | | Expunged | 526388544 | | Expunging |2147483648 | | Ready | 3833258311680 | +---+---+ 4 rows in set (0.00 sec) And a lot of VMs that have state=Expunged (in volume table) still present in VMware and on storage. For example all these VMs still present in VMware: mysql select vm.name,vm.instance_name,vm.state AS VM_state,v.id,v.size,v.state AS VOLUME_state,v.removed,d.root_disk_tag from volumes v, vm_instance vm, vm_root_disk_tags d where v.instance_id=vm.id and d.vm_id=vm.id and v.state like 'Expunged' and d.root_disk_tag like 'sata'; (Names have been changed) +--+---+---+---+--+--+-+---+ | name | instance_name |VM_state |id |size | VOLUME_state | removed | root_disk_tag | +--+---+---+---+--+--+-+---+ | name1| i-43-2147-VM | Expunging | 2195 | 53687091200 | Expunged | 2014-10-16 08:12:04 | sata | | name2| i-17-2123-VM | Expunging | 2173 | 10737418240 | Expunged | 2014-10-15 19:14:30 | sata | | name3| i-43-2052-VM | Expunging | 2098 | 10737418240 | Expunged | 2014-10-07 11:57:49 | sata | | name4| i-191-1954-VM | Expunging | 2000 | 42949672960 | Expunged | 2014-10-01 15:15:04 | sata | | name5| i-132-1966-VM | Expunging | 2012 | 21474836480 | Expunged | 2014-09-29 20:33:12 | sata | | name6| i-132-1967-VM | Expunging | 2013 | 21474836480 | Expunged | 2014-09-29 20:33:12 | sata | | name7| i-132-1962-VM | Expunging | 2008 | 10737418240 | Expunged | 2014-09-29 20:33:11 | sata | | name8| i-132-1964-VM | Expunging | 2010 | 10737418240 | Expunged | 2014-09-29 20:33:11 | sata | Not all VMs with 'Expunged' state still present in VMware but a lot of from them still weren't removed! mysql select id,uuid,name,status,capacity_bytes,capacity_iops,tag,disk_used_capacity,disk_reserved_capacity from storage_pool_view; ++--+---+-++---+--+++ | id | uuid | name | status | capacity_bytes | capacity_iops | tag | disk_used_capacity | disk_reserved_capacity | ++--+---+-++---+--+++ | 2 | 096b3b6e-481d-33b4-9b34-7178612a2535 | SATA | Up | 5497289703424 | NULL | sata | 7913594810761 | 0 | ++--+---+-++---+--+++ 5 rows in set (0.02 sec) Also I have found that Expunged volumes have 'chain_info' field: mysql select
Re: Primary Storage Allocated issue
GopalaKrishnan, I am appreciate you for quick reply! But unfortunately expunge.interval is not helpful. I have several time updated it recently and it wasn't removed old VMs from VMware. Currently I have: expunge.interval = 86400 There is no need to push manually to remove expunged volumes. Yes, I am agree with you that it's supposed to be. But unfortunately I still have a lot of volumes in 'Expunged' state and don't know how correctly remove them from CloudStack side. It looks like a bug in CloudStack. On 10/17/2014 01:35 PM, GopalaKrishnan wrote: Hi Denis, I think, it should be calculated disk size also from 'Expunged' volumes. Try to update expunge.interval in cloudstack global settings. There is no need to push manually to remove expunged volumes. Thank You. Gopalakrishnan.S Cloud Consultant. - Original Message - From: Denis Finko denis.fi...@ecommerce.com To: dev@cloudstack.apache.org; us...@cloudstack.apache.org Sent: Friday, October 17, 2014 1:47 PM Subject: Primary Storage Allocated issue Hello CloudStack community, Could you please take a look to following issue. The similar was described it that topic http://comments.gmane.org/gmane.comp.apache.cloudstack.user/13848 but looks like wasn't resolved. In my environment I have: CloudStack v. 4.2.1 VMware v. 5.1 Recently I have found that CloudStack UI provide following information for SATA storage: Disk Total 5.00 TB Disk Allocated7.26 TB I have looked to VMware side and found absolutely different data: Capacity:5.00 TB Provisioned Space:4.27 TB As you can see CloudStack show allocated disk space on 3 TB more. My Global Settings that could be helpful for investigation: storage.overprovisioning.factor = 4 storage.cleanup.enabled = true storage.cleanup.interval = 86400 storage.stats.interval = 6 capacity.check.period = 6 expunge.delay=60 expunge.interval=86400 expunge.workers=10 I have looked to CloudStack database and found that some Volumes state in 'Destroy' but also I have found a lot of in 'Expunged': mysql select v.state, sum(v.size) from volumes v, vm_instance vm, vm_root_disk_tags d where v.instance_id=vm.id and d.vm_id=vm.id and d.root_disk_tag like 'sata' group by v.state; +---+---+ | state | sum(v.size) | +---+---+ | Destroy | 664646189056 | | Expunged | 526388544 | | Expunging |2147483648 | | Ready | 3833258311680 | +---+---+ 4 rows in set (0.00 sec) And a lot of VMs that have state=Expunged (in volume table) still present in VMware and on storage. For example all these VMs still present in VMware: mysql select vm.name,vm.instance_name,vm.state AS VM_state,v.id,v.size,v.state AS VOLUME_state,v.removed,d.root_disk_tag from volumes v, vm_instance vm, vm_root_disk_tags d where v.instance_id=vm.id and d.vm_id=vm.id and v.state like 'Expunged' and d.root_disk_tag like 'sata'; (Names have been changed) +--+---+---+---+--+--+-+---+ | name | instance_name |VM_state |id |size | VOLUME_state | removed | root_disk_tag | +--+---+---+---+--+--+-+---+ | name1| i-43-2147-VM | Expunging | 2195 | 53687091200 | Expunged | 2014-10-16 08:12:04 | sata | | name2| i-17-2123-VM | Expunging | 2173 | 10737418240 | Expunged | 2014-10-15 19:14:30 | sata | | name3| i-43-2052-VM | Expunging | 2098 | 10737418240 | Expunged | 2014-10-07 11:57:49 | sata | | name4| i-191-1954-VM | Expunging | 2000 | 42949672960 | Expunged | 2014-10-01 15:15:04 | sata | | name5| i-132-1966-VM | Expunging | 2012 | 21474836480 | Expunged | 2014-09-29 20:33:12 | sata | | name6| i-132-1967-VM | Expunging | 2013 | 21474836480 | Expunged | 2014-09-29 20:33:12 | sata | | name7| i-132-1962-VM | Expunging | 2008 | 10737418240 | Expunged | 2014-09-29 20:33:11 | sata | | name8| i-132-1964-VM | Expunging | 2010 | 10737418240 | Expunged | 2014-09-29 20:33:11 | sata | Not all VMs with 'Expunged' state still present in VMware but a lot of from them still weren't removed! mysql select id,uuid,name,status,capacity_bytes,capacity_iops,tag,disk_used_capacity,disk_reserved_capacity from storage_pool_view; ++--+---+-++---+--+++ | id | uuid | name | status | capacity_bytes | capacity_iops | tag | disk_used_capacity |
Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316
Hi Rohit, I'm aware of this behavior, it start with 4.3.0, if you upgrade to 4.3.0 or 4.3.1 without having the new systemvm prior the upgrade, the db upgrade will fail. which is why upgrading from 4.2.x to 4.4.1 require 2 new systemvm to be install prior the upgrade. Further more, if you have multiple hypervisor type, let say you have XenServer and KVM clusters but forced system vm to run on xenserver only. by default you might only install the new sysvmtemplate for xenserver, but, if you upgrade without having install the kvm systemvm version the db upgrade will fail. I think their is jira issue around this already. On Fri, Oct 17, 2014 at 7:36 AM, Rohit Yadav rohit.ya...@shapeblue.com wrote: Hi Pierre, On 17-Oct-2014, at 4:42 pm, Pierre-Luc Dion pd...@cloudops.com wrote: Hi Rohit, The doc in /latest is not the 4.4.1 latest, the correct documentation is in /4.4.1 it should have been corrected for the behavior describe and also contain correct url for sysvm ( not jenkins.bac.o). Once the 4.4.1 is released ill change the defaut url and update issues lists in the RN. Thanks, that would be much needed. The issue is not that docs have those links, but that the Java class (440to441, the upgrade path) that upgrades CloudStack db has hard coded URL and MD5 checksums of 4.4.0 template. The real issue is when a user tries to upgrade from any prior version of CloudStack to 4.4.1 or later version, they would be required to register a 4.4.0-6 template (from Wido’s repo) before the upgrade which is something they skip or forget to do it which would result in messed up upgraded DB. For example, if I’m on 4.2.1 and I want to upgrade to 4.4.1 or later (say 4.5.0 in future) if I don’t follow the docs (i.e. register 4.4.0-06 template, that too not any 4.4.0 template, but the specific one from Wido’s repo or some other url) my upgrade will fail. 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 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.
Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316
CLOUDSTACK-7365 https://issues.apache.org/jira/browse/CLOUDSTACK-7365 was created by you Pierre-Luc. I am looking into the other side of the medal. have a generic systemvm upgrade api. It is related and I haven't found a ticket yet. On Fri, Oct 17, 2014 at 2:43 PM, Pierre-Luc Dion pdion...@apache.org wrote: Hi Rohit, I'm aware of this behavior, it start with 4.3.0, if you upgrade to 4.3.0 or 4.3.1 without having the new systemvm prior the upgrade, the db upgrade will fail. which is why upgrading from 4.2.x to 4.4.1 require 2 new systemvm to be install prior the upgrade. Further more, if you have multiple hypervisor type, let say you have XenServer and KVM clusters but forced system vm to run on xenserver only. by default you might only install the new sysvmtemplate for xenserver, but, if you upgrade without having install the kvm systemvm version the db upgrade will fail. I think their is jira issue around this already. On Fri, Oct 17, 2014 at 7:36 AM, Rohit Yadav rohit.ya...@shapeblue.com wrote: Hi Pierre, On 17-Oct-2014, at 4:42 pm, Pierre-Luc Dion pd...@cloudops.com wrote: Hi Rohit, The doc in /latest is not the 4.4.1 latest, the correct documentation is in /4.4.1 it should have been corrected for the behavior describe and also contain correct url for sysvm ( not jenkins.bac.o). Once the 4.4.1 is released ill change the defaut url and update issues lists in the RN. Thanks, that would be much needed. The issue is not that docs have those links, but that the Java class (440to441, the upgrade path) that upgrades CloudStack db has hard coded URL and MD5 checksums of 4.4.0 template. The real issue is when a user tries to upgrade from any prior version of CloudStack to 4.4.1 or later version, they would be required to register a 4.4.0-6 template (from Wido’s repo) before the upgrade which is something they skip or forget to do it which would result in messed up upgraded DB. For example, if I’m on 4.2.1 and I want to upgrade to 4.4.1 or later (say 4.5.0 in future) if I don’t follow the docs (i.e. register 4.4.0-06 template, that too not any 4.4.0 template, but the specific one from Wido’s repo or some other url) my upgrade will fail. 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 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: [ANNOUNCE] New PMC Member: Rajani Karuturi
Congratulations! On Friday, October 17, 2014, Daan Hoogland daan.hoogl...@gmail.com wrote: The Project Management Committee (PMC) for Apache CloudStack are pleased to announce that Rajani Karuturi has accepted our invitation to join the PMC. Please join me in congratulating her. On behalf of the Apache CloudStack PMC -- 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: Review Request 26866: VM Snapshot - Support only for vm revert cases that will not result in VM state change
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26866/#review57165 --- Ship it! Ship It! - anthony xu On Oct. 17, 2014, 7:46 a.m., Anshul Gangwar wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26866/ --- (Updated Oct. 17, 2014, 7:46 a.m.) Review request for cloudstack, anthony xu and Devdeep Singh. Bugs: CLOUDSTACK-7747 https://issues.apache.org/jira/browse/CLOUDSTACK-7747 Repository: cloudstack-git Description --- Currently we extend support for all the possible combinations .In cases were the Vm start changes from “Stopped” to “Running”, CS does not account for this VM’s capacity and VM start does not use our allocators. Following will be the only configuration we would have to support: 1.Revert a Running VM to a Disk and Memory Snapshot ( with and without quiesce option). 2.Revert a Stopped VM to a Disk Snapshot ( with and without quiesce option). Diffs - server/src/com/cloud/vm/snapshot/VMSnapshotManagerImpl.java f85f6c8 Diff: https://reviews.apache.org/r/26866/diff/ Testing --- tested that VM snapshot revert not allowed for running VM to disk type VM snapshot and stopped VM to disk and memory type snapshot. Thanks, Anshul Gangwar
Re: Review Request 26871: CLOUDSTACK-7748: Cloudstack version number is missing in system vm template.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/ --- (Updated Oct. 17, 2014, 5:22 p.m.) Review request for cloudstack, Kishan Kavala and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7748 https://issues.apache.org/jira/browse/CLOUDSTACK-7748 Repository: cloudstack-git Description --- CLOUDSTACK-7748: Cloudstack version number is missing in system vm template. /etc/cloudstack-release in system vm does not have version number which leads in vm deployment failure while checking router version Diffs - tools/appliance/build.sh 8bf78b1 Diff: https://reviews.apache.org/r/26871/diff/ Testing --- Thanks, Harikrishna Patnala
Re: master broken
YAY On Fri, Oct 17, 2014 at 2:31 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: I repaired master by reinserting most of Franks work. works on my laptop :s The merge exercise was not flawless but I still want to repeat it today. I saw double commits again but those should be coming in without problem as empty commits. I will certainly make sure travis-ci passes before pushing. On Thu, Oct 16, 2014 at 11:43 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: On Thu, Oct 16, 2014 at 11:37 PM, Frank Zhang frank.zh...@citrix.com wrote: Do you know what part of baremetal causes the issue? No it is due to the merge back of the 4.5 branch I built master on Wed and didn't see any issue. I will give it a try right now. I probably resolved some conflict the wrong way. I cannot find BaremetalProvisionDoneNotificationCmd in any of the commits. But this is only one of problems I think. -Original Message- From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] Sent: Thursday, October 16, 2014 2:28 PM To: dev; Frank Zhang Subject: Re: master broken I can't seem to get it working by reverting, neither the merge commit nor individual related commits. @Frank: can we disable baremetal all together until you are done? On Thu, Oct 16, 2014 at 9:43 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: I found some culprits, it is in partly reverted code that was committed before the cut of master and 4.5. All to do with Baremetal. I am having a look. On Thu, Oct 16, 2014 at 8:54 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: On Thu, Oct 16, 2014 at 8:17 PM, Marcus shadow...@gmail.com wrote: I mean as they are ordered in the log. The commits before and after the merge are both working points. We are talking about a merge of master and 4.5, so I am now trying 4.5 to see if the errors are in there as well. If they are I will fix there and merge forward. If not I will revert and morn. -- Daan -- Daan -- Daan -- Daan -- Daan
Re: Review Request 26871: CLOUDSTACK-7748: Cloudstack version number is missing in system vm template.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/ --- (Updated Oct. 17, 2014, 5:30 p.m.) Review request for cloudstack, Kishan Kavala and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7748 https://issues.apache.org/jira/browse/CLOUDSTACK-7748 Repository: cloudstack-git Description (updated) --- CLOUDSTACK-7748: Cloudstack version number is missing in system vm template. /etc/cloudstack-release in system vm does not have version number which leads in vm deployment failure while checking router version During the system vm build, arguments can be passed to build.sh script where 'version' argument is one of the optional arguments. The bug is even if version argument is not passed defalut value(CLOUDSTACK_RELEASE=4.4.0) is overridden by the null value (since argument is not passed). Diffs - tools/appliance/build.sh 8bf78b1 Diff: https://reviews.apache.org/r/26871/diff/ Testing --- Thanks, Harikrishna Patnala
Re: Review Request 26871: CLOUDSTACK-7748: Cloudstack version number is missing in system vm template.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/#review57173 --- tools/appliance/build.sh https://reviews.apache.org/r/26871/#comment97683 Why should version be optional at all ? 1. I think it should be mandatory. 2. I would like you to do a more harder check on version making sure it is in correct format as per expectations say it should be 1.0 and less than say 10.0 it should be an integer etc. - Nitin Mehta On Oct. 17, 2014, 5:30 p.m., Harikrishna Patnala wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/ --- (Updated Oct. 17, 2014, 5:30 p.m.) Review request for cloudstack, Kishan Kavala and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7748 https://issues.apache.org/jira/browse/CLOUDSTACK-7748 Repository: cloudstack-git Description --- CLOUDSTACK-7748: Cloudstack version number is missing in system vm template. /etc/cloudstack-release in system vm does not have version number which leads in vm deployment failure while checking router version During the system vm build, arguments can be passed to build.sh script where 'version' argument is one of the optional arguments. The bug is even if version argument is not passed defalut value(CLOUDSTACK_RELEASE=4.4.0) is overridden by the null value (since argument is not passed). Diffs - tools/appliance/build.sh 8bf78b1 Diff: https://reviews.apache.org/r/26871/diff/ Testing --- Thanks, Harikrishna Patnala
Re: Review Request 26871: CLOUDSTACK-7748: Cloudstack version number is missing in system vm template.
On Oct. 17, 2014, 5:41 p.m., Nitin Mehta wrote: tools/appliance/build.sh, line 253 https://reviews.apache.org/r/26871/diff/1/?file=724288#file724288line253 Why should version be optional at all ? 1. I think it should be mandatory. 2. I would like you to do a more harder check on version making sure it is in correct format as per expectations say it should be 1.0 and less than say 10.0 it should be an integer etc. Why it should be mandatory? if it has a default value. This value represents, in which version the template is released and is used to check if router upgrade is needed. I think the parameter is made optional, so that at any point of time during template build, we can make the template refer to that particular version if we want to. The current template build jobs are based on the default value. It is good to have harder check, I'll create a ticket for that. - Harikrishna --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/#review57173 --- On Oct. 17, 2014, 5:30 p.m., Harikrishna Patnala wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/ --- (Updated Oct. 17, 2014, 5:30 p.m.) Review request for cloudstack, Kishan Kavala and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7748 https://issues.apache.org/jira/browse/CLOUDSTACK-7748 Repository: cloudstack-git Description --- CLOUDSTACK-7748: Cloudstack version number is missing in system vm template. /etc/cloudstack-release in system vm does not have version number which leads in vm deployment failure while checking router version During the system vm build, arguments can be passed to build.sh script where 'version' argument is one of the optional arguments. The bug is even if version argument is not passed defalut value(CLOUDSTACK_RELEASE=4.4.0) is overridden by the null value (since argument is not passed). Diffs - tools/appliance/build.sh 8bf78b1 Diff: https://reviews.apache.org/r/26871/diff/ Testing --- Thanks, Harikrishna Patnala
Re: Review Request 26871: CLOUDSTACK-7748: Cloudstack version number is missing in system vm template.
On Oct. 17, 2014, 5:41 p.m., Nitin Mehta wrote: tools/appliance/build.sh, line 253 https://reviews.apache.org/r/26871/diff/1/?file=724288#file724288line253 Why should version be optional at all ? 1. I think it should be mandatory. 2. I would like you to do a more harder check on version making sure it is in correct format as per expectations say it should be 1.0 and less than say 10.0 it should be an integer etc. Harikrishna Patnala wrote: Why it should be mandatory? if it has a default value. This value represents, in which version the template is released and is used to check if router upgrade is needed. I think the parameter is made optional, so that at any point of time during template build, we can make the template refer to that particular version if we want to. The current template build jobs are based on the default value. It is good to have harder check, I'll create a ticket for that. The default value is not right. Once we move to 4.5/4.6 and say systemvm template changes the default should be accordingly different so I dont think there should be a default value. It would be great if you could make the stricter check as well right now, but I am fine either ways. Please do put the ticket and target for 4.5. Thanks. - Nitin --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/#review57173 --- On Oct. 17, 2014, 5:30 p.m., Harikrishna Patnala wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/26871/ --- (Updated Oct. 17, 2014, 5:30 p.m.) Review request for cloudstack, Kishan Kavala and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7748 https://issues.apache.org/jira/browse/CLOUDSTACK-7748 Repository: cloudstack-git Description --- CLOUDSTACK-7748: Cloudstack version number is missing in system vm template. /etc/cloudstack-release in system vm does not have version number which leads in vm deployment failure while checking router version During the system vm build, arguments can be passed to build.sh script where 'version' argument is one of the optional arguments. The bug is even if version argument is not passed defalut value(CLOUDSTACK_RELEASE=4.4.0) is overridden by the null value (since argument is not passed). Diffs - tools/appliance/build.sh 8bf78b1 Diff: https://reviews.apache.org/r/26871/diff/ Testing --- Thanks, Harikrishna Patnala
RE: Help in Adding XenServer to CS Management Server
Hi, I could move ahead with the issues and see the SSVM and CPVM coming up . But when I try to create a user VM I still don't see the default template. What could be the problem here? Any suggestions? Thanks Regards, Ritu S. -Original Message- From: Pierre-Luc Dion [mailto:pdion...@apache.org] Sent: Wednesday, October 15, 2014 7:52 PM To: dev@cloudstack.apache.org Subject: Re: Help in Adding XenServer to CS Management Server Ritu, You have to wait a little when creating a zone until you have the SSVM and CPVM ready. then it will automatically download a centos 5.6 which confirm your initial zone is working. if this is not happening, there might be a config issue related to primary, secondary storage or network label. hope this help, PL On Wed, Oct 15, 2014 at 9:08 PM, Yitao Jiang willier...@gmail.com wrote: 1.Check zone status, make sure enabled. 2.change mgmt server debug level, watch ing the log file in /var/log/cloud/ On Oct 16, 2014 7:13 AM, Ritu Sabharwal rsabh...@brocade.com wrote: Hi, I am trying to add XenServer to the CS Management Server. I could add the hosts and I see Host status as up on the GUI. But I don't see any System VMs coming up and Virtual Router coming up in the dashboard. When I try to create a User VM there is no template available to select. I am blocked at this point. I did seed Secondary Storage by importing system VM templat from http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm6 4/ for Xen (systemvm64template-4.4-2014-09-30-xen.vhd.bz2 http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/ lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-4 .4-2014-09-30-xen.vhd.bz2 ) Any help on this is appreciated. Thanks Regards, Ritu S.
Re: SSL Usages in CloudStack
For Apache server as pointed by Sheng here are some pointers. Its used in the following scenarios(though SSL by default is disabled). * Console view of virtual machines available through Console Proxy virtual machine (CPVM) * Copy Template available through Secondary Storage virtual machine (SSVM) * Download Template/ISO/Volume (SSVM) I would say read up on Implementation Details of uploading custom certificate [1] to find out how SSL is used [1] - https://cwiki.apache.org/confluence/display/CLOUDSTACK/Implementation+detai ls+and+troubleshooting+-+uploading+custom+domain+certificate+instead+of+usi ng+realhostip.com Thanks, -Nitin On 17/10/14 4:25 PM, Sheng Yang sh...@yasker.org wrote: There are two places uses SSL. Apache server and sockets. For sockets, all the code are in Link.java, NioServer/NioClient/NioConnection etc. I don't know much about Apache server one, which should be used in CPVM and download template etc. --Sheng On Thu, Oct 16, 2014 at 10:00 PM, Santhosh Edukulla santhosh.eduku...@citrix.com wrote: Team, Can you please point out the areas where ssl is used in CloudStack? EX: Agent communications, ssvm, cpvm, template download etc? as well pointers to corresponding modules for these? Regards, Santhosh
Re: Issue VM Access
Thanks for the reply. I was able to solved it today. Installing xrdp in the ubuntu VM from the console did the trick. Thanks, Bikas On Thu, Oct 16, 2014 at 10:23 PM, Yitao Jiang willier...@gmail.com wrote: Try loging into vms each other using ssh ,maybe your template play trick. Or Using vnc-viewer logged into vm to see if the sshd deamon running --- Thanks, Yitao(依涛 姜) jiangyt.github.io On Fri, Oct 17, 2014 at 5:48 AM, Bikas mbik...@uic.edu wrote: Thanks for the replies. I created another VM and connectivity between both VM works (ping from one VM console to another). But still not being able to remote login to any of them from the same network. Please let me what other option I should check. I have created the basic zone so could not able to provide any public ip range as there is no such option in basic mode. Could that be a reason. Thanks, Bikas On Tue, Oct 14, 2014 at 11:03 PM, Carlos Reategui create...@gmail.com wrote: Also try logging in from the console to verify ssh is running and also verify the IP address to make sure it has the ip it is supposed to. If it doesn't match there may be a rouge dhcp server. On Oct 14, 2014, at 7:41 PM, Yitao Jiang willier...@gmail.com wrote: Try spawning another instance within the same network of above , then verify the connectivity between two vms. --- Thanks, Yitao(依涛 姜) jiangyt.github.io On Wed, Oct 15, 2014 at 2:46 AM, Bikas mbik...@uic.edu wrote: Hi all, We are using basic zone configuration in cloud infrastructure. We have VM deployed with Ubuntu OS. We are able to ping the VM IP (instanceVMNameNICsIP address) from local desktop in the same network. However, we are not able to remote access(or ssh) the VM using remote desktop software even though we disable the firewall in both management server and host in hypervisor . We also added the ingress rules for TCP port 22 0.0.0.0/0 at the default security group. Thanks in advance, Bikas
CLOUDSTACK-7539
Looks like we are hitting that same problem, but with different symptoms on swift. We even see the template being pushed to secstor staging in a directory instead of a file. Any idea how to mitigate or workaround? We can deploy some templates, but not some others works once in 20. -- 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_
