You can use tags in disk offering/service offering to put volume in specific
storage pool.
You can specify algorithms for volume placement. For more info refer
http://support.citrix.com/article/CTX135790.
-Original Message-
From: Mārtiņš Jakubovičs [mailto:[email protected]]
Sent: Tue
Hi Somesh,
Yes i was successful in stopping both the system vm's and starting them
back i also could access them through the console that cloudstack provides.
May be the reason for that code snippet is that i didn't register the
template but i ran this script to install the system vm's.
1.
/
Thanks for your support Kevin
I have fine tuned cpu.overprovisioning.factor settings to manage my
capacity at this movement. I am keen to know is there any other way to
display the actual CPU socket count on the ACS infrastructure dashboard ?
Thanks
AR
On 1 January 2015 at 00:38, Kevin McCormick
Hi,
I updated my cloudstack deployment to 4.4.2 to 4.3.1. Now when we try to
deploy a VM i am getting following error
message. com.cloud.exception.StorageUnavailableException: Resource
[StoragePool:2] is unreachable: Unable to create
Vol[30|vm=58|ROOT]:com.cloud.utils.exception.CloudRuntimeExcepti
The sec store has some issues, you can login into KVM host and check if the sec
storage mount point is visible and the said folder is there. Check if ssvm is
running fine.
It is also possible that the sec store is fine but the template that is being
used to create VM is in inconsistent state, th
For now you can set ³pool.storage.capacity.disablethreshold² to 1 in
global settings , and restart ms .
Insufficient space on pool: 1 since its usage percentage:
0.9072490225390984 has crossed the pool.storage.capacity.disablethreshold:
0.85
On 12/31/14, 11:19 PM, "Somesh Naidu" wrote:
>> 20
Note - thinking about this some more, you may want to note that it behaves
as you say for pods and clusters, but not for zones. For those, only
exact matches work, which is, frankly, what I’d prefer. So there’s
inconsistent behavior from the API.
-I
On 12/31/14, 1:54 AM, "Rohit Yadav" wrote:
You should file bug reports for such things that you discover, I
understand there are (semantic) inconsistencies in the APIs but since I
did not implement those APIs I won't know any technical reason behind
those decisions.
On Friday 02 January 2015 10:54 AM, Ian Forde wrote:
Note - thinking abo
No worries - I just didn’t want to file one without having confirmation on
the mailing list first. ;) Thanks again…
-I
On 1/1/15, 9:44 PM, "Rohit Yadav" wrote:
>You should file bug reports for such things that you discover, I
>understand there are (semantic) inconsistencies in the APIs but s
