[GitHub] cloudstack pull request: Remove AWS api bridge
Github user pyr commented on the pull request: https://github.com/apache/cloudstack/pull/44#issuecomment-65030920 closing this since a new branch has been created by @runseb --- 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. ---
[GitHub] cloudstack pull request: Remove AWS api bridge
Github user pyr closed the pull request at: https://github.com/apache/cloudstack/pull/44 --- 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: root resize support in the UI
I think it would be usefull to have that resize feature for all guests (Linux, Windows, etc) - but perhaps customizes the Resize function to perform partition resize inside Linux (if we are deploying new VM from Linux template) - or simply do not do anything inside guest OS, just resize the drive - and let the client handle partition and file system resize...it might be more clean implementation I guess...? On 1 December 2014 at 08:48, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: It is interesting how, in genereal, this works for XenServer (for exmaple)? I do understand, that entire logic of CS is built around hypervisor capabilities. It does not do more than each specific hypervisor can offer. KVM do have virt-resize tool that can resize Linux partitions, but it will probably not work for Windows hosts anyway. So, to be honest, this UI feature should only be visible for Linux guests. I don't know whether different approach to build and resize root partitions for all hypervisors exist? If it is not possible to do on hypervisor level, how does CS do this? Vadim. -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Sunday, November 30, 2014 2:03 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI It's very possible Citrix customised that installation, what they do for their own customers is their own business. It was certainly possible to do it with 4.3, Marcus wrote some patches at some point to enable this functionality (KVM only, again). The UI has always been considered more of a proof of concept, though it's a very much needed part of ACS, as such everyone is encouraged to use the API and build their own interfaces. I missed some important options and customers because I thought GreenQloud, Exoscale etc will give you some credit as a new customer so you can check out their UI. They don't have as many options as the ACS one, but I found this to be a feature, customers shouldn't be exposed to too many options, they'll just get their noses caught in them. :) Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Sunday, 30 November, 2014 10:53:56 Subject: RE: root resize support in the UI Lucian, I have seen CS 4.3 installation made by Citrix at our parnter and they have the same feature enabled for XenServer and VmWare. I wonder how does it work ? They have their own team of developers to make some extra features they need (like plugin for statistics and billing), but did they implement particularly this feature or Citrix did it - I don't know. It seems this part of code is not contributed back to community anyway. It would be nice to have it, especially together with slieders which are quite popular right now as I understood. Vadim. -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Saturday, November 29, 2014 9:48 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Vadim, 1. Only KVM for now, due to lack of interest I guess 2. The root disk value needs to be equal or larger than that of the template, otherwise you end up with a broken disk, obviously. So go for minimal (say under 10G) templates that can resize themselves, such as the ones at http://dl.openvm.eu ;) 3. The backend API has been supporting this since 4.4.0, it's the UI that is lagging behind More details here https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Saturday, 29 November, 2014 15:17:16 Subject: RE: root resize support in the UI Nux, Can you give more information about this functionality? I am particularly interesting to show to the user this field, but don't know how it will work. Particularly is interesting: 1. Does it work for all hypervisors or just KVM? 2. Does it depend on the template root partition (i.e. I have 10G root at template and put 5G to desired. Will it work?) 3. This is just UI patch, shouldn't it be activated at the backend as well ? Thanks, Vadim From: Nux! [n...@li.nux.ro] Sent: Saturday, November 29, 2014 12:37 To: dev@cloudstack.apache.org Cc: Brian Federle Subject: Re: root resize support in the UI BTW, the code needed to enable custom root size during instance creation is very small, functionality is already there. This patch is needed https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=8 f ec09ba481fbd3b8c2a9e4d31ef06f113b037cb , I tested it and it works fine. And
Re: [ACS450] remove some upgrade path from Release Notes
Hey hey, Thinking as an administrator, I definitely don't want release notes (or upgrade paths themselves, or other documentation that contains procedures that have huge impact) that have not been tested. If I'm running cloudstack 2.2.14, and I want to upgrade to 4.4.2, and I ask on the users list what to do, what is the answer? If it is just follow the upgrade instructions for all consecutive releases and it'll be fine, keep it. Otherwise, remove it. My two cents :) cheers, Leo On Dec 1, 2014, at 12:39 AM, Pierre-Luc Dion pd...@cloudops.com wrote: I'm wondering if I should remove the upgrade instructions of 4.1.x, 4.0.x, 3.0.x and 2.2.14 from the 4.5.0 release notes. These upgrade instructions are fairly outdated and has not been tested(at least in 4.4). They also contain errors and some inconsistency. Unless someone is willing to validate them and fix instructions? any thoughts? thanks, PL
Re: root resize support in the UI
On Mon, Dec 1, 2014 at 9:02 AM, Andrija Panic andrija.pa...@gmail.com wrote: I think it would be usefull to have that resize feature for all guests (Linux, Windows, etc) - but perhaps customizes the Resize function to perform partition resize inside Linux (if we are deploying new VM from Linux template) - or simply do not do anything inside guest OS, just resize the drive - and let the client handle partition and file system resize...it might be more clean implementation I guess...? I believe cloud-init is capable of this? -- Erik
Re: root resize support in the UI
Guys, All that ACS does is to resize the ROOT disk (ie the whole /dev/vda or /dev/xvda), it does not care about partitions, filesystems or OSes inside it. Expanding the partitions and filesystems later on is left to the admin, or if you have cloud-init installed that will take care of it; it is also trivial to expand the partition and filesystem in Windows (Manage Disk management). ACS has nothing to do with virt-resize, that's part of libguestfs (which btw can deal with Windows, too); ACS uses qemu-img [resize] in KVM. HTH Lucian -- 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 Sent: Monday, 1 December, 2014 08:02:05 Subject: Re: root resize support in the UI I think it would be usefull to have that resize feature for all guests (Linux, Windows, etc) - but perhaps customizes the Resize function to perform partition resize inside Linux (if we are deploying new VM from Linux template) - or simply do not do anything inside guest OS, just resize the drive - and let the client handle partition and file system resize...it might be more clean implementation I guess...? On 1 December 2014 at 08:48, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: It is interesting how, in genereal, this works for XenServer (for exmaple)? I do understand, that entire logic of CS is built around hypervisor capabilities. It does not do more than each specific hypervisor can offer. KVM do have virt-resize tool that can resize Linux partitions, but it will probably not work for Windows hosts anyway. So, to be honest, this UI feature should only be visible for Linux guests. I don't know whether different approach to build and resize root partitions for all hypervisors exist? If it is not possible to do on hypervisor level, how does CS do this? Vadim. -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Sunday, November 30, 2014 2:03 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI It's very possible Citrix customised that installation, what they do for their own customers is their own business. It was certainly possible to do it with 4.3, Marcus wrote some patches at some point to enable this functionality (KVM only, again). The UI has always been considered more of a proof of concept, though it's a very much needed part of ACS, as such everyone is encouraged to use the API and build their own interfaces. I missed some important options and customers because I thought GreenQloud, Exoscale etc will give you some credit as a new customer so you can check out their UI. They don't have as many options as the ACS one, but I found this to be a feature, customers shouldn't be exposed to too many options, they'll just get their noses caught in them. :) Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Sunday, 30 November, 2014 10:53:56 Subject: RE: root resize support in the UI Lucian, I have seen CS 4.3 installation made by Citrix at our parnter and they have the same feature enabled for XenServer and VmWare. I wonder how does it work ? They have their own team of developers to make some extra features they need (like plugin for statistics and billing), but did they implement particularly this feature or Citrix did it - I don't know. It seems this part of code is not contributed back to community anyway. It would be nice to have it, especially together with slieders which are quite popular right now as I understood. Vadim. -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Saturday, November 29, 2014 9:48 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Vadim, 1. Only KVM for now, due to lack of interest I guess 2. The root disk value needs to be equal or larger than that of the template, otherwise you end up with a broken disk, obviously. So go for minimal (say under 10G) templates that can resize themselves, such as the ones at http://dl.openvm.eu ;) 3. The backend API has been supporting this since 4.4.0, it's the UI that is lagging behind More details here https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Saturday, 29 November, 2014 15:17:16 Subject: RE: root resize support in the UI Nux, Can you give more information about this functionality? I am particularly interesting to show to the user this field, but don't know how it will work.
Re: root resize support in the UI
Exactly my point - reside the damn drive with qemu-img and leave the rest for the Admin :) On 1 December 2014 at 09:11, Nux! n...@li.nux.ro wrote: Guys, All that ACS does is to resize the ROOT disk (ie the whole /dev/vda or /dev/xvda), it does not care about partitions, filesystems or OSes inside it. Expanding the partitions and filesystems later on is left to the admin, or if you have cloud-init installed that will take care of it; it is also trivial to expand the partition and filesystem in Windows (Manage Disk management). ACS has nothing to do with virt-resize, that's part of libguestfs (which btw can deal with Windows, too); ACS uses qemu-img [resize] in KVM. HTH Lucian -- 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 Sent: Monday, 1 December, 2014 08:02:05 Subject: Re: root resize support in the UI I think it would be usefull to have that resize feature for all guests (Linux, Windows, etc) - but perhaps customizes the Resize function to perform partition resize inside Linux (if we are deploying new VM from Linux template) - or simply do not do anything inside guest OS, just resize the drive - and let the client handle partition and file system resize...it might be more clean implementation I guess...? On 1 December 2014 at 08:48, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: It is interesting how, in genereal, this works for XenServer (for exmaple)? I do understand, that entire logic of CS is built around hypervisor capabilities. It does not do more than each specific hypervisor can offer. KVM do have virt-resize tool that can resize Linux partitions, but it will probably not work for Windows hosts anyway. So, to be honest, this UI feature should only be visible for Linux guests. I don't know whether different approach to build and resize root partitions for all hypervisors exist? If it is not possible to do on hypervisor level, how does CS do this? Vadim. -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Sunday, November 30, 2014 2:03 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI It's very possible Citrix customised that installation, what they do for their own customers is their own business. It was certainly possible to do it with 4.3, Marcus wrote some patches at some point to enable this functionality (KVM only, again). The UI has always been considered more of a proof of concept, though it's a very much needed part of ACS, as such everyone is encouraged to use the API and build their own interfaces. I missed some important options and customers because I thought GreenQloud, Exoscale etc will give you some credit as a new customer so you can check out their UI. They don't have as many options as the ACS one, but I found this to be a feature, customers shouldn't be exposed to too many options, they'll just get their noses caught in them. :) Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Sunday, 30 November, 2014 10:53:56 Subject: RE: root resize support in the UI Lucian, I have seen CS 4.3 installation made by Citrix at our parnter and they have the same feature enabled for XenServer and VmWare. I wonder how does it work ? They have their own team of developers to make some extra features they need (like plugin for statistics and billing), but did they implement particularly this feature or Citrix did it - I don't know. It seems this part of code is not contributed back to community anyway. It would be nice to have it, especially together with slieders which are quite popular right now as I understood. Vadim. -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Saturday, November 29, 2014 9:48 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Vadim, 1. Only KVM for now, due to lack of interest I guess 2. The root disk value needs to be equal or larger than that of the template, otherwise you end up with a broken disk, obviously. So go for minimal (say under 10G) templates that can resize themselves, such as the ones at http://dl.openvm.eu ;) 3. The backend API has been supporting this since 4.4.0, it's the UI that is lagging behind More details here https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org
WTF: Difference between schemas across branches?
Hi, While I’m working to backport changes on 4.3 branch, I discovered some changes between 4.3 branch’s schema-421to431.sql and master branch’s 421to431.sql files. While most changes are inserts/update related which may not severely harm a user upgrading from a previous version of CloudStack, but I found there were changes in the schema itself; in this case the `cloud`.`template_view`: 0e2e6995 setup/db/db/schema-421to430.sql (Nitin Mehta 2014-01-30 17:59:55 -0800 306) `cloud`.`template_store_ref` ON template_store_ref.template_id = vm_template.id and template_store_ref.store_role = 'Image' and template_store_ref.destroyed=0 While on 4.3 branch: abbae2aa setup/db/db/schema-420to430.sql (Alex Huang 2013-08-26 17:30:58 -0700 306) `cloud`.`template_store_ref` ON template_store_ref.template_id = vm_template.id and template_store_ref.store_role = ‘Image’ Which version should we keep? Here’s the complete diff: http://pastebin.com/PB6N7aCt You may do it locally against 4.3 (4.4/4.5 etc.) and master as well: git diff master 4.3 -- setup/db/db/schema-421to430.sql I think such issues are seen time and time again due to the way paid contributors work on private forks and upstream ACS. We simply don’t want to use code thrown over corporate fences to ACS branches. While who am I to tell you how to do your job - I simply request that all of the committers are expected to have some level of commitment to the project and ethics of their contributions. The best way to work together is to work in the upstream first and then work on your forks that is based on the upstream. Hope this will improve with time. 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: root resize support in the UI
I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is not feasible. Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 10:02 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI I think it would be usefull to have that resize feature for all guests (Linux, Windows, etc) - but perhaps customizes the Resize function to perform partition resize inside Linux (if we are deploying new VM from Linux template) - or simply do not do anything inside guest OS, just resize the drive - and let the client handle partition and file system resize...it might be more clean implementation I guess...? On 1 December 2014 at 08:48, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: It is interesting how, in genereal, this works for XenServer (for exmaple)? I do understand, that entire logic of CS is built around hypervisor capabilities. It does not do more than each specific hypervisor can offer. KVM do have virt-resize tool that can resize Linux partitions, but it will probably not work for Windows hosts anyway. So, to be honest, this UI feature should only be visible for Linux guests. I don't know whether different approach to build and resize root partitions for all hypervisors exist? If it is not possible to do on hypervisor level, how does CS do this? Vadim. -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Sunday, November 30, 2014 2:03 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI It's very possible Citrix customised that installation, what they do for their own customers is their own business. It was certainly possible to do it with 4.3, Marcus wrote some patches at some point to enable this functionality (KVM only, again). The UI has always been considered more of a proof of concept, though it's a very much needed part of ACS, as such everyone is encouraged to use the API and build their own interfaces. I missed some important options and customers because I thought GreenQloud, Exoscale etc will give you some credit as a new customer so you can check out their UI. They don't have as many options as the ACS one, but I found this to be a feature, customers shouldn't be exposed to too many options, they'll just get their noses caught in them. :) Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Sunday, 30 November, 2014 10:53:56 Subject: RE: root resize support in the UI Lucian, I have seen CS 4.3 installation made by Citrix at our parnter and they have the same feature enabled for XenServer and VmWare. I wonder how does it work ? They have their own team of developers to make some extra features they need (like plugin for statistics and billing), but did they implement particularly this feature or Citrix did it - I don't know. It seems this part of code is not contributed back to community anyway. It would be nice to have it, especially together with slieders which are quite popular right now as I understood. Vadim. -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Saturday, November 29, 2014 9:48 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Vadim, 1. Only KVM for now, due to lack of interest I guess 2. The root disk value needs to be equal or larger than that of the template, otherwise you end up with a broken disk, obviously. So go for minimal (say under 10G) templates that can resize themselves, such as the ones at http://dl.openvm.eu ;) 3. The backend API has been supporting this since 4.4.0, it's the UI that is lagging behind More details here https://issues.apache.org/jira/browse/CLOUDSTACK-6181 Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Saturday, 29 November, 2014 15:17:16 Subject: RE: root resize support in the UI Nux,
Re: root resize support in the UI
On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is not feasible. It's not given that you want to resize a partition or which one, just because you resize the disk. Thus it's not feasible to assume that the orchestration layer should be capable of doing it. -- Erik
Re: Random placing of Snapshots on multiple Secondary Storages
Its hardcoded so unfortunately can't be changed at the moment. There is a JIRA bug for this enhancement. Thanks, -Nitin On 29/11/14 6:44 PM, Wadia, Yohan ywa...@virtela.net wrote: Hi, Can anyone help me with this? -Original Message- From: Wadia, Yohan [mailto:ywa...@virtela.net] Sent: 28 November 2014 15:25 To: 'dev@cloudstack.apache.org' Subject: 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: WTF: Difference between schemas across branches?
Rohit, You are quite right to complain about this, as in +1. There was a similar thing in the 44to45 files between 4.5 and master. Hugo mailed about it and half of it got resolved! WTF indeed. mobile dev with bilingual spelling checker used (read at your own risk) Op 1 dec. 2014 09:18 schreef Rohit Yadav rohit.ya...@shapeblue.com: Hi, While I’m working to backport changes on 4.3 branch, I discovered some changes between 4.3 branch’s schema-421to431.sql and master branch’s 421to431.sql files. While most changes are inserts/update related which may not severely harm a user upgrading from a previous version of CloudStack, but I found there were changes in the schema itself; in this case the `cloud`.`template_view`: 0e2e6995 setup/db/db/schema-421to430.sql (Nitin Mehta 2014-01-30 17:59:55 -0800 306) `cloud`.`template_store_ref` ON template_store_ref.template_id = vm_template.id and template_store_ref.store_role = 'Image' and template_store_ref.destroyed=0 While on 4.3 branch: abbae2aa setup/db/db/schema-420to430.sql (Alex Huang 2013-08-26 17:30:58 -0700 306) `cloud`.`template_store_ref` ON template_store_ref.template_id = vm_template.id and template_store_ref.store_role = ‘Image’ Which version should we keep? Here’s the complete diff: http://pastebin.com/PB6N7aCt You may do it locally against 4.3 (4.4/4.5 etc.) and master as well: git diff master 4.3 -- setup/db/db/schema-421to430.sql I think such issues are seen time and time again due to the way paid contributors work on private forks and upstream ACS. We simply don’t want to use code thrown over corporate fences to ACS branches. While who am I to tell you how to do your job - I simply request that all of the committers are expected to have some level of commitment to the project and ethics of their contributions. The best way to work together is to work in the upstream first and then work on your forks that is based on the upstream. Hope this will improve with time. 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 Software Engineering http://shapeblue.com/cloudstack-software-engineering/ 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: [DISCUSS] LTS Releases
Hi everyone, Thanks for a great discussion. I understand it may be difficult to support releases for several years with CloudStack’s fast paced development, and the statistics Leo shared are certainly not what I was aiming for. I think it will be difficult to gather agreement in this stage and I certainly don’t want to hurt upstream in any way so I think it’s alright to simply keep doing bugfix releases without labelling them with anything on the upstream project. From ShapeBlue’s standpoint we will keep working on the upstream first and make sure we don’t fork CloudStack though we’ll have our support branches but those will be public too (https://github.com/shapeblue/cloudstack). We’ll be driving bugfix releases and if those releases are not possible (due to lack of upgrade paths to later/future versions say in 4.4.1, 4.4.2 etc) we’ll keep releasing our patches with suitable release notes publicly via our deb/rpm repositories publicly (shapeblue.com/packages) for everyone. On 28-Nov-2014, at 3:17 pm, Leo Simons lsim...@schubergphilis.com wrote: 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
Re: root resize support in the UI
Exactly, there may be more than 1 partion on that 1 drive.. So just increase disk size, and let administaror handle the inside VM job On 1 December 2014 at 09:34, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is not feasible. It's not given that you want to resize a partition or which one, just because you resize the disk. Thus it's not feasible to assume that the orchestration layer should be capable of doing it. -- Erik -- Andrija Panić
Is issue status can only change by owner on jira system ?
hi,all https://issues.apache.org/jira/browse/CLOUDSTACK-519 I recheck the status which 519 mentioned . The issue is not cloudstack bug . My question is : Is the issue status can only change/close by owner on jira system ? -- Regards, ChunFeng
RE: root resize support in the UI
But that means user can not create desired volume during instance set-up. If we would like to have, for example, VM with disk offers from 5-100Gb I need to create dozen of same templates that differ only at root size. Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 11:06 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Exactly, there may be more than 1 partion on that 1 drive.. So just increase disk size, and let administaror handle the inside VM job On 1 December 2014 at 09:34, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is not feasible. It's not given that you want to resize a partition or which one, just because you resize the disk. Thus it's not feasible to assume that the orchestration layer should be capable of doing it. -- Erik -- Andrija Panić
Re: root resize support in the UI
Vadim, not sure if I understand corrrectly - but you have i.e. 10GB template. you provision new VM with different size i.e. 50GB, and then after the instance is UP and running - there is just 40GB of additional unalocated space inside VM/disk, so admin need to resize partition and resize FS... ? I have been manually using qemu-img to resize some volumes (update the size inside DB) and then boot VM and do inside VM work of resizing stuff... If we only increase disk by qemu-img and update the DB - than no more admin-manual hacks needed - and we have consistent solution, that works across all platforms. And to support resize inside differente OS-es by ACS (partitions and FS) - seems pretty impossible for me, except for basic templates that have 1 partition, and i.e. no swap partition, etc...we loose consistency here completely... On 1 December 2014 at 10:33, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: But that means user can not create desired volume during instance set-up. If we would like to have, for example, VM with disk offers from 5-100Gb I need to create dozen of same templates that differ only at root size. Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 11:06 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Exactly, there may be more than 1 partion on that 1 drive.. So just increase disk size, and let administaror handle the inside VM job On 1 December 2014 at 09:34, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is not feasible. It's not given that you want to resize a partition or which one, just because you resize the disk. Thus it's not feasible to assume that the orchestration layer should be capable of doing it. -- Erik -- Andrija Panić -- Andrija Panić
Cloudstack repos
Hello Dev-s I am looking closer to the CS development process and if possible wish to contribute. I have found there are at least 2 repos for CS. One, I suppose, is official : git://git.apache.org/cloudstack.git another one is https://github.com/shapeblue/cloudstack.git Where does development take place? Are these 2 repos in sync with each other? Are there more repos where developers do their work? What is the purpose to have more of them ? Thanks for expaination, Vadim Kimlaychuk
Could you review the patch?
Dear colleagues, Could you review and submit the patch (if everything is okay)? Very minor change. https://reviews.apache.org/r/27979/ Kind regards, Ilia Shakitko Innovation Engineer LeaseWeb Technologies B.V. T: +31 20 316 0235 E: i.shaki...@tech.leaseweb.com W: www.leaseweb.comhttp://www.leaseweb.com Luttenbergweg 8,1101 EC Amsterdam, Netherlands
Re: Cloudstack repos
HI Vadim, first repo is official one, second repo is shapeblue's repo, since they also provide RPMs for convinience and with some patches... Anyway, you will go with official one. Cheers On 1 December 2014 at 11:12, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: Hello Dev-s I am looking closer to the CS development process and if possible wish to contribute. I have found there are at least 2 repos for CS. One, I suppose, is official : git://git.apache.org/cloudstack.git another one is https://github.com/shapeblue/cloudstack.git Where does development take place? Are these 2 repos in sync with each other? Are there more repos where developers do their work? What is the purpose to have more of them ? Thanks for expaination, Vadim Kimlaychuk -- Andrija Panić
Re: Review Request 27979: CLOUDSTACK-7903: Decrease minimal usage aggregation range value
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27979/#review63348 --- Ship it! I'm going ahead with the merge on master, 4.5 and 4.4 and 4.3. This is a very simple patch that lowers the minimum threshold from 10 mins to 1 mins for usage interval, I was only waiting for Kishan's review but we've waited for several weeks on this. - Rohit Yadav On Nov. 25, 2014, 7:25 a.m., Ilia Shakitko wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27979/ --- (Updated Nov. 25, 2014, 7:25 a.m.) Review request for cloudstack, Chip Childers, Kishan Kavala, Rohit Yadav, Simon Fiddaman, Stephen Hoogendijk, and Wei Zhou. Bugs: CLOUDSTACK-7903 https://issues.apache.org/jira/browse/CLOUDSTACK-7903 Repository: cloudstack-git Description --- When you want to build 95-percentile billing model for the network traffic usage, it is good to have 5-minutes (or 1-minute) usage samples instead of 10 (which is minimum allowed in ACS at the moment). Let admin to control it. This change decreases the lower limit for USAGE_AGGREGATION_RANGE_MIN parameter, making it minimum possible positive integer. It is also removes declaration of the same constant in 3 places. Will be happy if patch can be: - cherry-picked to the 4.4 and 4.5 branches - included to the 4.4.2 tag. Diffs - server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 23ddfb1 server/src/com/cloud/server/StatsCollector.java 1fcaa62 usage/src/com/cloud/usage/UsageManagerImpl.java fe7ee1e Diff: https://reviews.apache.org/r/27979/diff/ Testing --- Tested on master, 4.4 and 4.5 branches. But then during the review time I had to re-prepare the patch and it become compatible only for master branch. If you accept the patch, could you also cherry-pick my commit to 4.4 and 4.5 branches? (there will be 1 one-line conflict to resolve) Thanks, Ilia Shakitko
Re: Could you review the patch?
Done. On Monday 01 December 2014 03:48 PM, Ilia Shakitko wrote: Dear colleagues, Could you review and submit the patch (if everything is okay)? Very minor change. https://reviews.apache.org/r/27979/ Kind regards, Ilia Shakitko Innovation Engineer LeaseWeb Technologies B.V. T: +31 20 316 0235 E: i.shaki...@tech.leaseweb.com W: www.leaseweb.comhttp://www.leaseweb.com Luttenbergweg 8,1101 EC Amsterdam, Netherlands -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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.
CloudMonkey 5.3 not starting on Ubuntu 14.10
Hi guys, I am having issues starting cloudmonkey on ubuntu 14.10. I get the following error: $ cloudmonkey Import error in cloudmonkey.cloudmonkey : No module named packages I have tried to google for the error, but can't find the solution. I've installed it via pip install cloudmonkey. Could some one point me in the right direction please? Thanks Andrei
Build failed in Jenkins: build-master #1985
See http://jenkins.buildacloud.org/job/build-master/1985/changes Changes: [Rohit Yadav] CLOUDSTACK-7903: Decreased minimal usage aggregation range value -- [...truncated 1712 lines...] [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-server --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-engine-network --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-engine-network --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-master/ws/engine/network/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-engine-network --- [INFO] Compiling 1 source file to http://jenkins.buildacloud.org/job/build-master/ws/engine/network/target/classes [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-usage --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-usage --- [INFO] Executing tasks main: [copy] Copying 2 files to http://jenkins.buildacloud.org/job/build-master/ws/usage/target/transformed [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-usage --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-usage --- [INFO] Compiling 19 source files to http://jenkins.buildacloud.org/job/build-master/ws/usage/target/classes [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-engine-orchestration --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-engine-orchestration --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-engine-orchestration --- [INFO] Compiling 68 source files to http://jenkins.buildacloud.org/job/build-master/ws/engine/orchestration/target/classes [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ cloud-engine-network --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-master/ws/engine/network/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ cloud-engine-network --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-engine-network --- [INFO] Surefire report directory: http://jenkins.buildacloud.org/job/build-master/ws/engine/network/target/surefire-reports --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] http://jenkins.buildacloud.org/job/build-master/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[45,23] error: cannot find symbol [ERROR] symbol: class StatsCollector location: package com.cloud.server http://jenkins.buildacloud.org/job/build-master/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[249,39] error: cannot find symbol [ERROR] symbol: variable StatsCollector location: class UsageManagerImpl http://jenkins.buildacloud.org/job/build-master/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[250,109] error: cannot find symbol [ERROR] symbol: variable StatsCollector location: class UsageManagerImpl http://jenkins.buildacloud.org/job/build-master/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[251,39] error: cannot find symbol [INFO] 4 errors [INFO] - [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-server --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-server --- [INFO] Executing tasks main: [copy] Copying 3 files to http://jenkins.buildacloud.org/job/build-master/ws/server/target/conf [copy] Copying 1 file to http://jenkins.buildacloud.org/job/build-master/ws/server/target/conf [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-server --- [debug] execute contextualize [INFO] Using
Re: Cloudstack repos
Hi Vadim, The official repository is at https://git-wip-us.apache.org/repos/asf/cloudstack.git A mirror is available on Github which is more easy to work with, to get started I would recommend you fork the Github repository, work on it and pull/rebase using the above official repository, and send us Github Pull Requests for any code contributions: github.com/apache/cloudstack Our (ShapeBlue's) CloudStack repo on github is public for transparency purposes and to host release notes and tags of our patches. We think of our repo as a backup of CloudStack repository (that syncs faster than the github mirror using a cronjob) and we also note in its description that they should be considered as our backup only. On Monday 01 December 2014 03:42 PM, Vadim Kimlaychuk wrote: Hello Dev-s I am looking closer to the CS development process and if possible wish to contribute. I have found there are at least 2 repos for CS. One, I suppose, is official : git://git.apache.org/cloudstack.git another one is https://github.com/shapeblue/cloudstack.git Where does development take place? Are these 2 repos in sync with each other? Are there more repos where developers do their work? What is the purpose to have more of them ? Thanks for expaination, Vadim Kimlaychuk -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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.
Build failed in Jenkins: simulator-singlerun #719
See http://jenkins.buildacloud.org/job/simulator-singlerun/719/changes Changes: [Rohit Yadav] CLOUDSTACK-7903: Decreased minimal usage aggregation range value -- [...truncated 1857 lines...] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.24 sec Running com.cloud.network.security.SecurityGroupQueueTest Total jobs dequeued = 10, num queued=1001 queue current size=991 Num Vms= 50 Queue size = 50 Num Vms= 2 Queue size = 2 time=1069 ms Num Vms= 5000 Queue size = 5000 time=3265 ms Num Vms= 1 Queue size = 1 time=1 ms Num Vms= 100 Queue size = 100 time=317 ms Num Vms= 1 Queue size = 1 time=417 ms Total jobs dequeued = 10, num queued=1010 queue current size=1000 Total jobs dequeued = 1, num queued=1001 queue current size=1000 Total jobs dequeued = 10, num queued=1000 queue current size=990 Total jobs dequeued = 10, num queued=10 queue current size=0 Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.202 sec Running com.cloud.network.UpdatePhysicalNetworkTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running com.cloud.network.vpc.VpcManagerImplTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running com.cloud.network.element.VirtualRouterElementTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.008 sec Running com.cloud.network.router.VirtualNetworkApplianceManagerImplTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.145 sec Running com.cloud.network.router.RouterControlHelperTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running com.cloud.network.router.NetworkHelperImplTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec Running com.cloud.network.dao.NetworkDaoTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running com.cloud.network.CreatePrivateNetworkTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Running com.cloud.network.ExternalLoadBalancerDeviceManagerImplTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.216 sec Running com.cloud.server.ConfigurationServerImplTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.082 sec Running com.cloud.user.AccountManagerImplTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.288 sec Running com.cloud.alert.AlertControlsUnitTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec Running com.cloud.capacity.CapacityManagerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec Results : Tests run: 257, Failures: 0, Errors: 0, Skipped: 3 [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ cloud-server --- [INFO] Building jar: http://jenkins.buildacloud.org/job/simulator-singlerun/ws/server/target/cloud-server-4.6.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-server --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-server --- [INFO] Installing http://jenkins.buildacloud.org/job/simulator-singlerun/ws/server/target/cloud-server-4.6.0-SNAPSHOT.jar to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-server/4.6.0-SNAPSHOT/cloud-server-4.6.0-SNAPSHOT.jar [INFO] Installing http://jenkins.buildacloud.org/job/simulator-singlerun/ws/server/pom.xml to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-server/4.6.0-SNAPSHOT/cloud-server-4.6.0-SNAPSHOT.pom [INFO] [INFO] [INFO] Building Apache CloudStack Usage Server 4.6.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloud-usage --- [INFO] Deleting http://jenkins.buildacloud.org/job/simulator-singlerun/ws/usage/target (includes = [**/*], excludes = []) [INFO] Deleting http://jenkins.buildacloud.org/job/simulator-singlerun/ws/usage (includes = [target, dist], excludes = []) [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-usage --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-usage --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-usage --- [INFO] Executing tasks main: [copy] Copying 2 files to http://jenkins.buildacloud.org/job/simulator-singlerun/ws/usage/target/transformed [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-usage --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @
Build failed in Jenkins: build-4.5 #184
See http://jenkins.buildacloud.org/job/build-4.5/184/changes Changes: [Rohit Yadav] CLOUDSTACK-7903: Decreased minimal usage aggregation range value -- [...truncated 1646 lines...] [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-engine-network --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-engine-network --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-usage --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-engine-orchestration --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-engine-network --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-4.5/ws/engine/network/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-engine-network --- [INFO] Compiling 1 source file to http://jenkins.buildacloud.org/job/build-4.5/ws/engine/network/target/classes [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-engine-orchestration --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-engine-orchestration --- [INFO] Compiling 68 source files to http://jenkins.buildacloud.org/job/build-4.5/ws/engine/orchestration/target/classes [INFO] [INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-usage --- [INFO] Executing tasks main: [copy] Copying 2 files to http://jenkins.buildacloud.org/job/build-4.5/ws/usage/target/transformed [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-usage --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-usage --- [INFO] Compiling 19 source files to http://jenkins.buildacloud.org/job/build-4.5/ws/usage/target/classes [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ cloud-engine-network --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-4.5/ws/engine/network/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ cloud-engine-network --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-engine-network --- [INFO] Surefire report directory: http://jenkins.buildacloud.org/job/build-4.5/ws/engine/network/target/surefire-reports --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-server --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-server --- [INFO] Executing tasks main: [copy] Copying 3 files to http://jenkins.buildacloud.org/job/build-4.5/ws/server/target/conf [copy] Copying 1 file to http://jenkins.buildacloud.org/job/build-4.5/ws/server/target/conf [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-server --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 30 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-server --- [INFO] Compiling 362 source files to http://jenkins.buildacloud.org/job/build-4.5/ws/server/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] http://jenkins.buildacloud.org/job/build-4.5/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[45,23] error: cannot find symbol [ERROR] symbol: class StatsCollector location: package com.cloud.server http://jenkins.buildacloud.org/job/build-4.5/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[249,39] error: cannot find symbol [ERROR] symbol: variable StatsCollector location: class UsageManagerImpl http://jenkins.buildacloud.org/job/build-4.5/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[250,109] error: cannot find symbol [ERROR] symbol: variable
Re: CloudMonkey 5.3 not starting on Ubuntu 14.10
On Mon, Dec 1, 2014 at 11:32 AM, Andrei Mikhailovsky and...@arhont.com wrote: Hi guys, I am having issues starting cloudmonkey on ubuntu 14.10. I get the following error: $ cloudmonkey Import error in cloudmonkey.cloudmonkey : No module named packages I have the same on CentOS 6.6, cloudmonkey installed with pip -- Erik
Re: Cloudstack repos
On Dec 1, 2014, at 11:21 AM, Andrija Panic andrija.pa...@gmail.com wrote: HI Vadim, first repo is official one, second repo is shapeblue's repo, since they also provide RPMs for convinience and with some patches... Anyway, you will go with official one. Cheers If you want to work via github and submit pull request to upstream you can use the github mirror: https://github.com/apache/cloudstack This repo is a mirror of the official cloudstack git repo maintained by apache. On 1 December 2014 at 11:12, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: Hello Dev-s I am looking closer to the CS development process and if possible wish to contribute. I have found there are at least 2 repos for CS. One, I suppose, is official : git://git.apache.org/cloudstack.git another one is https://github.com/shapeblue/cloudstack.git Where does development take place? Are these 2 repos in sync with each other? Are there more repos where developers do their work? What is the purpose to have more of them ? Thanks for expaination, Vadim Kimlaychuk -- Andrija Panić
Re: Build failed in Jenkins: build-4.5 #184
Caused by recent review request merge, I’m on it. On 01-Dec-2014, at 4:10 pm, jenk...@cloudstack.org wrote: See http://jenkins.buildacloud.org/job/build-4.5/184/changes Changes: [Rohit Yadav] CLOUDSTACK-7903: Decreased minimal usage aggregation range value -- [...truncated 1646 lines...] [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-engine-network --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-engine-network --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-usage --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-engine-orchestration --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-engine-network --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-4.5/ws/engine/network/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-engine-network --- [INFO] Compiling 1 source file to http://jenkins.buildacloud.org/job/build-4.5/ws/engine/network/target/classes [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-engine-orchestration --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-engine-orchestration --- [INFO] Compiling 68 source files to http://jenkins.buildacloud.org/job/build-4.5/ws/engine/orchestration/target/classes [INFO] [INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-usage --- [INFO] Executing tasks main: [copy] Copying 2 files to http://jenkins.buildacloud.org/job/build-4.5/ws/usage/target/transformed [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-usage --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-usage --- [INFO] Compiling 19 source files to http://jenkins.buildacloud.org/job/build-4.5/ws/usage/target/classes [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ cloud-engine-network --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-4.5/ws/engine/network/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ cloud-engine-network --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-engine-network --- [INFO] Surefire report directory: http://jenkins.buildacloud.org/job/build-4.5/ws/engine/network/target/surefire-reports --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-server --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-server --- [INFO] Executing tasks main: [copy] Copying 3 files to http://jenkins.buildacloud.org/job/build-4.5/ws/server/target/conf [copy] Copying 1 file to http://jenkins.buildacloud.org/job/build-4.5/ws/server/target/conf [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-server --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 30 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-server --- [INFO] Compiling 362 source files to http://jenkins.buildacloud.org/job/build-4.5/ws/server/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] http://jenkins.buildacloud.org/job/build-4.5/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[45,23] error: cannot find symbol [ERROR] symbol: class StatsCollector location: package com.cloud.server http://jenkins.buildacloud.org/job/build-4.5/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[249,39] error: cannot find symbol [ERROR] symbol: variable
[NOTICE] CloudMonkey 5.3 not starting on Ubuntu 14.10
Hi Andrei, Thanks for bringing this to our notice. With Ubuntu 14.04/14.10, the default pip has some issues. To install CloudMonkey or any package dependent on requests users simply need to upgrade pip to make it work: 1. Uninstall the default pip: sudo apt-get remove --purge python-pip 2. Download and install latest pip from https://pip.pypa.io/en/latest/installing.html#install-pip I faced this issue too and the above worked for me. After doing the above, retry/reinstall cloudmonkey it should work. On Monday 01 December 2014 04:02 PM, Andrei Mikhailovsky wrote: Hi guys, I am having issues starting cloudmonkey on ubuntu 14.10. I get the following error: $ cloudmonkey Import error in cloudmonkey.cloudmonkey : No module named packages I have tried to google for the error, but can't find the solution. I've installed it via pip install cloudmonkey. Could some one point me in the right direction please? Thanks Andrei This is the bug reference from Launchpad: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1306991 If you've any issues, let me know. -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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: CloudMonkey 5.3 not starting on Ubuntu 14.10
On Dec 1, 2014, at 11:44 AM, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 11:32 AM, Andrei Mikhailovsky and...@arhont.com wrote: Hi guys, I am having issues starting cloudmonkey on ubuntu 14.10. I get the following error: $ cloudmonkey Import error in cloudmonkey.cloudmonkey : No module named packages I have the same on CentOS 6.6, cloudmonkey installed with pip Have you tried with virtualenv ? Are you upgrading ? -- Erik
Re: CloudMonkey 5.3 not starting on Ubuntu 14.10
Erik, this is a clean install, not an upgrade. I don't remember having issues on Ubuntu 14.04. I've also tried the easy_install method shown in the docs and that produced the same error. not really sure what you mean by the virtualenv. Andrei - Original Message - From: sebgoa run...@gmail.com To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 10:50:05 AM Subject: Re: CloudMonkey 5.3 not starting on Ubuntu 14.10 On Dec 1, 2014, at 11:44 AM, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 11:32 AM, Andrei Mikhailovsky and...@arhont.com wrote: Hi guys, I am having issues starting cloudmonkey on ubuntu 14.10. I get the following error: $ cloudmonkey Import error in cloudmonkey.cloudmonkey : No module named packages I have the same on CentOS 6.6, cloudmonkey installed with pip Have you tried with virtualenv ? Are you upgrading ? -- Erik
Re: CloudMonkey 5.3 not starting on Ubuntu 14.10
Andrei, I’ve replied to your query in another thread, that tries to publish this issue and its fix for everyone on users@ and dev@. Thanks. Quick solution - remove python-pip and install pip using pip project page. On 01-Dec-2014, at 4:22 pm, Andrei Mikhailovsky and...@arhont.com wrote: Erik, this is a clean install, not an upgrade. I don't remember having issues on Ubuntu 14.04. I've also tried the easy_install method shown in the docs and that produced the same error. not really sure what you mean by the virtualenv. Andrei - Original Message - From: sebgoa run...@gmail.com To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 10:50:05 AM Subject: Re: CloudMonkey 5.3 not starting on Ubuntu 14.10 On Dec 1, 2014, at 11:44 AM, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 11:32 AM, Andrei Mikhailovsky and...@arhont.com wrote: Hi guys, I am having issues starting cloudmonkey on ubuntu 14.10. I get the following error: $ cloudmonkey Import error in cloudmonkey.cloudmonkey : No module named packages I have the same on CentOS 6.6, cloudmonkey installed with pip Have you tried with virtualenv ? Are you upgrading ? -- Erik 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: CloudMonkey 5.3 not starting on Ubuntu 14.10
On Mon, Dec 1, 2014 at 11:50 AM, sebgoa run...@gmail.com wrote: On Dec 1, 2014, at 11:44 AM, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 11:32 AM, Andrei Mikhailovsky and...@arhont.com wrote: Hi guys, I am having issues starting cloudmonkey on ubuntu 14.10. I get the following error: $ cloudmonkey Import error in cloudmonkey.cloudmonkey : No module named packages I have the same on CentOS 6.6, cloudmonkey installed with pip Have you tried with virtualenv ? Are you upgrading ? Nope, all I've tried is: pip install cloudmonkey This was a fresh machine, so no upgrade. Stock CentOS 6.6. After doing yum remove python-pip, and installing pip as per the docs Rohit sent, and then doing: pip install --force-reinstall -U cloudmonkey, i now get: Traceback (most recent call last): File /usr/bin/cloudmonkey, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.6/site-packages/pkg_resources.py, line 2655, in module working_set.require(__requires__) File /usr/lib/python2.6/site-packages/pkg_resources.py, line 648, in require needed = self.resolve(parse_requirements(requirements)) File /usr/lib/python2.6/site-packages/pkg_resources.py, line 546, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: requests -- Erik
Re: CloudMonkey 5.3 not starting on Ubuntu 14.10
On Mon, Dec 1, 2014 at 11:53 AM, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 11:50 AM, sebgoa run...@gmail.com wrote: On Dec 1, 2014, at 11:44 AM, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 11:32 AM, Andrei Mikhailovsky and...@arhont.com wrote: Hi guys, I am having issues starting cloudmonkey on ubuntu 14.10. I get the following error: $ cloudmonkey Import error in cloudmonkey.cloudmonkey : No module named packages I have the same on CentOS 6.6, cloudmonkey installed with pip Have you tried with virtualenv ? Are you upgrading ? Nope, all I've tried is: pip install cloudmonkey This was a fresh machine, so no upgrade. Stock CentOS 6.6. After doing yum remove python-pip, and installing pip as per the docs Rohit sent, and then doing: pip install --force-reinstall -U cloudmonkey, i now get: Traceback (most recent call last): File /usr/bin/cloudmonkey, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.6/site-packages/pkg_resources.py, line 2655, in module working_set.require(__requires__) File /usr/lib/python2.6/site-packages/pkg_resources.py, line 648, in require needed = self.resolve(parse_requirements(requirements)) File /usr/lib/python2.6/site-packages/pkg_resources.py, line 546, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: requests I managed to get cloudmonkey running by doing: $ sudo easy_install --upgrade requests $ sudo easy_install --upgrade pygments I have no idea why pip couldn't fix it. -- Erik
Re: Cloudstack repos
Hi Rohit, For end user , even for developers , two repos may raise some mix-up. Could you please modify the README.md file in ShapeBlue's repo by add some statements for explaination ? -- Regards, ChunFeng -- Original -- From: Rohit Yadavrohit.ya...@shapeblue.com; Date: Mon, Dec 1, 2014 07:05 PM To: devdev@cloudstack.apache.org; Subject: Re: Cloudstack repos Hi Vadim, The official repository is at https://git-wip-us.apache.org/repos/asf/cloudstack.git A mirror is available on Github which is more easy to work with, to get started I would recommend you fork the Github repository, work on it and pull/rebase using the above official repository, and send us Github Pull Requests for any code contributions: github.com/apache/cloudstack Our (ShapeBlue's) CloudStack repo on github is public for transparency purposes and to host release notes and tags of our patches. We think of our repo as a backup of CloudStack repository (that syncs faster than the github mirror using a cronjob) and we also note in its description that they should be considered as our backup only. On Monday 01 December 2014 03:42 PM, Vadim Kimlaychuk wrote: Hello Dev-s I am looking closer to the CS development process and if possible wish to contribute. I have found there are at least 2 repos for CS. One, I suppose, is official : git://git.apache.org/cloudstack.git another one is https://github.com/shapeblue/cloudstack.git Where does development take place? Are these 2 repos in sync with each other? Are there more repos where developers do their work? What is the purpose to have more of them ? Thanks for expaination, Vadim Kimlaychuk -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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: CloudMonkey 5.3 not starting on Ubuntu 14.10
Rohit, I've tried your suggestion and that didn't work for me. Had the same error message. However, I can confirm that running Erik's suggestion fixed my problem. Andrei -- Andrei Mikhailovsky Director Arhont Information Security Web: http://www.arhont.com http://www.wi-foo.com Tel: +44 (0)870 4431337 Fax: +44 (0)208 429 3111 PGP: Key ID - 0x2B3438DE PGP: Server - keyserver.pgp.com DISCLAIMER The information contained in this email is intended only for the use of the person(s) to whom it is addressed and may be confidential or contain legally privileged information. If you are not the intended recipient you are hereby notified that any perusal, use, distribution, copying or disclosure is strictly prohibited. If you have received this email in error please immediately advise us by return email at and...@arhont.com and delete and purge the email and any attachments without making a copy. - Original Message - From: Rohit Yadav rohit.ya...@shapeblue.com To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 10:55:39 AM Subject: Re: CloudMonkey 5.3 not starting on Ubuntu 14.10 Andrei, I’ve replied to your query in another thread, that tries to publish this issue and its fix for everyone on users@ and dev@. Thanks. Quick solution - remove python-pip and install pip using pip project page. On 01-Dec-2014, at 4:22 pm, Andrei Mikhailovsky and...@arhont.com wrote: Erik, this is a clean install, not an upgrade. I don't remember having issues on Ubuntu 14.04. I've also tried the easy_install method shown in the docs and that produced the same error. not really sure what you mean by the virtualenv. Andrei - Original Message - From: sebgoa run...@gmail.com To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 10:50:05 AM Subject: Re: CloudMonkey 5.3 not starting on Ubuntu 14.10 On Dec 1, 2014, at 11:44 AM, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 11:32 AM, Andrei Mikhailovsky and...@arhont.com wrote: Hi guys, I am having issues starting cloudmonkey on ubuntu 14.10. I get the following error: $ cloudmonkey Import error in cloudmonkey.cloudmonkey : No module named packages I have the same on CentOS 6.6, cloudmonkey installed with pip Have you tried with virtualenv ? Are you upgrading ? -- Erik 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: CloudMonkey 5.3 not starting on Ubuntu 14.10
Hi Erik, You’re missing the point, the email I sent for today is only for Ubuntu 14.04/14.10 users. Please find my reply in-line; On 01-Dec-2014, at 4:23 pm, Erik Weber terbol...@gmail.com wrote: Nope, all I've tried is: pip install cloudmonkey This was a fresh machine, so no upgrade. Stock CentOS 6.6. After doing yum remove python-pip, and installing pip as per the docs Rohit sent, and then doing: pip install --force-reinstall -U cloudmonkey, i now get: Traceback (most recent call last): File /usr/bin/cloudmonkey, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.6/site-packages/pkg_resources.py, line 2655, in module working_set.require(__requires__) File /usr/lib/python2.6/site-packages/pkg_resources.py, line 648, in require needed = self.resolve(parse_requirements(requirements)) File /usr/lib/python2.6/site-packages/pkg_resources.py, line 546, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: requests On CentOS based, install python-setuptools and pip or python-pip. Try this: pip install requests pip install --upgrade cloudmonkey This works for me on Fedora. 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.
[GitHub] cloudstack pull request: CLOUDSTACK-7404: Failed to start an insta...
GitHub user llambiel opened a pull request: https://github.com/apache/cloudstack/pull/49 CLOUDSTACK-7404: Failed to start an instance when originating template h... CLOUDSTACK-7404: Failed to start an instance when originating template has been deleted You can merge this pull request into a Git repository by running: $ git pull https://github.com/exoscale/cloudstack CLOUDSTACK-7404 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/49.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 #49 commit 0e7e7f893d685cdf90be9a7196f954c9b541bf75 Author: Loic Lambiel l...@exoscale.ch Date: 2014-12-01T11:02:56Z CLOUDSTACK-7404: Failed to start an instance when originating template has been deleted --- 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. ---
Build failed in Jenkins: build-master #1986
See http://jenkins.buildacloud.org/job/build-master/1986/changes Changes: [w.zhou] Add 'View Instances' in template/iso details view -- [...truncated 1712 lines...] [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-engine-orchestration --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-engine-network --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-usage --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-engine-network --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-master/ws/engine/network/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-engine-network --- [INFO] Compiling 1 source file to http://jenkins.buildacloud.org/job/build-master/ws/engine/network/target/classes [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-engine-orchestration --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-usage --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-engine-orchestration --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-engine-orchestration --- [INFO] Executing tasks main: [copy] Copying 2 files to http://jenkins.buildacloud.org/job/build-master/ws/usage/target/transformed [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-usage --- [debug] execute contextualize [INFO] Compiling 68 source files to http://jenkins.buildacloud.org/job/build-master/ws/engine/orchestration/target/classes [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ cloud-usage --- [INFO] Compiling 19 source files to http://jenkins.buildacloud.org/job/build-master/ws/usage/target/classes [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ cloud-engine-network --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-master/ws/engine/network/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ cloud-engine-network --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ cloud-engine-network --- [INFO] Surefire report directory: http://jenkins.buildacloud.org/job/build-master/ws/engine/network/target/surefire-reports --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] Starting audit... Audit done. [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-server --- [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] http://jenkins.buildacloud.org/job/build-master/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[45,23] error: cannot find symbol [ERROR] symbol: class StatsCollector location: package com.cloud.server http://jenkins.buildacloud.org/job/build-master/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[249,39] error: cannot find symbol [ERROR] symbol: variable StatsCollector location: class UsageManagerImpl http://jenkins.buildacloud.org/job/build-master/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[250,109] error: cannot find symbol [ERROR] symbol: variable StatsCollector location: class UsageManagerImpl http://jenkins.buildacloud.org/job/build-master/ws/usage/src/com/cloud/usage/UsageManagerImpl.java:[251,39] error: cannot find symbol [INFO] 4 errors [INFO] - [INFO] [INFO] --- maven-antrun-plugin:1.7:run (generate-resource) @ cloud-server --- [INFO] Executing tasks main: [copy] Copying 3 files to http://jenkins.buildacloud.org/job/build-master/ws/server/target/conf [copy] Copying 1 file to http://jenkins.buildacloud.org/job/build-master/ws/server/target/conf [INFO] Executed tasks [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cloud-server --- [debug] execute contextualize [INFO] Using 'UTF-8'
RE: root resize support in the UI
Andrija, You did understand me correctly. I wish that for the customer disk offer could be customizable. And not just for KVM hypervisor. Particularly now I am interested in Xen and VmWare. CS admin should not have set of templates that differs only on root partition size. Swap partition can be (theoretically) located as another DATA disk and be re-sizable with existing functionality. How hard is to achieve such a requirement? Are these requirements something unusual and I should do it other way? For example we say to the customer, that you have unallocated space if you select different size and extend partition by yourself? Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 12:06 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Vadim, not sure if I understand corrrectly - but you have i.e. 10GB template. you provision new VM with different size i.e. 50GB, and then after the instance is UP and running - there is just 40GB of additional unalocated space inside VM/disk, so admin need to resize partition and resize FS... ? I have been manually using qemu-img to resize some volumes (update the size inside DB) and then boot VM and do inside VM work of resizing stuff... If we only increase disk by qemu-img and update the DB - than no more admin-manual hacks needed - and we have consistent solution, that works across all platforms. And to support resize inside differente OS-es by ACS (partitions and FS) - seems pretty impossible for me, except for basic templates that have 1 partition, and i.e. no swap partition, etc...we loose consistency here completely... On 1 December 2014 at 10:33, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: But that means user can not create desired volume during instance set-up. If we would like to have, for example, VM with disk offers from 5-100Gb I need to create dozen of same templates that differ only at root size. Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 11:06 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Exactly, there may be more than 1 partion on that 1 drive.. So just increase disk size, and let administaror handle the inside VM job On 1 December 2014 at 09:34, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is not feasible. It's not given that you want to resize a partition or which one, just because you resize the disk. Thus it's not feasible to assume that the orchestration layer should be capable of doing it. -- Erik -- Andrija Panić -- Andrija Panić
Review Request 28549: CLOUDSTACK-7993: Code enhancement - test_egress_fw_rules.py - Removing unncessary waits
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28549/ --- Review request for cloudstack and SrikanteswaraRao Talluri. Bugs: CLOUDSTACK-7993 https://issues.apache.org/jira/browse/CLOUDSTACK-7993 Repository: cloudstack-git Description --- All test cases in this test suite wait for vm expungement time period after destroying VMs. It is not necessary as now th VM is destroyed by default from Marvin with expunge parameter as True, hence it will be immediately destroyed and expunged. Diffs - test/integration/component/test_egress_fw_rules.py 0122e4f Diff: https://reviews.apache.org/r/28549/diff/ Testing --- Yes. Thanks, Gaurav Aradhye
Re: Cloudstack repos
Hi ChunFeng, I've updated the repository description here: https://github.com/shapeblue/cloudstack I've update on the README file the links to official Repo and something about the Github mirror to avoid confusion, since there are so many Github forks anyone could host CloudStack repo with their github account. I think people who are coming to Apache CloudStack would/should go to github.com/apache/cloudstack. On Monday 01 December 2014 04:29 PM, ChunFeng wrote: Hi Rohit, For end user , even for developers , two repos may raise some mix-up. Could you please modify the README.md file in ShapeBlue's repo by add some statements for explaination ? -- Regards, ChunFeng -- Original -- From: Rohit Yadavrohit.ya...@shapeblue.com; Date: Mon, Dec 1, 2014 07:05 PM To: devdev@cloudstack.apache.org; Subject: Re: Cloudstack repos Hi Vadim, The official repository is at https://git-wip-us.apache.org/repos/asf/cloudstack.git A mirror is available on Github which is more easy to work with, to get started I would recommend you fork the Github repository, work on it and pull/rebase using the above official repository, and send us Github Pull Requests for any code contributions: github.com/apache/cloudstack Our (ShapeBlue's) CloudStack repo on github is public for transparency purposes and to host release notes and tags of our patches. We think of our repo as a backup of CloudStack repository (that syncs faster than the github mirror using a cronjob) and we also note in its description that they should be considered as our backup only. On Monday 01 December 2014 03:42 PM, Vadim Kimlaychuk wrote: Hello Dev-s I am looking closer to the CS development process and if possible wish to contribute. I have found there are at least 2 repos for CS. One, I suppose, is official : git://git.apache.org/cloudstack.git another one is https://github.com/shapeblue/cloudstack.git Where does development take place? Are these 2 repos in sync with each other? Are there more repos where developers do their work? What is the purpose to have more of them ? Thanks for expaination, Vadim Kimlaychuk -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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. -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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
RE: Cloudstack repos
Thank you all ! Not it is clear Vadim. -Original Message- From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com] Sent: Monday, December 01, 2014 1:18 PM To: dev@cloudstack.apache.org Subject: Re: Cloudstack repos Hi ChunFeng, I've updated the repository description here: https://github.com/shapeblue/cloudstack I've update on the README file the links to official Repo and something about the Github mirror to avoid confusion, since there are so many Github forks anyone could host CloudStack repo with their github account. I think people who are coming to Apache CloudStack would/should go to github.com/apache/cloudstack. On Monday 01 December 2014 04:29 PM, ChunFeng wrote: Hi Rohit, For end user , even for developers , two repos may raise some mix-up. Could you please modify the README.md file in ShapeBlue's repo by add some statements for explaination ? -- Regards, ChunFeng -- Original -- From: Rohit Yadavrohit.ya...@shapeblue.com; Date: Mon, Dec 1, 2014 07:05 PM To: devdev@cloudstack.apache.org; Subject: Re: Cloudstack repos Hi Vadim, The official repository is at https://git-wip-us.apache.org/repos/asf/cloudstack.git A mirror is available on Github which is more easy to work with, to get started I would recommend you fork the Github repository, work on it and pull/rebase using the above official repository, and send us Github Pull Requests for any code contributions: github.com/apache/cloudstack Our (ShapeBlue's) CloudStack repo on github is public for transparency purposes and to host release notes and tags of our patches. We think of our repo as a backup of CloudStack repository (that syncs faster than the github mirror using a cronjob) and we also note in its description that they should be considered as our backup only. On Monday 01 December 2014 03:42 PM, Vadim Kimlaychuk wrote: Hello Dev-s I am looking closer to the CS development process and if possible wish to contribute. I have found there are at least 2 repos for CS. One, I suppose, is official : git://git.apache.org/cloudstack.git another one is https://github.com/shapeblue/cloudstack.git Where does development take place? Are these 2 repos in sync with each other? Are there more repos where developers do their work? What is the purpose to have more of them ? Thanks for expaination, Vadim Kimlaychuk -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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. -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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
Jenkins build is back to normal : build-master #1987
See http://jenkins.buildacloud.org/job/build-master/1987/changes
Re: root resize support in the UI
On Mon, Dec 1, 2014 at 12:09 PM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: Andrija, You did understand me correctly. I wish that for the customer disk offer could be customizable. And not just for KVM hypervisor. Particularly now I am interested in Xen and VmWare. CS admin should not have set of templates that differs only on root partition size. Swap partition can be (theoretically) located as another DATA disk and be re-sizable with existing functionality. How hard is to achieve such a requirement? Are these requirements something unusual and I should do it other way? For example we say to the customer, that you have unallocated space if you select different size and extend partition by yourself? It's not hard at all. You just need to find a developer that can spare the time to implement it in CloudStack. -- Erik
Jenkins build is back to normal : build-4.5 #185
See http://jenkins.buildacloud.org/job/build-4.5/185/changes
Re: Is issue status can only change by owner on jira system ?
ChunFeng, You can close issues once your account has access in jira. You need it? On Mon, Dec 1, 2014 at 10:21 AM, ChunFeng chunf...@domolo.com wrote: hi,all https://issues.apache.org/jira/browse/CLOUDSTACK-519 I recheck the status which 519 mentioned . The issue is not cloudstack bug . My question is : Is the issue status can only change/close by owner on jira system ? -- Regards, ChunFeng -- Daan
Re: root resize support in the UI
Vadim, Currently the ROOT resize feature is not available for hypervisors other than KVM. The developers working with these HVs are not interested in this feature a.t.m. Feel free to request this feature and stress them out. :) Based on this feature I now only use 1 template with 1 single partition in it mounted as / which cloud-init will expand to maximum during deployment. Self-resizing can also be done in Windows quite easily. I don't think it's acceptable to tell customer to deal with expanding the partition himself, so this is automated. I do not use swap, but when it is a must I use a file based swap (eg /var/swap.IMG). You could use another primary storage for swap, but IMHO this just complicated things and it's not worth it. Generally I try not to use multiple volumes for a VM, it makes life easier. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 11:09:24 Subject: RE: root resize support in the UI Andrija, You did understand me correctly. I wish that for the customer disk offer could be customizable. And not just for KVM hypervisor. Particularly now I am interested in Xen and VmWare. CS admin should not have set of templates that differs only on root partition size. Swap partition can be (theoretically) located as another DATA disk and be re-sizable with existing functionality. How hard is to achieve such a requirement? Are these requirements something unusual and I should do it other way? For example we say to the customer, that you have unallocated space if you select different size and extend partition by yourself? Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 12:06 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Vadim, not sure if I understand corrrectly - but you have i.e. 10GB template. you provision new VM with different size i.e. 50GB, and then after the instance is UP and running - there is just 40GB of additional unalocated space inside VM/disk, so admin need to resize partition and resize FS... ? I have been manually using qemu-img to resize some volumes (update the size inside DB) and then boot VM and do inside VM work of resizing stuff... If we only increase disk by qemu-img and update the DB - than no more admin-manual hacks needed - and we have consistent solution, that works across all platforms. And to support resize inside differente OS-es by ACS (partitions and FS) - seems pretty impossible for me, except for basic templates that have 1 partition, and i.e. no swap partition, etc...we loose consistency here completely... On 1 December 2014 at 10:33, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: But that means user can not create desired volume during instance set-up. If we would like to have, for example, VM with disk offers from 5-100Gb I need to create dozen of same templates that differ only at root size. Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 11:06 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Exactly, there may be more than 1 partion on that 1 drive.. So just increase disk size, and let administaror handle the inside VM job On 1 December 2014 at 09:34, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is not feasible. It's not given that you want to resize a partition or which one, just because you resize the disk. Thus it's not feasible to assume that the orchestration layer should be capable of doing it. -- Erik -- Andrija Panić -- Andrija Panić
[GitHub] cloudstack pull request: CLOUDSTACK-7404: Failed to start an insta...
Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/49#issuecomment-65053557 +1 As soon as travis passes, I'll help merge it. Thanks for sending the PR. --- 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: root resize support in the UI
ok, Nux, so you suggest, single partition layout, with some predefined usage scenario...that is definitively an option for me. On the other hand, if you have slightly complicated templates - then the only way I see is to only resize the disk qith qemu-img...(not going inside VM)... So we need to decide on the user-case scenario we find most usefull... On 1 December 2014 at 12:30, Nux! n...@li.nux.ro wrote: Vadim, Currently the ROOT resize feature is not available for hypervisors other than KVM. The developers working with these HVs are not interested in this feature a.t.m. Feel free to request this feature and stress them out. :) Based on this feature I now only use 1 template with 1 single partition in it mounted as / which cloud-init will expand to maximum during deployment. Self-resizing can also be done in Windows quite easily. I don't think it's acceptable to tell customer to deal with expanding the partition himself, so this is automated. I do not use swap, but when it is a must I use a file based swap (eg /var/swap.IMG). You could use another primary storage for swap, but IMHO this just complicated things and it's not worth it. Generally I try not to use multiple volumes for a VM, it makes life easier. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 11:09:24 Subject: RE: root resize support in the UI Andrija, You did understand me correctly. I wish that for the customer disk offer could be customizable. And not just for KVM hypervisor. Particularly now I am interested in Xen and VmWare. CS admin should not have set of templates that differs only on root partition size. Swap partition can be (theoretically) located as another DATA disk and be re-sizable with existing functionality. How hard is to achieve such a requirement? Are these requirements something unusual and I should do it other way? For example we say to the customer, that you have unallocated space if you select different size and extend partition by yourself? Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 12:06 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Vadim, not sure if I understand corrrectly - but you have i.e. 10GB template. you provision new VM with different size i.e. 50GB, and then after the instance is UP and running - there is just 40GB of additional unalocated space inside VM/disk, so admin need to resize partition and resize FS... ? I have been manually using qemu-img to resize some volumes (update the size inside DB) and then boot VM and do inside VM work of resizing stuff... If we only increase disk by qemu-img and update the DB - than no more admin-manual hacks needed - and we have consistent solution, that works across all platforms. And to support resize inside differente OS-es by ACS (partitions and FS) - seems pretty impossible for me, except for basic templates that have 1 partition, and i.e. no swap partition, etc...we loose consistency here completely... On 1 December 2014 at 10:33, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: But that means user can not create desired volume during instance set-up. If we would like to have, for example, VM with disk offers from 5-100Gb I need to create dozen of same templates that differ only at root size. Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 11:06 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Exactly, there may be more than 1 partion on that 1 drive.. So just increase disk size, and let administaror handle the inside VM job On 1 December 2014 at 09:34, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is
[GitHub] cloudstack pull request: CLOUDSTACK-7986 [F5 LB] Failed to execute...
Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/47#issuecomment-65053922 Our travis does not run noredist builds, can you confirm any build jobs (from Jenkins etc.) so I can help merge it? --- 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. ---
[GitHub] cloudstack pull request: Use the new build env on Travis
Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/43#issuecomment-65054083 Ping, should we do anything on this? --- 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: root resize support in the UI
I would like to see this for XenServer implemented. I get around this by having all my bare bone templates at 100GB...it would be nice not have to change in the DB, then catch it in from the console to expand before CS shuts it down. On Mon, Dec 1, 2014 at 6:30 AM, Nux! n...@li.nux.ro wrote: Vadim, Currently the ROOT resize feature is not available for hypervisors other than KVM. The developers working with these HVs are not interested in this feature a.t.m. Feel free to request this feature and stress them out. :) Based on this feature I now only use 1 template with 1 single partition in it mounted as / which cloud-init will expand to maximum during deployment. Self-resizing can also be done in Windows quite easily. I don't think it's acceptable to tell customer to deal with expanding the partition himself, so this is automated. I do not use swap, but when it is a must I use a file based swap (eg /var/swap.IMG). You could use another primary storage for swap, but IMHO this just complicated things and it's not worth it. Generally I try not to use multiple volumes for a VM, it makes life easier. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 11:09:24 Subject: RE: root resize support in the UI Andrija, You did understand me correctly. I wish that for the customer disk offer could be customizable. And not just for KVM hypervisor. Particularly now I am interested in Xen and VmWare. CS admin should not have set of templates that differs only on root partition size. Swap partition can be (theoretically) located as another DATA disk and be re-sizable with existing functionality. How hard is to achieve such a requirement? Are these requirements something unusual and I should do it other way? For example we say to the customer, that you have unallocated space if you select different size and extend partition by yourself? Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 12:06 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Vadim, not sure if I understand corrrectly - but you have i.e. 10GB template. you provision new VM with different size i.e. 50GB, and then after the instance is UP and running - there is just 40GB of additional unalocated space inside VM/disk, so admin need to resize partition and resize FS... ? I have been manually using qemu-img to resize some volumes (update the size inside DB) and then boot VM and do inside VM work of resizing stuff... If we only increase disk by qemu-img and update the DB - than no more admin-manual hacks needed - and we have consistent solution, that works across all platforms. And to support resize inside differente OS-es by ACS (partitions and FS) - seems pretty impossible for me, except for basic templates that have 1 partition, and i.e. no swap partition, etc...we loose consistency here completely... On 1 December 2014 at 10:33, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: But that means user can not create desired volume during instance set-up. If we would like to have, for example, VM with disk offers from 5-100Gb I need to create dozen of same templates that differ only at root size. Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 11:06 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Exactly, there may be more than 1 partion on that 1 drive.. So just increase disk size, and let administaror handle the inside VM job On 1 December 2014 at 09:34, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It seems that drive resize on hypervisor level is all that is needed, because it is far too complicated for hypervisor to be aware of all different types of partition layouts and file systems that might exist. Then upper layer (like CS) may take role of implementing different actions according to guest type and file system that have being used for particular guest. While OS type can be taken from template, FS type and partition type is information that is not stored in the database. Without it implementation is not feasible. It's not given that you want to resize a partition or which one, just because you resize
[GitHub] cloudstack pull request: Feature cenik123 vpcvrr 1.1.1
Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/33#issuecomment-65054379 Hi Karl, can you update us on what you're trying to do and how we can benefit from using packer instead of vagrant? Is packer more easy to setup and work with than Vagrant? Sorry, no one reviewed your work before. I'll ask our systemvm build system expert @lsimons to help review this along with myself since he did a fantastic job at refactoring our vagrant/veewee based build system recently. --- 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. ---
[GitHub] cloudstack pull request: Use the new build env on Travis
Github user imduffy15 commented on the pull request: https://github.com/apache/cloudstack/pull/43#issuecomment-65054605 No. It disables sudo usage so it breaks our setup. On 1 Dec 2014 11:48, Rohit Yadav notificati...@github.com wrote: Ping, should we do anything on this? â Reply to this email directly or view it on GitHub https://github.com/apache/cloudstack/pull/43#issuecomment-65054083. --- 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: root resize support in the UI
Andrija, Absolutely, everyone has their own needs. The single partition works best for us (we also implemented it in physical dedicated servers - makes p2v and v2p easy!) and it also seems to be the choice of others (official fedora/centos/ubuntu templates are like this as well). -- 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 Sent: Monday, 1 December, 2014 11:42:29 Subject: Re: root resize support in the UI ok, Nux, so you suggest, single partition layout, with some predefined usage scenario...that is definitively an option for me. On the other hand, if you have slightly complicated templates - then the only way I see is to only resize the disk qith qemu-img...(not going inside VM)... So we need to decide on the user-case scenario we find most usefull... On 1 December 2014 at 12:30, Nux! n...@li.nux.ro wrote: Vadim, Currently the ROOT resize feature is not available for hypervisors other than KVM. The developers working with these HVs are not interested in this feature a.t.m. Feel free to request this feature and stress them out. :) Based on this feature I now only use 1 template with 1 single partition in it mounted as / which cloud-init will expand to maximum during deployment. Self-resizing can also be done in Windows quite easily. I don't think it's acceptable to tell customer to deal with expanding the partition himself, so this is automated. I do not use swap, but when it is a must I use a file based swap (eg /var/swap.IMG). You could use another primary storage for swap, but IMHO this just complicated things and it's not worth it. Generally I try not to use multiple volumes for a VM, it makes life easier. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 11:09:24 Subject: RE: root resize support in the UI Andrija, You did understand me correctly. I wish that for the customer disk offer could be customizable. And not just for KVM hypervisor. Particularly now I am interested in Xen and VmWare. CS admin should not have set of templates that differs only on root partition size. Swap partition can be (theoretically) located as another DATA disk and be re-sizable with existing functionality. How hard is to achieve such a requirement? Are these requirements something unusual and I should do it other way? For example we say to the customer, that you have unallocated space if you select different size and extend partition by yourself? Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 12:06 PM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Vadim, not sure if I understand corrrectly - but you have i.e. 10GB template. you provision new VM with different size i.e. 50GB, and then after the instance is UP and running - there is just 40GB of additional unalocated space inside VM/disk, so admin need to resize partition and resize FS... ? I have been manually using qemu-img to resize some volumes (update the size inside DB) and then boot VM and do inside VM work of resizing stuff... If we only increase disk by qemu-img and update the DB - than no more admin-manual hacks needed - and we have consistent solution, that works across all platforms. And to support resize inside differente OS-es by ACS (partitions and FS) - seems pretty impossible for me, except for basic templates that have 1 partition, and i.e. no swap partition, etc...we loose consistency here completely... On 1 December 2014 at 10:33, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: But that means user can not create desired volume during instance set-up. If we would like to have, for example, VM with disk offers from 5-100Gb I need to create dozen of same templates that differ only at root size. Vadim. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Monday, December 01, 2014 11:06 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Exactly, there may be more than 1 partion on that 1 drive.. So just increase disk size, and let administaror handle the inside VM job On 1 December 2014 at 09:34, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 9:23 AM, Vadim Kimlaychuk vadim.kimlayc...@elion.ee wrote: I have done root partition resize under XenServer exactly as you described - resized drive and then using system tools on guest VM like fdisk, lvextend and ext2resize changed the size of the root. It
Jenkins build is unstable: simulator-singlerun #720
See http://jenkins.buildacloud.org/job/simulator-singlerun/720/changes
Build failed in Jenkins: build-master-noredist #3880
See http://jenkins.buildacloud.org/job/build-master-noredist/3880/changes Changes: [Rohit Yadav] README: add information about official git repository [w.zhou] CLOUDSTACK-7983: Create Disk/Service Offering for Domain Admin [w.zhou] CLOUDSTACK-7404: Failed to start an instance when originating template has been deleted -- [...truncated 8521 lines...] --- Running com.cloud.network.element.CiscoVnmcElementTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.369 sec Running org.apache.cloudstack.network.contrail.model.VirtualNetworkModelTest log4j:WARN No appenders could be found for logger (com.cloud.network.element.CiscoVnmcElement). 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: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.583 sec Running com.cloud.network.resource.CiscoVnmcResourceTest Success Success Success Success Success Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.113 sec Running com.cloud.network.cisco.CiscoVnmcConnectionTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.002 sec Results : Tests run: 14, Failures: 0, Errors: 0, Skipped: 1 [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ cloud-plugin-network-cisco-vnmc --- [INFO] Building jar: http://jenkins.buildacloud.org/job/build-master-noredist/ws/plugins/network-elements/cisco-vnmc/target/cloud-plugin-network-cisco-vnmc-4.6.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-plugin-network-cisco-vnmc --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-plugin-network-cisco-vnmc --- [INFO] Installing http://jenkins.buildacloud.org/job/build-master-noredist/ws/plugins/network-elements/cisco-vnmc/target/cloud-plugin-network-cisco-vnmc-4.6.0-SNAPSHOT.jar to /jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-network-cisco-vnmc/4.6.0-SNAPSHOT/cloud-plugin-network-cisco-vnmc-4.6.0-SNAPSHOT.jar [INFO] Installing http://jenkins.buildacloud.org/job/build-master-noredist/ws/plugins/network-elements/cisco-vnmc/pom.xml to /jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-network-cisco-vnmc/4.6.0-SNAPSHOT/cloud-plugin-network-cisco-vnmc-4.6.0-SNAPSHOT.pom Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.184 sec Results : Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ cloud-plugin-network-contrail --- [INFO] Building jar: http://jenkins.buildacloud.org/job/build-master-noredist/ws/plugins/network-elements/juniper-contrail/target/cloud-plugin-network-contrail-4.6.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-plugin-network-contrail --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-plugin-network-contrail --- [INFO] Installing http://jenkins.buildacloud.org/job/build-master-noredist/ws/plugins/network-elements/juniper-contrail/target/cloud-plugin-network-contrail-4.6.0-SNAPSHOT.jar to /jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-network-contrail/4.6.0-SNAPSHOT/cloud-plugin-network-contrail-4.6.0-SNAPSHOT.jar [INFO] Installing http://jenkins.buildacloud.org/job/build-master-noredist/ws/plugins/network-elements/juniper-contrail/pom.xml to /jenkins/.m2/repository/org/apache/cloudstack/cloud-plugin-network-contrail/4.6.0-SNAPSHOT/cloud-plugin-network-contrail-4.6.0-SNAPSHOT.pom [INFO] Building zip: http://jenkins.buildacloud.org/job/build-master-noredist/ws/systemvm/target/systemvm.zip [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ cloud-awsapi --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory http://jenkins.buildacloud.org/job/build-master-noredist/ws/awsapi/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ cloud-awsapi --- [INFO] Compiling 5 source files to http://jenkins.buildacloud.org/job/build-master-noredist/ws/awsapi/target/test-classes [INFO] [INFO] --- maven-resources-plugin:2.5:copy-resources (copy-resources) @ cloud-systemvm --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 1 resource [INFO] [INFO] --- exec-maven-plugin:1.2.1:exec (default) @ cloud-systemvm --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-systemvm --- [INFO] Installing http://jenkins.buildacloud.org/job/build-master-noredist/ws/systemvm/pom.xml to /jenkins/.m2/repository/org/apache/cloudstack/cloud-systemvm/4.6.0-SNAPSHOT/cloud-systemvm-4.6.0-SNAPSHOT.pom [INFO] Installing
New Defects reported by Coverity Scan for cloudstack
Hi,
Please find the latest report on new defect(s) introduced to cloudstack found
with Coverity Scan.
6 new defect(s) introduced to cloudstack found with Coverity Scan.
5 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent
build analyzed by Coverity Scan.
New defect(s) Reported-by: Coverity Scan
Showing 6 of 6 defect(s)
** CID 1256278: Dm: Dubious method used (FB.DM_DEFAULT_ENCODING)
/server/src/com/cloud/user/AccountManagerImpl.java: 2061 in
com.cloud.user.AccountManagerImpl.authenticateUser(java.lang.String,
java.lang.String, java.lang.Long, java.net.InetAddress, java.util.Map)()
/server/src/com/cloud/user/AccountManagerImpl.java: 2057 in
com.cloud.user.AccountManagerImpl.authenticateUser(java.lang.String,
java.lang.String, java.lang.Long, java.net.InetAddress, java.util.Map)()
/server/src/com/cloud/user/AccountManagerImpl.java: 2059 in
com.cloud.user.AccountManagerImpl.authenticateUser(java.lang.String,
java.lang.String, java.lang.Long, java.net.InetAddress, java.util.Map)()
** CID 1256277: SBSC: String concatenation in loop using + operator
(FB.SBSC_USE_STRINGBUFFER_CONCATENATION)
/server/src/com/cloud/user/AccountManagerImpl.java: 2042 in
com.cloud.user.AccountManagerImpl.authenticateUser(java.lang.String,
java.lang.String, java.lang.Long, java.net.InetAddress, java.util.Map)()
** CID 1256276: WMI: Inefficient Map Iterator (FB.WMI_WRONG_MAP_ITERATOR)
/server/src/com/cloud/user/AccountManagerImpl.java: 2013 in
com.cloud.user.AccountManagerImpl.authenticateUser(java.lang.String,
java.lang.String, java.lang.Long, java.net.InetAddress, java.util.Map)()
** CID 1256275: Resource leak (RESOURCE_LEAK)
/engine/schema/src/com/cloud/upgrade/dao/Upgrade442to450.java: 237 in
com.cloud.upgrade.dao.Upgrade442to450.updateSystemVmTemplates(java.sql.Connection)()
/engine/schema/src/com/cloud/upgrade/dao/Upgrade442to450.java: 291 in
com.cloud.upgrade.dao.Upgrade442to450.updateSystemVmTemplates(java.sql.Connection)()
/engine/schema/src/com/cloud/upgrade/dao/Upgrade442to450.java: 266 in
com.cloud.upgrade.dao.Upgrade442to450.updateSystemVmTemplates(java.sql.Connection)()
** CID 1256274: Resource leak on an exceptional path (RESOURCE_LEAK)
/engine/schema/src/com/cloud/upgrade/dao/Upgrade442to450.java: 115 in
com.cloud.upgrade.dao.Upgrade442to450.upgradeMemoryOfVirtualRoutervmOffering(java.sql.Connection)()
** CID 1256273: Resource leak on an exceptional path (RESOURCE_LEAK)
/engine/schema/src/com/cloud/upgrade/dao/Upgrade442to450.java: 157 in
com.cloud.upgrade.dao.Upgrade442to450.upgradeMemoryOfInternalLoadBalancervmOffering(java.sql.Connection)()
*** CID 1256278: Dm: Dubious method used (FB.DM_DEFAULT_ENCODING)
/server/src/com/cloud/user/AccountManagerImpl.java: 2061 in
com.cloud.user.AccountManagerImpl.authenticateUser(java.lang.String,
java.lang.String, java.lang.Long, java.net.InetAddress, java.util.Map)()
2055
2056 Mac mac = Mac.getInstance(HmacSHA1);
2057 SecretKeySpec keySpec = new
SecretKeySpec(key.getBytes(), HmacSHA1);
2058 mac.init(keySpec);
2059 mac.update(unsignedRequest.getBytes());
2060 byte[] encryptedBytes = mac.doFinal();
CID 1256278: Dm: Dubious method used (FB.DM_DEFAULT_ENCODING)
Found reliance on default encoding: new String(byte[])
2061 String computedSignature = new
String(Base64.encodeBase64(encryptedBytes));
2062 boolean equalSig = signature.equals(computedSignature);
2063 if (!equalSig) {
2064 s_logger.info(User signature: + signature +
is not equaled to computed signature: + computedSignature);
2065 } else {
2066 user = _userAccountDao.getUserAccount(username,
domainId);
/server/src/com/cloud/user/AccountManagerImpl.java: 2057 in
com.cloud.user.AccountManagerImpl.authenticateUser(java.lang.String,
java.lang.String, java.lang.Long, java.net.InetAddress, java.util.Map)()
2051 return null;
2052 }
2053
2054 unsignedRequest = unsignedRequest.toLowerCase();
2055
2056 Mac mac = Mac.getInstance(HmacSHA1);
CID 1256278: Dm: Dubious method used (FB.DM_DEFAULT_ENCODING)
Found reliance on default encoding: String.getBytes()
2057 SecretKeySpec keySpec = new
SecretKeySpec(key.getBytes(), HmacSHA1);
2058 mac.init(keySpec);
2059 mac.update(unsignedRequest.getBytes());
2060 byte[] encryptedBytes = mac.doFinal();
2061 String computedSignature = new
String(Base64.encodeBase64(encryptedBytes));
2062 boolean equalSig = signature.equals(computedSignature);
[GitHub] cloudstack pull request: CLOUDSTACK-7404: Failed to start an insta...
Github user bhaisaab commented on the pull request: https://github.com/apache/cloudstack/pull/49#issuecomment-65058250 Hi, I just saw Wei checked in the fix from 4.3/4.4 on master. I've applied the same on 4.5 branch so we don't lose your commit. Since, it's already in all 4.3+ branches, please close this PR. --- 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. ---
[GitHub] cloudstack pull request: Use the new build env on Travis
Github user bhaisaab commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/43#discussion_r21085810 --- Diff: .travis.yml --- @@ -16,27 +16,38 @@ # under the License. language: java + +jdk: + - oraclejdk7 + cache: directories: - - $HOME/.cache -jdk: -- oraclejdk7 -notifications: - email: false +- $HOME/.cache + +sudo: false --- End diff -- @imduffy15 will it work if we set sudo: true ? I'm not sure what benefit this gives, will really get us more RAM/CPU/Network only with syntactic refactoring? --- 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. ---
Jenkins build is back to normal : build-master-noredist #3881
See http://jenkins.buildacloud.org/job/build-master-noredist/3881/
[DISCUSS] Automatic usage reporting / call-home for CloudStack
Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? Wido [0]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/reporter [1]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=reporter/usage-report-collector.py;h=500a4d284b5172fd93acea08f5460cfff5520855;hb=reporter
Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack
On Dec 1, 2014, at 8:08 AM, Wido den Hollander w...@widodh.nl wrote: Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? We should ask users@ as well. I am +1 on this, Wido [0]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/reporter [1]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=reporter/usage-report-collector.py;h=500a4d284b5172fd93acea08f5460cfff5520855;hb=reporter
Jenkins build is still unstable: simulator-singlerun #721
See http://jenkins.buildacloud.org/job/simulator-singlerun/changes
Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack
On Mon, Dec 1, 2014 at 2:15 PM, Sebastien Goasguen run...@gmail.com wrote: On Dec 1, 2014, at 8:08 AM, Wido den Hollander w...@widodh.nl wrote: Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? We should ask users@ as well. I am +1 on this, As a cloudstack user I don't have any problem with this, +1. -- Erik
Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack
+1 On 1 December 2014 at 14:31, Erik Weber terbol...@gmail.com wrote: On Mon, Dec 1, 2014 at 2:15 PM, Sebastien Goasguen run...@gmail.com wrote: On Dec 1, 2014, at 8:08 AM, Wido den Hollander w...@widodh.nl wrote: Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? We should ask users@ as well. I am +1 on this, As a cloudstack user I don't have any problem with this, +1. -- Erik -- Andrija Panić
Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack
On 12/01/2014 02:15 PM, Sebastien Goasguen wrote: On Dec 1, 2014, at 8:08 AM, Wido den Hollander w...@widodh.nl wrote: Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? We should ask users@ as well. Yes, that is probably a good idea. First I'd like to have the politics set before we take it to users. In the end I'd like to see a VOTE coming up for this feature to go into CloudStack. Wido I am +1 on this, Wido [0]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/reporter [1]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=reporter/usage-report-collector.py;h=500a4d284b5172fd93acea08f5460cfff5520855;hb=reporter
Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack
+1, good job! -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Wido den Hollander w...@widodh.nl To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 13:08:02 Subject: [DISCUSS] Automatic usage reporting / call-home for CloudStack Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? Wido [0]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/reporter [1]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=reporter/usage-report-collector.py;h=500a4d284b5172fd93acea08f5460cfff5520855;hb=reporter
[GitHub] cloudstack pull request: CLOUDSTACK-7404: Failed to start an insta...
Github user llambiel closed the pull request at: https://github.com/apache/cloudstack/pull/49 --- 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. ---
Build failed in Jenkins: build-master-noredist #3885
See http://jenkins.buildacloud.org/job/build-master-noredist/3885/ -- [...truncated 2566 lines...] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.181 sec Running com.cloud.servlet.ConsoleProxyServletTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running com.cloud.resourcelimit.ResourceLimitManagerImplTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running com.cloud.network.firewall.FirewallManagerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.001 sec Running com.cloud.network.ExternalLoadBalancerDeviceManagerImplTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.566 sec Running com.cloud.network.element.VirtualRouterElementTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 0.053 sec Running com.cloud.network.UpdatePhysicalNetworkTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.184 sec Running com.cloud.network.CreatePrivateNetworkTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.069 sec Running com.cloud.network.NetworkModelTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.043 sec Running com.cloud.network.router.NetworkHelperImplTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec Running com.cloud.network.router.RouterControlHelperTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec Running com.cloud.network.router.VirtualNetworkApplianceManagerImplTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.272 sec Running com.cloud.network.security.SecurityGroupManagerImplTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.44 sec Running com.cloud.network.security.SecurityGroupQueueTest Total jobs dequeued = 10, num queued=1001 queue current size=991 Num Vms= 50 Queue size = 50 Num Vms= 2 Queue size = 2 time=252 ms Num Vms= 5000 Queue size = 5000 time=1484 ms Num Vms= 1 Queue size = 1 time=0 ms Num Vms= 100 Queue size = 100 time=909 ms Total jobs dequeued = 10, num queued=1000 queue current size=991 Tests run: 4, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 3.128 sec FAILURE! Running com.cloud.network.vpc.VpcManagerImplTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec Running com.cloud.network.DedicateGuestVlanRangesTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec Running com.cloud.network.lb.AssignLoadBalancerTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.085 sec Running com.cloud.network.lb.UpdateLoadBalancerTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.061 sec Running com.cloud.network.dao.NetworkDaoTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running com.cloud.vm.FirstFitPlannerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.664 sec Running com.cloud.vm.DeploymentPlanningManagerImplTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.893 sec Running com.cloud.vm.snapshot.VMSnapshotManagerTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.148 sec Running com.cloud.vm.UserVmManagerTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.423 sec Running com.cloud.configuration.ValidateIpRangeTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec Running com.cloud.configuration.ConfigurationManagerTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.068 sec Running com.cloud.server.ConfigurationServerImplTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running com.cloud.template.TemplateManagerImplTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running com.cloud.vpc.Site2SiteVpnTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.978 sec Running com.cloud.vpc.NetworkACLServiceTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.223 sec Running com.cloud.vpc.NetworkACLManagerTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.247 sec Running com.cloud.storage.VolumeApiServiceImplTest Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.133 sec Running com.cloud.user.AccountManagerImplTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.144 sec Running com.cloud.api.ApiServletTest Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec Running com.cloud.api.ApiResponseHelperTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec Running com.cloud.api.dispatch.ParamGenericValidationWorkerTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running com.cloud.api.dispatch.DispatchChainFactoryTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running
Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack
On 12/01/2014 04:00 PM, Nux! wrote: In addition: this should be opt-out, but clearly specified in the release notes, as well as visible in the UI. But where do we display this in the UI? I don't think we have a mechanism to show a one-time message after a upgrade. Do we? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Nux! n...@li.nux.ro To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 13:52:35 Subject: Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack +1, good job! -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Wido den Hollander w...@widodh.nl To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 13:08:02 Subject: [DISCUSS] Automatic usage reporting / call-home for CloudStack Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? Wido [0]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/reporter [1]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=reporter/usage-report-collector.py;h=500a4d284b5172fd93acea08f5460cfff5520855;hb=reporter
Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack
Hm, after an upgrade it might be tricky. Perhaps display it here somehow http://img.nux.ro/3hH-callhome.png Perhaps some UI/javascript specialist can help us here ... Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Wido den Hollander w...@widodh.nl To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 15:05:55 Subject: Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack On 12/01/2014 04:00 PM, Nux! wrote: In addition: this should be opt-out, but clearly specified in the release notes, as well as visible in the UI. But where do we display this in the UI? I don't think we have a mechanism to show a one-time message after a upgrade. Do we? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Nux! n...@li.nux.ro To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 13:52:35 Subject: Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack +1, good job! -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Wido den Hollander w...@widodh.nl To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 13:08:02 Subject: [DISCUSS] Automatic usage reporting / call-home for CloudStack Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? Wido [0]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/reporter [1]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=reporter/usage-report-collector.py;h=500a4d284b5172fd93acea08f5460cfff5520855;hb=reporter
Jenkins build is back to stable : simulator-singlerun #722
See http://jenkins.buildacloud.org/job/simulator-singlerun/722/changes
Jenkins build is back to normal : build-master-noredist #3886
See http://jenkins.buildacloud.org/job/build-master-noredist/3886/changes
RE: [DISCUSS] Automatic usage reporting / call-home for CloudStack
1+ from a user -Original Message- From: Wido den Hollander [mailto:w...@widodh.nl] Sent: Monday, December 01, 2014 10:21 AM To: dev@cloudstack.apache.org Subject: Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack On 12/01/2014 04:12 PM, Nux! wrote: Hm, after an upgrade it might be tricky. Perhaps display it here somehow http://img.nux.ro/3hH-callhome.png Perhaps some UI/javascript specialist can help us here ... Good idea. In that Menu we probably need a Call-Home link pointing to http://cloudstack.apache.org/callhome.html (doesn't exist yet!) Wido Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Wido den Hollander w...@widodh.nl To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 15:05:55 Subject: Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack On 12/01/2014 04:00 PM, Nux! wrote: In addition: this should be opt-out, but clearly specified in the release notes, as well as visible in the UI. But where do we display this in the UI? I don't think we have a mechanism to show a one-time message after a upgrade. Do we? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Nux! n...@li.nux.ro To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 13:52:35 Subject: Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack +1, good job! -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Wido den Hollander w...@widodh.nl To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 13:08:02 Subject: [DISCUSS] Automatic usage reporting / call-home for CloudStack Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? Wido [0]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlo g;h=refs/heads/reporter [1]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f= reporter/usage-report-collector.py;h=500a4d284b5172fd93acea08f5460 cfff5520855;hb=reporter
Re: root resize support in the UI
Just chiming in: I un-commented the Root Disk field in the Instance Wizard in our 4.4 deployment. Works fine with KVM / Ceph RBD. The logic we see is: A) If specified size is smaller than template size, throw an alert. B) If specified size is larger than template size then deploy root disk with specified size. C) If nothing is specified (default if the box isn't enabled) then deploy root disk with same size as template. This works with KVM and the RBD resize logic I committed a few months ago. I can't speak for how it works with Xen/VMware or other primary storage backends. Thank You, Logan Barfield Tranquil Hosting On Mon, Dec 1, 2014 at 11:34 AM, Matthew Midgett clouds...@trick-solutions.com.invalid wrote: 1+ from me for XenServer root disk resize for template deployments! I'm going with Nux on the single partition scheme and I want my root disk under 2GB as most all of my deployments are minimal systems. This makes the journey from sec storage to primary storage quite a bit faster. I need to deploy and resize and be running in under 60 seconds if possible to keep my users from sitting around waiting. I will be using hostbill in front of my ACS and they offer these sliders for choosing how much resources you want. Users really like this and if they deploy my 2gb template I'd like to be able to give them that 50GB disk they ask for without using a data disk. If cloud-init can do this then I as a user would develop my templates around the file system layout that it supports. EXT3,EXT4,BTRFS or LVMI honestly don't care for using LVM in a Virtual Machine, it's just one more layer of complexity on a disk that doesn’t need to be there. Most all Linux file systems can support online resize without LVM so I would consider not using it to simplify cloud-init resize. Just my 2cents Matthew Midgett -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Monday, December 01, 2014 7:06 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Andrija, Absolutely, everyone has their own needs. The single partition works best for us (we also implemented it in physical dedicated servers - makes p2v and v2p easy!) and it also seems to be the choice of others (official fedora/centos/ubuntu templates are like this as well). -- 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 Sent: Monday, 1 December, 2014 11:42:29 Subject: Re: root resize support in the UI ok, Nux, so you suggest, single partition layout, with some predefined usage scenario...that is definitively an option for me. On the other hand, if you have slightly complicated templates - then the only way I see is to only resize the disk qith qemu-img...(not going inside VM)... So we need to decide on the user-case scenario we find most usefull... On 1 December 2014 at 12:30, Nux! n...@li.nux.ro wrote: Vadim, Currently the ROOT resize feature is not available for hypervisors other than KVM. The developers working with these HVs are not interested in this feature a.t.m. Feel free to request this feature and stress them out. :) Based on this feature I now only use 1 template with 1 single partition in it mounted as / which cloud-init will expand to maximum during deployment. Self-resizing can also be done in Windows quite easily. I don't think it's acceptable to tell customer to deal with expanding the partition himself, so this is automated. I do not use swap, but when it is a must I use a file based swap (eg /var/swap.IMG). You could use another primary storage for swap, but IMHO this just complicated things and it's not worth it. Generally I try not to use multiple volumes for a VM, it makes life easier. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 11:09:24 Subject: RE: root resize support in the UI Andrija, You did understand me correctly. I wish that for the customer disk offer could be customizable. And not just for KVM hypervisor. Particularly now I am interested in Xen and VmWare. CS admin should not have set of templates that differs only on root partition size. Swap partition can be (theoretically) located as another DATA disk and be re-sizable with existing functionality. How hard is to achieve such a requirement? Are these requirements something unusual and I should do it other way? For example we say to the customer, that you have unallocated space if you select different size and extend partition by yourself? Vadim.
Re: git commit: updated refs/heads/master to ae0cb82
Hi Hugo, On Mon, Dec 1, 2014 at 7:27 PM, h...@apache.org wrote: Repository: cloudstack Updated Branches: refs/heads/master ce2b2a1fc - ae0cb8279 Both scripts should be able to use the data-server introduced in 4.4 What does this commit fix? Sorry, I've no idea about the data-server introduced in 4.4. Verbose git commit messages are always welcome. Regards. Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/ae0cb827 Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/ae0cb827 Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/ae0cb827 Branch: refs/heads/master Commit: ae0cb8279225db0b6d0f642a546792ba6f3f1117 Parents: ce2b2a1 Author: Hugo Trippaers htrippa...@schubergphilis.com Authored: Fri Nov 28 14:08:47 2014 +0100 Committer: Hugo Trippaers htrippa...@schubergphilis.com Committed: Mon Dec 1 14:56:58 2014 +0100 -- setup/bindir/cloud-set-guest-password.in | 69 +-- setup/bindir/cloud-set-guest-sshkey.in | 36 ++ 2 files changed, 48 insertions(+), 57 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/ae0cb827/setup/bindir/cloud-set-guest-password.in -- diff --git a/setup/bindir/cloud-set-guest-password.in b/setup/bindir/ cloud-set-guest-password.in index 4c7c575..2c7304b 100755 --- a/setup/bindir/cloud-set-guest-password.in +++ b/setup/bindir/cloud-set-guest-password.in @@ -40,45 +40,44 @@ for DHCP_FILE in $DHCP_FOLDERS; do if [ -n $PASSWORD_SERVER_IP ]; then logger -t cloud Found password server IP $PASSWORD_SERVER_IP in $DHCP_FILE - logger -t cloud Sending request to password server at $PASSWORD_SERVER_IP - - password=$(wget -q -t 3 -T 20 -O - --header DomU_Request: send_my_password $PASSWORD_SERVER_IP:$PASSWORD_SERVER_PORT) - - if [ $? -eq 0 ]; then - password=$(echo $password | tr -d '\r') - logger -t cloud Got response from server at $PASSWORD_SERVER_IP - - case $password in - ) - logger -t cloud Password server at $PASSWORD_SERVER_IP did not have any password for the VM - continue - ;; - bad_request) - logger -t cloud VM sent an invalid request to password server at $PASSWORD_SERVER_IP - error_count=$((error_count+1)) - continue - ;; - saved_password) - logger -t cloud VM has already saved a password from the password server at $PASSWORD_SERVER_IP - continue - ;; - *) - logger -t cloud VM got a valid password from server at $PASSWORD_SERVER_IP - password_received=1 - break - ;; - esac - else - logger -t cloud Failed to send request to password server at $PASSWORD_SERVER_IP - error_count=$((error_count+1)) - fi - else - logger -t cloud Could not find password server IP in $DHCP_FILE - error_count=$((error_count+1)) +break fi fi done +if [ -z $PASSWORD_SERVER_IP ] ; then + logger -t cloud Unable to determine the password server, falling back to data-server + PASSWORD_SERVER_IP=data-server +fi + +logger -t cloud Sending request to password server at $PASSWORD_SERVER_IP +password=$(wget -q -t 3 -T 20 -O - --header DomU_Request: send_my_password http://$PASSWORD_SERVER_IP:$PASSWORD_SERVER_PORT) +if [ $? -eq 0 ]; then +password=$(echo $password | tr -d '\r') +logger -t cloud Got response from server at $PASSWORD_SERVER_IP + +case $password in +) +logger -t cloud Password server at $PASSWORD_SERVER_IP did not have any password for the VM +;; +
Re: git commit: updated refs/heads/reporter to 026efd3
On Mon, Dec 1, 2014 at 6:37 PM, wid...@apache.org wrote:
Repository: cloudstack
Updated Branches:
refs/heads/reporter [created] 026efd344
Proposal of a Usage Reporter / call-home functionality for CloudStack
With this commit the Management Server will be default generate a
anonymous Usage
report every 7 (seven) days and submit this information back to the Apache
CloudStack project.
These anonymous reports do NOT contain any information about Instance
names, subnets, etc. It only
contains numbers about how CloudStack is being used.
This information is vital for the project to gain more insight in how
CloudStack is being used.
Users can turn the reporting off by setting usage.report.interval to 0
(zero)
Great initiative Wido! Do we have a data collection service that is already
running with ASF or you're building one?
Regards.
Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/026efd34
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/026efd34
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/026efd34
Branch: refs/heads/reporter
Commit: 026efd344452cef806f2475009bf690f5c2cbf9a
Parents: 449d123
Author: Wido den Hollander w...@widodh.nl
Authored: Thu Nov 20 14:43:33 2014 +0100
Committer: Wido den Hollander w...@widodh.nl
Committed: Mon Dec 1 14:00:10 2014 +0100
--
reporter/README.md | 18 +
reporter/usage-report-collector.py | 64 +++
server/pom.xml | 10 +
.../spring-server-core-managers-context.xml | 2 +
server/src/com/cloud/configuration/Config.java | 5 +-
.../apache/cloudstack/report/UsageReporter.java | 403 +++
setup/db/db/schema-450to460.sql | 4 +-
7 files changed, 504 insertions(+), 2 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cloudstack/blob/026efd34/reporter/README.md
--
diff --git a/reporter/README.md b/reporter/README.md
new file mode 100644
index 000..6453fa4
--- /dev/null
+++ b/reporter/README.md
@@ -0,0 +1,18 @@
+# CloudStack Usage Report
+
+This directory contains the CloudStack reporter webservice used by the
Apache CloudStack project
+to gather anonymous statistical information about CloudStack deployments.
+
+Since version FIX ME!! the management server sends out a anonymized
Usage Report out to the
+project every 7 days.
+
+This information is used to gain information about how CloudStack is
being used.
+
+Turning this Usage Reporting functionality off can be done in the Global
Settings by setting
+'usage.report.interval' to 0.
+
+# The webservice
+The Python Flask application in this directory is the webservice running
on https://reports.cloudstack.apache.org/ (FIX ME?)
+and stores all the incoming information in a ElasticSearch database.
+
+Since Apache CloudStack is Open Source we show not only how we generate
the report, but also how we process it.
http://git-wip-us.apache.org/repos/asf/cloudstack/blob/026efd34/reporter/usage-report-collector.py
--
diff --git a/reporter/usage-report-collector.py
b/reporter/usage-report-collector.py
new file mode 100755
index 000..500a4d2
--- /dev/null
+++ b/reporter/usage-report-collector.py
@@ -0,0 +1,64 @@
+#!/usr/bin/env python
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# License); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied. See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+from flask import abort, Flask, request, Response
+from elasticsearch import Elasticsearch
+import json
+import time
+
+def json_response(response):
+return json.dumps(response, indent=2) + \n, 200, {'Content-Type':
'application/json; charset=utf-8'}
+
+def generate_app(config=None):
+app = Flask(__name__)
+
+@app.route('/report/unique_id', methods=['POST'])
+def report(unique_id):
+# We expect JSON data, so if the Content-Type doesn't match JSON
data we throw an error
+
Re: [DISCUSS] Automatic usage reporting / call-home for CloudStack
+1 Wido, will the statistics be accessible online for everyone (like real-time) or will the PMC release aggregated data periodically? On Monday 01 December 2014 06:38 PM, Wido den Hollander wrote: Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? Wido [0]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/reporter [1]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=reporter/usage-report-collector.py;h=500a4d284b5172fd93acea08f5460cfff5520855;hb=reporter -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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] Automatic usage reporting / call-home for CloudStack
On 12/01/2014 06:40 PM, Rohit Yadav wrote: +1 Wido, will the statistics be accessible online for everyone (like real-time) or will the PMC release aggregated data periodically? I was thinking to keep the data PMC-only to start with and indeed release aggregated data periodically. On Monday 01 December 2014 06:38 PM, Wido den Hollander wrote: Hello, As a project we currently don't have a lot of insight information on about how CloudStack is being used. Surveys tell us a lot, but not everybody fills in the survey, so we still miss a lot of information. That's why I've written the Usage Reporting functionality for the management server which automatically sends back anonymous information about a CloudStack deployment. It's currently in the 'reporter' branch. [0] By default, every 7 days it generates a JSON document with: - Hosts (Number, version, type, hypervisor) - Clusters (Hypervisor en Management type) - Primary storage (Type and provider) - Zones (Network type and providers) - Instances (Number and types) This report is not complete yet, I'd like to add more information, but that will be Management Server information. The code on how this report is generated is obviously 100% Open Source, so end-users can always exactly see how the information was compiled. I want to discuss this new feature for CloudStack and the possible implications it might have. I'm opting for a opt-out. So every new or upgraded install to 4.6.0 (master) will have this enabled. Yes, we have to be very explicit in the Release Notes that this has been added. Why? It's the small price we as a project ask for using CloudStack. We want a little bit of information on how CloudStack is being used so that we can use this to make CloudStack even better. Turning it off is also just one global setting and it will never turn on again. On the server-side there is a Python flask application [1] (found in the reporter directory) which stores all the incoming information in a ElasticSearch database. From there analytics can be gathered on CloudStack deployments. It currently points to http://cs-report.widodh.nl/report which will NOT be the endpoint when this is merged into master. For 'production' I want to have https://report.cloudstack.apache.org/report where all reports are submitted. For every setup a unique ID is determined by hashing the first row in the 'version' table. This is the version + timestamp and that is hashed using SHA256. Using this unique ID we can track changes in deployments and see how they grow or shrink. Technically this wasn't that hard to implement, but the politics surrounding it might be the hardest part. What do other have to say about this? Should there be a VOTE for this feature to come into CloudStack? Opt-in, opt-out? Wido [0]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/reporter [1]: https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=reporter/usage-report-collector.py;h=500a4d284b5172fd93acea08f5460cfff5520855;hb=reporter -- Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.ya...@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design Buildhttp://shapeblue.com/iaas-cloud-design-and-build// CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/ CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/ CloudStack 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.
[ACS450] pick commit from master to 4.5
I don't know what the current procedure is for this, but I'd like to get 3a52a83faeaa72a8488b2db1253fef6d3308d708 from master in the 4.5 branch if possible.
CloudStack Quality Process
Hi Everyone, It was great to get to see a number of you at the recent CCC in Budapest. While I was there, I got to meet face to face with individuals working for several companies that have a real stake in the commercial success of the CloudStack project. After joining Citrix (and becoming involved in CloudStack) about a year ago, I’ve come to believe that we need to do more to mature our quality practices around this codebase. We all like to say #cloudstackworks (and it’s true), but this is a massive codebase that’s used in the most demanding situations. We have large telecommunications companies and enterprises who are betting their businesses on this software. It has to be great! There has been quite a bit of discussion on the mailing list in recent months about how we improve in this area. There is plenty of passion, but we haven’t made enough concrete progress as a community. In my discussions with key contributors as CCC, there was general agreement that the DEV list isn’t a good forum for hashing out these kinds of things. Email is too low-bandwidth and too impersonal. At CCC, I discussed with several people the idea that we commission a small sub team to go hash out a proposal for how we handle the following topics within the ACS community (which can then be brought back to the larger community for ratification): * Continuous integration and test automation * Gating of commits * Overall commit workflow We are looking for volunteers to commit to being part of this team. This would imply a serious commitment. We don’t want hangers on or observers. This will entail real work and late night meetings. We’re looking for people who are serious contributors to the codebase. From Citrix, David Nalley and Animesh Chaturvedi have booth told me they’re willing to commit to this project. They’ve both managed ACS releases and have a really good view into the current process — and I know both are passionate about improving our process. From my CCC discussions, I believe there are individuals from Schuberg Philis, Shape Blue and Cloud Ops who are willing to commit to this process. If you are willing to be part of this team to drive forward our community, please reply here. Thanks, -Steve Steve Wilson VP Product Unit Manager Cloud Software Citrix @virtualsteve
Re: [ACS450] pick commit from master to 4.5
mail this list with the tag acs45, kind of how you did it. @david Or do you prefer a different approach? On Mon, Dec 1, 2014 at 7:27 PM, Logan Barfield lbarfi...@tqhosting.com wrote: I don't know what the current procedure is for this, but I'd like to get 3a52a83faeaa72a8488b2db1253fef6d3308d708 from master in the 4.5 branch if possible. -- Daan
Re: CloudStack Quality Process
H Steve, As you mentioned one of us at Schuberg Philis will be on it. Without further notice it will be me. regards, Daan On Mon, Dec 1, 2014 at 8:12 PM, Steve Wilson steve.wil...@citrix.com wrote: Hi Everyone, It was great to get to see a number of you at the recent CCC in Budapest. While I was there, I got to meet face to face with individuals working for several companies that have a real stake in the commercial success of the CloudStack project. After joining Citrix (and becoming involved in CloudStack) about a year ago, I’ve come to believe that we need to do more to mature our quality practices around this codebase. We all like to say #cloudstackworks (and it’s true), but this is a massive codebase that’s used in the most demanding situations. We have large telecommunications companies and enterprises who are betting their businesses on this software. It has to be great! There has been quite a bit of discussion on the mailing list in recent months about how we improve in this area. There is plenty of passion, but we haven’t made enough concrete progress as a community. In my discussions with key contributors as CCC, there was general agreement that the DEV list isn’t a good forum for hashing out these kinds of things. Email is too low-bandwidth and too impersonal. At CCC, I discussed with several people the idea that we commission a small sub team to go hash out a proposal for how we handle the following topics within the ACS community (which can then be brought back to the larger community for ratification): * Continuous integration and test automation * Gating of commits * Overall commit workflow We are looking for volunteers to commit to being part of this team. This would imply a serious commitment. We don’t want hangers on or observers. This will entail real work and late night meetings. We’re looking for people who are serious contributors to the codebase. From Citrix, David Nalley and Animesh Chaturvedi have booth told me they’re willing to commit to this project. They’ve both managed ACS releases and have a really good view into the current process — and I know both are passionate about improving our process. From my CCC discussions, I believe there are individuals from Schuberg Philis, Shape Blue and Cloud Ops who are willing to commit to this process. If you are willing to be part of this team to drive forward our community, please reply here. Thanks, -Steve Steve Wilson VP Product Unit Manager Cloud Software Citrix @virtualsteve -- Daan
Re: [ACS450] pick commit from master to 4.5
No that worksforme. I'd prefer that Wido move this over, so that he can ensure that it's not going to break anything else. --David On Mon, Dec 1, 2014 at 2:51 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: mail this list with the tag acs45, kind of how you did it. @david Or do you prefer a different approach? On Mon, Dec 1, 2014 at 7:27 PM, Logan Barfield lbarfi...@tqhosting.com wrote: I don't know what the current procedure is for this, but I'd like to get 3a52a83faeaa72a8488b2db1253fef6d3308d708 from master in the 4.5 branch if possible. -- Daan
Re: [ACS450] pick commit from master to 4.5
Sounds good. I've been running this in production since July without any issues, so it shouldn't conflict with anything that I'm aware of. Wido, if you can respond here once it's in I'd appreciate it. Thank You, Logan Barfield Tranquil Hosting On Mon, Dec 1, 2014 at 3:08 PM, David Nalley da...@gnsa.us wrote: No that worksforme. I'd prefer that Wido move this over, so that he can ensure that it's not going to break anything else. --David On Mon, Dec 1, 2014 at 2:51 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: mail this list with the tag acs45, kind of how you did it. @david Or do you prefer a different approach? On Mon, Dec 1, 2014 at 7:27 PM, Logan Barfield lbarfi...@tqhosting.com wrote: I don't know what the current procedure is for this, but I'd like to get 3a52a83faeaa72a8488b2db1253fef6d3308d708 from master in the 4.5 branch if possible. -- Daan
Re: [ACS450] pick commit from master to 4.5
Hi Logan, On 01-Dec-2014, at 11:57 pm, Logan Barfield lbarfi...@tqhosting.com wrote: 3a52a83faeaa72a8488b2db1253fef6d3308d708 Thanks for raising this, looks like it was not merged into 4.5 at all. I’ve cherry-picked this on 4.5; commit 3a36681b6edbf317ef75ca96acb24522ca341556 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: [ACS450] pick commit from master to 4.5
Much appreciated Rohit. Thank You, Logan Barfield Tranquil Hosting On Mon, Dec 1, 2014 at 3:28 PM, Rohit Yadav rohit.ya...@shapeblue.com wrote: Hi Logan, On 01-Dec-2014, at 11:57 pm, Logan Barfield lbarfi...@tqhosting.com wrote: 3a52a83faeaa72a8488b2db1253fef6d3308d708 Thanks for raising this, looks like it was not merged into 4.5 at all. I’ve cherry-picked this on 4.5; commit 3a36681b6edbf317ef75ca96acb24522ca341556 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 Software Engineering http://shapeblue.com/cloudstack-software-engineering/ 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: [ACS450] pick commit from master to 4.5
On 12/01/2014 09:16 PM, Logan Barfield wrote: Sounds good. I've been running this in production since July without any issues, so it shouldn't conflict with anything that I'm aware of. Wido, if you can respond here once it's in I'd appreciate it. I see no problem in merging this into 4.5 Already done I see by Rohit, that's great. Wido Thank You, Logan Barfield Tranquil Hosting On Mon, Dec 1, 2014 at 3:08 PM, David Nalley da...@gnsa.us wrote: No that worksforme. I'd prefer that Wido move this over, so that he can ensure that it's not going to break anything else. --David On Mon, Dec 1, 2014 at 2:51 PM, Daan Hoogland daan.hoogl...@gmail.com wrote: mail this list with the tag acs45, kind of how you did it. @david Or do you prefer a different approach? On Mon, Dec 1, 2014 at 7:27 PM, Logan Barfield lbarfi...@tqhosting.com wrote: I don't know what the current procedure is for this, but I'd like to get 3a52a83faeaa72a8488b2db1253fef6d3308d708 from master in the 4.5 branch if possible. -- Daan
Review Request 28573: CLOUDSTACK-7995: Added GloboNetwork plugin to help regular (non-admin) users to manage shared network in a simpler way
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28573/ --- Review request for cloudstack. Repository: cloudstack-git Description --- JIRA: CLOUDSTACK-7995 Design document: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Regular+cloudstack+user+can+create+and+manage+shared+networks+by+GloboNetwork+in+a+simpler+way Base commit (in master): 4798db0de1862bbdf7f2af67f7684f2f3430609e Diffs - api/src/com/cloud/network/Network.java c5a9bf2 api/src/org/apache/cloudstack/api/ApiConstants.java 762ad70 api/src/org/apache/cloudstack/api/response/NetworkResponse.java 40c9072 api/src/org/apache/cloudstack/network/ExternalNetworkDeviceManager.java b349356 client/pom.xml 6803f9a client/tomcatconf/commands.properties.in a87d167 plugins/network-elements/globonetwork/LICENSE PRE-CREATION plugins/network-elements/globonetwork/NOTICE PRE-CREATION plugins/network-elements/globonetwork/pom.xml PRE-CREATION plugins/network-elements/globonetwork/resources/META-INF/cloudstack/globonetwork/module.properties PRE-CREATION plugins/network-elements/globonetwork/resources/META-INF/cloudstack/globonetwork/spring-globonetwork-context.xml PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/GloboNetworkEnvironmentVO.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/GloboNetworkNetworkVO.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/GloboNetworkVipAccVO.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/AddGloboNetworkEnvironmentCmd.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/AddGloboNetworkHostCmd.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/AddNetworkViaGloboNetworkCmd.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/DeleteNetworkInGloboNetworkCmd.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/GloboNetworkCapabilitiesResponse.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/GloboNetworkEnvironmentResponse.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/ListAllEnvironmentsFromGloboNetworkCmd.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/ListGloboNetworkCapabilitiesCmd.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/ListGloboNetworkEnvironmentsCmd.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/api/RemoveGloboNetworkEnvironmentCmd.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/ActivateNetworkCommand.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/CreateNewVlanInGloboNetworkCommand.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/DeallocateVlanFromGloboNetworkCommand.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/GetVlanInfoFromGloboNetworkCommand.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/GloboNetworkErrorAnswer.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/ListAllEnvironmentsFromGloboNetworkCommand.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/RegisterEquipmentAndIpInGloboNetworkCommand.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/RemoveNetworkInGloboNetworkCommand.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/UnregisterEquipmentAndIpInGloboNetworkCommand.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/commands/ValidateNicInVlanCommand.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/dao/GloboNetworkEnvironmentDao.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/dao/GloboNetworkEnvironmentDaoImpl.java PRE-CREATION plugins/network-elements/globonetwork/src/com/globo/globonetwork/cloudstack/dao/GloboNetworkNetworkDao.java PRE-CREATION
Re: git commit: updated refs/heads/master to ae0cb82
Use source Luke ;-) Apparently there is now an alias on the VR ip called data-server. The Ssh script used it to get the ssh keys if it can't find the dhcp server using the leases file. I didn't invent this feature, just made it work for passwords and cleaned up the code a bit. Hugo Sent from my iPhone On 01 Dec 2014, at 18:29, Rohit Yadav rohityada...@gmail.com wrote: Hi Hugo, On Mon, Dec 1, 2014 at 7:27 PM, h...@apache.org wrote: Repository: cloudstack Updated Branches: refs/heads/master ce2b2a1fc - ae0cb8279 Both scripts should be able to use the data-server introduced in 4.4 What does this commit fix? Sorry, I've no idea about the data-server introduced in 4.4. Verbose git commit messages are always welcome. Regards. Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/ae0cb827 Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/ae0cb827 Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/ae0cb827 Branch: refs/heads/master Commit: ae0cb8279225db0b6d0f642a546792ba6f3f1117 Parents: ce2b2a1 Author: Hugo Trippaers htrippa...@schubergphilis.com Authored: Fri Nov 28 14:08:47 2014 +0100 Committer: Hugo Trippaers htrippa...@schubergphilis.com Committed: Mon Dec 1 14:56:58 2014 +0100 -- setup/bindir/cloud-set-guest-password.in | 69 +-- setup/bindir/cloud-set-guest-sshkey.in | 36 ++ 2 files changed, 48 insertions(+), 57 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/ae0cb827/setup/bindir/cloud-set-guest-password.in -- diff --git a/setup/bindir/cloud-set-guest-password.in b/setup/bindir/ cloud-set-guest-password.in index 4c7c575..2c7304b 100755 --- a/setup/bindir/cloud-set-guest-password.in +++ b/setup/bindir/cloud-set-guest-password.in @@ -40,45 +40,44 @@ for DHCP_FILE in $DHCP_FOLDERS; do if [ -n $PASSWORD_SERVER_IP ]; then logger -t cloud Found password server IP $PASSWORD_SERVER_IP in $DHCP_FILE - logger -t cloud Sending request to password server at $PASSWORD_SERVER_IP - - password=$(wget -q -t 3 -T 20 -O - --header DomU_Request: send_my_password $PASSWORD_SERVER_IP:$PASSWORD_SERVER_PORT) - - if [ $? -eq 0 ]; then - password=$(echo $password | tr -d '\r') - logger -t cloud Got response from server at $PASSWORD_SERVER_IP - - case $password in - ) - logger -t cloud Password server at $PASSWORD_SERVER_IP did not have any password for the VM - continue - ;; - bad_request) - logger -t cloud VM sent an invalid request to password server at $PASSWORD_SERVER_IP - error_count=$((error_count+1)) - continue - ;; - saved_password) - logger -t cloud VM has already saved a password from the password server at $PASSWORD_SERVER_IP - continue - ;; - *) - logger -t cloud VM got a valid password from server at $PASSWORD_SERVER_IP - password_received=1 - break - ;; - esac - else - logger -t cloud Failed to send request to password server at $PASSWORD_SERVER_IP - error_count=$((error_count+1)) - fi - else - logger -t cloud Could not find password server IP in $DHCP_FILE - error_count=$((error_count+1)) +break fi fi done +if [ -z $PASSWORD_SERVER_IP ] ; then + logger -t cloud Unable to determine the password server, falling back to data-server + PASSWORD_SERVER_IP=data-server +fi + +logger -t cloud Sending request to password server at $PASSWORD_SERVER_IP +password=$(wget -q -t 3 -T 20 -O - --header DomU_Request: send_my_password
Re: 05bec59c - kvm, qcow, systemvm qemu-img -o compat
Edison, According to this page the default compat option is 0.10: http://manpages.ubuntu.com/manpages/trusty/man1/qemu-img.1.html Did you find that to not be the case and is that why you had to add the compat option? BTW, in an attempt to get the master system vms building again, I committed a change to master to remove the compat option. We now have master system vms building correctly, but Rohit rightly pointed out that I had basically reverted your change. I created a Jira ticket for this issue: https://issues.apache.org/jira/browse/CLOUDSTACK-7959 I have not reverted my change in master at this point, so it is building right now, but I also did not make the change to 4.5, so that branch is currently failing to build system vms. I will see if I can track down in which version of qemu the compat option was added so we can add some intelligent logic around this command. Will *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Thu, Nov 20, 2014 at 1:07 PM, edison su sudi...@gmail.com wrote: Hi Leo, Our new internal build system are using ubuntu 14.04 or something like that, which has qemu 1.x installed by default, that's why I added the compat option in the build script, otherwise, the image build by qemu 1.x, won't work on RHEL 6.x. The fix would be, in the build script, check the version of qemu-img, if it's 0.x, then don't add compat option. There are a lot of people still using RHEL 6.x as KVM hypervisor, we have to make sure the image we build can still work on these machines. On Thu, Nov 20, 2014 at 6:49 AM, Leo Simons lsim...@schubergphilis.com wrote: Hey Edison, all, https://github.com/apache/cloudstack/commit/05bec59c1498dbcfb8a1089c86855fd3b433ea58 breaks our internal build with + qemu-img convert -o compat=0.10 -f raw -c -O qcow2 raw.img \ systemvmtemplate-systemvm-persistent-config-4.5.0.124-kvm.qcow2 Unknown option 'compat' qemu-img: Invalid options for file format 'qcow2'. This is on CentOS release 6.6, which has qemu-img-0.15.0-1.el6.rfx.x86_64. Based on http://wiki.qemu.org/OlderNews that seems like it is a really old qemu (august 2011). I'm guessing you have a newer OS / newer qemu? Can you please let me know what OS, OS version and qemu(-img) version you are using? Also, does anyone know if there some minimum version of qemu-img that should be used / cloudstack assumes? Is 0.15 still ok to do an acceptable image conversion with? (we currently don't have any kvm use ourselves, but, I'd like for our build infra to produce useful kvm images nonetheless). According to http://wiki.qemu.org/ChangeLog/1.1 the -o compat switch was introduced in 1.1. According to https://github.com/qemu/qemu/commit/9117b47717ad208b12786ce88eacb013f9b3dd1c the default format was changed from 0.10 to 1.1 in qemu 1.7 and onwards. The libvirt people https://bugzilla.redhat.com/show_bug.cgi?id=997977 say they pass -o compat when qemu supports it (so when v = 1.1 I imagine). I think we should do the same in the build script and I'll make a patch. But, should we publish newer-format images too? According to http://wiki.qemu.org/Features/Qcow3 the new format is much better so I imagine qcow/kvm users will really appreciate the newer formats. Thoughts? cheers, Leo -- Best Regards, Edison
Re: root resize support in the UI
Matheww, offtopic - keep in mind that hostbill will make milion of computer offerings and everything, so if you login to cloudstack - you will get lost - at least per my latest experience with hostbill. Also we were told that they store credit cards in their database - something you might not want. On 1 December 2014 at 17:57, Logan Barfield lbarfi...@tqhosting.com wrote: Just chiming in: I un-commented the Root Disk field in the Instance Wizard in our 4.4 deployment. Works fine with KVM / Ceph RBD. The logic we see is: A) If specified size is smaller than template size, throw an alert. B) If specified size is larger than template size then deploy root disk with specified size. C) If nothing is specified (default if the box isn't enabled) then deploy root disk with same size as template. This works with KVM and the RBD resize logic I committed a few months ago. I can't speak for how it works with Xen/VMware or other primary storage backends. Thank You, Logan Barfield Tranquil Hosting On Mon, Dec 1, 2014 at 11:34 AM, Matthew Midgett clouds...@trick-solutions.com.invalid wrote: 1+ from me for XenServer root disk resize for template deployments! I'm going with Nux on the single partition scheme and I want my root disk under 2GB as most all of my deployments are minimal systems. This makes the journey from sec storage to primary storage quite a bit faster. I need to deploy and resize and be running in under 60 seconds if possible to keep my users from sitting around waiting. I will be using hostbill in front of my ACS and they offer these sliders for choosing how much resources you want. Users really like this and if they deploy my 2gb template I'd like to be able to give them that 50GB disk they ask for without using a data disk. If cloud-init can do this then I as a user would develop my templates around the file system layout that it supports. EXT3,EXT4,BTRFS or LVMI honestly don't care for using LVM in a Virtual Machine, it's just one more layer of complexity on a disk that doesn’t need to be there. Most all Linux file systems can support online resize without LVM so I would consider not using it to simplify cloud-init resize. Just my 2cents Matthew Midgett -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Monday, December 01, 2014 7:06 AM To: dev@cloudstack.apache.org Subject: Re: root resize support in the UI Andrija, Absolutely, everyone has their own needs. The single partition works best for us (we also implemented it in physical dedicated servers - makes p2v and v2p easy!) and it also seems to be the choice of others (official fedora/centos/ubuntu templates are like this as well). -- 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 Sent: Monday, 1 December, 2014 11:42:29 Subject: Re: root resize support in the UI ok, Nux, so you suggest, single partition layout, with some predefined usage scenario...that is definitively an option for me. On the other hand, if you have slightly complicated templates - then the only way I see is to only resize the disk qith qemu-img...(not going inside VM)... So we need to decide on the user-case scenario we find most usefull... On 1 December 2014 at 12:30, Nux! n...@li.nux.ro wrote: Vadim, Currently the ROOT resize feature is not available for hypervisors other than KVM. The developers working with these HVs are not interested in this feature a.t.m. Feel free to request this feature and stress them out. :) Based on this feature I now only use 1 template with 1 single partition in it mounted as / which cloud-init will expand to maximum during deployment. Self-resizing can also be done in Windows quite easily. I don't think it's acceptable to tell customer to deal with expanding the partition himself, so this is automated. I do not use swap, but when it is a must I use a file based swap (eg /var/swap.IMG). You could use another primary storage for swap, but IMHO this just complicated things and it's not worth it. Generally I try not to use multiple volumes for a VM, it makes life easier. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Vadim Kimlaychuk vadim.kimlayc...@elion.ee To: dev@cloudstack.apache.org Sent: Monday, 1 December, 2014 11:09:24 Subject: RE: root resize support in the UI Andrija, You did understand me correctly. I wish that for the customer disk offer could be customizable. And not just for KVM hypervisor. Particularly now I am interested in Xen and VmWare. CS admin should not have set of
Re: 05bec59c - kvm, qcow, systemvm qemu-img -o compat
Hi, If it helps, RHEL 7 ships qemu-img 1.5.3 and by default it does not produce compatible images with older qemu, the compat option needs to be specified. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Will Stevens wstev...@cloudops.com To: dev@cloudstack.apache.org Cc: Leo Simons lsim...@schubergphilis.com, Wilder Rodrigues wrodrig...@schubergphilis.com Sent: Monday, 1 December, 2014 21:06:27 Subject: Re: 05bec59c - kvm, qcow, systemvm qemu-img -o compat Edison, According to this page the default compat option is 0.10: http://manpages.ubuntu.com/manpages/trusty/man1/qemu-img.1.html Did you find that to not be the case and is that why you had to add the compat option? BTW, in an attempt to get the master system vms building again, I committed a change to master to remove the compat option. We now have master system vms building correctly, but Rohit rightly pointed out that I had basically reverted your change. I created a Jira ticket for this issue: https://issues.apache.org/jira/browse/CLOUDSTACK-7959 I have not reverted my change in master at this point, so it is building right now, but I also did not make the change to 4.5, so that branch is currently failing to build system vms. I will see if I can track down in which version of qemu the compat option was added so we can add some intelligent logic around this command. Will *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Thu, Nov 20, 2014 at 1:07 PM, edison su sudi...@gmail.com wrote: Hi Leo, Our new internal build system are using ubuntu 14.04 or something like that, which has qemu 1.x installed by default, that's why I added the compat option in the build script, otherwise, the image build by qemu 1.x, won't work on RHEL 6.x. The fix would be, in the build script, check the version of qemu-img, if it's 0.x, then don't add compat option. There are a lot of people still using RHEL 6.x as KVM hypervisor, we have to make sure the image we build can still work on these machines. On Thu, Nov 20, 2014 at 6:49 AM, Leo Simons lsim...@schubergphilis.com wrote: Hey Edison, all, https://github.com/apache/cloudstack/commit/05bec59c1498dbcfb8a1089c86855fd3b433ea58 breaks our internal build with + qemu-img convert -o compat=0.10 -f raw -c -O qcow2 raw.img \ systemvmtemplate-systemvm-persistent-config-4.5.0.124-kvm.qcow2 Unknown option 'compat' qemu-img: Invalid options for file format 'qcow2'. This is on CentOS release 6.6, which has qemu-img-0.15.0-1.el6.rfx.x86_64. Based on http://wiki.qemu.org/OlderNews that seems like it is a really old qemu (august 2011). I'm guessing you have a newer OS / newer qemu? Can you please let me know what OS, OS version and qemu(-img) version you are using? Also, does anyone know if there some minimum version of qemu-img that should be used / cloudstack assumes? Is 0.15 still ok to do an acceptable image conversion with? (we currently don't have any kvm use ourselves, but, I'd like for our build infra to produce useful kvm images nonetheless). According to http://wiki.qemu.org/ChangeLog/1.1 the -o compat switch was introduced in 1.1. According to https://github.com/qemu/qemu/commit/9117b47717ad208b12786ce88eacb013f9b3dd1c the default format was changed from 0.10 to 1.1 in qemu 1.7 and onwards. The libvirt people https://bugzilla.redhat.com/show_bug.cgi?id=997977 say they pass -o compat when qemu supports it (so when v = 1.1 I imagine). I think we should do the same in the build script and I'll make a patch. But, should we publish newer-format images too? According to http://wiki.qemu.org/Features/Qcow3 the new format is much better so I imagine qcow/kvm users will really appreciate the newer formats. Thoughts? cheers, Leo -- Best Regards, Edison
[GitHub] cloudstack pull request: Feature cenik123 vpcvrr 1.1.1
Github user KarlHarrisSungardAS commented on the pull request: https://github.com/apache/cloudstack/pull/33#issuecomment-65140570 I'm using Packer to build a System VM as well as a Vagrant SystemVM test box. My Packer code builds as systemVM which can then be used to deploy public virtual redundant routers. We are currently working with Vagrant boxes to generate changes and test VPC VRR's functionality. So is it easier to setup and work with than Vagrant? Since they are both used for different purposes I am confused by the question. In some ways Packer is easier to generate images from scratch and adapts easy to changes in all of the many pieces which come together to build a SystemVM. Vagrant is very nice for testing changes to the SystemVM's once a vagrant box is built. Please expand on your question. Thanks for the reply. Karl --- 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: [ACS450] remove some upgrade path from Release Notes
Actually, here is the best thread to ask the question... Does anyone validate upgrade instruction from 2.x, 3.x. 4.0.x, 4.1.x since 4.3.0 ? Thanks, On Mon, Dec 1, 2014 at 4:52 PM, Pierre-Luc Dion pd...@cloudops.com wrote: Well, I've never heard some someone tested upgrading a 2.2.x, 3.x.x, 4.0.x or 4.1.x since 4.4 as been released. I know for sure those upgrade path have not been tested. I'll ask for 4.5... Thanks, On Mon, Dec 1, 2014 at 3:07 AM, Leo Simons lsim...@schubergphilis.com wrote: Hey hey, Thinking as an administrator, I definitely don't want release notes (or upgrade paths themselves, or other documentation that contains procedures that have huge impact) that have not been tested. If I'm running cloudstack 2.2.14, and I want to upgrade to 4.4.2, and I ask on the users list what to do, what is the answer? If it is just follow the upgrade instructions for all consecutive releases and it'll be fine, keep it. Otherwise, remove it. My two cents :) cheers, Leo On Dec 1, 2014, at 12:39 AM, Pierre-Luc Dion pd...@cloudops.com wrote: I'm wondering if I should remove the upgrade instructions of 4.1.x, 4.0.x, 3.0.x and 2.2.14 from the 4.5.0 release notes. These upgrade instructions are fairly outdated and has not been tested(at least in 4.4). They also contain errors and some inconsistency. Unless someone is willing to validate them and fix instructions? any thoughts? thanks, PL
Re: [ACS450] remove some upgrade path from Release Notes
Well, I've never heard some someone tested upgrading a 2.2.x, 3.x.x, 4.0.x or 4.1.x since 4.4 as been released. I know for sure those upgrade path have not been tested. I'll ask for 4.5... Thanks, On Mon, Dec 1, 2014 at 3:07 AM, Leo Simons lsim...@schubergphilis.com wrote: Hey hey, Thinking as an administrator, I definitely don't want release notes (or upgrade paths themselves, or other documentation that contains procedures that have huge impact) that have not been tested. If I'm running cloudstack 2.2.14, and I want to upgrade to 4.4.2, and I ask on the users list what to do, what is the answer? If it is just follow the upgrade instructions for all consecutive releases and it'll be fine, keep it. Otherwise, remove it. My two cents :) cheers, Leo On Dec 1, 2014, at 12:39 AM, Pierre-Luc Dion pd...@cloudops.com wrote: I'm wondering if I should remove the upgrade instructions of 4.1.x, 4.0.x, 3.0.x and 2.2.14 from the 4.5.0 release notes. These upgrade instructions are fairly outdated and has not been tested(at least in 4.4). They also contain errors and some inconsistency. Unless someone is willing to validate them and fix instructions? any thoughts? thanks, PL
