Your Service Offering (specifically Compute Offering) needs to be
marked "HA". That will cause cloudstack to restart VM's automatically
when they go down or the server they are running on goes down.
See page 116 of the Administration Guide.
You can change the Service Offering of an existing VM. P
This is a bug. I just checked the code but couldn't find the reason for it
being there.
if (zone != null) {
sc.setParameters("dataCenterId", zone);
if(state == null) {
sc.setParameters("stateNEQ", "Destroyed");
}
}
Thanks,
-
Vms in Destroyed state should be returned in listVirtualMachines API
response (when the call is made by root/domain Admin) no matter if it's
executed with zoneId, or w/o.
Simon, please file a bug against management server component.
Thanks,
Alena.
On 10/5/12 9:27 AM, "Simon Waterhouse"
wrote:
I have a single zone CloudStack with some deleted instances in the zone
If I use the REST API to query "command=listVirtualMachines" then it returns me
a record of the deleted instances. However if I specify the UID of the zone
with the query "command=listVirtualMachines&zoneid=" then the server
We've had this requirement a few times before.
In short, it goes against CS's concept of service offerings
Theres two approaches we've used:
1. create, in advance, service offerings of every permutation of
memory/cpu/disk that you want to sell. Or
2. Use the API to generate new service offerin
HI,
I'm not sure you actually can. What billing integration we have is service
offering based.
You can create as many as you want and you price them individually. I think
cloud usage stores how long a service offering was used and you bill based on
that.
Of course there are other aspects to usa
