[
https://issues.apache.org/jira/browse/CLOUDSTACK-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599426#comment-13599426
]
ilya musayev commented on CLOUDSTACK-657:
-----------------------------------------
Sateesh,
Attempted to test the DVS on latest build today.
I've only modified the Guest and Public "Network Labes" and pointed them to my
DVS - PlatOpsCluster_dvSwitch1.
I've also over-rode the settings when adding the cluster and pointed the CS to
use the PortGroups withing DVS.
At the moment i cannot get CS to work with DVS.
Here is the error that i see...
2013-03-11 18:26:11,834 INFO [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Prepare network on vmwaresvs
P[null:untagged] with name prefix: cloud.private
2013-03-11 18:26:11,835 WARN [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Unrecognized broadcast type in
VmwareResource, type: LinkLocal. Use vlan info from labeling: untagged
2013-03-11 18:26:11,835 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Detected vswitch name as
undefined. Defaulting to vSwitch0
2013-03-11 18:26:12,084 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Network
cloud.private.untagged.0.1-vSwitch0 is ready on vSwitch vSwitch0
2013-03-11 18:26:12,085 INFO [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Preparing NIC device on network
cloud.private.untagged.0.1-vSwitch0
2013-03-11 18:26:12,088 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Prepare NIC at new device
{"operation":"ADD","device":{"addressType":"Manual","macAddress":"02:00:4c:45:00:02","key":-3,"backing":{"network":{"value":"network-1226","type":"Network"},"deviceName":"cloud.private.untagged.0.1-vSwitch0"},"connectable":{"startConnected":true,"allowGuestControl":true,"connected":true},"unitNumber":2}}
2013-03-11 18:26:12,089 INFO [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Prepare NIC device based on
NicTO:
{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"uuid":"9a34ccb5-66fa-4d7a-97d7-2a2099a688d7","ip":"172.25.219.1","netmask":"255.255.254.0","gateway":"172.25.218.1","mac":"06:09:1a:00:00:01","broadcastType":"Native","type":"Management","isSecurityGroupEnabled":false}
2013-03-11 18:26:12,105 INFO [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Prepare network on vmwaresvs
P[null:untagged] with name prefix: cloud.private
2013-03-11 18:26:12,106 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Detected vswitch name as
undefined. Defaulting to vSwitch0
2013-03-11 18:26:12,398 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Network
cloud.private.untagged.0.1-vSwitch0 is ready on vSwitch vSwitch0
2013-03-11 18:26:12,399 INFO [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Preparing NIC device on network
cloud.private.untagged.0.1-vSwitch0
2013-03-11 18:26:12,401 DEBUG [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Prepare NIC at new device
{"operation":"ADD","device":{"addressType":"Manual","macAddress":"06:09:1a:00:00:01","key":-4,"backing":{"network":{"value":"network-1226","type":"Network"},"deviceName":"cloud.private.untagged.0.1-vSwitch0"},"connectable":{"startConnected":true,"allowGuestControl":true,"connected":true},"unitNumber":3}}
2013-03-11 18:26:12,403 INFO [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Prepare NIC device based on
NicTO:
{"deviceId":2,"networkRateMbps":-1,"defaultNic":true,"uuid":"f2e441d7-60de-463e-a60b-5fc874da8c55","ip":"172.25.219.20","netmask":"255.255.254.0","gateway":"172.25.218.1","mac":"06:b8:f4:00:00:14","dns1":"172.27.254.11","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://untagged","isolationUri":"vlan://untagged","isSecurityGroupEnabled":false,"name":"PlatOpsCluster_dvSwitch1"}
2013-03-11 18:26:12,422 INFO [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) Prepare network on vmwaredvs
P[PlatOpsCluster_dvSwitch1:untagged] with name prefix: cloud.public
2013-03-11 18:26:12,500 WARN [vmware.resource.VmwareResource]
(DirectAgent-40:vmh03t-ops-08.portal.webmd.com) StartCommand failed due to
Exception: java.lang.NoClassDefFoundError
Message: Could not initialize class
com.sun.xml.internal.ws.fault.SOAPFaultBuilder
java.lang.NoClassDefFoundError: Could not initialize class
com.sun.xml.internal.ws.fault.SOAPFaultBuilder
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:107)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:129)
at $Proxy449.retrieveProperties(Unknown Source)
at
com.cloud.hypervisor.vmware.util.VmwareClient.getDecendentMoRef(VmwareClient.java:544)
at
com.cloud.hypervisor.vmware.mo.DatacenterMO.getDvSwitchMor(DatacenterMO.java:488)
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:442)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2518)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2289)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:432)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
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:722)
2013-03-11 18:26:12,510 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-40:null) Seq 1-1012334612: Cancelling because one of the answers
is false and it is stop on error.
I'm running OpenJDK 1.7 and i do have rt.jar present.
I can also post a video of the whole process, any help is appreciated.
Thanks
ilya
> 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
