Build failed in Jenkins: simulator-singlerun #855

2014-12-30 Thread jenkins
See http://jenkins.buildacloud.org/job/simulator-singlerun/855/changes Changes: [rajesh.battala] CLOUDSTACK-6920 Support listing of LBHealthcheck policy with LBHealthcheck policy ID [likitha.shetty] CLOUDSTACK-8134. Worker VMs don't have MS id set in vCenter annotation 'cloud.vm.workertag'.

Why Issues tab disappeared at CloudStack's github page ?

2014-12-30 Thread ChunFeng
Hi all, When you visit to page : https://github.com/apache/cloudstack , you will notice that the Issues tab missed , which should just under Code tab on the right side of the page . Why Issues tab disappeared at CloudStack's github page ? -- Regards, ChunFeng

Re: CS MS Logging Level

2014-12-30 Thread Daan Hoogland
Mike, It doesn't spew to vmops.log anymore, right? It seems that the new jetty version interprets all the log4j/classpath differently and the one from the hyperv plugin takes precedence. I have been looking for a solution but haven't found one yet. On Mon, Dec 29, 2014 at 10:02 PM, Mike

About The Instance Name on Cloudstack

2014-12-30 Thread Star Guo
Hi, All, When I create instance on cloudstack 4.4.2,set name within simple chinese as instance name but it tell me “Instance name can not be longer than 63 characters. Only ASCII letters a~z, A~Z, digits 0~9, hyphen are allowed. Must start with a letter and end with a letter or a digit.”

Build failed in Jenkins: build-master #2123

2014-12-30 Thread jenkins
See http://jenkins.buildacloud.org/job/build-master/2123/changes Changes: [likitha.shetty] CLOUDSTACK-8136. [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed. -- [...truncated 2745 lines...] [INFO]

Re: Why Issues tab disappeared at CloudStack's github page ?

2014-12-30 Thread Sebastien Goasguen
On Dec 30, 2014, at 3:27 AM, ChunFeng chunf...@domolo.com wrote: Hi all, When you visit to page : https://github.com/apache/cloudstack , you will notice that the Issues tab missed , which should just under Code tab on the right side of the page . Github is just a mirror of the

Review Request 29478: CLOUDSTACK-8137: Fixed cleanup issue in sec group tests in test_escalations_instances.py

2014-12-30 Thread Ashutosh Kelkar
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29478/ --- Review request for cloudstack and SrikanteswaraRao Talluri. Bugs:

Build failed in Jenkins: simulator-singlerun #856

2014-12-30 Thread jenkins
See http://jenkins.buildacloud.org/job/simulator-singlerun/856/changes Changes: [likitha.shetty] CLOUDSTACK-8136. [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed. -- [...truncated 9048 lines...] File

Unable to start VM due to concurrent operation

2014-12-30 Thread Mohamed Infaz
Hi All, I have successfully deployed cloudstack 4.3 with two hosts and the setup runs the management server on another physical host. I had issues with downloading an ISO but finally i was able to download an ISO image. When i want to create an instance i get the following error message saying

Re: CS MS Logging Level

2014-12-30 Thread Mike Tutkowski
No, vmops.log does not seem to be getting spammed...just the console. On Tue, Dec 30, 2014 at 1:44 AM, Daan Hoogland daan.hoogl...@gmail.com wrote: Mike, It doesn't spew to vmops.log anymore, right? It seems that the new jetty version interprets all the log4j/classpath differently and the

RE: New snapshot(s) text in GUI

2014-12-30 Thread Somesh Naidu
+1 for reverting. Would be interesting though to know the reason for why it was changed. Somesh -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Monday, December 29, 2014 8:38 PM To: dev@cloudstack.apache.org Subject: Re: New snapshot(s) text in GUI +1 for reverting, looks

RE: Physical network design options - which crime to comit

2014-12-30 Thread Somesh Naidu
Sorry, I was out on holidays :) I guess that should work. Just know that Primary traffic is hypervisor to storage and Secondary traffic is SSVM/Mgmt to storage. Cloudstack generally doesn't consider primary storage in its architecture design as it mostly relies on recommendation from the

RE: Unable to start VM due to concurrent operation

2014-12-30 Thread Somesh Naidu
Mohamed, The log snippet you have shared doesn't seem to be relevant to the concurrent operation exception (can't see that exception stack). The message that did catch my attention though is, - 2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-463d2f57)

Re: Physical network design options - which crime to comit

2014-12-30 Thread Andrija Panic
Somesh, thx - I understand that - one more question, since you guys are arround :) The primary storage network - I unnderstand how to separate that from management networks on the host (having separate NIC/vlan/IP inside each hypervisor host, etc) - but as far as I know, the SSVM doesnt have a

RE: Physical network design options - which crime to comit

2014-12-30 Thread Somesh Naidu
Interaction with primary storage would be via the hypervisor. SSVM doesn't access the primary storage directly. -Original Message- From: Andrija Panic [mailto:andrija.pa...@gmail.com] Sent: Tuesday, December 30, 2014 1:52 PM To: us...@cloudstack.apache.org Cc: dev@cloudstack.apache.org

Re: Physical network design options - which crime to comit

2014-12-30 Thread Andrija Panic
Somesh - I'm missing something here - just initiated new Volume Snapshot - and I see that the HOST does the qemu-img convert operation with 2 mount points, one primary and one secondary...so my wrong... I know the same happens when deploying new VM from template - HOST mounts primary and secondary

[Question] Creating a volume from a snapshot

2014-12-30 Thread Mike Tutkowski
Hi, I'm working on adding in zone-wide support for managed (primary) storage with regards to the create volume from snapshot feature that CloudStack has. It appears that the current intent of this feature is to create a volume (based on a given snapshot) on some primary storage that conforms to

Re: [Question] Creating a volume from a snapshot

2014-12-30 Thread Mike Tutkowski
For example: You want to create a volume based on snapshot S1. Snapshot S1 was created from volume V1. Volume V1 was associated disk offering DO1. Disk offering DO1 had the storage tags filled out as such: ST1, STA Now, when we go to create a new volume (based on S1), it looks like

Re: Unable to start VM due to concurrent operation

2014-12-30 Thread Mohamed Infaz
Hi Somesh, Thank you for the reply. Well both of my system vm's are running and it is downloading the iso image. And i was able to ping them. The system vm template i am using is for the version 4.3 cloudstack. Thank you. On 30 December 2014 at 23:59, Somesh Naidu somesh.na...@citrix.com wrote:

Re: Unable to start VM due to concurrent operation

2014-12-30 Thread Mohamed Infaz
systemvm64template-2014-01-14-master-kvm.qcow2.bz2 This is the template i used. On 31 December 2014 at 07:49, Mohamed Infaz infaz...@cse.mrt.ac.lk wrote: Hi Somesh, Thank you for the reply. Well both of my system vm's are running and it is downloading the iso image. And i was able to ping

Re: Application programming on CS

2014-12-30 Thread Giri Prasad
Thanks everybody for all your valuable comments. I am currently surfing around looking for the information. Will keep posted, when I find something useful. Giri From: Pierre-Luc Dion pd...@cloudops.com To: dev@cloudstack.apache.org dev@cloudstack.apache.org Cc:

RE: CS MS Logging Level

2014-12-30 Thread Anshul Gangwar
Daan, I am not seeing extraneous logs on my dev setup other than thread which is cleaning up expired async-jobs. You can safely change CONSOLE appender's threshold to INFO in hyperv plugin if you think that is causing the problem. We will not lose much info which we want to show to user by

RE: New snapshot(s) text in GUI

2014-12-30 Thread Suresh Sadhu
+1 for reverting. Sadhu -Original Message- From: Somesh Naidu [mailto:somesh.na...@citrix.com] Sent: 30 December 2014 23:59 To: dev@cloudstack.apache.org Subject: RE: New snapshot(s) text in GUI +1 for reverting. Would be interesting though to know the reason for why it was changed.