[jira] [Resolved] (CLOUDSTACK-1470) unhandled exception executing api command: deployVirtualMachine
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-1470. --- Resolution: Fixed This was pushed to the 4.1 branch. Please retest, and work with Min if there are outstanding issues. > unhandled exception executing api command: deployVirtualMachine > --- > > Key: CLOUDSTACK-1470 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1470 > 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: advanced zone > hypervisor: XS6.1 > MGMT SERVER: RHEL6.3 >Reporter: Srikanteswararao Talluri >Assignee: Min Chen >Priority: Blocker > Fix For: 4.1.0 > > Attachments: management-server.zip, SMlog > > > On advanced zone deployment, > 1. deploy a virtual machine > unhandled exception executing api command: deployVirtualMachine > java.lang.ClassCastException: $Proxy301 cannot be cast to > org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl > at > org.apache.cloudstack.platform.orchestration.CloudOrchestrator.createVirtualMachine(CloudOrchestrator.java:173) > 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.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > 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.GeneratedMethodAccessor27.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.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202) > at $Proxy286.createVirtualMachine(Unknown Source) > at > com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:3378) > at > com.cloud.vm.UserVmManagerImpl.createAdvancedVirtualMachine(UserVmManagerImpl.java:3095) > 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.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > 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.GeneratedMethodAccessor27.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.AbstractAsp
[jira] [Reopened] (CLOUDSTACK-1262) Failed to Prepare Secondary Storage in VMware,
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chip Childers reopened CLOUDSTACK-1262:
---
I wasn't able to find a patch on reviewboard for this, and attempting to
cherry-pick resulted in a conflict:
>From 4.1 branch:
# git cherry-pick cec4d8b59c33858c99a4ead29b66d9aff5f0af6f
error: could not apply cec4d8b... CLOUDSTACK-1262: update default built-in
systemvm.iso search patch to be consistent with RPM location
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add ' or 'git rm '
hint: and commit the result with 'git commit'
Please submit a patch to reviewboard that applies cleanly to the 4.1 branch.
Thanks Kelvin!
> Failed to Prepare Secondary Storage in VMware,
> ---
>
> Key: CLOUDSTACK-1262
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1262
> 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, 4.2.0
> Environment: CentOS 6.3
> Vmware
>Reporter: Rayees Namathponnan
>Assignee: Kelven Yang
>Priority: Blocker
> Fix For: 4.1.0, 4.2.0
>
> Attachments: management-server.log
>
>
> Failed to prepare secondary storage VM in VMware, since we are expecting
> systemvm.iso is available at /usr/lib64/cloud/common//vms/systemvm.iso
> instead of /usr/share/cloudstack-common/vms/systemvm.iso
> /plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
> private File getSystemVMPatchIsoFile() {
> // locate systemvm.iso
> URL url =
> this.getClass().getProtectionDomain().getCodeSource().getLocation();
> File file = new File(url.getFile());
> File isoFile = new File(file.getParent() + "/vms/systemvm.iso");
> if (!isoFile.exists()) {
> isoFile = new File("/usr/lib64/cloud/common/" +
> "/vms/systemvm.iso");
> if (!isoFile.exists()) {
> isoFile = new File("/usr/lib/cloud/common/" +
> "/vms/systemvm.iso");
> }
> }
> return isoFile;
> }
--
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-tabpanel&focusedCommentId=13590948#comment-13590948 ] Chip Childers commented on CLOUDSTACK-1252: --- Thanks Kelvin! > 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: KVM, VMware >Affects Versions: 4.1.0 > Environment: CentOS6.3 > 4.1 branch build > Hyper visor : VMware >Reporter: Rayees Namathponnan >Assignee: Kelven Yang >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] [Updated] (CLOUDSTACK-132) Mash up marvin into an interactive auto-completing API shell for CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-132: - Assignee: Rohit Yadav (was: Chip Childers) > Mash up marvin into an interactive auto-completing API shell for CloudStack > --- > > Key: CLOUDSTACK-132 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-132 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test Tools >Affects Versions: pre-4.0.0, 4.0.0 >Reporter: Prasanna Santhanam >Assignee: Rohit Yadav > Fix For: 4.1.0 > > > The marvin libraries contain the capability to convert marvin into an > interactive shell for CloudStack. Every cloud provider has an auto-completing > shell and cloudstack lacks options for this now. This should involve > refactoring all the marvin libraries to allow for auto-completion of APIs. > Furthermore the ability to autocomplete the entities like templates, images, > virtualmachines need to exist as a part of such a shell to make it useful at > cloudscale -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-132) Mash up marvin into an interactive auto-completing API shell for CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers reassigned CLOUDSTACK-132: Assignee: Chip Childers (was: Rohit Yadav) > Mash up marvin into an interactive auto-completing API shell for CloudStack > --- > > Key: CLOUDSTACK-132 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-132 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test Tools >Affects Versions: pre-4.0.0, 4.0.0 >Reporter: Prasanna Santhanam >Assignee: Chip Childers > Fix For: 4.1.0 > > > The marvin libraries contain the capability to convert marvin into an > interactive shell for CloudStack. Every cloud provider has an auto-completing > shell and cloudstack lacks options for this now. This should involve > refactoring all the marvin libraries to allow for auto-completion of APIs. > Furthermore the ability to autocomplete the entities like templates, images, > virtualmachines need to exist as a part of such a shell to make it useful at > cloudscale -- 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-1479) Document Search on Published Manuals
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1479: -- Issue Type: New Feature (was: Bug) > Document Search on Published Manuals > > > Key: CLOUDSTACK-1479 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1479 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Website >Reporter: Mark Hinkle >Priority: Minor > Labels: documentaion, manual, web > > Documentation Search indexs localhost not the doc directory - > http://incubator.apache.org/cloudstack/docs/en-US/index.html - tries search > doesn't work, looks like a artifact from Publican publishing. Should > probobably just pass the correct directory to Google to return results > otherwise all search results are empty. -- 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-tabpanel&focusedCommentId=13590583#comment-13590583 ] Chip Childers commented on CLOUDSTACK-1252: --- Anybody willing to take this bug? > 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: KVM, VMware >Affects Versions: 4.1.0 > Environment: CentOS6.3 > 4.1 branch build > Hyper visor : VMware >Reporter: Rayees Namathponnan >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-1415) .deb packaging merge
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588430#comment-13588430 ] Chip Childers commented on CLOUDSTACK-1415: --- Can we get this into 4.1 please? > .deb packaging merge > > > Key: CLOUDSTACK-1415 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1415 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Noa Resare >Assignee: Noa Resare > > This ticket tracks the merge of the packaging work that me and [~widodh] has > been working on in a separate branch. > The diff is kind of large, but most of the lines are the package > delimitations moving around resulting in a lot of file moves. The changes > should be orthogonal to non-packaging related developments and the target is > both the 4.1 and master branches. Since the current state of packaging is > very broken, at least it will be an improvement. > Concepts included in the diff: > * the replace.properties location used by maven is parameterized to allow for > a build that does not modify the currently git tracked files > * package naming is updated along the lines of what was discussed on the -dev > mailing list and between committers at the Build a Cloud Day in Belgium. > * package version pattern is updated (since we redo all package names, we > might as well drop the epoch) > This commit is not very well tested, and most likely broken in a few ways, > but since should be pretty safe regression-wise and it is a good starting > point to get to a broader user base for the last fixes to 4.1 packaging. -- 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-1386) BASIC zone SSVM fail to start due to exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587499#comment-13587499 ] Chip Childers commented on CLOUDSTACK-1386: --- Edison - Do you mind taking a look at this blocker? > BASIC zone SSVM fail to start due to exception > --- > > Key: CLOUDSTACK-1386 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1386 > 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: MS 10.223.195.114 rhel6.3 2/24/2013 ASF 4.1 > latest build > Host 10.223.51.2 XEN >Reporter: angeline shen >Assignee: edison su >Priority: Blocker > Fix For: 4.1.0 > > Attachments: management-server.log.gz, management-server.log.gz, > Screenshot-CloudStack - Mozilla Firefox-6.png > > > 1. create basic zone, Exception while trying to start secondary storage vm > 2013-02-25 13:26:51,908 WARN [storage.secondary.SecondaryStorageManagerImpl] > (secstorage-1:null) Exception while trying to start secondary storage vm > java.lang.NullPointerException > at > com.cloud.agent.manager.allocator.impl.RecreateHostAllocator.allocateTo(RecreateHostAllocator.java:95) > at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > 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.GeneratedMethodAccessor27.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.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202) > at $Proxy268.allocateTo(Unknown Source) > at > com.cloud.deploy.FirstFitPlanner.findSuitableHosts(FirstFitPlanner.java:713) > at > com.cloud.deploy.FirstFitPlanner.checkClustersforDestination(FirstFitPlanner.java:520) > at > com.cloud.deploy.FirstFitPlanner.scanClustersForDestinationInZoneOrPod(FirstFitPlanner.java:388) > at com.cloud.deploy.FirstFitPlanner.plan(FirstFitPlanner.java:259) > at sun.reflect.GeneratedMethodAccessor219.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > 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.GeneratedMethodAccessor27.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at
[jira] [Commented] (CLOUDSTACK-1339) ASF 4.1: Management server becomes unresponsive
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584345#comment-13584345 ] Chip Childers commented on CLOUDSTACK-1339: --- Srikanteswararao, Any response to Sudha's question? I know that Kelvin is digging into the issue (per his note to the dev list), but being able to restart the MS should keep you moving with other tests. > ASF 4.1: Management server becomes unresponsive > --- > > Key: CLOUDSTACK-1339 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1339 > 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: Srikanteswararao Talluri >Assignee: Kelven Yang >Priority: Blocker > Fix For: 4.1.0 > > Attachments: MS_log.txt > > > management server becomes unresponsive after running for a while and after > some time the process shuts down. > This is blocking the testing > logs can be found @ https://citrix.sharefile.com/d/sa684d7a73fb45ba8 -- 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-1357) Duplicate inside DeployVM's job response virtualmachine object Was: (Autoscale: Provisioned VMs from Netscaler not being added to lb vserver, provserv
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584339#comment-13584339 ] Chip Childers commented on CLOUDSTACK-1357: --- Are we talking about 4.1 or 4.0? Vijay, your comment above seems to be talking about 4.0. > Duplicate inside DeployVM's job response virtualmachine object > Was: (Autoscale: Provisioned VMs from Netscaler not being added to lb > vserver, provserver fails with provserver_err_asynctaskpoll) > -- > > Key: CLOUDSTACK-1357 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1357 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API >Affects Versions: 4.1.0 > Environment: Ubuntu 11.10, XS 6.1, Netscaler v 10.0 >Reporter: Sowmya Krishnan >Assignee: Vijay Venkatachalam >Priority: Blocker > Fix For: 4.1.0 > > Attachments: nslog > > > VMs are getting provisioned but are not getting added to the lb vserver. DNS > records not created either. Following is the provision log from ns.log: > Feb 21 07:02:29 ns provserverd[393]: Job provision request > for Service Group (Cloudabc622303efb4ebe9ad4fa272103e2fd) > Feb 21 07:02:34 10.102.192.50 02/21/2013:07:02:34 GMT 0-PPE-0 > : UI CMD_EXECUTED 3108 0 : User nsroot - Remote_ip 10.144.7.15 - Command > "show lb vserver Cloud-VirtualServer-1 > 0.102.196.245-22" - Status "Success" > Feb 21 07:02:59 ns provserverd[393]: Job with job type (0) for > Service Group (Cloudabc622303efb4ebe9ad4fa272103e2fd) -> Error : > provserver_err_asynctaskpoll > Feb 21 07:03:29 ns provserverd[393]: Job provision request > for Service Group (Cloudabc622303efb4ebe9ad4fa272103e2fd) > Steps > = > 1. Create an Autoscale config with suitable template and min members as 2 and > max as 5. Set appropriate scale up and scale down policies > 2. Verify lb rule is created in Netscaler > Result > = > Status of lb vserver is DOWN and dns record is not added for the deployed VM. > VMs continue to get deployed but it is not getting added to the lb vserver > Expected Result > = > 2 VMs should be provisioned and added to lb vserver and dns records for the > VMs should get added as well. > lb vserver status should be UP and so should the services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [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-tabpanel&focusedCommentId=13584338#comment-13584338 ] Chip Childers commented on CLOUDSTACK-1252: --- Rayees, Can you please re-confirm that you are using the 4.1 code, and not code from master? > 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: KVM, VMware >Affects Versions: 4.1.0 > Environment: CentOS6.3 > 4.1 branch build > Hyper visor : VMware >Reporter: Rayees Namathponnan >Assignee: Nitin Mehta >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-1264) System VM does not have default route.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584332#comment-13584332 ] Chip Childers commented on CLOUDSTACK-1264: --- Any update on the re-test? > System VM does not have default route. > -- > > Key: CLOUDSTACK-1264 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1264 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup, Network Devices, XenServer >Affects Versions: 4.1.0 > Environment: Build #15, rhel 6.3 >Reporter: Parth Jagirdar >Assignee: Jayapal Reddy >Priority: Blocker > > While troubleshooting it was found that System VM doesnt have default route. > Management sever logs that contains n/w info are attached. Which shows that > N/W info including G/W being passed. (May be the script on VM failed to > configure?) > Other Hypervisor (VMWARE) didnt have this issue. > This was confirmed on the setup mentioned in bug #1252. We were able to ping > external world. > https://issues.apache.org/jira/browse/CLOUDSTACK-1252 > Please contact if more info is needed. -- 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-760) nTier Apps 2.0 : Allow ACL on all layer 4 protocols
[ https://issues.apache.org/jira/browse/CLOUDSTACK-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584284#comment-13584284 ] Chip Childers commented on CLOUDSTACK-760: -- you mean master, right? This sounds like a new feature, and the jira record itself has 4.2 (not 4.1) in it. > nTier Apps 2.0 : Allow ACL on all layer 4 protocols > --- > > Key: CLOUDSTACK-760 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-760 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Kishan Kavala >Assignee: Pranav Saxena > Fix For: 4.2.0 > > > This item is sub task (2.14) of > https://issues.apache.org/jira/browse/CLOUDSTACK-621 > Currently, there are only 3 options that a user can specify for the protocol > field in the Network ACL APIs/UI. These fields are ICMP, UDP and TCP. This > requirement is to make the protocol field more flexible. > There is already backend support for "all" protocols in Firewall rules. Same > logic has to be implemented in network ACL case. -- 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-587) MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy:
[ https://issues.apache.org/jira/browse/CLOUDSTACK-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-587: - Fix Version/s: 4.0.2 > MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: > -- > > Key: CLOUDSTACK-587 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-587 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anthony Xu >Assignee: Anthony Xu > Fix For: 4.0.2 > > > > How can I figure out this exception when I try to create a new > > instance using by example Centos 6.3 ISO (compute offering = > > 500MHertz, 500MB, local > > storage) ? > > > > WARN [xen.resource.CitrixResourceBase] (DirectAgent-36:) Catch > > Exception: > > class com.xensource.xenapi.Types$XenAPIException due to > > MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min ? > > dynamic_min ? dynamic_max ? static_max > > MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min ? > > dynamic_min ? dynamic_max ? static_max at > > com.xensource.xenapi.Types.checkResponse(Types.java:1732) > > at com.xensource.xenapi.Connection.dispatch(Connection.java:368) > > at > > com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerCon > > n > > ection.dispatch(XenServerConnectionPool.java:909) > > at com.xensource.xenapi.VM.setMemoryStaticMin(VM.java:3450) > > at > > com.cloud.hypervisor.xen.resource.CitrixResourceBase.setMemory(CitrixR > > e > > sourceBase.java:3116) > > at > > com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTempl > > a > > te(CitrixResourceBase.java:985) > > at > > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixRes > > o > > urceBase.java:1278) > > at > > com.cloud.hypervisor.xen.resource.XcpOssResource.execute(XcpOssResourc > > e > > .java:142) > > at > > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(Ci > > t > > rixResourceBase.java:497) > > at > > com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOss > > R > > esource.java:136) > > at > > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache. > > java:191) > > at > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439 > > ) at > > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > > at > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.a > > c > > cess$301(ScheduledThreadPoolExecutor.java:98) > > at > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.r > > u > > n(ScheduledThreadPoolExecutor.java:206) > > at > > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu > > t > > or.java:886) > > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. > > j > > ava:908) > > at java.lang.Thread.run(Thread.java:680) > > > > Regards, > > > > -- -- 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-1343) Porting Baremetal related UI changes to ACS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582427#comment-13582427 ] Chip Childers commented on CLOUDSTACK-1343: --- Please clarify "port to ACS". Is this code already in another project / product? > Porting Baremetal related UI changes to ACS > --- > > Key: CLOUDSTACK-1343 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1343 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: 4.1.0 >Reporter: frank zhang >Assignee: Jessica Wang > Fix For: 4.1.0 > > > Baremetal network services need enabling from UI. > we already have this fix and need to port to ACS -- 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-1227) cloud-install-sys-tmplt script points to /etc/cloud/management/db.properties which doesn't exist
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1227: -- Assignee: Rohit Yadav (was: Wido den Hollander) > cloud-install-sys-tmplt script points to /etc/cloud/management/db.properties > which doesn't exist > > > Key: CLOUDSTACK-1227 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1227 > 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 >Reporter: Kiran Koneti >Assignee: Rohit Yadav >Priority: Critical > > > /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt > -m /tmp/sec/s -u http://10.147.28.7/templates/burbank-systemvm-08012012.ova > -h vmware -F > sed: can't read /etc/cloud/management/db.properties: No such file or directory > sed: can't read /etc/cloud/management/db.properties: No such file or directory > sed: can't read /etc/cloud/management/db.properties: No such file or directory > ERROR 2005 (HY000): Unknown MySQL server host '--user=' (1) > Unable to get template Id from database > Installation failed > workaround: > > modify references to /etc/cloud/management/db.properties to > /etc/cloudstack/management/db.properties in the file cloud-install-sys-tmplt -- 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-1078) Not able to start System Vms on Rhel 6.3 KVM host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-1078. --- Resolution: Invalid Per Marcus's note, following the documentation appears to have resolved this issue. > Not able to start System Vms on Rhel 6.3 KVM host > - > > Key: CLOUDSTACK-1078 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1078 > 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: Build from IPv6 branch >Reporter: Sangeetha Hariharan >Assignee: edison su >Priority: Critical > Fix For: 4.1.0 > > > I am testing with build from IPv6 branch. > I am trying to bring up an advanced zone using rhel6.3 KVM hosts. > System Vms are not able to start. > I see the following exceptions in agent logs: > 2013-01-28 22:10:02,576 WARN [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-5:null) Exception > com.cloud.exception.InternalErrorException: Failed to create vnet 1363: Set > name-type for VLAN subsystem. Should be visible in > /proc/net/vlan/configERROR: trying to add VLAN #1363 to IF -:br-1363:- > error: No such deviceFailed to create vlan 1363 on pif: br-1363. > at > com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVnet(BridgeVifDriver.java:170) > at > com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVlanBr(BridgeVifDriver.java:156) > at > com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:119) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3301) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3069) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3093) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1174) > at com.cloud.agent.Agent.processRequest(Agent.java:525) > at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852) > at com.cloud.utils.nio.Task.run(Task.java:83) > 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) > 2013-01-28 22:10:02,577 WARN [cloud.agent.Agent] > (agentRequest-Handler-5:null) Caught: > java.lang.NullPointerException > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.cleanupVMNetworks(LibvirtComputingResource.java:4223) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.handleVmStartFailure(LibvirtComputingResource.java:2992) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3116) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1174) > at com.cloud.agent.Agent.processRequest(Agent.java:525) > at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852) > at com.cloud.utils.nio.Task.run(Task.java:83) > 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) -- 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-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:all-tabpanel ] Chip Childers resolved CLOUDSTACK-1201. --- Resolution: Fixed Resolving per Marcus's comment below. > 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.(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
[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-tabpanel&focusedCommentId=13582299#comment-13582299 ] Chip Childers commented on CLOUDSTACK-1252: --- Nitin, Have you had a chance to look at this? > 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: KVM, VMware >Affects Versions: 4.1.0 > Environment: CentOS6.3 > 4.1 branch build > Hyper visor : VMware >Reporter: Rayees Namathponnan >Assignee: Nitin Mehta >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-1227) cloud-install-sys-tmplt script points to /etc/cloud/management/db.properties which doesn't exist
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582289#comment-13582289 ] Chip Childers commented on CLOUDSTACK-1227: --- Wido - Can you respond to Rohit's question please? > cloud-install-sys-tmplt script points to /etc/cloud/management/db.properties > which doesn't exist > > > Key: CLOUDSTACK-1227 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1227 > 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 >Reporter: Kiran Koneti >Assignee: Wido den Hollander >Priority: Critical > > > /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt > -m /tmp/sec/s -u http://10.147.28.7/templates/burbank-systemvm-08012012.ova > -h vmware -F > sed: can't read /etc/cloud/management/db.properties: No such file or directory > sed: can't read /etc/cloud/management/db.properties: No such file or directory > sed: can't read /etc/cloud/management/db.properties: No such file or directory > ERROR 2005 (HY000): Unknown MySQL server host '--user=' (1) > Unable to get template Id from database > Installation failed > workaround: > > modify references to /etc/cloud/management/db.properties to > /etc/cloudstack/management/db.properties in the file cloud-install-sys-tmplt -- 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-1321) [Site-to-Site VPN] No events are generated in case of status change in site to site vpn connection
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582288#comment-13582288 ] Chip Childers commented on CLOUDSTACK-1321: --- Sheng, and updates? > [Site-to-Site VPN] No events are generated in case of status change in site > to site vpn connection > -- > > Key: CLOUDSTACK-1321 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1321 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.1.0 > Environment: ASF 4.1 latest build; commit > cb83c23484c0fb9b276a1aed9087436b394a6f89 >Reporter: Sanjeev N >Assignee: Sheng Yang >Priority: Critical > Fix For: 4.1.0 > > Attachments: auth.log, vmops.rar > > > [Site-to-Site VPN] No events are generated in case of status change in site > to site vpn connection > Reproduction method: > > 1.Bring up CS in advanced zone > 2.create vpc, vpn gateway, customer vpn gateway > 3.create site to site vpn connection between cs vpn gateway and customer vpn > gateway > 4.Bring down the vpn connection (Restart vpc) > Expected Result: > = > When the vpn connection status changes from connected to Disconnected an > event should be generated. > Test Result: > = > No events are generated even though there is a change in vpn connection > status. -- 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-1315) [F5-SRX-InlineMode] Network implement failed with Run time Exception during network upgrade from VR to SRX-F5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582286#comment-13582286 ] Chip Childers commented on CLOUDSTACK-1315: --- Sheng, and updates? > [F5-SRX-InlineMode] Network implement failed with Run time Exception during > network upgrade from VR to SRX-F5 > - > > Key: CLOUDSTACK-1315 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1315 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.1.0 > Environment: Latest build on ASF 4.1 commit > cb83c23484c0fb9b276a1aed9087436b394a6f89 >Reporter: Sanjeev N >Assignee: Sheng Yang >Priority: Critical > Fix For: 4.1.0 > > Attachments: vmops.rar > > > [F5-SRX-InlineMode] Network implement failed with Run time Exception during > network upgrade from VR to SRX-F5 > Updgrade from a Network that has Network offering which has all services > provdied by VR to a network offering that has SRX/F5 inline mode. > Reproduction method: > > PreReq: > 1. Create a network offering NO1 using VR as service provider for all > services. > 2. Add SRX device. > 3. Add F5 device > 4. Add a user account. > 5. Deploy the few VMs using the above created NO1. > 6. Acquire an Ip addresses. > 7. Create Pf rule.Open firewall. > 8. Create LB rule.Open firewall. > 9. Create Static NAT.Open firewall. > Steps: > 1. Create a NO2 using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 > for LB (in shared inline mode) and rest of the services are provided by VR. > 2. Stop all the running guset vms belong to this network and upgrade NO1 to > NO2. > Test Result: > = > Network upgrade failed with Run time exception > Expected Result: > = > Network upgrade should succeed. > Observations: > == > Observed following exception during network implement > 2013-02-18 12:33:45,863 ERROR [cloud.async.AsyncJobManagerImpl] > (Job-Executor-28:job-148) Unexpected exception while executing > org.apache.cloudstack.api.command.user.network.UpdateNetworkCmd > com.cloud.utils.exception.CloudRuntimeException: Failed to implement network > (with specified id) elements and resources as a part of network update > at > com.cloud.network.NetworkServiceImpl.updateGuestNetwork(NetworkServiceImpl.java:1705) > 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.GeneratedMethodAccessor144.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:37) > at sun.reflect.GeneratedMethodAccessor46.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.spri
[jira] [Commented] (CLOUDSTACK-1292) [F5-SRX-InlineMode] Update network from SRX,F5 as service provideds to VR as service provider does not delete firewall rules from SRX
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582285#comment-13582285
]
Chip Childers commented on CLOUDSTACK-1292:
---
Sheng, and updates?
> [F5-SRX-InlineMode] Update network from SRX,F5 as service provideds to VR as
> service provider does not delete firewall rules from SRX
> -
>
> Key: CLOUDSTACK-1292
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1292
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.1.0
> Environment: ASF 4.1 latest build
>Reporter: Sanjeev N
>Assignee: Sheng Yang
>Priority: Critical
> Fix For: 4.1.0
>
> Attachments: vmops.rar
>
>
> [F5-SRX-InlineMode] Update network from SRX,F5 as service provideds to VR as
> service provider does not delete firewall rules from SRX
> Reproduction method:
> =
> 1. . Create a NO1 using SRX for PF,Static NAT, Source Nat (Zone wide) and F5
> for LB(inline mode) and rest of the services are provided by VR.
> 2. Add SRX device.
> 3. Add F5 device
> 4. Add a user account.
> 5. Deploy the few VMs using the above created NO.
> 6. Acquire an Ip addresses.
> 7. Create Pf rule.Open firewall.
> 8. Create LB rule.Open firewall.
> 9. Create Static NAT.Open firewall.
> Steps:
> 1. Create a NO2 using VR as service provider for all services.
> 2. Update NO1 to NO2.
> Test Result:
> =
> Firewall rules from SRX are not deleted after update network from network
> offering NO1 to NO2
> Expected Result:
> =
> Firewall rules in untrust filter should be deleted from SRX
> Observations:
> ==
> When network was implemented with network offering NO1, firewall rules were
> created on SRX to allow traffic from untrust zone.
> IPs allocated in this network are:
> mysql> select public_ip_address , network_id from user_ip_address where
> network_id=204;
> +---++
> | public_ip_address | network_id |
> +---++
> | 10.147.48.21 |204 |
> | 10.147.48.26 |204 |
> | 10.147.48.28 |204 |
> | 10.147.48.29 |204 |
> +---++
> 4 rows in set (0.21 sec)
> Output from SRX after network update from NO1 to NO2(All other configuration
> related to this netowrk was erased from SRX except the below firewall rules
> after network update):
> root# show firewall filter untrust term 10-147-48-21-10
> from {
> source-address {
> 0.0.0.0/0;
> }
> destination-address {
> 10.147.48.21/32;
> }
> protocol tcp;
> destination-port 1-65535;
> }
> then {
> count 10-147-48-21-i;
> accept;
> }
> [edit]
> root# show firewall filter untrust term 10-147-48-26-7
> from {
> source-address {
> 0.0.0.0/0;
> }
> destination-address {
> 10.147.48.26/32;
> }
> protocol tcp;
> destination-port 1-65535;
> }
> then {
> count 10-147-48-26-i;
> accept;
> }
> [edit]
> root# show firewall filter untrust term 10-147-48-28-9
> from {
> source-address {
> 0.0.0.0/0;
> }
> destination-address {
> 10.147.48.28/32;
> }
> protocol tcp;
> destination-port 1-65535;
> }
> then {
> count 10-147-48-28-i;
> accept;
> }
--
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-1288) [F5-SRX-InlineMode] classCastException during network restart with cleanup option true
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582284#comment-13582284 ] Chip Childers commented on CLOUDSTACK-1288: --- Sheng, and updates? > [F5-SRX-InlineMode] classCastException during network restart with cleanup > option true > -- > > Key: CLOUDSTACK-1288 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1288 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.1.0 > Environment: ASF 4.1 branch latest build >Reporter: Sanjeev N >Assignee: Sheng Yang >Priority: Critical > Fix For: 4.1.0 > > Attachments: vmops.rar > > > [F5-SRX-InlineMode] classCastException during network restart with cleanup > option true > Pre-Req: > 1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for > LB and rest of the services are provided by VR. > 2. Add SRX device > 3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode > 4. Add a user account. > 5. Deploy few VMs using the above created NO. > 6. Acquire Ip address. > 7. Create a PF rules on this ipaddress. > 8. Acquire another Ip address. > 9. Create a Static NAT on this ipaddress. > 10. Acquire another Ip address. > 11. Create a LB rule on this ipaddress. > 12. Make sure PF, Static NAT and Lb rules work as expected. > Steps: > Restart network -> with cleanup option. > Observations: > == > Restart network with cleanup option was successful, however observed > following exception during network restart: > 2013-02-15 05:40:36,420 WARN [cloud.network.NetworkManagerImpl] > (Job-Executor-2:job-105) shutdownNetworkRules failed during the network > Ntwk[204|Guest|13] shutdown due to > java.lang.ClassCastException: > com.cloud.network.dao.LoadBalancerVO$$EnhancerByCGLIB$$fb34eda2 cannot be > cast to com.cloud.network.lb.LoadBalancingRule > at > com.cloud.network.ExternalLoadBalancerDeviceManagerImpl.applyLoadBalancerRules(ExternalLoadBalancerDeviceManagerImpl.java:839) > at > com.cloud.network.element.F5ExternalLoadBalancerElement.applyLBRules(F5ExternalLoadBalancerElement.java:186) > 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.GeneratedMethodAccessor47.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.network.lb.LoadBalancingRulesManagerImpl.applyRules(LoadBalancingRulesManagerImpl.java:1166) > 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.GeneratedMethodAccessor47.invoke(Unknown Source) > at > sun.reflect.DelegatingMetho
[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-tabpanel&focusedCommentId=13582281#comment-13582281 ] Chip Childers commented on CLOUDSTACK-1201: --- Marcus / Hugo, Can this be resolved now? Should it actually be assigned to Marcus (since I see he's committing fixes against it)? > 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.(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 /
[jira] [Commented] (CLOUDSTACK-1078) Not able to start System Vms on Rhel 6.3 KVM host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582279#comment-13582279 ] Chip Childers commented on CLOUDSTACK-1078: --- Edison - Any updates? Do you think this can be resolved? > Not able to start System Vms on Rhel 6.3 KVM host > - > > Key: CLOUDSTACK-1078 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1078 > 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: Build from IPv6 branch >Reporter: Sangeetha Hariharan >Assignee: edison su >Priority: Critical > Fix For: 4.1.0 > > > I am testing with build from IPv6 branch. > I am trying to bring up an advanced zone using rhel6.3 KVM hosts. > System Vms are not able to start. > I see the following exceptions in agent logs: > 2013-01-28 22:10:02,576 WARN [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-5:null) Exception > com.cloud.exception.InternalErrorException: Failed to create vnet 1363: Set > name-type for VLAN subsystem. Should be visible in > /proc/net/vlan/configERROR: trying to add VLAN #1363 to IF -:br-1363:- > error: No such deviceFailed to create vlan 1363 on pif: br-1363. > at > com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVnet(BridgeVifDriver.java:170) > at > com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVlanBr(BridgeVifDriver.java:156) > at > com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:119) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3301) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3069) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3093) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1174) > at com.cloud.agent.Agent.processRequest(Agent.java:525) > at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852) > at com.cloud.utils.nio.Task.run(Task.java:83) > 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) > 2013-01-28 22:10:02,577 WARN [cloud.agent.Agent] > (agentRequest-Handler-5:null) Caught: > java.lang.NullPointerException > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.cleanupVMNetworks(LibvirtComputingResource.java:4223) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.handleVmStartFailure(LibvirtComputingResource.java:2992) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3116) > at > com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1174) > at com.cloud.agent.Agent.processRequest(Agent.java:525) > at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852) > at com.cloud.utils.nio.Task.run(Task.java:83) > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-43) Jenkins build process needs to allow for setting the appropriate version number within the built JARs.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers closed CLOUDSTACK-43. --- Resolution: Invalid Fix Version/s: (was: 4.1.0) This is actually invalid, since we will use the mvn release process to do this outside of jenkins. > Jenkins build process needs to allow for setting the appropriate version > number within the built JARs. > -- > > Key: CLOUDSTACK-43 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-43 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: pre-4.0.0, 4.1.0 >Reporter: Chip Childers >Assignee: Pradeep Soundararajan >Priority: Critical > > The Jenkins binary build processes are producing JAR files that contain > version numbers like 4.0.0-SNAPSHOT. We need a way to set a parameter within > the build to set the version from SNAPSHOT to RC1 or even drop the > pre-release identifier entirely (so that we can generate an actual release). -- 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-1289) [F5-SRX-InlineMode] Usage stats are not generated for Juniper SRX Firewall in inlinemode
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582273#comment-13582273 ] Chip Childers commented on CLOUDSTACK-1289: --- Kishan, Any update? > [F5-SRX-InlineMode] Usage stats are not generated for Juniper SRX Firewall in > inlinemode > > > Key: CLOUDSTACK-1289 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1289 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Usage >Affects Versions: 4.1.0 > Environment: ASF 4.1 branch latest code >Reporter: Sanjeev N >Assignee: Kishan Kavala >Priority: Blocker > Fix For: 4.1.0 > > Attachments: vmops.rar > > > [F5-SRX-InlineMode] Usage stats are not generated for Juniper SRX Firewall in > inlinemode > 1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for > LB and rest of the services are provided by VR. > 2. Add SRX device > 3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode > 4. Add a user account. > 5. Deploy few VMs using the above created NO. > 6. Acquire Ip address. > 7. Create a PF rules on this ipaddress. > 8. Acquire another Ip address. > 9. Create a Static NAT on this ipaddress. > 10. Acquire another Ip address. > 11. Create a LB rule on this ipaddress. > 12. Exersize the PF, Static NAT and Lb rules so that network tarffic is > created. > Observations: > === > user_statistics table in cloud db does not have an entry created for > external_firewall provider. Following is the user_statistics table output: > mysql> select * from user_statistics; > ++++---+---+--++++++++ > | id | data_center_id | account_id | public_ip_address | device_id | > device_type | network_id | net_bytes_received | net_bytes_sent | > current_bytes_received | current_bytes_sent | agg_bytes_received | > agg_bytes_sent | > ++++---+---+--++++++++ > | 1 | 1 | 2 | NULL |34 | > DomainRouter |204 | 0 | 0 | > 0 | 0 | 0 | 0 > | > | 2 | 1 | 2 | 10.147.48.26 | 5 | > ExternalLoadBalancer |204 | 0 | 0 | > 0 | 0 | 0 | 0 > | > | 3 | 1 | 4 | NULL |58 | > DomainRouter |209 | 0 | 0 | > 85917 | 307236 | 85917 | 303636 > | > | 4 | 1 | 2 | NULL |78 | > DomainRouter |210 | 0 | 0 | > 0 | 0 | 0 | 0 > | > | 5 | 1 | 2 | NULL |86 | > DomainRouter |211 | 0 | 0 | > 0 | 0 | 0 | 0 > | > | 6 | 1 | 2 | 10.147.48.27 | 5 | > ExternalLoadBalancer |211 | 0 | 0 | > 0 | 0 | 0 | 0 > | > | 7 | 1 | 2 | NULL |89 | > DomainRouter |204 | 0 | 0 | > 0 | 0 | 0 | 0 > | > ++++---+---+--++++++++ > 7 rows in set (0.00 sec) > mysql> select * from external_firewall_devices; > ++--+-+---++--+--+--+-+--+ > | id | uuid | physical_network_id | > provider_name | device_name| device_state | is_dedicated | > allocation_state | host_id | capacity | > ++--
[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-tabpanel&focusedCommentId=13582271#comment-13582271 ] Chip Childers commented on CLOUDSTACK-1252: --- Is this a duplicate of CLOUDSTACK-1228? > 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: KVM, VMware >Affects Versions: 4.1.0 > Environment: CentOS6.3 > 4.1 branch build > Hyper visor : VMware >Reporter: Rayees Namathponnan >Assignee: Nitin Mehta >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-1228) Unable to Create System Vm's in the VMware Hypervisor setup.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582269#comment-13582269 ] Chip Childers commented on CLOUDSTACK-1228: --- Venkata, Can you perhaps collaborate in real-time (sit down with or chat with) Kiran to get this sorted out? > Unable to Create System Vm's in the VMware Hypervisor setup. > > > Key: CLOUDSTACK-1228 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1228 > 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 >Reporter: Kiran Koneti >Assignee: Venkata Siva Vijayendra Bhamidipati >Priority: Blocker > Fix For: 4.1.0 > > Attachments: catalina.2013-02-11.zip, catalina.zip, > management-server-18-2-2013.zip, management-server.zip > > > Created a Advanced Zone setup using the Latest 4.1 build > (http://repo-ccp.citrix.com/releases/ASF/rhel/6.3/4.1/CloudStack-non-OSS-11-rhel6.3.tar.gz) > While trying to create the system VM's error messages are obserevd. > Attaching the Management server logs. > Error message Observed: > Executing copyTemplateFromSecondaryToPrimary. secondaryStorage: > nfs://10.147.28.7/export/home/kiran/s, templatePathAtSecondaryStorage: > template/tmpl/1/8/, templateName: routing-8 > 2013-02-11 23:03:41,530 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.47bfef59 > 2013-02-11 23:03:41,531 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.648a617f > 2013-02-11 23:03:41,531 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.2257f5b0 > 2013-02-11 23:03:41,532 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.3e22e9af > 2013-02-11 23:03:41,533 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.1e46e9bc > 2013-02-11 23:03:41,534 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.49fee4a0 > 2013-02-11 23:03:41,535 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.c1b6a94 > 2013-02-11 23:03:41,535 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.5604ba42 > 2013-02-11 23:03:41,536 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.3632e0de > 2013-02-11 23:03:41,537 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.22475368 > 2013-02-11 23:03:41,537 WARN [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create a mount point > 2013-02-11 23:03:41,538 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount point for > nfs://10.147.28.7/export/home/kiran/s > 2013-02-11 23:03:41,538 INFO [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Secondary storage mount point: /mnt/sec > 2013-02-11 23:03:41,538 INFO [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Executing command: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8/routing-8.ova > 2013-02-11 23:03:41,539 DEBUG [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Executing: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8/routing-8.ova > 2013-02-11 23:03:41,603 WARN [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Exception: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8/routing-8.ova > java.io.IOException: Cannot run program "tar" (in directory > "/mnt/sec/template/tmpl/1/8"): java.io.IOException: error=2, No such file or > directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:475) > at com.cloud.utils.script.Script.execute(Script.java:183) > at com.cloud.utils.script.Script.execute(Script.java:161) > at > com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:443) > at > com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:138) > at > com.cloud.hypervisor
[jira] [Closed] (CLOUDSTACK-1341) URL for the KEYs file is wrong in the installation guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers closed CLOUDSTACK-1341. - > URL for the KEYs file is wrong in the installation guide > > > Key: CLOUDSTACK-1341 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1341 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0, 4.0.1, 4.1.0 >Reporter: Chip Childers >Assignee: Chip Childers >Priority: Critical > Fix For: 4.0.2, 4.1.0 > > > The URL points to http://www.apache.org/dist/dev/incubator/cloudstack/KEYS > instead of http://www.apache.org/dist/incubator/cloudstack/KEYS. -- 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-1341) URL for the KEYs file is wrong in the installation guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-1341. --- Resolution: Fixed > URL for the KEYs file is wrong in the installation guide > > > Key: CLOUDSTACK-1341 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1341 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0, 4.0.1, 4.1.0 >Reporter: Chip Childers >Assignee: Chip Childers >Priority: Critical > Fix For: 4.0.2, 4.1.0 > > > The URL points to http://www.apache.org/dist/dev/incubator/cloudstack/KEYS > instead of http://www.apache.org/dist/incubator/cloudstack/KEYS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-1341) URL for the KEYs file is wrong in the installation guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers reassigned CLOUDSTACK-1341: - Assignee: Chip Childers > URL for the KEYs file is wrong in the installation guide > > > Key: CLOUDSTACK-1341 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1341 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0, 4.0.1, 4.1.0 >Reporter: Chip Childers >Assignee: Chip Childers >Priority: Critical > Fix For: 4.0.2, 4.1.0 > > > The URL points to http://www.apache.org/dist/dev/incubator/cloudstack/KEYS > instead of http://www.apache.org/dist/incubator/cloudstack/KEYS. -- 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-1341) URL for the KEYs file is wrong in the installation guide
Chip Childers created CLOUDSTACK-1341: - Summary: URL for the KEYs file is wrong in the installation guide Key: CLOUDSTACK-1341 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1341 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.0.0, 4.0.1, 4.1.0 Reporter: Chip Childers Priority: Critical Fix For: 4.0.2, 4.1.0 The URL points to http://www.apache.org/dist/dev/incubator/cloudstack/KEYS instead of http://www.apache.org/dist/incubator/cloudstack/KEYS. -- 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-774) Supporting kickstart in CloudStack baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581504#comment-13581504 ] Chip Childers commented on CLOUDSTACK-774: -- Only if testing and docs are done. > Supporting kickstart in CloudStack baremetal > > > Key: CLOUDSTACK-774 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-774 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: 4.1.0 >Reporter: frank zhang >Assignee: frank zhang > Fix For: 4.1.0 > > Attachments: CLOUDSTACK-774-baremetal-support.patch, > CLOUDSTACK-774-baremetal-support.patch.md5sum, > CLOUDSTACK-774-baremetal-support.patch.sig > > > Supporting kickstart install for RedHat like Linux in CloudStack Baremetal > provisioning > Release Planning: > Dev List Discussion: http://markmail.org/message/m6tg5nzfgqiwhzre > Functional Spec: https://cwiki.apache.org/CLOUDSTACK/baremetal-kickstart.html > Feature Branch: master -- 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-657) VMware vNetwork Distributed Virtual Switch support in CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578404#comment-13578404 ] Chip Childers commented on CLOUDSTACK-657: -- Since it's getting put into master now, it'll be part of our next feature release (4.2 hopefully, if we don't break API backward compatibility). +1 to that. I'm quite happy to see folks from the community crossing employer lines to help each other out! > 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] [Commented] (CLOUDSTACK-1076) Legal documentation improvements to separate source distributions from packaged distributions.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577099#comment-13577099 ] Chip Childers commented on CLOUDSTACK-1076: --- It shouldn't, but it will be reviewed during the release process at a minimum. -chip > Legal documentation improvements to separate source distributions from > packaged distributions. > -- > > Key: CLOUDSTACK-1076 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1076 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Chip Childers >Assignee: Chip Childers > Fix For: 4.1.0 > > > As discussed on the dev list, I'd like to make the following changes in > master: > * Remove all binary dependency license and notice info from the top > level LICENSE and NOTICE files in our source tree > * Create two copies of the Whisker descriptor.xml file (stored in > tools/whisker), one that can be used to regenerate the source distro's > LICENSE and NOTICE files, and one that can generate an appropriate > LICENSE and NOTICE file for a packaged version of the software. > * Generate and commit the package LICENSE and NOTICE file to the > tools/whisker folder. > * Ask that the folks working on packaging take the (to be committed) > tools/whisker/LICENSE and tools/whisker/NOTICE files as the correct > legal documents to include with the package installation. -- 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-738) Ability to manage Basic and Advanced Zone using a single instance of CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577046#comment-13577046 ] Chip Childers commented on CLOUDSTACK-738: -- Did this code actually get committed before the 4.1 feature freeze? > Ability to manage Basic and Advanced Zone using a single instance of > CloudStack > --- > > Key: CLOUDSTACK-738 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-738 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah >Assignee: Sonny Chhen > Fix For: 4.1.0 > > > Currently, CloudStack supports Basic Zones as well as Advanced Zones but the > UI supports management of only Basic Zones or Advanced Zones. > This enhancement is to track allowing management of Basic and Advanced Zones > using a single instance of CloudStack. -- 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-1198) Fix the legal documentation for Veewee configuration files stored in tools/
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1198: -- Fix Version/s: (was: 4.0.2) (was: 4.1.0) > Fix the legal documentation for Veewee configuration files stored in tools/ > --- > > Key: CLOUDSTACK-1198 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1198 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0, 4.0.1, 4.1.0 >Reporter: Chip Childers >Assignee: Chip Childers > > We need to include Veewee as a referenced project, and the MIT licensing > needs to be noted for the Veewee config files. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1198) Fix the legal documentation for Veewee configuration files stored in tools/
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers closed CLOUDSTACK-1198. - closing > Fix the legal documentation for Veewee configuration files stored in tools/ > --- > > Key: CLOUDSTACK-1198 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1198 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0, 4.0.1, 4.1.0 >Reporter: Chip Childers >Assignee: Chip Childers > Fix For: 4.0.2, 4.1.0 > > > We need to include Veewee as a referenced project, and the MIT licensing > needs to be noted for the Veewee config files. -- 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-1198) Fix the legal documentation for Veewee configuration files stored in tools/
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-1198. --- Resolution: Duplicate Assignee: Chip Childers (was: Joe Brockmeier) I actually already resolved this. Not sure why I opened a second bug, except that I managed to forget that I opened this one. > Fix the legal documentation for Veewee configuration files stored in tools/ > --- > > Key: CLOUDSTACK-1198 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1198 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0, 4.0.1, 4.1.0 >Reporter: Chip Childers >Assignee: Chip Childers > Fix For: 4.0.2, 4.1.0 > > > We need to include Veewee as a referenced project, and the MIT licensing > needs to be noted for the Veewee config files. -- 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-1228) Unable to Create System Vm's in the VMware Hypervisor setup.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576385#comment-13576385 ] Chip Childers commented on CLOUDSTACK-1228: --- This line is the interesting one to me: java.io.IOException: Cannot run program "tar" (in directory "/mnt/sec/template/tmpl/1/8"): java.io.IOException: error=2, No such file or directory But I realized that I asked a silly question. The better question is: Does this file exist? /mnt/sec/template/tmpl/1/8/routing-8.ova > Unable to Create System Vm's in the VMware Hypervisor setup. > > > Key: CLOUDSTACK-1228 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1228 > 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 >Reporter: Kiran Koneti >Priority: Blocker > Fix For: 4.1.0 > > Attachments: management-server.zip > > > Created a Advanced Zone setup using the Latest 4.1 build > (http://repo-ccp.citrix.com/releases/ASF/rhel/6.3/4.1/CloudStack-non-OSS-11-rhel6.3.tar.gz) > While trying to create the system VM's error messages are obserevd. > Attaching the Management server logs. > Error message Observed: > Executing copyTemplateFromSecondaryToPrimary. secondaryStorage: > nfs://10.147.28.7/export/home/kiran/s, templatePathAtSecondaryStorage: > template/tmpl/1/8/, templateName: routing-8 > 2013-02-11 23:03:41,530 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.47bfef59 > 2013-02-11 23:03:41,531 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.648a617f > 2013-02-11 23:03:41,531 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.2257f5b0 > 2013-02-11 23:03:41,532 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.3e22e9af > 2013-02-11 23:03:41,533 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.1e46e9bc > 2013-02-11 23:03:41,534 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.49fee4a0 > 2013-02-11 23:03:41,535 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.c1b6a94 > 2013-02-11 23:03:41,535 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.5604ba42 > 2013-02-11 23:03:41,536 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.3632e0de > 2013-02-11 23:03:41,537 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.22475368 > 2013-02-11 23:03:41,537 WARN [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create a mount point > 2013-02-11 23:03:41,538 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount point for > nfs://10.147.28.7/export/home/kiran/s > 2013-02-11 23:03:41,538 INFO [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Secondary storage mount point: /mnt/sec > 2013-02-11 23:03:41,538 INFO [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Executing command: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8/routing-8.ova > 2013-02-11 23:03:41,539 DEBUG [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Executing: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8/routing-8.ova > 2013-02-11 23:03:41,603 WARN [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Exception: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8/routing-8.ova > java.io.IOException: Cannot run program "tar" (in directory > "/mnt/sec/template/tmpl/1/8"): java.io.IOException: error=2, No such file or > directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:475) > at com.cloud.utils.script.Script.execute(Script.java:183) > at com.cloud.utils.script.Script.execute(Script.java:161) > at > com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:443) > at > com.cloud.hypervisor.vmware.manager.VmwareStorageManagerIm
[jira] [Assigned] (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:all-tabpanel ] Chip Childers reassigned CLOUDSTACK-1234: - Assignee: Hugo Trippaers Hugo, This sounds like it may be a packaging issue (but I'm obviously not sure). Do you mind reviewing? It's targeting CentOS 6.3. > 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: Hugo Trippaers >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] [Updated] (CLOUDSTACK-1223) Exception while starting jetty server: org.springframework.beans.factory.BeanCreationException Error creating bean with name 'apiServer':
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chip Childers updated CLOUDSTACK-1223:
--
Assignee: Rohit Yadav
Rohit,
I know you were working on DB setup related stuff. Can you please review and
see if you can resolve this?
Thanks!
> Exception while starting jetty server:
> org.springframework.beans.factory.BeanCreationException Error creating bean
> with name 'apiServer':
> --
>
> Key: CLOUDSTACK-1223
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1223
> 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: Ubuntu 11.10
>Reporter: Sowmya Krishnan
>Assignee: Rohit Yadav
>Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: jira1223.log
>
>
> Unable to start up jetty off the latest git pull from 4.1 branch.
> I am getting the following exception (i am using maven3, on ubuntu 11.10)
> I am on commit id: a184816488a73bbe60e6a36ac6b68c53b07ae41b
> Getting the following exception while running jetty command: mvn -pl
> :cloud-client-ui jetty:run
> 2013-02-11 14:45:27.206:WARN::Failed startup of context
> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@1a4250a{/client,/home/sowmya/ACS/incubator-cloudstack/client/target/cloud-client-ui-4.1.0-SNAPSHOT}
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'apiServer': Invocation of init method failed; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: null
> at
> org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:135)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:394)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1448)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:609)
> at
> org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469)
> at
> org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383)
> at
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283)
> at
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
> at
> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>
[jira] [Commented] (CLOUDSTACK-1228) Unable to Create System Vm's in the VMware Hypervisor setup.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576366#comment-13576366 ] Chip Childers commented on CLOUDSTACK-1228: --- Is tar installed on the effected system? > Unable to Create System Vm's in the VMware Hypervisor setup. > > > Key: CLOUDSTACK-1228 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1228 > 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 >Reporter: Kiran Koneti >Priority: Blocker > Fix For: 4.1.0 > > Attachments: management-server.zip > > > Created a Advanced Zone setup using the Latest 4.1 build > (http://repo-ccp.citrix.com/releases/ASF/rhel/6.3/4.1/CloudStack-non-OSS-11-rhel6.3.tar.gz) > While trying to create the system VM's error messages are obserevd. > Attaching the Management server logs. > Error message Observed: > Executing copyTemplateFromSecondaryToPrimary. secondaryStorage: > nfs://10.147.28.7/export/home/kiran/s, templatePathAtSecondaryStorage: > template/tmpl/1/8/, templateName: routing-8 > 2013-02-11 23:03:41,530 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.47bfef59 > 2013-02-11 23:03:41,531 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.648a617f > 2013-02-11 23:03:41,531 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.2257f5b0 > 2013-02-11 23:03:41,532 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.3e22e9af > 2013-02-11 23:03:41,533 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.1e46e9bc > 2013-02-11 23:03:41,534 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.49fee4a0 > 2013-02-11 23:03:41,535 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.c1b6a94 > 2013-02-11 23:03:41,535 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.5604ba42 > 2013-02-11 23:03:41,536 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.3632e0de > 2013-02-11 23:03:41,537 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount: > /var/lib/cloud/mnt/VM/7313725325399.22475368 > 2013-02-11 23:03:41,537 WARN [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create a mount point > 2013-02-11 23:03:41,538 ERROR [vmware.manager.VmwareManagerImpl] > (DirectAgent-2:10.147.40.18) Unable to create mount point for > nfs://10.147.28.7/export/home/kiran/s > 2013-02-11 23:03:41,538 INFO [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Secondary storage mount point: /mnt/sec > 2013-02-11 23:03:41,538 INFO [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Executing command: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8/routing-8.ova > 2013-02-11 23:03:41,539 DEBUG [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Executing: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8/routing-8.ova > 2013-02-11 23:03:41,603 WARN [vmware.manager.VmwareStorageManagerImpl] > (DirectAgent-2:10.147.40.18) Exception: tar --no-same-owner -xf > /mnt/sec/template/tmpl/1/8/routing-8.ova > java.io.IOException: Cannot run program "tar" (in directory > "/mnt/sec/template/tmpl/1/8"): java.io.IOException: error=2, No such file or > directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:475) > at com.cloud.utils.script.Script.execute(Script.java:183) > at com.cloud.utils.script.Script.execute(Script.java:161) > at > com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.copyTemplateFromSecondaryToPrimary(VmwareStorageManagerImpl.java:443) > at > com.cloud.hypervisor.vmware.manager.VmwareStorageManagerImpl.execute(VmwareStorageManagerImpl.java:138) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3587) > at > com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:401) > at > com.cloud.agen
[jira] [Commented] (CLOUDSTACK-1206) Failure in Copy of System templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576364#comment-13576364 ] Chip Childers commented on CLOUDSTACK-1206: --- Pradeep - Can you work with Rayees to see if we can get past this issue? > Failure in Copy of System templates > > > Key: CLOUDSTACK-1206 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1206 > 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 >Reporter: Rayees Namathponnan >Assignee: Pradeep Soundararajan > Fix For: 4.1.0 > > > Step 1 : Created new build from 4.1 branch > Step 2 : Install and configured MS server > Step 3 : Run below command to prepare system template > /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m > /mnt/secondary/ -u > http://download.cloud.com/templates/acton/acton-systemvm-02062012.ova -h > vmware > Actual result > Failed to prepare system template, since > /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt > still referring to "/etc/cloud/management" not "/etc/cloudstack/management" > Then i modified > /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt with > "/etc/cloud/management" to "/etc/cloudstack/management", but i am unable to > download template, getting below error > [root@auto_ms3 management]# > /usr/lib64/cloud/agent/scripts/storage/secondary/cloud-install-sys-tmplt -m > /mnt/secondary2/ -u > http://download.cloud.com/templates/acton/acton-systemvm-02062012.ova -h > vmware > Exception in thread "main" java.lang.NoClassDefFoundError: > org/jasypt/intf/cli/JasyptPBEStringDecryptionCLI > Caused by: java.lang.ClassNotFoundException: > org.jasypt.intf.cli.JasyptPBEStringDecryptionCLI > at java.net.URLClassLoader$1.run(URLClassLoader.java:217) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:205) > at java.lang.ClassLoader.loadClass(ClassLoader.java:321) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) > at java.lang.ClassLoader.loadClass(ClassLoader.java:266) > Could not find the main class: > org.jasypt.intf.cli.JasyptPBEStringDecryptionCLI. Program will exit. > Failed to decrypt DB password from db.properties > Installation failed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1235) Management failed to start with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576365#comment-13576365 ] Chip Childers commented on CLOUDSTACK-1235: --- What environment is this in? How are others testing if the mgmt server isn't able to start? Specifics would help! Thanks. > Management failed to start with NPE > --- > > Key: CLOUDSTACK-1235 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1235 > 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: Srikanteswararao Talluri >Priority: Blocker > > (HA-Worker-0:null) Caught this throwable, > java.lang.NullPointerException > 2013-02-12 04:05:17,819 ERROR [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-0:null) Caught this throwable, > java.lang.NullPointerException > 2013-02-12 04:05:17,819 ERROR [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-0:null) Caught this throwable, > java.lang.NullPointerException > 2013-02-12 04:05:17,799 ERROR [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:null) Caught this throwable, > java.lang.NullPointerException > 2013-02-12 04:05:17,835 ERROR [cloud.ha.HighAvailabilityManagerImpl] > (HA-Worker-3:null) Caught this throwable, > java.lang.NullPointerException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1233) Veewee configuration files are inappropriately identified as ASLv2 licensed files
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers closed CLOUDSTACK-1233. - Resolution: Fixed Closing, as I think this is fixed now. > Veewee configuration files are inappropriately identified as ASLv2 licensed > files > - > > Key: CLOUDSTACK-1233 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1233 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0, 4.1.0 >Reporter: Chip Childers >Assignee: Chip Childers > Fix For: 4.1.0 > > > The veewee configuration files used for the devcloud base-box build, as well > as the newly introduced files used to create a system vm, are inappropriately > identified as ASLv2 licensed and copyrighted by the ASF. > To fix: > The ASF headers need to be stripped, to match the source. > The files need to be excluded from RAT checks in the root pom. > The tools/whisker/descriptor.xml file needs to be updated to appropriately > credit the Veewee author and list the files as being under the MIT license. > The root LICENSE and NOTICE need to be re-generated > We should not have to change the descriptor-for-packaging.xml (and generated > legal docs), because we are not packaging these artifacts. -- 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-1233) Veewee configuration files are inappropriately identified as ASLv2 licensed files
Chip Childers created CLOUDSTACK-1233: - Summary: Veewee configuration files are inappropriately identified as ASLv2 licensed files Key: CLOUDSTACK-1233 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1233 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.0.0, 4.1.0 Reporter: Chip Childers Assignee: Chip Childers Fix For: 4.1.0 The veewee configuration files used for the devcloud base-box build, as well as the newly introduced files used to create a system vm, are inappropriately identified as ASLv2 licensed and copyrighted by the ASF. To fix: The ASF headers need to be stripped, to match the source. The files need to be excluded from RAT checks in the root pom. The tools/whisker/descriptor.xml file needs to be updated to appropriately credit the Veewee author and list the files as being under the MIT license. The root LICENSE and NOTICE need to be re-generated We should not have to change the descriptor-for-packaging.xml (and generated legal docs), because we are not packaging these artifacts. -- 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-449) Disk I/O polling for instances
[ https://issues.apache.org/jira/browse/CLOUDSTACK-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574661#comment-13574661 ] Chip Childers commented on CLOUDSTACK-449: -- I'm not sure if Wido has started working on this or not, but if you want to try to build it, that would be great! > Disk I/O polling for instances > -- > > Key: CLOUDSTACK-449 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-449 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Management Server, Usage, VMware, Xen >Reporter: Wido den Hollander >Priority: Minor > > Disk I/O polling for instances would gather disk I/O statistics for root and > data volumes attached to instancesn, just like we do with network traffic. > This enables administrators to figure out how much I/O each instance is > doing. In public clouds users might want to start billing for this. > This is not a monitoring solution for the backing storage, it doesn't alarm > about high disk I/O, it simply accounts how much I/O each instance is doing. > The function specification for this is online at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Feature+Disk+IO+statistics+for+instances -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1093) Deprecate current api server and developer a REST compliant API Server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1093: -- Fix Version/s: (was: 4.2.0) Future > Deprecate current api server and developer a REST compliant API Server > -- > > Key: CLOUDSTACK-1093 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1093 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav > Fix For: Future > > > Deprecate current apis and api server over next 1-2 years and develop a REST > compliant api server using JAX-RS or better technologies. The server should > be a separate component and not another monolithic entities inside CloudStack. -- 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-1199) External DNS not being added to reslov.conf
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1199: -- Affects Version/s: (was: 4.0.2) 4.0.1 > External DNS not being added to reslov.conf > > > Key: CLOUDSTACK-1199 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1199 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.0.1 > Environment: 4.0.1 >Reporter: Anthony Xu >Assignee: Anthony Xu > Fix For: 4.1.0 > > > only internal DNS is added to reslov.conf of guest VM > expected behavior, > if global configuration use.external.dns is ture > only external DNS is added to reslov.conf of guest VM > else > both internal DNS and external DNS is added to resolv.conf of guest VM -- 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-1199) External DNS not being added to reslov.conf
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1199: -- Environment: 4.0.1 (was: 4.0.2) > External DNS not being added to reslov.conf > > > Key: CLOUDSTACK-1199 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1199 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.0.2 > Environment: 4.0.1 >Reporter: Anthony Xu >Assignee: Anthony Xu > Fix For: 4.1.0 > > > only internal DNS is added to reslov.conf of guest VM > expected behavior, > if global configuration use.external.dns is ture > only external DNS is added to reslov.conf of guest VM > else > both internal DNS and external DNS is added to resolv.conf of guest VM -- 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-1198) Fix the legal documentation for Veewee configuration files stored in tools/
Chip Childers created CLOUDSTACK-1198: - Summary: Fix the legal documentation for Veewee configuration files stored in tools/ Key: CLOUDSTACK-1198 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1198 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.0.0, 4.0.1, 4.1.0 Reporter: Chip Childers Fix For: 4.0.2, 4.1.0 We need to include Veewee as a referenced project, and the MIT licensing needs to be noted for the Veewee config files. -- 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-1186) Mention irc channels on incubator.apache.org/cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-1186. --- Resolution: Fixed All done. > Mention irc channels on incubator.apache.org/cloudstack > --- > > Key: CLOUDSTACK-1186 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1186 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Website >Reporter: Rohit Yadav >Assignee: Chip Childers > > On the page, mentions all different irc channels; > http://incubator.apache.org/cloudstack/contribute.html > #cloudstack --- users > #cloudstack-dev -- development > #cloudstack-meeting -- meetings -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1186) Mention irc channels on incubator.apache.org/cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers closed CLOUDSTACK-1186. - > Mention irc channels on incubator.apache.org/cloudstack > --- > > Key: CLOUDSTACK-1186 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1186 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Website >Reporter: Rohit Yadav >Assignee: Chip Childers > > On the page, mentions all different irc channels; > http://incubator.apache.org/cloudstack/contribute.html > #cloudstack --- users > #cloudstack-dev -- development > #cloudstack-meeting -- meetings -- 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-1186) Mention irc channels on incubator.apache.org/cloudstack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1186: -- Component/s: Website Assignee: Chip Childers I'll grab this one. > Mention irc channels on incubator.apache.org/cloudstack > --- > > Key: CLOUDSTACK-1186 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1186 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Website >Reporter: Rohit Yadav >Assignee: Chip Childers > > On the page, mentions all different irc channels; > http://incubator.apache.org/cloudstack/contribute.html > #cloudstack --- users > #cloudstack-dev -- development > #cloudstack-meeting -- meetings -- 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-999) Plugin to provide Hyper-V 2012 support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-999: - Affects Version/s: (was: 4.1.0) 4.2.0 Fix Version/s: (was: 4.1.0) 4.2.0 Shifting to 4.2, based on the feature cut-off date. > Plugin to provide Hyper-V 2012 support > -- > > Key: CLOUDSTACK-999 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-999 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Template, UI >Affects Versions: 4.2.0 > Environment: Hyper-V 2012 is available on releases of Windows > operating system from 2012 onwards. E.g. Windows Server 2012, and Hyper-V > Server 2012. > The plugin will execute at least in part on the CloudStack management server. >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Labels: Hyper-V, newbie > Fix For: 4.2.0 > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hyper-V+2012+%283.0%29+Support -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-1034) Merge to Master
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1034: -- Affects Version/s: (was: 4.1.0) 4.2.0 Fix Version/s: (was: 4.1.0) 4.2.0 > Merge to Master > --- > > Key: CLOUDSTACK-1034 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1034 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Template, UI >Affects Versions: 4.2.0 >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Fix For: 4.2.0 > > > Synchronise the development branch with master, and determine what source > needs to be merged. -- 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-1033) Deployment Guides
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1033: -- Affects Version/s: (was: 4.1.0) 4.2.0 Fix Version/s: (was: 4.1.0) 4.2.0 > Deployment Guides > - > > Key: CLOUDSTACK-1033 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1033 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, Hypervisor Controller, Management Server >Affects Versions: 4.2.0 >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Fix For: 4.2.0 > > > Provide description of how to deploy the plugin with a management server, and > how to get the remote agent running on the hypervisor. -- 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-1031) Hypervisor Plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1031: -- Affects Version/s: (was: 4.1.0) Fix Version/s: (was: 4.1.0) 4.2.0 > Hypervisor Plugin > - > > Key: CLOUDSTACK-1031 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1031 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller > Environment: Windows O/S running Hyper-V 2012 >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Fix For: 4.2.0 > > > Plugin responsible for receiving message from management server and > dispatching to agent that will use WMI and file system to implement the > hypervisor commands and backing storage. -- 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-1032) Management Server updates for VHDX templates, and Hyper-V clusters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1032: -- Affects Version/s: (was: 4.1.0) 4.2.0 Fix Version/s: (was: 4.1.0) 4.2.0 > Management Server updates for VHDX templates, and Hyper-V clusters > -- > > Key: CLOUDSTACK-1032 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1032 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: API, Template, UI >Affects Versions: 4.2.0 >Reporter: Donal Lafferty >Assignee: Donal Lafferty > Fix For: 4.2.0 > > > UI exposed by management server must allow templates with the VHDX image type > used by Hyper-V 2012, and it must allow Hyper-V clusters to be configured. > SystemVMs are not available in this phase, so management server should be > stopped from attempting to create them on this kind of cluster. -- 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-1000) QA - Plugin to provide Hyper V support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1000: -- Affects Version/s: (was: 4.1.0) 4.2.0 Fix Version/s: 4.2.0 > QA - Plugin to provide Hyper V support > -- > > Key: CLOUDSTACK-1000 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1000 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller >Affects Versions: 4.2.0 >Reporter: Sudha Ponnaganti > Fix For: 4.2.0 > > > Need to post the following to ACS Wiki > - Unit Test Cases > - Functional test cases > - Test results -- 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-1001) Doc - Huper V Support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1001: -- Fix Version/s: 4.2.0 > Doc - Huper V Support > - > > Key: CLOUDSTACK-1001 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1001 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Template, UI >Reporter: Sudha Ponnaganti > Fix For: 4.2.0 > > > Need to document Hyper V Support -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-40) New Image based provisioning method for Baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572398#comment-13572398 ] Chip Childers commented on CLOUDSTACK-40: - So did this get completed for 4.1.0? If so, what's the commit-sh on master? If not, can we move it to 4.2? > New Image based provisioning method for Baremetal > - > > Key: CLOUDSTACK-40 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-40 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: pre-4.0.0 >Reporter: Rohit Yadav >Assignee: frank zhang > Fix For: 4.1.0 > > > Get rid of PING, implement a solution that: > - takes/restores image on host: Use Partimage or DD to restore a disk image > to baremetal host and take an image from host and saving as CloudStack > template > - a way to notify state of provisioning. Especially when provisioning is done. > - have a well organized API and doc > - easy to setup. > Release Planning: > Dev List Discussion: http://markmail.org/thread/lpfptu7wv22pexlk > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Baremetal > Feature Branch: Unknown -- 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-1165) VMware resource manager not found
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571698#comment-13571698 ] Chip Childers commented on CLOUDSTACK-1165: --- Did you build as non-oss with the VMware jars? > VMware resource manager not found > - > > Key: CLOUDSTACK-1165 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1165 > 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: Centos 6.3, vmware >Reporter: Venkata Siva Vijayendra Bhamidipati > > When creating a vmware cluster, the mgmt server fails with this message: > INFO [cloud.api.ApiServer] (1719136796@qtp-119090941-4:) Could not find > corresponding resource manager for VMware > The corresponding vmops.log excerpt is pasted below: > 2013-02-05 11:36:31,187 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-10:job-10) Executing > org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd for > job-10 > 2013-02-05 11:36:31,230 DEBUG [cloud.network.NetworkServiceImpl] > (Job-Executor-10:job-10) ISOLATION METHODS:[VLAN] > 2013-02-05 11:36:31,238 DEBUG [cloud.network.NetworkServiceImpl] > (Job-Executor-10:job-10) Deleting existing vnet range for the physicalNetwork > id= 200 and zone id=1 as a part of updatePhysicalNetwork call > 2013-02-05 11:36:31,239 DEBUG [cloud.network.NetworkServiceImpl] > (Job-Executor-10:job-10) Adding vnet range 2410-2430 for the physicalNetwork > id= 200 and zone id=1 as a part of updatePhysicalNetwork call > 2013-02-05 11:36:31,377 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-10:job-10) Complete async job-10, jobStatus: 1, resultCode: 0, > result: org.apache.cloudstack.api.response.PhysicalNetworkResponse@55c70eac > 2013-02-05 11:36:31,411 DEBUG [cloud.async.AsyncJobManagerImpl] > (Job-Executor-10:job-10) Done executing > org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd for > job-10 > 2013-02-05 11:36:34,191 DEBUG [cloud.api.ApiServlet] > (1719136796@qtp-119090941-4:null) ===START=== 10.217.252.50 -- GET > command=queryAsyncJobResult&jobid=d6d4b60a-5b95-4e70-a4ee-9654d8116a45&response=json&sessionkey=w7y8aGapGgsNK4wDAirE7QC2GBc%3D&_=1360092994083 > 2013-02-05 11:36:34,228 DEBUG [cloud.async.AsyncJobManagerImpl] > (1719136796@qtp-119090941-4:null) Async job-10 completed > 2013-02-05 11:36:34,236 DEBUG [cloud.api.ApiServlet] > (1719136796@qtp-119090941-4:null) ===END=== 10.217.252.50 -- GET > command=queryAsyncJobResult&jobid=d6d4b60a-5b95-4e70-a4ee-9654d8116a45&response=json&sessionkey=w7y8aGapGgsNK4wDAirE7QC2GBc%3D&_=1360092994083 > 2013-02-05 11:36:34,243 DEBUG [cloud.api.ApiServlet] > (1719136796@qtp-119090941-4:null) ===START=== 10.217.252.50 -- GET > command=addCluster&zoneId=d7a58f91-34f1-4727-843f-730120b15224&hypervisor=VMware&clustertype=ExternalManaged&podId=aa86996d-21e4-467b-81c8-a3bdedffe932&username=Administrator&url=http%3A%2F%2F10.223.52.61%2Fvijay-dc%2Fcluster1&clustername=10.223.52.61%2Fvijay-dc%2Fcluster1&response=json&sessionkey=w7y8aGapGgsNK4wDAirE7QC2GBc%3D&_=1360092994135 > 2013-02-05 11:36:34,330 INFO [cloud.api.ApiServer] > (1719136796@qtp-119090941-4:null) Could not find corresponding resource > manager for VMware > 2013-02-05 11:36:34,332 DEBUG [cloud.api.ApiServlet] > (1719136796@qtp-119090941-4:null) ===END=== 10.217.252.50 -- GET > command=addCluster&zoneId=d7a58f91-34f1-4727-843f-730120b15224&hypervisor=VMware&clustertype=ExternalManaged&podId=aa86996d-21e4-467b-81c8-a3bdedffe932&username=Administrator&url=http%3A%2F%2F10.223.52.61%2Fvijay-dc%2Fcluster1&clustername=10.223.52.61%2Fvijay-dc%2Fcluster1&response=json&sessionkey=w7y8aGapGgsNK4wDAirE7QC2GBc%3D&_=1360092994135 -- 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-197) Support for EC2 Query API (rest interface)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-197: - Assignee: Likitha Shetty (was: Chip Childers) > Support for EC2 Query API (rest interface) > -- > > Key: CLOUDSTACK-197 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-197 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Reporter: Likitha Shetty >Assignee: Likitha Shetty > Fix For: 4.1.0 > > > Introduce support for query api for the current set of AWS apis supported by > SOAP. > Release Planning: > Dev List Discussion: http://markmail.org/message/b6hdkyldogqgemjp > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/EC2++-+Functional+Spec+for+Query+API+support > Feature Branch: Will come in as reviews -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CLOUDSTACK-197) Support for EC2 Query API (rest interface)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers reassigned CLOUDSTACK-197: Assignee: Chip Childers (was: Likitha Shetty) > Support for EC2 Query API (rest interface) > -- > > Key: CLOUDSTACK-197 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-197 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: AWSAPI >Reporter: Likitha Shetty >Assignee: Chip Childers > Fix For: 4.1.0 > > > Introduce support for query api for the current set of AWS apis supported by > SOAP. > Release Planning: > Dev List Discussion: http://markmail.org/message/b6hdkyldogqgemjp > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/EC2++-+Functional+Spec+for+Query+API+support > Feature Branch: Will come in as reviews -- 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-240) Create-Tag feature is not avialable for VPN Customer Gateway
[ https://issues.apache.org/jira/browse/CLOUDSTACK-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-240: - Fix Version/s: (was: 4.1.0) 4.2.0 > Create-Tag feature is not avialable for VPN Customer Gateway > - > > Key: CLOUDSTACK-240 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-240 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: pre-4.0.0 >Reporter: prashant kumar mishra >Assignee: Alena Prokharchyk >Priority: Minor > Fix For: 4.2.0 > > > There is no option to tag VPN Customer Gateway. > Steps to check > -- > -- > 1-Go to network tab > 2-From select view select VPN Customer Gateway > 3- Click on add VPN Customer Gateway > 5-Select the VPN Customer Gateway > 6-there is no option to create/add Tag for VPN Customer Gateway > Release Planning: > Dev List Discussion: Unknown > Functional Spec: N/A > Feature Branch: Unknown > Documentation: Not needed > QA: Needs to be tested -- 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-150) Configure Maven to build rpm packages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-150: - Fix Version/s: (was: 4.1.0) > Configure Maven to build rpm packages > - > > Key: CLOUDSTACK-150 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-150 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Hugo Trippaers >Priority: Blocker > > Configure rpm-maven-plugin (http://mojo.codehaus.org/rpm-maven-plugin) to > build rpm packages, deprecate waf for building rpms. > Release Planning: > Dev list discussion: http://markmail.org/message/wwa74uqid3g2fuh6 > Functional Spec: unknown > Feature Branch: unknown > Docs task is CLOUDSTACK-1 > QA will occur based on testing the whole release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-149) Configure Maven to build deb packages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers closed CLOUDSTACK-149. Resolution: Won't Fix per Wido's comments - closing as won't fix > Configure Maven to build deb packages > - > > Key: CLOUDSTACK-149 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-149 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Reporter: Rohit Yadav >Assignee: Wido den Hollander >Priority: Blocker > > Configure a maven plugin to package debian packages. Deprecate waf as a > packaging tool. > Release Planning: > Dev list discussion: http://markmail.org/message/4yp5olwhept3wtd6 > Functional Spec: unknown > Feature Branch: unknown > Docs task is CLOUDSTACK-1 > QA will occur based on testing the whole release. -- 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-149) Configure Maven to build deb packages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-149: - Fix Version/s: (was: 4.1.0) > Configure Maven to build deb packages > - > > Key: CLOUDSTACK-149 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-149 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Reporter: Rohit Yadav >Assignee: Wido den Hollander >Priority: Blocker > > Configure a maven plugin to package debian packages. Deprecate waf as a > packaging tool. > Release Planning: > Dev list discussion: http://markmail.org/message/4yp5olwhept3wtd6 > Functional Spec: unknown > Feature Branch: unknown > Docs task is CLOUDSTACK-1 > QA will occur based on testing the whole release. -- 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-149) Configure Maven to build deb packages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers reopened CLOUDSTACK-149: -- > Configure Maven to build deb packages > - > > Key: CLOUDSTACK-149 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-149 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Reporter: Rohit Yadav >Assignee: Wido den Hollander >Priority: Blocker > Fix For: 4.1.0 > > > Configure a maven plugin to package debian packages. Deprecate waf as a > packaging tool. > Release Planning: > Dev list discussion: http://markmail.org/message/4yp5olwhept3wtd6 > Functional Spec: unknown > Feature Branch: unknown > Docs task is CLOUDSTACK-1 > QA will occur based on testing the whole release. -- 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-101) OVS support in KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571652#comment-13571652 ] Chip Childers commented on CLOUDSTACK-101: -- I notice that the docs are done... but is the feature complete? If so, can the commit-sh from master please be provided? > OVS support in KVM > -- > > Key: CLOUDSTACK-101 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-101 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: pre-4.0.0, 4.0.0 >Reporter: Prasanna Santhanam >Assignee: Hugo Trippaers > Labels: kvm, ovs > Fix For: 4.1.0 > > > OVS support currently works for XenServer but not in KVM. This is to improve > the KVM agent to support OVS which has been part of the Linux kernel mainline > for sometime now. > Release Planning: > Dev list discussion: http://markmail.org/thread/x2zncdgac52essxf > Functional Spec: unknown > Feature Branch: unknown -- 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-40) New Image based provisioning method for Baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571648#comment-13571648 ] Chip Childers commented on CLOUDSTACK-40: - What's the difference between this and CLOUDSTACK-774? > New Image based provisioning method for Baremetal > - > > Key: CLOUDSTACK-40 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-40 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: pre-4.0.0 >Reporter: Rohit Yadav >Assignee: frank zhang > Fix For: 4.1.0 > > > Get rid of PING, implement a solution that: > - takes/restores image on host: Use Partimage or DD to restore a disk image > to baremetal host and take an image from host and saving as CloudStack > template > - a way to notify state of provisioning. Especially when provisioning is done. > - have a well organized API and doc > - easy to setup. > Release Planning: > Dev List Discussion: http://markmail.org/thread/lpfptu7wv22pexlk > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Baremetal > Feature Branch: Unknown -- 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-1059) Stop cloudstack mailing list from stripping TO/CC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571601#comment-13571601 ] Chip Childers commented on CLOUDSTACK-1059: --- I don't think that this Jira item is really supposed to be in the CLOUDSTACK project. The INFRA team are the ones that manage the listserv. > Stop cloudstack mailing list from stripping TO/CC > - > > Key: CLOUDSTACK-1059 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1059 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Sheng Yang >Assignee: David Nalley >Priority: Critical > > According to the discussion on > http://comments.gmane.org/gmane.comp.apache.cloudstack.devel/9216 > We would like to stop cloudstack mailing list from sending out mail with > stripped TO/CC, and would change to use TO/CC to keep people in thread. -- 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-1076) Legal documentation improvements to separate source distributions from packaged distributions.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-1076. --- Resolution: Fixed Committed to master: commit afd7de7e3312066f4d835dc73369f2cdf244da81 Author: Chip Childers Date: Mon Jan 28 10:41:48 2013 -0500 CLOUDSTACK-1076: Legal documentation improvements to separate source distributions from packaged distributions. * Remove all binary dependency license and notice info from the top level LICENSE and NOTICE files in our source tree * Create two copies of the Whisker descriptor.xml file (stored in tools/whisker), one that can be used to regenerate the source distro's LICENSE and NOTICE files, and one that can generate an appropriate LICENSE and NOTICE file for a packaged version of the software. * Generate and commit the package LICENSE and NOTICE file to the tools/whisker folder. Signed-off-by: Chip Childers > Legal documentation improvements to separate source distributions from > packaged distributions. > -- > > Key: CLOUDSTACK-1076 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1076 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Chip Childers >Assignee: Chip Childers > Fix For: 4.1.0 > > > As discussed on the dev list, I'd like to make the following changes in > master: > * Remove all binary dependency license and notice info from the top > level LICENSE and NOTICE files in our source tree > * Create two copies of the Whisker descriptor.xml file (stored in > tools/whisker), one that can be used to regenerate the source distro's > LICENSE and NOTICE files, and one that can generate an appropriate > LICENSE and NOTICE file for a packaged version of the software. > * Generate and commit the package LICENSE and NOTICE file to the > tools/whisker folder. > * Ask that the folks working on packaging take the (to be committed) > tools/whisker/LICENSE and tools/whisker/NOTICE files as the correct > legal documents to include with the package installation. -- 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-1076) Legal documentation improvements to separate source distributions from packaged distributions.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1076: -- Assignee: Chip Childers > Legal documentation improvements to separate source distributions from > packaged distributions. > -- > > Key: CLOUDSTACK-1076 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1076 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Chip Childers >Assignee: Chip Childers > Fix For: 4.1.0 > > > As discussed on the dev list, I'd like to make the following changes in > master: > * Remove all binary dependency license and notice info from the top > level LICENSE and NOTICE files in our source tree > * Create two copies of the Whisker descriptor.xml file (stored in > tools/whisker), one that can be used to regenerate the source distro's > LICENSE and NOTICE files, and one that can generate an appropriate > LICENSE and NOTICE file for a packaged version of the software. > * Generate and commit the package LICENSE and NOTICE file to the > tools/whisker folder. > * Ask that the folks working on packaging take the (to be committed) > tools/whisker/LICENSE and tools/whisker/NOTICE files as the correct > legal documents to include with the package installation. -- 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-1076) Legal documentation improvements to separate source distributions from packaged distributions.
Chip Childers created CLOUDSTACK-1076: - Summary: Legal documentation improvements to separate source distributions from packaged distributions. Key: CLOUDSTACK-1076 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1076 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Reporter: Chip Childers Fix For: 4.1.0 As discussed on the dev list, I'd like to make the following changes in master: * Remove all binary dependency license and notice info from the top level LICENSE and NOTICE files in our source tree * Create two copies of the Whisker descriptor.xml file (stored in tools/whisker), one that can be used to regenerate the source distro's LICENSE and NOTICE files, and one that can generate an appropriate LICENSE and NOTICE file for a packaged version of the software. * Generate and commit the package LICENSE and NOTICE file to the tools/whisker folder. * Ask that the folks working on packaging take the (to be committed) tools/whisker/LICENSE and tools/whisker/NOTICE files as the correct legal documents to include with the package installation. -- 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-698) Modify build to generate the LICENSE and NOTICE files
[ https://issues.apache.org/jira/browse/CLOUDSTACK-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-698: - Fix Version/s: (was: 4.1.0) 4.2.0 > Modify build to generate the LICENSE and NOTICE files > - > > Key: CLOUDSTACK-698 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-698 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.0.0 >Reporter: Chip Childers >Assignee: Chip Childers >Priority: Blocker > Fix For: 4.2.0 > > > We need to modify the build to generate the LICENSE and NOTICE files, using > the latest changes from the Apache Whisker project. > We also need to ensure that the manually completed change to resolve > CLOUDSTACK-697 is included in the 4.1.0 fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CLOUDSTACK-1035) Odd visual behavior when hovering over "Infrastructure" breadcrumb link.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers closed CLOUDSTACK-1035. - > Odd visual behavior when hovering over "Infrastructure" breadcrumb link. > > > Key: CLOUDSTACK-1035 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1035 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 > Environment: Chrome on OSX >Reporter: Chip Childers > Attachments: Screen Shot 2013-01-22 at 2.06.20 PM.png > > > See screenshot for what I'm seeing. -- 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-1035) Odd visual behavior when hovering over "Infrastructure" breadcrumb link.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-1035. --- Resolution: Invalid Based on Pranav's comment, closing as Invalid. > Odd visual behavior when hovering over "Infrastructure" breadcrumb link. > > > Key: CLOUDSTACK-1035 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1035 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 > Environment: Chrome on OSX >Reporter: Chip Childers > Attachments: Screen Shot 2013-01-22 at 2.06.20 PM.png > > > See screenshot for what I'm seeing. -- 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-1035) Odd visual behavior when hovering over "Infrastructure" breadcrumb link.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1035: -- Attachment: Screen Shot 2013-01-22 at 2.06.20 PM.png > Odd visual behavior when hovering over "Infrastructure" breadcrumb link. > > > Key: CLOUDSTACK-1035 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1035 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 > Environment: Chrome on OSX >Reporter: Chip Childers > Attachments: Screen Shot 2013-01-22 at 2.06.20 PM.png > > -- 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-1035) Odd visual behavior when hovering over "Infrastructure" breadcrumb link.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-1035: -- Description: See screenshot for what I'm seeing. > Odd visual behavior when hovering over "Infrastructure" breadcrumb link. > > > Key: CLOUDSTACK-1035 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1035 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.1.0 > Environment: Chrome on OSX >Reporter: Chip Childers > Attachments: Screen Shot 2013-01-22 at 2.06.20 PM.png > > > See screenshot for what I'm seeing. -- 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-1035) Odd visual behavior when hovering over "Infrastructure" breadcrumb link.
Chip Childers created CLOUDSTACK-1035: - Summary: Odd visual behavior when hovering over "Infrastructure" breadcrumb link. Key: CLOUDSTACK-1035 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1035 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.1.0 Environment: Chrome on OSX Reporter: Chip Childers -- 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-132) Mash up marvin into an interactive auto-completing API shell for CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555090#comment-13555090 ] Chip Childers commented on CLOUDSTACK-132: -- Sounds fine to me. Plus, it's really already out in the wild, so I think we are OK not having a specific QA task for it. Thanks for reviewing Sudha! > Mash up marvin into an interactive auto-completing API shell for CloudStack > --- > > Key: CLOUDSTACK-132 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-132 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test Tools >Affects Versions: pre-4.0.0, 4.0.0 >Reporter: Prasanna Santhanam >Assignee: Rohit Yadav > Fix For: 4.1.0 > > > The marvin libraries contain the capability to convert marvin into an > interactive shell for CloudStack. Every cloud provider has an auto-completing > shell and cloudstack lacks options for this now. This should involve > refactoring all the marvin libraries to allow for auto-completion of APIs. > Furthermore the ability to autocomplete the entities like templates, images, > virtualmachines need to exist as a part of such a shell to make it useful at > cloudscale -- 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-714) S3-based secondary Storage - eliminating a dependence on NFS as a buffer for object storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555084#comment-13555084 ] Chip Childers commented on CLOUDSTACK-714: -- Sudha, The difference was discussed here: http://markmail.org/message/ccsurkqhvxunqe26 > S3-based secondary Storage - eliminating a dependence on NFS as a buffer for > object storage > --- > > Key: CLOUDSTACK-714 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-714 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Hari Kannan >Assignee: Nitin Mehta > Fix For: 4.1.0 > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/S3-based+secondary+Storage -- 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-933) CglibThrowableRendererTest writing stack traces to terminal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554099#comment-13554099 ] Chip Childers commented on CLOUDSTACK-933: -- This is a unit test, run by default during the build process. > CglibThrowableRendererTest writing stack traces to terminal > --- > > Key: CLOUDSTACK-933 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-933 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Noa Resare >Assignee: Noa Resare >Priority: Minor > Fix For: 4.1.0 > > > The test case in CglibThrowableRendererTest writes some scary looking stack > traces to the build log via the ConsoleAppender. Moreover it doesn't actually > test anything. I suppose the functionality of the code to be tested can be > manually verified via the console output, but that's not really in the spirit > of automated unit testing. -- 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-933) CglibThrowableRendererTest writing stack traces to terminal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers resolved CLOUDSTACK-933. -- Resolution: Fixed Fix Version/s: 4.1.0 Assignee: Noa Resare Reviewboard patch committed to master: commit 1033200b0b5943cc21d5397d12d3b54b69aa2273 Author: Noa Resare Date: Wed Jan 9 16:39:10 2013 +0100 CLOUDSTACK-933: CglibThrowableRendererTest writing stack traces... Improve CglibThrowableRenderer test case Log to a separate Logger instead of the default one to avoid spurious stack traces in test run output. Actually verify that registering CglibThrowableRenderer with the alternative log hierarchy actually removes call trace lines that contains the string > CglibThrowableRendererTest writing stack traces to terminal > --- > > Key: CLOUDSTACK-933 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-933 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Noa Resare >Assignee: Noa Resare >Priority: Minor > Fix For: 4.1.0 > > > The test case in CglibThrowableRendererTest writes some scary looking stack > traces to the build log via the ConsoleAppender. Moreover it doesn't actually > test anything. I suppose the functionality of the code to be tested can be > manually verified via the console output, but that's not really in the spirit > of automated unit testing. -- 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-778) user provided hostname to be specified in vCenter instead of CloudStack generated name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers reopened CLOUDSTACK-778: -- Reopening, since we (1) don't have the code in the repo and (2) need to sort out the ip ownership questions on this feature before inclusion. Please feel free to submit to reviewboard, but note that we should NOT commit until ip clearance is complete. > user provided hostname to be specified in vCenter instead of CloudStack > generated name > -- > > Key: CLOUDSTACK-778 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-778 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: haroon abdelrahman >Assignee: Venkata Siva Vijayendra Bhamidipati > Fix For: 4.1.0 > > > Release Planning: > Dev List discussion: unknown > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Allow+user+provided+hostname%2C+internal+VM+name+on+hypervisor+for+guest+VMs > Feature Branch: unknown -- 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-812) Document user provided hostname to be specified in vCenter instead of CloudStack generated name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers reopened CLOUDSTACK-812: -- This documentation is pending ip clearance. Please do not commit the review in question. > Document user provided hostname to be specified in vCenter instead of > CloudStack generated name > --- > > Key: CLOUDSTACK-812 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-812 > 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 user provided hostname to be specified in vCenter instead of > CloudStack generated name -- 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-832) Document L4-L7 network services in the shared network in the advanced zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551146#comment-13551146 ] Chip Childers commented on CLOUDSTACK-832: -- The feature in question is pending IP ownership issue resolution. The documentation is probably in the same state, given that it was already developed outside of the community. Please do not commit this documentation until the IP questions are resolved. > Document L4-L7 network services in the shared network in the advanced zone > -- > > Key: CLOUDSTACK-832 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-832 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Chip Childers > Fix For: 4.1.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CLOUDSTACK-312) enable L4-L7 network services in the shared network in the advanced zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers reopened CLOUDSTACK-312: -- Reopening issue, since the commits in question have potential IP ownership questions. Those need to be resolved before this feature is resolved, and it may require a revert of the noted commits in the interm. This needs to be discussed on the dev list. > enable L4-L7 network services in the shared network in the advanced zone > > > Key: CLOUDSTACK-312 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-312 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Murali Reddy >Assignee: Murali Reddy > Fix For: 4.1.0 > > > CloudStack today does not provide network services like firewall, load > balancing, NAT in the shared networks created in the advanced zone. This > feature will enable network services to be available in the shared network as > well. > Release Planning: > Dev List Discussion: http://markmail.org/message/m522lj7ud7heanlb > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/L4-L7+network+services+in+shared+network > Feature Branch: master -- 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-774) Supporting kickstart in CloudStack baremetal
[ https://issues.apache.org/jira/browse/CLOUDSTACK-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551136#comment-13551136 ] Chip Childers commented on CLOUDSTACK-774: -- This feature needs to go through the IP clearance process before being committed. Also, can you provide a link to the dev list discussion to help us know where we stand on community consensus for this feature? > Supporting kickstart in CloudStack baremetal > > > Key: CLOUDSTACK-774 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-774 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Baremetal >Affects Versions: 4.1.0 >Reporter: frank zhang >Assignee: frank zhang > Fix For: 4.1.0 > > > Supporting kickstart install for RedHat like Linux in CloudStack Baremetal > provisioning -- 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-805) Document Isolation based on Security Groups in Advanced Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551135#comment-13551135 ] Chip Childers commented on CLOUDSTACK-805: -- Please do not commit the documentation for this feature yet, due to IP ownership questions. The documentation may also need to come through IP clearance. If you do submit a review with this material (or already have), that's perfectly OK. It would actually make the IP clearance process easier if it did come in as a review. Please note the review URL in this ticket if you decide to do that. > Document Isolation based on Security Groups in Advanced Zone > > > Key: CLOUDSTACK-805 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-805 > 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 > > > Documentation on Isolation based on Security Groups in Advanced Zone -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-737) Security Groups Isolation in Advanced Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551133#comment-13551133 ] Chip Childers commented on CLOUDSTACK-737: -- As of right now, this feature is blocked due to IP ownership questions. Please do not commit the code until this has been resolved. Additionally, it would be best if the discussion started in November (http://markmail.org/message/cle3d64ci6pobs2i) was brought to a consensus. > Security Groups Isolation in Advanced Zone > -- > > Key: CLOUDSTACK-737 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-737 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah >Assignee: Anthony Xu > Fix For: 4.1.0 > > > Requirements described at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Security+Groups+Isolation+in+Advanced+Zone > FS described at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Isolation+based+on+Security+Groups+in+Advance+zone > Dev list discussion: http://markmail.org/message/cle3d64ci6pobs2i > Feature branch: unknown -- 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-737) Security Groups Isolation in Advanced Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-737: - Description: Requirements described at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Security+Groups+Isolation+in+Advanced+Zone FS described at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Isolation+based+on+Security+Groups+in+Advance+zone Dev list discussion: http://markmail.org/message/cle3d64ci6pobs2i Feature branch: unknown was: Requirements described at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Security+Groups+Isolation+in+Advanced+Zone FS described at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Isolation+based+on+Security+Groups+in+Advance+zone > Security Groups Isolation in Advanced Zone > -- > > Key: CLOUDSTACK-737 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-737 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah >Assignee: Anthony Xu > Fix For: 4.1.0 > > > Requirements described at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Security+Groups+Isolation+in+Advanced+Zone > FS described at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Isolation+based+on+Security+Groups+in+Advance+zone > Dev list discussion: http://markmail.org/message/cle3d64ci6pobs2i > Feature branch: unknown -- 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-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 ] Chip Childers reopened CLOUDSTACK-800: -- As of right now, the submitted documentation is potentially of an uncertain IP clearance status. Reopening until that issue is resolved. The commit may need to be reverted, but we'll work out that process on the dev list. > 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-306) Support SRX & F5 inline mode
[ https://issues.apache.org/jira/browse/CLOUDSTACK-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers reopened CLOUDSTACK-306: -- Reopening due to uncertain IP clearance status. The commits may need to be reverted, but we'll work out that process on the dev list. > Support SRX & F5 inline mode > - > > Key: CLOUDSTACK-306 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-306 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Sheng Yang >Assignee: Sheng Yang > Fix For: 4.1.0 > > > See: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Network+inline+mode+functional+spec > Currently we would only deal with SRX & F5 combination. > Release Planning: > Dev List Discussion: http://markmail.org/message/jnpl5b7b6cqqmrui > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Network+inline+mode+functional+spec > Feature Branch: master -- 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
