[jira] [Commented] (CLOUDSTACK-8697) Assign VPC Internal LB rule to a VM fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940963#comment-14940963
]
sebastien goasguen commented on CLOUDSTACK-8697:
[~pavanb] [~sadhu] what do you guys think ? Looks like the issue is understood,
but was also present in 4.4.4.
Any preference on how this should be fixed ?
Do you have a fix already yourselves ?
> Assign VPC Internal LB rule to a VM fails
> -
>
> Key: CLOUDSTACK-8697
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8697
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.4.4, 4.6.0
>Reporter: Pavan Kumar Bandarupally
>Assignee: Wilder Rodrigues
>Priority: Blocker
> Attachments: MS Log.rar, MSLog.rar
>
>
> Assigning an internal LB rule to a VM inside VPC network fails. Seems to be a
> configuration issue.
>
> 2015-07-31 21:13:49,059 ERROR [c.c.u.s.SshHelper]
> (DirectAgent-345:ctx-2bdddfcc) SSH execution of command
> /opt/cloud/bin/router_proxy.sh update_config.py 169.254.2.171
> load_balancer.json has an error status code in return. result output:
> 2015-07-31 21:13:49,062 DEBUG [c.c.a.r.v.VirtualRoutingResource]
> (DirectAgent-345:ctx-2bdddfcc) Processing ScriptConfigItem, executing
> update_config.py load_balancer.json took 6656ms
> 2015-07-31 21:13:49,062 WARN [c.c.a.r.v.VirtualRoutingResource]
> (DirectAgent-345:ctx-2bdddfcc) Expected 1 answers while executing
> LoadBalancerConfigCommand but received 2
> 2015-07-31 21:13:49,062 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-345:ctx-2bdddfcc) Seq 7-4435764157983228083: Response Received:
> 2015-07-31 21:13:49,063 DEBUG [c.c.a.t.Request]
> (DirectAgent-345:ctx-2bdddfcc) Seq 7-4435764157983228083: Processing: { Ans:
> , MgmtId: 6702933999656, via: 7, Ver: v1, Flags: 0,
> [{"com.cloud.agent.api.routing.GroupAnswer":{"results":["null - failed:
> ","null - failed: "],"result":false,"wait":0}}] }
> 2015-07-31 21:13:49,063 DEBUG [c.c.a.t.Request]
> (API-Job-Executor-9:ctx-4c2d49d3 job-315 ctx-06ebb5a1) Seq
> 7-4435764157983228083: Received: { Ans: , MgmtId: 6702933999656, via: 7,
> Ver: v1, Flags: 0, { GroupAnswer } }
> 2015-07-31 21:13:49,133 DEBUG [c.c.n.l.LoadBalancingRulesManagerImpl]
> (API-Job-Executor-9:ctx-4c2d49d3 job-315 ctx-06ebb5a1) LB Rollback rule id: 6
> while attaching VM: [29]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8899) baremetal VM deployment via service offering with host tag fail
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14936594#comment-14936594 ] sebastien goasguen commented on CLOUDSTACK-8899: how does this related to #8897 ? > baremetal VM deployment via service offering with host tag fail > --- > > Key: CLOUDSTACK-8899 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8899 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal, Management Server >Reporter: Harikrishna Patnala >Assignee: Harikrishna Patnala > Fix For: 4.6.0 > > > 1. BM zone. > 2. create service offerings: > Service offerings hosttag > -- > bm512SO1 large > bm512SO2 large2 > bm512SO3 large3 > 3. add 3 hosts with hosttag: > host IPMI hosttag > > Host1 -> large > Host2 -> large2 > Host3 -> large3 > 4. deploy S03V33 using service offering bm512SO3 (host tag 'large3') result > in host with hosttag 'large' - BUG > 5. deploy S02V32 using service offering bm512SO2 (host tag 'large2') result > in host with hosttag 'large2' - correct > 6. deploy S02secondV34 using service offering bm512SO2 (host tag 'large2') > result in host with hosttag 'large3' - BUG > 7. destroy S02V32. host with hosttag 'large2' is available resource. > deploy S01V31 using service offering bm512S01 (host tag 'large') result in > host with hosttag 'large2' - BUG > conclusion: VM deployment using host tag FAIL. VM deployment uses > available host only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-3201) Mesos bash script to install and configure mesos cluster
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen closed CLOUDSTACK-3201. -- Resolution: Won't Fix > Mesos bash script to install and configure mesos cluster > > > Key: CLOUDSTACK-3201 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3201 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Dharmesh Kakadia >Assignee: Dharmesh Kakadia > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6114) GSoC: Create config management recipes to install CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6114. Resolution: Fixed > GSoC: Create config management recipes to install CloudStack > > > Key: CLOUDSTACK-6114 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6114 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: sebastien goasguen >Assignee: Ian Duffy > Labels: gsoc2014 > > To ease deployment of CloudStack we need to develop a set of recipes for all > the configuration management systems. A few already exists using Chef, Puppet > and Ansible. > This project will do an inventory of existing recipes available on-line, > coalesce them into a coherent set and write missing recipes. > The student will need to learn configuration management with at least one > tool (chef, puppet, ansible, salt..etc) and will develop recipes using > Vagrant. > The outcome will be a fully functional devcloud (cloudstack sandbox) with > mutiple recipes. CloudStack will be deployable in a sanbox or in a > multi-machine environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-1778) GSoC: Create a bootstrap based GUI for CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen closed CLOUDSTACK-1778. -- Resolution: Won't Fix > GSoC: Create a bootstrap based GUI for CloudStack > - > > Key: CLOUDSTACK-1778 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1778 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: sebastien goasguen >Assignee: Shiva Teja Reddy > Labels: gsoc2013 > Fix For: Future > > > Apache CloudStack has a very efficient web based UI, however all UI actions > correspond to API calls. The Web UI was meant has a demo to show case what > can be done with the API. In this project, the student would create a new > WebUI using the Twitter BootStrap javascript framework and probably a python > web framework like flask. This would result in a standalone web UI that > anyone could use. > Language: javascript, python > Protocols: http(s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-5125) [doc] Release Note Known Issues, Fixed Issues, and New features
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-5125. Resolution: Fixed > [doc] Release Note Known Issues, Fixed Issues, and New features > --- > > Key: CLOUDSTACK-5125 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5125 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Radhika Nair >Assignee: Radhika Nair > Fix For: Future > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8249) Dockerize CloudStack deployment
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-8249. Resolution: Fixed > Dockerize CloudStack deployment > --- > > Key: CLOUDSTACK-8249 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8249 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Environment: linux, python, docker, sys admin knowledge >Reporter: sebastien goasguen >Assignee: Pierre-Luc Dion > Labels: gsoc2015 > > CloudStack like any IaaS can be daunting to install. > I propose to Dockerize the entire deployment process. There is already a few > docker images for the simulator. The project will consist of two steps: > 1-Dockerize the mgt server, including separate container for the MySQl DB and > the usage server. > 2-Dockerize the agent (assuming KVM ). Potentially even run KVM with Docker > to contain everything. > 3-Setup a self discovery mechanism with tools like register, confd, or etcd. > 4-Automatically configure CloudStack based on self-registered services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6197) GsoC: Improve GCE and EC2 python bridges to CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6197. Resolution: Fixed fixed through donation of ec2stack and gstack GsoC: Improve GCE and EC2 python bridges to CloudStack -- Key: CLOUDSTACK-6197 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6197 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: sebastien goasguen Labels: gsoc2014 CloudStack has its own native API which is different than the de-facto standard that is EC2. Google also announced general availability for GCE. There is a need to provide an API bridge from EC2/GCE to CloudStack api. Currently two projects do this: https://github.com/NOPping/gstack https://github.com/imduffy15/ec2stack They are both python and based on Flask microframework. The project would be to extend these two code base, add APIs not currently covered and fix existing bugs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8385) Donate gstack to CloudStack project
sebastien goasguen created CLOUDSTACK-8385: -- Summary: Donate gstack to CloudStack project Key: CLOUDSTACK-8385 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8385 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: sebastien goasguen Work through IP clearance to donate gstack to CloudStack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8384) Donate ec2stack to CloudStack project
sebastien goasguen created CLOUDSTACK-8384: -- Summary: Donate ec2stack to CloudStack project Key: CLOUDSTACK-8384 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8384 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: sebastien goasguen Work trough IP clearance to donate ec2stack to CloudStack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-5897) Remove OVM in add cluster drop down list
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-5897. Resolution: Invalid not valid, since we now have ovm3 support. Remove OVM in add cluster drop down list Key: CLOUDSTACK-5897 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5897 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0, 4.3.0 Reporter: sebastien goasguen Assignee: sebastien goasguen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6015) Write Sellenium tests for the UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6015. Resolution: Won't Fix Some of the tests have been merged but we are not taking advantage of them. Ideally we should also replace the user UI. So I am closing this for now. Write Sellenium tests for the UI Key: CLOUDSTACK-6015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: sebastien goasguen Assignee: sebastien goasguen Labels: gsoc2014 Fix For: Future To increase tests coverage for CloudStack we need to write a test suite for the UI. Using Sellenium we can write these tests for multiple browsers and export everything in Python. http://docs.seleniumhq.org These will be used with the unittest and the integration tests to make CloudStack higher quality. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-829) Document EC2 Query API usage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-829. --- Resolution: Invalid I am closing this, because I am working on donating ec2stack to cloudstack and would like to remove awsapi Document EC2 Query API usage Key: CLOUDSTACK-829 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-829 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI, Doc Reporter: Chip Childers Assignee: sebastien goasguen Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-3751) Improve the launchHadoopCluster api by calling Whirr library intead of using command line
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-3751. Resolution: Invalid this was a gsoc2014 project, with unsatisfactory results Improve the launchHadoopCluster api by calling Whirr library intead of using command line - Key: CLOUDSTACK-3751 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3751 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: menghan Assignee: menghan Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-3750) Write a basic CLoudStack API to invoke whirr through the command line
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-3750. Resolution: Won't Fix unsatisfactory gsoc2014 project Write a basic CLoudStack API to invoke whirr through the command line - Key: CLOUDSTACK-3750 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3750 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: menghan Assignee: menghan Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-3749) Deploy a hadoop cluster on CloudStack using Whirr
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-3749. Resolution: Won't Fix unsatisfactory gsoc2014 project Deploy a hadoop cluster on CloudStack using Whirr - Key: CLOUDSTACK-3749 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3749 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: menghan Assignee: menghan Fix For: Future -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-814) Integrate Opennebula Marketplace
[ https://issues.apache.org/jira/browse/CLOUDSTACK-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen closed CLOUDSTACK-814. - Resolution: Won't Fix Integrate Opennebula Marketplace Key: CLOUDSTACK-814 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-814 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.1.0 Reporter: sebastien goasguen Assignee: sebastien goasguen Fix For: Future Integrate the Opennebula marketplace within the CS marketplace -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8249) Dockerize CloudStack deployment
sebastien goasguen created CLOUDSTACK-8249: -- Summary: Dockerize CloudStack deployment Key: CLOUDSTACK-8249 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8249 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Environment: linux, python, docker, sys admin knowledge Reporter: sebastien goasguen CloudStack like any IaaS can be daunting to install. I propose to Dockerize the entire deployment process. There is already a few docker images for the simulator. The project will consist of two steps: 1-Dockerize the mgt server, including separate container for the MySQl DB and the usage server. 2-Dockerize the agent (assuming KVM ). Potentially even run KVM with Docker to contain everything. 3-Setup a self discovery mechanism with tools like register, confd, or etcd. 4-Automatically configure CloudStack based on self-registered services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-5992) [Upgrade] default values of configuraiton parameters in configuration table are set NULL on fresh setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14122765#comment-14122765 ] sebastien goasguen commented on CLOUDSTACK-5992: I should this be picked up in 4.4 and 4.3 as well… it would be nice to get in the habit for nicely filling up the ticket and making sure the patch gets applied to all branches, not only master. I will pick it up in 4.3 for a potential 4.3.2 after 4.3.1 is out. if it applies to 4.4 we need it in a hot fix branch and ask Daan to merge.. thx [Upgrade] default values of configuraiton parameters in configuration table are set NULL on fresh setup Key: CLOUDSTACK-5992 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5992 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Upgrade Affects Versions: 4.3.0 Reporter: Harikrishna Patnala Assignee: Harikrishna Patnala Fix For: 4.5.0 Attachments: ConfigPropertiesComparison.html During recent Upgrade test, 1) many of the global parameters have NULL values as the default Values. 2) Component names are different in fresh and upgrade setup I attached the comparison document to this -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7404) Failed to start an instance when originating template has been deleted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-7404. Resolution: Fixed Fix Version/s: 4.3.1 Failed to start an instance when originating template has been deleted -- Key: CLOUDSTACK-7404 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7404 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Affects Versions: 4.3.0 Environment: Ubuntu 12.04, KVM, basic networking, Cloudstack 4.3.0 Reporter: Loic Lambiel Fix For: 4.3.1 Hi, I have an issue were I cannot start an instance that was previously stopped when it's originating template has been deleted. Steps to reproduce: Deploy an instance Stop the instance Delete it's originating template Wait a few minutes Start the instance This was working ok on CS 4.0.x Management server log: 2014-08-22 14:01:51,163 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) VM state transitted from :Stopped to Starting with event: StartReques tedvm's original host id: 48 new host id: null host id before state transition: null 2014-08-22 14:01:51,164 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Successfully transitioned to start state for VM[User|VM-69b4c242-fcd1 -47ec-9afa-a798c370da5d] reservation id = 7bc0e976-6ba3-4b58-aa59-1eb011c1de4e 2014-08-22 14:01:51,167 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Trying to deploy VM, vm has dcId: 1 and podId: 1 2014-08-22 14:01:51,168 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) advanceStart: DeploymentPlan is provided, using dcId:1, podId: 1, clu sterId: 1, hostId: 48, poolId: null 2014-08-22 14:01:51,168 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Deploy avoids pods: null, clusters: null, hosts: null 2014-08-22 14:01:51,177 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) VM state transitted from :Starting to Stopped with event: OperationFa iledvm's original host id: 48 new host id: null host id before state transition: null 2014-08-22 14:01:51,188 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) VM state transitted from :Stopped to Starting with event: StartReques tedvm's original host id: 48 new host id: null host id before state transition: null 2014-08-22 14:01:51,189 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Successfully transitioned to start state for VM[User|VM-69b4c242-fcd1 -47ec-9afa-a798c370da5d] reservation id = 342cb1d2-fc32-4cdf-94c6-049cf16d5509 2014-08-22 14:01:51,191 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Trying to deploy VM, vm has dcId: 1 and podId: 1 2014-08-22 14:01:51,192 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) Deploy avoids pods: null, clusters: null, hosts: null 2014-08-22 14:01:51,198 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-87:ctx-17783fe6 ctx-7479eb99) VM state transitted from :Starting to Stopped with event: OperationFa iledvm's original host id: 48 new host id: null host id before state transition: null 2014-08-22 14:01:51,210 ERROR [cloud.api.ApiAsyncJobDispatcher] (Job-Executor-87:ctx-17783fe6) Unexpected exception while executing org.apache.cloudstack.api.command.user.vm.StartVMCmd java.lang.NullPointerException at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:858) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:601) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:207) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3581) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2043) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at
[jira] [Commented] (CLOUDSTACK-7419) Document How to configure SAML SSO/SLO with CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14113906#comment-14113906 ] sebastien goasguen commented on CLOUDSTACK-7419: [~bhaisaab] yes put it in the admin guide somewhere... Document How to configure SAML SSO/SLO with CloudStack -- Key: CLOUDSTACK-7419 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7419 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Rohit Yadav Assignee: Rohit Yadav Priority: Minor Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7343) cannot create Instance from template using Swift as secondary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109137#comment-14109137 ] sebastien goasguen commented on CLOUDSTACK-7343: 4.3.0 is not concerned by this ? cannot create Instance from template using Swift as secondary storage - Key: CLOUDSTACK-7343 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7343 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0, 4.4.1 Environment: acs4.4.1-snapshot Reporter: Pierre-Luc Dion Assignee: Pierre-Luc Dion Priority: Minor Labels: swift Attachments: cloud.log_fromtemplate Fail to create Instance from Template or ISOS when using Swift as secondary storage. The templates is show as ready in Cloudstack UI, when creating the new instance the template is created on the staging NFS share at the SSVM, but the vm will still fail to create. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6892) Database HA Config prevents mgmt server from starting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103810#comment-14103810 ] sebastien goasguen commented on CLOUDSTACK-6892: [~adrianlewis] did you check that it solves your problem ? Database HA Config prevents mgmt server from starting - Key: CLOUDSTACK-6892 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6892 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: Future, 4.3.0, 4.4.0 Environment: MySQL configured for DB HA Reporter: Adrian Lewis Assignee: Hugo Trippaers Priority: Critical When configuring the database HA feature introduced in 4.3, the manangement server fails to create the DB connection due to the mysql connector jar being loaded using tomcat's common class loader but the cloud-plugin-database-mysqlha-4.3.0.jar is loaded by the webapp class loader. The cloud-plugin-database-mysqlha-4.3.0.jar needs to also be loaded from the common class loader instead of webapp class loader. Fix is to declare the cloud-plugin-database-mysqlha-4.3.0.jar under the common.loader section in /etc/cloudstack/management/catalina.properties. Only tested using a fresh install on Centos 6.5 and the public repo packages. Manual fix provided by Damoder Reddy in users mailing list: Looks like we did not change the catalina.properties while refactoring out the mysql connector part -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7193) Rebooting a VM doesn't update iptables rules
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastien goasguen updated CLOUDSTACK-7193:
---
Fix Version/s: 4.4.1
4.3.1
Rebooting a VM doesn't update iptables rules
Key: CLOUDSTACK-7193
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7193
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM
Affects Versions: 4.3.0
Environment: Ubuntu Lucid 12.04 and more recent
Reporter: Vincent Bernat
Assignee: sebastien goasguen
Fix For: 4.3.1, 4.4.1
Hi!
Rebooting a VM doesn't update the iptables rules despite the change on the
interface name. To reproduce:
1. Starts two VM
2. Stop the first one.
3. Reboot the second one. It will use the vnet device of the first one.
4. Checks that the iptables rules for the second one are still referencing
the old interface.
The defect seems to be in security_group.py. The periodic
get_rule_logs_for_vm which also handles rebooted VM fails because of the
following traceback:
{code}
2014-07-28 15:15:19,035 - 'int' object has no attribute 'isdigit'
Traceback (most recent call last):
File /usr/share/cloudstack-common/scripts/vm/network/security_group.py,
line 705, in get_rule_logs_for_vms
network_rules_for_rebooted_vm(name)
File /usr/share/cloudstack-common/scripts/vm/network/security_group.py,
line 637, in network_rules_for_rebooted_vm
[curr_domid, old_domid] = check_domid_changed(vm_name)
File /usr/share/cloudstack-common/scripts/vm/network/security_group.py,
line 619, in check_domid_changed
if (curr_domid is None) or (not curr_domid.isdigit()):
AttributeError: 'int' object has no attribute 'isdigit'
{code}
This exception is catched by some try...except.
On Ubuntu Lucid 12.04, a domain ID is an integer. This is with libvirt 0.9.8.
I also checked that this is still the case with libvirt 1.2.4.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-7193) Rebooting a VM doesn't update iptables rules
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastien goasguen reassigned CLOUDSTACK-7193:
--
Assignee: sebastien goasguen
Rebooting a VM doesn't update iptables rules
Key: CLOUDSTACK-7193
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7193
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM
Affects Versions: 4.3.0
Environment: Ubuntu Lucid 12.04 and more recent
Reporter: Vincent Bernat
Assignee: sebastien goasguen
Fix For: 4.3.1, 4.4.1
Hi!
Rebooting a VM doesn't update the iptables rules despite the change on the
interface name. To reproduce:
1. Starts two VM
2. Stop the first one.
3. Reboot the second one. It will use the vnet device of the first one.
4. Checks that the iptables rules for the second one are still referencing
the old interface.
The defect seems to be in security_group.py. The periodic
get_rule_logs_for_vm which also handles rebooted VM fails because of the
following traceback:
{code}
2014-07-28 15:15:19,035 - 'int' object has no attribute 'isdigit'
Traceback (most recent call last):
File /usr/share/cloudstack-common/scripts/vm/network/security_group.py,
line 705, in get_rule_logs_for_vms
network_rules_for_rebooted_vm(name)
File /usr/share/cloudstack-common/scripts/vm/network/security_group.py,
line 637, in network_rules_for_rebooted_vm
[curr_domid, old_domid] = check_domid_changed(vm_name)
File /usr/share/cloudstack-common/scripts/vm/network/security_group.py,
line 619, in check_domid_changed
if (curr_domid is None) or (not curr_domid.isdigit()):
AttributeError: 'int' object has no attribute 'isdigit'
{code}
This exception is catched by some try...except.
On Ubuntu Lucid 12.04, a domain ID is an integer. This is with libvirt 0.9.8.
I also checked that this is still the case with libvirt 1.2.4.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7006) Template ID is missing in ROOT volume usages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen updated CLOUDSTACK-7006: --- Fix Version/s: 4.4.1 Template ID is missing in ROOT volume usages Key: CLOUDSTACK-7006 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7006 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0 Reporter: Olivier Lemasle Assignee: Olivier Lemasle Priority: Minor Fix For: 4.3.1, 4.4.1 In previous versions of CloudStack, the template ID was recorded for ROOT volume usages, when the VM is created from a template. Since CloudStack 4.2, the template ID isn't recorded anymore, due to a regression in the EVENT_VOLUME_CREATE event publishing: In commit https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=730d04508507409065a432e2aac931225947f268, the last EVENT_VOLUME_CREATE misses the template id, that was previously set. It seems a simple copy-paste error. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7193) Rebooting a VM doesn't update iptables rules
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastien goasguen resolved CLOUDSTACK-7193.
Resolution: Fixed
Rebooting a VM doesn't update iptables rules
Key: CLOUDSTACK-7193
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7193
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM
Affects Versions: 4.3.0
Environment: Ubuntu Lucid 12.04 and more recent
Reporter: Vincent Bernat
Assignee: sebastien goasguen
Fix For: 4.3.1, 4.4.1
Hi!
Rebooting a VM doesn't update the iptables rules despite the change on the
interface name. To reproduce:
1. Starts two VM
2. Stop the first one.
3. Reboot the second one. It will use the vnet device of the first one.
4. Checks that the iptables rules for the second one are still referencing
the old interface.
The defect seems to be in security_group.py. The periodic
get_rule_logs_for_vm which also handles rebooted VM fails because of the
following traceback:
{code}
2014-07-28 15:15:19,035 - 'int' object has no attribute 'isdigit'
Traceback (most recent call last):
File /usr/share/cloudstack-common/scripts/vm/network/security_group.py,
line 705, in get_rule_logs_for_vms
network_rules_for_rebooted_vm(name)
File /usr/share/cloudstack-common/scripts/vm/network/security_group.py,
line 637, in network_rules_for_rebooted_vm
[curr_domid, old_domid] = check_domid_changed(vm_name)
File /usr/share/cloudstack-common/scripts/vm/network/security_group.py,
line 619, in check_domid_changed
if (curr_domid is None) or (not curr_domid.isdigit()):
AttributeError: 'int' object has no attribute 'isdigit'
{code}
This exception is catched by some try...except.
On Ubuntu Lucid 12.04, a domain ID is an integer. This is with libvirt 0.9.8.
I also checked that this is still the case with libvirt 1.2.4.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-1302) Add per storage setting for cache=none/writeback/writethrough options for VMs on KVM hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14062207#comment-14062207 ] sebastien goasguen commented on CLOUDSTACK-1302: does not look like this was put in 4.4, so I am adding 4.5 has release having the fix. Should we consider putting this in 4.4.1 ? Add per storage setting for cache=none/writeback/writethrough options for VMs on KVM hypervisor - Key: CLOUDSTACK-1302 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1302 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.0.0 Environment: Ubuntu 12.04.2 Host, KVM hypervisor Reporter: Jason Villalta Assignee: Wido den Hollander Priority: Minor Fix For: 4.4.0, 4.5.0 Version 4.0.0 of Cloudstack has a hard coded value of cache=none for virtual machines deployed. This causes conflict with filesystems mounted with fuse such as ZFS, GlusterFs and CEPH as fuse does not support directio with these file systems. When starting VMs libvirt throws an error could not open disk image disk Invalid argument Changing the cache= setting to writethough or writeback solves this problem but there currently is no way to set this. Ideally this would get set on a per datastore basis. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-1302) Add per storage setting for cache=none/writeback/writethrough options for VMs on KVM hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen updated CLOUDSTACK-1302: --- Fix Version/s: 4.5.0 Add per storage setting for cache=none/writeback/writethrough options for VMs on KVM hypervisor - Key: CLOUDSTACK-1302 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1302 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.0.0 Environment: Ubuntu 12.04.2 Host, KVM hypervisor Reporter: Jason Villalta Assignee: Wido den Hollander Priority: Minor Fix For: 4.4.0, 4.5.0 Version 4.0.0 of Cloudstack has a hard coded value of cache=none for virtual machines deployed. This causes conflict with filesystems mounted with fuse such as ZFS, GlusterFs and CEPH as fuse does not support directio with these file systems. When starting VMs libvirt throws an error could not open disk image disk Invalid argument Changing the cache= setting to writethough or writeback solves this problem but there currently is no way to set this. Ideally this would get set on a per datastore basis. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (CLOUDSTACK-1302) Add per storage setting for cache=none/writeback/writethrough options for VMs on KVM hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen reopened CLOUDSTACK-1302: Can this be applied to 4.3.1 or 4.4.1 ? Add per storage setting for cache=none/writeback/writethrough options for VMs on KVM hypervisor - Key: CLOUDSTACK-1302 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1302 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.0.0 Environment: Ubuntu 12.04.2 Host, KVM hypervisor Reporter: Jason Villalta Assignee: Wido den Hollander Priority: Minor Fix For: 4.4.0, 4.5.0 Version 4.0.0 of Cloudstack has a hard coded value of cache=none for virtual machines deployed. This causes conflict with filesystems mounted with fuse such as ZFS, GlusterFs and CEPH as fuse does not support directio with these file systems. When starting VMs libvirt throws an error could not open disk image disk Invalid argument Changing the cache= setting to writethough or writeback solves this problem but there currently is no way to set this. Ideally this would get set on a per datastore basis. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4611) [Ubuntu] ebtables-save command not exist on Ubuntu 12.04
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14060405#comment-14060405 ] sebastien goasguen commented on CLOUDSTACK-4611: [~weizhou] any update on this, can this be fixed on 12.04 ? I think ebtables-save is now available on 14.04 . [Ubuntu] ebtables-save command not exist on Ubuntu 12.04 Key: CLOUDSTACK-4611 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4611 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Wei Zhou Priority: Minor /usr/share/cloudstack-common/scripts/vm/network/security_group.py use ebtables-save in cleanup_rules(). However, ebtables-save command exists on CentOS/RHEL, but not exist on Ubuntu 12.04 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-1492) Missing Guide: Allocator Implementation Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-1492. Resolution: Fixed Missing Guide: Allocator Implementation Guide - Key: CLOUDSTACK-1492 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1492 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.0.0, 4.1.0, 4.2.0 Reporter: Joe Brockmeier Fix For: Future We seem to be missing the CloudStack Allocator Implementation Guide. It looks like this doc was never carried over when CloudStack was donated to Apache. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-1492) Missing Guide: Allocator Implementation Guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14060598#comment-14060598 ] sebastien goasguen commented on CLOUDSTACK-1492: Allocator guide is in the new docs at http://docs.cloudstack.apache.org/en/master/alloc.html closing this Missing Guide: Allocator Implementation Guide - Key: CLOUDSTACK-1492 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1492 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.0.0, 4.1.0, 4.2.0 Reporter: Joe Brockmeier Fix For: Future We seem to be missing the CloudStack Allocator Implementation Guide. It looks like this doc was never carried over when CloudStack was donated to Apache. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-1814) Document LXC Support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen reassigned CLOUDSTACK-1814: -- Assignee: sebastien goasguen Document LXC Support Key: CLOUDSTACK-1814 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1814 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Jessica Tomechak Assignee: sebastien goasguen Need to add a new section at the same level as KVM, VMware, etc. Also update all sections where we list the supported hypervisors, where we list hypervisor choices in dropdowns in the UI, etc. One approach might be to search docs for the terms KVM and hypervisor to find likely spots for adding LXC text. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-1814) Document LXC Support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-1814. Resolution: Fixed Document LXC Support Key: CLOUDSTACK-1814 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1814 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Jessica Tomechak Assignee: sebastien goasguen Need to add a new section at the same level as KVM, VMware, etc. Also update all sections where we list the supported hypervisors, where we list hypervisor choices in dropdowns in the UI, etc. One approach might be to search docs for the terms KVM and hypervisor to find likely spots for adding LXC text. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5943) [doc] Palo Alto Firewall
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-5943. Resolution: Fixed committed to docs by will stevens [doc] Palo Alto Firewall Key: CLOUDSTACK-5943 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5943 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-1409) Add Troubleshooting documentation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-1409. Resolution: Fixed it's in the docs at http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/troubleshooting.html Add Troubleshooting documentation - Key: CLOUDSTACK-1409 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1409 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.0.1 Reporter: Nik Martin Labels: documentation Fix For: Future Attachments: Troubleshooting.docx The cloudstack admin guide has little to no documentation for troubleshooting and maintenance of cloudstack: log files, how to replace a host, how to replace a controller, etc. We are going through the different failure scenarios in a production cloud, and the very first one, a management controller failure/replacement, is not documented anywhere. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-1814) Document LXC Support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14060647#comment-14060647 ] sebastien goasguen commented on CLOUDSTACK-1814: This is in the docs http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/hypervisor/lxc.html Document LXC Support Key: CLOUDSTACK-1814 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1814 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Jessica Tomechak Need to add a new section at the same level as KVM, VMware, etc. Also update all sections where we list the supported hypervisors, where we list hypervisor choices in dropdowns in the UI, etc. One approach might be to search docs for the terms KVM and hypervisor to find likely spots for adding LXC text. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-1919) Runbooks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-1919. Resolution: Fixed Closing this as too old and too generic Runbooks Key: CLOUDSTACK-1919 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1919 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Jessica Tomechak The RS [RightScale] runbooks are good stuff - we should seriously consider producing CS-specific content like that. (Kevin Kluge) On 03/02/2012 01:27 PM, Chiradeep Vittal wrote: Those are useful /tools. /I am more interested in the /content. / Running a cloud is a combination of operating cloudstack (stop / start / add host / delete host/ devices / storage) + operating the storage + operating the network + operating the hypervisor + ancilliary items like the SQL server database. It is clear for instance that the requisite checks were not done at [customer] before adding hosts to the cluster (check CPU level, driver patch levels, firmware upgrades), nor were they monitoring cloudstack for warnings about filling up storage or monitoring the XS hotfix mailblast. The Run Book for the cloud will contain content like this and solutions for when they receive alerts about storage filling up or how to recover corrupt vhds, how to periodically back up primary storage, etc. How to transfer VMs between failure domains when a particular failure domain has failed. References to other runbooks such as How to backup and restore MySQL. Monitor CS server and the underlying hardware with Nagios etc. Host maintenance procedures, storage maintenance procedures. In addition, there needs to be a reference architecture for deploying a cloud (define your failure domains, plan for capacity based on service offerings, calculate IOPs requirements, network bandwidth, switch capacity, core router capacity, ip address planning – public and private). Finally, [before a user sets up a cloud, they should evaluate whether they are ready]. Do they have change management procedures? Do they have a CMDB? Do they have document problem management procedures? Let me just throw ITIL in there. I agree - honestly the complexity of what IaaS is incredible. I'd go a step further in [the user] evaluation and say: * Do they have config management * Do they have automated provisioning (esp for hypervisors) - can they get a new hypervisor up in EXACTLY the same configuration as the last one, down to network bonding without any manual intervention? * Do they have a monitoring system in place - and is it or can it be made capable of monitoring cloudstack. [Need to define the baseline of what the user should be monitoring] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-1601) Document how to get help with CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen updated CLOUDSTACK-1601: --- Due Date: 18/Jul/14 Assignee: sebastien goasguen Document how to get help with CloudStack Key: CLOUDSTACK-1601 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1601 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.0.0, 4.1.0 Reporter: Jessica Tomechak Assignee: sebastien goasguen Priority: Minor The documentation is lacking a section like Getting Help which would tell people about the mailing lists, blogs, forums, and all the ways they can get more information than the documentation provides. This section should be included at the top of every book: Install, Admin, Developer's, Release Notes, and any others. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-381) Install Guide: Section 2.5: Notes that you can skip secondary storage if you are using local disks.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen updated CLOUDSTACK-381: -- Assignee: sebastien goasguen Install Guide: Section 2.5: Notes that you can skip secondary storage if you are using local disks. --- Key: CLOUDSTACK-381 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-381 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: pre-4.0.0 Reporter: Chip Childers Assignee: sebastien goasguen Fix For: Future Install Guide: Section 2.5: Notes that you can skip secondary storage if you are using local disks. I'm not sure this is the case. I thought local disk was only for primary storage. We should also reword that section to talk about local storage as an option more generally... since it's now a feature that can be enabled. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-4692) Release notes refer to componentsContext.xml instead of componentContext.xml
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-4692. Resolution: Fixed Fixed in latest RTD docs https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs-rn.git;h=8d4d51f https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs-rn.git;h=2ae743f Release notes refer to componentsContext.xml instead of componentContext.xml Key: CLOUDSTACK-4692 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4692 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Demetrius Tsitrelis Assignee: Travis Graham Attachments: Release_Notes.patch In several sections of the Release Notes (https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=docs/en-US/Release_Notes.xml), the document mentions modifying the componentsContext.xml to make changes in how CloudStack handles authentication. There appears to be an extra 's' in that filename as only componentContext.xml(.in) at https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=client/tomcatconf/componentContext.xml.in exists in the source tree. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7038) MySQL Client RPMs not a dependency in CS Packages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052458#comment-14052458 ] sebastien goasguen commented on CLOUDSTACK-7038: [~adrianlewis] do you have the logs that show the error ? MySQL Client RPMs not a dependency in CS Packages - Key: CLOUDSTACK-7038 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7038 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: Future, 4.3.0, 4.4.0 Environment: Centos or RPM-based distro where MySQL installed on separate server Reporter: Adrian Lewis Priority: Minor Perhaps simple enough to fix in docs but if anyone is installing from packages on Centos, the 'mysql' client package is not installed as a dependency which it should be. Likely not picked up in testing as those installing the 'mysql-server' package will automatically get the client part but for those using MySQL on a separate server, the management server will not start. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6665) DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastien goasguen resolved CLOUDSTACK-6665.
Resolution: Fixed
Fix Version/s: 4.3.1
4.4.0
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
-
Key: CLOUDSTACK-6665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM
Affects Versions: 4.3.0, 4.4.0
Reporter: Remi Bergsma
Priority: Critical
Fix For: 4.4.0, 4.3.1
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
How to reproduce:
- create vpc network with small prefix
- create as many vm’s until all ip address space is consumed
- delete one vm
- now create a vm again: there should be an ip address freed
- it does not work though. Error on router:
/var/log/dnsmasq.log:May 13 12:53:16 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:00:0d:00:b6 no address available
How to reproduce #2:
- create a vm with static ip
- destroy it
- create vm with same static ip: this ip should be free again
This does not work either:
/var/log/dnsmasq.log:May 13 13:59:41 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:69:06:00:c1 no address available
Cause:
edithosts.sh is supposed to clean up addresses.
edithosts.sh line 101:
dhcp_release eth0 $ipv4 $(grep $ipv4 $DHCP_LEASES | awk '{print $2}')
/dev/null 21
But it doesn’t work, because eth0 is the link local address on VPC routers.
We should make the interface variable on VPC routers.
It does work fine on redundant routers, for example. Because eth0 is the
actual guest network.
CloudStack reports to the user: Insufficient capacity.
Manual work-around:
Run on the router:
dhcp_release eth3 02:00:69:06:00:c1 10.75.16.8
Replace eth3 with the correct interface.
It logs:
/var/log/messages-20140419:May 13 13:38:29 r-4197-VM cloud: edithosts:
released 10.75.16.8
It now works!
This an annoying bug for users that use static ip’s in their networks. Also
users that deploy a lot of test vm’s in the same network are impacted. Let’s
fix it :-)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6665) DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14049955#comment-14049955
]
sebastien goasguen commented on CLOUDSTACK-6665:
Let's close it, I just committed it to 4.3.1 and talking with Daan this is in
master and 4.4
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
-
Key: CLOUDSTACK-6665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM
Affects Versions: 4.3.0, 4.4.0
Reporter: Remi Bergsma
Priority: Critical
Fix For: 4.4.0, 4.3.1
DHCP does not release ip addresses properly on VPC routers (edithosts.sh)
How to reproduce:
- create vpc network with small prefix
- create as many vm’s until all ip address space is consumed
- delete one vm
- now create a vm again: there should be an ip address freed
- it does not work though. Error on router:
/var/log/dnsmasq.log:May 13 12:53:16 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:00:0d:00:b6 no address available
How to reproduce #2:
- create a vm with static ip
- destroy it
- create vm with same static ip: this ip should be free again
This does not work either:
/var/log/dnsmasq.log:May 13 13:59:41 dnsmasq-dhcp[32100]: DHCPDISCOVER(eth3)
02:00:69:06:00:c1 no address available
Cause:
edithosts.sh is supposed to clean up addresses.
edithosts.sh line 101:
dhcp_release eth0 $ipv4 $(grep $ipv4 $DHCP_LEASES | awk '{print $2}')
/dev/null 21
But it doesn’t work, because eth0 is the link local address on VPC routers.
We should make the interface variable on VPC routers.
It does work fine on redundant routers, for example. Because eth0 is the
actual guest network.
CloudStack reports to the user: Insufficient capacity.
Manual work-around:
Run on the router:
dhcp_release eth3 02:00:69:06:00:c1 10.75.16.8
Replace eth3 with the correct interface.
It logs:
/var/log/messages-20140419:May 13 13:38:29 r-4197-VM cloud: edithosts:
released 10.75.16.8
It now works!
This an annoying bug for users that use static ip’s in their networks. Also
users that deploy a lot of test vm’s in the same network are impacted. Let’s
fix it :-)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6892) Database HA Config prevents mgmt server from starting
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14050025#comment-14050025 ] sebastien goasguen commented on CLOUDSTACK-6892: [~adrianlewis] what's your OS and hypervisor ? Database HA Config prevents mgmt server from starting - Key: CLOUDSTACK-6892 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6892 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, Management Server Affects Versions: Future, 4.3.0, 4.4.0 Environment: MySQL configured for DB HA Reporter: Adrian Lewis Assignee: Hugo Trippaers Priority: Critical When configuring the database HA feature introduced in 4.3, the manangement server fails to create the DB connection due to the mysql connector jar being loaded using tomcat's common class loader but the cloud-plugin-database-mysqlha-4.3.0.jar is loaded by the webapp class loader. The cloud-plugin-database-mysqlha-4.3.0.jar needs to also be loaded from the common class loader instead of webapp class loader. Fix is to declare the cloud-plugin-database-mysqlha-4.3.0.jar under the common.loader section in /etc/cloudstack/management/catalina.properties. Only tested using a fresh install on Centos 6.5 and the public repo packages. Manual fix provided by Damoder Reddy in users mailing list: Looks like we did not change the catalina.properties while refactoring out the mysql connector part -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-7006) Template ID is missing in ROOT volume usages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen closed CLOUDSTACK-7006. -- Resolution: Fixed Fix Version/s: 4.3.1 Template ID is missing in ROOT volume usages Key: CLOUDSTACK-7006 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7006 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0 Reporter: Olivier Lemasle Assignee: Olivier Lemasle Priority: Minor Fix For: 4.3.1 In previous versions of CloudStack, the template ID was recorded for ROOT volume usages, when the VM is created from a template. Since CloudStack 4.2, the template ID isn't recorded anymore, due to a regression in the EVENT_VOLUME_CREATE event publishing: In commit https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=730d04508507409065a432e2aac931225947f268, the last EVENT_VOLUME_CREATE misses the template id, that was previously set. It seems a simple copy-paste error. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6297) Cloudstack Fails to Launch on Ubuntu missing MySQL Driver
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048047#comment-14048047 ] sebastien goasguen commented on CLOUDSTACK-6297: I believe this is resolved in the latest 4.3 branch. I was able to setup cloudstack on ubuntu 14.04. Cloudstack Fails to Launch on Ubuntu missing MySQL Driver - Key: CLOUDSTACK-6297 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6297 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Environment: Ubuntu Server 13.10 Reporter: Joshua Rogers Priority: Critical Fix For: 4.3.1 On Ubuntu Server 13.10, installing Cloudstack 4.3 as specified in the documentation does not produce a runnable system. Cloudstack-management dies shortly after it starts with a stack trace indicating that it can't find the MySQL driver (trace listed below.) This continues to occur after running apt-get install libmysql-java cp /usr/share/java/mysql-connector-java-5.1.25.jar /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/ reboot --- Stack Trace --- 2014-03-27 20:53:11,112 INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false 2014-03-27 20:53:11,186 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to get a new db connection java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/cloud?autoReconnect=trueprepStmtCacheSize=517cachePrepStmts=true at java.sql.DriverManager.getConnection(DriverManager.java:635) at java.sql.DriverManager.getConnection(DriverManager.java:195) at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106) at com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:204) at com.cloud.utils.db.Merovingian2.init(Merovingian2.java:68) at com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:80) at com.cloud.server.LockMasterListener.init(LockMasterListener.java:33) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:534) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1045) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:949) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) at
[jira] [Resolved] (CLOUDSTACK-6297) Cloudstack Fails to Launch on Ubuntu missing MySQL Driver
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6297. Resolution: Fixed Fix Version/s: 4.3.1 Cloudstack Fails to Launch on Ubuntu missing MySQL Driver - Key: CLOUDSTACK-6297 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6297 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Environment: Ubuntu Server 13.10 Reporter: Joshua Rogers Priority: Critical Fix For: 4.3.1 On Ubuntu Server 13.10, installing Cloudstack 4.3 as specified in the documentation does not produce a runnable system. Cloudstack-management dies shortly after it starts with a stack trace indicating that it can't find the MySQL driver (trace listed below.) This continues to occur after running apt-get install libmysql-java cp /usr/share/java/mysql-connector-java-5.1.25.jar /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/ reboot --- Stack Trace --- 2014-03-27 20:53:11,112 INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false 2014-03-27 20:53:11,186 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to get a new db connection java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/cloud?autoReconnect=trueprepStmtCacheSize=517cachePrepStmts=true at java.sql.DriverManager.getConnection(DriverManager.java:635) at java.sql.DriverManager.getConnection(DriverManager.java:195) at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106) at com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:204) at com.cloud.utils.db.Merovingian2.init(Merovingian2.java:68) at com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:80) at com.cloud.server.LockMasterListener.init(LockMasterListener.java:33) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:534) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1045) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:949) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:141)
[jira] [Commented] (CLOUDSTACK-5853) cannot deploy vm with differing service storage tag and data disk storage tag
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048057#comment-14048057 ] sebastien goasguen commented on CLOUDSTACK-5853: Can someone update this and close the ticket or not ? [~prachidamle] ? thx cannot deploy vm with differing service storage tag and data disk storage tag - Key: CLOUDSTACK-5853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5853 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, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Priority: Critical Fix For: 4.4.0 Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6209) Building noredist packages for ubuntu doesn't include vmware jars in systemvm.iso
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6209. Resolution: Fixed wiki doc issue Building noredist packages for ubuntu doesn't include vmware jars in systemvm.iso - Key: CLOUDSTACK-6209 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6209 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Packaging, SystemVM Affects Versions: 4.2.0, 4.3.0, 4.4.0 Environment: Ubuntu 12.04.4 LTS Reporter: David Bierce Building Debian/Ubuntu packages with support for VMware completes but doesn't include the VMware jars in the Systemvm.iso. Building using the guide here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingDEBpackages With the actual options of: mvn clean install -P deps -Dnoredist; export ACS_BUILD_OPTS=-Dnoredist; dpkg-buildpackage Building with the follow options creates a usable build with correct systevm.iso: mvn install -P deps -Dnoredist -Dnonoss; export ACS_BUILD_OPTS=-Dnoredist -Dnonoss; dpkg-buildpackage -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6209) Building noredist packages for ubuntu doesn't include vmware jars in systemvm.iso
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048076#comment-14048076 ] sebastien goasguen commented on CLOUDSTACK-6209: Made a note on the wiki Building noredist packages for ubuntu doesn't include vmware jars in systemvm.iso - Key: CLOUDSTACK-6209 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6209 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Packaging, SystemVM Affects Versions: 4.2.0, 4.3.0, 4.4.0 Environment: Ubuntu 12.04.4 LTS Reporter: David Bierce Building Debian/Ubuntu packages with support for VMware completes but doesn't include the VMware jars in the Systemvm.iso. Building using the guide here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingDEBpackages With the actual options of: mvn clean install -P deps -Dnoredist; export ACS_BUILD_OPTS=-Dnoredist; dpkg-buildpackage Building with the follow options creates a usable build with correct systevm.iso: mvn install -P deps -Dnoredist -Dnonoss; export ACS_BUILD_OPTS=-Dnoredist -Dnonoss; dpkg-buildpackage -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6634) DOC: update the ldap section of the admin guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048090#comment-14048090 ] sebastien goasguen commented on CLOUDSTACK-6634: [~rajanik] Care to submit a pull request ? I know you can :) DOC: update the ldap section of the admin guide --- Key: CLOUDSTACK-6634 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6634 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Rajani Karuturi Labels: ldap Fix For: 4.4.0 http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.3/accounts.html#using-an-ldap-server-for-user-authentication there are changes/enhancements in the way ldap server is configured since 4.3 documentation needs to be updated with the latest info. https://cwiki.apache.org/confluence/display/CLOUDSTACK/LDAP+user+provisioning -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6927) Security group python script has several issues
sebastien goasguen created CLOUDSTACK-6927: -- Summary: Security group python script has several issues Key: CLOUDSTACK-6927 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6927 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.4.0, 4.3.1 Reporter: sebastien goasguen Fix For: 4.3.1 -virtual router is not cleaned up properly from iptables -routes are not cleaned up properly if needed -not using python list to store results of virsh list. -there can be duplicates in cleanup list - -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5926) [Doc] Create 4.3 Release Notes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen closed CLOUDSTACK-5926. -- Resolution: Fixed Fix Version/s: (was: 4.4.0) 4.3.0 [Doc] Create 4.3 Release Notes -- Key: CLOUDSTACK-5926 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5926 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6419) Develop an OCCI interface
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6419. Resolution: Fixed Assignee: sebastien goasguen Develop an OCCI interface - Key: CLOUDSTACK-6419 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6419 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: sebastien goasguen Assignee: sebastien goasguen OCCI is a standard for cloud computing from the Open Grid Forum (OGF). Here is the background blog: http://buildacloud.org/blog/296-occi-interface-to-cloudstack.html Which was done with early work at: https://github.com/isaacchiang/rOCCI-server this was submitted as a pull request to: https://github.com/gwdg/rOCCI-server/pull/72 Since then the rOCCI-server has been re-architected and the OCCI driver for cloudstack needs to be refactored. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-2391) A new user guide for ACS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-2391. Resolution: Won't Fix A new user guide for ACS Key: CLOUDSTACK-2391 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2391 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: sebastien goasguen Assignee: sebastien goasguen -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6419) Develop an OCCI interface
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006017#comment-14006017 ] sebastien goasguen commented on CLOUDSTACK-6419: done: http://java.dzone.com/articles/occi-interface-cloudstack Develop an OCCI interface - Key: CLOUDSTACK-6419 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6419 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: sebastien goasguen OCCI is a standard for cloud computing from the Open Grid Forum (OGF). Here is the background blog: http://buildacloud.org/blog/296-occi-interface-to-cloudstack.html Which was done with early work at: https://github.com/isaacchiang/rOCCI-server this was submitted as a pull request to: https://github.com/gwdg/rOCCI-server/pull/72 Since then the rOCCI-server has been re-architected and the OCCI driver for cloudstack needs to be refactored. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6419) Develop an OCCI interface
sebastien goasguen created CLOUDSTACK-6419: -- Summary: Develop an OCCI interface Key: CLOUDSTACK-6419 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6419 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: sebastien goasguen OCCI is a standard for cloud computing from the Open Grid Forum (OGF). Here is the background blog: http://buildacloud.org/blog/296-occi-interface-to-cloudstack.html Which was done with early work at: https://github.com/isaacchiang/rOCCI-server this was submitted as a pull request to: https://github.com/gwdg/rOCCI-server/pull/72 Since then the rOCCI-server has been re-architected and the OCCI driver for cloudstack needs to be refactored. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6299) GetVMPassword decypher instructions are wrong
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6299. Resolution: Fixed Fix Version/s: 4.3.1 4.4.0 All fixed, thanks for the bug GetVMPassword decypher instructions are wrong - Key: CLOUDSTACK-6299 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6299 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Antoine Coetsier Assignee: sebastien goasguen Priority: Trivial Labels: documentation Fix For: 4.4.0, 4.3.1 The procedure described in the Wiki at https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34014652 is incorrect. The first openssl conversion step will give you an empty file. The correct procedure is: openssl enc -base64 -in encryptedpassword -out binarytext -d -A openssl rsautl -decrypt -in binarytext -out plaintext -inkey private.pem Please correct the wiki page and add detail in the API doc to the base64 format of the API getVMpassword result. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6299) GetVMPassword decypher instructions are wrong
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen reassigned CLOUDSTACK-6299: -- Assignee: sebastien goasguen GetVMPassword decypher instructions are wrong - Key: CLOUDSTACK-6299 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6299 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.3.0 Reporter: Antoine Coetsier Assignee: sebastien goasguen Priority: Trivial Labels: documentation The procedure described in the Wiki at https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34014652 is incorrect. The first openssl conversion step will give you an empty file. The correct procedure is: openssl enc -base64 -in encryptedpassword -out binarytext -d -A openssl rsautl -decrypt -in binarytext -out plaintext -inkey private.pem Please correct the wiki page and add detail in the API doc to the base64 format of the API getVMpassword result. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5954) update-ssl.png missing from docs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-5954. Resolution: Fixed Fix Version/s: 4.3.0 update-ssl.png missing from docs Key: CLOUDSTACK-5954 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5954 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: sebastien goasguen Fix For: 4.3.0 Attachments: update-ssl.png there does not seem to be a update-ssl.png in en-US/images -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6114) GSoC: Create config management recipes to install CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen updated CLOUDSTACK-6114: --- Summary: GSoC: Create config management recipes to install CloudStack (was: Create config management recipes to install CloudStack) GSoC: Create config management recipes to install CloudStack Key: CLOUDSTACK-6114 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6114 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: sebastien goasguen Labels: gsoc2014 To ease deployment of CloudStack we need to develop a set of recipes for all the configuration management systems. A few already exists using Chef, Puppet and Ansible. This project will do an inventory of existing recipes available on-line, coalesce them into a coherent set and write missing recipes. The student will need to learn configuration management with at least one tool (chef, puppet, ansible, salt..etc) and will develop recipes using Vagrant. The outcome will be a fully functional devcloud (cloudstack sandbox) with mutiple recipes. CloudStack will be deployable in a sanbox or in a multi-machine environment. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-1725) publican update_pot might overwrite license headers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-1725. Resolution: Invalid Marking this as invalid, since we are moving to readthedocs. publican won't be used anymore and we are moving to sphinx publican update_pot might overwrite license headers Key: CLOUDSTACK-1725 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1725 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: sebastien goasguen Assignee: sebastien goasguen Priority: Minor Fix For: 4.3.0 When adding documentation files and updating the list of pot files. publican update_pot does not keep the license header. We need to check this. Also the .tx/config file may be overwritten... This is just a sanity to check to avoid re-committing things and breaking the RAT report. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-1784) GSoC: Integration project to deploy and use Mesos on a CloudStack based cloud
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen updated CLOUDSTACK-1784: --- Labels: gsoc2013 gsoc2014 (was: gsoc2013) adding this to gsoc2014 list since this was not completed in 2013 GSoC: Integration project to deploy and use Mesos on a CloudStack based cloud - Key: CLOUDSTACK-1784 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1784 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: Future Reporter: sebastien goasguen Assignee: Dharmesh Kakadia Labels: gsoc2013, gsoc2014 In this project student(s), will deploy a CloudStack based cloud and use mesos to schedule tasks on the resulting virtual clusters. They will show how to run traditional parallel application with MPI and big data application with Hadoop/Map Reduce. This is primarily an integration project that will result in a proof of concept. Bootstrap code will most likely be created to dynamically provision the virtual clusters and configure mesos on the resulting nodes. We envision a set of puppet or chef recipes and some Python boostrapping code. Potentially this could be an extension of the apache incubating Provisionr project Language: Java, bash, python Knowledge: system administration -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-1782) GSoC: Improve CloudStack support in apache whirr and incubator-provisioner to created hadoop clusters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen closed CLOUDSTACK-1782. -- Resolution: Fixed provisioner was dropped, and whirr works. GSoC: Improve CloudStack support in apache whirr and incubator-provisioner to created hadoop clusters - Key: CLOUDSTACK-1782 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1782 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: sebastien goasguen Assignee: menghan Labels: gsoc2013 Fix For: Future A IaaS is used to create virtual clusters, with the interest in big data it is crucial to automate the provisioning of hadoop clusters using IaaS solutions. This project will bring together several apache projects (Top Level and in incubation) to improve CloudStack support in apache Whirr and Provisionr in order to enable provisioning of Hadoop clusters on CloudStack based clouds. Language: Java, Python Knowledge: Hadoop -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6115) GSoC: Investigate the use of TravisCI for CloudStack integration testing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13940377#comment-13940377 ] sebastien goasguen commented on CLOUDSTACK-6115: Hi Harsha, Sorry for the delay, if you are interested you only have two days to submit your proposal via google melange website. We currently use Jenkins for all our automation and integration testing. Travis CI is a new automation service originally aimed for Python but now supports Java. We can setup the cloudstack code to automatically build on Travis and run the tests. The end result would be that for every commit Travis would try to build the code and run tests that we would define. CloudStack also contains a simulator. if we could deploy the simulator in Travis on the fly, we could run the integration tests that way. One advantage would be that all tests and automation would be committed to the code in a travis configuration file, and that the builds/simulation would be triggered on every commit. Don't hesitate to join IRC and the dev@ mailing list to start joining the community. -Sebastien GSoC: Investigate the use of TravisCI for CloudStack integration testing Key: CLOUDSTACK-6115 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6115 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: sebastien goasguen Labels: gsoc2014 Integration testing is currently performed using jenkins and the CloudStack simulator. In this project the student will learn about integration testing and the marvin framework in CloudStack (written in Python). The student will also learn about TravisCI a system to perform continuous testing and integration testing. Using a github mirror, the student will setup Travis builds that will use the cloudstack simulator and run the integration tests on each commit. This is a great project to learn about CI, tests and CloudStack. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6197) GsoC: Improve GCE and EC2 python bridges to CloudStack
sebastien goasguen created CLOUDSTACK-6197: -- Summary: GsoC: Improve GCE and EC2 python bridges to CloudStack Key: CLOUDSTACK-6197 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6197 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: sebastien goasguen CloudStack has its own native API which is different than the de-facto standard that is EC2. Google also announced general availability for GCE. There is a need to provide an API bridge from EC2/GCE to CloudStack api. Currently two projects do this: https://github.com/NOPping/gstack https://github.com/imduffy15/ec2stack They are both python and based on Flask microframework. The project would be to extend these two code base, add APIs not currently covered and fix existing bugs. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6114) Create config management recipes to install CloudStack
sebastien goasguen created CLOUDSTACK-6114: -- Summary: Create config management recipes to install CloudStack Key: CLOUDSTACK-6114 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6114 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: sebastien goasguen To ease deployment of CloudStack we need to develop a set of recipes for all the configuration management systems. A few already exists using Chef, Puppet and Ansible. This project will do an inventory of existing recipes available on-line, coalesce them into a coherent set and write missing recipes. The student will need to learn configuration management with at least one tool (chef, puppet, ansible, salt..etc) and will develop recipes using Vagrant. The outcome will be a fully functional devcloud (cloudstack sandbox) with mutiple recipes. CloudStack will be deployable in a sanbox or in a multi-machine environment. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-6115) GSoC: Investigate the use of TravisCI for CloudStack integration testing
sebastien goasguen created CLOUDSTACK-6115: -- Summary: GSoC: Investigate the use of TravisCI for CloudStack integration testing Key: CLOUDSTACK-6115 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6115 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: sebastien goasguen Integration testing is currently performed using jenkins and the CloudStack simulator. In this project the student will learn about integration testing and the marvin framework in CloudStack (written in Python). The student will also learn about TravisCI a system to perform continuous testing and integration testing. Using a github mirror, the student will setup Travis builds that will use the cloudstack simulator and run the integration tests on each commit. This is a great project to learn about CI, tests and CloudStack. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-6015) Write Sellenium tests for the UI
sebastien goasguen created CLOUDSTACK-6015: -- Summary: Write Sellenium tests for the UI Key: CLOUDSTACK-6015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6015 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: sebastien goasguen To increase tests coverage for CloudStack we need to write a test suite for the UI. Using Sellenium we can write these tests for multiple browsers and export everything in Python. http://docs.seleniumhq.org These will be used with the unittest and the integration tests to make CloudStack higher quality. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5954) update-ssl.png missing from docs
sebastien goasguen created CLOUDSTACK-5954: -- Summary: update-ssl.png missing from docs Key: CLOUDSTACK-5954 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5954 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: sebastien goasguen there does not seem to be a update-ssl.png in en-US/images -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5897) Remove OVM in add cluster drop down list
sebastien goasguen created CLOUDSTACK-5897: -- Summary: Remove OVM in add cluster drop down list Key: CLOUDSTACK-5897 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5897 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0, 4.3.0 Reporter: sebastien goasguen Assignee: sebastien goasguen -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-4787) Allow selection of scsi controller type in vSphere
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen updated CLOUDSTACK-4787: --- Affects Version/s: 4.3.0 Issue Type: Bug (was: New Feature) Allow selection of scsi controller type in vSphere -- Key: CLOUDSTACK-4787 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4787 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, UI, VMware Affects Versions: 4.2.0, 4.3.0 Environment: vSphere 5.1 Reporter: Chris Sciarrino Priority: Blocker Fix For: Future When adding an OVA template for a vSphere environment allow the selection of the scsi controller type. Currently the instances are deployed with the the LSI Parallel controller type. This results in a blue screen on boot when attempting to deploy templates that use the LSI SAS controller. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5881) No QA running on jenkins.buildacloud.org
sebastien goasguen created CLOUDSTACK-5881: -- Summary: No QA running on jenkins.buildacloud.org Key: CLOUDSTACK-5881 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5881 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: sebastien goasguen Priority: Blocker There are no integration tests running on jenkins: http://jenkins.buildacloud.org/view/cloudstack-qa/ This means that 4.3 is untested... -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5882) UI has different fonts and font sizes
sebastien goasguen created CLOUDSTACK-5882: -- Summary: UI has different fonts and font sizes Key: CLOUDSTACK-5882 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5882 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: sebastien goasguen Priority: Blocker I am raising this as a blocker until we have at least a discussion about it. The new UI looks great but at the same time it has issues. Here is a screenshot: http://awesomescreenshot.com/0ba27oxn42 There seems to be a mix of fonts and font sizes, bold and color that makes it very distracting and not polished. I think the CSS needs to be fixed. Also in a page like the user view, the frame encapsulating the user keys is such that it truncates the keys badly. This is actually a regression from previous version: http://awesomescreenshot.com/00427oxz9f -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5864) Simulator profile broken
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastien goasguen updated CLOUDSTACK-5864:
---
Assignee: Santhosh Kumar Edukulla
Simulator profile broken
-
Key: CLOUDSTACK-5864
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5864
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: marvin
Affects Versions: 4.2.1, 4.3.0
Reporter: sebastien goasguen
Assignee: Santhosh Kumar Edukulla
Priority: Blocker
Fix For: 4.3.0
When running the simulator we use the marvin.setup profile:
mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl
:cloud-marvin integration-test
Recent argument changes in deployAndrun.py broke this profile in
tools/marvin/pom.xml
executions
execution
idpre-integration-test/id
phasepre-integration-test/phase
goals
goalexec/goal
/goals
configuration
workingDirectory${basedir}/marvin/workingDirectory
executablepython/executable
arguments
argumentdeployAndRun.py/argument
argument-c/argument
argument${resolved.userdir}/${marvin.config}/argument
argument-t/argument
argument/tmp/t.log/argument
argument-r/argument
argument/tmp/r.log/argument
argument-f/argument
argument${resolved.basedir}/marvin/testSetupSuccess.py/argument
/arguments
/configuration
/execution
/executions
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5864) Simulator profile broken
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastien goasguen resolved CLOUDSTACK-5864.
Resolution: Fixed
Fix Version/s: 4.3.0
Fixed with 00a5063107f70e8b8d9a74c9aa8d272db8a3a9f4
Simulator profile broken
-
Key: CLOUDSTACK-5864
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5864
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: marvin
Affects Versions: 4.2.1, 4.3.0
Reporter: sebastien goasguen
Assignee: Santhosh Kumar Edukulla
Priority: Blocker
Fix For: 4.3.0
When running the simulator we use the marvin.setup profile:
mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl
:cloud-marvin integration-test
Recent argument changes in deployAndrun.py broke this profile in
tools/marvin/pom.xml
executions
execution
idpre-integration-test/id
phasepre-integration-test/phase
goals
goalexec/goal
/goals
configuration
workingDirectory${basedir}/marvin/workingDirectory
executablepython/executable
arguments
argumentdeployAndRun.py/argument
argument-c/argument
argument${resolved.userdir}/${marvin.config}/argument
argument-t/argument
argument/tmp/t.log/argument
argument-r/argument
argument/tmp/r.log/argument
argument-f/argument
argument${resolved.basedir}/marvin/testSetupSuccess.py/argument
/arguments
/configuration
/execution
/executions
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5875) No templates in simulator run
sebastien goasguen created CLOUDSTACK-5875: -- Summary: No templates in simulator run Key: CLOUDSTACK-5875 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5875 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.2.1, 4.3.0 Reporter: sebastien goasguen When running the simulator and configuring a zone with marvin, there is no template available hence trying to start instances won't work. See https://reviews.apache.org/r/16856/ for additional related discussions -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5866) Remove maven profile used to configure zone
sebastien goasguen created CLOUDSTACK-5866: -- Summary: Remove maven profile used to configure zone Key: CLOUDSTACK-5866 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5866 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.3.0 Reporter: sebastien goasguen When running the simulator, you can use a maven profile to configure a zone: mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl :cloud-marvin integration-test We need to investigate removing this marvin.setup profile all together. Discuss implications and make sure nothing is using it. When removing we also need to updated documentation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5864) Simulator profile broken
sebastien goasguen created CLOUDSTACK-5864:
--
Summary: Simulator profile broken
Key: CLOUDSTACK-5864
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5864
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: marvin
Affects Versions: 4.3.0
Reporter: sebastien goasguen
Priority: Blocker
When running the simulator we use the marvin.setup profile:
mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl
:cloud-marvin integration-test
Recent argument changes in deployAndrun.py broke this profile in
tools/marvin/pom.xml
executions
execution
idpre-integration-test/id
phasepre-integration-test/phase
goals
goalexec/goal
/goals
configuration
workingDirectory${basedir}/marvin/workingDirectory
executablepython/executable
arguments
argumentdeployAndRun.py/argument
argument-c/argument
argument${resolved.userdir}/${marvin.config}/argument
argument-t/argument
argument/tmp/t.log/argument
argument-r/argument
argument/tmp/r.log/argument
argument-f/argument
argument${resolved.basedir}/marvin/testSetupSuccess.py/argument
/arguments
/configuration
/execution
/executions
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5864) Simulator profile broken
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastien goasguen updated CLOUDSTACK-5864:
---
Affects Version/s: 4.2.1
Simulator profile broken
-
Key: CLOUDSTACK-5864
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5864
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: marvin
Affects Versions: 4.2.1, 4.3.0
Reporter: sebastien goasguen
Priority: Blocker
When running the simulator we use the marvin.setup profile:
mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl
:cloud-marvin integration-test
Recent argument changes in deployAndrun.py broke this profile in
tools/marvin/pom.xml
executions
execution
idpre-integration-test/id
phasepre-integration-test/phase
goals
goalexec/goal
/goals
configuration
workingDirectory${basedir}/marvin/workingDirectory
executablepython/executable
arguments
argumentdeployAndRun.py/argument
argument-c/argument
argument${resolved.userdir}/${marvin.config}/argument
argument-t/argument
argument/tmp/t.log/argument
argument-r/argument
argument/tmp/r.log/argument
argument-f/argument
argument${resolved.basedir}/marvin/testSetupSuccess.py/argument
/arguments
/configuration
/execution
/executions
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5835) awsapi s3 Implementation not functioning
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-5835. Resolution: Won't Fix awsapi s3 Implementation not functioning Key: CLOUDSTACK-5835 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5835 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Environment: CentOS 6.3 Reporter: Alok Assignee: sebastien goasguen Steps completed to enable awsapi S3 implementation == 1) Below settings have been enabled Using Cloudstack_management UI enable.s3.api enable Amazon S3 API on CloudStack true s3.rrs.enabledenable s3 reduced redundancy storagetrue 2 Modified cloud-bridge.properties to storage.root to a valid directory. 3) restarted Cloudstack_management service. 4) Executed below command and received User registration is successful Message, cloudstack-aws-api-register --apikey=1cn1BBE9aaA1FSHij3ee6YS4orlsid-EfXaWBXMtX-BsqjtQwEj8UDANzzdQobBrGjTmKnny2sQF_GYRMNBDSA --secretkey=-guBDlSM2OC18wAK_Kj5WGnlq3P1NluChq52jBDcSudOKQ637fh17imMHETkQC5ZIjtaEKuxajos3yADGLIVwA --cert=cert.pem -- Problem Statement = Tried to access : http://localhost:7080/awsapi/rest/AmazonS3 from browser its resulting in below exception and got 500 response The endpoint reference (EPR) for the Operation not found is /awsapi/services/AmazonEC2/ and the WSA Action = null SEVERE: Allocate exception for servlet CloudBridgeS3Servlet javax.servlet.ServletException: Error initializing awsapi: null at com.cloud.bridge.service.S3RestServlet.init(S3RestServlet.java:128) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:809) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) 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:701) Jan 8, 2014 6:39:00 PM org.apache.axis2.engine.AxisEngine receive SEVERE: The endpoint reference (EPR) for the Operation not found is /awsapi/services/AmazonEC2/ and the WSA Action = null org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation not found is /awsapi/services/AmazonEC2/ and the WSA Action = null at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:89) at org.apache.axis2.engine.Phase.invoke(Phase.java:334) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:254) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160) at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135) at org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:130) at org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:825) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:271) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) Observation: I have seen below exception in catalina.out file during cloudstack-management server start-up 2014 6:11:00 PM org.apache.axis2.deployment.ModuleDeployer deploy SEVERE: The addressing-1.5.4.mar module, which is not valid, caused The module.xml file cannot be found for the module: /usr/share/cloudstack-management/webapps7080/awsapi/WEB-INF/modules/addressing-1.5.4.mar
[jira] [Commented] (CLOUDSTACK-4982) Top of dialogs cut off
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13819017#comment-13819017 ] sebastien goasguen commented on CLOUDSTACK-4982: Mike, can you enter the commit that fixed this. Is it in 4.3 now ? Looks like asfbot did not pick it up Top of dialogs cut off -- Key: CLOUDSTACK-4982 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4982 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Environment: Chrome Version 30.0.1599.101 on Mac OS X 10.8.3 Reporter: Mike Tutkowski Priority: Minor Fix For: 4.3.0 Attachments: Top of Dialog.png Please see the attached screen shot. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4982) Top of dialogs cut off
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13819021#comment-13819021 ] sebastien goasguen commented on CLOUDSTACK-4982: looks like this has been fixed in 4.3 Top of dialogs cut off -- Key: CLOUDSTACK-4982 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4982 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Environment: Chrome Version 30.0.1599.101 on Mac OS X 10.8.3 Reporter: Mike Tutkowski Priority: Minor Fix For: 4.3.0 Attachments: Top of Dialog.png Please see the attached screen shot. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-5029) cloud-bugtool isn't in release package like release notes say
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen reassigned CLOUDSTACK-5029: -- Assignee: sebastien goasguen Removed mention of cloud-bugtool in docs as the tool as was not accepted in the code base. cloud-bugtool isn't in release package like release notes say - Key: CLOUDSTACK-5029 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5029 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Environment: CentOS 6.3 x64 CloudStack 4.2.0 Reporter: gavin lee Assignee: sebastien goasguen Fix For: 4.3.0 Unlike the CS4.2 release notes say, I could not find cloud-bugtool in source tree or installed/upgrade CS4.2 platform. Further research shows it is in Citrix CloudPlatform 4.2. Since CS4.2 now was released, and CS4.2.1 won't add any new features. I guess it would be included in CS4.3. Currently the only change is remove the related info in CS4.2 release notes. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-4998) assignVirtualMachine API has wrong response string, causing Cloudmonkey to crash
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sebastien goasguen reassigned CLOUDSTACK-4998:
--
Assignee: sebastien goasguen
Fixed in master and 4.2
assignVirtualMachine API has wrong response string, causing Cloudmonkey to
crash
Key: CLOUDSTACK-4998
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4998
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API, Cloudmonkey
Affects Versions: 4.2.0
Environment: CloudStack 4.2.0, XenServer 6.2, Cloudmonkey 5.0.0
Reporter: Ryan Lei
Assignee: sebastien goasguen
Fix For: 4.2.1, 4.3.0
From mailing list discussion:
[~ryanleitaiwan] says:
For now, the only way to change the ownership of a VM is by the
assignVirtualMachine API.
But executing this API using Cloudmonkey leads to the following error that
crashes the program:
assign virtualmachine virtualmachineid=7fe548bb-b2a7-4aec-92c5-5012ef9fd4f4
account=domain1-user1 domainid=cfc19b03-0858-4f39-9058-e0b67685bc2f
Traceback (most recent call last):
File /usr/bin/cloudmonkey, line 9, in module
load_entry_point('cloudmonkey==5.0.0', 'console_scripts', 'cloudmonkey')()
File
/usr/lib/python2.6/site-packages/cloudmonkey-5.0.0-py2.6.egg/cloudmonkey/cloudmonkey.py,
line 536, in main
shell.cmdloop()
File
/usr/lib/python2.6/site-packages/cloudmonkey-5.0.0-py2.6.egg/cloudmonkey/cloudmonkey.py,
line 106, in cmdloop
super(CloudMonkeyShell, self).cmdloop(intro=)
File /usr/lib64/python2.6/cmd.py, line 142, in cmdloop
stop = self.onecmd(line)
File /usr/lib64/python2.6/cmd.py, line 219, in onecmd
return func(arg)
File
/usr/lib/python2.6/site-packages/cloudmonkey-5.0.0-py2.6.egg/cloudmonkey/cloudmonkey.py,
line 134, in grammar_closure
self.default(%s %s % (cmd, args))
File
/usr/lib/python2.6/site-packages/cloudmonkey-5.0.0-py2.6.egg/cloudmonkey/cloudmonkey.py,
line 303, in default
result = self.make_request(apiname, args_dict, isasync)
File
/usr/lib/python2.6/site-packages/cloudmonkey-5.0.0-py2.6.egg/cloudmonkey/cloudmonkey.py,
line 257, in make_request
self.timeout, self.protocol, self.path)
File
/usr/lib/python2.6/site-packages/cloudmonkey-5.0.0-py2.6.egg/cloudmonkey/requester.py,
line 121, in monkeyrequest
responsekey = filter(lambda x: 'response' in x, response.keys())[0]
IndexError: list index out of range
[cs42]~#
Here's the assignVirtualMachine response json from log:
http://apaste.info/9f1H
[~sebgoa] says:
I think the error is in the java code of AssignVirtualMachine:
api/src/org/apache/cloudstack/api/command/admin/vm/AssignVMCmd.java:
@APICommand(name = assignVirtualMachine, description=Change ownership of a
VM from one account to another. This API is available for Basic zones with
security groups and Advanced zones with guest networks. A root administrator
can reassign a VM from any account to any other account in any domain. A
domain administrator can reassign a VM to any account in the same domain.,
responseObject=UserVmResponse.class, since=3.0.0)
public class AssignVMCmd extends BaseCmd {
public static final Logger s_logger =
Logger.getLogger(AssignVMCmd.class.getName());
private static final String s_name = moveuservmresponse;
}
Shouldn't the string be assignvirtualmachineresponse ?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Assigned] (CLOUDSTACK-4970) [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen reassigned CLOUDSTACK-4970: -- Assignee: sebastien goasguen [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command --- Key: CLOUDSTACK-4970 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4970 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Radhika Nair Assignee: sebastien goasguen Fix For: 4.2.1 At this link: https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/management-server-install-flow.html The command for installing the management server for Ubuntu is spelt incorrectly, make sure you spell management correctly if you are copying and pasting from the guide. If someone could spend the 20 seconds updating the guide, even better. (Posted on behalf of Mark van der Meulen m...@fivenynes.com) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CLOUDSTACK-4970) [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-4970. Resolution: Fixed Fix Version/s: 4.2.1 already fixed in master [Doc] Installation Guide Error: Typo in the Ubuntu Installation Command --- Key: CLOUDSTACK-4970 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4970 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Radhika Nair Assignee: sebastien goasguen Fix For: 4.2.1 At this link: https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/management-server-install-flow.html The command for installing the management server for Ubuntu is spelt incorrectly, make sure you spell management correctly if you are copying and pasting from the guide. If someone could spend the 20 seconds updating the guide, even better. (Posted on behalf of Mark van der Meulen m...@fivenynes.com) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (CLOUDSTACK-2057) Developer's Guide incorrectly describes API signature as hash of base URL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen closed CLOUDSTACK-2057. -- Developer's Guide incorrectly describes API signature as hash of base URL - Key: CLOUDSTACK-2057 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2057 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.0.0, 4.1.0, 4.2.0 Reporter: Jessica Tomechak Assignee: sebastien goasguen This affects the Signing API Requests section in the Developer's Guide. The source file is signing-api-requests.xml. The docs define the Base URL as http://hostname:port and then go on to say Signature: This is the hashed signature of the Base URL. But when describing how to generate the signature, the Base URL isn't used. The Command String is used. Need to determine which description is correct. The current info is self-contradictory. (Requested by Matty Courtney) -- 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-3143) revoke securitygroup ingress/egress does not return correct response
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen closed CLOUDSTACK-3143. -- Assignee: sebastien goasguen revoke securitygroup ingress/egress does not return correct response Key: CLOUDSTACK-3143 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3143 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.1.0 Environment: seems that revokeSecurityGroupIngress and revokeSecurityGroupEgress don't return the correct response. Instead of revokesecuritygroupingressresponse it returns revokesecuritygroupingress. same for revokeSecurityGroupEgress Reporter: sebastien goasguen Assignee: sebastien goasguen Fix For: 4.2.0 -- 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-4451) associateIPaddress requires zone id but apidoc says it's optional
sebastien goasguen created CLOUDSTACK-4451:
--
Summary: associateIPaddress requires zone id but apidoc says it's
optional
Key: CLOUDSTACK-4451
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4451
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: API
Affects Versions: 4.2.0
Reporter: sebastien goasguen
Fix For: Future
apidoc for associateIPaddress says that zone id is optional:
http://cloudstack.apache.org/docs/api/apidocs-4.1/root_admin/associateIpAddress.html
but it's required:
Try calling it with cloudmonkey without any arguments.
Exception: {u'associateipaddressresponse': {u'errorcode': 431, u'uuidList': [],
u'errortext': u'Unable to figure out zone to assign ip to'}}
--
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-2057) Developer's Guide incorrectly describes API signature as hash of base URL
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-2057. Resolution: Fixed Developer's Guide incorrectly describes API signature as hash of base URL - Key: CLOUDSTACK-2057 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2057 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.0.0, 4.1.0, 4.2.0 Reporter: Jessica Tomechak Assignee: sebastien goasguen This affects the Signing API Requests section in the Developer's Guide. The source file is signing-api-requests.xml. The docs define the Base URL as http://hostname:port and then go on to say Signature: This is the hashed signature of the Base URL. But when describing how to generate the signature, the Base URL isn't used. The Command String is used. Need to determine which description is correct. The current info is self-contradictory. (Requested by Matty Courtney) -- 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-2373) Docs page not found http://cloudstack.apache.org/docs/zh-CN/index.html
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713502#comment-13713502 ] sebastien goasguen commented on CLOUDSTACK-2373: Please try again to reach cloudstack.apache.org/docs then select chinese in the drop down button that selects languages. thanks Docs page not found http://cloudstack.apache.org/docs/zh-CN/index.html -- Key: CLOUDSTACK-2373 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2373 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: zhifeng hu Docs page not found http://cloudstack.apache.org/docs/zh-CN/index.html Not Found The requested URL /docs/zh-CN/index.html was not found on this server. Apache/2.4.4 (Unix) mod_wsgi/3.4 Python/2.7.3 OpenSSL/1.0.0g Server at cloudstack.apache.org Port 80 -- 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-3457) Language: Japanese. Nothing is displayed on a screen after login.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13705935#comment-13705935 ] sebastien goasguen commented on CLOUDSTACK-3457: Satoru, can you confirm that this happens on the 4.2 branch ? The 4.1 release should be fine. Language: Japanese. Nothing is displayed on a screen after login. -- Key: CLOUDSTACK-3457 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3457 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Environment: Management Server : CentOS 6.3 Reporter: satoru nakaya Priority: Critical 1. Language : Choose Japanese. 2. Log in. 3. Nothing is displayed on a screen after login. -- 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-3300) [DOC] Working with Volume section is missing again in 4.2 and master
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13697636#comment-13697636 ] sebastien goasguen commented on CLOUDSTACK-3300: Cool, thanks Ryan [DOC] Working with Volume section is missing again in 4.2 and master Key: CLOUDSTACK-3300 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3300 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0, Future Environment: platform-independent Reporter: Ryan Lei Assignee: sebastien goasguen Priority: Blocker Fix For: 4.2.0, Future In the current Jenkins build, the admin guide is missing this whole section Working with Volume. http://jenkins.cloudstack.org/view/master/job/build-docs-admin-master/ After browsing the source and history, it seems like CLOUDSTACK-1313 should have been committed to master, too. https://issues.apache.org/jira/browse/CLOUDSTACK-1313 working-with-volumes.xml in master has never had the missing subsections since it was created. If the removal is not intentional, we should at least have the same working-with-volumes.xml as in 4.1 branch. -- 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-814) Integrate Opennebula Marketplace
[ https://issues.apache.org/jira/browse/CLOUDSTACK-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen updated CLOUDSTACK-814: -- Fix Version/s: (was: 4.2.0) Future Integrate Opennebula Marketplace Key: CLOUDSTACK-814 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-814 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.1.0 Reporter: sebastien goasguen Assignee: sebastien goasguen Fix For: Future Integrate the Opennebula marketplace within the CS marketplace -- 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-3300) [DOC] Working with Volume section is missing again in 4.2 and master
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13696689#comment-13696689 ] sebastien goasguen commented on CLOUDSTACK-3300: fixed, let's check the next build thanks for reporting this. [DOC] Working with Volume section is missing again in 4.2 and master Key: CLOUDSTACK-3300 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3300 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0, Future Environment: platform-independent Reporter: Ryan Lei Assignee: sebastien goasguen Priority: Blocker Fix For: 4.2.0, Future In the current Jenkins build, the admin guide is missing this whole section Working with Volume. http://jenkins.cloudstack.org/view/master/job/build-docs-admin-master/ After browsing the source and history, it seems like CLOUDSTACK-1313 should have been committed to master, too. https://issues.apache.org/jira/browse/CLOUDSTACK-1313 working-with-volumes.xml in master has never had the missing subsections since it was created. If the removal is not intentional, we should at least have the same working-with-volumes.xml as in 4.1 branch. -- 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-3300) [DOC] Working with Volume section is missing again in 4.2 and master
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen reassigned CLOUDSTACK-3300: -- Assignee: sebastien goasguen [DOC] Working with Volume section is missing again in 4.2 and master Key: CLOUDSTACK-3300 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3300 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0, Future Environment: platform-independent Reporter: Ryan Lei Assignee: sebastien goasguen Priority: Blocker Fix For: 4.2.0, Future In the current Jenkins build, the admin guide is missing this whole section Working with Volume. http://jenkins.cloudstack.org/view/master/job/build-docs-admin-master/ After browsing the source and history, it seems like CLOUDSTACK-1313 should have been committed to master, too. https://issues.apache.org/jira/browse/CLOUDSTACK-1313 working-with-volumes.xml in master has never had the missing subsections since it was created. If the removal is not intentional, we should at least have the same working-with-volumes.xml as in 4.1 branch. -- 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-3300) [DOC] Working with Volume section is missing again in 4.2 and master
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-3300. Resolution: Fixed I applied Radhika's patches from 1313 [DOC] Working with Volume section is missing again in 4.2 and master Key: CLOUDSTACK-3300 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3300 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0, Future Environment: platform-independent Reporter: Ryan Lei Assignee: sebastien goasguen Priority: Blocker Fix For: 4.2.0, Future In the current Jenkins build, the admin guide is missing this whole section Working with Volume. http://jenkins.cloudstack.org/view/master/job/build-docs-admin-master/ After browsing the source and history, it seems like CLOUDSTACK-1313 should have been committed to master, too. https://issues.apache.org/jira/browse/CLOUDSTACK-1313 working-with-volumes.xml in master has never had the missing subsections since it was created. If the removal is not intentional, we should at least have the same working-with-volumes.xml as in 4.1 branch. -- 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
