date:20130531


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal updated CLOUDSTACK-2758:
---

   Priority: Blocker  (was: Critical)
Description: 
For the last two days the packages for CloudStack from jenkins.cs.o haven't 
been able to boot up the management server. The service start reports OK, but 
the service dies immediately.

[root@cloudstack-centos63 ~]# bash -x /etc/init.d/cloudstack-management start
+ '[' -r /etc/rc.d/init.d/functions ']'
+ . /etc/rc.d/init.d/functions
++ TEXTDOMAIN=initscripts
++ umask 022
++ PATH=/sbin:/usr/sbin:/bin:/usr/bin
++ export PATH
++ '[' -z '' ']'
++ COLUMNS=80
++ '[' -z '' ']'
+++ /sbin/consoletype
++ CONSOLETYPE=pty
++ '[' -f /etc/sysconfig/i18n -a -z '' -a -z '' ']'
++ . /etc/profile.d/lang.sh
++ unset LANGSH_SOURCED
++ '[' -z '' ']'
++ '[' -f /etc/sysconfig/init ']'
++ . /etc/sysconfig/init
+++ BOOTUP=color
+++ RES_COL=60
+++ MOVE_TO_COL='echo -en \033[60G'
+++ SETCOLOR_SUCCESS='echo -en \033[0;32m'
+++ SETCOLOR_FAILURE='echo -en \033[0;31m'
+++ SETCOLOR_WARNING='echo -en \033[0;33m'
+++ SETCOLOR_NORMAL='echo -en \033[0;39m'
+++ PROMPT=yes
+++ AUTOSWAP=no
+++ ACTIVE_CONSOLES='/dev/tty[1-6]'
+++ SINGLE=/sbin/sushell
++ '[' pty = serial ']'
++ 
__sed_discard_ignored_files='/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d'
+ '[' -r /lib/lsb/init-functions ']'
+ . /lib/lsb/init-functions
++ basename /etc/init.d/cloudstack-management
+ NAME=cloudstack-management
+ case "$1" in
+ set_ulimit
++ ulimit -n
+ fd_limit=1024
+ '[' 1024 '!=' 4096 ']'
++ whoami
+ user=root
+ '[' root == root ']'
+ ulimit -n 4096
+ . /etc/rc.d/init.d/tomcat6
++ '[' -r /lib/lsb/init-functions ']'
++ . /lib/lsb/init-functions
+++ lsb_release -i -s
++ DISTRIB_ID=CentOS
+++ basename /etc/init.d/cloudstack-management
++ NAME=cloudstack-management
++ unset ISBOOT
++ '[' c = S -o c = K ']'
++ '[' -x /sbin/runuser ']'
++ SU='/sbin/runuser -s /bin/sh'
++ TOMCAT_CFG=/etc/tomcat6/tomcat6.conf
++ '[' -r /etc/tomcat6/tomcat6.conf ']'
++ . /etc/tomcat6/tomcat6.conf
+++ CATALINA_BASE=/usr/share/tomcat6
+++ CATALINA_HOME=/usr/share/tomcat6
+++ JASPER_HOME=/usr/share/tomcat6
+++ CATALINA_TMPDIR=/var/cache/tomcat6/temp
+++ JAVA_OPTS=' 
-Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory'
+++ TOMCAT_USER=tomcat
+++ SECURITY_MANAGER=false
+++ SHUTDOWN_WAIT=30
+++ SHUTDOWN_VERBOSE=false
+++ CATALINA_PID=/var/run/tomcat6.pid
++ '[' -r /etc/sysconfig/cloudstack-management ']'
++ . /etc/sysconfig/cloudstack-management
+++ dummy=1
+++ export TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
+++ TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
+++ . /etc/cloudstack/management/tomcat6.conf
 CATALINA_BASE=/usr/share/cloudstack-management
 CATALINA_HOME=/usr/share/cloudstack-management
 JASPER_HOME=/usr/share/cloudstack-management
 CATALINA_TMPDIR=/usr/share/cloudstack-management/temp
 JAVA_OPTS='-Djava.awt.headless=true 
-Dcom.sun.management.jmxremote.port=45219 
-Dcom.sun.management.jmxremote.authenticate=false 
-Dcom.sun.management.jmxremote.ssl=false -Xmx2g -XX:+HeapDumpOnOutOfMemoryError 
-XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M 
-XX:MaxPermSize=800m'
 TOMCAT_USER=cloud
 TOMCAT6_USER=cloud
 TOMCAT_LOG=/var/log/cloudstack/management//catalina.out
 SECURITY_MANAGER=false
 SHUTDOWN_WAIT=30
 SHUTDOWN_VERBOSE=false
 CATALINA_PID=/var/run/cloudstack-management.pid
 dummy=1
 . /etc/cloudstack/management/classpath.conf
+ SYSTEMJARS=
++ build-classpath
+ SCP=
+ '[' 2 '!=' 0 ']'
+ export SCP=
+ SCP=
+ MCP=
+ DCP=
+ 
CLASSPATH=:::/etc/cloudstack/management:/usr/share/cloudstack-management/setup
+ for jarfile in '"/usr/share/cloudstack-management/premium"/*'
+ '[' '!' -e '/usr/share/cloudstack-management/premium/*' ']'
+ continue
+ for plugin in '"/usr/share/cloudstack-management/plugin"/*'
+ '[' '!' -e '/usr/share/cloudstack-management/plugin/*' ']'
+ continue
+ for vendorconf in '"/etc/cloudstack/management"/vendor/*'
+ '[' '!' -d '/etc/cloudstack/management/vendor/*' ']'
+ continue
+ export CLASSPATH
+ PATH=/sbin:/usr/sbin:/sbin:/usr/sbin:/bin:/usr/bin
+ export PATH
++ CONNECTOR_PORT=8080
++ TOMCAT_SCRIPT=/usr/sbin/tomcat6
++ TOMCAT_PROG=cloudstack-management
++ TOMCAT_USER=cloud
++ TOMCAT_LOG=/var/log/cloudstack/management//catalina.out
++ export CATALINA_PID=/var/run/cloudstack-management.pid
++ CATALINA_PID=/var/run/cloudstack-management.pid
++ RETVAL=0
++ RETVAL=0
++ case "$1" in
++ start
++ echo -n 'Starting cloudstack-management: '
Starting cloudstack-management: ++ '[' 0 '!=' 0 ']'
++ '[' -f /var/lock/subsys/cloudstack-management ']'
++ touch /var/run/cloudstack-management.pid
++ '[' 0 -eq 0 -a 0 -eq 0 ']'
++ chown cloud:cloud /var/run/cloudstack-management.pid
++ parseOptions
++ options=
+++ awk '

[jira] [Created] (CLOUDSTACK-2782) UI Support to add/remove VMware DC to CloudStack zone.

2013-05-31 Thread ASF subversion and git services (JIRA)

Sateesh Chodapuneedi created CLOUDSTACK-2782:


 Summary: UI Support to add/remove VMware DC to CloudStack zone.
 Key: CLOUDSTACK-2782
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2782
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Sateesh Chodapuneedi
 Fix For: 4.2.0


Need to modify zone wizard to allow adding VMware DC to Cloudstack zone.
We allow adding/removing cluster to/from zone outside of zone creation wizard. 
Similarly need means to add/remove VMware DC to CloudStack zone.

API commands are -
To remove VMware DC from cloudstack zone :-
http://10.102.192.110:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json
To add VMware DC to cloudstack zone :-
http://10.102.192.110:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=vCenter!9&url=http%3A%2F%2F10.102.192.248%2Fdc%2Fc2&response=json

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671256#comment-13671256
 ] 

ASF subversion and git services commented on CLOUDSTACK-1963:
-

Commit 3696605ad6b02706ac40c776d2821abef98a993f in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3696605 ]

CLOUDSTACK-1963 New mapping model for CloudStack zone and Vmware datacenter

DB schema changes to support this feature.
Added 3 new tables.
'vmware_data_center' to persist information about each Vmware datacenter known 
to cloudstack.
'vmware_data_center_zone_map' to persist mapping information of a Vmware 
datacenter & cloudstack zone.
'legacy_zones' to persist the known legacy zones in the deployment.

Signed-off-by: Sateesh Chodapuneedi 


> New mapping model for CloudStack zone and Vmware datacenter 
> 
>
> Key: CLOUDSTACK-1963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Functional specification document is here, 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Branch for this feature's code is refs/heads/vmware-datamodel 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671252#comment-13671252
 ] 

ASF subversion and git services commented on CLOUDSTACK-1963:
-

Commit 4b67b1d36a0c441c7e1125420f27e572728c2e25 in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4b67b1d ]

CLOUDSTACK-1963 New mapping model for CloudStack zone and Vmware datacenter

Unit tests to test functionality of the feature.

Signed-off-by: Sateesh Chodapuneedi 


> New mapping model for CloudStack zone and Vmware datacenter 
> 
>
> Key: CLOUDSTACK-1963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Functional specification document is here, 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Branch for this feature's code is refs/heads/vmware-datamodel 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671254#comment-13671254
 ] 

ASF subversion and git services commented on CLOUDSTACK-1963:
-

Commit cf2b8694b55684f7aa04f3d672827449357f7749 in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cf2b869 ]

CLOUDSTACK-1963 New mapping model for CloudStack zone and Vmware datacenter

Adding all new beans introduced during the feature implementation to nonoss 
component context.

Signed-off-by: Sateesh Chodapuneedi 


> New mapping model for CloudStack zone and Vmware datacenter 
> 
>
> Key: CLOUDSTACK-1963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Functional specification document is here, 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Branch for this feature's code is refs/heads/vmware-datamodel 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671253#comment-13671253
 ] 

ASF subversion and git services commented on CLOUDSTACK-1963:
-

Commit 2b0ca781d8c607c6c8820be6c9119f75b4cd44ae in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2b0ca78 ]

CLOUDSTACK-1963 New mapping model for CloudStack zone and Vmware datacenter

Upgrade handling.
Detect legacy zones during db upgrade and perform data migration.
If legacy zone is detected the table 'cloud'.'legacy_zones' is populated.
If an existing zone which has resources that belong to single VMware datacenter 
then such zone would not be marked as legacy zone. Such zone would be 
automatically associated with the specific Vmware datacenter of the clusters 
inside the zone.

Signed-off-by: Sateesh Chodapuneedi 


> New mapping model for CloudStack zone and Vmware datacenter 
> 
>
> Key: CLOUDSTACK-1963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Functional specification document is here, 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Branch for this feature's code is refs/heads/vmware-datamodel 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671257#comment-13671257
 ] 

Sateesh Chodapuneedi commented on CLOUDSTACK-1963:
--

Feature merged into master.

> New mapping model for CloudStack zone and Vmware datacenter 
> 
>
> Key: CLOUDSTACK-1963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Functional specification document is here, 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Branch for this feature's code is refs/heads/vmware-datamodel 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2783) listHypervisorCapabilities API is not providing maxdatavolume, maxhostspercluster and storagemotionenabled fields in the repsonse

2013-05-31 Thread Srikanteswararao Talluri (JIRA)

Srikanteswararao Talluri created CLOUDSTACK-2783:


 Summary: listHypervisorCapabilities API is not providing 
maxdatavolume, maxhostspercluster and storagemotionenabled fields in the 
repsonse
 Key: CLOUDSTACK-2783
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2783
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
 Fix For: 4.2.0


listHypervisorCapabilities API is not providing maxdatavolume, 
maxhostspercluster and storagemotionenabled fields in the repsonse


17

1
default
XenServer
50
true


2
XCP 1.0
XenServer
50
true


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2783) listHypervisorCapabilities API is not providing maxdatavolume, maxhostspercluster and storagemotionenabled fields in the repsonse

2013-05-31 Thread Srikanteswararao Talluri (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Srikanteswararao Talluri reassigned CLOUDSTACK-2783:


Assignee: Srikanteswararao Talluri

> listHypervisorCapabilities API is not providing maxdatavolume, 
> maxhostspercluster and storagemotionenabled fields in the repsonse
> -
>
> Key: CLOUDSTACK-2783
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2783
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Srikanteswararao Talluri
>Assignee: Srikanteswararao Talluri
> Fix For: 4.2.0
>
>
> listHypervisorCapabilities API is not providing maxdatavolume, 
> maxhostspercluster and storagemotionenabled fields in the repsonse
> 
> 17
> 
> 1
> default
> XenServer
> 50
> true
> 
> 
> 2
> XCP 1.0
> XenServer
> 50
> true
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1192) Add disk I/O polling to statistics accounting of Instances


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671266#comment-13671266
 ] 

ASF subversion and git services commented on CLOUDSTACK-1192:
-

Commit 385ca81e01754f0f65c18d32f0d35b41616498ac in branch 
refs/heads/disk_io_stat from [~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=385ca81 ]

CLOUDSTACK-1192: add RBD support


> Add disk I/O polling to statistics accounting of Instances
> --
>
> Key: CLOUDSTACK-1192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1192
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller, Usage
>Affects Versions: 4.2.0
>Reporter: Wido den Hollander
>Assignee: Wei Zhou
>  Labels: I/O, IOps
> Fix For: 4.2.0
>
>
> In public clouds (and also private ones) it's important to know how much disk 
> I/O each Instance is consuming.
> Today disk I/O is more expensive then RAM, CPU and Network bandwith, but 
> CloudStack has no way of accounting this.
> CloudStack should collect the disk I/O statistics of all running instances so 
> we can present these in the UI and in the Usage server
> The wiki page for this improvement: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Disk+IO+statistics+for+instances

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671272#comment-13671272
 ] 

Sateesh Chodapuneedi commented on CLOUDSTACK-1963:
--

UI changes are being tracked at CLOUDSTACK-2782


> New mapping model for CloudStack zone and Vmware datacenter 
> 
>
> Key: CLOUDSTACK-1963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Functional specification document is here, 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
> Branch for this feature's code is refs/heads/vmware-datamodel 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2029) zone wide primary storage support for cloudstack over vmware deployments


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671275#comment-13671275
 ] 

Sateesh Chodapuneedi commented on CLOUDSTACK-2029:
--

UI changes are being tracked at sub-task ticket CLOUDSTACK-2784

> zone wide primary storage support for cloudstack over vmware deployments
> 
>
> Key: CLOUDSTACK-2029
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2029
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller, VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Support for primary storage that span across clusters in CloudStack zone.
> Similar to Amazon's EBS.
> This is to facilitate virtual disk availability across clusters.
> Functional Specification: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Zone-wide+primary+storage+target
>  
> A dedicated section is being added to the above FS with specifics around 
> VMware resource support.
> Code for this feature can be found in branch 
> refs/heads/zone-primarystorage-vmware 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2784) UI changes to provide hypervisor type option while adding zone wide primary storage pool

Sateesh Chodapuneedi created CLOUDSTACK-2784:


 Summary: UI changes to provide hypervisor type option while adding 
zone wide primary storage pool
 Key: CLOUDSTACK-2784
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2784
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
Reporter: Sateesh Chodapuneedi
 Fix For: 4.2.0


Currently UI form to add primary storage pool with scope as ZONE doesn't 
provided option to choose type of hypervisor.
Need to update UI to support this option if user chooses scope of primary 
storage pool as "ZONE".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2785) Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, infrastructure.css

Isaac Chiang created CLOUDSTACK-2785:


 Summary: Missing css files : vnmcAsa1000v.css, 
vnmcNetworkProvider.css, infrastructure.css
 Key: CLOUDSTACK-2785
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2785
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
 Environment: Master
Reporter: Isaac Chiang


The following css files are failed to include : vnmcAsa1000v.css, 
vnmcNetworkProvider.css, infrastructure.css

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2785) Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, infrastructure.css


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isaac Chiang updated CLOUDSTACK-2785:
-

Attachment: Screen Shot 2013-05-31 at 5.29.05 PM.png

Screenshot attached

> Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, 
> infrastructure.css
> -
>
> Key: CLOUDSTACK-2785
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2785
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
> Environment: Master
>Reporter: Isaac Chiang
>  Labels: ui
> Attachments: Screen Shot 2013-05-31 at 5.29.05 PM.png
>
>
> The following css files are failed to include : vnmcAsa1000v.css, 
> vnmcNetworkProvider.css, infrastructure.css

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2786) System VM on vmware setup is not coming up

shweta agarwal created CLOUDSTACK-2786:
--

 Summary: System VM on vmware setup is not coming up
 Key: CLOUDSTACK-2786
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2786
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server, VMware
Affects Versions: 4.2.0
 Environment: build:
CloudStack-non-OSS-MASTER-426-rhel6.3.tar.gz
ESXI5.1 host
NFS Storage
Reporter: shweta agarwal
Priority: Blocker
 Fix For: 4.2.0


Repro steps:
1. Create a VMware zone
2. Enable it

Bug:
I am hitting exception 

2013-05-31 10:59:13,178 INFO  [vmware.manager.VmwareStorageManagerImpl] 
(DirectAgent-1:10.147.40.27) Template routing-8 is not setup yet, setup 
template from secondary storage with uuid name: d5beee04cb3e3a8593e41cb574cc0e9f
2013-05-31 10:59:13,193 INFO  [vmware.manager.VmwareStorageManagerImpl] 
(DirectAgent-1:10.147.40.27) Executing copyTemplateFromSecondaryToPrimary. 
secondaryStorage: nfs://10.147.28.7/export/home/shweta/vmwaresecondary.premium, 
templatePathAtSecondaryStorage: template/tmpl/1/8/, templateName: routing-8
2013-05-31 10:59:13,203 DEBUG [vmware.manager.VmwareManagerImpl] 
(DirectAgent-1:10.147.40.27) Executing: sudo mount -t nfs 
10.147.28.7:/export/home/shweta/vmwaresecondary.premium 
/var/cloudstack/mnt/VM/6909931290812.606fba60
2013-05-31 10:59:13,217 WARN  [vmware.manager.VmwareManagerImpl] 
(DirectAgent-1:10.147.40.27) Exception: sudo mount -t nfs 
10.147.28.7:/export/home/shweta/vmwaresecondary.premium 
/var/cloudstack/mnt/VM/6909931290812.606fba60
java.io.IOException: Cannot run program "sudo": java.io.IOException: error=12, 
Cannot allocate memory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:475)
at com.cloud.utils.script.Script.execute(Script.java:183)
at com.cloud.utils.script.Script.execute(Script.java:161)
at 
com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.mount(VmwareManagerImpl.java:690)
at 
com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.getMountPoint(VmwareManagerImpl.java:598)
at 
com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:559)
at 
com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:262)
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3939)
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:436)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.io.IOException: java.io.IOException: error=12, Cannot allocate 
memory
at java.lang.UNIXProcess.(UNIXProcess.java:164)
at java.lang.ProcessImpl.start(ProcessImpl.java:81)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:468)
... 17 more
2013-05-31 10:59:13,218 WARN  [vmware.manager.VmwareManagerImpl] 
(DirectAgent-1:10.147.40.27) Unable to mount 
10.147.28.7:/export/home/shweta/vmwaresecondary.premium due to 
java.io.IOException: Cannot run program "sudo": java.io.IOException: error=12, 
Cannot allocate memory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:475)
at com.cloud.utils.script.Script.execute(Script.java:183)
at com.cloud.utils.script.Script.execute(Script.java:161)

   
 at com.cloud.utils.script.Script.execute(Script.java:161)
at 
com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.mount(VmwareManagerImpl.java:690)
at 
com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.getMountPoint(VmwareManagerImpl.java:598)
at 
com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:559)
at 
com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:262)
at 
com.cloud.hypervisor.vmware

[jira] [Updated] (CLOUDSTACK-2686) Upload volume to project is not shown in project storage view


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal updated CLOUDSTACK-2686:
---

Attachment: management-server.log

> Upload volume to project is not shown in project storage view
> -
>
> Key: CLOUDSTACK-2686
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2686
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Volumes
>Affects Versions: 4.2.0
> Environment: build:
> CloudStack-non-OSS-MASTER-389-rhel6.3
>Reporter: shweta agarwal
>Assignee: Mice Xia
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log
>
>
> Repro steps:
> 1. Create a Project
> 2. Upload a Volume to the project
> Bug:
> Volume uploaded does not belong to project . Uploaded volume is not shown in 
> Project Storage view
> Expected result:
> Uploaded volume should belong to the project and should be shown in  Project 
> storage View.
> API call :
> http://10.147.59.212:8080/client/api?command=uploadVolume&response=json&sessionkey=yV6GY8KRbZ27uN8vauSKUwtCBcM%3D&projectid=e2a9e94d-0285-4c07-943c-9e666f9d9d61&name=ov&zoneId=e9d7d1e4-9020-427e-ac13-25cefbc72b28&format=OVA&url=http%3A%2F%2F10.147.28.7%2Ftemplates%2Fvmware%2FCentos6_2.ova&_=1369632336913
> http://10.147.59.212:8080/client/api?command=queryAsyncJobResult&jobId=009686d9-a383-4d57-a2e8-9838f91ef0ab&response=json&sessionkey=yV6GY8KRbZ27uN8vauSKUwtCBcM%3D&projectid=e2a9e94d-0285-4c07-943c-9e666f9d9d61&_=1369632340133
> Response:
> { "queryasyncjobresultresponse" : 
> {"accountid":"7b3e166c-c399-11e2-8675-0648d8bc","userid":"7b3eb860-c399-11e2-8675-0648d8bc","cmd":"org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd","jobstatus":1,"jobprocstatus":0,"jobresultcode":0,"jobresulttype":"object","jobresult":{"volume":{"id":"beabdf48-31ff-4118-8899-77b66d3aa40e","name":"ov","zoneid":"e9d7d1e4-9020-427e-ac13-25cefbc72b28","zonename":"vmware","zonetype":"Advanced","type":"DATADISK","size":0,"created":"2013-05-27T06:54:33-0400","state":"Uploaded","account":"admin","domainid":"51a5a572-c399-11e2-8675-0648d8bc","domain":"ROOT","storagetype":"shared","diskofferingid":"831db814-883b-489a-9c6a-ae7084ba8bdb","diskofferingname":"Custom","diskofferingdisplaytext":"Custom
>  
> Disk","destroyed":false,"isextractable":true,"tags":[],"displayvolume":false}},"created":"2013-05-27T06:54:33-0400","jobid":"009686d9-a383-4d57-a2e8-9838f91ef0ab"}
>  }
> The issue is in response instead of getting project id  and project as 
> parameter  its getting account as parameter . So the uploaded volume gets 
> assign to account owner instead of project .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2782) UI Support to add/remove VMware DC to CloudStack zone.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sateesh Chodapuneedi updated CLOUDSTACK-2782:
-

Description: 
Need to modify zone wizard to allow adding VMware DC to Cloudstack zone.
We allow adding/removing cluster to/from zone outside of zone creation wizard. 
Similarly need means to add/remove VMware DC to CloudStack zone.

API commands are -
To remove VMware DC from cloudstack zone :-
http://MSIP:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json
To add VMware DC to cloudstack zone :-
http://MSIP:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=keys&url=http%3A%2F%2FVCENTER%2Fdc%2Fc2&response=json

  was:
Need to modify zone wizard to allow adding VMware DC to Cloudstack zone.
We allow adding/removing cluster to/from zone outside of zone creation wizard. 
Similarly need means to add/remove VMware DC to CloudStack zone.

API commands are -
To remove VMware DC from cloudstack zone :-
http://MSIP:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json
To add VMware DC to cloudstack zone :-
http://MSIP:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=vCenter!9&url=http%3A%2F%2F10.102.192.248%2Fdc%2Fc2&response=json


> UI Support to add/remove VMware DC to CloudStack zone.
> --
>
> Key: CLOUDSTACK-2782
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2782
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Need to modify zone wizard to allow adding VMware DC to Cloudstack zone.
> We allow adding/removing cluster to/from zone outside of zone creation 
> wizard. Similarly need means to add/remove VMware DC to CloudStack zone.
> API commands are -
> To remove VMware DC from cloudstack zone :-
> http://MSIP:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json
> To add VMware DC to cloudstack zone :-
> http://MSIP:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=keys&url=http%3A%2F%2FVCENTER%2Fdc%2Fc2&response=json

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2782) UI Support to add/remove VMware DC to CloudStack zone.


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sateesh Chodapuneedi updated CLOUDSTACK-2782:
-

Description: 
Need to modify zone wizard to allow adding VMware DC to Cloudstack zone.
We allow adding/removing cluster to/from zone outside of zone creation wizard. 
Similarly need means to add/remove VMware DC to CloudStack zone.

API commands are -
To remove VMware DC from cloudstack zone :-
http://MSIP:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json
To add VMware DC to cloudstack zone :-
http://MSIP:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=vCenter!9&url=http%3A%2F%2F10.102.192.248%2Fdc%2Fc2&response=json

  was:
Need to modify zone wizard to allow adding VMware DC to Cloudstack zone.
We allow adding/removing cluster to/from zone outside of zone creation wizard. 
Similarly need means to add/remove VMware DC to CloudStack zone.

API commands are -
To remove VMware DC from cloudstack zone :-
http://10.102.192.110:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json
To add VMware DC to cloudstack zone :-
http://10.102.192.110:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=vCenter!9&url=http%3A%2F%2F10.102.192.248%2Fdc%2Fc2&response=json


> UI Support to add/remove VMware DC to CloudStack zone.
> --
>
> Key: CLOUDSTACK-2782
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2782
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Need to modify zone wizard to allow adding VMware DC to Cloudstack zone.
> We allow adding/removing cluster to/from zone outside of zone creation 
> wizard. Similarly need means to add/remove VMware DC to CloudStack zone.
> API commands are -
> To remove VMware DC from cloudstack zone :-
> http://MSIP:8096/?command=removeVmwareDc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&response=json
> To add VMware DC to cloudstack zone :-
> http://MSIP:8096/?command=addVmwareDc&name=dc&zoneId=68da495b-cbb1-428c-a292-7686f02f9576&username=administrator&password=vCenter!9&url=http%3A%2F%2F10.102.192.248%2Fdc%2Fc2&response=json

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2786) System VM on vmware setup is not coming up


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal updated CLOUDSTACK-2786:
---

Attachment: management-server.log

> System VM on vmware setup is not coming up
> --
>
> Key: CLOUDSTACK-2786
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2786
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.2.0
> Environment: build:
> CloudStack-non-OSS-MASTER-426-rhel6.3.tar.gz
> ESXI5.1 host
> NFS Storage
>Reporter: shweta agarwal
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.log
>
>
> Repro steps:
> 1. Create a VMware zone
> 2. Enable it
> Bug:
> I am hitting exception 
> 2013-05-31 10:59:13,178 INFO  [vmware.manager.VmwareStorageManagerImpl] 
> (DirectAgent-1:10.147.40.27) Template routing-8 is not setup yet, setup 
> template from secondary storage with uuid name: 
> d5beee04cb3e3a8593e41cb574cc0e9f
> 2013-05-31 10:59:13,193 INFO  [vmware.manager.VmwareStorageManagerImpl] 
> (DirectAgent-1:10.147.40.27) Executing copyTemplateFromSecondaryToPrimary. 
> secondaryStorage: 
> nfs://10.147.28.7/export/home/shweta/vmwaresecondary.premium, 
> templatePathAtSecondaryStorage: template/tmpl/1/8/, templateName: routing-8
> 2013-05-31 10:59:13,203 DEBUG [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-1:10.147.40.27) Executing: sudo mount -t nfs 
> 10.147.28.7:/export/home/shweta/vmwaresecondary.premium 
> /var/cloudstack/mnt/VM/6909931290812.606fba60
> 2013-05-31 10:59:13,217 WARN  [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-1:10.147.40.27) Exception: sudo mount -t nfs 
> 10.147.28.7:/export/home/shweta/vmwaresecondary.premium 
> /var/cloudstack/mnt/VM/6909931290812.606fba60
> java.io.IOException: Cannot run program "sudo": java.io.IOException: 
> error=12, Cannot allocate memory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:475)
> at com.cloud.utils.script.Script.execute(Script.java:183)
> at com.cloud.utils.script.Script.execute(Script.java:161)
> at 
> com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.mount(VmwareManagerImpl.java:690)
> at 
> com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.getMountPoint(VmwareManagerImpl.java:598)
> at 
> com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:559)
> at 
> com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:262)
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3939)
> at 
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:436)
> at 
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.io.IOException: java.io.IOException: error=12, Cannot 
> allocate memory
> at java.lang.UNIXProcess.(UNIXProcess.java:164)
> at java.lang.ProcessImpl.start(ProcessImpl.java:81)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:468)
> ... 17 more
> 2013-05-31 10:59:13,218 WARN  [vmware.manager.VmwareManagerImpl] 
> (DirectAgent-1:10.147.40.27) Unable to mount 
> 10.147.28.7:/export/home/shweta/vmwaresecondary.premium due to 
> java.io.IOException: Cannot run program "sudo": java.io.IOException: 
> error=12, Cannot allocate memory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:475)
> at com.cloud.utils.script.Script.execute(Script.java:183)
> at com.cloud.utils.script.Script.execute(Script.java:161)
>   
>  
>  at com.cloud.utils.script.Script.execute(Script.java:161)
> at 
> com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.mount(VmwareManagerImpl.j

[jira] [Updated] (CLOUDSTACK-2506) create network dialog is not displaying network offerings with specifyvlan=true to admin


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

shweta agarwal updated CLOUDSTACK-2506:
---

Priority: Blocker  (was: Critical)

> create network dialog is not displaying network offerings with 
> specifyvlan=true to admin
> 
>
> Key: CLOUDSTACK-2506
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2506
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
> Environment: build:
> CloudStack-non-OSS-MASTER-329-rhel6.3
>Reporter: shweta agarwal
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Repro steps:
> 1. Create a network offerings with specify vlan=true 
> 2. As a root admin Goto network tab and open create network dialog
> Bug:
> Notice its not showing network offerings created in step 1 
> Expected result:
> It should show the network offerings created in step1
> Actually When we open create network dialog presently its only firing 
> following api
> http://10.147.59.212:8080/client/api?command=listNetworkOfferings&zoneid=dd1f4b0f-bc77-4b3b-8f47-45130d4b816a&forVpc=false&response=json&sessionkey=dNddt90WhymsHK2%2FNj9eD5fZbWk%3D&guestiptype=Isolated&supportedServices=SourceNat&specifyvlan=false&state=Enabled&_=1368600062363
> it need to fire one more api with specifyvlan=true param value for isolated 
> network

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2785) Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, infrastructure.css

2013-05-31 Thread Pranav Saxena (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671383#comment-13671383
 ] 

Pranav Saxena commented on CLOUDSTACK-2785:
---

Isaac , I know you must have seen them in the firebug logs but this is not an 
issue actually since all these CSS files are part of the plugin framework and 
are loaded dynamically when the plugin is activated .We'll try to handle the 
this. 

Thanks,
Pranav

> Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, 
> infrastructure.css
> -
>
> Key: CLOUDSTACK-2785
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2785
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
> Environment: Master
>Reporter: Isaac Chiang
>  Labels: ui
> Attachments: Screen Shot 2013-05-31 at 5.29.05 PM.png
>
>
> The following css files are failed to include : vnmcAsa1000v.css, 
> vnmcNetworkProvider.css, infrastructure.css

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2787) updateVpcOffering should have id as a required attribute

2013-05-31 Thread ASF subversion and git services (JIRA)

Prasanna Santhanam created CLOUDSTACK-2787:
--

 Summary: updateVpcOffering should have id as a required attribute
 Key: CLOUDSTACK-2787
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2787
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.2.0
Reporter: Prasanna Santhanam
 Fix For: 4.2.0


id is not a required attribute in updateVpcOfferingCmd.java but without the id 
one cannot update the vpc offering.

@APICommand(name = "updateVPCOffering", description="Updates VPC offering", 
responseObject=VpcOfferingResponse.class)
public class UpdateVPCOfferingCmd extends BaseAsyncCmd{
public static final Logger s_logger = 
Logger.getLogger(UpdateVPCOfferingCmd.class.getName());
private static final String _name = "updatevpcofferingresponse";

/
 API parameters /
/

@Parameter(name=ApiConstants.ID, type=CommandType.UUID, entityType = 
VpcOfferingResponse.class,
description="the id of the VPC offering")
private Long id;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2787) updateVpcOffering should have id as a required attribute


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671387#comment-13671387
 ] 

ASF subversion and git services commented on CLOUDSTACK-2787:
-

Commit aefcee5753d4a050bdb38fd1a51f1e1de1a634ae in branch refs/heads/master 
from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=aefcee5 ]

CLOUDSTACK-2787: updateVpcOffering should have id as a required

without the id you cannot update a VPC offering. The docs for API will
go wrong and Marvin tests using update VPC will fail.

Signed-off-by: Prasanna Santhanam 


> updateVpcOffering should have id as a required attribute
> 
>
> Key: CLOUDSTACK-2787
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2787
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in updateVpcOfferingCmd.java but without the 
> id one cannot update the vpc offering.
> @APICommand(name = "updateVPCOffering", description="Updates VPC offering", 
> responseObject=VpcOfferingResponse.class)
> public class UpdateVPCOfferingCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(UpdateVPCOfferingCmd.class.getName());
> private static final String _name = "updatevpcofferingresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, entityType = 
> VpcOfferingResponse.class,
> description="the id of the VPC offering")
> private Long id;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2787) updateVpcOffering should have id as a required attribute


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam resolved CLOUDSTACK-2787.


Resolution: Fixed

> updateVpcOffering should have id as a required attribute
> 
>
> Key: CLOUDSTACK-2787
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2787
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in updateVpcOfferingCmd.java but without the 
> id one cannot update the vpc offering.
> @APICommand(name = "updateVPCOffering", description="Updates VPC offering", 
> responseObject=VpcOfferingResponse.class)
> public class UpdateVPCOfferingCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(UpdateVPCOfferingCmd.class.getName());
> private static final String _name = "updatevpcofferingresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, entityType = 
> VpcOfferingResponse.class,
> description="the id of the VPC offering")
> private Long id;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2506) create network dialog is not displaying network offerings with specifyvlan=true to admin

2013-05-31 Thread Pranav Saxena (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671418#comment-13671418
 ] 

Pranav Saxena commented on CLOUDSTACK-2506:
---

Did you activate source NAT service while creating the offering ? 

> create network dialog is not displaying network offerings with 
> specifyvlan=true to admin
> 
>
> Key: CLOUDSTACK-2506
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2506
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
> Environment: build:
> CloudStack-non-OSS-MASTER-329-rhel6.3
>Reporter: shweta agarwal
>Priority: Blocker
> Fix For: 4.2.0
>
>
> Repro steps:
> 1. Create a network offerings with specify vlan=true 
> 2. As a root admin Goto network tab and open create network dialog
> Bug:
> Notice its not showing network offerings created in step 1 
> Expected result:
> It should show the network offerings created in step1
> Actually When we open create network dialog presently its only firing 
> following api
> http://10.147.59.212:8080/client/api?command=listNetworkOfferings&zoneid=dd1f4b0f-bc77-4b3b-8f47-45130d4b816a&forVpc=false&response=json&sessionkey=dNddt90WhymsHK2%2FNj9eD5fZbWk%3D&guestiptype=Isolated&supportedServices=SourceNat&specifyvlan=false&state=Enabled&_=1368600062363
> it need to fire one more api with specifyvlan=true param value for isolated 
> network

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2788) restartVpc should have id as a required attribute


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam updated CLOUDSTACK-2788:
---

Summary: restartVpc should have id as a required attribute  (was: 
restartVpcOffering should have id as a required attribute)

> restartVpc should have id as a required attribute
> -
>
> Key: CLOUDSTACK-2788
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2788
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in restartVpcOfferingCmd.java but without the 
> id one cannot update the vpc offering.
> @APICommand(name = "restartVPC", description="Restarts a VPC", 
> responseObject=VpcResponse.class)
> public class RestartVPCCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(RestartVPCCmd.class.getName());
> private static final String _name = "restartvpcresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
> entityType=VpcResponse.class,
> description="the id of the VPC")
> private Long id;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2788) restartVpcOffering should have id as a required attribute


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam updated CLOUDSTACK-2788:
---

Description: 
id is not a required attribute in restartVpcOfferingCmd.java but without the id 
one cannot update the vpc offering.


@APICommand(name = "restartVPC", description="Restarts a VPC", 
responseObject=VpcResponse.class)
public class RestartVPCCmd extends BaseAsyncCmd{
public static final Logger s_logger = 
Logger.getLogger(RestartVPCCmd.class.getName());
private static final String _name = "restartvpcresponse";

/
 API parameters /
/

@Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
entityType=VpcResponse.class,
description="the id of the VPC")
private Long id;


  was:
id is not a required attribute in updateVpcOfferingCmd.java but without the id 
one cannot update the vpc offering.

@APICommand(name = "updateVPCOffering", description="Updates VPC offering", 
responseObject=VpcOfferingResponse.class)
public class UpdateVPCOfferingCmd extends BaseAsyncCmd{
public static final Logger s_logger = 
Logger.getLogger(UpdateVPCOfferingCmd.class.getName());
private static final String _name = "updatevpcofferingresponse";

/
 API parameters /
/

@Parameter(name=ApiConstants.ID, type=CommandType.UUID, entityType = 
VpcOfferingResponse.class,
description="the id of the VPC offering")
private Long id;


> restartVpcOffering should have id as a required attribute
> -
>
> Key: CLOUDSTACK-2788
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2788
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in restartVpcOfferingCmd.java but without the 
> id one cannot update the vpc offering.
> @APICommand(name = "restartVPC", description="Restarts a VPC", 
> responseObject=VpcResponse.class)
> public class RestartVPCCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(RestartVPCCmd.class.getName());
> private static final String _name = "restartvpcresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
> entityType=VpcResponse.class,
> description="the id of the VPC")
> private Long id;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2788) restartVpcOffering should have id as a required attribute

Prasanna Santhanam created CLOUDSTACK-2788:
--

 Summary: restartVpcOffering should have id as a required attribute
 Key: CLOUDSTACK-2788
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2788
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.2.0
Reporter: Prasanna Santhanam
 Fix For: 4.2.0


id is not a required attribute in updateVpcOfferingCmd.java but without the id 
one cannot update the vpc offering.

@APICommand(name = "updateVPCOffering", description="Updates VPC offering", 
responseObject=VpcOfferingResponse.class)
public class UpdateVPCOfferingCmd extends BaseAsyncCmd{
public static final Logger s_logger = 
Logger.getLogger(UpdateVPCOfferingCmd.class.getName());
private static final String _name = "updatevpcofferingresponse";

/
 API parameters /
/

@Parameter(name=ApiConstants.ID, type=CommandType.UUID, entityType = 
VpcOfferingResponse.class,
description="the id of the VPC offering")
private Long id;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2789) updateVpc should have id and name as required attributes

Prasanna Santhanam created CLOUDSTACK-2789:
--

 Summary: updateVpc should have id and name as required attributes
 Key: CLOUDSTACK-2789
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2789
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.2.0
Reporter: Prasanna Santhanam
 Fix For: 4.2.0


id is not a required attribute in restartVpcOfferingCmd.java but without the id 
one cannot update the vpc offering.


@APICommand(name = "restartVPC", description="Restarts a VPC", 
responseObject=VpcResponse.class)
public class RestartVPCCmd extends BaseAsyncCmd{
public static final Logger s_logger = 
Logger.getLogger(RestartVPCCmd.class.getName());
private static final String _name = "restartvpcresponse";

/
 API parameters /
/

@Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
entityType=VpcResponse.class,
description="the id of the VPC")
private Long id;


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2789) updateVpc should have id and name as required attributes


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam updated CLOUDSTACK-2789:
---

Description: 
id is not a required attribute in updateVpcCMd.java but without the id and a 
name one cannot update the vpc.


@APICommand(name = "updateVPC", description="Updates a VPC", 
responseObject=VpcResponse.class)
public class UpdateVPCCmd extends BaseAsyncCmd{
public static final Logger s_logger = 
Logger.getLogger(UpdateVPCCmd.class.getName());
private static final String _name = "updatevpcresponse";

/
 API parameters /
/

@Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
entityType=VpcResponse.class,
description="the id of the VPC")
private Long id;

@Parameter(name=ApiConstants.NAME, type=CommandType.STRING, 
description="the name of the VPC")
private String vpcName;


  was:
id is not a required attribute in restartVpcOfferingCmd.java but without the id 
one cannot update the vpc offering.


@APICommand(name = "restartVPC", description="Restarts a VPC", 
responseObject=VpcResponse.class)
public class RestartVPCCmd extends BaseAsyncCmd{
public static final Logger s_logger = 
Logger.getLogger(RestartVPCCmd.class.getName());
private static final String _name = "restartvpcresponse";

/
 API parameters /
/

@Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
entityType=VpcResponse.class,
description="the id of the VPC")
private Long id;



> updateVpc should have id and name as required attributes
> 
>
> Key: CLOUDSTACK-2789
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2789
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in updateVpcCMd.java but without the id and a 
> name one cannot update the vpc.
> @APICommand(name = "updateVPC", description="Updates a VPC", 
> responseObject=VpcResponse.class)
> public class UpdateVPCCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(UpdateVPCCmd.class.getName());
> private static final String _name = "updatevpcresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
> entityType=VpcResponse.class,
> description="the id of the VPC")
> private Long id;
> @Parameter(name=ApiConstants.NAME, type=CommandType.STRING, 
> description="the name of the VPC")
> private String vpcName;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2788) restartVpc should have id as a required attribute

2013-05-31 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam updated CLOUDSTACK-2788:
---

Description: 
id is not a required attribute in restartVpcCmd.java but without the id one 
cannot update the vpc offering.


@APICommand(name = "restartVPC", description="Restarts a VPC", 
responseObject=VpcResponse.class)
public class RestartVPCCmd extends BaseAsyncCmd{
public static final Logger s_logger = 
Logger.getLogger(RestartVPCCmd.class.getName());
private static final String _name = "restartvpcresponse";

/
 API parameters /
/

@Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
entityType=VpcResponse.class,
description="the id of the VPC")
private Long id;


  was:
id is not a required attribute in restartVpcOfferingCmd.java but without the id 
one cannot update the vpc offering.


@APICommand(name = "restartVPC", description="Restarts a VPC", 
responseObject=VpcResponse.class)
public class RestartVPCCmd extends BaseAsyncCmd{
public static final Logger s_logger = 
Logger.getLogger(RestartVPCCmd.class.getName());
private static final String _name = "restartvpcresponse";

/
 API parameters /
/

@Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
entityType=VpcResponse.class,
description="the id of the VPC")
private Long id;



> restartVpc should have id as a required attribute
> -
>
> Key: CLOUDSTACK-2788
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2788
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in restartVpcCmd.java but without the id one 
> cannot update the vpc offering.
> @APICommand(name = "restartVPC", description="Restarts a VPC", 
> responseObject=VpcResponse.class)
> public class RestartVPCCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(RestartVPCCmd.class.getName());
> private static final String _name = "restartvpcresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
> entityType=VpcResponse.class,
> description="the id of the VPC")
> private Long id;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2285) [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed in basic zone


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671460#comment-13671460
 ] 

ASF subversion and git services commented on CLOUDSTACK-2285:
-

Commit f84a27324d2f0c586d825a20f02ebcb149078c84 in branch refs/heads/master 
from Murali Reddy 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f84a273 ]

CLOUDSTACK-2285:[GSLB] addNetscalerLoadBalancer with GSLB functionality
shouldn't be exposed in basic zone

reverting the original fix for this bug. When you add network service
provider instance into a physical network in a basic zone, its not
necessary that a network has been provisioned into zone. So its no
straight-forward to know if the basic zone network has EIP/ELB services enabled.


> [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed 
> in basic zone
> --
>
> Key: CLOUDSTACK-2285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit 0e2ffe72aa641f4551cae63fbc36454c5934342f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: api.log.tgz
>
>
> Steps to reproduce :
> 1. Have a basic zone setup with at least one XEN cluster using the offering 
> "DefaultSharedNetworkOfferingWithSGService"
> 2. Try "addNetscalerLoadBalancer" with GSLB enabled
> Observations:
> (i) It gets added successfully.
> command=addNetscalerLoadBalancer&physicalnetworkid=4dbe1d3c-1cee-4f88-aeca-45c4a8a76b4d&username=nsroot&password=nsroot&networkdevicetype=NetscalerVPXLoadBalancer&gslbprovider=true&gslbproviderpublicip=1.1.1.1&gslbproviderprivateip=1.1.1.1&url=https://10.147.54.5?publicinterface=1/1&privateinterface=1/2&numretries=2&lbdevicededicated=false&;
> mysql> select id,name,networktype from data_center where id=1;
> ++---+-+
> | id | name  | networktype |
> ++---+-+
> |  1 | zone1 | Basic   |
> ++---+-+
> mysql> select * from external_load_balancer_devices where id=2\G
> *** 1. row ***
>  id: 2
>uuid: 8c467bfc-7ac3-410a-92d7-11e5853a5d79
> physical_network_id: 200
>   provider_name: Netscaler
> device_name: NetscalerVPXLoadBalancer
>capacity: 50
>device_state: Enabled
>allocation_state: Free
>is_dedicated: 0
>  is_managed: 0
> host_id: 15
>  parent_host_id: 0
>is_gslb_provider: 1
>  gslb_site_publicip: NULL
> gslb_site_privateip: 1.1.1.1
> (ii) There is no need for enabling GSLB functionality in basic zones created 
> with above network offerings because there is no LB feature enabled in this 
> case.
> May be having a check at the API level and allowing it only based on type of 
> zone will help in this case but, if we are supporting GSLB for ELB enabled 
> zones then we need to handle that situation as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2332) [GSLB] deleteAccount is not cleaning the gslb rules created by the account

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671458#comment-13671458
 ] 

ASF subversion and git services commented on CLOUDSTACK-2332:
-

Commit 9c0f9aceb8ccfef7b3b5d0a58a619cb8e32f1eea in branch refs/heads/master 
from Murali Reddy 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9c0f9ac ]

CLOUDSTACK-2332:[GSLB] deleteAccount is not cleaning the gslb rules
created by the account

revoking GSLB rules of account on delete


> [GSLB] deleteAccount is not cleaning the gslb rules created by the account
> --
>
> Key: CLOUDSTACK-2332
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2332
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit #09af15035b9febe6f55e73a1389f950ab042564f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have at least one account other than admin
> 2. login as the above created account
> 3. Go To regions and create a GSLB rule.
> 4. delete the account
> Observations :
> (i) delete account didn't trigger any "deleteGSLBRules" for the account
> (ii) Here is the snippet from mgmt log related to the account cleanup 
> 2013-05-06 06:51:53,699 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-31:job-137) Executing 
> org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd for job-137
> 2013-05-06 06:51:53,738 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Removed account 6
> 2013-05-06 06:51:53,794 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Successfully deleted snapshots directories for all 
> volumes under account 6 across all zones
> 2013-05-06 06:51:53,804 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Expunging # of vms (accountId=6): 0
> 2013-05-06 06:51:53,850 INFO  [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) deleteAccount: Deleted 1 network groups for account 
> 6
> 2013-05-06 06:51:53,857 INFO  [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) deleteAccount: Deleted 0 affinity groups for 
> account 6
> 2013-05-06 06:51:53,857 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Deleting networks for account 6
> 2013-05-06 06:51:53,860 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Deleting vpcs for account 6
> 2013-05-06 06:51:53,878 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Deleting site-to-site VPN customer gateways for 
> account 6
> 2013-05-06 06:51:53,992 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Account specific Virtual IP ranges  are 
> successfully released as a part of account id=6 cleanup.
> 2013-05-06 06:51:53,992 INFO  [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Cleanup for account 6 is not needed.
> 2013-05-06 06:51:54,016 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-31:job-137) Complete async job-137, jobStatus: 1, resultCode: 
> 0, result: org.apache.cloudstack.api.response.SuccessResponse@30005187
> (iii) Account got deleted successfully but, we still see the gslb rule in the 
> DB
> mysql> select * from global_load_balancing_rules;
> ++--++---+---+--+-+++-+--+--+
> | id | uuid | account_id | domain_id | 
> region_id | name | description | state  | algorithm  | persistence | 
> service_type | gslb_domain_name |
> ++--++---+---+--+-+++-+--+--+
> |  2 | 3143a2a5-632b-4621-a9c4-10a98f2a64f3 |  6 | 1 |
>  1 | tmp  | tmp | Staged | roundrobin | sourceip| tcp  | 
> tmp  |
> ++--++---+---+--+-+++-+--+--+
> mysql> select * from account where id=6;
> ++--+--+--+---+-+-+++-+-+
> | id | account_name | uuid | type | domain_id 
> | state   | removed | cleanup_needed | network_domain | 
> default_zone_id | default |
> ++--+-

[jira] [Commented] (CLOUDSTACK-2192) [EIP/Optonal PublicIP] listNetworkOfferings is not returning info about the capability "AssociatePublicIP"

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671459#comment-13671459
 ] 

ASF subversion and git services commented on CLOUDSTACK-2192:
-

Commit 470995b1c41a73f74e77d88663e61d08d7404ffa in branch refs/heads/master 
from Murali Reddy 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=470995b ]

CLOUDSTACK-2192: [EIP/Optonal PublicIP] listNetworkOfferings is not
returning info about the capability "AssociatePublicIP"

added eip and associateEip capability details to the StaticNat service
response


> [EIP/Optonal PublicIP] listNetworkOfferings is not returning info about the 
> capability "AssociatePublicIP"
> --
>
> Key: CLOUDSTACK-2192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2192
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit # 0e2ffe72aa641f4551cae63fbc36454c5934342f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have latest setup from master with EIP offering that has the capability 
> "AssociatePublicIP" set to "False"
>id: 15
>  name: EIPOffering
>  uuid: 6207d909-c780-4661-8a61-7e397aad7b77
>   unique_name: EIPOffering
>  display_text: EIPOffering
>   nw_rate: NULL
>   mc_rate: 10
>  traffic_type: Guest
>  tags: NULL
>   system_only: 0
>  specify_vlan: 1
>   service_offering_id: NULL
> conserve_mode: 0
>   created: 2013-04-24 17:23:07
>   removed: NULL
>   default: 0
>  availability: Optional
>  dedicated_lb_service: 0
> shared_source_nat_service: 0
>  sort_key: 0
>  redundant_router_service: 0
> state: Enabled
>guest_type: Shared
>elastic_ip_service: 1
>   eip_associate_public_ip: 0
>elastic_lb_service: 1
> specify_ip_ranges: 1
>inline: 0
> is_persistent: 0
> select * from networks;
>id: 15
>  name: EIPOffering
>  uuid: 6207d909-c780-4661-8a61-7e397aad7b77
>   unique_name: EIPOffering
>  display_text: EIPOffering
>   nw_rate: NULL
>   mc_rate: 10
>  traffic_type: Guest
>  tags: NULL
>   system_only: 0
>  specify_vlan: 1
>   service_offering_id: NULL
> conserve_mode: 0
>   created: 2013-04-24 17:23:07
>   removed: NULL
>   default: 0
>  availability: Optional
>  dedicated_lb_service: 0
> shared_source_nat_service: 0
>  sort_key: 0
>  redundant_router_service: 0
> state: Enabled
>guest_type: Shared
>elastic_ip_service: 1
>   eip_associate_public_ip: 0
>elastic_lb_service: 1
> specify_ip_ranges: 1
>inline: 0
> is_persistent: 0
> mysql> select * from ntwk_service_map;
> +++---+---+-+
> | id | network_id | service   | provider  | created   
>   |
> +++---+---+-+
> |  1 |204 | SecurityGroup | SecurityGroupProvider | 2013-04-24 
> 17:30:05 |
> |  2 |204 | Dns   | VirtualRouter | 2013-04-24 
> 17:30:05 |
> |  3 |204 | StaticNat | Netscaler | 2013-04-24 
> 17:30:05 |
> |  4 |204 | Dhcp  | VirtualRouter | 2013-04-24 
> 17:30:05 |
> |  5 |204 | UserData  | VirtualRouter | 2013-04-24 
> 17:30:05 |
> |  6 |204 | Lb| Netscaler | 2013-04-24 
> 17:30:05 |
> +++---+---+-+
> 2. Try to fire "listNetworkOfferings" API and verify the output
> Observations:
> (i) Here is the snippet of output
> http://10.147.59.194:8096/api?command=listNetworkOfferings&id=6207d909-c780-4661-8a61-7e397aad7b77&account=admin&response=json
> { "listnetworkofferingsresponse" : { "count":1 ,"networkoffering" : [  
> {"id":"6207d909-c780-4661-8a61-7e397aad7b77","name":"EIPOffering","displaytext":"EIPOffering","t

[jira] [Resolved] (CLOUDSTACK-2332) [GSLB] deleteAccount is not cleaning the gslb rules created by the account

2013-05-31 Thread Murali Reddy (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Murali Reddy resolved CLOUDSTACK-2332.
--

Resolution: Fixed

> [GSLB] deleteAccount is not cleaning the gslb rules created by the account
> --
>
> Key: CLOUDSTACK-2332
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2332
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit #09af15035b9febe6f55e73a1389f950ab042564f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have at least one account other than admin
> 2. login as the above created account
> 3. Go To regions and create a GSLB rule.
> 4. delete the account
> Observations :
> (i) delete account didn't trigger any "deleteGSLBRules" for the account
> (ii) Here is the snippet from mgmt log related to the account cleanup 
> 2013-05-06 06:51:53,699 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-31:job-137) Executing 
> org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd for job-137
> 2013-05-06 06:51:53,738 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Removed account 6
> 2013-05-06 06:51:53,794 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Successfully deleted snapshots directories for all 
> volumes under account 6 across all zones
> 2013-05-06 06:51:53,804 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Expunging # of vms (accountId=6): 0
> 2013-05-06 06:51:53,850 INFO  [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) deleteAccount: Deleted 1 network groups for account 
> 6
> 2013-05-06 06:51:53,857 INFO  [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) deleteAccount: Deleted 0 affinity groups for 
> account 6
> 2013-05-06 06:51:53,857 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Deleting networks for account 6
> 2013-05-06 06:51:53,860 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Deleting vpcs for account 6
> 2013-05-06 06:51:53,878 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Deleting site-to-site VPN customer gateways for 
> account 6
> 2013-05-06 06:51:53,992 DEBUG [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Account specific Virtual IP ranges  are 
> successfully released as a part of account id=6 cleanup.
> 2013-05-06 06:51:53,992 INFO  [cloud.user.AccountManagerImpl] 
> (Job-Executor-31:job-137) Cleanup for account 6 is not needed.
> 2013-05-06 06:51:54,016 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-31:job-137) Complete async job-137, jobStatus: 1, resultCode: 
> 0, result: org.apache.cloudstack.api.response.SuccessResponse@30005187
> (iii) Account got deleted successfully but, we still see the gslb rule in the 
> DB
> mysql> select * from global_load_balancing_rules;
> ++--++---+---+--+-+++-+--+--+
> | id | uuid | account_id | domain_id | 
> region_id | name | description | state  | algorithm  | persistence | 
> service_type | gslb_domain_name |
> ++--++---+---+--+-+++-+--+--+
> |  2 | 3143a2a5-632b-4621-a9c4-10a98f2a64f3 |  6 | 1 |
>  1 | tmp  | tmp | Staged | roundrobin | sourceip| tcp  | 
> tmp  |
> ++--++---+---+--+-+++-+--+--+
> mysql> select * from account where id=6;
> ++--+--+--+---+-+-+++-+-+
> | id | account_name | uuid | type | domain_id 
> | state   | removed | cleanup_needed | network_domain | 
> default_zone_id | default |
> ++--+--+--+---+-+-+++-+-+
> |  6 | tmp  | 99d2bf78-aa15-4014-a056-0d2d81c4db0e |0 | 1 
> | enabled | 2013-05-06 10:51:53 |  0 | NULL   |   
>  NULL |   0 |
> ++--+

[jira] [Resolved] (CLOUDSTACK-2192) [EIP/Optonal PublicIP] listNetworkOfferings is not returning info about the capability "AssociatePublicIP"

2013-05-31 Thread Murali Reddy (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Murali Reddy resolved CLOUDSTACK-2192.
--

Resolution: Fixed

> [EIP/Optonal PublicIP] listNetworkOfferings is not returning info about the 
> capability "AssociatePublicIP"
> --
>
> Key: CLOUDSTACK-2192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2192
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit # 0e2ffe72aa641f4551cae63fbc36454c5934342f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have latest setup from master with EIP offering that has the capability 
> "AssociatePublicIP" set to "False"
>id: 15
>  name: EIPOffering
>  uuid: 6207d909-c780-4661-8a61-7e397aad7b77
>   unique_name: EIPOffering
>  display_text: EIPOffering
>   nw_rate: NULL
>   mc_rate: 10
>  traffic_type: Guest
>  tags: NULL
>   system_only: 0
>  specify_vlan: 1
>   service_offering_id: NULL
> conserve_mode: 0
>   created: 2013-04-24 17:23:07
>   removed: NULL
>   default: 0
>  availability: Optional
>  dedicated_lb_service: 0
> shared_source_nat_service: 0
>  sort_key: 0
>  redundant_router_service: 0
> state: Enabled
>guest_type: Shared
>elastic_ip_service: 1
>   eip_associate_public_ip: 0
>elastic_lb_service: 1
> specify_ip_ranges: 1
>inline: 0
> is_persistent: 0
> select * from networks;
>id: 15
>  name: EIPOffering
>  uuid: 6207d909-c780-4661-8a61-7e397aad7b77
>   unique_name: EIPOffering
>  display_text: EIPOffering
>   nw_rate: NULL
>   mc_rate: 10
>  traffic_type: Guest
>  tags: NULL
>   system_only: 0
>  specify_vlan: 1
>   service_offering_id: NULL
> conserve_mode: 0
>   created: 2013-04-24 17:23:07
>   removed: NULL
>   default: 0
>  availability: Optional
>  dedicated_lb_service: 0
> shared_source_nat_service: 0
>  sort_key: 0
>  redundant_router_service: 0
> state: Enabled
>guest_type: Shared
>elastic_ip_service: 1
>   eip_associate_public_ip: 0
>elastic_lb_service: 1
> specify_ip_ranges: 1
>inline: 0
> is_persistent: 0
> mysql> select * from ntwk_service_map;
> +++---+---+-+
> | id | network_id | service   | provider  | created   
>   |
> +++---+---+-+
> |  1 |204 | SecurityGroup | SecurityGroupProvider | 2013-04-24 
> 17:30:05 |
> |  2 |204 | Dns   | VirtualRouter | 2013-04-24 
> 17:30:05 |
> |  3 |204 | StaticNat | Netscaler | 2013-04-24 
> 17:30:05 |
> |  4 |204 | Dhcp  | VirtualRouter | 2013-04-24 
> 17:30:05 |
> |  5 |204 | UserData  | VirtualRouter | 2013-04-24 
> 17:30:05 |
> |  6 |204 | Lb| Netscaler | 2013-04-24 
> 17:30:05 |
> +++---+---+-+
> 2. Try to fire "listNetworkOfferings" API and verify the output
> Observations:
> (i) Here is the snippet of output
> http://10.147.59.194:8096/api?command=listNetworkOfferings&id=6207d909-c780-4661-8a61-7e397aad7b77&account=admin&response=json
> { "listnetworkofferingsresponse" : { "count":1 ,"networkoffering" : [  
> {"id":"6207d909-c780-4661-8a61-7e397aad7b77","name":"EIPOffering","displaytext":"EIPOffering","traffictype":"Guest","isdefault":false,"specifyvlan":true,"conservemode":false,"specifyipranges":true,"availability":"Optional","networkrate":200,"state":"Enabled","guestiptype":"Shared","serviceofferingid":"56ae83b7-2674-482b-a302-603fb326a370","service":[{"name":"StaticNat","provider":[{"name":"Netscaler"}],"capability":[{"name":"ElasticIp","value":"true","canchooseservicecapability":false}]},{"name":"UserData","provider":[{"name":"VirtualRouter"}]},{"

[jira] [Resolved] (CLOUDSTACK-2285) [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed in basic zone

2013-05-31 Thread Murali Reddy (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Murali Reddy resolved CLOUDSTACK-2285.
--

Resolution: Won't Fix


This problem is not specific to GSLB. But in general its good to have NetScaler 
not added when basic zone does not have EIP/ELB service.

But problem, is adding a network service provider instance (in this case 
NetScaler) into a physical network is independent action. When an instance of 
NetScaler is ready to be added, only zone and physical network needed to be in 
the deployment. Zone has no (should no have) info that its EIP/ELB zone. Unless 
a basic zoe network is created, its no ppossible to check if zone has EIP and 
ELB services enabled. 

While this problem can be fixed if we have flag at zone level (with createZone) 
but its not much value.

Event if admin adds netscaler, its not used because there are no networks that 
need it. So its harmless.

Closing this as wont't fix.

> [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed 
> in basic zone
> --
>
> Key: CLOUDSTACK-2285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller
>Affects Versions: 4.2.0
> Environment: commit 0e2ffe72aa641f4551cae63fbc36454c5934342f
>Reporter: venkata swamybabu budumuru
>Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: api.log.tgz
>
>
> Steps to reproduce :
> 1. Have a basic zone setup with at least one XEN cluster using the offering 
> "DefaultSharedNetworkOfferingWithSGService"
> 2. Try "addNetscalerLoadBalancer" with GSLB enabled
> Observations:
> (i) It gets added successfully.
> command=addNetscalerLoadBalancer&physicalnetworkid=4dbe1d3c-1cee-4f88-aeca-45c4a8a76b4d&username=nsroot&password=nsroot&networkdevicetype=NetscalerVPXLoadBalancer&gslbprovider=true&gslbproviderpublicip=1.1.1.1&gslbproviderprivateip=1.1.1.1&url=https://10.147.54.5?publicinterface=1/1&privateinterface=1/2&numretries=2&lbdevicededicated=false&;
> mysql> select id,name,networktype from data_center where id=1;
> ++---+-+
> | id | name  | networktype |
> ++---+-+
> |  1 | zone1 | Basic   |
> ++---+-+
> mysql> select * from external_load_balancer_devices where id=2\G
> *** 1. row ***
>  id: 2
>uuid: 8c467bfc-7ac3-410a-92d7-11e5853a5d79
> physical_network_id: 200
>   provider_name: Netscaler
> device_name: NetscalerVPXLoadBalancer
>capacity: 50
>device_state: Enabled
>allocation_state: Free
>is_dedicated: 0
>  is_managed: 0
> host_id: 15
>  parent_host_id: 0
>is_gslb_provider: 1
>  gslb_site_publicip: NULL
> gslb_site_privateip: 1.1.1.1
> (ii) There is no need for enabling GSLB functionality in basic zones created 
> with above network offerings because there is no LB feature enabled in this 
> case.
> May be having a check at the API level and allowing it only based on type of 
> zone will help in this case but, if we are supporting GSLB for ELB enabled 
> zones then we need to handle that situation as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2785) Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, infrastructure.css


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isaac Chiang updated CLOUDSTACK-2785:
-

Priority: Minor  (was: Major)

> Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, 
> infrastructure.css
> -
>
> Key: CLOUDSTACK-2785
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2785
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
> Environment: Master
>Reporter: Isaac Chiang
>Priority: Minor
>  Labels: ui
> Attachments: Screen Shot 2013-05-31 at 5.29.05 PM.png
>
>
> The following css files are failed to include : vnmcAsa1000v.css, 
> vnmcNetworkProvider.css, infrastructure.css

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2785) Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, infrastructure.css

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671479#comment-13671479
 ] 

Isaac Chiang commented on CLOUDSTACK-2785:
--

Get it:) I'll change the ticket status to minor.

Thanks

Isaac

> Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, 
> infrastructure.css
> -
>
> Key: CLOUDSTACK-2785
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2785
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
> Environment: Master
>Reporter: Isaac Chiang
>Priority: Minor
>  Labels: ui
> Attachments: Screen Shot 2013-05-31 at 5.29.05 PM.png
>
>
> The following css files are failed to include : vnmcAsa1000v.css, 
> vnmcNetworkProvider.css, infrastructure.css

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2788) restartVpc should have id as a required attribute


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671485#comment-13671485
 ] 

ASF subversion and git services commented on CLOUDSTACK-2788:
-

Commit 49b5e61869fb5ca0dbea729a1ba9ab38d6a5e646 in branch refs/heads/master 
from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=49b5e61 ]

CLOUDSTACK-2788: restartVpc should have id as required

Signed-off-by: Prasanna Santhanam 


> restartVpc should have id as a required attribute
> -
>
> Key: CLOUDSTACK-2788
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2788
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in restartVpcCmd.java but without the id one 
> cannot update the vpc offering.
> @APICommand(name = "restartVPC", description="Restarts a VPC", 
> responseObject=VpcResponse.class)
> public class RestartVPCCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(RestartVPCCmd.class.getName());
> private static final String _name = "restartvpcresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
> entityType=VpcResponse.class,
> description="the id of the VPC")
> private Long id;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2789) updateVpc should have id and name as required attributes

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671484#comment-13671484
 ] 

ASF subversion and git services commented on CLOUDSTACK-2789:
-

Commit 16a76e92abce6864be0ebd6a82cbe7c46f456824 in branch refs/heads/master 
from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=16a76e9 ]

CLOUDSTACK-2789: updateVPC takes in id and name as required

Signed-off-by: Prasanna Santhanam 


> updateVpc should have id and name as required attributes
> 
>
> Key: CLOUDSTACK-2789
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2789
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in updateVpcCMd.java but without the id and a 
> name one cannot update the vpc.
> @APICommand(name = "updateVPC", description="Updates a VPC", 
> responseObject=VpcResponse.class)
> public class UpdateVPCCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(UpdateVPCCmd.class.getName());
> private static final String _name = "updatevpcresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
> entityType=VpcResponse.class,
> description="the id of the VPC")
> private Long id;
> @Parameter(name=ApiConstants.NAME, type=CommandType.STRING, 
> description="the name of the VPC")
> private String vpcName;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2788) restartVpc should have id as a required attribute


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam resolved CLOUDSTACK-2788.


Resolution: Fixed

> restartVpc should have id as a required attribute
> -
>
> Key: CLOUDSTACK-2788
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2788
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in restartVpcCmd.java but without the id one 
> cannot update the vpc offering.
> @APICommand(name = "restartVPC", description="Restarts a VPC", 
> responseObject=VpcResponse.class)
> public class RestartVPCCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(RestartVPCCmd.class.getName());
> private static final String _name = "restartvpcresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
> entityType=VpcResponse.class,
> description="the id of the VPC")
> private Long id;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2789) updateVpc should have id and name as required attributes


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam resolved CLOUDSTACK-2789.


Resolution: Fixed

> updateVpc should have id and name as required attributes
> 
>
> Key: CLOUDSTACK-2789
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2789
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
> Fix For: 4.2.0
>
>
> id is not a required attribute in updateVpcCMd.java but without the id and a 
> name one cannot update the vpc.
> @APICommand(name = "updateVPC", description="Updates a VPC", 
> responseObject=VpcResponse.class)
> public class UpdateVPCCmd extends BaseAsyncCmd{
> public static final Logger s_logger = 
> Logger.getLogger(UpdateVPCCmd.class.getName());
> private static final String _name = "updatevpcresponse";
> /
>  API parameters /
> /
> @Parameter(name=ApiConstants.ID, type=CommandType.UUID, 
> entityType=VpcResponse.class,
> description="the id of the VPC")
> private Long id;
> @Parameter(name=ApiConstants.NAME, type=CommandType.STRING, 
> description="the name of the VPC")
> private String vpcName;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2790) AWSAPI: packaging includes all .class files bloating size of the RPM

Prasanna Santhanam created CLOUDSTACK-2790:
--

 Summary: AWSAPI: packaging includes all .class files bloating size 
of the RPM
 Key: CLOUDSTACK-2790
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2790
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Packaging
Reporter: Prachi Damle
Assignee: Rayees Namathponnan
 Fix For: 4.2.0


awsapi webapp is not getting deployed on axis2 when management server is 
started. 

Following  file is missing and causing this issue: 
webapps7080/awsapi/WEB-INF/services/cloud-ec2.aar

I don’t see this file on a setup using rpm packages under:  
/usr/share/cloudstack-bridge/webapps/awsapi/WEB-INF/services. So looks like the 
.aar file is not being generated by the apache build.


Apache build should  create this jar file [cloud-ec2.aar] too and package it 
under webapps7080/awsapi/WEB-INF/services


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2790) AWSAPI: packaging includes all .class files bloating size of the RPM


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam updated CLOUDSTACK-2790:
---

Description: The AWSAPI package cloudstack-awsapi seems to be including all 
the .class files as part of the RPM instead of putting them into a jar/aar 
archive. This bloats the size of the package to ~60M. It can be much smaller if 
archived  (was: awsapi webapp is not getting deployed on axis2 when management 
server is started. 

Following  file is missing and causing this issue: 
webapps7080/awsapi/WEB-INF/services/cloud-ec2.aar

I don’t see this file on a setup using rpm packages under:  
/usr/share/cloudstack-bridge/webapps/awsapi/WEB-INF/services. So looks like the 
.aar file is not being generated by the apache build.


Apache build should  create this jar file [cloud-ec2.aar] too and package it 
under webapps7080/awsapi/WEB-INF/services
)

> AWSAPI: packaging includes all .class files bloating size of the RPM
> 
>
> Key: CLOUDSTACK-2790
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2790
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Reporter: Prachi Damle
>Assignee: Rayees Namathponnan
> Fix For: 4.2.0
>
>
> The AWSAPI package cloudstack-awsapi seems to be including all the .class 
> files as part of the RPM instead of putting them into a jar/aar archive. This 
> bloats the size of the package to ~60M. It can be much smaller if archived

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2739) Improve website landing page by adding Link for reporting bugs

2013-05-31 Thread Chip Childers (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chip Childers resolved CLOUDSTACK-2739.
---

Resolution: Fixed
  Assignee: Chip Childers

pushed out the change

> Improve website landing page by adding Link for reporting bugs
> --
>
> Key: CLOUDSTACK-2739
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2739
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Website
>Reporter: Shanker Balan
>Assignee: Chip Childers
>Priority: Trivial
>
> It would be nice if we can add a link on the main landing page navigation bar 
> pointing to the bug reporting page.
> http://httpd.apache.org for example has a "reporting bug" link under "getting 
> involved" sidebar.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CLOUDSTACK-2739) Improve website landing page by adding Link for reporting bugs

2013-05-31 Thread Chip Childers (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chip Childers closed CLOUDSTACK-2739.
-


> Improve website landing page by adding Link for reporting bugs
> --
>
> Key: CLOUDSTACK-2739
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2739
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Website
>Reporter: Shanker Balan
>Assignee: Chip Childers
>Priority: Trivial
>
> It would be nice if we can add a link on the main landing page navigation bar 
> pointing to the bug reporting page.
> http://httpd.apache.org for example has a "reporting bug" link under "getting 
> involved" sidebar.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2695) [Object_Store_Refactor] Provisioning object storage(S3 based secondary storage) can't be at zone level

2013-05-31 Thread Min Chen (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen reassigned CLOUDSTACK-2695:


Assignee: (was: Min Chen)

> [Object_Store_Refactor] Provisioning object storage(S3 based secondary 
> storage) can't be at zone level
> --
>
> Key: CLOUDSTACK-2695
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2695
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
> Environment: Build from object_store branch
>Reporter: Sanjeev N
>Priority: Critical
> Fix For: 4.2.0
>
>
> Provisioning object storage can't be at zone level.
> 1.With current CS implementation , Regions is self created.
> 2.Provisioning object storage is at zone level but it should be at region 
> level.
> 3.If the user creates multiple zones then user has to provide s3 object store 
> details in each zone . Since s3 is a region level storage, adding s3 should 
> also be at region level rather than at zone level.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2695) [Object_Store_Refactor]UI: Provisioning object storage(S3 based secondary storage) can't be at zone level

2013-05-31 Thread Min Chen (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen updated CLOUDSTACK-2695:
-

Summary: [Object_Store_Refactor]UI:  Provisioning object storage(S3 based 
secondary storage) can't be at zone level  (was: [Object_Store_Refactor] 
Provisioning object storage(S3 based secondary storage) can't be at zone level)

> [Object_Store_Refactor]UI:  Provisioning object storage(S3 based secondary 
> storage) can't be at zone level
> --
>
> Key: CLOUDSTACK-2695
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2695
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
> Environment: Build from object_store branch
>Reporter: Sanjeev N
>Priority: Critical
> Fix For: 4.2.0
>
>
> Provisioning object storage can't be at zone level.
> 1.With current CS implementation , Regions is self created.
> 2.Provisioning object storage is at zone level but it should be at region 
> level.
> 3.If the user creates multiple zones then user has to provide s3 object store 
> details in each zone . Since s3 is a region level storage, adding s3 should 
> also be at region level rather than at zone level.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2791) Installation instruction wrong

2013-05-31 Thread Ron Wheeler (JIRA)

Ron Wheeler created CLOUDSTACK-2791:
---

 Summary: Installation instruction wrong
 Key: CLOUDSTACK-2791
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2791
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Affects Versions: 4.0.1
 Environment: All
Reporter: Ron Wheeler


http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Installation_Guide/configure-package-repository.html

Instruction
 Next you'll want to add the GPG key:

$ rpm --import http://server.url/downloads/RPM-GPG-KEY.txt

is not correct

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2758) cloudstack-management does not start from RPM packages

2013-05-31 Thread wqmeng (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671681#comment-13671681
 ] 

wqmeng commented on CLOUDSTACK-2758:


Copied from the Mail list. 

---
Okay,

I have tried this

chmod 777 /usr/share/cloud/management/logs/catalina.out

Seems it helps to get the tomcat to run.

but the command not need before, I think at lease last week, I have
never run this command to change the permission and have succeeded to
set-up the management without any problem.

Or I have miss something?


Thank you.


> cloudstack-management does not start from RPM packages
> --
>
> Key: CLOUDSTACK-2758
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2758
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Priority: Blocker
> Fix For: 4.2.0
>
>
> For the last two days the packages for CloudStack from jenkins.cs.o haven't 
> been able to boot up the management server. The service start reports OK, but 
> the service dies immediately.
> [root@cloudstack-centos63 ~]# bash -x /etc/init.d/cloudstack-management start
> + '[' -r /etc/rc.d/init.d/functions ']'
> + . /etc/rc.d/init.d/functions
> ++ TEXTDOMAIN=initscripts
> ++ umask 022
> ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin
> ++ export PATH
> ++ '[' -z '' ']'
> ++ COLUMNS=80
> ++ '[' -z '' ']'
> +++ /sbin/consoletype
> ++ CONSOLETYPE=pty
> ++ '[' -f /etc/sysconfig/i18n -a -z '' -a -z '' ']'
> ++ . /etc/profile.d/lang.sh
> ++ unset LANGSH_SOURCED
> ++ '[' -z '' ']'
> ++ '[' -f /etc/sysconfig/init ']'
> ++ . /etc/sysconfig/init
> +++ BOOTUP=color
> +++ RES_COL=60
> +++ MOVE_TO_COL='echo -en \033[60G'
> +++ SETCOLOR_SUCCESS='echo -en \033[0;32m'
> +++ SETCOLOR_FAILURE='echo -en \033[0;31m'
> +++ SETCOLOR_WARNING='echo -en \033[0;33m'
> +++ SETCOLOR_NORMAL='echo -en \033[0;39m'
> +++ PROMPT=yes
> +++ AUTOSWAP=no
> +++ ACTIVE_CONSOLES='/dev/tty[1-6]'
> +++ SINGLE=/sbin/sushell
> ++ '[' pty = serial ']'
> ++ 
> __sed_discard_ignored_files='/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d'
> + '[' -r /lib/lsb/init-functions ']'
> + . /lib/lsb/init-functions
> ++ basename /etc/init.d/cloudstack-management
> + NAME=cloudstack-management
> + case "$1" in
> + set_ulimit
> ++ ulimit -n
> + fd_limit=1024
> + '[' 1024 '!=' 4096 ']'
> ++ whoami
> + user=root
> + '[' root == root ']'
> + ulimit -n 4096
> + . /etc/rc.d/init.d/tomcat6
> ++ '[' -r /lib/lsb/init-functions ']'
> ++ . /lib/lsb/init-functions
> +++ lsb_release -i -s
> ++ DISTRIB_ID=CentOS
> +++ basename /etc/init.d/cloudstack-management
> ++ NAME=cloudstack-management
> ++ unset ISBOOT
> ++ '[' c = S -o c = K ']'
> ++ '[' -x /sbin/runuser ']'
> ++ SU='/sbin/runuser -s /bin/sh'
> ++ TOMCAT_CFG=/etc/tomcat6/tomcat6.conf
> ++ '[' -r /etc/tomcat6/tomcat6.conf ']'
> ++ . /etc/tomcat6/tomcat6.conf
> +++ CATALINA_BASE=/usr/share/tomcat6
> +++ CATALINA_HOME=/usr/share/tomcat6
> +++ JASPER_HOME=/usr/share/tomcat6
> +++ CATALINA_TMPDIR=/var/cache/tomcat6/temp
> +++ JAVA_OPTS=' 
> -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory'
> +++ TOMCAT_USER=tomcat
> +++ SECURITY_MANAGER=false
> +++ SHUTDOWN_WAIT=30
> +++ SHUTDOWN_VERBOSE=false
> +++ CATALINA_PID=/var/run/tomcat6.pid
> ++ '[' -r /etc/sysconfig/cloudstack-management ']'
> ++ . /etc/sysconfig/cloudstack-management
> +++ dummy=1
> +++ export TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
> +++ TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
> +++ . /etc/cloudstack/management/tomcat6.conf
>  CATALINA_BASE=/usr/share/cloudstack-management
>  CATALINA_HOME=/usr/share/cloudstack-management
>  JASPER_HOME=/usr/share/cloudstack-management
>  CATALINA_TMPDIR=/usr/share/cloudstack-management/temp
>  JAVA_OPTS='-Djava.awt.headless=true 
> -Dcom.sun.management.jmxremote.port=45219 
> -Dcom.sun.management.jmxremote.authenticate=false 
> -Dcom.sun.management.jmxremote.ssl=false -Xmx2g 
> -XX:+HeapDumpOnOutOfMemoryError 
> -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M 
> -XX:MaxPermSize=800m'
>  TOMCAT_USER=cloud
>  TOMCAT6_USER=cloud
>  TOMCAT_LOG=/var/log/cloudstack/management//catalina.out
>  SECURITY_MANAGER=false
>  SHUTDOWN_WAIT=30
>  SHUTDOWN_VERBOSE=false
>  CATALINA_PID=/var/run/cloudstack-management.pid
>  dummy=1
>  . /etc/cloudstack/management/classpath.conf
> + SYSTEMJARS=
> ++ build-classpath
> + SCP=
> + '[' 2 '!=' 0 ']'
> + export SCP=
> + SCP=
> + MCP=
> + DCP=
> + 
> CLASSPATH=:::/etc/cloudstack/management:/usr/share/cloudstack-management/setup
> + for jarfile in '

[jira] [Commented] (CLOUDSTACK-2758) cloudstack-management does not start from RPM packages

2013-05-31 Thread wqmeng (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671684#comment-13671684
 ] 

wqmeng commented on CLOUDSTACK-2758:


To add,  
It is also has the problem with the latest released package CloudStack4.02  
My   CentOS6.4 X64,  CS4.02. 

The change should be happen after last weekend.  Maybe since 27 May or some 
other time near that.  
Not sure what's changed, maybe a update of the Tomcat from yum.

Thanks

> cloudstack-management does not start from RPM packages
> --
>
> Key: CLOUDSTACK-2758
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2758
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Priority: Blocker
> Fix For: 4.2.0
>
>
> For the last two days the packages for CloudStack from jenkins.cs.o haven't 
> been able to boot up the management server. The service start reports OK, but 
> the service dies immediately.
> [root@cloudstack-centos63 ~]# bash -x /etc/init.d/cloudstack-management start
> + '[' -r /etc/rc.d/init.d/functions ']'
> + . /etc/rc.d/init.d/functions
> ++ TEXTDOMAIN=initscripts
> ++ umask 022
> ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin
> ++ export PATH
> ++ '[' -z '' ']'
> ++ COLUMNS=80
> ++ '[' -z '' ']'
> +++ /sbin/consoletype
> ++ CONSOLETYPE=pty
> ++ '[' -f /etc/sysconfig/i18n -a -z '' -a -z '' ']'
> ++ . /etc/profile.d/lang.sh
> ++ unset LANGSH_SOURCED
> ++ '[' -z '' ']'
> ++ '[' -f /etc/sysconfig/init ']'
> ++ . /etc/sysconfig/init
> +++ BOOTUP=color
> +++ RES_COL=60
> +++ MOVE_TO_COL='echo -en \033[60G'
> +++ SETCOLOR_SUCCESS='echo -en \033[0;32m'
> +++ SETCOLOR_FAILURE='echo -en \033[0;31m'
> +++ SETCOLOR_WARNING='echo -en \033[0;33m'
> +++ SETCOLOR_NORMAL='echo -en \033[0;39m'
> +++ PROMPT=yes
> +++ AUTOSWAP=no
> +++ ACTIVE_CONSOLES='/dev/tty[1-6]'
> +++ SINGLE=/sbin/sushell
> ++ '[' pty = serial ']'
> ++ 
> __sed_discard_ignored_files='/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d'
> + '[' -r /lib/lsb/init-functions ']'
> + . /lib/lsb/init-functions
> ++ basename /etc/init.d/cloudstack-management
> + NAME=cloudstack-management
> + case "$1" in
> + set_ulimit
> ++ ulimit -n
> + fd_limit=1024
> + '[' 1024 '!=' 4096 ']'
> ++ whoami
> + user=root
> + '[' root == root ']'
> + ulimit -n 4096
> + . /etc/rc.d/init.d/tomcat6
> ++ '[' -r /lib/lsb/init-functions ']'
> ++ . /lib/lsb/init-functions
> +++ lsb_release -i -s
> ++ DISTRIB_ID=CentOS
> +++ basename /etc/init.d/cloudstack-management
> ++ NAME=cloudstack-management
> ++ unset ISBOOT
> ++ '[' c = S -o c = K ']'
> ++ '[' -x /sbin/runuser ']'
> ++ SU='/sbin/runuser -s /bin/sh'
> ++ TOMCAT_CFG=/etc/tomcat6/tomcat6.conf
> ++ '[' -r /etc/tomcat6/tomcat6.conf ']'
> ++ . /etc/tomcat6/tomcat6.conf
> +++ CATALINA_BASE=/usr/share/tomcat6
> +++ CATALINA_HOME=/usr/share/tomcat6
> +++ JASPER_HOME=/usr/share/tomcat6
> +++ CATALINA_TMPDIR=/var/cache/tomcat6/temp
> +++ JAVA_OPTS=' 
> -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory'
> +++ TOMCAT_USER=tomcat
> +++ SECURITY_MANAGER=false
> +++ SHUTDOWN_WAIT=30
> +++ SHUTDOWN_VERBOSE=false
> +++ CATALINA_PID=/var/run/tomcat6.pid
> ++ '[' -r /etc/sysconfig/cloudstack-management ']'
> ++ . /etc/sysconfig/cloudstack-management
> +++ dummy=1
> +++ export TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
> +++ TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
> +++ . /etc/cloudstack/management/tomcat6.conf
>  CATALINA_BASE=/usr/share/cloudstack-management
>  CATALINA_HOME=/usr/share/cloudstack-management
>  JASPER_HOME=/usr/share/cloudstack-management
>  CATALINA_TMPDIR=/usr/share/cloudstack-management/temp
>  JAVA_OPTS='-Djava.awt.headless=true 
> -Dcom.sun.management.jmxremote.port=45219 
> -Dcom.sun.management.jmxremote.authenticate=false 
> -Dcom.sun.management.jmxremote.ssl=false -Xmx2g 
> -XX:+HeapDumpOnOutOfMemoryError 
> -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M 
> -XX:MaxPermSize=800m'
>  TOMCAT_USER=cloud
>  TOMCAT6_USER=cloud
>  TOMCAT_LOG=/var/log/cloudstack/management//catalina.out
>  SECURITY_MANAGER=false
>  SHUTDOWN_WAIT=30
>  SHUTDOWN_VERBOSE=false
>  CATALINA_PID=/var/run/cloudstack-management.pid
>  dummy=1
>  . /etc/cloudstack/management/classpath.conf
> + SYSTEMJARS=
> ++ build-classpath
> + SCP=
> + '[' 2 '!=' 0 ']'
> + export SCP=
> + SCP=
> + MCP=
> + DCP=
> + 
> CLASSPATH=:::/etc/cloudstack/management:/usr/share/cloudstack-management/setup
> + for jarfile in '"/usr/share/cloudstack-management/premium"/*'
> + '[' '!' -e '/usr/share/cloudstack-management/premiu

[jira] [Commented] (CLOUDSTACK-2758) cloudstack-management does not start from RPM packages

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671694#comment-13671694
 ] 

Prasanna Santhanam commented on CLOUDSTACK-2758:


[root@cloudstack-centos63 ~]# rpm -qa | grep tomcat
tomcat6-jsp-2.1-api-6.0.24-55.el6_4.noarch
tomcat6-servlet-2.5-api-6.0.24-55.el6_4.noarch
tomcat6-el-2.1-api-6.0.24-55.el6_4.noarch
tomcat6-6.0.24-55.el6_4.noarch
apache-tomcat-apis-0.1-1.el6.noarch
tomcat6-lib-6.0.24-55.el6_4.noarch


^^ That's the tomcat versions I'm seeing. Just tried a fresh 4.1 install and 
it's got the same issue. 

> cloudstack-management does not start from RPM packages
> --
>
> Key: CLOUDSTACK-2758
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2758
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.2.0
>Reporter: Prasanna Santhanam
>Priority: Blocker
> Fix For: 4.2.0
>
>
> For the last two days the packages for CloudStack from jenkins.cs.o haven't 
> been able to boot up the management server. The service start reports OK, but 
> the service dies immediately.
> [root@cloudstack-centos63 ~]# bash -x /etc/init.d/cloudstack-management start
> + '[' -r /etc/rc.d/init.d/functions ']'
> + . /etc/rc.d/init.d/functions
> ++ TEXTDOMAIN=initscripts
> ++ umask 022
> ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin
> ++ export PATH
> ++ '[' -z '' ']'
> ++ COLUMNS=80
> ++ '[' -z '' ']'
> +++ /sbin/consoletype
> ++ CONSOLETYPE=pty
> ++ '[' -f /etc/sysconfig/i18n -a -z '' -a -z '' ']'
> ++ . /etc/profile.d/lang.sh
> ++ unset LANGSH_SOURCED
> ++ '[' -z '' ']'
> ++ '[' -f /etc/sysconfig/init ']'
> ++ . /etc/sysconfig/init
> +++ BOOTUP=color
> +++ RES_COL=60
> +++ MOVE_TO_COL='echo -en \033[60G'
> +++ SETCOLOR_SUCCESS='echo -en \033[0;32m'
> +++ SETCOLOR_FAILURE='echo -en \033[0;31m'
> +++ SETCOLOR_WARNING='echo -en \033[0;33m'
> +++ SETCOLOR_NORMAL='echo -en \033[0;39m'
> +++ PROMPT=yes
> +++ AUTOSWAP=no
> +++ ACTIVE_CONSOLES='/dev/tty[1-6]'
> +++ SINGLE=/sbin/sushell
> ++ '[' pty = serial ']'
> ++ 
> __sed_discard_ignored_files='/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d'
> + '[' -r /lib/lsb/init-functions ']'
> + . /lib/lsb/init-functions
> ++ basename /etc/init.d/cloudstack-management
> + NAME=cloudstack-management
> + case "$1" in
> + set_ulimit
> ++ ulimit -n
> + fd_limit=1024
> + '[' 1024 '!=' 4096 ']'
> ++ whoami
> + user=root
> + '[' root == root ']'
> + ulimit -n 4096
> + . /etc/rc.d/init.d/tomcat6
> ++ '[' -r /lib/lsb/init-functions ']'
> ++ . /lib/lsb/init-functions
> +++ lsb_release -i -s
> ++ DISTRIB_ID=CentOS
> +++ basename /etc/init.d/cloudstack-management
> ++ NAME=cloudstack-management
> ++ unset ISBOOT
> ++ '[' c = S -o c = K ']'
> ++ '[' -x /sbin/runuser ']'
> ++ SU='/sbin/runuser -s /bin/sh'
> ++ TOMCAT_CFG=/etc/tomcat6/tomcat6.conf
> ++ '[' -r /etc/tomcat6/tomcat6.conf ']'
> ++ . /etc/tomcat6/tomcat6.conf
> +++ CATALINA_BASE=/usr/share/tomcat6
> +++ CATALINA_HOME=/usr/share/tomcat6
> +++ JASPER_HOME=/usr/share/tomcat6
> +++ CATALINA_TMPDIR=/var/cache/tomcat6/temp
> +++ JAVA_OPTS=' 
> -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory'
> +++ TOMCAT_USER=tomcat
> +++ SECURITY_MANAGER=false
> +++ SHUTDOWN_WAIT=30
> +++ SHUTDOWN_VERBOSE=false
> +++ CATALINA_PID=/var/run/tomcat6.pid
> ++ '[' -r /etc/sysconfig/cloudstack-management ']'
> ++ . /etc/sysconfig/cloudstack-management
> +++ dummy=1
> +++ export TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
> +++ TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
> +++ . /etc/cloudstack/management/tomcat6.conf
>  CATALINA_BASE=/usr/share/cloudstack-management
>  CATALINA_HOME=/usr/share/cloudstack-management
>  JASPER_HOME=/usr/share/cloudstack-management
>  CATALINA_TMPDIR=/usr/share/cloudstack-management/temp
>  JAVA_OPTS='-Djava.awt.headless=true 
> -Dcom.sun.management.jmxremote.port=45219 
> -Dcom.sun.management.jmxremote.authenticate=false 
> -Dcom.sun.management.jmxremote.ssl=false -Xmx2g 
> -XX:+HeapDumpOnOutOfMemoryError 
> -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M 
> -XX:MaxPermSize=800m'
>  TOMCAT_USER=cloud
>  TOMCAT6_USER=cloud
>  TOMCAT_LOG=/var/log/cloudstack/management//catalina.out
>  SECURITY_MANAGER=false
>  SHUTDOWN_WAIT=30
>  SHUTDOWN_VERBOSE=false
>  CATALINA_PID=/var/run/cloudstack-management.pid
>  dummy=1
>  . /etc/cloudstack/management/classpath.conf
> + SYSTEMJARS=
> ++ build-classpath
> + SCP=
> + '[' 2 '!=' 0 ']'
> + export SCP=
> + SCP=
> + MCP=
> + DCP=
> + 
> CLASSPATH=:::/etc/cloudstack/management:/usr/share/cloudstack-management/setup
> ++

[jira] [Commented] (CLOUDSTACK-659) Enable storage xenmotion support in XenServer 6.1

[
https://issues.apache.org/jira/browse/CLOUDSTACK-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671726#comment-13671726
]

ASF subversion and git services commented on CLOUDSTACK-659:

Commit f24e81fe0da053692b00d962f3ab9bd1e35158f8 in branch refs/heads/master
from Sateesh Chodapuneedi
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f24e81f ]

CLOUDSTACK-659 Support for storage migration in Cloudstack deployment over
VMware Added VmwareStorageMotionStrategy to deal with storage motion tasks.
Added target host parameter to MigrateWithStorageCommand.

Signed-off-by: Sateesh Chodapuneedi

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware Added
Resource changes to perform VM live migration along with virtual disks across
the clusters in a zone.

Signed-off-by: Sateesh Chodapuneedi

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware

Added VmwareStorageMotionStrategy to application context.

Signed-off-by: Sateesh Chodapuneedi

Support for volume live migration across datastores

Unit tests for vmware storage motion. These test the
VmwareStorageMotionStrategy.

CLOUDSTACK-659

Fixing migrate volume.

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware Added
Resource changes to perform VM live migration along with virtual disks across
the clusters in a zone.

Signed-off-by: Sateesh Chodapuneedi

Support for volume live migration across datastores

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware Added
Resource changes to perform VM live migration along with virtual disks across
the clusters in a zone.

Signed-off-by: Sateesh Chodapuneedi

Support for volume live migration across datastores

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware Added
Resource changes to perform VM live migration along with virtual disks across
the clusters in a zone.

Signed-off-by: Sateesh Chodapuneedi

Support for volume live migration across datastores

Added vm type to prepareNetworkFromNicInfo in MigrateWithStorageCommand
implementation.

CLOUDSTACK-2701 - Enable storage migration for VMware resources

Fixing attach volume and delete volume cases for volumes that are moved off
original path in datastore when created.
If volume is not found in root directory or datastore, do search in sub folders.

CLOUDSTACK-2701 - Enable storage migration for VMware resources

Sending command MigrateWithStorageCommand to source host instead of target host
for the case of migration of VM within cluster.

CLOUDSTACK-2701 - Enable storage migration for VMware resources

Searching for virtual disk during device tear down.

Adding dependency of 'cloud-engine-storage' to vmware hypervisor plugin.

Add hypervisor capability storage_motion_supported for VMware 5.0 and 5.1

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware
Added VmwareStorageMotionStrategy to deal with storage motion tasks.
Added target host parameter to MigrateWithStorageCommand.

Signed-off-by: Sateesh Chodapuneedi

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware Added
Resource changes to perform VM live migration along with virtual disks across
the clusters in a zone.

Signed-off-by: Sateesh Chodapuneedi

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware

Added VmwareStorageMotionStrategy to application context.

Signed-off-by: Sateesh Chodapuneedi

Support for volume live migration across datastores

Unit tests for vmware storage motion. These test the
VmwareStorageMotionStrategy.

CLOUDSTACK-659

Fixing migrate volume.

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware Added
Resource changes to perform VM live migration along with virtual disks across
the clusters in a zone.

Signed-off-by: Sateesh Chodapuneedi

Support for volume live migration across datastores

Added vm type to prepareNetworkFromNicInfo in MigrateWithStorageCommand
implementation.

Adding dependency of 'cloud-engine-storage' to vmware hypervisor plugin.

Add hypervisor capability storage_motion_supported for VMware 5.0 and 5.1

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware
Added VmwareStorageMotionStrategy to deal with storage motion tasks.
Added target host parameter to MigrateWithStorageCommand.

Signed-off-by: Sateesh Chodapuneedi

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware Added
Resource changes to perform VM live migration along with virtual disks across
the clusters in a zone.

Signed-off-by: Sateesh Chodapuneedi

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware

Added VmwareStorageMotionStrategy to application context.

Signed-off-by: Sateesh Chodapuneedi

Sup

[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671725#comment-13671725
 ] 

ASF subversion and git services commented on CLOUDSTACK-2701:
-

Commit 51996094ff2cb7d275507779bc8ed108dd8057e4 in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5199609 ]

CLOUDSTACK-2701 - Enable storage migration for VMware resources

Whitespace cleanup

Signed-off-by: Sateesh Chodapuneedi 

CLOUDSTACK-2701 - Enable storage migration for VMware resources

Removing injections which are not required in Vmware Manager


> Enable storage migration for VMware resources
> -
>
> Key: CLOUDSTACK-2701
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.0
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Storage vMotion allows VMs to be moved from one host to another, along with 
> storage across datastores in datacenter. It provides the option to live 
> migrate a VM’s disks along with the VM itself. 
> It is now possible to migrate a VM from one datastore to another, or even to 
> migrate a VM’s disks from one datastore to another with VM running on same 
> host, all while the VM is running. 
> This issue is to track the support of storage vMotion for VMware resources in 
> cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done 
> to branch vmware-storage-motion. Just now created this ticket to deal with 
> specific areas in implementation that is well contained and limited to VMware 
> resource only. Commits related to VmwareStorageMotionStrategy class and it's 
> implementation along with commands MigrateWithStorageCommand and 
> MigrateVolumeCommand are done under CLOUDSTACK-659 ticket.
> Release Planning: 
> Functional Spec: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer
>  (section VMware resource)
> Feature branch: vmware-storage-motion

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2029) zone wide primary storage support for cloudstack over vmware deployments

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671743#comment-13671743
 ] 

ASF subversion and git services commented on CLOUDSTACK-2029:
-

Commit e7d468e221fc85cc21eb5c54d6e9dc3e45f187ee in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e7d468e ]

CLOUDSTACK-2029 zone wide primary storage support for cloudstack over vmware 
deployments

DB changes to support hypervisor specific zone wide storage pool.
Added method findZoneWideStoragePoolsByHypervisor to PrimaryStorageDaoImpl to 
find suitable zone wide storage pool of specific hypervisor type.
Added column 'hypervisor' to table storage_pool. This column can be NULL. 
Used/populated only for zone wide primary storage pools.

Signed-off-by: Sateesh Chodapuneedi 


> zone wide primary storage support for cloudstack over vmware deployments
> 
>
> Key: CLOUDSTACK-2029
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2029
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller, VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Support for primary storage that span across clusters in CloudStack zone.
> Similar to Amazon's EBS.
> This is to facilitate virtual disk availability across clusters.
> Functional Specification: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Zone-wide+primary+storage+target
>  
> A dedicated section is being added to the above FS with specifics around 
> VMware resource support.
> Code for this feature can be found in branch 
> refs/heads/zone-primarystorage-vmware 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2029) zone wide primary storage support for cloudstack over vmware deployments

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671742#comment-13671742
 ] 

ASF subversion and git services commented on CLOUDSTACK-2029:
-

Commit 7998413f48784863a392d8e7719ff4c440a84659 in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7998413 ]

CLOUDSTACK-2029 zone wide primary storage support for cloudstack over vmware 
deployments

Added hypervisor type to CreateStoragePoolCmd & Storage pool responses.
DatastoreLifeCycle would consider hypervisor type while attaching datastore to 
zone.
ZoneWideStoragePoolAllocator would filter zone wide primary storage pools by 
hypervisor type along with tags in disk profile.
hypervisor type is mandatory parameter if scope is specified as ZONE while 
creating primary storage pool.
As of now KVM, VMware are allowed to use ZoneWideStoragePoolAllocator.

Signed-off-by: Sateesh Chodapuneedi 


> zone wide primary storage support for cloudstack over vmware deployments
> 
>
> Key: CLOUDSTACK-2029
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2029
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller, VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Support for primary storage that span across clusters in CloudStack zone.
> Similar to Amazon's EBS.
> This is to facilitate virtual disk availability across clusters.
> Functional Specification: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Zone-wide+primary+storage+target
>  
> A dedicated section is being added to the above FS with specifics around 
> VMware resource support.
> Code for this feature can be found in branch 
> refs/heads/zone-primarystorage-vmware 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2029) zone wide primary storage support for cloudstack over vmware deployments

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671744#comment-13671744
 ] 

ASF subversion and git services commented on CLOUDSTACK-2029:
-

Commit 2705f01651adfaf600647e5c2ea76c357c08c02a in branch refs/heads/master 
from Sateesh Chodapuneedi 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2705f01 ]

CLOUDSTACK-2029 zone wide primary storage support for cloudstack over vmware 
deployments

Added new column 'hypervisor' to table storage_pool to associate a identify a 
pool at zone level by hypervisor type.

Signed-off-by: Sateesh Chodapuneedi 


> zone wide primary storage support for cloudstack over vmware deployments
> 
>
> Key: CLOUDSTACK-2029
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2029
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller, VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Support for primary storage that span across clusters in CloudStack zone.
> Similar to Amazon's EBS.
> This is to facilitate virtual disk availability across clusters.
> Functional Specification: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Zone-wide+primary+storage+target
>  
> A dedicated section is being added to the above FS with specifics around 
> VMware resource support.
> Code for this feature can be found in branch 
> refs/heads/zone-primarystorage-vmware 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2701) Enable storage migration for VMware resources


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671747#comment-13671747
 ] 

Sateesh Chodapuneedi commented on CLOUDSTACK-2701:
--

Merged feature branch vmware-storage-motion into Master.

> Enable storage migration for VMware resources
> -
>
> Key: CLOUDSTACK-2701
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.0
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Storage vMotion allows VMs to be moved from one host to another, along with 
> storage across datastores in datacenter. It provides the option to live 
> migrate a VM’s disks along with the VM itself. 
> It is now possible to migrate a VM from one datastore to another, or even to 
> migrate a VM’s disks from one datastore to another with VM running on same 
> host, all while the VM is running. 
> This issue is to track the support of storage vMotion for VMware resources in 
> cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done 
> to branch vmware-storage-motion. Just now created this ticket to deal with 
> specific areas in implementation that is well contained and limited to VMware 
> resource only. Commits related to VmwareStorageMotionStrategy class and it's 
> implementation along with commands MigrateWithStorageCommand and 
> MigrateVolumeCommand are done under CLOUDSTACK-659 ticket.
> Release Planning: 
> Functional Spec: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer
>  (section VMware resource)
> Feature branch: vmware-storage-motion

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2701) Enable storage migration for VMware resources


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sateesh Chodapuneedi resolved CLOUDSTACK-2701.
--

Resolution: Fixed

> Enable storage migration for VMware resources
> -
>
> Key: CLOUDSTACK-2701
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.0
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Storage vMotion allows VMs to be moved from one host to another, along with 
> storage across datastores in datacenter. It provides the option to live 
> migrate a VM’s disks along with the VM itself. 
> It is now possible to migrate a VM from one datastore to another, or even to 
> migrate a VM’s disks from one datastore to another with VM running on same 
> host, all while the VM is running. 
> This issue is to track the support of storage vMotion for VMware resources in 
> cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done 
> to branch vmware-storage-motion. Just now created this ticket to deal with 
> specific areas in implementation that is well contained and limited to VMware 
> resource only. Commits related to VmwareStorageMotionStrategy class and it's 
> implementation along with commands MigrateWithStorageCommand and 
> MigrateVolumeCommand are done under CLOUDSTACK-659 ticket.
> Release Planning: 
> Functional Spec: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer
>  (section VMware resource)
> Feature branch: vmware-storage-motion

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2029) zone wide primary storage support for cloudstack over vmware deployments


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671749#comment-13671749
 ] 

Sateesh Chodapuneedi commented on CLOUDSTACK-2029:
--

Merged feature branch "zone-primarystorage-vmware" into Master. 

> zone wide primary storage support for cloudstack over vmware deployments
> 
>
> Key: CLOUDSTACK-2029
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2029
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller, VMware
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Support for primary storage that span across clusters in CloudStack zone.
> Similar to Amazon's EBS.
> This is to facilitate virtual disk availability across clusters.
> Functional Specification: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Zone-wide+primary+storage+target
>  
> A dedicated section is being added to the above FS with specifics around 
> VMware resource support.
> Code for this feature can be found in branch 
> refs/heads/zone-primarystorage-vmware 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CLOUDSTACK-2753) PVLAN - Ubuntu 13.04 KVM openvswitch - Add host Fail


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angeline shen closed CLOUDSTACK-2753.
-


verified  build  CloudStack-non-OSS-MASTER-425-rhel6.3.tar.gz

> PVLAN - Ubuntu 13.04 KVM  openvswitch - Add host Fail
> -
>
> Key: CLOUDSTACK-2753
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2753
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: MS ubuntu 13.04 KVM ACS 4.2 PVLAN build 417
> host ubuntu 13.04 KVM ACS 4.2 PVLANbuild 22
>Reporter: angeline shen
>Assignee: Sheng Yang
>Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: agent.log, management-server.log.gz
>
>
> 1. advance zone. Add host fail.
>On host,  kill libvirtd,libvirtd  -d -l   .Add host  still fail.
> 2.  Host:
> root@ubuntu8161:/var/log/cloudstack/agent# ip route
> default via 10.223.81.1 dev cloudbr0 
> 10.223.81.0/26 dev cloudbr0  proto kernel  scope link  src 10.223.81.61 
> 169.254.0.0/16 dev cloud0  proto kernel  scope link  src 169.254.0.1 
> 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.
> root@ubuntu8161:/var/log/cloudstack/agent# ps aux | grep libvirtd
> root 23938  0.1  0.2 325108  9976 ?Sl   16:42   0:00 libvirtd -d 
> -l
> root 24012  0.0  0.0   9436   960 pts/2S+   16:43   0:00 grep 
> --color=auto libvirtd
> root@ubuntu8161:/var/log/cloudstack/agent# kill -9 23938
> root@ubuntu8161:/var/log/cloudstack/agent# libvirtd -d -l
> root@ubuntu8161:/var/log/cloudstack/agent# ps aux | grep libvirtd
> root 24016  1.6  0.2 325108  9956 ?Sl   16:44   0:00 libvirtd -d 
> -l
> root 24076  0.0  0.0   9436   960 pts/2S+   16:44   0:00 grep 
> --color=auto libvirtd
> root@ubuntu8161:/var/log/cloudstack/agent# ps aux | grep libvirtd
> root 24016  0.5  0.2 325108  9956 ?Sl   16:44   0:00 libvirtd -d 
> -l
> root 24079  0.0  0.0   9436   960 pts/2S+   16:44   0:00 grep 
> --color=auto libvirtd
> 3.   agent.log:
> 2013-05-29 16:41:15,951 INFO  
> [resource.virtualnetwork.VirtualRoutingResource] (main:null) 
> VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
> 2013-05-29 16:41:16,137 ERROR [cloud.agent.AgentShell] (main:null) Unable to 
> start agent: 
> com.cloud.utils.exception.CloudRuntimeException: Failed to connect socket to 
> '/var/run/libvirt/libvirt-sock': No such file or directory
> at 
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:717)
> at com.cloud.agent.Agent.(Agent.java:163)
> at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:506)
> at 
> com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:461)
> at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:442)
> at com.cloud.agent.AgentShell.start(AgentShell.java:539)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CLOUDSTACK-2755) PVLAN - Ubuntu 13.04 KVM openvswitch - SSVM CPVM unable to go to running state.

2013-05-31 Thread Venkata Siva Vijayendra Bhamidipati (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angeline shen closed CLOUDSTACK-2755.
-


Verified CloudStack-non-OSS-MASTER-425-rhel6.3.tar.gz

> PVLAN - Ubuntu 13.04 KVM  openvswitch - SSVM  CPVM unable to go to running 
> state.
> -
>
> Key: CLOUDSTACK-2755
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2755
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: MS ubuntu 13.04 KVM ACS 4.2 PVLAN build 417
> host ubuntu 13.04 KVM ACS 4.2 PVLAN build 22 
>Reporter: angeline shen
>Assignee: Sheng Yang
>Priority: Blocker
> Fix For: 4.2.0
>
>
> 1. Create advance zone.  SSVM  CPVM unable to go to running state.
> MS log:
> 2013-05-28 19:12:06,023 DEBUG [agent.transport.Request] 
> (AgentManager-Handler-7:null) Seq 1-685047847: Processing:  { Ans: , MgmtId: 
> 6655051826959, via: 1, Ver: v1, Flags: 110, 
> [{"StartAnswer":{"vm":{"id":2,"name":"v-2-VM","type":"ConsoleProxy","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"Debian
>  GNU/Linux 5.0 (32-bit)","bootArgs":" template=domP type=consoleproxy 
> host=10.223.195.113 port=8250 name=v-2-VM premium=true zone=1 pod=1 
> guid=Proxy.2 proxy_vm=2 disable_rp_filter=true eth2ip=10.223.161.58 
> eth2mask=255.255.255.192 gateway=10.223.161.1 eth0ip=169.254.3.222 
> eth0mask=255.255.0.0 eth1ip=10.223.81.50 eth1mask=255.255.255.192 
> mgmtcidr=10.223.195.0/24 localgw=10.223.81.1 internaldns1=10.223.110.254 
> dns1=10.223.110.254","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"ef44f7b5cb5dd158","vncAddr":"10.223.81.61","params":{},"uuid":"011eec7d-8776-4149-b17f-6f0904191417","disks":[{"id":6,"name":"ROOT-2","mountPoint":"/export/home/angie/primary/kvm424","path":"bd28415c-5961-4bef-9efa-495b9d6c8a77","size":0,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"774b9428-0310-3e2d-b0b5-1540dd953251","deviceId":0}],"nics":[{"deviceId":2,"networkRateMbps":-1,"defaultNic":true,"uuid":"d9c2b426-358c-4005-962f-cdfab8079bb8","ip":"10.223.161.58","netmask":"255.255.255.192","gateway":"10.223.161.1","mac":"06:c7:fa:00:00:08","dns1":"10.223.110.254","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://1610","isolationUri":"vlan://1610","isSecurityGroupEnabled":false},{"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"dd237a46-1d56-4f81-830f-baef24c96018","ip":"169.254.3.222","netmask":"255.255.0.0","gateway":"169.254.0.1","mac":"0e:00:a9:fe:03:de","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"uuid":"8000e4c2-74e3-485b-8a34-01754e27c4c8","ip":"10.223.81.50","netmask":"255.255.255.192","gateway":"10.223.81.1","mac":"06:67:c8:00:00:01","broadcastType":"Native","type":"Management","isSecurityGroupEnabled":false}]},"result":false,"details":"java.io.IOException:
>  Cannot run program 
> \"/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl\": 
> java.io.IOException: error=13, Permission denied\n\tat 
> java.lang.ProcessBuilder.start(ProcessBuilder.java:488)\n\tat 
> com.cloud.utils.script.Script.execute(Script.java:183)\n\tat 
> com.cloud.utils.script.Script.execute(Script.java:161)\n\tat 
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.passCmdLine(LibvirtComputingResource.java:1063)\n\tat
>  
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3323)\n\tat
>  
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1187)\n\tat
>  com.cloud.agent.Agent.processRequest(Agent.java:525)\n\tat 
> com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\n\tat 
> com.cloud.utils.nio.Task.run(Task.java:83)\n\tat 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)\n\tat
>  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat
>  java.lang.Thread.run(Thread.java:679)\nCaused by: java.io.IOException: 
> java.io.IOException: error=13, Permission denied\n\tat 
> java.lang.UNIXProcess.(UNIXProcess.java:164)\n\tat 
> java.lang.ProcessImpl.start(ProcessImpl.java:81)\n\tat 
> java.lang.ProcessBuilder.start(ProcessBuilder.java:470)\n\t... 11 
> more\n","wait":0}},{"Answer":{"result":false,"details":"Stopped by previous 
> failure","wait":0}}] }
> 2013-05-28 19:12:06,023 DEBUG [agent.transport.Request] (consoleproxy-1:null) 
> Seq 1-685047847: Received:  { Ans: , MgmtId: 6655051826959, via: 1, Ver: v1, 
> Flags: 110, { Sta

[jira] [Assigned] (CLOUDSTACK-2730) vmware:addcluster failed in basiczone


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Venkata Siva Vijayendra Bhamidipati reassigned CLOUDSTACK-2730:
---

Assignee: (was: Venkata Siva Vijayendra Bhamidipati)

Unassigning so that someone can take a look at this from the GUI side.

> vmware:addcluster failed in basiczone
> -
>
> Key: CLOUDSTACK-2730
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2730
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.0
>Reporter: sadhu suresh
> Attachments: management-server.log
>
>
> In case of vmware ,when i try to configure basic zone with shared 
> network.addcluster failed with 
> "Creating cluster Something went wrong; please correct the following:Don't 
> support hypervisor type VMware in advanced security enabled zone" even though 
> i select the bassic and shared network.
> 1.select the  zone type as basic
> 2.select the network type as shared
> 3.provide pod ,guest details  and configure primary and secondary detaisl
> 4.click on "finish" to create basic zone with shared network mode
> Actual result:
> even though i select shared network in basic zone,it sends security group 
> enble to true internally. due to this  addcluster failed .
> It throws following error:
> Creating cluster Something went wrong; please correct the following:Don't 
> support hypervisor type VMware in advanced security enabled zone
> mysql> select * from data_center where id=2\G;
> *** 1. row ***
>id: 2
>  name: zone1
>  uuid: c642382d-8587-4cd7-a1e9-5a488bb47da7
>   description: NULL
>  dns1: 10.103.128.16
>  dns2: NULL
> internal_dns1: 10.103.128.16
> internal_dns2: NULL
>   gateway: NULL
>   netmask: NULL
>router_mac_address: 02:00:00:00:00:01
>   mac_address: 23
>guest_network_cidr: NULL
>domain: NULL
> domain_id: NULL
>   networktype: Basic
>  dns_provider: VirtualRouter
>  gateway_provider: NULL
> firewall_provider: NULL
> dhcp_provider: VirtualRouter
>   lb_provider: ElasticLoadBalancerVm
>  vpn_provider: NULL
> userdata_provider: VirtualRouter
>  allocation_state: Disabled
>zone_token: 68de3ddf-3a08-3371-9506-a57a4a0a8af5
> is_security_group_enabled: 1
>  is_local_storage_enabled: 0
>   removed: NULL
> owner: NULL
>   created: NULL
>   lastUpdated: NULL
>  engine_state: Disabled
>  ip6_dns1: NULL
>  ip6_dns2: NULL
> 1 row in set (0.00 sec)
> mysql> select * from networks where id=209\G;
> *** 1. row ***
>id: 209
>  name: defaultGuestNetwork
>  uuid: eca88272-2ad4-47a8-ab90-442393b6d034
>  display_text: defaultGuestNetwork
>  traffic_type: Guest
> broadcast_domain_type: Native
> broadcast_uri: vlan://untagged
>   gateway: NULL
>  cidr: NULL
>  mode: Dhcp
>   network_offering_id: 7
>   physical_network_id: 201
>data_center_id: 2
> guru_name: DirectPodBasedNetworkGuru
> state: Setup
>   related: 209
> domain_id: 1
>account_id: 1
>  dns1: NULL
>  dns2: NULL
> guru_data: NULL
>set_fields: 0
>  acl_type: Domain
>network_domain: cs1cloud.internal
>reservation_id: NULL
>guest_type: Shared
>  restart_required: 0
>   created: 2013-05-29 12:21:04
>   removed: NULL
> specify_ip_ranges: 1
>vpc_id: NULL
>   ip6_gateway: NULL
>  ip6_cidr: NULL
>  network_cidr: NULL
>   display_network: 1
>network_acl_id: NULL
> 1 row in set (0.00 sec)
> http://10.147.59.83:8080/client/api?command=createZone&networktype=Basic&name=zone1&dns1=10.103.128.16&internaldns1=10.103.128.16&response=json&sessionkey=6%2BUi17Y6gpixRBAR9s4yhQCQkhs%3D&_=1369810303912
> { "createzoneresponse" :  { "zone" : 
> {"id":"c642382d-8587-4cd7-a1e9-5a488bb47da7","name":"zone1","dns1":"10.103.128.16","internaldns1":"10.103.128.16","networktype":"Basic","securitygroupsenabled":true,"allocationstate":"Disabled","zonetoken":"68de3ddf-3a08-3371-9506-a57a4a0a8af5","

[jira] [Assigned] (CLOUDSTACK-2746) [VPC UI]: when tier with Internal LB is created, UI doesn't let you create the tier with public LB

2013-05-31 Thread Jessica Wang (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang reassigned CLOUDSTACK-2746:


Assignee: Jessica Wang

> [VPC UI]: when tier with Internal LB is created, UI doesn't let you create 
> the tier with public LB
> --
>
> Key: CLOUDSTACK-2746
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2746
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Alena Prokharchyk
>Assignee: Jessica Wang
> Fix For: 4.2.0
>
>
> Steps to reproduce:
> =
> 1) Create network offering with Internal LB support.
> 2) Create VPC
> 3) Add first network to the VPC using the network offering with Internal LB.
> Bug: when try to add the second network, the network offering with the public 
> LB support is not shown in the UI (the offering is present in the api 
> response of the call the UI makes)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2746) [VPC UI]: when tier with Internal LB is created, UI doesn't let you create the tier with public LB

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671871#comment-13671871
 ] 

ASF subversion and git services commented on CLOUDSTACK-2746:
-

Commit 8deeb90a6dcd90797d36f3c0ecd903a068140093 in branch refs/heads/master 
from Jessica Wang 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8deeb90 ]

CLOUDSTACK-2746: UI - InternalLB - VPC section - tiers - add tier dialog - 
network offering dropdown - exclude PublicLb network offerings only when 
PublicLb networks exists (i.e. LB network whose provider is VpcVirtualRouter or 
Netscaler exists).


> [VPC UI]: when tier with Internal LB is created, UI doesn't let you create 
> the tier with public LB
> --
>
> Key: CLOUDSTACK-2746
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2746
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Alena Prokharchyk
> Fix For: 4.2.0
>
>
> Steps to reproduce:
> =
> 1) Create network offering with Internal LB support.
> 2) Create VPC
> 3) Add first network to the VPC using the network offering with Internal LB.
> Bug: when try to add the second network, the network offering with the public 
> LB support is not shown in the UI (the offering is present in the api 
> response of the call the UI makes)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2746) [VPC UI]: when tier with Internal LB is created, UI doesn't let you create the tier with public LB

2013-05-31 Thread Jessica Wang (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang resolved CLOUDSTACK-2746.
--

Resolution: Fixed

> [VPC UI]: when tier with Internal LB is created, UI doesn't let you create 
> the tier with public LB
> --
>
> Key: CLOUDSTACK-2746
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2746
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: Alena Prokharchyk
>Assignee: Jessica Wang
> Fix For: 4.2.0
>
>
> Steps to reproduce:
> =
> 1) Create network offering with Internal LB support.
> 2) Create VPC
> 3) Add first network to the VPC using the network offering with Internal LB.
> Bug: when try to add the second network, the network offering with the public 
> LB support is not shown in the UI (the offering is present in the api 
> response of the call the UI makes)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2792) Redundant router: Password is reset again after fail-over happened

2013-05-31 Thread Sheng Yang (JIRA)

Sheng Yang created CLOUDSTACK-2792:
--

 Summary: Redundant router: Password is reset again after fail-over 
happened
 Key: CLOUDSTACK-2792
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2792
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.0.0
Reporter: Sheng Yang
Assignee: Sheng Yang
 Fix For: 4.2.0


Consider this scenario with RVR and "Password protected" VM:

1. Both Master and Backup is running.
2. We reset the password on VM
3. Both Master and Backup have password; for example say; "password1"
4. VM boots up and requests for password; receives it from Master VR
5. Master VR sets the password to Saved_Password and Backup VR continues to
keep "password1"
6. Backup VR goes down; it had password as "password1"
7. Maste VR is running
8. We reset the password; so the password is only changed to Master VR (as
Backup VR is down); for example "password2"
9. VM boots up and requests the password; gets it as "password2"
10. Master VR sets the password to be Saved_Password
11. Now Master VR goes down
12. Backup VR was brought online (it still has "password1")
13. Now we reboot the VM
14. It sends a password request
15. Backup VR (which is only available now; so is Master) sends the password as
"password1"

User tries to login as "password2" and he cannot; unless we reset the password
again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2793) PVLAN - Ubuntu 13.04 - Unable to start Stopped VM

angeline shen created CLOUDSTACK-2793:
-

 Summary: PVLAN - Ubuntu 13.04 - Unable to start Stopped VM
 Key: CLOUDSTACK-2793
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2793
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.2.0
 Environment: MS ubuntu 13.04 KVM ACS 4.2 PVLAN
host ubuntu 13.04 KVM ACS 4.2 PVLAN
Reporter: angeline shen
Assignee: angeline shen
Priority: Critical
 Fix For: 4.2.0


1. advance zone. Add 2 hosts.
  create PVLAN shared network with VLAN ID, private VLAN ID, IPV4 gateway, 
netmask, start IP, end IP

2. Deploy VMs in PVLAN shared network
3. stop VM
4. Start stopped VM failed 

2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-57:job-55) Successfully released network resources for the vm 
VM[User|z1admin1612-153V86]
2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-57:job-55) Successfully cleanued up resources for the vm 
VM[User|z1admin1612-153V86] in Starting state
2013-05-31 20:01:36,077 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-57:job-55) VM state transitted from :Starting to Stopped with 
event: OperationFailedvm's original host id: 4 new host id: null host id before 
s
tate transition: 4
2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-57:job-55) Hosts's actual total CPU: 9040 and CPU after applying 
overprovisioning: 9040
2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-57:job-55) Hosts's actual total RAM: 16816881664 and RAM after 
applying overprovisioning: 16816881664
2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-57:job-55) release cpu from host: 4, old used: 1200,reserved: 0, 
actual total: 9040, total with overprovisioning: 9040; new used: 1100,reserved
:0; movedfromreserved: false,moveToReserveredfalse
2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-57:job-55) release mem from host: 4, old used: 
2281701376,reserved: 0, total: 16816881664; new used: 1744830464,reserved:0; 
movedfromreserved: false,moveToReserveredfalse
2013-05-31 20:01:36,101 ERROR [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-57:job-55) Unexpected exception while executing 
org.apache.cloudstack.api.command.user.vm.StartVMCmd
com.cloud.exception.AgentUnavailableException: Resource [Host:4] is 
unreachable: Host 4: Unable to start instance due to Unable to get answer that 
is of class com.cloud.agent.api.StartAnswer
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:937)
at 
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
at 
org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243)
at 
org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3243)
at 
com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1786)
at 
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at 
org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at 
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get 
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at 
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:873)
... 19 more
2013-05-31 20:01:36,102 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-57:job-55) Complete async job-55, jobStatus: 2, resultCode: 530, 
result: Error Code: 530 Error text: Resource [Host:4] is unreachable: Host 4: 
Unable to start instance due to Unable to get answer that is of class 
com.cloud.agent.api.StartAnswer
2013-05-31 20:01:36,735 DEBUG [cloud.server.StatsCollector] 
(StatsColle

[jira] [Updated] (CLOUDSTACK-2638) PVLAN - Ubuntu 13.04 - Unable to start Stopped VM


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angeline shen updated CLOUDSTACK-2638:
--

Attachment: Screenshot-CloudStack - Mozilla Firefox-5.png
management-server.log.gz

> PVLAN - Ubuntu 13.04 - Unable to start Stopped VM
> -
>
> Key: CLOUDSTACK-2638
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2638
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: MS  ubuntu 13.04 KVM ACS 4.2 PVLAN
> host ubuntu 13.04 KVM ACS 4.2 PVLAN 
>Reporter: angeline shen
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, management-server.log.gz, 
> Screenshot-CloudStack - Mozilla Firefox-1.png, Screenshot-CloudStack - 
> Mozilla Firefox-2.png, Screenshot-CloudStack - Mozilla Firefox-5.png
>
>
> 1. advance zone. Add 2 hosts. 
>   create PVLAN shared network with VLAN ID, private VLAN ID, IPV4 gateway, 
> netmask, start IP, end IP 
> 2. Deploy VMs in PVLAN shared network
> 3. stop VM
> 4. Start stopped VM failed 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2793) PVLAN - Ubuntu 13.04 - Unable to start Stopped VM

2013-05-31 Thread ASF subversion and git services (JIRA)


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angeline shen updated CLOUDSTACK-2793:
--

Attachment: management-server.log.gz
Screenshot-CloudStack - Mozilla Firefox-5.png

> PVLAN - Ubuntu 13.04 - Unable to start Stopped VM
> -
>
> Key: CLOUDSTACK-2793
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2793
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: MS ubuntu 13.04 KVM ACS 4.2 PVLAN
> host ubuntu 13.04 KVM ACS 4.2 PVLAN
>Reporter: angeline shen
>Assignee: angeline shen
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, Screenshot-CloudStack - 
> Mozilla Firefox-5.png
>
>
> 1. advance zone. Add 2 hosts.
>   create PVLAN shared network with VLAN ID, private VLAN ID, IPV4 gateway, 
> netmask, start IP, end IP
> 2. Deploy VMs in PVLAN shared network
> 3. stop VM
> 4. Start stopped VM failed 
> 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (Job-Executor-57:job-55) Successfully released network resources for the vm 
> VM[User|z1admin1612-153V86]
> 2013-05-31 20:01:36,070 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (Job-Executor-57:job-55) Successfully cleanued up resources for the vm 
> VM[User|z1admin1612-153V86] in Starting state
> 2013-05-31 20:01:36,077 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-57:job-55) VM state transitted from :Starting to Stopped with 
> event: OperationFailedvm's original host id: 4 new host id: null host id 
> before s
> tate transition: 4
> 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-57:job-55) Hosts's actual total CPU: 9040 and CPU after 
> applying overprovisioning: 9040
> 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-57:job-55) Hosts's actual total RAM: 16816881664 and RAM after 
> applying overprovisioning: 16816881664
> 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-57:job-55) release cpu from host: 4, old used: 1200,reserved: 
> 0, actual total: 9040, total with overprovisioning: 9040; new used: 
> 1100,reserved
> :0; movedfromreserved: false,moveToReserveredfalse
> 2013-05-31 20:01:36,084 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-57:job-55) release mem from host: 4, old used: 
> 2281701376,reserved: 0, total: 16816881664; new used: 1744830464,reserved:0; 
> movedfromreserved: false,moveToReserveredfalse
> 2013-05-31 20:01:36,101 ERROR [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-57:job-55) Unexpected exception while executing 
> org.apache.cloudstack.api.command.user.vm.StartVMCmd
> com.cloud.exception.AgentUnavailableException: Resource [Host:4] is 
> unreachable: Host 4: Unable to start instance due to Unable to get answer 
> that is of class com.cloud.agent.api.StartAnswer
> at 
> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:937)
> at 
> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:550)
> at 
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:243)
> at 
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
> at 
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3243)
> at 
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1786)
> at 
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at 
> org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get 
> answer that is of class com.cloud.agent.api.StartAnswer
> at com.cloud.agent.manager.Commands.getAnswer(Commands.

[jira] [Commented] (CLOUDSTACK-1192) Add disk I/O polling to statistics accounting of Instances


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671998#comment-13671998
 ] 

ASF subversion and git services commented on CLOUDSTACK-1192:
-

Commit 65a886de5d45bb6df806ad59de618b586aaba4c5 in branch 
refs/heads/disk_io_stat from [~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=65a886d ]

Revert "CLOUDSTACK-1192: add RBD support"

This reverts commit 385ca81e01754f0f65c18d32f0d35b41616498ac.


> Add disk I/O polling to statistics accounting of Instances
> --
>
> Key: CLOUDSTACK-1192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1192
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller, Usage
>Affects Versions: 4.2.0
>Reporter: Wido den Hollander
>Assignee: Wei Zhou
>  Labels: I/O, IOps
> Fix For: 4.2.0
>
>
> In public clouds (and also private ones) it's important to know how much disk 
> I/O each Instance is consuming.
> Today disk I/O is more expensive then RAM, CPU and Network bandwith, but 
> CloudStack has no way of accounting this.
> CloudStack should collect the disk I/O statistics of all running instances so 
> we can present these in the UI and in the Usage server
> The wiki page for this improvement: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Disk+IO+statistics+for+instances

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1301) VM Disk I/O Throttling

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671999#comment-13671999
 ] 

ASF subversion and git services commented on CLOUDSTACK-1301:
-

Commit 6dad8adf8fc22417f0242126b8f52ee081f74f49 in branch refs/heads/master 
from [~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6dad8ad ]

CLOUDSTACK-1301: Add VM Disk I/O Throttling


> VM Disk I/O Throttling
> --
>
> Key: CLOUDSTACK-1301
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1301
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.0.0, 4.1.0
>Reporter: Wei Zhou
>Assignee: Wei Zhou
> Fix For: 4.2.0
>
>
> VM Disk I/O Throttling, to set the maximum disk I/O rate of VMs.
> Virtual machines are running on the same storage device (local storage or 
> share strage). Because of the rate limitation of device (such as iops), if 
> one VM has large disk operation, it may affect the disk performance of other 
> VMs running on the same storage device.
>  It is neccesary to set the maximum rate and limit the disk I/O of VMs.
> More details:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+IO+Throttling

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1192) Add disk I/O polling to statistics accounting of Instances

2013-05-31 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672000#comment-13672000
 ] 

ASF subversion and git services commented on CLOUDSTACK-1192:
-

Commit b9b0168da4c7b8c2d36a226b2747db5dab60fa98 in branch refs/heads/master 
from [~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b9b0168 ]

CLOUDSTACK-1192: Add Disk I/O Statistics


> Add disk I/O polling to statistics accounting of Instances
> --
>
> Key: CLOUDSTACK-1192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1192
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Storage Controller, Usage
>Affects Versions: 4.2.0
>Reporter: Wido den Hollander
>Assignee: Wei Zhou
>  Labels: I/O, IOps
> Fix For: 4.2.0
>
>
> In public clouds (and also private ones) it's important to know how much disk 
> I/O each Instance is consuming.
> Today disk I/O is more expensive then RAM, CPU and Network bandwith, but 
> CloudStack has no way of accounting this.
> CloudStack should collect the disk I/O statistics of all running instances so 
> we can present these in the UI and in the Usage server
> The wiki page for this improvement: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Disk+IO+statistics+for+instances

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2758) cloudstack-management does not start from RPM packages


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672002#comment-13672002
 ] 

Prasanna Santhanam commented on CLOUDSTACK-2758:


Had to stop and start the management service after chmod +777 on catalina.out

> cloudstack-management does not start from RPM packages
> --
>
> Key: CLOUDSTACK-2758
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2758
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.2.0
>Reporter: Prasanna Santhanam
>Priority: Blocker
> Fix For: 4.2.0
>
>
> For the last two days the packages for CloudStack from jenkins.cs.o haven't 
> been able to boot up the management server. The service start reports OK, but 
> the service dies immediately.
> [root@cloudstack-centos63 ~]# bash -x /etc/init.d/cloudstack-management start
> + '[' -r /etc/rc.d/init.d/functions ']'
> + . /etc/rc.d/init.d/functions
> ++ TEXTDOMAIN=initscripts
> ++ umask 022
> ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin
> ++ export PATH
> ++ '[' -z '' ']'
> ++ COLUMNS=80
> ++ '[' -z '' ']'
> +++ /sbin/consoletype
> ++ CONSOLETYPE=pty
> ++ '[' -f /etc/sysconfig/i18n -a -z '' -a -z '' ']'
> ++ . /etc/profile.d/lang.sh
> ++ unset LANGSH_SOURCED
> ++ '[' -z '' ']'
> ++ '[' -f /etc/sysconfig/init ']'
> ++ . /etc/sysconfig/init
> +++ BOOTUP=color
> +++ RES_COL=60
> +++ MOVE_TO_COL='echo -en \033[60G'
> +++ SETCOLOR_SUCCESS='echo -en \033[0;32m'
> +++ SETCOLOR_FAILURE='echo -en \033[0;31m'
> +++ SETCOLOR_WARNING='echo -en \033[0;33m'
> +++ SETCOLOR_NORMAL='echo -en \033[0;39m'
> +++ PROMPT=yes
> +++ AUTOSWAP=no
> +++ ACTIVE_CONSOLES='/dev/tty[1-6]'
> +++ SINGLE=/sbin/sushell
> ++ '[' pty = serial ']'
> ++ 
> __sed_discard_ignored_files='/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d'
> + '[' -r /lib/lsb/init-functions ']'
> + . /lib/lsb/init-functions
> ++ basename /etc/init.d/cloudstack-management
> + NAME=cloudstack-management
> + case "$1" in
> + set_ulimit
> ++ ulimit -n
> + fd_limit=1024
> + '[' 1024 '!=' 4096 ']'
> ++ whoami
> + user=root
> + '[' root == root ']'
> + ulimit -n 4096
> + . /etc/rc.d/init.d/tomcat6
> ++ '[' -r /lib/lsb/init-functions ']'
> ++ . /lib/lsb/init-functions
> +++ lsb_release -i -s
> ++ DISTRIB_ID=CentOS
> +++ basename /etc/init.d/cloudstack-management
> ++ NAME=cloudstack-management
> ++ unset ISBOOT
> ++ '[' c = S -o c = K ']'
> ++ '[' -x /sbin/runuser ']'
> ++ SU='/sbin/runuser -s /bin/sh'
> ++ TOMCAT_CFG=/etc/tomcat6/tomcat6.conf
> ++ '[' -r /etc/tomcat6/tomcat6.conf ']'
> ++ . /etc/tomcat6/tomcat6.conf
> +++ CATALINA_BASE=/usr/share/tomcat6
> +++ CATALINA_HOME=/usr/share/tomcat6
> +++ JASPER_HOME=/usr/share/tomcat6
> +++ CATALINA_TMPDIR=/var/cache/tomcat6/temp
> +++ JAVA_OPTS=' 
> -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory'
> +++ TOMCAT_USER=tomcat
> +++ SECURITY_MANAGER=false
> +++ SHUTDOWN_WAIT=30
> +++ SHUTDOWN_VERBOSE=false
> +++ CATALINA_PID=/var/run/tomcat6.pid
> ++ '[' -r /etc/sysconfig/cloudstack-management ']'
> ++ . /etc/sysconfig/cloudstack-management
> +++ dummy=1
> +++ export TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
> +++ TOMCAT_CFG=/etc/cloudstack/management/tomcat6.conf
> +++ . /etc/cloudstack/management/tomcat6.conf
>  CATALINA_BASE=/usr/share/cloudstack-management
>  CATALINA_HOME=/usr/share/cloudstack-management
>  JASPER_HOME=/usr/share/cloudstack-management
>  CATALINA_TMPDIR=/usr/share/cloudstack-management/temp
>  JAVA_OPTS='-Djava.awt.headless=true 
> -Dcom.sun.management.jmxremote.port=45219 
> -Dcom.sun.management.jmxremote.authenticate=false 
> -Dcom.sun.management.jmxremote.ssl=false -Xmx2g 
> -XX:+HeapDumpOnOutOfMemoryError 
> -XX:HeapDumpPath=/var/log/cloudstack/management/ -XX:PermSize=512M 
> -XX:MaxPermSize=800m'
>  TOMCAT_USER=cloud
>  TOMCAT6_USER=cloud
>  TOMCAT_LOG=/var/log/cloudstack/management//catalina.out
>  SECURITY_MANAGER=false
>  SHUTDOWN_WAIT=30
>  SHUTDOWN_VERBOSE=false
>  CATALINA_PID=/var/run/cloudstack-management.pid
>  dummy=1
>  . /etc/cloudstack/management/classpath.conf
> + SYSTEMJARS=
> ++ build-classpath
> + SCP=
> + '[' 2 '!=' 0 ']'
> + export SCP=
> + SCP=
> + MCP=
> + DCP=
> + 
> CLASSPATH=:::/etc/cloudstack/management:/usr/share/cloudstack-management/setup
> + for jarfile in '"/usr/share/cloudstack-management/premium"/*'
> + '[' '!' -e '/usr/share/cloudstack-management/premium/*' ']'
> + continue
> + for plugin in '"/usr/share/cloudstack-management/plugin"/*'
> + '[' '!' -e '/usr/share/cloudstack-management/plugin/*' ']'

[jira] [Updated] (CLOUDSTACK-2758) cloudstack-management does not start from RPM packages