Page History

...

Architecture and Design description

...

• CloudStack assumes dvSwitch is already created in customer's datacenter.

...

• CloudStack's doesn't

...

• deal with dynamic migration of virtual adapters

...

• of existing VMs across differnt types of virtual switches in scenarios in which co-existance of multiple types of virtual switches

...

• (Cisco's Nexus 1000v or VMware standard vSwitch and dvSwitch

...

• ) is possible. Instead this is left to administrator

...

• to decide.

• Highlight architectural patterns being used (queues, async/sync, state machines, etc) - N/A

...

• Talk about main algorithms

...

• used
• * Isolated network configuration using VLAN over dvSwitch. CloudStack manages dvPortGroup configured with a designated VLAN ID.
• * The scenarios to be covered are,

...

• * Adding host/compute resource to podcluster

...

• . Create necessary cloudstack managed virtual networks on designated dvSwitch.
• * Livemigration
• * All VM life cycle operations which might need instantiation of guest network etc.

...

• * Network operations like

...

• network creation, network destroy etc.

...

• * Port binding would be static binding.

...

• * Create dvPortGroup with open dvPorts

...

• Explain what components are being changed and what the dependent components are

...

• VmwareResource and VmwareManager (server)

...

• Regarding database: talk about tables being added/modified - N/A

...

• Performance implications: what are the improvements or risks introduced to capacity, response time, resources usage and other relevant KPIs•In vSphere 5.0, we will use "AutoExpand" support to configure dvPorts per dvPortGroup. This ensures that we don't pre-allocate unnecessary dvPorts so that they exhaust quicker.

...

• If possible, publish signatures of all methods classes and interfaces implement, and the explain the object information of different classes

...

• *core package (VmwareManager, VmwareResource)

...

• *server package

...

• *vmware-base package mo and util packages

...

• highlight architectural patterns being used (queues, async/sync, state machines, etc)
• talk about main algorithms used
• explain what components are being changed and what the dependent components are
• regarding database: talk about tables being added/modified
• performance implications: what are the improvements or risks introduced to capacity, response time, resources usage and other relevant KPIs
• preferably show class diagrams, sequence diagrams and state diagrams
• if possible, publish signatures of all methods classes and interfaces implement, and the explain the object information of different classes

Web Services APIs

Changes to existing web services APIs - AddClusterCmd
Adding an optional parameter named 'virtulSwitchType' which can have values 'vmwaresvs' or 'vmwaredvs' or 'nexusdvs'.
New APIs introduced - N/A

...