cloudstack/setup/db
prachi 923f562aa8 Bug 6873: disable/enable mode for clusters (and pods and zones and hosts)
- Added a new flag 'allocation_state' to zone,pod,cluster and host
- The possible values for this flag are 'Enabled' or 'Disabled'
- When a new zone,pod,cluster or host is added, allocation_state is 'Disabled' by default.
- For existing zone,pod,cluster or host, the state is 'Enabled'.
- All Add/Update/List  commands for each of zone,pod,cluster or host can now take a new parameter 'allocationstate'
- If 'allocation_state' is 'Disabled', Allocators skip that zone or pod or cluster or pod.
- For a root admin, ListZones lists all zones including the 'Disabled' zones. But for any other user, the 'Disabled' zones are not included in the response.
- For any usecase that creates/deploys/adds/registers a resource and takes in zone as parameter, now we check if the Zone is 'Disabled'. If yes then the operation cannot be performed by a user other than root-admin. Add volume, snapshot, templates are examples of this usecase.
- To enable the root admin to test a particular pod/cluster/host, deployVM command takes in 'host_id' parameter that can be passed in only by root admin.
If this parameter is passed in by the admin, allocators do not search for hosts and use that host only. StoragePools are searched in the cluster of that host.
If VM cannot be deployed to that host, allocators and deployVM fails without retrying
2011-03-23 22:15:35 -07:00
..
22beta4to22GA.sql added queries to handle unit MB to bytes change for volume usage 2011-02-22 17:12:22 +05:30
221to222.sql Fixed DB upgrade script - vm_type field can be NULL 2011-03-05 10:37:57 -08:00
221to222_usage.sql bug 8601: these are the 2 sql files for the cloud and cloud_usage db migration. I have tested some of the most common cases, as well as some uncommon cases (create a direct and virtual network in same zone). 2011-02-25 17:06:26 -08:00
221to222upgrade.sh checking to see if mysql is running 2011-02-28 13:43:38 -08:00
create-database.sql more file changes 2010-09-09 13:27:20 -07:00
create-index-fk.sql remove snapshot_policy_ref index 2011-03-08 18:03:16 -08:00
create-schema.sql Bug 6873: disable/enable mode for clusters (and pods and zones and hosts) 2011-03-23 22:15:35 -07:00
data-20to21.sql Source code committed 2010-08-11 09:13:29 -07:00
data-21to22.sql bug 8939: add management.network.cidr 2011-03-09 16:32:18 -05:00
data-22beta1to22beta2.sql move db migration to script 2010-12-03 11:24:25 -08:00
deploy-db-dev.sh - dos2unix deploy-db-dev.sh 2010-08-12 17:19:30 -07:00
index-20to21.sql Source code committed 2010-08-11 09:13:29 -07:00
index-21to22.sql add vpnusersdao into components.xml, schema migration, add another constraint 2010-11-03 14:02:13 -07:00
index-212to213.sql bug 5985: rename hotfix for bug to be consistent with other migration scripts, and include in fedora / ubuntu packaging 2010-08-26 19:18:37 -07:00
postprocess-20to21.sql Source code committed 2010-08-11 09:13:29 -07:00
schema-20to21.sql Source code committed 2010-08-11 09:13:29 -07:00
schema-21to22-cleanup.sql restarting domr is close to working 2011-03-21 17:56:00 -07:00
schema-21to22.sql Clean async Job 2011-03-23 16:06:52 -07:00
schema-22beta1to22beta2.sql bug 7144: return snapshotId with jobid 2010-12-02 19:23:34 -08:00
schema-22beta3to22beta4.sql DB upgrade script from 2.2beta3 to 2.2beta4 2011-01-18 20:08:44 +05:30
schema-221to222-cleanup.sql adding a migration step from 221 to 222 using alex's framework. this should only be used for alex's upgrade from 217 to 22, for 221 to 222 for 222 release, we still are providing the bash script for upgrade. 2011-03-01 16:00:14 -08:00
schema-221to222.sql bug 8601: merge from 2.2.2 to master 2011-03-04 16:31:58 -08:00
schema-222to224.sql bug 8533: all IP Address fields in DB have char(40) type 2011-03-22 14:06:14 -07:00
schema-level.sql more file changes 2010-09-09 13:27:20 -07:00
schema-snapshot-217to223.sql added 2.2.2 to 2.2.4 2011-03-18 10:41:58 -07:00
server-setup.sql Source code committed 2010-08-11 09:13:29 -07:00
server-setup.xml comment out snmp configuration in server-setup.xml 2011-02-04 20:09:04 -08:00
templates.kvm.sql Source code committed 2010-08-11 09:13:29 -07:00
templates.sql bug 8655: add security group for direct tagged network 2011-02-23 15:53:14 -05:00
templates.vmware.sql Update vcenter address to vmware demo instance 2010-09-29 18:40:48 -07:00
templates.xenserver.sql bug 6546: support ubuntu 10.04 PV kernel, 2010-10-21 18:28:31 -07:00