13 Commits

Author	SHA1	Message	Date
David Nalley	c15948a3ef	committing Chip Childers patches fixing licensing headers ... Applying to the following directories: * api * deamonize * agnet * agent-simulator * cloud-cli	2012-06-12 12:32:58 -04:00
frank	2f634c0913	Switch to Apache license	2012-04-03 04:50:05 -07:00
prachi	e37732c4de	Bug 13766 - VMs are still running after disabling the zone ... Reviewed-by: Sheng Yang Changes: - Do not check if allocation_state is 'Enabled' in planner if the caller is Root Admin. - This should let Root Admin create a VM in a disabled Zone.	2012-02-22 17:34:00 -08:00
Alena Prokharchyk	3a87cf8331	Code style fixes for API package	2012-02-03 14:25:26 -08:00
alena	219978a9be	Create network using physical network id	2011-10-20 18:25:13 -07:00
Sheng Yang	e5e76881c6	Redundant virtual router: Try to deploy the second virtual router to different pod/cluster/host/storagepool ... The old strategy is to deploy the second virtual router to diffent host only.	2011-07-19 14:26:37 -07:00
Alex Huang	ee2670edc7	Some operations on the lock table allowed through jmx	2011-07-06 16:10:18 -07:00
Frank	92155522f2	Add license header to files	2011-04-14 11:23:14 -07:00
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
Alex Huang	e27bb550fe	Harmony among gurus	2010-11-03 21:18:31 -07:00
root	077690cf15	switched from networkprofile to network configuration	2010-09-09 17:48:24 -07:00
Alex Huang	b250b985ec	changes	2010-08-18 12:19:22 -07:00
Manuel Amador (Rudd-O)	05c020e1f6	Source code committed	2010-08-11 09:13:29 -07:00