[jira] [Assigned] (CLOUDSTACK-2801) [nTier Apps] Documentation for NAT on private GW-VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair reassigned CLOUDSTACK-2801: Assignee: Radhika Nair > [nTier Apps] Documentation for NAT on private GW-VPC > > > Key: CLOUDSTACK-2801 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2801 > 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.2.0 > > > CloudStack-1828 -- 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-2803) Policy (DNAT,PF,ACL) containers from Cisco VNMC are not removed when Public IP is released from Cloudstack
Sailaja Mada created CLOUDSTACK-2803: Summary: Policy (DNAT,PF,ACL) containers from Cisco VNMC are not removed when Public IP is released from Cloudstack Key: CLOUDSTACK-2803 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2803 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller, Network Devices Affects Versions: 4.2.0 Reporter: Sailaja Mada Priority: Minor Steps: 1. Configure Advanced Networking zone with VMWARE Nexus enabled cluster 2. Add Cisco VNMC,ASA firewall devices 3. Create Network offering with Cisco VNMC provider as (Source NAT, PF,Firewall,Static NAT ) 4. Deploy Instance using this network 5. Acquire new public IP and configure Static NAT Rule . 6. Release IP Observation: 1. Rules are removed from Cisco VNMC 2. But Policy (DNAT,PF,ACL) containers from Cisco VNMC are not removed when Public IP is released from Cloudstack. (Attached the snap) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1301) VM Disk I/O Throttling
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672854#comment-13672854 ] ASF subversion and git services commented on CLOUDSTACK-1301: - Commit f714d2603914bbcce5dee307bf845a1e6b83e8f9 in branch refs/heads/master from [~weizhou] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f714d26 ] Revert "CLOUDSTACK-1301: Add VM Disk I/O Throttling" This reverts commit 6dad8adf8fc22417f0242126b8f52ee081f74f49. > VM Disk I/O Throttling > -- > > Key: CLOUDSTACK-1301 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1301 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.0.0, 4.1.0 >Reporter: Wei Zhou >Assignee: Wei Zhou > Fix For: 4.2.0 > > > VM Disk I/O Throttling, to set the maximum disk I/O rate of VMs. > Virtual machines are running on the same storage device (local storage or > share strage). Because of the rate limitation of device (such as iops), if > one VM has large disk operation, it may affect the disk performance of other > VMs running on the same storage device. > It is neccesary to set the maximum rate and limit the disk I/O of VMs. > More details: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+IO+Throttling -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2802) Update the Current VPC Documentation for nTier Apps Related Changes
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair updated CLOUDSTACK-2802: - Description: Update the following files: vpc.xml add-vpc.xml add-tier.xml configure-acl.xml add-gateway-vpc.xml add-vm-to-tier.xml acquire-new-ip-for-vpc.xml release-ip-for-vpc.xml enable-disable-static-nat-vpc.xml add-loadbalancer-rule-vpc.xml add-portforward-rule-vpc.xml remove-tier.xml remove-vpc.xml was: Change the following files: vpc.xml add-vpc.xml add-tier.xml configure-acl.xml add-gateway-vpc.xml add-vm-to-tier.xml acquire-new-ip-for-vpc.xml release-ip-for-vpc.xml enable-disable-static-nat-vpc.xml add-loadbalancer-rule-vpc.xml add-portforward-rule-vpc.xml remove-tier.xml remove-vpc.xml > Update the Current VPC Documentation for nTier Apps Related Changes > --- > > Key: CLOUDSTACK-2802 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2802 > 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.2.0 > > > Update the following files: > vpc.xml > add-vpc.xml > add-tier.xml > configure-acl.xml > add-gateway-vpc.xml > add-vm-to-tier.xml > acquire-new-ip-for-vpc.xml > release-ip-for-vpc.xml > enable-disable-static-nat-vpc.xml > add-loadbalancer-rule-vpc.xml > add-portforward-rule-vpc.xml > remove-tier.xml > remove-vpc.xml -- 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-2802) Update the Current VPC Documentation for nTier Apps Related Changes
Radhika Nair created CLOUDSTACK-2802: Summary: Update the Current VPC Documentation for nTier Apps Related Changes Key: CLOUDSTACK-2802 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2802 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.2.0 Change the following files: vpc.xml add-vpc.xml add-tier.xml configure-acl.xml add-gateway-vpc.xml add-vm-to-tier.xml acquire-new-ip-for-vpc.xml release-ip-for-vpc.xml enable-disable-static-nat-vpc.xml add-loadbalancer-rule-vpc.xml add-portforward-rule-vpc.xml remove-tier.xml remove-vpc.xml -- 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-2699) [VPC][Private gateway]Unable to create static nat rule for a private gateway after VPC VR is rebooted.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayapal Reddy reassigned CLOUDSTACK-2699:
-
Assignee: Jayapal Reddy
> [VPC][Private gateway]Unable to create static nat rule for a private gateway
> after VPC VR is rebooted.
> --
>
> Key: CLOUDSTACK-2699
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2699
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
>Affects Versions: 4.2.0
>Reporter: manasaveloori
>Assignee: Jayapal Reddy
>Priority: Critical
> Fix For: 4.2.0
>
>
> 1.Have a CS with advanced zone.
> 2.Create a VPC .
> 3.Add a private gateway to the vpc.
> 4.Create a static nat.Verify the static nat rule in VR.( ip route show
> table static_route)
> 5.Now reboot the VPC VR fron CS.
> 6.Try to create a static nat rule for a private gateway now.
> Observations:
> 1.The configured static nat rules are visible in UI but not getting
> configured back in VR after reboot.( ip route show table static_route is
> empty)
> 2.Aslo after the VR is rebooted ,unable to add any more static
> routes.giving following exception:
> 2013-05-27 23:05:53,489 DEBUG [agent.transport.Request]
> (DirectAgent-404:null) Seq 3-1205667013: Processing: { Ans: , MgmtId:
> 6805241462820, via: 3, Ver: v1, Flags: 0,
> [{"routing.SetStaticRouteAnswer":{"results":["Failed","Failed","Failed","Failed","Failed"],"result":false,"wait":0}}]
> }
> 2013-05-27 23:05:53,489 DEBUG [agent.transport.Request]
> (Job-Executor-77:job-63) Seq 3-1205667013: Received: { Ans: , MgmtId:
> 6805241462820, via: 3, Ver: v1, Flags: 0, { SetStaticRouteAnswer } }
> 2013-05-27 23:05:53,504 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-77:job-63) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vpc.CreateStaticRouteCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to apply static
> routes in vpc [VPC [1-vpc1]
>at
> com.cloud.network.element.VpcVirtualRouterElement.applyStaticRoutes(VpcVirtualRouterElement.java:441)
>at
> com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1638)
>at
> com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1601)
>at
> com.cloud.network.vpc.VpcManagerImpl.applyStaticRoutes(VpcManagerImpl.java:1586)
>at
> com.cloud.network.vpc.VpcManagerImpl.revokeStaticRoute(VpcManagerImpl.java:1663)
>at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>at
> org.apache.cloudstack.api.command.user.vpc.CreateStaticRouteCmd.execute(CreateStaticRouteCmd.java:108)
>at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
>at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
>at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>at java.lang.Thread.run(Thread.java:679)
> 2013-05-27 23:05:53,506 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-77:job-63) Complete async job-63, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: Failed to apply static routes in vpc
> [VPC [1-vpc1]
> 2013-05-27 23:05:53,533 DEBUG [cloud.async.SyncQueueManagerImpl]
> (Job-Executor-77:job-63) Sync queue (1) is currently empty
> 2013-05-27 23:05:53,826 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-112:null) Ping from 3
> 2013-05-27 23:05:54,360 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null)
> ===START=== 10.252.241.232 -- GET
> command=queryAsyncJobResult&jobId=43385df3-eb7f-44e3-a092-
--
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-2765) Dashboard is showing invalid value for storage "Allocated 0.00KB/0.00KB"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-2765: -- Assignee: Nitin Mehta > Dashboard is showing invalid value for storage "Allocated 0.00KB/0.00KB" > -- > > Key: CLOUDSTACK-2765 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2765 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Storage Controller >Affects Versions: 4.2.0 >Reporter: prashant kumar mishra >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.0 > > Attachments: Dashboard.png, MSlogs.rar > > > please check screenshot for more detail > Database > -- > mysql> select *from op_host_capacity ; > ++-++++---+---++---++-+-+ > | id | host_id | data_center_id | pod_id | cluster_id | used_capacity | > reserved_capacity | total_capacity | capacity_type | capacity_state | > update_time | created | > ++-++++---+---++---++-+-+ > | 1 | 1 | 1 | 1 | 1 |2550136832 | > 0 |16190157312 | 0 | Enabled| 2013-05-30 > 12:34:38 | 2013-05-30 12:19:55 | > | 2 | 1 | 1 | 1 | 1 | 2500 | > 0 | 9576 | 1 | Enabled| 2013-05-30 > 12:34:38 | 2013-05-30 12:19:55 | > | 3 |NULL | 1 | NULL | NULL | 3 | > 0 | 28 | 4 | Enabled| 2013-05-30 > 12:34:55 | 2013-05-30 12:19:55 | > | 4 |NULL | 1 | NULL | NULL | 0 | > 0 | 0 | 8 | Enabled| 2013-05-30 > 12:19:55 | 2013-05-30 12:19:55 | > | 5 |NULL | 1 | NULL | NULL | 1 | > 0 | 10 | 7 | Enabled| 2013-05-30 > 12:34:55 | 2013-05-30 12:19:55 | > | 6 |NULL | 1 | 1 | NULL | 3 | > 0 | 10 | 5 | Enabled| 2013-05-30 > 12:24:55 | 2013-05-30 12:19:55 | > | 7 | 3 | 1 | 1 | 1 | 36995040256 | > 0 |58210910208 | 3 | Enabled| 2013-05-30 > 17:26:41 | 2013-05-30 12:22:39 | > ++-++++---+---++---++-+-+ > Storage detail > - > [root@RHEL62 ~]# df -h > FilesystemSize Used Avail Use% Mounted on > /dev/mapper/vg_rhel62-lv_root >28G 9.9G 16G 39% / > tmpfs 499M 0 499M 0% /dev/shm > /dev/sda1 485M 32M 428M 7% /boot > /tmp/iso/rhel-server-6.2-x86_64-dvd.iso > 3.4G 3.4G 0 100% /media -- 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-2781) [VPC Network ACL] listNetworkACLLists is listing the all ACL lists irrespective of VPC id.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reassigned CLOUDSTACK-2781: -- Assignee: Kishan Kavala > [VPC Network ACL] listNetworkACLLists is listing the all ACL lists > irrespective of VPC id. > -- > > Key: CLOUDSTACK-2781 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2781 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Affects Versions: 4.2.0 >Reporter: manasaveloori >Assignee: Kishan Kavala >Priority: Critical > Fix For: 4.2.0 > > > Steps: > 1.Have a CS with advanced zone. > 2.Create a VPC say vpc1 and create a network ACL list eg TestACLList. > 3.Now create another VPC say vpc2. > Observation: > 1.For vpc2 ,the VPC VR shows the ACL lists configured for vpc1 also apart > from default lists. > 2.Verified the issue using API also. For different vpc ids the > listNetworkACLLists is providing the same response. > 3.The API is not considering the VPC id(displaying same response for > invalid vpc ids also). > http://10.147.38.154:8096/client/api?command=listNetworkACLLists&vpc_id=74eb6055-6f31-403b-818b-3b11079d84fb > vpc1 > http://10.147.38.154:8096/client/api?command=listNetworkACLLists&vpc_id=c124d506-babd-4d5f-868f-0605074c0809 > -vpc2 > http://10.147.38.154:8096/client/api?command=listNetworkACLLists > All the above APIs give the same response. -- 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-2667) ScaleVM: marvin test_scalevm test fails to scale the vm to new offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta reassigned CLOUDSTACK-2667: --- Assignee: Nitin Mehta > ScaleVM: marvin test_scalevm test fails to scale the vm to new offering > --- > > Key: CLOUDSTACK-2667 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2667 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Test >Affects Versions: 4.2.0 >Reporter: Prasanna Santhanam >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.2.0 > > > http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-smoke-matrix/suite=test_scale_vm/lastCompletedBuild/testReport/integration.smoke.test_scale_vm/TestScaleVm/test_01_scale_vm/ > The above test has been consistently failing for the past 69 builds. Please > fix it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-2796) [Automation] Failed to add primary storage with error "Missing parameter hypervisor."
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi resolved CLOUDSTACK-2796. -- Resolution: Fixed > [Automation] Failed to add primary storage with error "Missing parameter > hypervisor." > - > > Key: CLOUDSTACK-2796 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2796 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 > Environment: Master branch, commit : > 6dad8adf8fc22417f0242126b8f52ee081f74f49 >Reporter: Rayees Namathponnan >Assignee: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.2.0 > > > Create new build from master branch commit > 6dad8adf8fc22417f0242126b8f52ee081f74f49 > Create advanced zone, with primary strorage scope = "cluster" > Result : > Failed to primary storage with below error > "Missing parameter hypervisor. Hypervisor type is required to create zone > wide primary 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] [Assigned] (CLOUDSTACK-2371) NTier: Deletion of Private Gateway failed due to Null Pointer Exception
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek reassigned CLOUDSTACK-2371:
--
Assignee: (was: Abhinandan Prateek)
> NTier: Deletion of Private Gateway failed due to Null Pointer Exception
> ---
>
> Key: CLOUDSTACK-2371
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2371
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.2.0
>Reporter: Chandan Purushothama
>Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.zip
>
>
> ===
> Observations:
> ===
> 2013-05-07 18:31:57,693 DEBUG [cloud.api.ApiServlet] (catalina-exec-8:null)
> ===END=== 10.216.132.104 -- GET
> command=deletePrivateGateway&id=59ec16d4-a076-4692-9abe-b986cf81cda4&response=json&sessionkey=xMoElKyZsirl3kELteeIURhHbIU%3D&_=1367976753038
> 2013-05-07 18:31:57,695 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-50:job-41) Executing
> org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd for job-41
> 2013-05-07 18:31:57,700 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-50:job-41) Sync job-41 execution on object vpc.1
> 2013-05-07 18:31:57,706 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-50:job-41) job
> org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd for
> job-41 was queued, processing the queue.
> 2013-05-07 18:31:57,711 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-50:job-41) Executing sync queue item: SyncQueueItemVO {id:21,
> queueId: 1, contentType: AsyncJob, contentId: 41, lastProcessMsid:
> 7508777239729, lastprocessNumber: 21, lastProcessTime: Tue May 07 18:31:57
> PDT 2013, created: Tue May 07 18:31:57 PDT 2013}
> 2013-05-07 18:31:57,712 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-50:job-41) Schedule queued job-41
> 2013-05-07 18:31:57,718 DEBUG [cloud.async.SyncQueueManagerImpl]
> (Job-Executor-50:job-41) There is a pending process in sync queue(id: 1)
> 2013-05-07 18:31:57,719 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-51:job-41) Executing
> org.apache.cloudstack.api.command.admin.vpc.DeletePrivateGatewayCmd for job-41
> 2013-05-07 18:31:57,727 DEBUG [network.vpc.VpcManagerImpl]
> (Job-Executor-51:job-41) Marked gateway VpcGateway[10|10.223.60.32|1] with
> state Deleting
> 2013-05-07 18:31:57,736 DEBUG
> [network.router.VpcVirtualNetworkApplianceManagerImpl]
> (Job-Executor-51:job-41) Releasing private ip for gateway
> com.cloud.network.vpc.PrivateGatewayProfile@eed2c67 from
> VM[DomainRouter|r-5-NATONPRVGW]
> 2013-05-07 18:31:57,743 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-51:job-41) Service SecurityGroup is not supported in the
> network id=209
> 2013-05-07 18:31:57,753 DEBUG [agent.transport.Request]
> (Job-Executor-51:job-41) Seq 1-275054878: Sending { Cmd , MgmtId:
> 7508777239729, via: 1, Ver: v1, Flags: 100011,
> [{"routing.IpAssocVpcCommand":{"ipAddresses":[{"accountId":1,"publicIp":"10.223.60.33","sourceNat":true,"add":false,"oneToOneNat":false,"firstIP":false,"vlanId":"600","vlanGateway":"10.223.60.1","vlanNetmask":"255.255.255.192","vifMacAddress":"06:11:c0:00:00:2b","trafficType":"Guest"}],"accessDetails":{"router.guest.ip":"10.223.60.33","zone.network.type":"Advanced","router.ip":"169.254.3.235","router.name":"r-5-NATONPRVGW"},"wait":0}}]
> }
> 2013-05-07 18:31:58,544 DEBUG [agent.transport.Request]
> (AgentManager-Handler-5:null) Seq 1-275054878: Processing: { Ans: , MgmtId:
> 7508777239729, via: 1, Ver: v1, Flags: 10,
> [{"routing.IpAssocAnswer":{"results":["10.223.60.33 -
> success"],"result":true,"wait":0}}] }
> 2013-05-07 18:31:58,544 DEBUG [agent.transport.Request]
> (Job-Executor-51:job-41) Seq 1-275054878: Received: { Ans: , MgmtId:
> 7508777239729, via: 1, Ver: v1, Flags: 10, { IpAssocAnswer } }
> 2013-05-07 18:31:58,544 DEBUG
> [network.router.VpcVirtualNetworkApplianceManagerImpl]
> (Job-Executor-51:job-41) Successfully applied ip association for ip
> com.cloud.network.vpc.PrivateIpAddress@32595f0d in vpc network
> Ntwk[209|Guest|5]
> 2013-05-07 18:31:58,544 DEBUG
> [network.router.VpcVirtualNetworkApplianceManagerImpl]
> (Job-Executor-51:job-41) Removing router VM[DomainRouter|r-5-NATONPRVGW] from
> private network Ntwk[209|Guest|5] as a part of delete private gateway
> 2013-05-07 18:31:58,557 DEBUG [cloud.network.NetworkModelImpl]
> (Job-Executor-51:job-41) Service SecurityGroup is not supported in the
> network id=209
> 2013-05-07 18:31:58,598 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-51:job-41) Unexpected exception while executing
> org.apa
[jira] [Created] (CLOUDSTACK-2801) [nTier Apps] Documentation for NAT on private GW-VPC
Radhika Nair created CLOUDSTACK-2801: Summary: [nTier Apps] Documentation for NAT on private GW-VPC Key: CLOUDSTACK-2801 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2801 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Fix For: 4.2.0 CloudStack-1828 -- 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-2432) AES NI module in the VR is installled but it does not seem to work with openssl
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek resolved CLOUDSTACK-2432. Resolution: Fixed > AES NI module in the VR is installled but it does not seem to work with > openssl > --- > > Key: CLOUDSTACK-2432 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2432 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Affects Versions: 4.2.0 >Reporter: Bharat Kumar >Assignee: Abhinandan Prateek >Priority: Blocker > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2432) AES NI module in the VR is installled but it does not seem to work with openssl
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672816#comment-13672816 ] Abhinandan Prateek commented on CLOUDSTACK-2432: lsmod shows that the aesni module is loaded by default on wheezy. > AES NI module in the VR is installled but it does not seem to work with > openssl > --- > > Key: CLOUDSTACK-2432 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2432 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Affects Versions: 4.2.0 >Reporter: Bharat Kumar >Assignee: Abhinandan Prateek >Priority: Blocker > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi resolved CLOUDSTACK-1963. -- Resolution: Fixed > New mapping model for CloudStack zone and Vmware datacenter > > > Key: CLOUDSTACK-1963 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi > Fix For: 4.2.0 > > > Functional specification document is here, > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter > Branch for this feature's code is refs/heads/vmware-datamodel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2796) [Automation] Failed to add primary storage with error "Missing parameter hypervisor."
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672815#comment-13672815 ] ASF subversion and git services commented on CLOUDSTACK-2796: - Commit b4969c4af5264879ccbec01b65b6c94886fc79d4 in branch refs/heads/master from Sateesh Chodapuneedi [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b4969c4 ] CLOUDSTACK-2796 Hypervisor type validation would be applicable only for zone wide primary storage pool. > [Automation] Failed to add primary storage with error "Missing parameter > hypervisor." > - > > Key: CLOUDSTACK-2796 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2796 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 > Environment: Master branch, commit : > 6dad8adf8fc22417f0242126b8f52ee081f74f49 >Reporter: Rayees Namathponnan >Assignee: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.2.0 > > > Create new build from master branch commit > 6dad8adf8fc22417f0242126b8f52ee081f74f49 > Create advanced zone, with primary strorage scope = "cluster" > Result : > Failed to primary storage with below error > "Missing parameter hypervisor. Hypervisor type is required to create zone > wide primary 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-2701) Enable storage migration for VMware resources
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672814#comment-13672814 ] ASF subversion and git services commented on CLOUDSTACK-2701: - Commit 984b59d1eecf677ad2d824d37175976f9b6e2eec in branch refs/heads/master from Sateesh Chodapuneedi [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=984b59d ] CLOUDSTACK-2701 Moved bean VmwareStorageMotionStrategy to nonossComponentContext.xml.in > Enable storage migration for VMware resources > - > > Key: CLOUDSTACK-2701 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2701 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi > Fix For: 4.2.0 > > > Storage vMotion allows VMs to be moved from one host to another, along with > storage across datastores in datacenter. It provides the option to live > migrate a VM’s disks along with the VM itself. > It is now possible to migrate a VM from one datastore to another, or even to > migrate a VM’s disks from one datastore to another with VM running on same > host, all while the VM is running. > This issue is to track the support of storage vMotion for VMware resources in > cloudstack. Till now ticket CLOUDSTACK-659 was using in all code commits done > to branch vmware-storage-motion. Just now created this ticket to deal with > specific areas in implementation that is well contained and limited to VMware > resource only. Commits related to VmwareStorageMotionStrategy class and it's > implementation along with commands MigrateWithStorageCommand and > MigrateVolumeCommand are done under CLOUDSTACK-659 ticket. > Release Planning: > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer > (section VMware resource) > Feature branch: vmware-storage-motion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-999) Plugin to provide Hyper-V 2012 support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672795#comment-13672795 ] Sudha Ponnaganti commented on CLOUDSTACK-999: - Hi Donal, Is phase 2 also planned for 4.2. Recently there were discussions so checking if that is going to be materialized for 4.2. thanks /sudha > 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-2800) QA: New mapping model for CloudStack zone and Vmware datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2800: - Summary: QA: New mapping model for CloudStack zone and Vmware datacenter (was: QA: New mapping ) > QA: New mapping model for CloudStack zone and Vmware datacenter > > > Key: CLOUDSTACK-2800 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2800 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Affects Versions: 4.2.0 >Reporter: Sudha Ponnaganti > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2800) QA: New mapping
Sudha Ponnaganti created CLOUDSTACK-2800: Summary: QA: New mapping Key: CLOUDSTACK-2800 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2800 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-1963) New mapping model for CloudStack zone and Vmware datacenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672789#comment-13672789 ] Sudha Ponnaganti commented on CLOUDSTACK-1963: -- Sateesh, If UI is tracked seprately, can you move this to resolved state?? > New mapping model for CloudStack zone and Vmware datacenter > > > Key: CLOUDSTACK-1963 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1963 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi > Fix For: 4.2.0 > > > Functional specification document is here, > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter > Branch for this feature's code is refs/heads/vmware-datamodel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-716) Make netscaler plugin part of apache release
[ https://issues.apache.org/jira/browse/CLOUDSTACK-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672788#comment-13672788 ] Sudha Ponnaganti commented on CLOUDSTACK-716: - Vijay, I think it is too late to add this. Are you still considering to add this?? I am looking at validation aspect for this feature so just checking. If you are not planning it would be better to move it to "future" release thanks /sudha > Make netscaler plugin part of apache release > > > Key: CLOUDSTACK-716 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-716 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Affects Versions: 4.0.0 >Reporter: Alex Huang >Assignee: Vijay Venkatachalam > Fix For: 4.2.0 > > > Can we get a license from citrix to make the netscaler plugin part of the > apache release? > I assigned to Chiradeep to get his input on possibility. -- 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-742) Integrate Cisco ASA 1000v into CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-742. Resolution: Fixed > Integrate Cisco ASA 1000v into CloudStack > - > > Key: CLOUDSTACK-742 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-742 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah >Assignee: Koushik Das > Fix For: 4.2.0 > > > Requirements described at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Integrate+Cisco+ASA+1000v+as+a+FW+for+CloudStack > Requirements discussion email thread link: -- 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-742) Integrate Cisco ASA 1000v into CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672765#comment-13672765 ] Sudha Ponnaganti commented on CLOUDSTACK-742: - Koushik, It is ok to move it to resolved status. Once sub tasks are done, I will move it to closed state thanks /sudha > Integrate Cisco ASA 1000v into CloudStack > - > > Key: CLOUDSTACK-742 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-742 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah >Assignee: Koushik Das > Fix For: 4.2.0 > > > Requirements described at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Integrate+Cisco+ASA+1000v+as+a+FW+for+CloudStack > Requirements discussion email thread link: -- 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-2799) Automation: Add automation for Create-Tag feature for VPN in Customer gateway
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2799: - Summary: Automation: Add automation for Create-Tag feature for VPN in Customer gateway (was: Automation: Add automation for Create-Tag feature for VPC gateway) > Automation: Add automation for Create-Tag feature for VPN in Customer gateway > - > > Key: CLOUDSTACK-2799 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2799 > Project: CloudStack > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Reporter: Sudha Ponnaganti > Fix For: 4.2.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2799) Automation: Add automation for Create-Tag feature for VPC gateway
Sudha Ponnaganti created CLOUDSTACK-2799: Summary: Automation: Add automation for Create-Tag feature for VPC gateway Key: CLOUDSTACK-2799 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2799 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti -- 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-2798) Automation: Add automation for changed behavior of refresh button for this implementation
Sudha Ponnaganti created CLOUDSTACK-2798: Summary: Automation: Add automation for changed behavior of refresh button for this implementation Key: CLOUDSTACK-2798 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2798 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2797) QA: Test Consistent use of refresh Button
Sudha Ponnaganti created CLOUDSTACK-2797: Summary: QA: Test Consistent use of refresh Button Key: CLOUDSTACK-2797 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2797 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Fix For: 4.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2796) [Automation] Failed to add primary storage with error "Missing parameter hypervisor."
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi updated CLOUDSTACK-2796: - Assignee: Sateesh Chodapuneedi > [Automation] Failed to add primary storage with error "Missing parameter > hypervisor." > - > > Key: CLOUDSTACK-2796 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2796 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 > Environment: Master branch, commit : > 6dad8adf8fc22417f0242126b8f52ee081f74f49 >Reporter: Rayees Namathponnan >Assignee: Sateesh Chodapuneedi >Priority: Blocker > Fix For: 4.2.0 > > > Create new build from master branch commit > 6dad8adf8fc22417f0242126b8f52ee081f74f49 > Create advanced zone, with primary strorage scope = "cluster" > Result : > Failed to primary storage with below error > "Missing parameter hypervisor. Hypervisor type is required to create zone > wide primary 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-733) BigSwitch network plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672548#comment-13672548 ] Sudha Ponnaganti commented on CLOUDSTACK-733: - Murali, Wanted to check status on this feature?? Also would like to request if anyone in community would be interested to pick it up for validation thanks /sudha > BigSwitch network plugin > > > Key: CLOUDSTACK-733 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-733 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Kanzhe Jiang >Assignee: Murali Reddy > Fix For: 4.2.0 > > Original Estimate: 360h > Remaining Estimate: 360h > > BVS is one of the SDN applications available for the BigSwitch network > controller. BVS application provides network virtualization, manages isolated > and virtual networks on top of the underlying physical and virtual switch > infrastructure. These virtual networks correspond directly to the groups of > VMs, servers, and other devices that need their own secure connectivity. The > virtual networks are programmed into the physical and/or virtual switches > without having to separately configure individual network devices. > The proposed CloudStack networking plugin will bring the OpenFlow-based > standard network virtualization technology to CloudStack. > There won't be any change to the existing CloudStack workflow. In a typical > deployment, all OpenFlow-enabled physical and virtual switches and other > network resources are configured to be managed by the BigSwitch > controller(s). When a guest network is created, the plugin will create a > corresponding virtual network in the BVS When a guest VM is launched, the VM > is automatically assigned to its configured guest network(s). The BVS > application will provide network isolation and connectivities among VMs. -- 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-739) Affinity / Anti-affinity Rules
[ https://issues.apache.org/jira/browse/CLOUDSTACK-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672546#comment-13672546 ] Sudha Ponnaganti commented on CLOUDSTACK-739: - Prachi, With GIT Check ins and based on limitations discussed in ML, can this story be closed. I would think the limitations can be opened as another ticket for future release. Ie. affinity part of the story need to be separated. thanks /sudha > Affinity / Anti-affinity Rules > -- > > Key: CLOUDSTACK-739 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-739 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Manan Shah >Assignee: Prachi Damle > Fix For: 4.2.0 > > > Requirements described at: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Affinity+-+Anti-affinity+rules > Requirements discussion email thread link: > FS link: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/FS+-+Affinity-Anti-affinity+groups -- 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=13672547#comment-13672547 ] Manan Shah commented on CLOUDSTACK-738: --- Thank you for your email. I will be out of office on May 31st. I will respond to your emails as soon as possible. Regards, -Manan > 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.2.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] [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=13672543#comment-13672543 ] Sudha Ponnaganti commented on CLOUDSTACK-738: - Sonny, This code has been available in Master. Wanted to check if you can post GIT ref here and change status. As per test results, Manasa V has already tested this feature thanks /sudha > 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.2.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] [Commented] (CLOUDSTACK-625) 3rd Party Plugin
[ https://issues.apache.org/jira/browse/CLOUDSTACK-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672542#comment-13672542 ] Sudha Ponnaganti commented on CLOUDSTACK-625: - Sonny, This story has been checked in on 15th Feb. Can you assign proper status?? thanks /sudha > 3rd Party Plugin > > > Key: CLOUDSTACK-625 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-625 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.0.1 >Reporter: Sonny Chhen >Assignee: Sonny Chhen >Priority: Minor > Labels: ui > Fix For: 4.2.0 > > > This features will allow for developers to write their own plugins and > install them into CloudStack as well as utilizing the current ui in > maintaining a cohesive design/experience. > Release Planning: > Dev list discussion: http://markmail.org/message/45sbbzrz2wjnefve > Functional Spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugin > Feature branch: UI-Plugins -- 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-645) add/remove network on VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672539#comment-13672539 ] Sudha Ponnaganti commented on CLOUDSTACK-645: - Radhika, Checking if the supportability limitation has been documented or not. I will close this story and leave 2059 open so 4.1 stories can be closed thanks /sudha > add/remove network on VM > > > Key: CLOUDSTACK-645 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-645 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller >Reporter: Marcus Sorensen >Assignee: Marcus Sorensen > Fix For: 4.1.0 > > > We would like the ability to move VMs between networks and/or reconfigure a > VM's network, in order to accomodate hybrid/traditional server loads. We've > implemented 3 API calls and would like to submit these for the community to > edit/adjust/approve. The three calls are > 'addNicToVirtualMachine','removeNicFromVirtualMachine', and > 'updateDefaultNicForVirtualMachine'. One provides a VM Id and a network id, > default Nics cannot be removed. The names might need adjustment to better fit > the API, perhaps 'attachNetworkToVirtualMachine', etc. Looking for feedback, > advice, potential pitfalls... does a feature branch need to be created or > just a review? > Release Planning: > Dev list discussion: [jira] [Created] (CLOUDSTACK-645) add/remove network on > VM > Functional spec: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs > Feature branch: add_remove_nics -- 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-2059) Support remove network over VMware deployments with dvSwitch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672538#comment-13672538 ] Sudha Ponnaganti commented on CLOUDSTACK-2059: -- Sateesh/Marcus, I am closing 645 as that has been addressed and this would be fixed for 4.2 thanks /sudha > Support remove network over VMware deployments with dvSwitch > > > Key: CLOUDSTACK-2059 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2059 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Sateesh Chodapuneedi >Assignee: Sateesh Chodapuneedi >Priority: Critical > Fix For: 4.2.0 > > > Remove network from user VM is supported in VMware only for standard > vSwitches. This need to be supported for dvSwitches as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
