date:20130617

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

Ian Duffy updated CLOUDSTACK-2877:
--

Description:
Setup Virtualbox.

Install CentOS VM, this will be used as the development environment. Install
required dev tools and pull down the cloudstack source.

Import devcloud and check that it runs ok.

Build cloudstack on the development environment. Deploy it and check that the
devcloud is successfully added as a host.

This has been documented over here:
http://imduffy15.blogspot.ie/2013/06/setting-up-cloudstack-development.html

was:
Setup Virtualbox.

Install CentOS VM, this will be used as the development environment. Install
required dev tools and pull down the cloudstack source.

Import devcloud and check that it runs ok.

Build cloudstack on the development environment. Deploy it and check that the
devcloud is successfully added as a host.

Create another CentOS VM, install and do the required configuration for
OpenLDAP. Configure cloudstack to use LDAP auth. Test login of LDAP user.

Summary: Setup Dev environment and build cloudstack (was: Setup
development environment)

Setup Dev environment and build cloudstack
--

Key: CLOUDSTACK-2877
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2877
Project: CloudStack
Issue Type: Sub-task
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Environment: Centos 6.4 and DevCloud
Reporter: Ian Duffy
Assignee: Ian Duffy
Fix For: Future

Setup Virtualbox.
Install CentOS VM, this will be used as the development environment. Install
required dev tools and pull down the cloudstack source.
Import devcloud and check that it runs ok.
Build cloudstack on the development environment. Deploy it and check that the
devcloud is successfully added as a host.
This has been documented over here:
http://imduffy15.blogspot.ie/2013/06/setting-up-cloudstack-development.html

--
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-3033) Talk with Abhi - Discuss the current ldap implementation

Ian Duffy created CLOUDSTACK-3033:
-

 Summary: Talk with Abhi - Discuss the current ldap implementation
 Key: CLOUDSTACK-3033
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3033
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Ian Duffy


Discuss the current ldap implementation with ldap. Look at the code behind it.

--
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-3033) Talk with Abhi - Discuss the current ldap implementation


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

Ian Duffy reassigned CLOUDSTACK-3033:
-

Assignee: Ian Duffy

 Talk with Abhi - Discuss the current ldap implementation
 

 Key: CLOUDSTACK-3033
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3033
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Reporter: Ian Duffy
Assignee: Ian Duffy
 Fix For: Future


 Discuss the current ldap implementation with ldap. Look at the code behind it.

--
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-3035) Talk with Abhi - Discuss cloudstack user management

Ian Duffy created CLOUDSTACK-3035:
-

 Summary: Talk with Abhi - Discuss cloudstack user management
 Key: CLOUDSTACK-3035
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3035
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Ian Duffy


Discuss the roles within cloudstack with Abhi.

That is, develop an understanding of what is meant by a user, an account and a 
domain.

--
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-3034) Setup OpenLDAP server


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

Ian Duffy closed CLOUDSTACK-3034.
-

Resolution: Fixed

This has been completed and documented 
http://imduffy15.blogspot.ie/2013/06/setting-up-openldap-server.html

 Setup OpenLDAP server
 -

 Key: CLOUDSTACK-3034
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3034
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
 Environment: CentOS 6.4
Reporter: Ian Duffy
Assignee: Ian Duffy
 Fix For: Future


 Setup an OpenLDAP server on CentOS 6.4 for looking at the current 
 implementation

--
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-3035) Talk with Abhi - Discuss cloudstack user management

2013-06-17 Thread ASF subversion and git services (JIRA)


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

Ian Duffy closed CLOUDSTACK-3035.
-

Resolution: Fixed

This was discussed on the mailing list. 

The following links were supplied:
https://cwiki.apache.org/CLOUDSTACK/accounts-domains-and-admin-explained.html
https://cwiki.apache.org/confluence/display/CLOUDSTACK/2012/09/13/A-CS+Post+Install+Architecture

The thread on the mailing list can be seen at:
http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201306.mbox/%3ccaej3w4vfijnck2duhh1-imc0arww_p7crjweicoxwo0htvu...@mail.gmail.com%3E

 Talk with Abhi - Discuss cloudstack user management
 ---

 Key: CLOUDSTACK-3035
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3035
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Reporter: Ian Duffy
Assignee: Ian Duffy
 Fix For: Future


 Discuss the roles within cloudstack with Abhi.
 That is, develop an understanding of what is meant by a user, an account and 
 a domain.

--
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-2008) guest network vlan tag chain issue

2013-06-17 Thread danny webb (JIRA)


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

danny webb closed CLOUDSTACK-2008.
--

   Resolution: Fixed
Fix Version/s: 4.1.0

issue was fixed in the 4.1.0 release, no idea why/how, just was

 guest network vlan tag chain issue
 --

 Key: CLOUDSTACK-2008
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2008
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Affects Versions: 4.0.1
 Environment: centos 6.4
 HP BL460 G1 
Reporter: danny webb
 Fix For: 4.1.0


 Hi,
 I have setup a cloudstack instance where my root eth device is a vlan 
 tagged bond0.60 (as the network I am on has a different default VLAN id than 
 my test vlans).  
 so I am setup like this:
 bond0.60 / cloudbr0 == management network / ip of box (bond0 == nothing)
  
 bond0.60  Link encap:Ethernet  HWaddr 00:17:A4:77:48:3C  
   inet6 addr: fe80::217:a4ff:fe77:483c/64 Scope:Link
   UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
   RX packets:37189 errors:0 dropped:0 overruns:0 frame:0
   TX packets:34030 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:4476334 (4.2 MiB)  TX bytes:31055747 (29.6 MiB)
 cloudbr0  Link encap:Ethernet  HWaddr 00:17:A4:77:48:3C  
   inet addr:172.18.102.8  Bcast:172.18.102.255  Mask:255.255.255.0
   inet6 addr: fe80::217:a4ff:fe77:483c/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:36531 errors:0 dropped:0 overruns:0 frame:0
   TX packets:32606 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:4435824 (4.2 MiB)  TX bytes:30976056 (29.5 MiB)
  
 when it went to setup a new guest network (with a vlan id of 80) it created 
 it ontop of the bond0.60 like:
  
 bond0.60.80 Link encap:Ethernet  HWaddr 00:17:A4:77:48:3C  
   inet6 addr: fe80::217:a4ff:fe77:483c/64 Scope:Link
   UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
   TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:0 (0.0 b)  TX bytes:13777 (13.4 KiB)
  
 [root@slo-cnkvm004 ~]# brctl show
 bridge name bridge id   STP enabled interfaces
 cloud0  8000.   no 
 cloudVirBr808000.0017a477483c   no  
 bond0.60.80
  
 which doesn't seem to work and I am pretty sure is syntactically wrong.  I 
 can't ping any guests that come up on that network.  When creating new 
 devices it should I believe be creating them off of the base eth device (ie 
 eth0, or bond0).

--
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-3019) Tag missing for test integration.component.test_advancedsg_networks.py


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685101#comment-13685101
 ] 

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

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

CLOUDSTACK-3019: add missing tags for test 
integration.component.test_advancedsg_networks.py


 Tag missing for test integration.component.test_advancedsg_networks.py
 --

 Key: CLOUDSTACK-3019
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3019
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.2.0
 Environment: Automation
Reporter: Rayees Namathponnan
Assignee: Wei Zhou
 Fix For: 4.2.0


 Below test case not getting executed since, no tags
 Tag missing for test integration.component.test_advancedsg_networks.py

--
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-3031) [Objce_Store_Branch]ssvm-check.sh script returen ERROR on object_store branch

2013-06-17 Thread Rajesh Battala (JIRA)


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

Rajesh Battala reassigned CLOUDSTACK-3031:
--

Assignee: Rajesh Battala

 [Objce_Store_Branch]ssvm-check.sh script returen ERROR on object_store branch
 -

 Key: CLOUDSTACK-3031
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3031
 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: Latest build from Object Store Branch
Reporter: Sanjeev N
Assignee: Rajesh Battala
Priority: Critical
 Fix For: 4.2.0


 ssvm-check.sh script returen ERROR on object_store branch
 Steps to Reproduce:
 =
 1.Bring up CS in advanced zone with xenserver using latest build from 
 objcet_store branch
 2.When ssvm is up and running run ssvm-check.sh script
 Following is the script output:
 root@s-26-QA:~# /usr/local/cloud/systemvm/ssvm-check.sh
 
 First DNS server is  10.103.128.16
 PING 10.103.128.16 (10.103.128.16): 56 data bytes
 64 bytes from 10.103.128.16: icmp_seq=0 ttl=122 time=22.551 ms
 64 bytes from 10.103.128.16: icmp_seq=1 ttl=122 time=20.952 ms
 --- 10.103.128.16 ping statistics ---
 2 packets transmitted, 2 packets received, 0% packet loss
 round-trip min/avg/max/stddev = 20.952/21.752/22.551/0.800 ms
 Good: Can ping DNS server
 
 Good: DNS resolves download.cloud.com
 
 NFS is currently mounted
 Mount point is /var/lib/nfs/rpc_pipefs
 touch: cannot touch `/var/lib/nfs/rpc_pipefs/foo': Permission denied
 ERROR: Cannot write to mount point
 You need to export with norootsquash
 
 Management server is 10.147.59.126. Checking connectivity.
 Good: Can connect to management server port 8250
 
 Good: Java process is running
 
 Tests Complete. Look for ERROR or WARNING above.
 Creating a file in mount point /var/lib/nfs/rpc_pipefs/ is failing.
 File permissions on the mount point are as follows:
 root@s-26-QA:~# ls -altr /var/lib/nfs/rpc_pipefs
 total 1
 drwxr-xr-x 5 statd nogroup 1024 Jun  3 04:13 ..
 dr-xr-xr-x 2 root  root   0 Jun 14 14:33 statd
 dr-xr-xr-x 2 root  root   0 Jun 14 14:33 portmap
 dr-xr-xr-x 2 root  root   0 Jun 14 14:33 nfsd4_cb
 dr-xr-xr-x 2 root  root   0 Jun 14 14:33 nfs
 dr-xr-xr-x 2 root  root   0 Jun 14 14:33 mount
 dr-xr-xr-x 2 root  root   0 Jun 14 14:33 lockd
 dr-xr-xr-x 2 root  root   0 Jun 14 14:33 cache
 drwxr-xr-x 9 root  root   0 Jun 14 14:33 .

--
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-2927) [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error

2013-06-17 Thread Likitha Shetty (JIRA)


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

Likitha Shetty reassigned CLOUDSTACK-2927:
--

Assignee: Likitha Shetty

 [AWSAPI] EC2 SOAP calls fail with 'Uninitalized user context' error
 ---

 Key: CLOUDSTACK-2927
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2927
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: AWSAPI
Affects Versions: 4.2.0
Reporter: Likitha Shetty
Assignee: Likitha Shetty
 Fix For: 4.2.0

 Attachments: awsapi.log


 Set enable.ec2.api to true.
 Register user using cloudstack-aws-api-register.
 Make any SOAP API call e.g. ec2-describe-images using ec2 tools.
 Output - Server.InternalError: An unexpected error occurred
 Attached awsapi.log for log details
  

--
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-2823) SystemVMs start fail on CentOS 6.4

2013-06-17 Thread Wei Zhou (JIRA)


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

Wei Zhou updated CLOUDSTACK-2823:
-

Summary: SystemVMs start fail on CentOS 6.4  (was: SystemVMs start fail and 
have no HA)

 SystemVMs start fail on CentOS 6.4
 --

 Key: CLOUDSTACK-2823
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2823
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
 Environment: CentOS 6.4, KVM
 CloudStack master
Reporter: Wei Zhou
Priority: Blocker

 Host:
 [root@cs-kvm015 ~]# virsh version
 Compiled against library: libvirt 0.10.2
 Using library: libvirt 0.10.2
 Using API: QEMU 0.10.2
 Running hypervisor: QEMU 0.12.1
 Network:
 em0 - cloudbr0 (Guest, Public), Guest: 172.16.61.0/24, Public: 10.11.11.0/24 
 (Can not connect outside)
 em1.103 - cloudbr1 (Management, Storage) , IP: 192.168.103.*
 Issue descripion
 (1) SystemVMs (SSVM, CPVM) start fails , and have no IP (Public, guest, 
 management)
 (2) After I destroyed SystemVM, no new SystemVM will be created automatically.
 This issue only exists on master branch
 Deploy 4.1 successfully, and SystemVms work 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] [Resolved] (CLOUDSTACK-3011) [Dedicated Resources] Global config to disallow an account from acquiring public ips and guest vlans from the system

2013-06-17 Thread Likitha Shetty (JIRA)


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

Likitha Shetty resolved CLOUDSTACK-3011.


Resolution: Fixed

 [Dedicated Resources] Global config to disallow an account from acquiring 
 public ips and guest vlans from the system
 

 Key: CLOUDSTACK-3011
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3011
 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
Reporter: Likitha Shetty
Assignee: Likitha Shetty
 Fix For: 4.2.0


 Add 2 configs - use.system.public.ips and use.system.guest.vlans
 The 2 global configs should allow root admin to disallow any account from 
 acquiring public ips and guest vlans from the system if the account has 
 dedicated resources and these dedicated resources have all been consumed.
 Both configs should be configurable at the account level too.

--
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] [Comment Edited] (CLOUDSTACK-3011) [Dedicated Resources] Global config to disallow an account from acquiring public ips and guest vlans from the system

2013-06-17 Thread Likitha Shetty (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685496#comment-13685496
 ] 

Likitha Shetty edited comment on CLOUDSTACK-3011 at 6/17/13 12:29 PM:
--

branch - master
commit-id -  770cf02ccff2e4eac04a332216d1c575f18639be

  was (Author: likithas):
branch - master
commit-id:  770cf02ccff2e4eac04a332216d1c575f18639be
  
 [Dedicated Resources] Global config to disallow an account from acquiring 
 public ips and guest vlans from the system
 

 Key: CLOUDSTACK-3011
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3011
 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
Reporter: Likitha Shetty
Assignee: Likitha Shetty
 Fix For: 4.2.0


 Add 2 configs - use.system.public.ips and use.system.guest.vlans
 The 2 global configs should allow root admin to disallow any account from 
 acquiring public ips and guest vlans from the system if the account has 
 dedicated resources and these dedicated resources have all been consumed.
 Both configs should be configurable at the account level too.

--
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-3036) Configure cloudstack to authenticate users against openldap


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

Ian Duffy updated CLOUDSTACK-3036:
--

Description: Configure cloudstack to auth using an openldap server.  (was: 
Configure cloudstack to authenticate to the openldap server I setup using the 
current implementation.)
Summary: Configure cloudstack to authenticate users against openldap  
(was: Configure cloudstack to authenticate users again openldap)

 Configure cloudstack to authenticate users against openldap
 ---

 Key: CLOUDSTACK-3036
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3036
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Reporter: Ian Duffy
Assignee: Ian Duffy
 Fix For: Future


 Configure cloudstack to auth using an openldap server.

--
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-2901) Ubuntu 13.04 - Migrate guest VM fail - async jobs not completed


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

Alena Prokharchyk reassigned CLOUDSTACK-2901:
-

Assignee: Alena Prokharchyk

 Ubuntu 13.04 - Migrate guest VM  fail - async jobs not completed
 

 Key: CLOUDSTACK-2901
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2901
 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   ASF 4.2   build  
 CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
 hosts ubuntu 13.04CloudStack-non-OSS-master-22-ubuntu13.04.tar.gz
Reporter: angeline shen
Assignee: Alena Prokharchyk
Priority: Blocker
 Fix For: 4.2.0

 Attachments: management-server.log.gz


 1. zone with two PVLAN networks
 2. deploy VMs in both PVLANs.
 Confirm VMs in same PVLAN cannot connect to each other.
 confirm VMs in 1 PVLAN can reach VMs in other PVLAN. VMs can reach 
 outside world
 3. Migrate  guest VMs  async jobs not completed even after 45 minutes, still 
 waiting  .
 2013-06-07 12:48:59,329 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-12:null) submit async job-44, details: AsyncJobVO {id:44, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: 
 null, cmd: org.ap
 ache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null, 
 cmdInfo: 
 {response:json,sessionkey:ZD1MBAdDE0LXFWamvA7uLghcE7g\u003d,virtualmachineid:ce363fbf-3ae5-4917-a0da-4254892e48af,hostid:85e6649c-6b8
 7-49e0-a9be-33552d515182,ctxUserId:2,httpmethod:GET,_:1370634858107,ctxAccountId:2,ctxStartEventId:159},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, resu
 lt: null, initMsid: 206915885084099, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-06-07 12:48:59,329 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-21:job-44) Executing 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-44
 2013-06-07 12:48:59,330 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) 
 ===END===  10.216.133.70 -- GET  
 command=migrateVirtualMachinehostid=85e6649c-6b87-49e0-a9be-33552d515182virtualmachineid=ce363fbf-3ae5-4917-a0da-4254
 892e48afresponse=jsonsessionkey=ZD1MBAdDE0LXFWamvA7uLg
 4.  after 45 minutes
 2013-06-07 13:18:59,377 DEBUG [agent.manager.AgentAttache] 
 (Job-Executor-21:job-44) Seq 5-1461193119: Waiting some more time because 
 this is the current command
 5.  migrate guest VM:
 2013-06-07 12:42:41,015 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-24:null) submit async job-43, details: AsyncJobVO {id:43, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: 
 null, cmd: org.ap
 ache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null, 
 cmdInfo: 
 {response:json,sessionkey:ZD1MBAdDE0LXFWamvA7uLghcE7g\u003d,virtualmachineid:5cb7f1e1-6f9c-45ce-a840-512b09c0fbbb,hostid:08912eba-92d
 a-4495-9566-3a021d29b399,ctxUserId:2,httpmethod:GET,_:1370634479806,ctxAccountId:2,ctxStartEventId:157},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, resu
 lt: null, initMsid: 206915885084099, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-06-07 12:42:41,015 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-20:job-43) Executing 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-43
 2013-06-07 12:42:41,016 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) 
 ===END===  10.216.133.70 -- GET  
 command=migrateVirtualMachinehostid=08912eba-92da-4495-9566-3a021d29b399virtualmachineid=5cb7f1e1-6f9c-45ce-a840-512b
 09c0fbbbresponse=jsonsessionkey=ZD1MBAdDE0LXFWamvA7uLghcE7g%3D_=1370634479806
 6. after 45  minutes
 2013-06-07 13:12:41,067 DEBUG [agent.manager.AgentAttache] 
 (Job-Executor-20:job-43) Seq 1-198249334: Waiting some more time because this 
 is the current command

--
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-3043) Project test suites failing with KeyError: 'classname'

2013-06-17 Thread Rayees Namathponnan (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685668#comment-13685668
 ] 

Rayees Namathponnan commented on CLOUDSTACK-3043:
-

integration/component/test_project_configs.py
integration/component/test_project_limits.py

 Project test suites failing with KeyError: 'classname'
 --

 Key: CLOUDSTACK-3043
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3043
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation
Affects Versions: 4.2.0
 Environment: Automation
Reporter: Rayees Namathponnan
 Fix For: 4.2.0


 Traceback (most recent call last):
   File /usr/local/lib/python2.7/site-packages/nose/suite.py, line 208, in 
 run
 self.setUp()
   File /usr/local/lib/python2.7/site-packages/nose/suite.py, line 291, in 
 setUp
 self.setupContext(ancestor)
   File /usr/local/lib/python2.7/site-packages/nose/suite.py, line 314, in 
 setupContext
 try_run(context, names)
   File /usr/local/lib/python2.7/site-packages/nose/util.py, line 469, in 
 try_run
 return func()
   File 
 /Repo_30X/ipcl/cloudstack/test/integration/component/test_project_configs.py,
  line 458, in setUpClass
 domainid=cls.domain.id
   File 
 /usr/local/lib/python2.7/site-packages/marvin/integration/lib/base.py, line 
 101, in create
 if services[classname] is not None:
 KeyError: 'classname'

--
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-2861) Internal LB VM stuck and does not expunge


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685675#comment-13685675
 ] 

Alena Prokharchyk commented on CLOUDSTACK-2861:
---

The internal lb vm was attempted to be removed as a part of deleteAccount call.

 Internal LB VM stuck and does not expunge
 -

 Key: CLOUDSTACK-2861
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2861
 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
Reporter: Prasanna Santhanam
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.2.0

 Attachments: dbdump.tar.bz2, vmops.log.tar.bz2


 The internal LB vm seems to be having a problem expunging. I'm running the 
 test test_internal_lb.py from test/integration/smoke using a simulator setup 
 Steps:
 1. mvn -pl client jetty:run
 2. deploy advanced zone
 mvn -Pdeveloper,marvin.setup -pl :cloud-marvin integration-test 
 -Dmarvin.config=setup/dev/advanced.cfg
 3. Run internal lb test
 nosetests --with-marvin --marvin-config=setup/dev/advanced.cfg 
 test/integration/smoke/test_internal_lb.py --load
 The test ERRORs out but tearDown does not occur since the internal LB VM is 
 stuck before expunging
 2013-06-05 20:28:10,309 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Network-Scavenger-1:null) Waiting some more to make sure there's no activity 
 on VM[InternalLoadBalancerVm|b-34-VM]
 2013-06-05 20:28:12,790 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-40:job-138) Waiting some more to make sure there's no activity 
 on VM[InternalLoadBalancerVm|b-55-QA]
 Attaching db dump and management server logs

--
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-2914) Regression: With introduction of internal lb provider one must specify the lbScheme when creating network offerings (backward compat)


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

Alena Prokharchyk resolved CLOUDSTACK-2914.
---

Resolution: Fixed

Fixed with fc16e29f992d81156a4e08a77da215f8276f4efe

 Regression: With introduction of internal lb provider one must specify the 
 lbScheme when creating network offerings (backward compat)
 -

 Key: CLOUDSTACK-2914
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2914
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Automation, Doc, Network Controller
Affects Versions: 4.2.0
Reporter: Prasanna Santhanam
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.2.0


 If you choose to have LB in your VPC (by default on the public side) you will 
 need to specify the lbScheme in the serviceCapability list when creating the 
 network offering or LB creation when the network is implemented will fail.
 Following automated test fails:
 nose.suite.ContextSuite context=TestVPCNetworkGc:setup (from nosetests)
 Failing for the past 14 builds (Since #11 )
 Took 16 min.
 add description
 Error Message
 Execute cmd: createloadbalancerrule failed, due to: errorCode: 530, 
 errorText:Failed to create load balancer rule: SSH
 Stacktrace
 Traceback (most recent call last):
   File 
 /var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py,
  line 208, in run
 self.setUp()
   File 
 /var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py,
  line 291, in setUp
 self.setupContext(ancestor)
   File 
 /var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py,
  line 314, in setupContext
 try_run(context, names)
   File 
 /var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/util.py,
  line 469, in try_run
 return func()
   File 
 /var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/test/integration/component/test_vpc_network.py,
  line 2238, in setUpClass
 domainid=cls.account.domainid
   File 
 /var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/integration/lib/base.py,
  line 1498, in create
 return LoadBalancerRule(apiclient.createLoadBalancerRule(cmd).__dict__)
   File 
 /var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 893, in createLoadBalancerRule
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File 
 /var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/cloudstackConnection.py,
  line 223, in marvin_request
 response = jsonHelper.getResultObj(response.json(), response_type)
   File 
 /var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/jsonHelper.py,
  line 128, in getResultObj
 raise 
 cloudstackException.cloudstackAPIException(responseName.replace(response, 
 ), errMsg)
 cloudstackAPIException: Execute cmd: createloadbalancerrule failed, due to: 
 errorCode: 530, errorText:Failed to create load balancer rule: SSH
 In the management server logs:
 WARN  [network.lb.LoadBalancingRulesManagerImpl] 
 (1347080201@qtp-675153853-0:) Failed to create load balancer due to 
 com.cloud.exception.InvalidParameterValueException: Scheme Public is not 
 supported by the network offering [Network Offering [14-Guest-VPC Network 
 offering-P5GNGX]
   at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.isLbServiceSupportedInNetwork(LoadBalancingRulesManagerImpl.java:2103)
   at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.createPublicLoadBalancer(LoadBalancingRulesManagerImpl.java:1401)
   at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
   at 
 com.cloud.network.lb.LoadBalancingRulesManagerImpl.createPublicLoadBalancerRule(LoadBalancingRulesManagerImpl.java:1329)
   at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
   at 
 org.apache.cloudstack.api.command.user.loadbalancer.CreateLoadBalancerRuleCmd.create(CreateLoadBalancerRuleCmd.java:281)
   at

[jira] [Assigned] (CLOUDSTACK-2901) Ubuntu 13.04 - Migrate guest VM fail - async jobs not completed

2013-06-17 Thread ASF subversion and git services (JIRA)


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

Alena Prokharchyk reassigned CLOUDSTACK-2901:
-

Assignee: angeline shen  (was: Alena Prokharchyk)

Angie, can you please reproduce the issue with the TRACE log level? 

 Ubuntu 13.04 - Migrate guest VM  fail - async jobs not completed
 

 Key: CLOUDSTACK-2901
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2901
 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   ASF 4.2   build  
 CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
 hosts ubuntu 13.04CloudStack-non-OSS-master-22-ubuntu13.04.tar.gz
Reporter: angeline shen
Assignee: angeline shen
Priority: Blocker
 Fix For: 4.2.0

 Attachments: management-server.log.gz


 1. zone with two PVLAN networks
 2. deploy VMs in both PVLANs.
 Confirm VMs in same PVLAN cannot connect to each other.
 confirm VMs in 1 PVLAN can reach VMs in other PVLAN. VMs can reach 
 outside world
 3. Migrate  guest VMs  async jobs not completed even after 45 minutes, still 
 waiting  .
 2013-06-07 12:48:59,329 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-12:null) submit async job-44, details: AsyncJobVO {id:44, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: 
 null, cmd: org.ap
 ache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null, 
 cmdInfo: 
 {response:json,sessionkey:ZD1MBAdDE0LXFWamvA7uLghcE7g\u003d,virtualmachineid:ce363fbf-3ae5-4917-a0da-4254892e48af,hostid:85e6649c-6b8
 7-49e0-a9be-33552d515182,ctxUserId:2,httpmethod:GET,_:1370634858107,ctxAccountId:2,ctxStartEventId:159},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, resu
 lt: null, initMsid: 206915885084099, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-06-07 12:48:59,329 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-21:job-44) Executing 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-44
 2013-06-07 12:48:59,330 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) 
 ===END===  10.216.133.70 -- GET  
 command=migrateVirtualMachinehostid=85e6649c-6b87-49e0-a9be-33552d515182virtualmachineid=ce363fbf-3ae5-4917-a0da-4254
 892e48afresponse=jsonsessionkey=ZD1MBAdDE0LXFWamvA7uLg
 4.  after 45 minutes
 2013-06-07 13:18:59,377 DEBUG [agent.manager.AgentAttache] 
 (Job-Executor-21:job-44) Seq 5-1461193119: Waiting some more time because 
 this is the current command
 5.  migrate guest VM:
 2013-06-07 12:42:41,015 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-24:null) submit async job-43, details: AsyncJobVO {id:43, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: 
 null, cmd: org.ap
 ache.cloudstack.api.command.admin.vm.MigrateVMCmd, cmdOriginator: null, 
 cmdInfo: 
 {response:json,sessionkey:ZD1MBAdDE0LXFWamvA7uLghcE7g\u003d,virtualmachineid:5cb7f1e1-6f9c-45ce-a840-512b09c0fbbb,hostid:08912eba-92d
 a-4495-9566-3a021d29b399,ctxUserId:2,httpmethod:GET,_:1370634479806,ctxAccountId:2,ctxStartEventId:157},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, resu
 lt: null, initMsid: 206915885084099, completeMsid: null, lastUpdated: null, 
 lastPolled: null, created: null}
 2013-06-07 12:42:41,015 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-20:job-43) Executing 
 org.apache.cloudstack.api.command.admin.vm.MigrateVMCmd for job-43
 2013-06-07 12:42:41,016 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) 
 ===END===  10.216.133.70 -- GET  
 command=migrateVirtualMachinehostid=08912eba-92da-4495-9566-3a021d29b399virtualmachineid=5cb7f1e1-6f9c-45ce-a840-512b
 09c0fbbbresponse=jsonsessionkey=ZD1MBAdDE0LXFWamvA7uLghcE7g%3D_=1370634479806
 6. after 45  minutes
 2013-06-07 13:12:41,067 DEBUG [agent.manager.AgentAttache] 
 (Job-Executor-20:job-43) Seq 1-198249334: Waiting some more time because this 
 is the current command

--
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-2902) baseurl incorrect in installation guide


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685755#comment-13685755
 ] 

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

Commit c1bb2a561b9a445241e02402232a29d75f612fde in branch refs/heads/4.1 from 
[~chip.child...@sungard.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c1bb2a5 ]

CLOUDSTACK-2902: Updating repository refs


 baseurl incorrect in installation guide
 ---

 Key: CLOUDSTACK-2902
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2902
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.1.0
 Environment: CentOS/RHEL
Reporter: Paul Angus
Priority: Minor
  Labels: documentation
 Fix For: 4.1.1


 baseurl for 4.1.x convenience repo is incorrect - line reads:
 baseurl=http://cloudstack.apt-get.eu/rhel/4.0/
 should read
 baseurl=http://cloudstack.apt-get.eu/rhel/4.1/

--
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-2902) baseurl incorrect in installation guide

2013-06-17 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685758#comment-13685758
 ] 

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

Commit 25726277975fb9e39ade7c08d680a93d33dc16b2 in branch refs/heads/master 
from [~chip.child...@sungard.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2572627 ]

Revert CLOUDSTACK-2902: Fixing references to 4.1 repository for this release

This reverts commit 76d3c27bf4c0ab3690840e56ca162935cea91d48.


 baseurl incorrect in installation guide
 ---

 Key: CLOUDSTACK-2902
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2902
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.1.0
 Environment: CentOS/RHEL
Reporter: Paul Angus
Priority: Minor
  Labels: documentation
 Fix For: 4.1.1


 baseurl for 4.1.x convenience repo is incorrect - line reads:
 baseurl=http://cloudstack.apt-get.eu/rhel/4.0/
 should read
 baseurl=http://cloudstack.apt-get.eu/rhel/4.1/

--
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-2902) baseurl incorrect in installation guide

2013-06-17 Thread Chip Childers (JIRA)


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

Chip Childers resolved CLOUDSTACK-2902.
---

Resolution: Fixed
  Assignee: Chip Childers

 baseurl incorrect in installation guide
 ---

 Key: CLOUDSTACK-2902
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2902
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.1.0
 Environment: CentOS/RHEL
Reporter: Paul Angus
Assignee: Chip Childers
Priority: Minor
  Labels: documentation
 Fix For: 4.1.1


 baseurl for 4.1.x convenience repo is incorrect - line reads:
 baseurl=http://cloudstack.apt-get.eu/rhel/4.0/
 should read
 baseurl=http://cloudstack.apt-get.eu/rhel/4.1/

--
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-869) nTier Apps 2.0 : Support NetScalar as external LB provider

2013-06-17 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685774#comment-13685774
 ] 

ASF subversion and git services commented on CLOUDSTACK-869:


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

CLOUDSTACK-869: Add VPC dialog - add Public LB Provider dropdown, remove VPC 
Offering dropdown. When Public LB Provider is selected as Netscaler, pass 
Default VPC offering with Netscaler to createVPC API. When Public LB Provider 
is selected as VpcVirtualRouter, pass Default VPC Offering to createVPC API.


 nTier Apps 2.0 : Support NetScalar as external LB provider
 --

 Key: CLOUDSTACK-869
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-869
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Kishan Kavala
Assignee: Rajesh Battala
 Fix For: 4.2.0


 As part of supporting external physical devices to do FW  LB,
 https://issues.apache.org/jira/browse/CLOUDSTACK-749
 NetScalarVpcProvider has to be implemented along with corresponding backend 
 scripts.

--
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-2861) Internal LB VM stuck and does not expunge


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

Alena Prokharchyk resolved CLOUDSTACK-2861.
---

Resolution: Cannot Reproduce

I can't reproduce it in the latest build (commit 
952fa2464da9f10b63fbba869922ee735c231c42). Please reopen if you see the issue 
again.

 Internal LB VM stuck and does not expunge
 -

 Key: CLOUDSTACK-2861
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2861
 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
Reporter: Prasanna Santhanam
Assignee: Alena Prokharchyk
Priority: Critical
 Fix For: 4.2.0

 Attachments: dbdump.tar.bz2, vmops.log.tar.bz2


 The internal LB vm seems to be having a problem expunging. I'm running the 
 test test_internal_lb.py from test/integration/smoke using a simulator setup 
 Steps:
 1. mvn -pl client jetty:run
 2. deploy advanced zone
 mvn -Pdeveloper,marvin.setup -pl :cloud-marvin integration-test 
 -Dmarvin.config=setup/dev/advanced.cfg
 3. Run internal lb test
 nosetests --with-marvin --marvin-config=setup/dev/advanced.cfg 
 test/integration/smoke/test_internal_lb.py --load
 The test ERRORs out but tearDown does not occur since the internal LB VM is 
 stuck before expunging
 2013-06-05 20:28:10,309 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Network-Scavenger-1:null) Waiting some more to make sure there's no activity 
 on VM[InternalLoadBalancerVm|b-34-VM]
 2013-06-05 20:28:12,790 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-40:job-138) Waiting some more to make sure there's no activity 
 on VM[InternalLoadBalancerVm|b-55-QA]
 Attaching db dump and management server logs

--
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] [Reopened] (CLOUDSTACK-2481) Object_Store_Refactor - Templates - Not able to create a template from snapshot.

2013-06-17 Thread Sangeetha Hariharan (JIRA)


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

Sangeetha Hariharan reopened CLOUDSTACK-2481:
-


Reopening this issue to  include vhd-util as part of system Vm templates.

 Object_Store_Refactor - Templates - Not able to create a template from 
 snapshot.
 

 Key: CLOUDSTACK-2481
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2481
 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: Build from object store
Reporter: Sangeetha Hariharan
Assignee: edison su
Priority: Critical
 Fix For: 4.2.0


 Steps to reproduce the problem:
 Deploy a VM.
 Take a snapshot of the root volume.
 Create a template from this snapshot.
 API fails with following error message:
 DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@bb917d1: DELETE FROM 
 vm_template WHERE vm_template.id= 203
 Management server logs:
 2013-05-14 09:32:33,964 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) 
 ===START===  10.217.252.128 -- GET  command=createTemplateresponse=json
 sessionkey=X%2FK09rgZ%2BYIUuGYkv7UGa0FoBEc%3Dsnapshotid=d44ae73f-3cbd-49d3-8964-6c3325c24286name=template1displayText=template1osTypeId=fce76ff
 6-bc28-11e2-8a23-6a01c7e420f0isPublic=truepasswordEnabled=false_=1368552572710
 2013-05-14 09:32:34,059 DEBUG [cloud.template.TemplateManagerImpl] 
 (catalina-exec-3:null) This template is getting created from other template, 
 sett
 ing source template Id to: 202
 2013-05-14 09:32:34,118 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-3:null) submit async job-18, details: AsyncJobVO {id:18, 
 userId: 2, a
 ccountId: 2, sessionKey: null, instanceType: Template, instanceId: 203, cmd: 
 org.apache.cloudstack.api.command.user.template.CreateTemplateCmd, cmdO
 riginator: null, cmdInfo: 
 {sessionkey:X/K09rgZ+YIUuGYkv7UGa0FoBEc\u003d,ctxUserId:2,httpmethod:GET,osTypeId:fce76ff6-bc28-11e2-8a23-6
 a01c7e420f0,isPublic:true,response:json,id:203,displayText:template1,snapshotid:d44ae73f-3cbd-49d3-8964-6c3325c24286,passwordE
 nabled:false,name:template1,_:1368552572710,ctxAccountId:2,ctxStartEventId:61},
  cmdVersion: 0, callbackType: 0, callbackAddress:
 null, status: 0, processStatus: 0, resultCode: 0, result: null, initMsid: 
 206915885079359, completeMsid: null, lastUpdated: null, lastPolled: null,
 created: null}
 2013-05-14 09:32:34,119 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-20:job-18) Executing 
 org.apache.cloudstack.api.command.user.template.C
 reateTemplateCmd for job-18
 2013-05-14 09:32:34,122 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) 
 ===END===  10.217.252.128 -- GET  command=createTemplateresponse=jsons
 essionkey=X%2FK09rgZ%2BYIUuGYkv7UGa0FoBEc%3Dsnapshotid=d44ae73f-3cbd-49d3-8964-6c3325c24286name=template1displayText=template1osTypeId=fce76ff6-
 bc28-11e2-8a23-6a01c7e420f0isPublic=truepasswordEnabled=false_=1368552572710
 2013-05-14 09:32:34,207 DEBUG [agent.transport.Request] 
 (Job-Executor-20:job-18) Seq 3-178062289: Sending  { Cmd , MgmtId: 
 206915885079359, via: 3,
 Ver: v1, Flags: 100111, 
 [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{path:
 snapshots/2/1/29d8dd25-c221-4bbc-bc8b-b89d37e362de,volume:{uuid:5d0bd6d7-4ebe-4fb6-98ad-5df52850e739,volumeType:ROOT,dataStore:{org.a
 pache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:e97b5727-d157-3dc1-b32c-065b99806623,id:1,poolType:NetworkFilesystem,host:10.223.
 110.232,path:/export/home/sangeetha/campo-systemp-1/primary,port:2049}},name:ROOT-5,size:8589934592,path:86b8d3a8-44c9-4bb0-b4fb-1ba
 98d3e4f75,volumeId:5,vmName:i-2-5-VM,accountId:2,id:5},dataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232/export/h
 ome/sangeetha/campo-systemp-1/secondary,_role:Image}},vmName:i-2-5-VM,name:test-2_ROOT-5_20130514161859,hypervisorType:XenServer,i
 d:1}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/2/203,uuid:7f10ae7a-0e78-40ed-9b51-3a6a23c9dc66,id
 :203,format:RAW,accountId:2,hvm:true,displayText:template1,imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.2
 32/export/home/sangeetha/campo-systemp-1/secondary,_role:Image}},name:25860e266-0bd4-3eab-abe5-190cd2cafb8b}},wait:10800}}]
  }
 2013-05-14 09:32:37,151 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) 
 ===START===  10.217.252.128 -- GET  command=queryAsyncJobResultjobId=8
 21ce4f1-c8a8-42ce-a095-70144886b536response=jsonsessionkey=X%2FK09rgZ%2BYIUuGYkv7UGa0FoBEc%3D_=1368552575986
 2013-05-14 09:32:37,203 DEBUG [cloud.api.ApiServlet] (catalina-exec-18:null) 
 ===END===

[jira] [Assigned] (CLOUDSTACK-3028) Object_Store_Refactor - S3 reduced redundancy storage should be an option.

2013-06-17 Thread ASF subversion and git services (JIRA)

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

Min Chen reassigned CLOUDSTACK-3028:

Assignee: Min Chen

Object_Store_Refactor - S3 reduced redundancy storage should be an option.
--

Key: CLOUDSTACK-3028
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3028
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Template
Environment: latest object_store branch on fedora 17
devcloud on same machine
Cloudian (for S3 services) on separate machine. (expect similar result with
other S3 object stores).
Reporter: Thomas O'Dowd
Assignee: Min Chen

When uploading a template to the S3 object store, I noticed that the request
asked to be stored using reduced redundancy. I think this should be an option
rather than the default behavior.
Steps:
1. setup S3 object storage (can be amazon)
2. Add S3 as secondary storage
3. Upload a new template (I uploaded tinyLinux.vhd.gz by giving a url on my
local network where I had it hosted)
If you sniff the S3 traffic (assuming you don't use ssl) when you upload the
template in step 3, you can see something like this request.
=== initiate multipart upload request
POST
/template%2Ftmpl%2F2%2F201%2F201-2-f9a12429-7cf4-3df5-b81c-420f09c1bbcd%2FtinyLinux.vhd.gz?uploads
HTTP/1.1.
Host: hello.s3.cloudian.com:18080.
Authorization: AWS 00d25034c817eeb8c095:5P8Y2VM69TgAbixlZoXhAsNjAzI=.
x-amz-storage-class: REDUCED_REDUNDANCY.
Date: Fri, 14 Jun 2013 07:05:26 GMT.
User-Agent: aws-sdk-java/1.3.21.1 Linux/2.6.32-5-686-bigmem
Java_HotSpot(TM)_Client_VM/20.1-b02.
Content-Type: application/x-www-form-urlencoded; charset=utf-8.
Transfer-Encoding: chunked.
Connection: Keep-Alive.
.
0.
.
=== initiate multipart upload request
Notice that the x-amz-storage-class is set to REDUCED_REDUNDANCY. I cannot
see any GUI option to overload this and choose the default storage class.

[jira] [Updated] (CLOUDSTACK-2471) test_host_high_availability.py refers to non-existent library method wait_for_vm

2013-06-17 Thread Sudha Ponnaganti (JIRA)


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

Sudha Ponnaganti updated CLOUDSTACK-2471:
-

Priority: Major  (was: Critical)

 test_host_high_availability.py refers to non-existent library method 
 wait_for_vm
 

 Key: CLOUDSTACK-2471
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2471
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test
Affects Versions: 4.2.0
Reporter: Prasanna Santhanam
 Fix For: 4.2.0


 test_host_high_availability.py:
  #verify the VM live migration happened to another running host
 self.debug(Waiting for VM to come up)
 wait_for_vm( --does not exist in common.py
 self.apiclient,
 virtualmachineid=vm_with_ha_disabled.id,
 interval=timeout
 )
 

--
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-869) nTier Apps 2.0 : Support NetScalar as external LB provider


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685813#comment-13685813
 ] 

ASF subversion and git services commented on CLOUDSTACK-869:


Commit 3e3e5830b45eeba16b3dacfb5475d53d8d2dee27 in branch 
refs/heads/master-6-17-stable from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3e3e583 ]

CLOUDSTACK-869: Add VPC dialog - add Public LB Provider dropdown, remove VPC 
Offering dropdown. When Public LB Provider is selected as Netscaler, pass 
Default VPC offering with Netscaler to createVPC API. When Public LB Provider 
is selected as VpcVirtualRouter, pass Default VPC Offering to createVPC API.


 nTier Apps 2.0 : Support NetScalar as external LB provider
 --

 Key: CLOUDSTACK-869
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-869
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Kishan Kavala
Assignee: Rajesh Battala
 Fix For: 4.2.0


 As part of supporting external physical devices to do FW  LB,
 https://issues.apache.org/jira/browse/CLOUDSTACK-749
 NetScalarVpcProvider has to be implemented along with corresponding backend 
 scripts.

--
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-1623) MySQL Database connection can fail to localhost on a V6 enabled host

2013-06-17 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685834#comment-13685834
 ] 

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

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

CLOUDSTACK-1623: Update documentation to check hosts entry for correct loopback 
interface setup to fix cloud-setup-databases issues during setup


 MySQL Database connection can fail to localhost on a V6 enabled host
 --

 Key: CLOUDSTACK-1623
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1623
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
 Environment: CentOS / RHEL MySQL
Reporter: Shanker Balan
Priority: Trivial
  Labels: doc

 The below snippet can fail on a host with a IPv6 loopback entry in the hosts 
 file and MySQL is not setup to listen on the loopback interface.
 cloud-setup-databases cloud:dbpassword@localhost \
 --deploy-as=root:password \
 -e encryption_type \
 -m management_server_key \
 -k database_key
 The documentation could be updated to mention:
 1) Ensure that MySQL is running on the IPv6 loopback interface ::1
 2) OR, remove the localhost entry which points to ::1 from the hosts file
 [root@db01 ~]# telnet ::1 mysql
 Trying ::1...
 telnet: connect to address ::1: Connection refused
 [root@db01 ~]# telnet 127.0.0.1 mysql
 Trying 127.0.0.1...
 Connected to 127.0.0.1.
 Escape character is '^]'.
 8
 5.1.66-log?!.c,M~vk6i1U:`Ug+:
 ^]
 telnet Connection closed.
 [root@db01 ~]# 

--
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-3028) Object_Store_Refactor - S3 reduced redundancy storage should be an option.

2013-06-17 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685838#comment-13685838
 ] 

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

Commit 1df4cf839e05970e45b9979951cdb66c2feb1f5b in branch 
refs/heads/object_store from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1df4cf8 ]

CLOUDSTACK-3028: Object_Store_Refactor - S3 reduced redundancy storage
should be an option.

 Object_Store_Refactor - S3 reduced redundancy storage should be an option.
 --

 Key: CLOUDSTACK-3028
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3028
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Template
 Environment: latest object_store branch on fedora 17 
 devcloud on same machine 
 Cloudian (for S3 services) on separate machine. (expect similar result with 
 other S3 object stores).
Reporter: Thomas O'Dowd
Assignee: Min Chen

 When uploading a template to the S3 object store, I noticed that the request 
 asked to be stored using reduced redundancy. I think this should be an option 
 rather than the default behavior.
 Steps: 
 1. setup S3 object storage (can be amazon) 
 2. Add S3 as secondary storage 
 3. Upload a new template (I uploaded tinyLinux.vhd.gz by giving a url on my 
 local network where I had it hosted)
 If you sniff the S3 traffic (assuming you don't use ssl) when you upload the 
 template in step 3, you can see something like this request.
 === initiate multipart upload request 
 POST 
 /template%2Ftmpl%2F2%2F201%2F201-2-f9a12429-7cf4-3df5-b81c-420f09c1bbcd%2FtinyLinux.vhd.gz?uploads
  HTTP/1.1.
 Host: hello.s3.cloudian.com:18080.
 Authorization: AWS 00d25034c817eeb8c095:5P8Y2VM69TgAbixlZoXhAsNjAzI=.
 x-amz-storage-class: REDUCED_REDUNDANCY.
 Date: Fri, 14 Jun 2013 07:05:26 GMT.
 User-Agent: aws-sdk-java/1.3.21.1 Linux/2.6.32-5-686-bigmem 
 Java_HotSpot(TM)_Client_VM/20.1-b02.
 Content-Type: application/x-www-form-urlencoded; charset=utf-8.
 Transfer-Encoding: chunked.
 Connection: Keep-Alive.
 .
 0.
 .
 === initiate multipart upload request 
 Notice that the x-amz-storage-class is set to REDUCED_REDUNDANCY. I cannot 
 see any GUI option to overload this and choose the default storage class.

--
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-3028) Object_Store_Refactor - S3 reduced redundancy storage should be an option.

2013-06-17 Thread ASF subversion and git services (JIRA)

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

Min Chen resolved CLOUDSTACK-3028.
--

Resolution: Fixed

Object_Store_Refactor - S3 reduced redundancy storage should be an option.
--

[jira] [Updated] (CLOUDSTACK-2994) [Automation][Object_Store] Failed to attach ISO to vm

2013-06-17 Thread Sudha Ponnaganti (JIRA)


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

Sudha Ponnaganti updated CLOUDSTACK-2994:
-

Priority: Blocker  (was: Major)

 [Automation][Object_Store] Failed to attach ISO to vm
 -

 Key: CLOUDSTACK-2994
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2994
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: ISO
Affects Versions: 4.2.0
 Environment: Object_Store branch build
 KVM
Reporter: Rayees Namathponnan
Priority: Blocker
 Fix For: 4.2.0


 BVT test 
 integration.smoke.test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso
   failed due to this
 Steps to reproduce 
 Step 1 : Add iSO http://people.apache.org/~tsp/dummy.iso
 Step 2 : Create new VM
 Step 3 : Attach ISO to VM
 Attach ISO failedwith below error 
 2013-06-13 10:27:36,215 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null) 
 ===START===  10.216.51.168 -- GET  
 command=attachIsovirtualmachineid=b50c968b-92c2-44fb-b82a-de6891f77a5bid=6cc5a9c8-c35f-4c44-bdb2-b14ab64dcd36response=jsonsessionkey=ThbZI1AXRGDVsDUBZS5Iq9ZvFhw%3D_=1371133809191
 2013-06-13 10:27:36,218 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-332:null) Ping from 1
 2013-06-13 10:27:36,249 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-35:job-279) Executing 
 org.apache.cloudstack.api.command.user.iso.AttachIsoCmd for job-279
 2013-06-13 10:27:36,253 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-21:null) submit async job-279, details: AsyncJobVO {id:279, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: 
 null, cmd: org.apache.cloudstack.api.command.user.iso.AttachIsoCmd, 
 cmdOriginator: null, cmdInfo: 
 {id:6cc5a9c8-c35f-4c44-bdb2-b14ab64dcd36,response:json,sessionkey:ThbZI1AXRGDVsDUBZS5Iq9ZvFhw\u003d,virtualmachineid:b50c968b-92c2-44fb-b82a-de6891f77a5b,ctxUserId:2,httpmethod:GET,_:1371133809191,ctxAccountId:2,ctxStartEventId:1239},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 29066118877352, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-06-13 10:27:36,255 DEBUG [cloud.api.ApiServlet] (catalina-exec-21:null) 
 ===END===  10.216.51.168 -- GET  
 command=attachIsovirtualmachineid=b50c968b-92c2-44fb-b82a-de6891f77a5bid=6cc5a9c8-c35f-4c44-bdb2-b14ab64dcd36response=jsonsessionkey=ThbZI1AXRGDVsDUBZS5Iq9ZvFhw%3D_=1371133809191
 2013-06-13 10:27:36,286 DEBUG [agent.transport.Request] 
 (Job-Executor-35:job-279) Seq 4-1568017056: Sending  { Cmd , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.AttachCommand:{disk:{data:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/2/210/210-2-726db663-1f18-3551-9358-1124895169dc.iso,origUrl:http://people.apache.org/~tsp/dummy.iso,uuid:6cc5a9c8-c35f-4c44-bdb2-b14ab64dcd36,id:210,format:ISO,accountId:2,checksum:b11099d68763f87ee90eab7af1d4dd1e,hvm:true,displayText:iso,imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary,_role:Image}},name:210-2-726db663-1f18-3551-9358-1124895169dc}},type:ISO},vmName:i-2-88-VM,wait:0}}]
  }
 2013-06-13 10:27:36,488 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-6:null) Seq 4-1568017056: Processing:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10, 
 [{com.cloud.agent.api.Answer:{result:false,details:org.libvirt.LibvirtException:
  Domain not found: no domain with matching uuid 
 '3670-3193-38c2-a567-ff66dfeb8e66',wait:0}}] }
 2013-06-13 10:27:36,489 DEBUG [agent.transport.Request] 
 (Job-Executor-35:job-279) Seq 4-1568017056: Received:  { Ans: , MgmtId: 
 29066118877352, via: 4, Ver: v1, Flags: 10, { Answer } }
 2013-06-13 10:27:36,489 DEBUG [agent.manager.AgentManagerImpl] 
 (Job-Executor-35:job-279) Details from executing class 
 org.apache.cloudstack.storage.command.AttachCommand: 
 org.libvirt.LibvirtException: Domain not found: no domain with matching uuid 
 '3670-3193-38c2-a567-ff66dfeb8e66'
 2013-06-13 10:27:36,494 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-35:job-279) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.iso.AttachIsoCmd
 com.cloud.utils.exception.CloudRuntimeException: Failed to attach iso
 at 
 com.cloud.template.TemplateManagerImpl.attachIso(TemplateManagerImpl.java:975)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.iso.AttachIsoCmd.execute(AttachIsoCmd.java:99)

[jira] [Assigned] (CLOUDSTACK-3038) [Object_Store_Refactor] Deleting account fails when there are snapshots present on primary for this account

2013-06-17 Thread edison su (JIRA)


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

edison su reassigned CLOUDSTACK-3038:
-

Assignee: edison su

 [Object_Store_Refactor] Deleting account fails when there are snapshots 
 present on primary for this account
 ---

 Key: CLOUDSTACK-3038
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3038
 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: Latest build on object_store branch
Reporter: Sanjeev N
Assignee: edison su
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


 Deleting account fails when there are snapshots present on primary for this 
 account
 Steps to Reproduce:
 =
 1.Bring up CS in advanced zone with S3 as the secondary storage provider
 2.Create a domain-admin account
 3.With the domain-admin created at step2 deploy guest vms using the default 
 cent os templates downloaded to S3 
 3.Create Manual/Recurring snapshots on the root/data disk of the guest 
 vms(Snapshot will be created on primary but backing up to secondary will fail 
 which is a know issue)
 4. Delete the domain-admin account
 Observations:
 ===
 Account creation failed with DB Exceptions. Following is the log snippet from 
 management server log:
 2013-06-17 10:27:17,911 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-86:job-94) Executing 
 org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd for job-94
 2013-06-17 10:27:17,981 DEBUG [cloud.user.AccountManagerImpl] 
 (Job-Executor-86:job-94) Removed account 7
 2013-06-17 10:27:17,998 DEBUG [agent.transport.Request] 
 (Job-Executor-86:job-94) Seq 4-1483016562: Sending  { Cmd , MgmtId: 
 6615759585382, via: 4, Ver: v1, Flags: 100111, 
 [{com.cloud.agent.api.DeleteSnapshotsDirCommand:{store:{com.cloud.agent.api.to.S3TO:{id:1,uuid:9eb0800d-41ab-4338-a449-cd4624a7fe19,accessKey:9M7I6JPYZHDNLG43TWCD,secretKey:KL7IAVYcYO8URicgniNjeCmL7k3tYKMpJRXNHw==,endPoint:10.147.29.57:8080,bucketName:imagestore,httpsFlag:false,created:Jun
  14, 2013 8:00:03 AM}},directory:snapshots/7/5,wait:0}}] }
 2013-06-17 10:27:18,099 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-15:null) Seq 4-1483016562: Processing:  { Ans: , 
 MgmtId: 6615759585382, via: 4, Ver: v1, Flags: 110, 
 [{com.cloud.agent.api.Answer:{result:true,details:Deleted snapshot %s 
 from bucket imagestore.,wait:0}}] }
 2013-06-17 10:27:18,099 DEBUG [agent.manager.AgentAttache] 
 (AgentManager-Handler-15:null) Seq 4-1483016562: No more commands found
 2013-06-17 10:27:18,099 DEBUG [agent.transport.Request] 
 (Job-Executor-86:job-94) Seq 4-1483016562: Received:  { Ans: , MgmtId: 
 6615759585382, via: 4, Ver: v1, Flags: 110, { Answer } }
 2013-06-17 10:27:18,099 DEBUG [storage.snapshot.SnapshotManagerImpl] 
 (Job-Executor-86:job-94) Deleted all snapshots for volume: 5 under account: 7
 2013-06-17 10:27:18,102 DEBUG [db.Transaction.Transaction] 
 (Job-Executor-86:job-94) Rolling back the transaction: Time = 2 Name =  
 -AsyncJobManagerImpl$1.run:401-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679;
  called by 
 -Transaction.rollback:890-Transaction.removeUpTo:833-Transaction.close:657-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-SnapshotManagerImpl.deleteSnapshotDirsForAccount:688-AccountManagerImpl.cleanupAccount:581-AccountManagerImpl.deleteAccount:544-AccountManagerImpl.deleteUserAccount:1255-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-RegionManagerImpl.deleteUserAccount:177-RegionServiceImpl.deleteUserAccount:118
 2013-06-17 10:27:18,104 WARN  [cloud.user.AccountManagerImpl] 
 (Job-Executor-86:job-94) Failed to cleanup account Acct[7-test-WA24HE] due to
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@39a10f0: DELETE FROM snapshots WHERE 
 snapshots.id= 1
 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1137)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.snapshot.SnapshotManagerImpl.deleteSnapshotDirsForAccount(SnapshotManagerImpl.java:688)
 at 
 com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:581)
 at 
 com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:544)

[jira] [Assigned] (CLOUDSTACK-2821) [XenServer] ModifyStoragePoolCommand fails with error com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: a1a1a150-6709-3d81-a414-4cee93e621

2013-06-17 Thread Devdeep Singh (JIRA)


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

Devdeep Singh reassigned CLOUDSTACK-2821:
-

Assignee: Devdeep Singh

 [XenServer] ModifyStoragePoolCommand fails with error 
 com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: 
 a1a1a150-6709-3d81-a414-4cee93e62168 from on 
 host:0afd552a-6c99-4c50-aa58-47b817786793
 -

 Key: CLOUDSTACK-2821
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2821
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: XenServer
Affects Versions: 4.2.0
 Environment: commit # b4969c4af5264879ccbec01b65b6c94886fc79d4
Reporter: venkata swamybabu budumuru
Assignee: Devdeep Singh
Priority: Critical
 Fix For: 4.2.0

 Attachments: logs.tgz


 Steps to reproduce:
 1. Have the latest CloudStack setup with at least 1 adv zone (1 cluster with 
 XenServer 6.1 with all latest patches) and only system VMs in running state.
 2. Make sure that all the system vms are in Stopped state and no user vms 
 are created and the zone is in disabled state.
 3. Push the XenServer host into Maintenance mode
 4. After the host is successfully placed in maintenance, remove the host.
 5. Add a totally different freshly installed host to the same cluster.
 Observations:-
 (i) It failed with the following error.
 2013-06-03 13:06:00,403 DEBUG [agent.transport.Request] 
 (AgentTaskPool-2:null) Seq 8-690552836: Sending  { Cmd , MgmtId: 
 7280707764394, via: 8, Ver: v1, Flags: 100011, 
 [{ModifyStoragePoolCommand:{add:true,pool:{id:2,uuid:a1a1a150-6709-3d81-a414-4cee93e62168,host:10.147.28.7,path:/export/home/swamy/primary.campo.xen.1,port:2049,type:NetworkFilesystem},localPath:/mnt//a1a1a150-6709-3d81-a414-4cee93e62168,wait:0}}]
  }
 2013-06-03 13:06:00,407 DEBUG [agent.transport.Request] 
 (AgentTaskPool-2:null) Seq 8-690552836: Executing:  { Cmd , MgmtId: 
 7280707764394, via: 8, Ver: v1, Flags: 100011, 
 [{ModifyStoragePoolCommand:{add:true,pool:{id:2,uuid:a1a1a150-6709-3d81-a414-4cee93e62168,host:10.147.28.7,path:/export/home/swamy/primary.campo.xen.1,port:2049,type:NetworkFilesystem},localPath:/mnt//a1a1a150-6709-3d81-a414-4cee93e62168,wait:0}}]
  }
 2013-06-03 13:06:00,407 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-2:null) Seq 8-690552836: Executing request
 2013-06-03 13:06:00,489 WARN  [xen.resource.CitrixResourceBase] 
 (DirectAgent-2:null) ModifyStoragePoolCommand add XenAPIException:Can not see 
 storage pool: a1a1a150-6709-3d81-a414-4cee93e62168 from on 
 host:0afd552a-6c99-4c50-aa58-47b817786793 
 host:0afd552a-6c99-4c50-aa58-47b817786793 pool: 
 10.147.28.7/export/home/swamy/primary.campo.xen.1
 com.cloud.utils.exception.CloudRuntimeException: Can not see storage pool: 
 a1a1a150-6709-3d81-a414-4cee93e62168 from on 
 host:0afd552a-6c99-4c50-aa58-47b817786793
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.getStorageRepository(CitrixResourceBase.java:7548)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:5568)
 at 
 com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:510)
 at 
 com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
 at 
 com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102)
 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)
 (ii) CS sent modifyStoragePoolCmd and it didn't fine any SR with the UUID 
 of primary and it resulted in failure.
 (iii) Due to the above mentioned error, Primary storage never gets mounted 
 and no VMs can be started until the primary storage is completely removed 
 from CS and added newly.

[jira] [Commented] (CLOUDSTACK-3016) remove zonetype parameter from list API commands


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686072#comment-13686072
 ] 

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

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

CLOUDSTACK-3016: remove zonetype parameter from listSnapshots API.


 remove zonetype parameter from list API commands
 

 Key: CLOUDSTACK-3016
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Reporter: Jessica Wang
Assignee: Jessica Wang



--
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-3045) UI - Error array2 is undefined shown when try to add a host

2013-06-17 Thread Sheng Yang (JIRA)

Sheng Yang created CLOUDSTACK-3045:
--

 Summary: UI -  Error array2 is undefined shown when try to add a 
host
 Key: CLOUDSTACK-3045
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3045
 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: Sheng Yang
Priority: Critical
 Fix For: 4.2.0


Tried to add a host, UI would show array2 is undefined for firebugs, and the 
screen won't be updated anyway.

Firebugs said:

TypeError: array2 is undefined
[Break On This Error]   

...eURL(dedicateHosthostId= +hostId +domainId= +args.data.domainId + 
array2.j...

--
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-2956) listStoragePools API is returning cluster details for zone scoped primary storage

2013-06-17 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686083#comment-13686083
 ] 

Min Chen commented on CLOUDSTACK-2956:
--

This is actually not an issue with listStoragePools, but how you invoked 
createStoragePool API. You invoked createStoragePool with scope=zone, but still 
passed clusterId and podId, this invocation itself is already contradictory, so 
createStoragePool persists cluster information with the pool created, causing 
list to show them as well. 

 listStoragePools API is returning cluster details for zone scoped primary 
 storage
 -

 Key: CLOUDSTACK-2956
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2956
 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
Reporter: Srikanteswararao Talluri
Assignee: Min Chen
Priority: Critical
 Fix For: 4.2.0


 1. While deploying a zone using zone create wizard and add a zone scoped 
 primary storage.
 2. Invoke listStoragePools API.
 It is listing cluster details for  zone scoped primary storage which doesn't 
 make sense.
 This is happening when  createStoragePool API is invoked by providing 
 clustered= and podId= 
 command=createStoragePoolzoneid=223c3687-f561-4b16-9584-2e1266c303b1podId=fd70cc91-07ee-4c5e-92ff-3090911653a8clusterid=ce410600-35c3-4e69-af4e-972b61bd9259name=primscope=zonehypervisor=VMwareurl=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Ftalluri%2Fmysetup_primresponse=jsonsessionkey=vQryK5i4jo4Lm%2BLJ%2F3gHgGQzneg%3D_=1371030846595
 liststoragepoolsresponse cloud-stack-version=4.2.0-SNAPSHOT
 count3/count
 storagepool
 id98a13fa4-5768-3a67-b6ed-6c06e609a4dc/id
 zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
 zonenamezwpszone/zonename
 zonetypeAdvanced/zonetype
 podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid
 podnamepod/podname
 nameprim3/name
 ipaddress10.147.28.7/ipaddress
 path/export/home/talluri/mysetup_prim3/path
 created2013-06-12T21:44:10+0530/created
 typeNetworkFilesystem/type
 clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid
 clustername10.147.60.15/stormig/stormig_clus/clustername
 disksizetotal590228480/disksizetotal
 disksizeallocated0/disksizeallocated
 disksizeused3281502081024/disksizeused
 stateUp/state
 scopeZONE/scope
 hypervisorVMware/hypervisor
 /storagepool
 storagepool
 idece502dc-5d06-3043-afec-38e3d54fe995/id
 zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
 zonenamezwpszone/zonename
 zonetypeAdvanced/zonetype
 nameprim2/name
 ipaddress10.147.28.7/ipaddress
 path/export/home/talluri/mysetup_prim2/path
 created2013-06-12T21:23:13+0530/created
 typeNetworkFilesystem/type
 disksizetotal590228480/disksizetotal
 disksizeallocated0/disksizeallocated
 disksizeused3281155739648/disksizeused
 stateUp/state
 scopeZONE/scope
 hypervisorVMware/hypervisor
 /storagepool
 storagepool
 id5a830e2f-3b1e-32fd-bdde-a418fba453a2/id
 zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
 zonenamezwpszone/zonename
 zonetypeAdvanced/zonetype
 podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid
 podnamepod/podname
 nameprim/name
 ipaddress10.147.28.7/ipaddress
 path/export/home/talluri/mysetup_prim/path
 created2013-06-12T20:49:33+0530/created
 typeNetworkFilesystem/type
 clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid
 clustername10.147.60.15/stormig/stormig_clus/clustername
 disksizetotal590228480/disksizetotal
 disksizeallocated8489271296/disksizeallocated
 disksizeused3280631812096/disksizeused
 stateUp/state
 scopeZONE/scope
 hypervisorVMware/hypervisor
 /storagepool
 /liststoragepoolsresponse

--
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-3016) remove zonetype parameter from list API commands


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686099#comment-13686099
 ] 

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

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

CLOUDSTACK-3016: remove zonetype parameter from listClusters API.


 remove zonetype parameter from list API commands
 

 Key: CLOUDSTACK-3016
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Reporter: Jessica Wang
Assignee: Jessica Wang



--
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-2956) createStoragePools API should ignore passed clusterId and podId parameters in creating zone scoped primary storage

2013-06-17 Thread ASF subversion and git services (JIRA)


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

Min Chen updated CLOUDSTACK-2956:
-

Summary: createStoragePools API should ignore passed clusterId and podId 
parameters in creating zone scoped primary storage  (was: listStoragePools API 
is returning cluster details for zone scoped primary storage)

Edit the bug subject to reflect the real problem.

 createStoragePools API should ignore passed clusterId and podId parameters in 
 creating zone scoped primary storage
 --

 Key: CLOUDSTACK-2956
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2956
 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
Reporter: Srikanteswararao Talluri
Assignee: Min Chen
Priority: Critical
 Fix For: 4.2.0


 1. While deploying a zone using zone create wizard and add a zone scoped 
 primary storage.
 2. Invoke listStoragePools API.
 It is listing cluster details for  zone scoped primary storage which doesn't 
 make sense.
 This is happening when  createStoragePool API is invoked by providing 
 clustered= and podId= 
 command=createStoragePoolzoneid=223c3687-f561-4b16-9584-2e1266c303b1podId=fd70cc91-07ee-4c5e-92ff-3090911653a8clusterid=ce410600-35c3-4e69-af4e-972b61bd9259name=primscope=zonehypervisor=VMwareurl=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Ftalluri%2Fmysetup_primresponse=jsonsessionkey=vQryK5i4jo4Lm%2BLJ%2F3gHgGQzneg%3D_=1371030846595
 liststoragepoolsresponse cloud-stack-version=4.2.0-SNAPSHOT
 count3/count
 storagepool
 id98a13fa4-5768-3a67-b6ed-6c06e609a4dc/id
 zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
 zonenamezwpszone/zonename
 zonetypeAdvanced/zonetype
 podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid
 podnamepod/podname
 nameprim3/name
 ipaddress10.147.28.7/ipaddress
 path/export/home/talluri/mysetup_prim3/path
 created2013-06-12T21:44:10+0530/created
 typeNetworkFilesystem/type
 clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid
 clustername10.147.60.15/stormig/stormig_clus/clustername
 disksizetotal590228480/disksizetotal
 disksizeallocated0/disksizeallocated
 disksizeused3281502081024/disksizeused
 stateUp/state
 scopeZONE/scope
 hypervisorVMware/hypervisor
 /storagepool
 storagepool
 idece502dc-5d06-3043-afec-38e3d54fe995/id
 zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
 zonenamezwpszone/zonename
 zonetypeAdvanced/zonetype
 nameprim2/name
 ipaddress10.147.28.7/ipaddress
 path/export/home/talluri/mysetup_prim2/path
 created2013-06-12T21:23:13+0530/created
 typeNetworkFilesystem/type
 disksizetotal590228480/disksizetotal
 disksizeallocated0/disksizeallocated
 disksizeused3281155739648/disksizeused
 stateUp/state
 scopeZONE/scope
 hypervisorVMware/hypervisor
 /storagepool
 storagepool
 id5a830e2f-3b1e-32fd-bdde-a418fba453a2/id
 zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
 zonenamezwpszone/zonename
 zonetypeAdvanced/zonetype
 podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid
 podnamepod/podname
 nameprim/name
 ipaddress10.147.28.7/ipaddress
 path/export/home/talluri/mysetup_prim/path
 created2013-06-12T20:49:33+0530/created
 typeNetworkFilesystem/type
 clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid
 clustername10.147.60.15/stormig/stormig_clus/clustername
 disksizetotal590228480/disksizetotal
 disksizeallocated8489271296/disksizeallocated
 disksizeused3280631812096/disksizeused
 stateUp/state
 scopeZONE/scope
 hypervisorVMware/hypervisor
 /storagepool
 /liststoragepoolsresponse

--
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-2956) createStoragePools API should ignore passed clusterId and podId parameters in creating zone scoped primary storage


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686115#comment-13686115
 ] 

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

Commit dff87ed7cf048fb845bb6f466587d60cf3f8fcb7 in branch 
refs/heads/master-6-17-stable from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=dff87ed ]

CLOUDSTACK-2956:createStoragePools API should ignore passed clusterId
and podId parameters in creating zone scoped primary storage

 createStoragePools API should ignore passed clusterId and podId parameters in 
 creating zone scoped primary storage
 --

 Key: CLOUDSTACK-2956
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2956
 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
Reporter: Srikanteswararao Talluri
Assignee: Min Chen
Priority: Critical
 Fix For: 4.2.0


 1. While deploying a zone using zone create wizard and add a zone scoped 
 primary storage.
 2. Invoke listStoragePools API.
 It is listing cluster details for  zone scoped primary storage which doesn't 
 make sense.
 This is happening when  createStoragePool API is invoked by providing 
 clustered= and podId= 
 command=createStoragePoolzoneid=223c3687-f561-4b16-9584-2e1266c303b1podId=fd70cc91-07ee-4c5e-92ff-3090911653a8clusterid=ce410600-35c3-4e69-af4e-972b61bd9259name=primscope=zonehypervisor=VMwareurl=nfs%3A%2F%2F10.147.28.7%2Fexport%2Fhome%2Ftalluri%2Fmysetup_primresponse=jsonsessionkey=vQryK5i4jo4Lm%2BLJ%2F3gHgGQzneg%3D_=1371030846595
 liststoragepoolsresponse cloud-stack-version=4.2.0-SNAPSHOT
 count3/count
 storagepool
 id98a13fa4-5768-3a67-b6ed-6c06e609a4dc/id
 zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
 zonenamezwpszone/zonename
 zonetypeAdvanced/zonetype
 podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid
 podnamepod/podname
 nameprim3/name
 ipaddress10.147.28.7/ipaddress
 path/export/home/talluri/mysetup_prim3/path
 created2013-06-12T21:44:10+0530/created
 typeNetworkFilesystem/type
 clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid
 clustername10.147.60.15/stormig/stormig_clus/clustername
 disksizetotal590228480/disksizetotal
 disksizeallocated0/disksizeallocated
 disksizeused3281502081024/disksizeused
 stateUp/state
 scopeZONE/scope
 hypervisorVMware/hypervisor
 /storagepool
 storagepool
 idece502dc-5d06-3043-afec-38e3d54fe995/id
 zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
 zonenamezwpszone/zonename
 zonetypeAdvanced/zonetype
 nameprim2/name
 ipaddress10.147.28.7/ipaddress
 path/export/home/talluri/mysetup_prim2/path
 created2013-06-12T21:23:13+0530/created
 typeNetworkFilesystem/type
 disksizetotal590228480/disksizetotal
 disksizeallocated0/disksizeallocated
 disksizeused3281155739648/disksizeused
 stateUp/state
 scopeZONE/scope
 hypervisorVMware/hypervisor
 /storagepool
 storagepool
 id5a830e2f-3b1e-32fd-bdde-a418fba453a2/id
 zoneid223c3687-f561-4b16-9584-2e1266c303b1/zoneid
 zonenamezwpszone/zonename
 zonetypeAdvanced/zonetype
 podidfd70cc91-07ee-4c5e-92ff-3090911653a8/podid
 podnamepod/podname
 nameprim/name
 ipaddress10.147.28.7/ipaddress
 path/export/home/talluri/mysetup_prim/path
 created2013-06-12T20:49:33+0530/created
 typeNetworkFilesystem/type
 clusteridce410600-35c3-4e69-af4e-972b61bd9259/clusterid
 clustername10.147.60.15/stormig/stormig_clus/clustername
 disksizetotal590228480/disksizetotal
 disksizeallocated8489271296/disksizeallocated
 disksizeused3280631812096/disksizeused
 stateUp/state
 scopeZONE/scope
 hypervisorVMware/hypervisor
 /storagepool
 /liststoragepoolsresponse

--
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-3016) remove zonetype parameter from list API commands

2013-06-17 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686122#comment-13686122
 ] 

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

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

CLOUDSTACK-3016: remove zonetype parameter from listPods API.


 remove zonetype parameter from list API commands
 

 Key: CLOUDSTACK-3016
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Reporter: Jessica Wang
Assignee: Jessica Wang



--
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-2883) Add default network offering with Internal LB support

2013-06-17 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686157#comment-13686157
 ] 

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

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

CLOUDSTACK-2883: create default network offering with internal lb support (if 
doesn't exist already)


 Add default network offering with Internal LB support
 -

 Key: CLOUDSTACK-2883
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2883
 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
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
 Fix For: 4.2.0


 Would make sense to have a default network offering with the Internal LB 
 support.

--
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-3016) remove zonetype parameter from list API commands

2013-06-17 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686162#comment-13686162
 ] 

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

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

CLOUDSTACK-3016: remove zonetype parameter from listNetworks API.


 remove zonetype parameter from list API commands
 

 Key: CLOUDSTACK-3016
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3016
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Reporter: Jessica Wang
Assignee: Jessica Wang



--
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-2883) Add default network offering with Internal LB support