Use correct object in system.js that fixes the issue of management traffic
details not getting loaded as it fails on type error.
Fixes regression introduced in 95b6a5eeda
Support for local data disk. Currently enable/disable config is at zone level, in subsequent checkins it can be made more granular.
Following changes are made:
- Create disk offering API now takes an extra parameter to denote storage type (local or shared). This is similar to storage type in service offering.
- Create/delete of data volume on local storage
- Attach/detach for local data volumes. Re-attach is allowed as long as vm host and data volume storage pool host is same.
- Migration of VM instance is not supported if it uses local root or data volumes.
- Migrate is not supported for local volumes.
- Zone level config to enable/disable local storage usage for service and disk offerings.
- Local storage gets discovered when a host is added/reconnected if zone level config is enabled. When disabled existing local storages are not removed but any new local storage is not added.
- Deploy VM command validates service and disk offerings based on local storage config.
- Upgrade uses the global config 'use.local.storage' to set the zone level config for local storage.
(cherry picked from commit 62710aed37606168012a0ed255a876c8e7954010)
Adds a 'type' column to virtual router list views, which is labeled
either 'VPC,' 'Project,' or 'System' [default router].
--This also fixes an issue where project routers were never listed
This patch adds RBD (RADOS Block Device) support for primary storage in combination with KVM.
To get this patch working you need:
- libvirt-java 0.4.8
- libvirt with RBD storage pool support (>0.9.13)
- Qemu with RBD support (>0.14)
The primary storage does not support all the functions of CloudStack yet, for example snapshotting is disabled
due to the fact that backupping up a RBD snapshot is not possible in the way CloudStack wants to do it.
Creating templates from RBD volumes goes well, creating a VM from a template however is still a hit-and-miss.
NFS primary storage is also still required, you are not able to run your System VM's from RBD, they will need
to run on NFS.
Other then these points you can run instances with RBD backed disks.
-Don't pass subdomainaccess param when scope=project
-Fix guest network detail view by passing projectid=-1, due to project
details not returning response for project-level guest networks
-When in add cluster screen, show the add vSwitch fields when
hypervisor == VMware and 'vmware.use.nexus.vswitch' configuration
flag is enabled.
-Remove 'add Nexus vSwitch' checkbox, as the vSwitch fields will
always be shown for VMware if the above config flag is set.
Implement ability to add and modify Nexus vSwitches at the cluster
level:
-Add new fields to add cluster form, to allow addition of a vSwitch
-Add new tab to VMware clusters to list cluster's vSwitch
-Add details panel to vSwitch allowing enable, disable, and removal of
vSwitch from cluster
Edison Su
Rohit Yadav
Jessica Wang
Brian Federle
Koushik Das
Mice Xia
Pranav Saxena
Alena Prokharchyk
Edison Su
Mice Xia
Wido den Hollander
olgasmola
bfederle
David Nalley
Devdeep Singh
Sanjay Tripathi