[jira] [Assigned] (CLOUDSTACK-1053) Start systemvm
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav reassigned CLOUDSTACK-1053: --- Assignee: (was: Rohit Yadav) Unable to reproduce the bug, as Rubec suggests that both the global config vars are true, I don't know what could be the issue. Unassigned, so someone else can have a second look. Start systemvm -- Key: CLOUDSTACK-1053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1053 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Xen Affects Versions: 4.0.0 Environment: Centos 6.3, xcp 1.5 beta Reporter: Rubec Anton So, i create zone in advanced mode, added host with local storage(...use.local..= true in global set) and when i enabled zone, cloud cant run the systemvm like ssvm onsole proxy Log catalina.out WARN [storage.secondary.SecondaryStorageManagerImpl] (Job-Executor-1:job-24) Exception while trying to start secondary storage vm com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[SecondaryStorageVm|s-10-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:472) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:465) at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:257) at com.cloud.server.ManagementServerImpl.startSecondaryStorageVm(ManagementServerImpl.java:2604) at com.cloud.event.ActionEventCallback.intercept(ActionEventCallback.java:36) at com.cloud.server.ManagementServerImpl.startSystemVM(ManagementServerImpl.java:2730) at com.cloud.api.commands.StartSystemVMCmd.execute(StartSystemVMCmd.java:107) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) WARN [cloud.api.ApiDispatcher] (Job-Executor-1:job-24) class com.cloud.api.ServerApiException : Fail to start system vm WARN [cloud.resource.DiscovererBase] (ClusteredAgentManager Timer:) Unable to configure resource due to Can not get host information from 10.12.41.85 WARN [agent.manager.AgentManagerImpl] (ClusteredAgentManager Timer:) Unable to load the resource: 1 WARN [cloud.consoleproxy.ConsoleProxyManagerImpl] (Job-Executor-2:job-25) Exception while trying to start console proxy com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[ConsoleProxy|v-2-VM]Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:734) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:472) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:465) at com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:627) at com.cloud.server.ManagementServerImpl.startConsoleProxy(ManagementServerImpl.java:1911) at com.cloud.server.ManagementServerImpl.startSystemVM(ManagementServerImpl.java:2728) at com.cloud.api.commands.StartSystemVMCmd.execute(StartSystemVMCmd.java:107) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) WARN [cloud.api.ApiDispatcher] (Job-Executor-2:job-25) class com.cloud.api.ServerApiException : Fail to start system vm WARN [cloud.resource.DiscovererBase] (ClusteredAgentManager
Re: Review Request: Documentation on Persistent Network
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9421/ --- (Updated Feb. 13, 2013, 8:18 a.m.) Review request for cloudstack, David Nalley, Chip Childers, Jessica Tomechak, Likitha Shetty, and Joe Brockmeier. Changes --- created a patch purely for 4.1 branch. Description --- Documentation changes for the feature Persistent Network. The document describes what is Persistent Networks, how to configure one, and the advantages. This addresses bug CLOUDSTACK-852. Diffs - docs/en-US/creating-network-offerings.xml 0269ce0 docs/en-US/networks.xml a7b9ea1 docs/en-US/persistent-network.xml PRE-CREATION Diff: https://reviews.apache.org/r/9421/diff/ Testing --- Patch cleanly applies. The initial tech review is done by the developer. Build fine for both Admin and Install Guides. Thanks, Radhika PC
Re: Review Request: Documentation on Persistent Network
On Feb. 13, 2013, 7:54 a.m., Pranav Saxena wrote: Tried to cherry pick the same commit to 4.1 but it gives a merge conflict in networkOfferings.xml file. Could you please resolve them and send an updated patch for asf/4.1 . Regards, Pranav Jessica had some commit on the 4.1 branch (on the file creating-network-offering.xml)because of which there was a merge conflict. I am attaching a new patch taken against 4.1 branch is attaching. Please merge. - Radhika --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9421/#review16505 --- On Feb. 13, 2013, 8:18 a.m., Radhika PC wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9421/ --- (Updated Feb. 13, 2013, 8:18 a.m.) Review request for cloudstack, David Nalley, Chip Childers, Jessica Tomechak, Likitha Shetty, and Joe Brockmeier. Description --- Documentation changes for the feature Persistent Network. The document describes what is Persistent Networks, how to configure one, and the advantages. This addresses bug CLOUDSTACK-852. Diffs - docs/en-US/creating-network-offerings.xml 0269ce0 docs/en-US/networks.xml a7b9ea1 docs/en-US/persistent-network.xml PRE-CREATION Diff: https://reviews.apache.org/r/9421/diff/ Testing --- Patch cleanly applies. The initial tech review is done by the developer. Build fine for both Admin and Install Guides. Thanks, Radhika PC
Re: Review Request: Documentation on Persistent Network
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9421/#review16507 --- Sorry , not able to apply your patch cleanly on 4.1 because of this - error: patch failed: docs/en-US/creating-network-offerings.xml:22 error: docs/en-US/creating-network-offerings.xml: patch does not apply could you please check ? Thanks! - Pranav Saxena On Feb. 13, 2013, 8:18 a.m., Radhika PC wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9421/ --- (Updated Feb. 13, 2013, 8:18 a.m.) Review request for cloudstack, David Nalley, Chip Childers, Jessica Tomechak, Likitha Shetty, and Joe Brockmeier. Description --- Documentation changes for the feature Persistent Network. The document describes what is Persistent Networks, how to configure one, and the advantages. This addresses bug CLOUDSTACK-852. Diffs - docs/en-US/creating-network-offerings.xml 0269ce0 docs/en-US/networks.xml a7b9ea1 docs/en-US/persistent-network.xml PRE-CREATION Diff: https://reviews.apache.org/r/9421/diff/ Testing --- Patch cleanly applies. The initial tech review is done by the developer. Build fine for both Admin and Install Guides. Thanks, Radhika PC
Build failed in Jenkins: build-docs-install-master #763
Something went wrong with: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=eaf7767c8521e88f9d5b6f2865acafd34f9430fe Regards. -- Forwarded message -- From: jenk...@cloudstack.org Date: Wed, Feb 13, 2013 at 1:58 PM Subject: Build failed in Jenkins: build-docs-install-master #763 To: cloudstack-comm...@incubator.apache.org, bhais...@apache.org, pranav.sax...@citrix.com See http://jenkins.cloudstack.org/job/build-docs-install-master/763/changes Changes: [Rohit Yadav] maven: build client at the end, fixes path error for console-proxy build target -- [...truncated 249 lines...] Processing file tmp/en-US/xml_tmp/hypervisor-installation.xml - tmp/en-US/xml/hypervisor-installation.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-install-flow.xml - tmp/en-US/xml/hypervisor-kvm-install-flow.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-requirements.xml - tmp/en-US/xml/hypervisor-kvm-requirements.xml Processing file tmp/en-US/xml_tmp/hypervisor-support-for-primarystorage.xml - tmp/en-US/xml/hypervisor-support-for-primarystorage.xml Processing file tmp/en-US/xml_tmp/import-ami.xml - tmp/en-US/xml/import-ami.xml Processing file tmp/en-US/xml_tmp/increase-management-server-max-memory.xml - tmp/en-US/xml/increase-management-server-max-memory.xml Processing file tmp/en-US/xml_tmp/incremental-snapshots-backup.xml - tmp/en-US/xml/incremental-snapshots-backup.xml Processing file tmp/en-US/xml_tmp/initial-setup-of-external-firewalls-loadbalancers.xml - tmp/en-US/xml/initial-setup-of-external-firewalls-loadbalancers.xml Processing file tmp/en-US/xml_tmp/initialize-and-test.xml - tmp/en-US/xml/initialize-and-test.xml Processing file tmp/en-US/xml_tmp/install-usage-server.xml - tmp/en-US/xml/install-usage-server.xml Processing file tmp/en-US/xml_tmp/installation-complete.xml - tmp/en-US/xml/installation-complete.xml Processing file tmp/en-US/xml_tmp/installation-steps-overview.xml - tmp/en-US/xml/installation-steps-overview.xml Processing file tmp/en-US/xml_tmp/installation.xml - tmp/en-US/xml/installation.xml Processing file tmp/en-US/xml_tmp/installation_steps_overview.xml - tmp/en-US/xml/installation_steps_overview.xml Processing file tmp/en-US/xml_tmp/installing-publican.xml - tmp/en-US/xml/installing-publican.xml Processing file tmp/en-US/xml_tmp/inter-vlan-routing.xml - tmp/en-US/xml/inter-vlan-routing.xml Processing file tmp/en-US/xml_tmp/introduction.xml - tmp/en-US/xml/introduction.xml Processing file tmp/en-US/xml_tmp/ip-forwarding-firewalling.xml - tmp/en-US/xml/ip-forwarding-firewalling.xml Processing file tmp/en-US/xml_tmp/ip-load-balancing.xml - tmp/en-US/xml/ip-load-balancing.xml Processing file tmp/en-US/xml_tmp/ipaddress-usage-record-format.xml - tmp/en-US/xml/ipaddress-usage-record-format.xml Processing file tmp/en-US/xml_tmp/isolated-networks.xml - tmp/en-US/xml/isolated-networks.xml Processing file tmp/en-US/xml_tmp/job-status.xml - tmp/en-US/xml/job-status.xml Processing file tmp/en-US/xml_tmp/kvm-topology-req.xml - tmp/en-US/xml/kvm-topology-req.xml Processing file tmp/en-US/xml_tmp/large_scale_redundant_setup.xml - tmp/en-US/xml/large_scale_redundant_setup.xml Processing file tmp/en-US/xml_tmp/layer2-switch.xml - tmp/en-US/xml/layer2-switch.xml Processing file tmp/en-US/xml_tmp/lb-policy-pfwd-rule-usage-record-format.xml - tmp/en-US/xml/lb-policy-pfwd-rule-usage-record-format.xml Processing file tmp/en-US/xml_tmp/linux-installation.xml - tmp/en-US/xml/linux-installation.xml Processing file tmp/en-US/xml_tmp/load-balancer-rules.xml - tmp/en-US/xml/load-balancer-rules.xml Processing file tmp/en-US/xml_tmp/log-in-root-admin.xml - tmp/en-US/xml/log-in-root-admin.xml Processing file tmp/en-US/xml_tmp/log-in.xml - tmp/en-US/xml/log-in.xml Processing file tmp/en-US/xml_tmp/long-running-job-events.xml - tmp/en-US/xml/long-running-job-events.xml Processing file tmp/en-US/xml_tmp/maintain-hypervisors-on-hosts.xml - tmp/en-US/xml/maintain-hypervisors-on-hosts.xml Processing file tmp/en-US/xml_tmp/maintenance-mode-for-primary-storage.xml - tmp/en-US/xml/maintenance-mode-for-primary-storage.xml Processing file tmp/en-US/xml_tmp/making-api-request.xml - tmp/en-US/xml/making-api-request.xml Processing file tmp/en-US/xml_tmp/manage-cloud.xml - tmp/en-US/xml/manage-cloud.xml Processing file tmp/en-US/xml_tmp/management-server-install-client.xml - tmp/en-US/xml/management-server-install-client.xml Processing file tmp/en-US/xml_tmp/management-server-install-complete.xml - tmp/en-US/xml/management-server-install-complete.xml Processing file tmp/en-US/xml_tmp/management-server-install-db-external.xml -
[jira] [Updated] (CLOUDSTACK-1019) Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav updated CLOUDSTACK-1019: Summary: Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades (was: Fix cloud-setup-database to use DatabaseCreator for setting up cloudstack databases) Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades Key: CLOUDSTACK-1019 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1019 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: branch: javelin (or master if merge happens) Reporter: Rohit Yadav Assignee: Rohit Yadav Fix For: 4.1.0 A new tool/class called DatabaseCreator is introduced in javelin, the idea is that DatabaseCreator can be used by mgmt server, cloud-setup-database script, maven (developer/pom.xml) and possibly by plugins in future to: 1. Initialize database using db.properties file 2. Run sql scripts 3. Run database upgrades Presently, this has been fixed in javelin, in cloud-server and is used by maven to deploydb, the task is to fix that same for cloud-setup-databases. Current help doc, usage and options: DatabaseCreator creates the database schema by removing the previous schema, creating the schema, and running through the database updaters. Usage: DatabaseCreator [options] [db.properties file] [schema.sql files] [database upgrade class] Options: --database=a,b comma separate databases to initialize, use the db name in db.properties defined as db.xyz.host, xyz should be passed --rootpassword=password, by default it will try with an empty password --dry or -d, this would not run any process, just does a dry run --verbose or -v to print running sql commands, by default it won't print them --help or -h for help -- 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-1019) Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav updated CLOUDSTACK-1019: Description: A new tool/class called DatabaseCreator is introduced in javelin, the idea is that DatabaseCreator can be used by mgmt server, cloud-setup-database script, maven (developer/pom.xml) and possibly by plugins in future to: 1. Initialize database using db.properties file 2. Run sql scripts 3. Run database upgrades Presently, this has been fixed in javelin, in cloud-server and is used by maven to deploydb, the task is to fix that same for cloud-setup-databases. Current help doc, usage and options: DatabaseCreator creates the database schema by removing the previous schema, creating the schema, and running through the database updaters. Usage: DatabaseCreator [options] [db.properties file] [schema.sql files] [database upgrade class] Options: --database=a,b comma separate databases to initialize, use the db name in db.properties defined as db.xyz.host, xyz should be passed --rootpassword=password, by default it will try with an empty password --dry or -d, this would not run any process, just does a dry run --verbose or -v to print running sql commands, by default it won't print them --help or -h for help The issue now is to make cloudstack-setup-databases use DatabaseCreator and remove db upgrading logic from mgmt server and move it to DatabaseCreator. was: A new tool/class called DatabaseCreator is introduced in javelin, the idea is that DatabaseCreator can be used by mgmt server, cloud-setup-database script, maven (developer/pom.xml) and possibly by plugins in future to: 1. Initialize database using db.properties file 2. Run sql scripts 3. Run database upgrades Presently, this has been fixed in javelin, in cloud-server and is used by maven to deploydb, the task is to fix that same for cloud-setup-databases. Current help doc, usage and options: DatabaseCreator creates the database schema by removing the previous schema, creating the schema, and running through the database updaters. Usage: DatabaseCreator [options] [db.properties file] [schema.sql files] [database upgrade class] Options: --database=a,b comma separate databases to initialize, use the db name in db.properties defined as db.xyz.host, xyz should be passed --rootpassword=password, by default it will try with an empty password --dry or -d, this would not run any process, just does a dry run --verbose or -v to print running sql commands, by default it won't print them --help or -h for help Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades Key: CLOUDSTACK-1019 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1019 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: branch: javelin (or master if merge happens) Reporter: Rohit Yadav Assignee: Rohit Yadav Fix For: 4.1.0 A new tool/class called DatabaseCreator is introduced in javelin, the idea is that DatabaseCreator can be used by mgmt server, cloud-setup-database script, maven (developer/pom.xml) and possibly by plugins in future to: 1. Initialize database using db.properties file 2. Run sql scripts 3. Run database upgrades Presently, this has been fixed in javelin, in cloud-server and is used by maven to deploydb, the task is to fix that same for cloud-setup-databases. Current help doc, usage and options: DatabaseCreator creates the database schema by removing the previous schema, creating the schema, and running through the database updaters. Usage: DatabaseCreator [options] [db.properties file] [schema.sql files] [database upgrade class] Options: --database=a,b comma separate databases to initialize, use the db name in db.properties defined as db.xyz.host, xyz should be passed --rootpassword=password, by default it will try with an empty password --dry or -d, this would not run any process, just does a dry run --verbose or -v to print running sql commands, by default it won't print them --help or -h for help The issue now is to make cloudstack-setup-databases use DatabaseCreator and remove db upgrading logic from mgmt server and move it to DatabaseCreator. -- 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-1240) Unable to registerTemplate : Cannot find template adapter for XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577430#comment-13577430 ] Hongtu Zang commented on CLOUDSTACK-1240: - I fixed this bug. In TemplateManagerImpl.java, function getAdapter(), TemplateAdapterType.Hypervisor.getName() returns HyervisorAdapter, while it should returns HyervisorTemplateAdapter. So, in AdapterBase.java function getAdapterByName() returns null. https://reviews.apache.org/r/9420/ Unable to registerTemplate : Cannot find template adapter for XenServer --- Key: CLOUDSTACK-1240 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1240 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.1.0 Environment: ms: rhel6.3 hypervisor: Xenserver6.1 advanced zone Reporter: Srikanteswararao Talluri Priority: Blocker Fix For: 4.1.0 unhandled exception executing api command: registerTemplate com.cloud.utils.exception.CloudRuntimeException: Cannot find template adapter for XenServer at com.cloud.template.TemplateManagerImpl.getAdapter(TemplateManagerImpl.java:192) at com.cloud.template.TemplateManagerImpl.registerTemplate(TemplateManagerImpl.java:221) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41) at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at org.apache.cloudstack.api.command.user.template.RegisterTemplateCmd.execute(RegisterTemplateCmd.java:229) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.utils.db.TransactionContextBuilder.invoke(TransactionContextBuilder.java:60) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at
RE: Build failed in Jenkins: build-docs-install-master #763
Jessica /Radhika Could you please check what's wrong with the patch for persistent networks and also verify if it builds properly else I'll have to revert this commit . Regards, Pranav -Original Message- From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf Of Rohit Yadav Sent: Wednesday, February 13, 2013 2:37 PM To: cloudstack-dev@incubator.apache.org Subject: Build failed in Jenkins: build-docs-install-master #763 Something went wrong with: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=eaf7767c8521e88f9d5b6f2865acafd34f9430fe Regards. -- Forwarded message -- From: jenk...@cloudstack.org Date: Wed, Feb 13, 2013 at 1:58 PM Subject: Build failed in Jenkins: build-docs-install-master #763 To: cloudstack-comm...@incubator.apache.org, bhais...@apache.org, pranav.sax...@citrix.com See http://jenkins.cloudstack.org/job/build-docs-install-master/763/changes Changes: [Rohit Yadav] maven: build client at the end, fixes path error for console-proxy build target -- [...truncated 249 lines...] Processing file tmp/en-US/xml_tmp/hypervisor-installation.xml - tmp/en-US/xml/hypervisor-installation.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-install-flow.xml - tmp/en-US/xml/hypervisor-kvm-install-flow.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-requirements.xml - tmp/en-US/xml/hypervisor-kvm-requirements.xml Processing file tmp/en-US/xml_tmp/hypervisor-support-for-primarystorage.xml - tmp/en-US/xml/hypervisor-support-for-primarystorage.xml Processing file tmp/en-US/xml_tmp/import-ami.xml - tmp/en-US/xml/import-ami.xml Processing file tmp/en-US/xml_tmp/increase-management-server-max-memory.xml - tmp/en-US/xml/increase-management-server-max-memory.xml Processing file tmp/en-US/xml_tmp/incremental-snapshots-backup.xml - tmp/en-US/xml/incremental-snapshots-backup.xml Processing file tmp/en-US/xml_tmp/initial-setup-of-external-firewalls-loadbalancers.xml - tmp/en-US/xml/initial-setup-of-external-firewalls-loadbalancers.xml Processing file tmp/en-US/xml_tmp/initialize-and-test.xml - tmp/en-US/xml/initialize-and-test.xml Processing file tmp/en-US/xml_tmp/install-usage-server.xml - tmp/en-US/xml/install-usage-server.xml Processing file tmp/en-US/xml_tmp/installation-complete.xml - tmp/en-US/xml/installation-complete.xml Processing file tmp/en-US/xml_tmp/installation-steps-overview.xml - tmp/en-US/xml/installation-steps-overview.xml Processing file tmp/en-US/xml_tmp/installation.xml - tmp/en-US/xml/installation.xml Processing file tmp/en-US/xml_tmp/installation_steps_overview.xml - tmp/en-US/xml/installation_steps_overview.xml Processing file tmp/en-US/xml_tmp/installing-publican.xml - tmp/en-US/xml/installing-publican.xml Processing file tmp/en-US/xml_tmp/inter-vlan-routing.xml - tmp/en-US/xml/inter-vlan-routing.xml Processing file tmp/en-US/xml_tmp/introduction.xml - tmp/en-US/xml/introduction.xml Processing file tmp/en-US/xml_tmp/ip-forwarding-firewalling.xml - tmp/en-US/xml/ip-forwarding-firewalling.xml Processing file tmp/en-US/xml_tmp/ip-load-balancing.xml - tmp/en-US/xml/ip-load-balancing.xml Processing file tmp/en-US/xml_tmp/ipaddress-usage-record-format.xml - tmp/en-US/xml/ipaddress-usage-record-format.xml Processing file tmp/en-US/xml_tmp/isolated-networks.xml - tmp/en-US/xml/isolated-networks.xml Processing file tmp/en-US/xml_tmp/job-status.xml - tmp/en-US/xml/job-status.xml Processing file tmp/en-US/xml_tmp/kvm-topology-req.xml - tmp/en-US/xml/kvm-topology-req.xml Processing file tmp/en-US/xml_tmp/large_scale_redundant_setup.xml - tmp/en-US/xml/large_scale_redundant_setup.xml Processing file tmp/en-US/xml_tmp/layer2-switch.xml - tmp/en-US/xml/layer2-switch.xml Processing file tmp/en-US/xml_tmp/lb-policy-pfwd-rule-usage-record-format.xml - tmp/en-US/xml/lb-policy-pfwd-rule-usage-record-format.xml Processing file tmp/en-US/xml_tmp/linux-installation.xml - tmp/en-US/xml/linux-installation.xml Processing file tmp/en-US/xml_tmp/load-balancer-rules.xml - tmp/en-US/xml/load-balancer-rules.xml Processing file tmp/en-US/xml_tmp/log-in-root-admin.xml - tmp/en-US/xml/log-in-root-admin.xml Processing file tmp/en-US/xml_tmp/log-in.xml - tmp/en-US/xml/log-in.xml Processing file tmp/en-US/xml_tmp/long-running-job-events.xml - tmp/en-US/xml/long-running-job-events.xml Processing file tmp/en-US/xml_tmp/maintain-hypervisors-on-hosts.xml - tmp/en-US/xml/maintain-hypervisors-on-hosts.xml Processing file tmp/en-US/xml_tmp/maintenance-mode-for-primary-storage.xml - tmp/en-US/xml/maintenance-mode-for-primary-storage.xml Processing file tmp/en-US/xml_tmp/making-api-request.xml -
[jira] [Assigned] (CLOUDSTACK-1019) Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav reassigned CLOUDSTACK-1019: --- Assignee: (was: Rohit Yadav) Unassigning to be picked up by someone else. I'm not sure how to do it correctly, picked up other things to work on. TODO includes: - Fix cloudstack-setup-databases to use DatabaseCreator and to do that we require configuring packaging so a classpath is expanded and used to call DatabaseCreator - Refactor and move out logic that does upgrades from mgmt server to databasecreator. Fix cloud-setup-database to use DatabaseCreator and make DatabaseCreator do the upgrades Key: CLOUDSTACK-1019 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1019 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: branch: javelin (or master if merge happens) Reporter: Rohit Yadav Fix For: 4.1.0 A new tool/class called DatabaseCreator is introduced in javelin, the idea is that DatabaseCreator can be used by mgmt server, cloud-setup-database script, maven (developer/pom.xml) and possibly by plugins in future to: 1. Initialize database using db.properties file 2. Run sql scripts 3. Run database upgrades Presently, this has been fixed in javelin, in cloud-server and is used by maven to deploydb, the task is to fix that same for cloud-setup-databases. Current help doc, usage and options: DatabaseCreator creates the database schema by removing the previous schema, creating the schema, and running through the database updaters. Usage: DatabaseCreator [options] [db.properties file] [schema.sql files] [database upgrade class] Options: --database=a,b comma separate databases to initialize, use the db name in db.properties defined as db.xyz.host, xyz should be passed --rootpassword=password, by default it will try with an empty password --dry or -d, this would not run any process, just does a dry run --verbose or -v to print running sql commands, by default it won't print them --help or -h for help The issue now is to make cloudstack-setup-databases use DatabaseCreator and remove db upgrading logic from mgmt server and move it to DatabaseCreator. -- 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
Re: [DISCUSS] Fixing cloud-setup-databases
Unassigned CLOUDSTACK-1019 to be picked up by someone else. I'm not sure how to do it correctly, picked up other things to work on. TODO includes from the discussion on this thread: - Fix cloudstack-setup-databases to use DatabaseCreator and to do that we require configuring packaging so a classpath is expanded and used to call DatabaseCreator - Refactor and move out logic that does upgrades from mgmt server to databasecreator. Regards. On Tue, Feb 12, 2013 at 5:02 PM, Abhinandan Prateek abhinandan.prat...@citrix.com wrote: We can discuss this one ? On 12/02/13 3:46 PM, Rohit Yadav bhais...@apache.org wrote: On Mon, Feb 11, 2013 at 11:45 PM, Alex Huang alex.hu...@citrix.com wrote: Rohit, The two should be one. Having the two separate is a bad idea because it means developers is running something very different from the actual deployment version which means actual deployment version is not tested until QA hits it. The setup database script should give options and the target in maven should just have all of the options standardized for developer. The other thing is you should announce this to the list with big headlines. Starting 4.1, we no longer modify the create-schema.sql. Only modify the upgrade schemas. The process should look like this and should be documented. +1 - For every major release (first dot release), we need to roll-up all of the changes in the schema and produce a create-schema.sql. The version recorded inside the create-schema.sql is the version of the major release. The steps to do this should be recorded in a wiki for the release manager to use. Okay will start a wiki on this. I just want to say that I don't know how to fix it, I don't understand the requirements clearly but will try my best to fix it. - Every release from this major release, we always create the database from create-schema.sql and then run the upgrades. The upgrades are exactly the same as what the management server would do to upgrade from existing version to current. We should discuss the following things: - Management Server no longer auto-upgrades. It brings more problems than it solves. Alright, so there are a lot of Upgrade versionx-versiony classes which are used by DatabaseUpgradeChecker. I did not write DatabaseCreator in python because I wanted to skip rewriting logic for these upgrade paths again. Do we want to keep it that way or should I start porting them to Python? It should just detect that the version in the database is different than its software version and exit. We can provide a flag to override that function. I just didn't think this through when I designed it but the good thing is it's all self-contained in a plugin so it's not difficult to change it. Instead of management server calling DatabaseUpgradeChecker, DatabaseCreator should call it. The upgrade path does not work in DatabaseCreator because I'll have to clean the spring stuff and get upgrading logic out of mgmt server if we don't want mgmt server to do it. - DatabaseCreator should take care of both upgrade situations and initial schema creation (which I believe you did already) and upgrade cleanup (not sure if you did this part) after all management servers have been upgraded. Yes, the initial schema creation work and no the upgrade and cleanup does not work because they need some refactoring and mgmt server in that case does not need to call DatabaseUpgradeChecker. This means - Developers don't write schemas in two places. It's always written in the upgrade files. +1 - Upgrade process for the admin is multi-steps. So, do we require sysadmin to run DatabaseCreator from version to version or should n't it just automatically upgrade to latest version? - Run DatabaseCreator (may be in a script) to do pre-upgrade and as part of this step should be the script to dump the database in case problems happen. - Upgrade all management server - Run DatabaseCreator (again maybe in a script) to do post-upgrade cleanup. - Release manager produces the create-schema.sql for every major release. For 4.1, we need to get rid of the 4.1-new-schema. I have no idea why that's created as it obviously doesn't fit into our upgrade strategy. Everything in that file should be moved into the DB upgrade scripts and that file removed in git and from the developer/pom.xml. Also, the version in create-schema.sql needs to stay the same and not changed with the release version any more. Alright. Regards. --Alex -Original Message- From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf Of Rohit Yadav Sent: Monday, February 11, 2013 9:13 AM To: Hugo Trippaers Cc: cloudstack-dev@incubator.apache.org Subject: Re: [DISCUSS] Fixing cloud-setup-databases Forgot to mention, one more reason why it was written in Java, as we pass a database upgrade class which is suppose to do the upgrade, tests etc. If we take the python route, these things can be python modules
RE: Build failed in Jenkins: build-docs-install-master #763
The issue is that on Master there is no section on creating a network offering in the Install Guide, whereas in 4.1 branch Jessica has fixed the issue. I shall fix this issue using the condition tag, and give a new patch. Pranav: Sorry about it, but you can revert the patch for now. -Original Message- From: Pranav Saxena Sent: Wednesday, February 13, 2013 2:56 PM To: cloudstack-dev@incubator.apache.org Cc: Jessica Tomechak; Radhika Puthiyetath Subject: RE: Build failed in Jenkins: build-docs-install-master #763 Jessica /Radhika Could you please check what's wrong with the patch for persistent networks and also verify if it builds properly else I'll have to revert this commit . Regards, Pranav -Original Message- From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf Of Rohit Yadav Sent: Wednesday, February 13, 2013 2:37 PM To: cloudstack-dev@incubator.apache.org Subject: Build failed in Jenkins: build-docs-install-master #763 Something went wrong with: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=eaf7767c8521e88f9d5b6f2865acafd34f9430fe Regards. -- Forwarded message -- From: jenk...@cloudstack.org Date: Wed, Feb 13, 2013 at 1:58 PM Subject: Build failed in Jenkins: build-docs-install-master #763 To: cloudstack-comm...@incubator.apache.org, bhais...@apache.org, pranav.sax...@citrix.com See http://jenkins.cloudstack.org/job/build-docs-install-master/763/changes Changes: [Rohit Yadav] maven: build client at the end, fixes path error for console-proxy build target -- [...truncated 249 lines...] Processing file tmp/en-US/xml_tmp/hypervisor-installation.xml - tmp/en-US/xml/hypervisor-installation.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-install-flow.xml - tmp/en-US/xml/hypervisor-kvm-install-flow.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-requirements.xml - tmp/en-US/xml/hypervisor-kvm-requirements.xml Processing file tmp/en-US/xml_tmp/hypervisor-support-for-primarystorage.xml - tmp/en-US/xml/hypervisor-support-for-primarystorage.xml Processing file tmp/en-US/xml_tmp/import-ami.xml - tmp/en-US/xml/import-ami.xml Processing file tmp/en-US/xml_tmp/increase-management-server-max-memory.xml - tmp/en-US/xml/increase-management-server-max-memory.xml Processing file tmp/en-US/xml_tmp/incremental-snapshots-backup.xml - tmp/en-US/xml/incremental-snapshots-backup.xml Processing file tmp/en-US/xml_tmp/initial-setup-of-external-firewalls-loadbalancers.xml - tmp/en-US/xml/initial-setup-of-external-firewalls-loadbalancers.xml Processing file tmp/en-US/xml_tmp/initialize-and-test.xml - tmp/en-US/xml/initialize-and-test.xml Processing file tmp/en-US/xml_tmp/install-usage-server.xml - tmp/en-US/xml/install-usage-server.xml Processing file tmp/en-US/xml_tmp/installation-complete.xml - tmp/en-US/xml/installation-complete.xml Processing file tmp/en-US/xml_tmp/installation-steps-overview.xml - tmp/en-US/xml/installation-steps-overview.xml Processing file tmp/en-US/xml_tmp/installation.xml - tmp/en-US/xml/installation.xml Processing file tmp/en-US/xml_tmp/installation_steps_overview.xml - tmp/en-US/xml/installation_steps_overview.xml Processing file tmp/en-US/xml_tmp/installing-publican.xml - tmp/en-US/xml/installing-publican.xml Processing file tmp/en-US/xml_tmp/inter-vlan-routing.xml - tmp/en-US/xml/inter-vlan-routing.xml Processing file tmp/en-US/xml_tmp/introduction.xml - tmp/en-US/xml/introduction.xml Processing file tmp/en-US/xml_tmp/ip-forwarding-firewalling.xml - tmp/en-US/xml/ip-forwarding-firewalling.xml Processing file tmp/en-US/xml_tmp/ip-load-balancing.xml - tmp/en-US/xml/ip-load-balancing.xml Processing file tmp/en-US/xml_tmp/ipaddress-usage-record-format.xml - tmp/en-US/xml/ipaddress-usage-record-format.xml Processing file tmp/en-US/xml_tmp/isolated-networks.xml - tmp/en-US/xml/isolated-networks.xml Processing file tmp/en-US/xml_tmp/job-status.xml - tmp/en-US/xml/job-status.xml Processing file tmp/en-US/xml_tmp/kvm-topology-req.xml - tmp/en-US/xml/kvm-topology-req.xml Processing file tmp/en-US/xml_tmp/large_scale_redundant_setup.xml - tmp/en-US/xml/large_scale_redundant_setup.xml Processing file tmp/en-US/xml_tmp/layer2-switch.xml - tmp/en-US/xml/layer2-switch.xml Processing file tmp/en-US/xml_tmp/lb-policy-pfwd-rule-usage-record-format.xml - tmp/en-US/xml/lb-policy-pfwd-rule-usage-record-format.xml Processing file tmp/en-US/xml_tmp/linux-installation.xml - tmp/en-US/xml/linux-installation.xml Processing file tmp/en-US/xml_tmp/load-balancer-rules.xml - tmp/en-US/xml/load-balancer-rules.xml Processing file tmp/en-US/xml_tmp/log-in-root-admin.xml - tmp/en-US/xml/log-in-root-admin.xml Processing
RE: Build failed in Jenkins: build-docs-install-master #763
Sure Radhika . No problems , I' have reverted the patch for the persistent networks documentation for now. Regards, Pranav -Original Message- From: Radhika Puthiyetath Sent: Wednesday, February 13, 2013 2:59 PM To: Pranav Saxena; cloudstack-dev@incubator.apache.org Cc: Jessica Tomechak Subject: RE: Build failed in Jenkins: build-docs-install-master #763 The issue is that on Master there is no section on creating a network offering in the Install Guide, whereas in 4.1 branch Jessica has fixed the issue. I shall fix this issue using the condition tag, and give a new patch. Pranav: Sorry about it, but you can revert the patch for now. -Original Message- From: Pranav Saxena Sent: Wednesday, February 13, 2013 2:56 PM To: cloudstack-dev@incubator.apache.org Cc: Jessica Tomechak; Radhika Puthiyetath Subject: RE: Build failed in Jenkins: build-docs-install-master #763 Jessica /Radhika Could you please check what's wrong with the patch for persistent networks and also verify if it builds properly else I'll have to revert this commit . Regards, Pranav -Original Message- From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf Of Rohit Yadav Sent: Wednesday, February 13, 2013 2:37 PM To: cloudstack-dev@incubator.apache.org Subject: Build failed in Jenkins: build-docs-install-master #763 Something went wrong with: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=eaf7767c8521e88f9d5b6f2865acafd34f9430fe Regards. -- Forwarded message -- From: jenk...@cloudstack.org Date: Wed, Feb 13, 2013 at 1:58 PM Subject: Build failed in Jenkins: build-docs-install-master #763 To: cloudstack-comm...@incubator.apache.org, bhais...@apache.org, pranav.sax...@citrix.com See http://jenkins.cloudstack.org/job/build-docs-install-master/763/changes Changes: [Rohit Yadav] maven: build client at the end, fixes path error for console-proxy build target -- [...truncated 249 lines...] Processing file tmp/en-US/xml_tmp/hypervisor-installation.xml - tmp/en-US/xml/hypervisor-installation.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-install-flow.xml - tmp/en-US/xml/hypervisor-kvm-install-flow.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-requirements.xml - tmp/en-US/xml/hypervisor-kvm-requirements.xml Processing file tmp/en-US/xml_tmp/hypervisor-support-for-primarystorage.xml - tmp/en-US/xml/hypervisor-support-for-primarystorage.xml Processing file tmp/en-US/xml_tmp/import-ami.xml - tmp/en-US/xml/import-ami.xml Processing file tmp/en-US/xml_tmp/increase-management-server-max-memory.xml - tmp/en-US/xml/increase-management-server-max-memory.xml Processing file tmp/en-US/xml_tmp/incremental-snapshots-backup.xml - tmp/en-US/xml/incremental-snapshots-backup.xml Processing file tmp/en-US/xml_tmp/initial-setup-of-external-firewalls-loadbalancers.xml - tmp/en-US/xml/initial-setup-of-external-firewalls-loadbalancers.xml Processing file tmp/en-US/xml_tmp/initialize-and-test.xml - tmp/en-US/xml/initialize-and-test.xml Processing file tmp/en-US/xml_tmp/install-usage-server.xml - tmp/en-US/xml/install-usage-server.xml Processing file tmp/en-US/xml_tmp/installation-complete.xml - tmp/en-US/xml/installation-complete.xml Processing file tmp/en-US/xml_tmp/installation-steps-overview.xml - tmp/en-US/xml/installation-steps-overview.xml Processing file tmp/en-US/xml_tmp/installation.xml - tmp/en-US/xml/installation.xml Processing file tmp/en-US/xml_tmp/installation_steps_overview.xml - tmp/en-US/xml/installation_steps_overview.xml Processing file tmp/en-US/xml_tmp/installing-publican.xml - tmp/en-US/xml/installing-publican.xml Processing file tmp/en-US/xml_tmp/inter-vlan-routing.xml - tmp/en-US/xml/inter-vlan-routing.xml Processing file tmp/en-US/xml_tmp/introduction.xml - tmp/en-US/xml/introduction.xml Processing file tmp/en-US/xml_tmp/ip-forwarding-firewalling.xml - tmp/en-US/xml/ip-forwarding-firewalling.xml Processing file tmp/en-US/xml_tmp/ip-load-balancing.xml - tmp/en-US/xml/ip-load-balancing.xml Processing file tmp/en-US/xml_tmp/ipaddress-usage-record-format.xml - tmp/en-US/xml/ipaddress-usage-record-format.xml Processing file tmp/en-US/xml_tmp/isolated-networks.xml - tmp/en-US/xml/isolated-networks.xml Processing file tmp/en-US/xml_tmp/job-status.xml - tmp/en-US/xml/job-status.xml Processing file tmp/en-US/xml_tmp/kvm-topology-req.xml - tmp/en-US/xml/kvm-topology-req.xml Processing file tmp/en-US/xml_tmp/large_scale_redundant_setup.xml - tmp/en-US/xml/large_scale_redundant_setup.xml Processing file tmp/en-US/xml_tmp/layer2-switch.xml - tmp/en-US/xml/layer2-switch.xml Processing file tmp/en-US/xml_tmp/lb-policy-pfwd-rule-usage-record-format.xml -
Re: [DISCUSS] Correctly fix cloud- to cloudstack- rename refactoring
I am would say lets fix real bugs than making these fixes. This can potentially break migration paths and the value add from this change is little except consistency in naming. On 13/02/13 12:05 PM, Rohit Yadav bhais...@apache.org wrote: Pl. rename any script references which have renamed from cloud- to cloudstack- in docs, code and elsewhere? Since we're renaming the packages to cloudstack- why not rename artifacts to cloudstack- as well? Regards.
RE: Build failed in Jenkins: build-docs-install-master #763
Thanks Rohit for pointing that out. Build is back to normal now . -Original Message- From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf Of Rohit Yadav Sent: Wednesday, February 13, 2013 2:37 PM To: cloudstack-dev@incubator.apache.org Subject: Build failed in Jenkins: build-docs-install-master #763 Something went wrong with: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=eaf7767c8521e88f9d5b6f2865acafd34f9430fe Regards. -- Forwarded message -- From: jenk...@cloudstack.org Date: Wed, Feb 13, 2013 at 1:58 PM Subject: Build failed in Jenkins: build-docs-install-master #763 To: cloudstack-comm...@incubator.apache.org, bhais...@apache.org, pranav.sax...@citrix.com See http://jenkins.cloudstack.org/job/build-docs-install-master/763/changes Changes: [Rohit Yadav] maven: build client at the end, fixes path error for console-proxy build target -- [...truncated 249 lines...] Processing file tmp/en-US/xml_tmp/hypervisor-installation.xml - tmp/en-US/xml/hypervisor-installation.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-install-flow.xml - tmp/en-US/xml/hypervisor-kvm-install-flow.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-requirements.xml - tmp/en-US/xml/hypervisor-kvm-requirements.xml Processing file tmp/en-US/xml_tmp/hypervisor-support-for-primarystorage.xml - tmp/en-US/xml/hypervisor-support-for-primarystorage.xml Processing file tmp/en-US/xml_tmp/import-ami.xml - tmp/en-US/xml/import-ami.xml Processing file tmp/en-US/xml_tmp/increase-management-server-max-memory.xml - tmp/en-US/xml/increase-management-server-max-memory.xml Processing file tmp/en-US/xml_tmp/incremental-snapshots-backup.xml - tmp/en-US/xml/incremental-snapshots-backup.xml Processing file tmp/en-US/xml_tmp/initial-setup-of-external-firewalls-loadbalancers.xml - tmp/en-US/xml/initial-setup-of-external-firewalls-loadbalancers.xml Processing file tmp/en-US/xml_tmp/initialize-and-test.xml - tmp/en-US/xml/initialize-and-test.xml Processing file tmp/en-US/xml_tmp/install-usage-server.xml - tmp/en-US/xml/install-usage-server.xml Processing file tmp/en-US/xml_tmp/installation-complete.xml - tmp/en-US/xml/installation-complete.xml Processing file tmp/en-US/xml_tmp/installation-steps-overview.xml - tmp/en-US/xml/installation-steps-overview.xml Processing file tmp/en-US/xml_tmp/installation.xml - tmp/en-US/xml/installation.xml Processing file tmp/en-US/xml_tmp/installation_steps_overview.xml - tmp/en-US/xml/installation_steps_overview.xml Processing file tmp/en-US/xml_tmp/installing-publican.xml - tmp/en-US/xml/installing-publican.xml Processing file tmp/en-US/xml_tmp/inter-vlan-routing.xml - tmp/en-US/xml/inter-vlan-routing.xml Processing file tmp/en-US/xml_tmp/introduction.xml - tmp/en-US/xml/introduction.xml Processing file tmp/en-US/xml_tmp/ip-forwarding-firewalling.xml - tmp/en-US/xml/ip-forwarding-firewalling.xml Processing file tmp/en-US/xml_tmp/ip-load-balancing.xml - tmp/en-US/xml/ip-load-balancing.xml Processing file tmp/en-US/xml_tmp/ipaddress-usage-record-format.xml - tmp/en-US/xml/ipaddress-usage-record-format.xml Processing file tmp/en-US/xml_tmp/isolated-networks.xml - tmp/en-US/xml/isolated-networks.xml Processing file tmp/en-US/xml_tmp/job-status.xml - tmp/en-US/xml/job-status.xml Processing file tmp/en-US/xml_tmp/kvm-topology-req.xml - tmp/en-US/xml/kvm-topology-req.xml Processing file tmp/en-US/xml_tmp/large_scale_redundant_setup.xml - tmp/en-US/xml/large_scale_redundant_setup.xml Processing file tmp/en-US/xml_tmp/layer2-switch.xml - tmp/en-US/xml/layer2-switch.xml Processing file tmp/en-US/xml_tmp/lb-policy-pfwd-rule-usage-record-format.xml - tmp/en-US/xml/lb-policy-pfwd-rule-usage-record-format.xml Processing file tmp/en-US/xml_tmp/linux-installation.xml - tmp/en-US/xml/linux-installation.xml Processing file tmp/en-US/xml_tmp/load-balancer-rules.xml - tmp/en-US/xml/load-balancer-rules.xml Processing file tmp/en-US/xml_tmp/log-in-root-admin.xml - tmp/en-US/xml/log-in-root-admin.xml Processing file tmp/en-US/xml_tmp/log-in.xml - tmp/en-US/xml/log-in.xml Processing file tmp/en-US/xml_tmp/long-running-job-events.xml - tmp/en-US/xml/long-running-job-events.xml Processing file tmp/en-US/xml_tmp/maintain-hypervisors-on-hosts.xml - tmp/en-US/xml/maintain-hypervisors-on-hosts.xml Processing file tmp/en-US/xml_tmp/maintenance-mode-for-primary-storage.xml - tmp/en-US/xml/maintenance-mode-for-primary-storage.xml Processing file tmp/en-US/xml_tmp/making-api-request.xml - tmp/en-US/xml/making-api-request.xml Processing file tmp/en-US/xml_tmp/manage-cloud.xml - tmp/en-US/xml/manage-cloud.xml
[jira] [Commented] (CLOUDSTACK-1237) Register Template fails with Cannot find template adapter for XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577452#comment-13577452 ] Rohit Yadav commented on CLOUDSTACK-1237: - Hi Hongfu thanks for your patch, I was in middle of working and testing the patch. Sorry I could n't see the review and went ahead to commit the fix. Register Template fails with Cannot find template adapter for XenServer - Key: CLOUDSTACK-1237 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1237 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Environment: RHEL 6.3, XenServer 5.6 Reporter: Sowmya Krishnan Assignee: Anthony Xu Priority: Blocker Fix For: 4.1.0 Attachments: mslog_1237 I am trying to Register a custom rhel template. It's unable to find the template adapter. This is with latest off 4.1 branch. I am using a private build that uses CentOS packaging. I am trying to run this on Rhel 6.3 with Xenserver 5.6. Although this looks related to https://issues.apache.org/jira/browse/CLOUDSTACK-1070 I am not very sure. Exception: 2013-02-12 12:30:26,465 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null) ===START=== 10.144.7.15 -- GET command=registerTemplateresponse=jsonsessionkey=GwJQ8fFTEJsC%2BXurGG3sRXalpMs %3Dname=Rhel.vhddisplayText=RHEl+ws+templateurl=http%3A%2F%2F10.144.7.15%2FRef_106.vhdzoneid=3785b828-93d7-45cc-84df-9f4ec53ef3afformat=VHDisextractable=falsepasswordEnabled=falseos TypeId=0a5a3e9e-7439-11e2-8735-ca9c098803afhypervisor=XenServerispublic=trueisfeatured=true_=1360652434419 2013-02-12 12:30:26,521 ERROR [cloud.api.ApiServer] (catalina-exec-15:null) unhandled exception executing api command: registerTemplate com.cloud.utils.exception.CloudRuntimeException: Cannot find template adapter for XenServer at com.cloud.template.TemplateManagerImpl.getAdapter(TemplateManagerImpl.java:192) at com.cloud.template.TemplateManagerImpl.registerTemplate(TemplateManagerImpl.java:221) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at
[jira] [Commented] (CLOUDSTACK-1237) Register Template fails with Cannot find template adapter for XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577454#comment-13577454 ] ASF subversion and git services commented on CLOUDSTACK-1237: - Commit ce46821b4a33e77cf4e705545fec1ed84ddcdea7 in branch refs/heads/4.1 from [~bhaisaab] [ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=ce46821 ] CLOUDSTACK-1237: Fix an overriding method that would help find template adapter Signed-off-by: Rohit Yadav bhais...@apache.org (cherry picked from commit fcb4b7a6a7e646c5e3cd7961336258a3d30d6abc) Signed-off-by: Rohit Yadav bhais...@apache.org Register Template fails with Cannot find template adapter for XenServer - Key: CLOUDSTACK-1237 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1237 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Environment: RHEL 6.3, XenServer 5.6 Reporter: Sowmya Krishnan Assignee: Anthony Xu Priority: Blocker Fix For: 4.1.0 Attachments: mslog_1237 I am trying to Register a custom rhel template. It's unable to find the template adapter. This is with latest off 4.1 branch. I am using a private build that uses CentOS packaging. I am trying to run this on Rhel 6.3 with Xenserver 5.6. Although this looks related to https://issues.apache.org/jira/browse/CLOUDSTACK-1070 I am not very sure. Exception: 2013-02-12 12:30:26,465 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null) ===START=== 10.144.7.15 -- GET command=registerTemplateresponse=jsonsessionkey=GwJQ8fFTEJsC%2BXurGG3sRXalpMs %3Dname=Rhel.vhddisplayText=RHEl+ws+templateurl=http%3A%2F%2F10.144.7.15%2FRef_106.vhdzoneid=3785b828-93d7-45cc-84df-9f4ec53ef3afformat=VHDisextractable=falsepasswordEnabled=falseos TypeId=0a5a3e9e-7439-11e2-8735-ca9c098803afhypervisor=XenServerispublic=trueisfeatured=true_=1360652434419 2013-02-12 12:30:26,521 ERROR [cloud.api.ApiServer] (catalina-exec-15:null) unhandled exception executing api command: registerTemplate com.cloud.utils.exception.CloudRuntimeException: Cannot find template adapter for XenServer at com.cloud.template.TemplateManagerImpl.getAdapter(TemplateManagerImpl.java:192) at com.cloud.template.TemplateManagerImpl.registerTemplate(TemplateManagerImpl.java:221) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at
[jira] [Resolved] (CLOUDSTACK-1237) Register Template fails with Cannot find template adapter for XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav resolved CLOUDSTACK-1237. - Resolution: Fixed Assignee: Rohit Yadav (was: Anthony Xu) Fixed on master and 4.1, please reopen if there is any other issue. Register Template fails with Cannot find template adapter for XenServer - Key: CLOUDSTACK-1237 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1237 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Environment: RHEL 6.3, XenServer 5.6 Reporter: Sowmya Krishnan Assignee: Rohit Yadav Priority: Blocker Fix For: 4.1.0 Attachments: mslog_1237 I am trying to Register a custom rhel template. It's unable to find the template adapter. This is with latest off 4.1 branch. I am using a private build that uses CentOS packaging. I am trying to run this on Rhel 6.3 with Xenserver 5.6. Although this looks related to https://issues.apache.org/jira/browse/CLOUDSTACK-1070 I am not very sure. Exception: 2013-02-12 12:30:26,465 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null) ===START=== 10.144.7.15 -- GET command=registerTemplateresponse=jsonsessionkey=GwJQ8fFTEJsC%2BXurGG3sRXalpMs %3Dname=Rhel.vhddisplayText=RHEl+ws+templateurl=http%3A%2F%2F10.144.7.15%2FRef_106.vhdzoneid=3785b828-93d7-45cc-84df-9f4ec53ef3afformat=VHDisextractable=falsepasswordEnabled=falseos TypeId=0a5a3e9e-7439-11e2-8735-ca9c098803afhypervisor=XenServerispublic=trueisfeatured=true_=1360652434419 2013-02-12 12:30:26,521 ERROR [cloud.api.ApiServer] (catalina-exec-15:null) unhandled exception executing api command: registerTemplate com.cloud.utils.exception.CloudRuntimeException: Cannot find template adapter for XenServer at com.cloud.template.TemplateManagerImpl.getAdapter(TemplateManagerImpl.java:192) at com.cloud.template.TemplateManagerImpl.registerTemplate(TemplateManagerImpl.java:221) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
Re: Review Request: fix bug 1237 and 1240 : Register Template fails with Cannot find template adapter for XenServer
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9420/#review16509 --- This fix would have worked for Hypervisor but would have failed for baremetal... if we fix like this, there may be other template adapters whose class (simple) names. So, it was better to impl getName() for all implementing template adapters. Hongfu thank you for your patch, I was in middle of working and testing the patch and went ahead to commit the fix. - Rohit Yadav On Feb. 13, 2013, 5:07 a.m., Hongtu Zang wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9420/ --- (Updated Feb. 13, 2013, 5:07 a.m.) Review request for cloudstack, mice xia, anthony xu, and SrikanteswaraRao Talluri. Description --- In TemplateManagerImpl.java, function getAdapter(), TemplateAdapterType.Hypervisor.getName() returns HyervisorAdapter, while it should returns HyervisorTemplateAdapter. So, in AdapterBase.java function getAdapterByName() returns null. This addresses bugs CLOUDSTACK-1237 and CLOUDSTACK-1240. Diffs - server/src/com/cloud/template/TemplateAdapter.java 19cfef0 Diff: https://reviews.apache.org/r/9420/diff/ Testing --- register a template and start a vm. success. Thanks, Hongtu Zang
[jira] [Closed] (CLOUDSTACK-1240) Unable to registerTemplate : Cannot find template adapter for XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav closed CLOUDSTACK-1240. --- Assignee: Rohit Yadav 4.1.0 duplicate, closing the issue. Pl. follow the same bug and fix on CLOUDSTACK-1237. Unable to registerTemplate : Cannot find template adapter for XenServer --- Key: CLOUDSTACK-1240 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1240 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.1.0 Environment: ms: rhel6.3 hypervisor: Xenserver6.1 advanced zone Reporter: Srikanteswararao Talluri Assignee: Rohit Yadav Priority: Blocker Fix For: 4.1.0 unhandled exception executing api command: registerTemplate com.cloud.utils.exception.CloudRuntimeException: Cannot find template adapter for XenServer at com.cloud.template.TemplateManagerImpl.getAdapter(TemplateManagerImpl.java:192) at com.cloud.template.TemplateManagerImpl.registerTemplate(TemplateManagerImpl.java:221) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41) at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at org.apache.cloudstack.api.command.user.template.RegisterTemplateCmd.execute(RegisterTemplateCmd.java:229) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.utils.db.TransactionContextBuilder.invoke(TransactionContextBuilder.java:60) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:159) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at
Duplicate BareMetalTemplateAdapter classes
Hi Frank, Can you check why we have two BareMetalTemplateAdapter; ./plugins/hypervisors/baremetal/src/com/cloud/baremetal/manager/BareMetalTemplateAdapter.java (Found no usage across codebase, removable?) ./server/src/com/cloud/baremetal/BareMetalTemplateAdapter.java (only this one is used, as spring would instantiate only this one with @Component annotation) And remove one which is redundant code? Found this while fixing CLOUDSTACK-1237. Regards. On Wed, Feb 13, 2013 at 3:26 PM, Rohit Yadav bhais...@apache.org wrote: This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9420/ This fix would have worked for Hypervisor but would have failed for baremetal... if we fix like this, there may be other template adapters whose class (simple) names. So, it was better to impl getName() for all implementing template adapters. Hongfu thank you for your patch, I was in middle of working and testing the patch and went ahead to commit the fix. - Rohit On February 13th, 2013, 5:07 a.m., Hongtu Zang wrote: Review request for cloudstack, mice xia, anthony xu, and SrikanteswaraRao Talluri. By Hongtu Zang. *Updated Feb. 13, 2013, 5:07 a.m.* Description In TemplateManagerImpl.java, function getAdapter(), TemplateAdapterType.Hypervisor.getName() returns HyervisorAdapter, while it should returns HyervisorTemplateAdapter. So, in AdapterBase.java function getAdapterByName() returns null. Testing register a template and start a vm. success. *Bugs: * CLOUDSTACK-1237, CLOUDSTACK-1240 Diffs - server/src/com/cloud/template/TemplateAdapter.java (19cfef0) View Diff https://reviews.apache.org/r/9420/diff/
Re: Build failed in Jenkins: build-docs-install-master #763
Cool, pl. backport whatever changes are missing in either branches, keep 'em in sync :) Thanks. On Wed, Feb 13, 2013 at 3:15 PM, Pranav Saxena pranav.sax...@citrix.com wrote: Thanks Rohit for pointing that out. Build is back to normal now . -Original Message- From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf Of Rohit Yadav Sent: Wednesday, February 13, 2013 2:37 PM To: cloudstack-dev@incubator.apache.org Subject: Build failed in Jenkins: build-docs-install-master #763 Something went wrong with: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commit;h=eaf7767c8521e88f9d5b6f2865acafd34f9430fe Regards. -- Forwarded message -- From: jenk...@cloudstack.org Date: Wed, Feb 13, 2013 at 1:58 PM Subject: Build failed in Jenkins: build-docs-install-master #763 To: cloudstack-comm...@incubator.apache.org, bhais...@apache.org, pranav.sax...@citrix.com See http://jenkins.cloudstack.org/job/build-docs-install-master/763/changes Changes: [Rohit Yadav] maven: build client at the end, fixes path error for console-proxy build target -- [...truncated 249 lines...] Processing file tmp/en-US/xml_tmp/hypervisor-installation.xml - tmp/en-US/xml/hypervisor-installation.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-install-flow.xml - tmp/en-US/xml/hypervisor-kvm-install-flow.xml Processing file tmp/en-US/xml_tmp/hypervisor-kvm-requirements.xml - tmp/en-US/xml/hypervisor-kvm-requirements.xml Processing file tmp/en-US/xml_tmp/hypervisor-support-for-primarystorage.xml - tmp/en-US/xml/hypervisor-support-for-primarystorage.xml Processing file tmp/en-US/xml_tmp/import-ami.xml - tmp/en-US/xml/import-ami.xml Processing file tmp/en-US/xml_tmp/increase-management-server-max-memory.xml - tmp/en-US/xml/increase-management-server-max-memory.xml Processing file tmp/en-US/xml_tmp/incremental-snapshots-backup.xml - tmp/en-US/xml/incremental-snapshots-backup.xml Processing file tmp/en-US/xml_tmp/initial-setup-of-external-firewalls-loadbalancers.xml - tmp/en-US/xml/initial-setup-of-external-firewalls-loadbalancers.xml Processing file tmp/en-US/xml_tmp/initialize-and-test.xml - tmp/en-US/xml/initialize-and-test.xml Processing file tmp/en-US/xml_tmp/install-usage-server.xml - tmp/en-US/xml/install-usage-server.xml Processing file tmp/en-US/xml_tmp/installation-complete.xml - tmp/en-US/xml/installation-complete.xml Processing file tmp/en-US/xml_tmp/installation-steps-overview.xml - tmp/en-US/xml/installation-steps-overview.xml Processing file tmp/en-US/xml_tmp/installation.xml - tmp/en-US/xml/installation.xml Processing file tmp/en-US/xml_tmp/installation_steps_overview.xml - tmp/en-US/xml/installation_steps_overview.xml Processing file tmp/en-US/xml_tmp/installing-publican.xml - tmp/en-US/xml/installing-publican.xml Processing file tmp/en-US/xml_tmp/inter-vlan-routing.xml - tmp/en-US/xml/inter-vlan-routing.xml Processing file tmp/en-US/xml_tmp/introduction.xml - tmp/en-US/xml/introduction.xml Processing file tmp/en-US/xml_tmp/ip-forwarding-firewalling.xml - tmp/en-US/xml/ip-forwarding-firewalling.xml Processing file tmp/en-US/xml_tmp/ip-load-balancing.xml - tmp/en-US/xml/ip-load-balancing.xml Processing file tmp/en-US/xml_tmp/ipaddress-usage-record-format.xml - tmp/en-US/xml/ipaddress-usage-record-format.xml Processing file tmp/en-US/xml_tmp/isolated-networks.xml - tmp/en-US/xml/isolated-networks.xml Processing file tmp/en-US/xml_tmp/job-status.xml - tmp/en-US/xml/job-status.xml Processing file tmp/en-US/xml_tmp/kvm-topology-req.xml - tmp/en-US/xml/kvm-topology-req.xml Processing file tmp/en-US/xml_tmp/large_scale_redundant_setup.xml - tmp/en-US/xml/large_scale_redundant_setup.xml Processing file tmp/en-US/xml_tmp/layer2-switch.xml - tmp/en-US/xml/layer2-switch.xml Processing file tmp/en-US/xml_tmp/lb-policy-pfwd-rule-usage-record-format.xml - tmp/en-US/xml/lb-policy-pfwd-rule-usage-record-format.xml Processing file tmp/en-US/xml_tmp/linux-installation.xml - tmp/en-US/xml/linux-installation.xml Processing file tmp/en-US/xml_tmp/load-balancer-rules.xml - tmp/en-US/xml/load-balancer-rules.xml Processing file tmp/en-US/xml_tmp/log-in-root-admin.xml - tmp/en-US/xml/log-in-root-admin.xml Processing file tmp/en-US/xml_tmp/log-in.xml - tmp/en-US/xml/log-in.xml Processing file tmp/en-US/xml_tmp/long-running-job-events.xml - tmp/en-US/xml/long-running-job-events.xml Processing file tmp/en-US/xml_tmp/maintain-hypervisors-on-hosts.xml - tmp/en-US/xml/maintain-hypervisors-on-hosts.xml Processing file
Re: Review Request: Documentation on Persistent Network
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9421/ --- (Updated Feb. 13, 2013, 10:03 a.m.) Review request for cloudstack, David Nalley, Chip Childers, Jessica Tomechak, Likitha Shetty, and Joe Brockmeier. Changes --- 1. Updated the diff. This new patch should not break the build. I added a conditional tag to creating-network-offerings.xml file so that it would not break install guide. This section is not part of the Install Guide on the master. Need to fix. I tested my changes against the wrong set of Install guide files, which showed that the doc builds just fine! Mistake from my part. 2. Created a new patch against 4.1 branch, mainly because the creating-network-offerings.xml is different on 4.1. There are many changes went into 4.1 but not on master. Please merge in master. Please make sure that my changes are not over-written. Sorry Pranav for the double work. Thanks Rohit for reporting the issue Description --- Documentation changes for the feature Persistent Network. The document describes what is Persistent Networks, how to configure one, and the advantages. This addresses bug CLOUDSTACK-852. Diffs (updated) - docs/en-US/creating-network-offerings.xml 0269ce0 docs/en-US/networks.xml a7b9ea1 docs/en-US/persistent-network.xml PRE-CREATION Diff: https://reviews.apache.org/r/9421/diff/ Testing --- Patch cleanly applies. The initial tech review is done by the developer. Build fine for both Admin and Install Guides. Thanks, Radhika PC
[jira] [Created] (CLOUDSTACK-1255) Admin Guide and Install Guide Need a Revamp: Some Sections Are Common
Radhika Nair created CLOUDSTACK-1255: Summary: Admin Guide and Install Guide Need a Revamp: Some Sections Are Common Key: CLOUDSTACK-1255 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1255 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: Future Some sections are common across the guides. For example: Managing Networks and Traffic Probably, the Networking sections need a restructuring across the guides. The guides need to be re-looked and revamped. -- 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-1070) javelin: NPE on executing registerIso API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577470#comment-13577470 ] ASF subversion and git services commented on CLOUDSTACK-1070: - Commit 7401b06cb199037006a3991b944e0fbde730e04c in branch refs/heads/master from [~bhaisaab] [ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=7401b06 ] CLOUDSTACK-1070: Don't create HyervisorTemplateAdapter bean, it's already a @Component The issue was completely different than a spring injection issue Signed-off-by: Rohit Yadav bhais...@apache.org javelin: NPE on executing registerIso API - Key: CLOUDSTACK-1070 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1070 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Prasanna Santhanam Assignee: Kelven Yang Fix For: 4.1.0 Following NPE was noticed when registering an damn-small linux ISO on javelin running with devcloud 2013-01-26 13:11:24,889 DEBUG [cloud.api.ApiServlet] (1572716377@qtp-588170311-2:null) ===START=== 127.0.0.1 -- GET account=test-GNFNS4apiKey=yJ-FacgjPkYyQxwt28hAkf9aNjIOEiAAUiG0CAa8NP24A4Bdn2f9DvxoFLE4fnY16FBIJnakC4itJDEmBwKaQgcommand=registerIsodisplaytext=Test+ISO+2domainid=ceef2d20-678a-11e2-a987-691e5966f392isextractable=Trueisfeatured=Trueispublic=Truename=ISO+2ostypeid=ce611ba2-678a-11e2-a987-691e5966f392response=jsonurl=http%3A%2F%2Fiso.linuxquestions.org%2Fdownload%2F504%2F1819%2Fhttp%2Fgd4.tuwien.ac.at%2Fdsl-4.4.10.isozoneid=588cd04f-a451-484b-adbf-7ebc686d32efsignature=4iLl5oM%2FAq0wLX8kFOG9xd0n8%2Bg%3D 2013-01-26 13:11:24,936 ERROR [cloud.api.ApiServer] (1572716377@qtp-588170311-2:null) unhandled exception executing api command: registerIso java.lang.NullPointerException at com.cloud.utils.component.AdapterBase.getAdapterByName(AdapterBase.java:57) at com.cloud.template.TemplateManagerImpl.getAdapter(TemplateManagerImpl.java:222) at com.cloud.template.TemplateManagerImpl.registerIso(TemplateManagerImpl.java:235) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at
[jira] [Commented] (CLOUDSTACK-1070) javelin: NPE on executing registerIso API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577472#comment-13577472 ] ASF subversion and git services commented on CLOUDSTACK-1070: - Commit 0119d223705a1e1b285f0d28db7e57d540a81cdc in branch refs/heads/4.1 from [~bhaisaab] [ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=0119d22 ] CLOUDSTACK-1070: Don't create HyervisorTemplateAdapter bean, it's already a @Component The issue was completely different than a spring injection issue Signed-off-by: Rohit Yadav bhais...@apache.org (cherry picked from commit 7401b06cb199037006a3991b944e0fbde730e04c) Signed-off-by: Rohit Yadav bhais...@apache.org javelin: NPE on executing registerIso API - Key: CLOUDSTACK-1070 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1070 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Prasanna Santhanam Assignee: Kelven Yang Fix For: 4.1.0 Following NPE was noticed when registering an damn-small linux ISO on javelin running with devcloud 2013-01-26 13:11:24,889 DEBUG [cloud.api.ApiServlet] (1572716377@qtp-588170311-2:null) ===START=== 127.0.0.1 -- GET account=test-GNFNS4apiKey=yJ-FacgjPkYyQxwt28hAkf9aNjIOEiAAUiG0CAa8NP24A4Bdn2f9DvxoFLE4fnY16FBIJnakC4itJDEmBwKaQgcommand=registerIsodisplaytext=Test+ISO+2domainid=ceef2d20-678a-11e2-a987-691e5966f392isextractable=Trueisfeatured=Trueispublic=Truename=ISO+2ostypeid=ce611ba2-678a-11e2-a987-691e5966f392response=jsonurl=http%3A%2F%2Fiso.linuxquestions.org%2Fdownload%2F504%2F1819%2Fhttp%2Fgd4.tuwien.ac.at%2Fdsl-4.4.10.isozoneid=588cd04f-a451-484b-adbf-7ebc686d32efsignature=4iLl5oM%2FAq0wLX8kFOG9xd0n8%2Bg%3D 2013-01-26 13:11:24,936 ERROR [cloud.api.ApiServer] (1572716377@qtp-588170311-2:null) unhandled exception executing api command: registerIso java.lang.NullPointerException at com.cloud.utils.component.AdapterBase.getAdapterByName(AdapterBase.java:57) at com.cloud.template.TemplateManagerImpl.getAdapter(TemplateManagerImpl.java:222) at com.cloud.template.TemplateManagerImpl.registerIso(TemplateManagerImpl.java:235) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at
[jira] [Commented] (CLOUDSTACK-1070) javelin: NPE on executing registerIso API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577473#comment-13577473 ] Rohit Yadav commented on CLOUDSTACK-1070: - Kelven, I fixed CLOUDSTACK-1237 and found that adding the component in xml is not the right fix. It was already having the @Component annotation. The problem was no adapter was returned as getName() was not implemented by the implementing adapter which should return one of the static class's attributes. I found that it was sort of a regression due to the baremetal merge. javelin: NPE on executing registerIso API - Key: CLOUDSTACK-1070 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1070 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Prasanna Santhanam Assignee: Kelven Yang Fix For: 4.1.0 Following NPE was noticed when registering an damn-small linux ISO on javelin running with devcloud 2013-01-26 13:11:24,889 DEBUG [cloud.api.ApiServlet] (1572716377@qtp-588170311-2:null) ===START=== 127.0.0.1 -- GET account=test-GNFNS4apiKey=yJ-FacgjPkYyQxwt28hAkf9aNjIOEiAAUiG0CAa8NP24A4Bdn2f9DvxoFLE4fnY16FBIJnakC4itJDEmBwKaQgcommand=registerIsodisplaytext=Test+ISO+2domainid=ceef2d20-678a-11e2-a987-691e5966f392isextractable=Trueisfeatured=Trueispublic=Truename=ISO+2ostypeid=ce611ba2-678a-11e2-a987-691e5966f392response=jsonurl=http%3A%2F%2Fiso.linuxquestions.org%2Fdownload%2F504%2F1819%2Fhttp%2Fgd4.tuwien.ac.at%2Fdsl-4.4.10.isozoneid=588cd04f-a451-484b-adbf-7ebc686d32efsignature=4iLl5oM%2FAq0wLX8kFOG9xd0n8%2Bg%3D 2013-01-26 13:11:24,936 ERROR [cloud.api.ApiServer] (1572716377@qtp-588170311-2:null) unhandled exception executing api command: registerIso java.lang.NullPointerException at com.cloud.utils.component.AdapterBase.getAdapterByName(AdapterBase.java:57) at com.cloud.template.TemplateManagerImpl.getAdapter(TemplateManagerImpl.java:222) at com.cloud.template.TemplateManagerImpl.registerIso(TemplateManagerImpl.java:235) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.event.ActionEventInterceptor.AroundAnyMethod(ActionEventInterceptor.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at
Regarding cpu and ram overcommit feature
Hi All, After some discussion i think the new overcommit ratio should not affect the VMs already deployed. It will only effect the VMs deployed after the change. I we need to reconfigure the previously running VMs we need to stop start them. I will call this out in the Functional spec. Bharat.
Re: Review Request: fix bug 1237 and 1240 : Register Template fails with Cannot find template adapter for XenServer
On Feb. 13, 2013, 9:56 a.m., Rohit Yadav wrote: This fix would have worked for Hypervisor but would have failed for baremetal... if we fix like this, there may be other template adapters whose class (simple) names. So, it was better to impl getName() for all implementing template adapters. Hongfu thank you for your patch, I was in middle of working and testing the patch and went ahead to commit the fix. Yes, I haven't note about baremetal. It should use BareMetalTemplateAdapter instead of BareMetalAdapter. But I cannot test it now. can you test it? I will update the patch. - Hongtu --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9420/#review16509 --- On Feb. 13, 2013, 5:07 a.m., Hongtu Zang wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9420/ --- (Updated Feb. 13, 2013, 5:07 a.m.) Review request for cloudstack, mice xia, anthony xu, and SrikanteswaraRao Talluri. Description --- In TemplateManagerImpl.java, function getAdapter(), TemplateAdapterType.Hypervisor.getName() returns HyervisorAdapter, while it should returns HyervisorTemplateAdapter. So, in AdapterBase.java function getAdapterByName() returns null. This addresses bugs CLOUDSTACK-1237 and CLOUDSTACK-1240. Diffs - server/src/com/cloud/template/TemplateAdapter.java 19cfef0 Diff: https://reviews.apache.org/r/9420/diff/ Testing --- register a template and start a vm. success. Thanks, Hongtu Zang
Re: Review Request: fix bug 1237 and 1240 : Register Template fails with Cannot find template adapter for XenServer
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9420/ --- (Updated Feb. 13, 2013, 10:57 a.m.) Review request for cloudstack, mice xia, anthony xu, and SrikanteswaraRao Talluri. Changes --- update the patch. correct BareMetalAdapter into BareMetalTemplateAdapter for the failure of baremetal. Description --- In TemplateManagerImpl.java, function getAdapter(), TemplateAdapterType.Hypervisor.getName() returns HyervisorAdapter, while it should returns HyervisorTemplateAdapter. So, in AdapterBase.java function getAdapterByName() returns null. This addresses bugs CLOUDSTACK-1237 and CLOUDSTACK-1240. Diffs (updated) - server/src/com/cloud/template/TemplateAdapter.java 19cfef0 Diff: https://reviews.apache.org/r/9420/diff/ Testing --- register a template and start a vm. success. Thanks, Hongtu Zang
Re: Review Request: Utility for generating the .tx/config file
Sorry I've been off the grid, incredibly busy. I will close the ticket as soon as I get a chance. This week is a write off for me getting anything done. Sent from my iPhone On Feb 12, 2013, at 10:11 PM, Animesh Chaturvedi animesh.chaturv...@citrix.com wrote: Sebstien, Kelcey thanks for bringing this to closure -Original Message- From: Sebastien Goasguen [mailto:nore...@reviews.apache.org] On Behalf Of Sebastien Goasguen Sent: Tuesday, February 12, 2013 12:58 AM To: Kelcey Jamison-Damage; Sebastien Goasguen; cloudstack Subject: Re: Review Request: Utility for generating the .tx/config file --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/8307/#review16463 --- This is not needed anymore since we agreed to a maximum of 50 char for basename. We can use transifex client to do it. Kelcey can you discard your patch and close it. thanks - Sebastien Goasguen On Dec. 2, 2012, 1:29 a.m., Kelcey Jamison-Damage wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/8307/ --- (Updated Dec. 2, 2012, 1:29 a.m.) Review request for cloudstack. Description --- Utility for generating the .tx/config file Long names are truncated and suffixed with -long, and duplicates are numerically tagged. Diffs - docs/doc-config-gen.py PRE-CREATION Diff: https://reviews.apache.org/r/8307/diff/ Testing --- tested against dupes and long names in en-US. uses relative paths so must be executed from /docs Thanks, Kelcey Jamison-Damage
Re: Regarding cpu and ram overcommit feature
As part of the current implementation changing the overcommit ratio will not have immediate affect on the VM already running. -abhi On 13/02/13 4:19 PM, Bharat Kumar bharat.ku...@citrix.com wrote: Hi All, After some discussion i think the new overcommit ratio should not affect the VMs already deployed. It will only effect the VMs deployed after the change. I we need to reconfigure the previously running VMs we need to stop start them. I will call this out in the Functional spec. Bharat.
[jira] [Updated] (CLOUDSTACK-811) Document Additional VMX Settings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-811: Status: Ready To Review (was: In Progress) Document Additional VMX Settings Key: CLOUDSTACK-811 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-811 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: 4.1.0 document additional vmx settings -- 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
Review Request: The developer guide has been updated for the 4.1 release. Added new and changed APIs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9423/ --- Review request for cloudstack, David Nalley, Venkata Siva Vijayendra Bhamidipati, Jessica Tomechak, and Joe Brockmeier. Description --- The following sections have been added: 4.1. What's New in the API for 4.1 4.1.1. Additional VMX Settings 4.1.2. Resetting SSH Keys to Access VMs 4.1.3. Changed API Commands in 4.1-incubating 4.1.4. Added API Commands in 4.1-incubating This addresses bugs CLOUDSTACK-1087 and CLOUDSTACK-811. Diffs - docs/en-US/added-API-commands-4-1.xml PRE-CREATION docs/en-US/changed-apicommands-4.1.xml PRE-CREATION docs/en-US/reset-ssh-key-dev.xml PRE-CREATION docs/en-US/vmx-settings-dev.xml PRE-CREATION docs/en-US/whats-new.xml 77b3ec3 Diff: https://reviews.apache.org/r/9423/diff/ Testing --- Tested against Master: git am patch-name Publican tested: publican build --langs=en-US --formats=html-single --config publican-devguide.cfg Thanks, Radhika PC
[jira] [Commented] (CLOUDSTACK-1087) Update the Developer Guide for ASFCS 4.1 Release
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577493#comment-13577493 ] Radhika Nair commented on CLOUDSTACK-1087: -- https://reviews.apache.org/r/9423/ Update the Developer Guide for ASFCS 4.1 Release Key: CLOUDSTACK-1087 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1087 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.1.0 Update the developer guide: What's New New APIs Changed APIs Removed APIs -- 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-811) Document Additional VMX Settings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577492#comment-13577492 ] Radhika Nair commented on CLOUDSTACK-811: - https://reviews.apache.org/r/9423/ Document Additional VMX Settings Key: CLOUDSTACK-811 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-811 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: 4.1.0 document additional vmx settings -- 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-1087) Update the Developer Guide for ASFCS 4.1 Release
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-1087: - Status: Ready To Review (was: In Progress) Update the Developer Guide for ASFCS 4.1 Release Key: CLOUDSTACK-1087 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1087 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair Fix For: 4.1.0 Update the developer guide: What's New New APIs Changed APIs Removed APIs -- 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
Re: Review Request: fix bug 1237 and 1240 : Register Template fails with Cannot find template adapter for XenServer
On Feb. 13, 2013, 9:56 a.m., Rohit Yadav wrote: This fix would have worked for Hypervisor but would have failed for baremetal... if we fix like this, there may be other template adapters whose class (simple) names. So, it was better to impl getName() for all implementing template adapters. Hongfu thank you for your patch, I was in middle of working and testing the patch and went ahead to commit the fix. Hongtu Zang wrote: Yes, I haven't note about baremetal. It should use BareMetalTemplateAdapter instead of BareMetalAdapter. But I cannot test it now. can you test it? I will update the patch. Thanks, but changing the string won't be correct fix. Say there is another class implementation of TemplateAdapter which is of HypervisorAdapter type but has a different impl, in that case that class may have a different class name but we want that the getName() used in BaseAdapter to get the name returns one of these template types, i.e. name which is static var in TemplateAdapter. I've already fixed this issue on master and 4.1 in this way. You may resend a patch if there is another better way, or submit the review to close it. Thanks. - Rohit --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9420/#review16509 --- On Feb. 13, 2013, 10:57 a.m., Hongtu Zang wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9420/ --- (Updated Feb. 13, 2013, 10:57 a.m.) Review request for cloudstack, mice xia, anthony xu, and SrikanteswaraRao Talluri. Description --- In TemplateManagerImpl.java, function getAdapter(), TemplateAdapterType.Hypervisor.getName() returns HyervisorAdapter, while it should returns HyervisorTemplateAdapter. So, in AdapterBase.java function getAdapterByName() returns null. This addresses bugs CLOUDSTACK-1237 and CLOUDSTACK-1240. Diffs - server/src/com/cloud/template/TemplateAdapter.java 19cfef0 Diff: https://reviews.apache.org/r/9420/diff/ Testing --- register a template and start a vm. success. Thanks, Hongtu Zang
Re: Review Request: The developer guide has been updated for the 4.1 release. Added new and changed APIs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9423/ --- (Updated Feb. 13, 2013, 11:31 a.m.) Review request for cloudstack, David Nalley, Venkata Siva Vijayendra Bhamidipati, Jessica Tomechak, and Joe Brockmeier. Changes --- Adding another patch that took against branch 4.1 Description --- The following sections have been added: 4.1. What's New in the API for 4.1 4.1.1. Additional VMX Settings 4.1.2. Resetting SSH Keys to Access VMs 4.1.3. Changed API Commands in 4.1-incubating 4.1.4. Added API Commands in 4.1-incubating This addresses bugs CLOUDSTACK-1087 and CLOUDSTACK-811. Diffs - docs/en-US/added-API-commands-4-1.xml PRE-CREATION docs/en-US/changed-apicommands-4.1.xml PRE-CREATION docs/en-US/reset-ssh-key-dev.xml PRE-CREATION docs/en-US/vmx-settings-dev.xml PRE-CREATION docs/en-US/whats-new.xml 77b3ec3 Diff: https://reviews.apache.org/r/9423/diff/ Testing --- Tested against Master: git am patch-name Publican tested: publican build --langs=en-US --formats=html-single --config publican-devguide.cfg Thanks, Radhika PC
[jira] [Resolved] (CLOUDSTACK-800) documentation for SRX and F5 Inline Mode
[ https://issues.apache.org/jira/browse/CLOUDSTACK-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-800. - Resolution: Fixed patch has been submitted. documentation for SRX and F5 Inline Mode Key: CLOUDSTACK-800 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-800 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: 4.1.0 Document the support for SRX and F5 inline mode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-1245) Not able to install Debian based PV Instances from ISO,only HVM instances is possible.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin parker reopened CLOUDSTACK-1245:
--
It is possible to create PV Debian instances using xen centre
Not able to install Debian based PV Instances from ISO,only HVM instances is
possible.
--
Key: CLOUDSTACK-1245
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1245
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Install and Setup, ISO, XenServer
Affects Versions: 4.0.0, 4.0.1
Environment: CS 4.0.1.20130109153237, Xenserver 6.0.2-53456p,
Reporter: kevin parker
=Uploading ISO
Tried to upload ISO of Ubuntu 10.04 by filling necessary option and choose
Ubuntu 10.04 (64) as os type and uploaded from Ubuntu Official iso site.
=When Used that ISO to create instance/FAILED with
Error=
After Uploading, When tried to create VM with that iso its showing state as
error with error log saying:
error Info: [INVALID_SOURCE, Unable to access a required file in the
specified repository: file:///tmp/cdrom-repo-tkGltG/isolinux/vmlinuz., ]
but there is no such file or directory.
Work around=
Edited ISO image OS type from Ubuntu 10.04 to Other.
This time Instance got created but as HVM instance and not PV.
Full Log: http://pastebin.com/93UmqYUC
2013-02-12 14:11:06,975 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-485:null) Seq 1-362549166: Executing request
2013-02-12 14:11:17,253 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-02-12 14:11:17,452 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-02-12 14:11:18,419 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-485:null) Seq 1-362549166: Response Received:
2013-02-12 14:11:18,419 DEBUG [agent.transport.Request]
(DirectAgent-485:null) Seq 1-362549166: Processing: { Ans: , MgmtId:
173871959764157, via: 1, Ver: v1, Flags: 110,
[{Answer:{result:true,wait:0}},{Answer:{result:true,wait:0}}] }
2013-02-12 14:11:18,420 DEBUG [agent.manager.AgentAttache]
(DirectAgent-485:null) Seq 1-362549166: No more commands found
2013-02-12 14:11:18,420 DEBUG [agent.transport.Request]
(Job-Executor-58:job-91) Seq 1-362549166: Received: { Ans: , MgmtId:
173871959764157, via: 1, Ver: v1, Flags: 110, { Answer, Answer } }
2013-02-12 14:11:18,420 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking Ovs to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,420 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking ExternalDhcpServer to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,426 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers.
2013-02-12 14:11:18,428 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking BareMetal to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,428 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking SecurityGroupProvider to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking CiscoNexus1000vVSM to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking VpcVirtualRouter to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 WARN [network.element.VpcVirtualRouterElement]
(Job-Executor-58:job-91) Network Ntwk[204|Guest|6] is not associated with any
VPC
2013-02-12 14:11:18,439 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking NiciraNvp to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,449 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Checking if we need to prepare 1 volumes for
VM[User|ghgh]
2013-02-12 14:11:18,494 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Creating volume: Vol[37|vm=35|ROOT]
2013-02-12 14:11:18,494 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Trying to create in Pool[201|PreSetup]
2013-02-12 14:11:18,526 DEBUG [agent.transport.Request]
(Job-Executor-58:job-91) Seq 1-362549167: Sending { Cmd ,
[jira] [Issue Comment Deleted] (CLOUDSTACK-1245) Not able to install Debian based PV Instances from ISO,only HVM instances is possible.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin parker updated CLOUDSTACK-1245:
-
Comment: was deleted
(was: Seems issue with Ubuntu 10.04 support for xen,as it is not supported
natively,Not issue of Cloud stack)
Not able to install Debian based PV Instances from ISO,only HVM instances is
possible.
--
Key: CLOUDSTACK-1245
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1245
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Install and Setup, ISO, XenServer
Affects Versions: 4.0.0, 4.0.1
Environment: CS 4.0.1.20130109153237, Xenserver 6.0.2-53456p,
Reporter: kevin parker
=Uploading ISO
Tried to upload ISO of Ubuntu 10.04 by filling necessary option and choose
Ubuntu 10.04 (64) as os type and uploaded from Ubuntu Official iso site.
=When Used that ISO to create instance/FAILED with
Error=
After Uploading, When tried to create VM with that iso its showing state as
error with error log saying:
error Info: [INVALID_SOURCE, Unable to access a required file in the
specified repository: file:///tmp/cdrom-repo-tkGltG/isolinux/vmlinuz., ]
but there is no such file or directory.
Work around=
Edited ISO image OS type from Ubuntu 10.04 to Other.
This time Instance got created but as HVM instance and not PV.
Full Log: http://pastebin.com/93UmqYUC
2013-02-12 14:11:06,975 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-485:null) Seq 1-362549166: Executing request
2013-02-12 14:11:17,253 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-02-12 14:11:17,452 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-02-12 14:11:18,419 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-485:null) Seq 1-362549166: Response Received:
2013-02-12 14:11:18,419 DEBUG [agent.transport.Request]
(DirectAgent-485:null) Seq 1-362549166: Processing: { Ans: , MgmtId:
173871959764157, via: 1, Ver: v1, Flags: 110,
[{Answer:{result:true,wait:0}},{Answer:{result:true,wait:0}}] }
2013-02-12 14:11:18,420 DEBUG [agent.manager.AgentAttache]
(DirectAgent-485:null) Seq 1-362549166: No more commands found
2013-02-12 14:11:18,420 DEBUG [agent.transport.Request]
(Job-Executor-58:job-91) Seq 1-362549166: Received: { Ans: , MgmtId:
173871959764157, via: 1, Ver: v1, Flags: 110, { Answer, Answer } }
2013-02-12 14:11:18,420 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking Ovs to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,420 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking ExternalDhcpServer to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,426 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers.
2013-02-12 14:11:18,428 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking BareMetal to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,428 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking SecurityGroupProvider to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking CiscoNexus1000vVSM to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking VpcVirtualRouter to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 WARN [network.element.VpcVirtualRouterElement]
(Job-Executor-58:job-91) Network Ntwk[204|Guest|6] is not associated with any
VPC
2013-02-12 14:11:18,439 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking NiciraNvp to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,449 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Checking if we need to prepare 1 volumes for
VM[User|ghgh]
2013-02-12 14:11:18,494 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Creating volume: Vol[37|vm=35|ROOT]
2013-02-12 14:11:18,494 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Trying to create in Pool[201|PreSetup]
2013-02-12 14:11:18,526 DEBUG [agent.transport.Request]
[jira] [Updated] (CLOUDSTACK-1245) Not able to install Debian based PV Instances from ISO,only HVM instances is possible.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin parker updated CLOUDSTACK-1245:
-
Labels: Reproduceable (was: )
Not able to install Debian based PV Instances from ISO,only HVM instances is
possible.
--
Key: CLOUDSTACK-1245
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1245
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Hypervisor Controller, Install and Setup, ISO, XenServer
Affects Versions: 4.0.0, 4.0.1
Environment: CS 4.0.1.20130109153237, Xenserver 6.0.2-53456p,
Reporter: kevin parker
Labels: Reproduceable
=Uploading ISO
Tried to upload ISO of Ubuntu 10.04 by filling necessary option and choose
Ubuntu 10.04 (64) as os type and uploaded from Ubuntu Official iso site.
=When Used that ISO to create instance/FAILED with
Error=
After Uploading, When tried to create VM with that iso its showing state as
error with error log saying:
error Info: [INVALID_SOURCE, Unable to access a required file in the
specified repository: file:///tmp/cdrom-repo-tkGltG/isolinux/vmlinuz., ]
but there is no such file or directory.
Work around=
Edited ISO image OS type from Ubuntu 10.04 to Other.
This time Instance got created but as HVM instance and not PV.
Full Log: http://pastebin.com/93UmqYUC
2013-02-12 14:11:06,975 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-485:null) Seq 1-362549166: Executing request
2013-02-12 14:11:17,253 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-02-12 14:11:17,452 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-02-12 14:11:18,419 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-485:null) Seq 1-362549166: Response Received:
2013-02-12 14:11:18,419 DEBUG [agent.transport.Request]
(DirectAgent-485:null) Seq 1-362549166: Processing: { Ans: , MgmtId:
173871959764157, via: 1, Ver: v1, Flags: 110,
[{Answer:{result:true,wait:0}},{Answer:{result:true,wait:0}}] }
2013-02-12 14:11:18,420 DEBUG [agent.manager.AgentAttache]
(DirectAgent-485:null) Seq 1-362549166: No more commands found
2013-02-12 14:11:18,420 DEBUG [agent.transport.Request]
(Job-Executor-58:job-91) Seq 1-362549166: Received: { Ans: , MgmtId:
173871959764157, via: 1, Ver: v1, Flags: 110, { Answer, Answer } }
2013-02-12 14:11:18,420 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking Ovs to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,420 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking ExternalDhcpServer to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,426 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers.
2013-02-12 14:11:18,428 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking BareMetal to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,428 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking SecurityGroupProvider to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking CiscoNexus1000vVSM to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking VpcVirtualRouter to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 WARN [network.element.VpcVirtualRouterElement]
(Job-Executor-58:job-91) Network Ntwk[204|Guest|6] is not associated with any
VPC
2013-02-12 14:11:18,439 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking NiciraNvp to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,449 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Checking if we need to prepare 1 volumes for
VM[User|ghgh]
2013-02-12 14:11:18,494 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Creating volume: Vol[37|vm=35|ROOT]
2013-02-12 14:11:18,494 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Trying to create in Pool[201|PreSetup]
2013-02-12 14:11:18,526 DEBUG [agent.transport.Request]
(Job-Executor-58:job-91) Seq 1-362549167: Sending { Cmd , MgmtId:
Review Request: CLOUDSTACK-1201: fix for failed to create ssh key for cloud
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/9424/ --- Review request for cloudstack and Hugo Trippaers. Description --- packaging: rpm setting the homedir of user cloud cloud.spec changed to fix the packaging issue for user cloud. cloud has homedir set to /var/cloudstack/management after this fix. This addresses bug CLOUDSTACK-1201. Diffs - packaging/centos63/cloud.spec 7a740a6 Diff: https://reviews.apache.org/r/9424/diff/ Testing --- deployed the package on to fresh centos 6.3 VM and private key generates successfully as well as 8096 port opens up after restart of cloudstack-management Thanks, Prasanna Santhanam
Re: [DISCUSS] Correctly fix cloud- to cloudstack- rename refactoring
I'm OK with it, as long as the name changes are tested well before they're committed. We've just about got the current naming changes fixed, wouldn't want to break it again. As Nitin in says, probably low priority at the moment. On Feb 12, 2013 11:36 PM, Rohit Yadav bhais...@apache.org wrote: Pl. rename any script references which have renamed from cloud- to cloudstack- in docs, code and elsewhere? Since we're renaming the packages to cloudstack- why not rename artifacts to cloudstack- as well? Regards.
[jira] [Commented] (CLOUDSTACK-1088) EnableStaticNat error will clear the data in database
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577539#comment-13577539 ] ASF subversion and git services commented on CLOUDSTACK-1088: - Commit 2e2ee2f3ed389b1b1a8a89eae8a641314417ca83 in branch refs/heads/master from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=2e2ee2f ] CLOUDSTACK-1088: EnableStaticNat error will clear the data in database The issue occur in two conditions (1) If I use two sessions or browsers to EnableStaticNat on CloudStack UI. one is successful, the other is failed. However, there is no ip in database. (2) If I use API call EnableStaticNat several times The first time succeed, the second failed, the third succeed. the result is success-fail-success-fail-success-fail, which it is not correct. Reported-by: Wei Zhou w.z...@leaseweb.com Reviewed-by: https://reviews.apache.org/r/9254/ Signed-off-by: Prasanna Santhanam t...@apache.org EnableStaticNat error will clear the data in database - Key: CLOUDSTACK-1088 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1088 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.0.0, 4.1.0 Reporter: Wei Zhou Labels: integration-test The issue occur in two conditions (1) If I use two sessions or browsers to EnableStaticNat on CloudStack UI. one is successful, the other is failed. However, there is no ip in database. (2) If I use API call EnableStaticNat several times The first time succeed, the second failed, the third succeed. the result is success-fail-success-fail-success-fail, which it is not correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-1088) EnableStaticNat error will clear the data in database
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanna Santhanam resolved CLOUDSTACK-1088. Resolution: Fixed Fix Version/s: 4.1.0 4.0.2 commit 2e2ee2f3ed389b1b1a8a89eae8a641314417ca83 Author: Wei Zhou w.z...@leaseweb.com Date: Wed Feb 13 18:42:38 2013 +0530 CLOUDSTACK-1088: EnableStaticNat error will clear the data in database The issue occur in two conditions (1) If I use two sessions or browsers to EnableStaticNat on CloudStack UI. one is successful, the other is failed. However, there is no ip in database. (2) If I use API call EnableStaticNat several times The first time succeed, the second failed, the third succeed. the result is success-fail-success-fail-success-fail, which it is not correct. Reported-by: Wei Zhou w.z...@leaseweb.com Reviewed-by: https://reviews.apache.org/r/9254/ Signed-off-by: Prasanna Santhanam t...@apache.org Applied on master (2e2ee2), 4.1 (f81719e), and 4.0 (a61a2b) EnableStaticNat error will clear the data in database - Key: CLOUDSTACK-1088 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1088 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.0.0, 4.1.0 Reporter: Wei Zhou Labels: integration-test Fix For: 4.0.2, 4.1.0 The issue occur in two conditions (1) If I use two sessions or browsers to EnableStaticNat on CloudStack UI. one is successful, the other is failed. However, there is no ip in database. (2) If I use API call EnableStaticNat several times The first time succeed, the second failed, the third succeed. the result is success-fail-success-fail-success-fail, which it is not correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Review Request: (CLOUDSTACK-1088) EnableStaticNat error will clear the data in database
On Tue, Feb 12, 2013 at 02:12:21AM -0500, Animesh Chaturvedi wrote: Prasanna Can you review the updated patch and if it looks good apply it to master and close the item Pushed to reqd branches. Let's use the practice however to enforce that whoever marks ship it ideally commits the patch if they have committer privileges. If you are okay with the patch and want counter-review from another committer it's okay to say LGTM or some such and add the reviewer or have the contributor add them (which is what I asked of Wei in this case). RB or gerrit - the tool only helps when used as per workflows. Just my 2cents -- Prasanna.,
[jira] [Commented] (CLOUDSTACK-1201) Failed to create ssh key for user cloud /var/lib/cloud/management/.ssh/id_rsa and failed to start management server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577560#comment-13577560 ] Prasanna Santhanam commented on CLOUDSTACK-1201: sent in a review request for Hugo: https://reviews.apache.org/r/9424/ Failed to create ssh key for user cloud /var/lib/cloud/management/.ssh/id_rsa and failed to start management server --- Key: CLOUDSTACK-1201 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1201 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.1.0 Environment: Cent OS 6.0.3 Branch 4.1 Commit 368d5a1ea597c612e050613e13c95687bc0992c2 Reporter: Rayees Namathponnan Assignee: Hugo Trippaers Priority: Critical Fix For: 4.1.0 Step 1 : Created new build from 4.1 branch Step 2 : Install and configure MS server Step 3 : run cloudstack-setup-management Actual result Failed to start MS, you can see below error in log 2013-02-07 16:33:55,996 INFO [cloud.server.ConfigurationServerImpl] (main:null) Systemvm keypairs not found in database. Need to store them in the database 2013-02-07 16:33:55,996 DEBUG [utils.script.Script] (main:null) Executing: /bin/bash -c if [ -f /var/lib/cloud/management/.ssh/id_rsa ]; then rm -f /var/lib/cloud/management/.ssh/id_rsa; fi; ssh-keygen -t rsa -N '' -f /var/lib/cloud/management/.ssh/id_rsa -q 2013-02-07 16:33:56,829 DEBUG [utils.script.Script] (main:null) Exit value is 1 2013-02-07 16:33:56,829 DEBUG [utils.script.Script] (main:null) Could not create directory '/var/lib/cloud/management/.ssh'.open /var/lib/cloud/management/.ssh/id_rsa failed: No such file or directory.Saving the key failed: /var/lib/cloud/management/.ssh/id_rsa. 2013-02-07 16:33:56,866 ERROR [cloud.server.ConfigurationServerImpl] (main:null) Cannot read the private key file java.io.FileNotFoundException: /var/lib/cloud/management/.ssh/id_rsa (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:137) at com.cloud.server.ConfigurationServerImpl.updateKeyPairs(ConfigurationServerImpl.java:615) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:273) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:144) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:43) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:100) at com.cloud.servlet.CloudStartupServlet.init(CloudStartupServlet.java:38) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173) Work around, We need to create the manually and do restart MS, i followed below steps and restarted MS userdel cloud useradd -M -c CloudStack unprivileged user -r -s /bin/sh -d /var/lib/cloud/management cloud|| true mkdir -p /var/lib/cloud/management/ chown cloud:cloud /var/lib/cloud/management/ su -
Re: [MERGE] Support VM Snapshot
On 02/13/2013 01:44 AM, Sangeetha Hariharan wrote: I am planning on testing this feature and wanted to know the list of hypervisors that support this feature. When I refer to the design document - https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+Snapshots , I see the support being extended for Vmware, Xenserver and KVM. From the discussions in the email thread , I see that KVM implementation has dependencies on libvirt-java and for Xenserver there is dependency on volume snapshot design being improved. For KVM that is correct. The patches are in upstream libvirt-java, but no release is out there with the patches in it. Wido Could you please confirm? -Thanks Sangeetha -Original Message- From: Wido den Hollander [mailto:w...@widodh.nl] Sent: Monday, February 04, 2013 3:39 AM To: cloudstack-dev@incubator.apache.org Subject: Re: [MERGE] Support VM Snapshot On 02/03/2013 03:09 AM, Mice Xia wrote: So...it seems there are still some consensus to be reached and the codes were not merged before 4.1 feature freeze. This will not be in 4.1 release. That would also give the libvirt guys time to catch up and we can have full support through libvirt-java for 4.2 See these commits: * http://libvirt.org/git/?p=libvirt-java.git;a=commit;h=cd00a4b8f25944f6fe2ce3ecb2ac00cbcad8db8d * http://libvirt.org/git/?p=libvirt-java.git;a=commit;h=23a7750e4470ebce1c5b63b64a26be90057a79ae Wido -Mice -Original Message- From: Mice Xia [mailto:mice_...@tcloudcomputing.com] Sent: Saturday, February 02, 2013 11:26 AM To: Alex Huang; Anthony Xu; cloudstack-dev@incubator.apache.org Subject: RE: [MERGE] Support VM Snapshot For now, Volume snapshot and VM snapshot cannot be taken at the same time, i.e, it will check if there are active volume snapshots tasks when taking a VM snapshot, and vice versa. Another way to clear any potential impacts is, making volume snapshot and VM snapshot totally mutually exclusive, i.e. cannot take one VM snapshot if there are existing volume snapshots, and vice versa. Regards Mice From: Alex Huang [mailto:alex.hu...@citrix.com] Sent: Saturday, February 02, 2013 10:57 AM To: Anthony Xu; Mice Xia; cloudstack-dev@incubator.apache.org Subject: RE: [MERGE] Support VM Snapshot Perhaps we should just say XenServer is not supported for VM Snapshot until the volume snapshot design is fixed? I don’t think KVM and VmWare have this problem given that it’s full snapshots each time. Although it might have the same scheduling/locking race condition problems that you’re pointing out. --Alex From: Anthony Xu Sent: Friday, February 01, 2013 5:44 PM To: 'Mice Xia'; cloudstack-dev@incubator.apache.org; Alex Huang; Mice Xia Subject: RE: [MERGE] Support VM Snapshot I see, snapshot manager detected the change in primary storage, and create a full snapshot instead, which is supposed to be a delta snapshot. It doesn’t break volume snapshot function, but this degrades the volume snapshot performance. This is just a simple test, it cannot prove there is no impact to volume snapshot. I’m not sure what will happen if execute these two commands at the same time, is there any mechanism to sync/serialize these two operation? I’m not sure if revert VM has impact to volume snapshot. For now, it is better to have a global configuration to only choose one. later, we may support both of them in one setup. Anthony From: Mice Xia [mailto:mice_...@tcloudcomputing.com] Sent: Friday, February 01, 2013 5:30 PM To: cloudstack-dev@incubator.apache.org; Alex Huang; Mice Xia; Anthony Xu Subject: 答复: [MERGE] Support VM Snapshot Anthony, Thanks for your comments. Tested on a datadisk with steps you provide on xenserver, all the files (test1, test2, test3) are present, the function is not affected. But as i have replied, volume snapshot (s2) is not a delta snapshot, it is a full one. Users need to be aware of this if they want to use both snapshots simultaneously. Regards Mice -Original Message- From: Anthony Xu [mailto:xuefei...@citrix.com] Sent: 2013-2-2 (星期六) 4:05 To: Alex Huang; Mice Xia; cloudstack-dev@incubator.apache.org Subject: RE: [MERGE] Support VM Snapshot CS uses XenServer delta snapshot, snapshot manager records a VHD chain in snapshot DB for each volume. VM snapshot creation/revert also operate on volume snapshot, if snapshot manager doesn't know the VM snapshot , volume snapshot might be broken. You can try following test, 1. create a VM. 2. create empty file test1 inside this VM. 3. create a volume snapshot(s1) 4. create empty file test2 inside this VM 5. create a VM snapshot (vm1) 6. create empty file test3 inside this VM 7. create a volume snapshot (s2) 8. create a volume from snapshot (s2) 9. attach this volume to a VM 10. if one of test1, test2, test3 is missing in this volume, might mean volume snapshot is broken. It might be difficult to support both VM snapshot and volume snapshot in the same
[jira] [Commented] (CLOUDSTACK-1234) Unable to start KVM agent with 4.1 build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577574#comment-13577574 ] Prasanna Santhanam commented on CLOUDSTACK-1234: Hmm - Should we refer the service using a string constant? It's sprinkled in various places in SSHCmdHelper. Unable to start KVM agent with 4.1 build Key: CLOUDSTACK-1234 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1234 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.1.0 Environment: CentOS 6.3 Reporter: Rayees Namathponnan Assignee: Marcus Sorensen Priority: Blocker Fix For: 4.1.0 Step 1 : Created new build from 4.1 branch Step 2 : Install and configured MS server and Agent on CentOS 6.3 Step 3 : Start Agent service cloudstack-agent start Actual result KVM agent is not starting, i cannot see any log in /var/log/cloudstack/agent, this directory location is blank -- 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-1256) change EnableStaticNat to async call
Wei Zhou created CLOUDSTACK-1256: Summary: change EnableStaticNat to async call Key: CLOUDSTACK-1256 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1256 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: API Affects Versions: 4.0.1 Reporter: Wei Zhou When I use EnableStaticNat in CloudStack UI, I have to wait 10 seconds for the response. It is because that EnableStaticNat is sync call [1]. However, the other calls about NAT, like DisableStaticNat and createIpForwardingRule and deleteIpForwardingRule, are all async call. Maybe we need to change EnableStaticNat to async call. [1] http://incubator.apache.org/cloudstack/docs/api/apidocs-4.0.0/TOC_Root_Admin.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [DOCS] Update on translation, Help needed.
On Feb 12, 2013, at 4:38 PM, Mathias Mullins mathias.mull...@citrix.com wrote: Sebastien, Just as a point, can we change the Runbook to Quick Install Guide to make it easier for people to understand what the use is? I don't think people wanting to come in and quickly get started are going to understand to look to the term Runbook to help get them going, when it's an industry term for a set of Operations instructions. It may be too late, but just wondering. I have a couple people that will be really interested in it and will dive into it quickly. Matt, that's really a question for David Nalley who wrote the runbook. Thanks, Matt On 2/12/13 10:21 AM, Sebastien Goasguen run...@gmail.com wrote: All, Translation is picking up, thanks to all translators. Doc freeze is aimed for the end of the month, that means that in March we should be working on a non evolving set of docs. The runbook is finished in French. Japanese and Chinese need a few updates to be complete (due to the new push of strings). Italy is fast catching up on the runbook (61%): https://www.transifex.com/projects/p/ACS-Runbook/ This is a relatively easy one to get done. To check where they stand and how the look see: French: http://people.apache.org/~sebgoa/fr-FR/index.html Japanese: http://people.apache.org/~sebgoa/ja-JP/html/index.html Chinese (mainland): http://people.apache.org/~sebgoa/zh-CN/html/index.html Chinese (Taiwan): http://people.apache.org/~sebgoa/zh-TW/html/index.html Italian: http://people.apache.org/~sebgoa/it_IT/html/index.html I only know French, English and a bit of spanish, so please don't take offense if the documents are not properly rendered. This might be a transifex issue. Just report the issue to the list and I will fix it. The UI is seeing the most work with: Japanese, Korean, Russian, Chinese, French, Portuguese, Spanish, German, Norwegian and Catalan having a good chance of being finished by 4.1. We need a big push on the general documentation: https://www.transifex.com/projects/p/ACS_DOCS/ Chinese, Japanese and Portuguese are the only three languages we can realistically hope to finish on time for 4.1. Keep it up and get people involved, we have ~90 days to get this done :) Cheers, -Sebastien
Re: [DISCUSS] Packaging in 4.1
Hm, this package.sh is still doing weird things for me. If I pull a fresh incubator-cloudstack and run this: cd packaging/centos63 chmod +x package.sh ./package.sh I get this output (truncated, but you get the idea) tar: \rDownloaded\:: Cannot stat: No such file or directory tar: http\://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml: Cannot stat: No such file or directory tar: (22: Cannot stat: No such file or directory tar: KB: Cannot stat: No such file or directory tar: at: Cannot stat: No such file or directory tar: 96.8: Cannot stat: No such file or directory tar: KB/sec): Cannot stat: No such file or directory [root@devcloud-kvm centos63]# ls ? ?120145?172?203235.3 ?27 320.7 401.7 ?54?7292 10 ?121?145 172.4 20.3?236 270 323 402 ?55728.8 ?92 (10121.3 14.5 173 204 238?271326.8 (402 55173 921.8 ?10121.8 146?174?204238.6 274 327 405.7 (551 ?7393 100122 ?146 175.9 20.4239?275(33 406.3 55.7 739.4 ?93 ?100 122.1 148176 ?205?239 275.6 ?33 4.1.0-SNAPSHOT 557.5 74 93.0 10.0 1227.3 ?148 ?176206 24 278 330.2 42 56 ?7493.3 ?101 123 149177 207 (24278.3 331 ?42 ?5675 94 101.0 ?123?149 ?17720.7?24?27933.4424 56.0 75.5 ?94 102124 15 ?178?208?240 28 335 (424 ?57755.1 94.2 ?102 ?124(15179.3 ?209242(28 33.5429.8 58 ?7695 103?125?1518 209.0 243?28 3352.2 ?43 ?58762.9 954.6 104126 150(18 209.4 ?243 280.9 339 437.4 580.7 77 96 ?104 ?126(150 ?18 210 243.6 282 34 44 58.2 ?77?96 ?105 ?127?150 180 211 ?244 ?283(34 (44 582.0 78 96.1 106128 151?18021.1246283.0 ?34 ?44 582.9 ?7896.8 ?106 ?12815.1 181 211.4 247286 34.1443.3 (5979 ?97 107?129152?182?212?247 ?287343 44.4 ?598 97.5 10.7 (13 ?152 ?184?213?248 (289347 44.8 598.6 (8 98 108?13 153184.0 214 25 ?28935 455.7 6 ?8 ?98 ?108 130 ?153 185 215 (25(29 ?35 46 (6 ?8099 ?109 ?130153.3 ?1862157.1 ?25?29 351 ?46 ?6 ?81998 (11?131153.9 1873.3 (216250290 355 468 60 818.7 (998 ?11131.2 ?154 188 ?21625129.135.7(468 (6082 99.8 110132 154.4 ?188?217?251 29.3359 469.1 ?60?82at ?110 ?1321561883.0 218 251.6 294 36 47 ?6183 available 11.0 132.5 ?156 189 219 ?252 295.3 ?36 (47 618.0 83.3 B 110.9 134 157189.0 22 252.0 296.1 36.0?47 62 84 cloud-agent.rc 111?134?158 19 (22 25429.7363 471 ?62?84cloud-ipallocator.rc 112(135158.3 ?19 ?22 254.8 2972.9 367 (471 63 8.4cloud-management.rc ?112 ?13516 ?190?220255298 367.6 47.9 (63?85cloud-management.sysconfig ?113 1359.0 (16?192?221?255 3 368 48 ?6385.7 cloud.spec 113.0 136 ?16193 222 256(3 3683.1 ?48 636.5 859.6 cloud-usage.rc 114?1361.6?194223 (256 ?3 (37 48.1 64 86 dependency ?114 137 160?196?223?256 30 ?37 483.2 ?64?86?Downloaded: 114.6 137.8 ?160 197 ?225258(30 370 483.5 66 86.8 Downloading: 115138 161?197226 ?258 ?30 374 488.4 ?6687 for 11.5 ?13816.1 198 227 258.0 302 378 (49 67 ?87http: 116?139?162 ?198?227?259 30.238 ?49 ?6787.7 information ?116 1396.8 1642 ?22826 305 ?38 491.0 68 88 is 116.0 14 ?164 (2 229.4 (26306.3 382 492 ?68(88KB 116.7 (14 16.5 ?2 23 ?26307 386 (492 68.2 ?88missing, (117 ?14 16620 (23 (260 (31 ?39 (5 684.9 89 no ?117 140 ?166 ?20 ?23 ?260 ?31 390 ?5 69 (89org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 117.7 ?140167.5 ?2002.3 26.0 310.2 394 50 ?69?89package.sh 118141 16820.0230 262311 398 ?50 (7 89.0 POM 119?141?168
RE: [DOCS] Update on translation, Help needed.
I am really curious to know as to why David chose the title 'Runbook', instead of Quick Start Guide. -Radhika -Original Message- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: Wednesday, February 13, 2013 7:37 PM To: cloudstack-us...@incubator.apache.org Cc: cloudstack-dev@incubator.apache.org Developers Subject: Re: [DOCS] Update on translation, Help needed. On Feb 12, 2013, at 4:38 PM, Mathias Mullins mathias.mull...@citrix.com wrote: Sebastien, Just as a point, can we change the Runbook to Quick Install Guide to make it easier for people to understand what the use is? I don't think people wanting to come in and quickly get started are going to understand to look to the term Runbook to help get them going, when it's an industry term for a set of Operations instructions. It may be too late, but just wondering. I have a couple people that will be really interested in it and will dive into it quickly. Matt, that's really a question for David Nalley who wrote the runbook. Thanks, Matt On 2/12/13 10:21 AM, Sebastien Goasguen run...@gmail.com wrote: All, Translation is picking up, thanks to all translators. Doc freeze is aimed for the end of the month, that means that in March we should be working on a non evolving set of docs. The runbook is finished in French. Japanese and Chinese need a few updates to be complete (due to the new push of strings). Italy is fast catching up on the runbook (61%): https://www.transifex.com/projects/p/ACS-Runbook/ This is a relatively easy one to get done. To check where they stand and how the look see: French: http://people.apache.org/~sebgoa/fr-FR/index.html Japanese: http://people.apache.org/~sebgoa/ja-JP/html/index.html Chinese (mainland): http://people.apache.org/~sebgoa/zh-CN/html/index.html Chinese (Taiwan): http://people.apache.org/~sebgoa/zh-TW/html/index.html Italian: http://people.apache.org/~sebgoa/it_IT/html/index.html I only know French, English and a bit of spanish, so please don't take offense if the documents are not properly rendered. This might be a transifex issue. Just report the issue to the list and I will fix it. The UI is seeing the most work with: Japanese, Korean, Russian, Chinese, French, Portuguese, Spanish, German, Norwegian and Catalan having a good chance of being finished by 4.1. We need a big push on the general documentation: https://www.transifex.com/projects/p/ACS_DOCS/ Chinese, Japanese and Portuguese are the only three languages we can realistically hope to finish on time for 4.1. Keep it up and get people involved, we have ~90 days to get this done :) Cheers, -Sebastien
[MERGE] Runbook
Hi folks: If I receive no objection in the next few days, I plan on merging the runbook branch changes into master, 4.1, and 4.0. For master and 4.1 the content isn't perfect, but its a bit better than what is currently there. I'll also plan on publishing this under the title Quick Install Guide in the docs section. --David
Re: [DOCS] Update on translation, Help needed.
On Wed, Feb 13, 2013 at 9:18 AM, Radhika Puthiyetath radhika.puthiyet...@citrix.com wrote: I am really curious to know as to why David chose the title 'Runbook', instead of Quick Start Guide. -Radhika So originally I chose runbook because there was already a quick install guide in the 2.2 (and maybe even early 3.0 days) So a naming conflict. So it does bear one similarity with a runbook, in that it's a set of directions to follow, there are no options, it's a single path to a single goal, which is typically what a runbook does from an ops perspective. Since we don't have a quick install guide anymore, I'll change the name shortly. --David
Re: [DOCS] Update on translation, Help needed.
Matt: We haven't officially published it yet, so I am fine with that as a title. I'll work on doing that in the next day or so. --David On Wed, Feb 13, 2013 at 9:06 AM, Sebastien Goasguen run...@gmail.com wrote: On Feb 12, 2013, at 4:38 PM, Mathias Mullins mathias.mull...@citrix.com wrote: Sebastien, Just as a point, can we change the Runbook to Quick Install Guide to make it easier for people to understand what the use is? I don't think people wanting to come in and quickly get started are going to understand to look to the term Runbook to help get them going, when it's an industry term for a set of Operations instructions. It may be too late, but just wondering. I have a couple people that will be really interested in it and will dive into it quickly. Matt, that's really a question for David Nalley who wrote the runbook. Thanks, Matt On 2/12/13 10:21 AM, Sebastien Goasguen run...@gmail.com wrote: All, Translation is picking up, thanks to all translators. Doc freeze is aimed for the end of the month, that means that in March we should be working on a non evolving set of docs. The runbook is finished in French. Japanese and Chinese need a few updates to be complete (due to the new push of strings). Italy is fast catching up on the runbook (61%): https://www.transifex.com/projects/p/ACS-Runbook/ This is a relatively easy one to get done. To check where they stand and how the look see: French: http://people.apache.org/~sebgoa/fr-FR/index.html Japanese: http://people.apache.org/~sebgoa/ja-JP/html/index.html Chinese (mainland): http://people.apache.org/~sebgoa/zh-CN/html/index.html Chinese (Taiwan): http://people.apache.org/~sebgoa/zh-TW/html/index.html Italian: http://people.apache.org/~sebgoa/it_IT/html/index.html I only know French, English and a bit of spanish, so please don't take offense if the documents are not properly rendered. This might be a transifex issue. Just report the issue to the list and I will fix it. The UI is seeing the most work with: Japanese, Korean, Russian, Chinese, French, Portuguese, Spanish, German, Norwegian and Catalan having a good chance of being finished by 4.1. We need a big push on the general documentation: https://www.transifex.com/projects/p/ACS_DOCS/ Chinese, Japanese and Portuguese are the only three languages we can realistically hope to finish on time for 4.1. Keep it up and get people involved, we have ~90 days to get this done :) Cheers, -Sebastien
RE: [MERGE] Runbook
+1 . Great work David ! -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 7:49 PM To: cloudstack-dev@incubator.apache.org Subject: [MERGE] Runbook Hi folks: If I receive no objection in the next few days, I plan on merging the runbook branch changes into master, 4.1, and 4.0. For master and 4.1 the content isn't perfect, but its a bit better than what is currently there. I'll also plan on publishing this under the title Quick Install Guide in the docs section. --David
New committer: Likitha Shetty
Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
RE: New committer: Likitha Shetty
Congrats Likitha. Regards, Sailaja.M -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 8:07 PM To: cloudstack-dev@incubator.apache.org Subject: New committer: Likitha Shetty Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
RE: New committer: Likitha Shetty
Congrats Likitha. This news calls for a treat..:-) I have one more person in Bangalore to trouble with my patch submission (and occasional revert!) -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 8:07 PM To: cloudstack-dev@incubator.apache.org Subject: New committer: Likitha Shetty Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
RE: New committer: Likitha Shetty
Congrats Likitha. -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 8:07 PM To: cloudstack-dev@incubator.apache.org Subject: New committer: Likitha Shetty Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
[DISCUSS] Graduation to a TLP?
Hi all, I started a conversation within cloudstack-private@i.a.o about the prospect of graduation from the incubator, and have received positive reactions from everyone that replied. I wanted to kick off the discussion here on the public list, to see if anyone has any concerns or objections to us starting down the path of trying to graduate? My general impression is that we have come a long way as a community since CloudStack entered the incubator. While there are still rough edges for us to work through over time, we are dealing with our problems quite well as a community. The simple reason that I believe we are in a position to ask to graduate, is that we are no longer getting value from the incubation process! That's a good thing, because it means that we have managed to learn quite a bit about the ASF processes, rules, methods and preferences. Thoughts, comments, discussion? If the community is in general agreement, we have some work to get done: We need to go through the podling status file, and ensure that we have completed everything that needs to be completed: http://incubator.apache.org/projects/cloudstack.html The CloudStack trademark is currently owned by Citrix. We need to have that transfered to ASF prior to graduation. David also suggested in the private list that we probably need to execute the formal ASF name search, for the purpose of providing the ASF with assurances that there are no surprise conflicts. Once we get the final pre-graduation requirements completed, we need to go through the process of attempting to graduate. I suggest that folks take a minute to read through the Incubator's Guide to Successful Graduation page [1]. The first step of the process seems to be to kick off a formal community vote to propose graduation to the IPMC. If we vote to graduate, then we have to draft a charter / graduation resolution. This is will be proposed to the IPMC for their review, and if passed in an IPMC vote we forward it to the ASF board for their vote during a monthly board meeting. So that's the high level process... As I asked above, any thoughts? -chip [1] http://incubator.apache.org/guides/graduation.html
Re: New committer: Likitha Shetty
On Wed, Feb 13, 2013 at 09:37:06AM -0500, David Nalley wrote: Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC Congratulations Likitha!
RE: New committer: Likitha Shetty
Congrats Likitha :) -Original Message- From: Devdeep Singh [mailto:devdeep.si...@citrix.com] Sent: Wednesday, February 13, 2013 8:20 PM To: cloudstack-dev@incubator.apache.org Subject: RE: New committer: Likitha Shetty Congrats Likitha. -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 8:07 PM To: cloudstack-dev@incubator.apache.org Subject: New committer: Likitha Shetty Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
RE: New committer: Likitha Shetty
Congrats Likitha ! Well done. -Original Message- From: Deepti Dohare [mailto:deepti.doh...@citrix.com] Sent: Wednesday, February 13, 2013 8:22 PM To: cloudstack-dev@incubator.apache.org Subject: RE: New committer: Likitha Shetty Congrats Likitha :) -Original Message- From: Devdeep Singh [mailto:devdeep.si...@citrix.com] Sent: Wednesday, February 13, 2013 8:20 PM To: cloudstack-dev@incubator.apache.org Subject: RE: New committer: Likitha Shetty Congrats Likitha. -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 8:07 PM To: cloudstack-dev@incubator.apache.org Subject: New committer: Likitha Shetty Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
Re: New committer: Likitha Shetty
Well done and well deserved ! You can now apply all those EC2 patches yourself :) -sebastien On Feb 13, 2013, at 3:55 PM, Pranav Saxena pranav.sax...@citrix.com wrote: Congrats Likitha ! Well done. -Original Message- From: Deepti Dohare [mailto:deepti.doh...@citrix.com] Sent: Wednesday, February 13, 2013 8:22 PM To: cloudstack-dev@incubator.apache.org Subject: RE: New committer: Likitha Shetty Congrats Likitha :) -Original Message- From: Devdeep Singh [mailto:devdeep.si...@citrix.com] Sent: Wednesday, February 13, 2013 8:20 PM To: cloudstack-dev@incubator.apache.org Subject: RE: New committer: Likitha Shetty Congrats Likitha. -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 8:07 PM To: cloudstack-dev@incubator.apache.org Subject: New committer: Likitha Shetty Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
Re: [DISCUSS] Graduation to a TLP?
On Wed, Feb 13, 2013 at 9:50 AM, Chip Childers chip.child...@sungard.com wrote: Hi all, I started a conversation within cloudstack-private@i.a.o about the prospect of graduation from the incubator, and have received positive reactions from everyone that replied. I wanted to kick off the discussion here on the public list, to see if anyone has any concerns or objections to us starting down the path of trying to graduate? My general impression is that we have come a long way as a community since CloudStack entered the incubator. While there are still rough edges for us to work through over time, we are dealing with our problems quite well as a community. The simple reason that I believe we are in a position to ask to graduate, is that we are no longer getting value from the incubation process! That's a good thing, because it means that we have managed to learn quite a bit about the ASF processes, rules, methods and preferences. Thoughts, comments, discussion? If the community is in general agreement, we have some work to get done: We need to go through the podling status file, and ensure that we have completed everything that needs to be completed: http://incubator.apache.org/projects/cloudstack.html The CloudStack trademark is currently owned by Citrix. We need to have that transfered to ASF prior to graduation. David also suggested in the private list that we probably need to execute the formal ASF name search, for the purpose of providing the ASF with assurances that there are no surprise conflicts. Once we get the final pre-graduation requirements completed, we need to go through the process of attempting to graduate. I suggest that folks take a minute to read through the Incubator's Guide to Successful Graduation page [1]. The first step of the process seems to be to kick off a formal community vote to propose graduation to the IPMC. If we vote to graduate, then we have to draft a charter / graduation resolution. This is will be proposed to the IPMC for their review, and if passed in an IPMC vote we forward it to the ASF board for their vote during a monthly board meeting. So I'd propose that instead of two votes for charter/resolution and whether or not to vote, that we determine the overall community feeling/consensus in this thread, and then vote to graduate with a specific resolution as a single vote. --David
RE: New committer: Likitha Shetty
Many Congratulations Likitha! -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 8:07 PM To: cloudstack-dev@incubator.apache.org Subject: New committer: Likitha Shetty Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
Re: [MERGE] Runbook
On Wed, Feb 13, 2013 at 09:18:42AM -0500, David Nalley wrote: Hi folks: If I receive no objection in the next few days, I plan on merging the runbook branch changes into master, 4.1, and 4.0. For master and 4.1 the content isn't perfect, but its a bit better than what is currently there. I'll also plan on publishing this under the title Quick Install Guide in the docs section. --David +1 to both the merge and the name change.
Re: [DISCUSS] Graduation to a TLP?
On Wed, Feb 13, 2013 at 09:59:39AM -0500, David Nalley wrote: On Wed, Feb 13, 2013 at 9:50 AM, Chip Childers chip.child...@sungard.com wrote: Hi all, I started a conversation within cloudstack-private@i.a.o about the prospect of graduation from the incubator, and have received positive reactions from everyone that replied. I wanted to kick off the discussion here on the public list, to see if anyone has any concerns or objections to us starting down the path of trying to graduate? My general impression is that we have come a long way as a community since CloudStack entered the incubator. While there are still rough edges for us to work through over time, we are dealing with our problems quite well as a community. The simple reason that I believe we are in a position to ask to graduate, is that we are no longer getting value from the incubation process! That's a good thing, because it means that we have managed to learn quite a bit about the ASF processes, rules, methods and preferences. Thoughts, comments, discussion? If the community is in general agreement, we have some work to get done: We need to go through the podling status file, and ensure that we have completed everything that needs to be completed: http://incubator.apache.org/projects/cloudstack.html The CloudStack trademark is currently owned by Citrix. We need to have that transfered to ASF prior to graduation. David also suggested in the private list that we probably need to execute the formal ASF name search, for the purpose of providing the ASF with assurances that there are no surprise conflicts. Once we get the final pre-graduation requirements completed, we need to go through the process of attempting to graduate. I suggest that folks take a minute to read through the Incubator's Guide to Successful Graduation page [1]. The first step of the process seems to be to kick off a formal community vote to propose graduation to the IPMC. If we vote to graduate, then we have to draft a charter / graduation resolution. This is will be proposed to the IPMC for their review, and if passed in an IPMC vote we forward it to the ASF board for their vote during a monthly board meeting. So I'd propose that instead of two votes for charter/resolution and whether or not to vote, that we determine the overall community feeling/consensus in this thread, and then vote to graduate with a specific resolution as a single vote. --David Many other podlings seem to have done it that way, and I'm in agreement to that approach. -chip
RE: New committer: Likitha Shetty
Hearty Congratulations Likitha :) -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 8:07 PM To: cloudstack-dev@incubator.apache.org Subject: New committer: Likitha Shetty Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
RE: New committer: Likitha Shetty
Great news! Congrats Likitha :) Regards, Sateesh -Original Message- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: 13 February 2013 20:27 To: cloudstack-dev@incubator.apache.org Subject: Re: New committer: Likitha Shetty Well done and well deserved ! You can now apply all those EC2 patches yourself :) -sebastien On Feb 13, 2013, at 3:55 PM, Pranav Saxena pranav.sax...@citrix.com wrote: Congrats Likitha ! Well done. -Original Message- From: Deepti Dohare [mailto:deepti.doh...@citrix.com] Sent: Wednesday, February 13, 2013 8:22 PM To: cloudstack-dev@incubator.apache.org Subject: RE: New committer: Likitha Shetty Congrats Likitha :) -Original Message- From: Devdeep Singh [mailto:devdeep.si...@citrix.com] Sent: Wednesday, February 13, 2013 8:20 PM To: cloudstack-dev@incubator.apache.org Subject: RE: New committer: Likitha Shetty Congrats Likitha. -Original Message- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, February 13, 2013 8:07 PM To: cloudstack-dev@incubator.apache.org Subject: New committer: Likitha Shetty Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
Re: New committer: Likitha Shetty
On Wed, Feb 13, 2013 at 09:37:06AM -0500, David Nalley wrote: Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC About time. congratulations Likitha! -- Prasanna.,
[jira] [Created] (CLOUDSTACK-1257) resetssh:able to ssh to vm without sshkey pair
sadhu suresh created CLOUDSTACK-1257:
Summary: resetssh:able to ssh to vm without sshkey pair
Key: CLOUDSTACK-1257
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1257
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.1.0
Reporter: sadhu suresh
Assignee: Harikrishna Patnala
1. generate the keypair
http://10.147.38.236:8096/api?command=createSSHKeyPairname=k2account=sadhudomainid=1
2.deploy a VM using above keypair
http://10.147.38.236:8096/client/api?command=deployVirtualMachinezoneId=a47cec47-5317-479b-96c4-
7b1ac7756cd1templateId=51cbd77a-746f-11e2-b806-06466676hypervisor=XenServerserviceOfferingId=8d43fe05-803b-4018-b745-
c9ebd0c3bd92networkIds=aeb0e192-2e74-4fcf-b3df-
264a50129dd9displayname=guest2name=guest2account=sadhudomainid=1keypair=k2response=json
{ deployvirtualmachineresponse :
{id:63fea898-95c4-4bb1-bd6f-0de1a6641d88,jobid:ca6542d6-f674-4d66-ae3f-
97bdf6f86b52} }
3.try to ssh to using ssh key pair as with out passing ssh keypair
actual result:
even with out passing key-pair also its allowing to ssh to guest VM
additioanl Info; copied the cloud-set-guest-sshkey in the guest vm as per
documentation.
MS IP:10.147.38.236
--
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
Re: Review Request: Utility for generating the .tx/config file
I see its discarded already probably by Sebastien Thanks Animesh On Feb 13, 2013, at 2:57 AM, Kelcey Damage m...@kelceydamage.com wrote: Sorry I've been off the grid, incredibly busy. I will close the ticket as soon as I get a chance. This week is a write off for me getting anything done. Sent from my iPhone On Feb 12, 2013, at 10:11 PM, Animesh Chaturvedi animesh.chaturv...@citrix.com wrote: Sebstien, Kelcey thanks for bringing this to closure -Original Message- From: Sebastien Goasguen [mailto:nore...@reviews.apache.org] On Behalf Of Sebastien Goasguen Sent: Tuesday, February 12, 2013 12:58 AM To: Kelcey Jamison-Damage; Sebastien Goasguen; cloudstack Subject: Re: Review Request: Utility for generating the .tx/config file --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/8307/#review16463 --- This is not needed anymore since we agreed to a maximum of 50 char for basename. We can use transifex client to do it. Kelcey can you discard your patch and close it. thanks - Sebastien Goasguen On Dec. 2, 2012, 1:29 a.m., Kelcey Jamison-Damage wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/8307/ --- (Updated Dec. 2, 2012, 1:29 a.m.) Review request for cloudstack. Description --- Utility for generating the .tx/config file Long names are truncated and suffixed with -long, and duplicates are numerically tagged. Diffs - docs/doc-config-gen.py PRE-CREATION Diff: https://reviews.apache.org/r/8307/diff/ Testing --- tested against dupes and long names in en-US. uses relative paths so must be executed from /docs Thanks, Kelcey Jamison-Damage
Re: New committer: Likitha Shetty
Congrats Likitha ! On 13/02/13 8:07 PM, David Nalley da...@gnsa.us wrote: Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
RE: New committer: Likitha Shetty
Congratulations Likitha :) -Original Message- From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of Prasanna Santhanam Sent: Wednesday, February 13, 2013 8:59 PM To: cloudstack-dev@incubator.apache.org Subject: Re: New committer: Likitha Shetty On Wed, Feb 13, 2013 at 09:37:06AM -0500, David Nalley wrote: Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC About time. congratulations Likitha! -- Prasanna.,
Re: [DISCUSS] Graduation to a TLP?
On Wed, Feb 13, 2013 at 10:07 AM, Chip Childers chip.child...@sungard.com wrote: On Wed, Feb 13, 2013 at 09:59:39AM -0500, David Nalley wrote: On Wed, Feb 13, 2013 at 9:50 AM, Chip Childers chip.child...@sungard.com wrote: Hi all, I started a conversation within cloudstack-private@i.a.o about the prospect of graduation from the incubator, and have received positive reactions from everyone that replied. I wanted to kick off the discussion here on the public list, to see if anyone has any concerns or objections to us starting down the path of trying to graduate? My general impression is that we have come a long way as a community since CloudStack entered the incubator. While there are still rough edges for us to work through over time, we are dealing with our problems quite well as a community. The simple reason that I believe we are in a position to ask to graduate, is that we are no longer getting value from the incubation process! That's a good thing, because it means that we have managed to learn quite a bit about the ASF processes, rules, methods and preferences. Thoughts, comments, discussion? If the community is in general agreement, we have some work to get done: We need to go through the podling status file, and ensure that we have completed everything that needs to be completed: http://incubator.apache.org/projects/cloudstack.html The CloudStack trademark is currently owned by Citrix. We need to have that transfered to ASF prior to graduation. David also suggested in the private list that we probably need to execute the formal ASF name search, for the purpose of providing the ASF with assurances that there are no surprise conflicts. Once we get the final pre-graduation requirements completed, we need to go through the process of attempting to graduate. I suggest that folks take a minute to read through the Incubator's Guide to Successful Graduation page [1]. The first step of the process seems to be to kick off a formal community vote to propose graduation to the IPMC. If we vote to graduate, then we have to draft a charter / graduation resolution. This is will be proposed to the IPMC for their review, and if passed in an IPMC vote we forward it to the ASF board for their vote during a monthly board meeting. So I'd propose that instead of two votes for charter/resolution and whether or not to vote, that we determine the overall community feeling/consensus in this thread, and then vote to graduate with a specific resolution as a single vote. --David Many other podlings seem to have done it that way, and I'm in agreement to that approach. -chip So after mulling this over a cup of coffee - I still like the idea, but have seen the IPMC suggest changes to resolutions when they come to that list. I don't want folks to think the resolution voted on is immutable without a revote. Perhaps we draft the resolution on a consensus basis. --David
Re: Review Request: Utility for generating the .tx/config file
On Feb 13, 2013, at 4:39 PM, Animesh Chaturvedi animesh.chaturv...@citrix.com wrote: I see its discarded already probably by Sebastien nope, I don't think I have the privileges to do that. Thanks Animesh On Feb 13, 2013, at 2:57 AM, Kelcey Damage m...@kelceydamage.com wrote: Sorry I've been off the grid, incredibly busy. I will close the ticket as soon as I get a chance. This week is a write off for me getting anything done. Sent from my iPhone On Feb 12, 2013, at 10:11 PM, Animesh Chaturvedi animesh.chaturv...@citrix.com wrote: Sebstien, Kelcey thanks for bringing this to closure -Original Message- From: Sebastien Goasguen [mailto:nore...@reviews.apache.org] On Behalf Of Sebastien Goasguen Sent: Tuesday, February 12, 2013 12:58 AM To: Kelcey Jamison-Damage; Sebastien Goasguen; cloudstack Subject: Re: Review Request: Utility for generating the .tx/config file --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/8307/#review16463 --- This is not needed anymore since we agreed to a maximum of 50 char for basename. We can use transifex client to do it. Kelcey can you discard your patch and close it. thanks - Sebastien Goasguen On Dec. 2, 2012, 1:29 a.m., Kelcey Jamison-Damage wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/8307/ --- (Updated Dec. 2, 2012, 1:29 a.m.) Review request for cloudstack. Description --- Utility for generating the .tx/config file Long names are truncated and suffixed with -long, and duplicates are numerically tagged. Diffs - docs/doc-config-gen.py PRE-CREATION Diff: https://reviews.apache.org/r/8307/diff/ Testing --- tested against dupes and long names in en-US. uses relative paths so must be executed from /docs Thanks, Kelcey Jamison-Damage
Re: [DISCUSS] Graduation to a TLP?
On Feb 13, 2013, at 4:43 PM, David Nalley da...@gnsa.us wrote: On Wed, Feb 13, 2013 at 10:07 AM, Chip Childers chip.child...@sungard.com wrote: On Wed, Feb 13, 2013 at 09:59:39AM -0500, David Nalley wrote: On Wed, Feb 13, 2013 at 9:50 AM, Chip Childers chip.child...@sungard.com wrote: Hi all, I started a conversation within cloudstack-private@i.a.o about the prospect of graduation from the incubator, and have received positive reactions from everyone that replied. I wanted to kick off the discussion here on the public list, to see if anyone has any concerns or objections to us starting down the path of trying to graduate? My general impression is that we have come a long way as a community since CloudStack entered the incubator. While there are still rough edges for us to work through over time, we are dealing with our problems quite well as a community. The simple reason that I believe we are in a position to ask to graduate, is that we are no longer getting value from the incubation process! That's a good thing, because it means that we have managed to learn quite a bit about the ASF processes, rules, methods and preferences. Thoughts, comments, discussion? Are you thinking to do this prior to 4.2 release ? With my individual hat on, I think it might be best to put up a strong 4.2 release and then vote for graduation. It would strengthen our case. If the community is in general agreement, we have some work to get done: We need to go through the podling status file, and ensure that we have completed everything that needs to be completed: http://incubator.apache.org/projects/cloudstack.html The CloudStack trademark is currently owned by Citrix. We need to have that transfered to ASF prior to graduation. David also suggested in the private list that we probably need to execute the formal ASF name search, for the purpose of providing the ASF with assurances that there are no surprise conflicts. Once we get the final pre-graduation requirements completed, we need to go through the process of attempting to graduate. I suggest that folks take a minute to read through the Incubator's Guide to Successful Graduation page [1]. The first step of the process seems to be to kick off a formal community vote to propose graduation to the IPMC. If we vote to graduate, then we have to draft a charter / graduation resolution. This is will be proposed to the IPMC for their review, and if passed in an IPMC vote we forward it to the ASF board for their vote during a monthly board meeting. So I'd propose that instead of two votes for charter/resolution and whether or not to vote, that we determine the overall community feeling/consensus in this thread, and then vote to graduate with a specific resolution as a single vote. --David Many other podlings seem to have done it that way, and I'm in agreement to that approach. -chip So after mulling this over a cup of coffee - I still like the idea, but have seen the IPMC suggest changes to resolutions when they come to that list. I don't want folks to think the resolution voted on is immutable without a revote. Perhaps we draft the resolution on a consensus basis. --David
[jira] [Created] (CLOUDSTACK-1258) Enhance the CloudStack API to support DHCP options per subnet.
Jeffrey McGovern created CLOUDSTACK-1258: Summary: Enhance the CloudStack API to support DHCP options per subnet. Key: CLOUDSTACK-1258 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1258 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: API Reporter: Jeffrey McGovern Priority: Minor Description taken from discussion on user list: Problem: I am trying to solve the problem that occurs when you want to egress from a VDC to some place that is not the Internet. So as an example if you have a VDC within a CloudStack managed environment with Internet access which will also connect to another physical environment within the same datacenter (or not) that is layer 3 separated from the virtualized environment. I can see two options for solving this issue. One would be to get a second external interface configured on the CloudStack managed gateway that would route me to a private VRF somewhere on the provider core while the second way which is the one that spawned this question would be to bring up a separate gateway (This now involves having two routers/firewalls within the same VDC). With the second gateway we can now add routes directly to the VMs themselves using option 121 (or 33/249 pending some of the OS differences) on the DHCP server to control what egress point the VM would choose. The Virtual Private gateway may be one way to solve this but I can foresee a few other examples where being able to pass DHCP options will be very useful. -- 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
Not able to create Debian PV instance using CS 4.0.1 only HVM is possible
Trying to Install Ubuntu instances as PV mode using iso upload but its not
working,able to install only as HVM instance.I hope this is an Old Bug and
still not able to fix it
*Setup: *
*Hypervisor:XS 6.0.2*
*CS:4.0.1*(from jenkins.org)
*CS Host:*Centos 6.2
*Storage:*Both primary and Secondary on CS Host(Able to mount both storage
from Hypervisor)
*Issue:*not able to install Ubuntu PV instances
*Ipaddress*:Every machine is using Public ip on same CIDR
*
*
*Situation:*
Uploading ISO
Tried to upload ISO of Ubuntu 10.04 by filling necessary option and choose
Ubuntu 10.04 (64) as os type and uploaded from Ubuntu Official iso site.
=When Used that ISO to create instance/FAILED with
Error=
After Uploading, When tried to create VM with that iso its showing state as
error with error log saying:
error Info: [INVALID_SOURCE, Unable to access a required file in the
specified repository: file:///tmp/cdrom-repo-tkGltG/isolinux/vmlinuz., ]
but there is no such file or directory.
Work around=
Edited ISO image OS type from Ubuntu 10.04 to Other.(even selecting Other
PV 64bit didnt work)
This time Instance got created but as HVM instance and not PV.
Full Log: http://pastebin.com/93UmqYUC
2013-02-12 14:11:06,975 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-485:null) Seq 1-362549166: Executing request
2013-02-12 14:11:17,253 DEBUG
[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1
is ready to launch secondary storage VM
2013-02-12 14:11:17,452 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-02-12 14:11:18,419 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-485:null) Seq 1-362549166: Response Received:
2013-02-12 14:11:18,419 DEBUG [agent.transport.Request]
(DirectAgent-485:null) Seq 1-362549166: Processing: { Ans: , MgmtId:
173871959764157, via: 1, Ver: v1, Flags: 110,
[{Answer:{result:true,wait:0}},{Answer:{result:true,wait:0}}] }
2013-02-12 14:11:18,420 DEBUG [agent.manager.AgentAttache]
(DirectAgent-485:null) Seq 1-362549166: No more commands found
2013-02-12 14:11:18,420 DEBUG [agent.transport.Request]
(Job-Executor-58:job-91) Seq 1-362549166: Received: { Ans: , MgmtId:
173871959764157, via: 1, Ver: v1, Flags: 110, { Answer, Answer } }
2013-02-12 14:11:18,420 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking Ovs to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,420 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking ExternalDhcpServer to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,426 DEBUG
[network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers.
2013-02-12 14:11:18,428 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking BareMetal to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,428 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking SecurityGroupProvider to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking CiscoNexus1000vVSM to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking VpcVirtualRouter to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,433 WARN [network.element.VpcVirtualRouterElement]
(Job-Executor-58:job-91) Network Ntwk[204|Guest|6] is not associated with
any VPC
2013-02-12 14:11:18,439 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-58:job-91) Asking NiciraNvp to prepare for
Nic[41-35-63225d1d-5e2e-4903-942a-7da00da0c343-x.x.106.107]
2013-02-12 14:11:18,449 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Checking if we need to prepare 1 volumes for
VM[User|ghgh]
2013-02-12 14:11:18,494 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Creating volume: Vol[37|vm=35|ROOT]
2013-02-12 14:11:18,494 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-58:job-91) Trying to create in Pool[201|PreSetup]
2013-02-12 14:11:18,526 DEBUG [agent.transport.Request]
(Job-Executor-58:job-91) Seq 1-362549167: Sending { Cmd , MgmtId:
173871959764157, via: 1, Ver: v1, Flags: 100111,
[{storage.CreateCommand:{volId:37,pool:{id:201,uuid:36fc99d1-1a78-8a57-3164-a8e2e5d79ed2,host:localhost,path:/36fc99d1-1a78-8a57-3164-a8e2e5d79ed2,port:0,type:PreSetup},diskCharacteristics:{size:5368709120,tags:[],type:ROOT,name:ROOT-35,useLocalStorage:false,recreatable:false,diskOfferingId:3,volumeId:37,hyperType:XenServer},wait:0}}]
}
2013-02-12 14:11:18,526 DEBUG [agent.transport.Request]
(Job-Executor-58:job-91) Seq 1-362549167: Executing: { Cmd , MgmtId:
Re: New committer: Likitha Shetty
Congrats Likitha !!! Well deserved On 13/02/13 8:07 PM, David Nalley da...@gnsa.us wrote: Hi folks: The Podling Project Management Committee (PPMC) for Apache CloudStack has asked Likitha Shetty to become a committer and we are pleased to announce that they have accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in congratulating Likitha --David on behalf of the CloudStack PPMC
[jira] [Created] (CLOUDSTACK-1259) NPE at service shutdown
Prasanna Santhanam created CLOUDSTACK-1259: -- Summary: NPE at service shutdown Key: CLOUDSTACK-1259 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1259 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Prasanna Santhanam Priority: Minor During shutdown of mgmt service the following NPE is observed: 2013-02-13 15:53:33,128 ERROR [async.dao.SyncQueueItemDaoImpl] (AsyncJobMgr-Heartbeat-1:null) Unexpected excetpion, java.lang.NullPointerException at org.apache.log4j.helpers.PatternConverter.spacePad(PatternConverter.java:107) at org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:80) at org.apache.log4j.PatternLayout.format(PatternLayout.java:506) at org.apache.log4j.net.SyslogAppender.append(SyslogAppender.java:320) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66) at org.apache.log4j.Category.callAppenders(Category.java:206) at org.apache.log4j.Category.forcedLog(Category.java:391) at org.apache.log4j.Category.warn(Category.java:1043) at com.cloud.utils.db.Transaction.getConnection(Transaction.java:552) at com.cloud.utils.db.Transaction.prepareStatement(Transaction.java:461) at com.cloud.utils.db.Transaction.prepareAutoCloseStatement(Transaction.java:454) at com.cloud.async.dao.SyncQueueItemDaoImpl.getNextQueueItems(SyncQueueItemDaoImpl.java:95) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:37) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622) at com.cloud.async.SyncQueueManagerImpl.dequeueFromAny(SyncQueueManagerImpl.java:141) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at com.cloud.async.SyncQueueManagerImpl.dequeueFromAny(SyncQueueManagerImpl.java:141) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:37) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at
Re: [ACS41] New dependencies / Removed dependencies
On Tue, Feb 12, 2013 at 02:45:04PM -0800, Sheng Yang wrote: I've added dependency for java-ipv6(apache2 license) package for utils. http://code.google.com/p/java-ipv6/ ACK - thanks --Sheng On Tue, Feb 12, 2013 at 2:13 PM, Chip Childers chip.child...@sungard.com wrote: Hi all, Hoping that everyone that has worked on new features for 4.1 can take a moment to help ensure that we have properly accounted for any new dependencies. I'll do a review of the pom's, but I'd also ask that people take a minute and respond to this thread when anything they know they added or removed. -chip
Re: [DISCUSS] Graduation to a TLP?
On Wed, Feb 13, 2013 at 04:49:55PM +0100, Sebastien Goasguen wrote: On Feb 13, 2013, at 4:43 PM, David Nalley da...@gnsa.us wrote: On Wed, Feb 13, 2013 at 10:07 AM, Chip Childers chip.child...@sungard.com wrote: On Wed, Feb 13, 2013 at 09:59:39AM -0500, David Nalley wrote: On Wed, Feb 13, 2013 at 9:50 AM, Chip Childers chip.child...@sungard.com wrote: Hi all, I started a conversation within cloudstack-private@i.a.o about the prospect of graduation from the incubator, and have received positive reactions from everyone that replied. I wanted to kick off the discussion here on the public list, to see if anyone has any concerns or objections to us starting down the path of trying to graduate? My general impression is that we have come a long way as a community since CloudStack entered the incubator. While there are still rough edges for us to work through over time, we are dealing with our problems quite well as a community. The simple reason that I believe we are in a position to ask to graduate, is that we are no longer getting value from the incubation process! That's a good thing, because it means that we have managed to learn quite a bit about the ASF processes, rules, methods and preferences. Thoughts, comments, discussion? Are you thinking to do this prior to 4.2 release ? With my individual hat on, I think it might be best to put up a strong 4.2 release and then vote for graduation. It would strengthen our case. So I think that we don't have to tie this to a specific release. We've proven that we know how to do the mechanics of an ASF release now (with 2 under our belts), and anything we would do to get better at our community's release processes are purely for our community to be concerned with (assuming that we don't regress in any of our obligations as an Apache project). I also don't think that we really have a case to build. As I indicated, the discussion on the private list was positive, and that included comments from mentors saying that they felt we were ready. IMO, the decision to ask to graduate should be based on what I believe the primary goal of incubation is for a podling (assuming the legal, procedural, policy stuff is sorted): Building an Open and Diverse community [1]. I'd add the ability to self govern to that goal. I believe that we have achieved this, and, while we will need to perpetually work to grow and strengthen the community, we aren't getting value from being in the incubator anymore. Directly answering the question about prior to 4.2: I don't think they are related. If we are ready and it happens before 4.2, then great. If not, then that should be because our process to graduate just took that long. Thoughts? -chip [1] http://incubator.apache.org/guides/graduation.html#community
Re: Review Request: Patch 2 : CLOUDSTACK-657 VMware vNetwork Distributed Virtual Switch support in CloudStack
On Tue, Feb 12, 2013 at 03:55:53AM +, Sateesh Chodapuneedi wrote: On Feb. 12, 2013, 3:09 a.m., Chip Childers wrote: You mention tests were added, but where are they? Tests are included in patch-4 (https://reviews.apache.org/r/9201/) - Sateesh Thanks Sateesh! -chip
Re: New committer: Likitha Shetty
On Wed, Feb 13, 2013, at 08:37 AM, David Nalley wrote: Please join me in congratulating Likitha Likitha, thanks very much for your work on the project so far - it's greatly appreciated. Congratulations! Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/
Re: [ACS41] New dependencies / Removed dependencies
I have added below dependency in plugins/event-bus/rabbitmq/pom.xml dependency groupIdcom.rabbitmq/groupId artifactIdamqp-client/artifactId version2.8.7/version /dependency On 13/02/13 3:43 AM, Chip Childers chip.child...@sungard.com wrote: Hi all, Hoping that everyone that has worked on new features for 4.1 can take a moment to help ensure that we have properly accounted for any new dependencies. I'll do a review of the pom's, but I'd also ask that people take a minute and respond to this thread when anything they know they added or removed. -chip
[jira] [Updated] (CLOUDSTACK-657) VMware vNetwork Distributed Virtual Switch support in CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi updated CLOUDSTACK-657: Fix Version/s: (was: 4.1.0) 4.2.0 Environment: VMware vSphere 4.1/5.0/5.1 (was: VMware vSphere 5.0/5.1) VMware vNetwork Distributed Virtual Switch support in CloudStack Key: CLOUDSTACK-657 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-657 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Environment: VMware vSphere 4.1/5.0/5.1 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Need to integrate the functionality of VMware dvSwitch with CloudStack. This enables orchestration of virtual networks in VMware environment over distributed virtual switch inside vCenter. Background:- - VMware Distributed Switch is an aggregation of per-host virtual switches presented and controlled as a single distributed switch through vCenter Server at the Datacenter level. vDS abstracts configuration of individual virtual switches and enables centralized provisioning, administration, and monitoring. vDS is integral component of vCenter. Hence the native vDS support makes sense for wider and larger deployments of Cloudstack over vSphere. Each Standard vSwitch represents an independent point of configuration that needs to be managed and monitored. The management of virtual networks required by instances in the cloud is tedious when virtual networks have to span across large number of hosts. Using distributed vSwitch (vDS) simplifies the configuration and monitoring. Being standalone implementations, standard vSwitches do not provide any support for virtual machine mobility. So there needed a component to ensure that the network configurations on the source and the destination virtual switch are consistent and will allow the VM to operate without breaking connectivity or network policies. Particularly during migration of VM across hosts, the sync up among peers need to be taken care. However in case of distributed vSwitch during VMotion, the vCenter server, would update the vSwitch modules on the hosts in cluster accordingly. Following features are available with a Distributed Switch over and above Standard vSwitch of vSphere. 1. Shaping of inbound (RX) traffic 2. Supports a central unified management interface through vCenter Server 3. Supports Private VLANs (PVLANs) 4. Provides potential customization of Data and Control Planes 5. Increased visibility of inter-virtual machine traffic through Netflow 6. Improved monitoring through port mirroring (dvMirror) 7. Support for LLDP (Link Layer Discovery Protocol), a vendor-neutral protocol. Release Planning: Dev list discussions: http://markmail.org/message/eehzokoniwssrx5d http://markmail.org/message/ow7za62d3qmnjd2h Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Integration+of+CloudStack+with+VMware+DVS Feature branch: reviewboard submission -- 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-801) QA for VMWare vNetwork Distributed switch support in cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi updated CLOUDSTACK-801: Fix Version/s: (was: 4.1.0) 4.2.0 QA for VMWare vNetwork Distributed switch support in cloudstack --- Key: CLOUDSTACK-801 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-801 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.1.0 Environment: See Test Plan Reporter: Sudha Ponnaganti Assignee: ilya musayev Labels: testing Fix For: 4.2.0 - Need to have compehensive Test plan for the feature based on Requirements/FS - Please do provide Automation if there is any - You can take a look at Cloudmonkey /python framework - Any unit tests would also be good - pl take a look at Junit - test plan and Test results can be posted at https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.1+QA+Plan -- 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
Re: [DOCS][DISCUSS]Documentation for 4.1
On Feb 12, 2013, at 8:30 PM, Chip Childers chip.child...@sungard.com wrote: On Tue, Feb 12, 2013 at 10:54:42AM -0600, Joe Brockmeier wrote: On Tue, Feb 12, 2013 at 05:25:11PM +0100, Sebastien Goasguen wrote: After 2/28 we will just fix doc bugs, not add new docs, even if a feature is included in 4.1 if its docs are not in by 2/28 then too bad. -1 to this. The reason for stopping feature development with a hard freeze is that new features have the potential to disrupt the codebase badly enough that it's a major issue. Adding new docs makes it a problem for translators, but it doesn't carry the same level of disruption as new features. For example, think about the impact if Javelin landed a week later than it did into master vs. the impact of adding another section to the install or admin guide. It's not really comparable. Also - leaving a feature out of a release means it can be picked up in a later release. Failing to document features is, basically, a bug that should be fixed (if possible) before a release. Unless that feature's lack of documentation effectively just means that it's not used (but available). That's a bit of tough love, but that's what will happen if we want to stick to the schedule. I'd like to stick to the schedule, but we should have more flexibility here than with features. It's also worth noting this is the first time through with a hard feature release and we're still finding our way - and what we seem to be finding is that ~1 month for documentation is a bit tricky when a lot of features land (or don't) right on the feature deadline. I actually agree with Joe for 4.1.0. Right up until 2013-03-22, but only as a way to give our docs folks a bit more time to catch up. The more that's done earlier the better. The implication of this is that our translations will suffer (i.e., not be done). We could have a post-release translation update planned, since the published docs site doesn't have to be part of a release officially. BTW, do we have anything beyond en-US published to the website anyway? If not, we should! All that being said, I think that we need to work out a better schedule / plan for the next feature release. I think back to the discussions about the schedule, and a general desire to consider done for a feature as meaning coded, tested, documented. Perhaps that has to become the criteria for next time? I am fine with this, but I'd like to see the schedule updated (otherwise it becomes meaningless). It's not an issue of translations, it's really an issue of procedure and schedule. On the docs release, I think we need to have yet another thread :(. Docs code is part of a release, but we may get updates prior to a bug fix release. It would be good to be able to release new docs continuously. ( Jessica had started a thread about this). -sebastien Best, jzb -- Joe Brockmeier http://dissociatedpress.net/ Twitter: @jzb
Re: [DISCUSS] Graduation to a TLP?
On Feb 13, 2013, at 5:02 PM, Chip Childers chip.child...@sungard.com wrote: On Wed, Feb 13, 2013 at 04:49:55PM +0100, Sebastien Goasguen wrote: On Feb 13, 2013, at 4:43 PM, David Nalley da...@gnsa.us wrote: On Wed, Feb 13, 2013 at 10:07 AM, Chip Childers chip.child...@sungard.com wrote: On Wed, Feb 13, 2013 at 09:59:39AM -0500, David Nalley wrote: On Wed, Feb 13, 2013 at 9:50 AM, Chip Childers chip.child...@sungard.com wrote: Hi all, I started a conversation within cloudstack-private@i.a.o about the prospect of graduation from the incubator, and have received positive reactions from everyone that replied. I wanted to kick off the discussion here on the public list, to see if anyone has any concerns or objections to us starting down the path of trying to graduate? My general impression is that we have come a long way as a community since CloudStack entered the incubator. While there are still rough edges for us to work through over time, we are dealing with our problems quite well as a community. The simple reason that I believe we are in a position to ask to graduate, is that we are no longer getting value from the incubation process! That's a good thing, because it means that we have managed to learn quite a bit about the ASF processes, rules, methods and preferences. Thoughts, comments, discussion? Are you thinking to do this prior to 4.2 release ? With my individual hat on, I think it might be best to put up a strong 4.2 release and then vote for graduation. It would strengthen our case. I meant 4.1 So I think that we don't have to tie this to a specific release. We've proven that we know how to do the mechanics of an ASF release now (with 2 under our belts), and anything we would do to get better at our community's release processes are purely for our community to be concerned with (assuming that we don't regress in any of our obligations as an Apache project). I also don't think that we really have a case to build. As I indicated, the discussion on the private list was positive, and that included comments from mentors saying that they felt we were ready. Ok, I did not get that from your first email, so this is good news. IMO, the decision to ask to graduate should be based on what I believe the primary goal of incubation is for a podling (assuming the legal, procedural, policy stuff is sorted): Building an Open and Diverse community [1]. I'd add the ability to self govern to that goal. I believe that we have achieved this, and, while we will need to perpetually work to grow and strengthen the community, we aren't getting value from being in the incubator anymore. IMHO we are fine on the self-govern, there are still rough edges on the procedures. Directly answering the question about prior to 4.2: I don't think they are related. If we are ready and it happens before 4.2, then great. If not, then that should be because our process to graduate just took that long. ok Thoughts? -chip [1] http://incubator.apache.org/guides/graduation.html#community
Re: [DISCUSS] Graduation to a TLP?
On Wed, Feb 13, 2013, at 10:24 AM, Marcus Sorensen wrote: My main concerns revolve around those rough edges you mention. There still seems to be a lot of confusion around the time-based release. We got a lot of wait, I can't include this emails, I've seen people commit directly to the 4.0 branch post-release rather than the manager pulling in (perhaps they got buy-off from the release manager, I don't know, but still it raised alarm bells for me to see the logs). There was the whole javelin thing. Confusion around voting on the mailing lists, etc. We're not perfect - but that's not the point of incubation, really. At this point, at least from my POV, we're policing ourselves well and following Apache policies. If we waited until we had every process sorted out and no confusion... well, that'd be a very long time. And that's not a bad thing. I tend to agree with you Chip, that the incubation process itself may not teach us anything further about these things, and they're just things we need to iron out over time. +1 Graduating isn't saying we're perfect now just that we've reached a stage where we can handle issues within the project and/or know when to reach out for help from other parts of the Apache project - like @legal, @trademarks, etc. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/
[CI] Jenkins master node usage
Please try to avoid scheduling jobs on master as it runs out of space often. Only jobs tied to master will now run on master. If you are scheduling jobs try to use the 'Clone Workspace Plugin' from the build pipeline on your node to avoid cloning the git repository in each job. The disk usage plugin should alert us of jobs abusing disk space from now. If there are any doubts please ask on the lists. Thanks -- Prasanna.,
Re: [DISCUSS] Graduation to a TLP?
On Wed, Feb 13, 2013 at 05:54:36PM +0100, Sebastien Goasguen wrote: On Feb 13, 2013, at 5:02 PM, Chip Childers chip.child...@sungard.com wrote: On Wed, Feb 13, 2013 at 04:49:55PM +0100, Sebastien Goasguen wrote: On Feb 13, 2013, at 4:43 PM, David Nalley da...@gnsa.us wrote: On Wed, Feb 13, 2013 at 10:07 AM, Chip Childers chip.child...@sungard.com wrote: On Wed, Feb 13, 2013 at 09:59:39AM -0500, David Nalley wrote: On Wed, Feb 13, 2013 at 9:50 AM, Chip Childers chip.child...@sungard.com wrote: Hi all, I started a conversation within cloudstack-private@i.a.o about the prospect of graduation from the incubator, and have received positive reactions from everyone that replied. I wanted to kick off the discussion here on the public list, to see if anyone has any concerns or objections to us starting down the path of trying to graduate? My general impression is that we have come a long way as a community since CloudStack entered the incubator. While there are still rough edges for us to work through over time, we are dealing with our problems quite well as a community. The simple reason that I believe we are in a position to ask to graduate, is that we are no longer getting value from the incubation process! That's a good thing, because it means that we have managed to learn quite a bit about the ASF processes, rules, methods and preferences. Thoughts, comments, discussion? Are you thinking to do this prior to 4.2 release ? With my individual hat on, I think it might be best to put up a strong 4.2 release and then vote for graduation. It would strengthen our case. I meant 4.1 So I think that we don't have to tie this to a specific release. We've proven that we know how to do the mechanics of an ASF release now (with 2 under our belts), and anything we would do to get better at our community's release processes are purely for our community to be concerned with (assuming that we don't regress in any of our obligations as an Apache project). I also don't think that we really have a case to build. As I indicated, the discussion on the private list was positive, and that included comments from mentors saying that they felt we were ready. Ok, I did not get that from your first email, so this is good news. IMO, the decision to ask to graduate should be based on what I believe the primary goal of incubation is for a podling (assuming the legal, procedural, policy stuff is sorted): Building an Open and Diverse community [1]. I'd add the ability to self govern to that goal. I believe that we have achieved this, and, while we will need to perpetually work to grow and strengthen the community, we aren't getting value from being in the incubator anymore. IMHO we are fine on the self-govern, there are still rough edges on the procedures. If there's one thing I've learned over the years, it's that no software project is satisfied with it's processes. ;-) They are always going to be a little rough, and we'll always be improving them. My point is that the processes we use, or will use, are an issue for the community to deal with. We aren't getting any special value from being a podling as we work on improving them. Directly answering the question about prior to 4.2: I don't think they are related. If we are ready and it happens before 4.2, then great. If not, then that should be because our process to graduate just took that long. ok Thoughts? -chip [1] http://incubator.apache.org/guides/graduation.html#community
[jira] [Updated] (CLOUDSTACK-1252) Failed to download default template in VMware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-1252: --- Assignee: Venkata Siva Vijayendra Bhamidipati Failed to download default template in VMware -- Key: CLOUDSTACK-1252 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1252 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.1.0 Environment: CentOS6.3 4.1 branch build Hyper visor : VMware Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.1.0 Attachments: cloud.rar Step 1 : Created new build from 4.1 branch Step 2 : Install and configured MS server on CentOS 6.3 Step 3 : Prepared system template and created advanced zone Actual result System VM are created, but default templates are not available in template section. I tried to started agent from SSVM, with command service cloudstack-agent start and failed, but command service cloud start works If you look at the SSVM cloud.out (/var/log/cloud/clout.out) you can see class not found exception java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource + java -Djavax.net.ssl.trustStore=./certs/realhostip.keystore -mx168m -cp ./:./conf:aopalliance-1.0.jar:apache-log4j-extras-1.1.jar:aspectjrt-1.7.1.jar:aspectjweaver-1.7.1.jar:aws-java-sdk-1.3.21.1.jar:backport-util-concurrent-3.1.jar:bcprov-jdk16-1.46.jar:cglib-nodep-2.2.2.jar:cloud-agent-4.1.0-SNAPSHOT.jar:cloud-api-4.1.0-SNAPSHOT.jar:cloud-console-proxy-4.1.0-SNAPSHOT.jar:cloud-core-4.1.0-SNAPSHOT.jar:cloud-utils-4.1.0-SNAPSHOT.jar:commons-codec-1.6.jar:commons-collections-3.2.1.jar:commons-configuration-1.8.jar:commons-dbcp-1.4.jar:commons-discovery-0.5.jar:commons-httpclient-3.1.jar:commons-lang-2.6.jar:commons-logging-1.1.1.jar:commons-pool-1.6.jar:dom4j-1.6.1.jar:ehcache-1.5.0.jar:ejb-api-3.0.jar:gson-1.7.1.jar:guava-14.0-rc1.jar:httpclient-4.1.jar:httpcore-4.1.jar:jackson-core-asl-1.8.9.jar:jackson-mapper-asl-1.8.9.jar:jasypt-1.9.0.jar:java-ipv6-0.8.jar:javassist-3.12.1.GA.jar:javax.inject-1.jar:javax.persistence-2.0.0.jar:jsch-0.1.42.jar:jsr107cache-1.0.jar:log4j-1.2.16.jar:reflections-0.9.8.jar:spring-aop-3.1.2.RELEASE.jar:spring-asm-3.1.2.RELEASE.jar:spring-beans-3.1.2.RELEASE.jar:spring-context-3.1.2.RELEASE.jar:spring-core-3.1.2.RELEASE.jar:spring-expression-3.1.2.RELEASE.jar:spring-web-3.1.2.RELEASE.jar:trilead-ssh2-build213-svnkit-1.3-patch.jar:xml-apis-1.0.b2.jar com.cloud.agent.AgentShell template=domP type=secstorage host=10.223.49.197 port=8250 name=s-3-VM zone=1 pod=1 guid=s-3-VM resource=com.cloud.storage.resource.PremiumSecondaryStorageResource instance=SecStorage sslcopy=true role=templateProcessor mtu=1500 eth2ip=10.223.243.20 eth2mask=255.255.255.192 gateway=10.223.243.1 public.network.device=eth2 eth0mask=0.0.0.0 eth0ip=0.0.0.0 eth1ip=10.223.250.169 eth1mask=255.255.255.192 mgmtcidr=10.223.49.192/26 localgw=10.223.250.129 private.network.device=eth1 eth3ip=10.223.250.156 eth3mask=255.255.255.192 storageip=10.223.250.156 storagenetmask=255.255.255.192 storagegateway=10.223.250.129 internaldns1=10.223.110.254 internaldns2=10.223.110.253 dns1=72.52.126.11 dns2=72.52.126.12 log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.params.DefaultHttpParams). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource Attached cloud.out for reference -- 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-1252) Failed to download default template in VMware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577735#comment-13577735 ] Animesh Chaturvedi commented on CLOUDSTACK-1252: Vijay can you check into this issue Failed to download default template in VMware -- Key: CLOUDSTACK-1252 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1252 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.1.0 Environment: CentOS6.3 4.1 branch build Hyper visor : VMware Reporter: Rayees Namathponnan Assignee: Venkata Siva Vijayendra Bhamidipati Priority: Blocker Fix For: 4.1.0 Attachments: cloud.rar Step 1 : Created new build from 4.1 branch Step 2 : Install and configured MS server on CentOS 6.3 Step 3 : Prepared system template and created advanced zone Actual result System VM are created, but default templates are not available in template section. I tried to started agent from SSVM, with command service cloudstack-agent start and failed, but command service cloud start works If you look at the SSVM cloud.out (/var/log/cloud/clout.out) you can see class not found exception java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource + java -Djavax.net.ssl.trustStore=./certs/realhostip.keystore -mx168m -cp ./:./conf:aopalliance-1.0.jar:apache-log4j-extras-1.1.jar:aspectjrt-1.7.1.jar:aspectjweaver-1.7.1.jar:aws-java-sdk-1.3.21.1.jar:backport-util-concurrent-3.1.jar:bcprov-jdk16-1.46.jar:cglib-nodep-2.2.2.jar:cloud-agent-4.1.0-SNAPSHOT.jar:cloud-api-4.1.0-SNAPSHOT.jar:cloud-console-proxy-4.1.0-SNAPSHOT.jar:cloud-core-4.1.0-SNAPSHOT.jar:cloud-utils-4.1.0-SNAPSHOT.jar:commons-codec-1.6.jar:commons-collections-3.2.1.jar:commons-configuration-1.8.jar:commons-dbcp-1.4.jar:commons-discovery-0.5.jar:commons-httpclient-3.1.jar:commons-lang-2.6.jar:commons-logging-1.1.1.jar:commons-pool-1.6.jar:dom4j-1.6.1.jar:ehcache-1.5.0.jar:ejb-api-3.0.jar:gson-1.7.1.jar:guava-14.0-rc1.jar:httpclient-4.1.jar:httpcore-4.1.jar:jackson-core-asl-1.8.9.jar:jackson-mapper-asl-1.8.9.jar:jasypt-1.9.0.jar:java-ipv6-0.8.jar:javassist-3.12.1.GA.jar:javax.inject-1.jar:javax.persistence-2.0.0.jar:jsch-0.1.42.jar:jsr107cache-1.0.jar:log4j-1.2.16.jar:reflections-0.9.8.jar:spring-aop-3.1.2.RELEASE.jar:spring-asm-3.1.2.RELEASE.jar:spring-beans-3.1.2.RELEASE.jar:spring-context-3.1.2.RELEASE.jar:spring-core-3.1.2.RELEASE.jar:spring-expression-3.1.2.RELEASE.jar:spring-web-3.1.2.RELEASE.jar:trilead-ssh2-build213-svnkit-1.3-patch.jar:xml-apis-1.0.b2.jar com.cloud.agent.AgentShell template=domP type=secstorage host=10.223.49.197 port=8250 name=s-3-VM zone=1 pod=1 guid=s-3-VM resource=com.cloud.storage.resource.PremiumSecondaryStorageResource instance=SecStorage sslcopy=true role=templateProcessor mtu=1500 eth2ip=10.223.243.20 eth2mask=255.255.255.192 gateway=10.223.243.1 public.network.device=eth2 eth0mask=0.0.0.0 eth0ip=0.0.0.0 eth1ip=10.223.250.169 eth1mask=255.255.255.192 mgmtcidr=10.223.49.192/26 localgw=10.223.250.129 private.network.device=eth1 eth3ip=10.223.250.156 eth3mask=255.255.255.192 storageip=10.223.250.156 storagenetmask=255.255.255.192 storagegateway=10.223.250.129 internaldns1=10.223.110.254 internaldns2=10.223.110.253 dns1=72.52.126.11 dns2=72.52.126.12 log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.params.DefaultHttpParams). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource Attached cloud.out for reference -- 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
