Re: Re[2]: Detach Root Disck

2016-10-05 Thread Simon Weller
Great! The re-attach of a root disk occurs the same way. Just pass device ID of 0. - Si From: David Amorín Sent: Wednesday, October 5, 2016 12:19 PM To: users@cloudstack.apache.org Subject: RE: Re[2]: Detach Root Disck Hi Simon

RE: Re[2]: Detach Root Disck

2016-10-05 Thread David Amorín
Hi Simon We tried to pass device ID of 0 and now we can dettach root disk directly. That's awesome!! I really appreciate your help .. David Amorín En 28 sept. 2016 15:08, en 15:08, Simon Weller escribió: >Pass device id of 0. > >Kvm should support

Re: Re[4]: Network ACL rules in VPCs are applied in an inverted order (CLOUDSTACK-9404)

2016-10-05 Thread Simon Weller
Try doing a restart with network cleanup and see if that fixes your problem. The fixes are in the system iso and that will required a redeploy. - Si From: David Amorín Sent: Wednesday, October 5, 2016 11:18 AM To: Simon Weller;

Re[4]: Network ACL rules in VPCs are applied in an inverted order (CLOUDSTACK-9404)

2016-10-05 Thread David Amorín
Yes, we did the upgrade from 4.5.2 to 4.9.0 -- Mensaje original -- De: "Simon Weller" Para: "users@cloudstack.apache.org" ; "David Amorín" Enviado: 05/10/2016 18:11:26 Asunto: Re: Re[2]: Network ACL rules

Re: Re[2]: Network ACL rules in VPCs are applied in an inverted order (CLOUDSTACK-9404)

2016-10-05 Thread Simon Weller
Was this an upgrade from an older release? From: David Amorín Sent: Wednesday, October 5, 2016 10:11 AM To: users@cloudstack.apache.org Subject: Re[2]: Network ACL rules in VPCs are applied in an inverted order (CLOUDSTACK-9404)

Re[2]: Network ACL rules in VPCs are applied in an inverted order (CLOUDSTACK-9404)

2016-10-05 Thread David Amorín
We are running 4.9.0 and we are still facing the issues of the ACL Rules (CLOUDSTACK-9404) -- Mensaje original -- De: "Simon Weller" Para: "users@cloudstack.apache.org" ; "David Amorín" Enviado: 04/10/2016

Re: Implicit dedication vs Explicit dedication

2016-10-05 Thread Sergey Levitskiy
To do so you can use a specific service offerring. Sent from my iPhone > On Oct 5, 2016, at 7:14 AM, cs user wrote: > > Hi Rafael, > > Thanks for responding. It is possible to force them to only be able to use > that pod however? > > So that when the create a machine,

Re: Implicit dedication vs Explicit dedication

2016-10-05 Thread Rafael Weingärtner
That is a good question. Sorry I have not seen your first email. I have just read it now. I noticed you already tried dedicating a POD to an account. I am curious by what you meant with: "When the account selects this service offering, the instance is created on an empty host. Addition instances

Re: Implicit dedication vs Explicit dedication

2016-10-05 Thread cs user
Hi Rafael, Thanks for responding. It is possible to force them to only be able to use that pod however? So that when the create a machine, these machines are forced to launch in that pod. Cheers On Wed, Oct 5, 2016 at 3:11 PM, Rafael Weingärtner < rafaelweingart...@gmail.com> wrote: > You can

Re: Implicit dedication vs Explicit dedication

2016-10-05 Thread Rafael Weingärtner
[UPDATE] this is the API method that you could use: https://cloudstack.apache.org/api/apidocs-4.9/apis/dedicatePod.html On Wed, Oct 5, 2016 at 11:11 AM, Rafael Weingärtner < rafaelweingart...@gmail.com> wrote: > You can dedicate a pod to a user account or domain. > Have you tried that? > > On

Re: Implicit dedication vs Explicit dedication

2016-10-05 Thread Rafael Weingärtner
You can dedicate a pod to a user account or domain. Have you tried that? On Wed, Oct 5, 2016 at 11:09 AM, cs user wrote: > Hi All, > > I asked this a while back and never got a response. With the latest version > of Cloudstack, is it possible to force an account to launch

Re: Implicit dedication vs Explicit dedication

2016-10-05 Thread cs user
Hi All, I asked this a while back and never got a response. With the latest version of Cloudstack, is it possible to force an account to launch in a particular pod? Cheers! On Mon, Mar 21, 2016 at 12:59 PM, cs user wrote: > Hi All, > > Question regarding dedicating a Pod

Re: Error in creating new instances

2016-10-05 Thread Dag Sonstebo
Hi Ghait, So your problem secondary share is hosted on a XenServer? Apart from this not being supported I could see this causing you a few technical issues – I would suggest you move your problem secondary share to your CentOS box. Attachments are stripped from mailing list postings

RE: Error in creating new instances

2016-10-05 Thread Ghaith Bannoura
Best Regards, Ghaith Bannoura G http://www.etq.com -Original Message- From: Ghaith Bannoura [mailto:gbanno...@etq.com] Sent: Wednesday, October 5, 2016 3:37 PM To: users@cloudstack.apache.org Subject: RE: Error in creating new instances Hello Dag, Sorry for that but I founded the

RE: Error in creating new instances

2016-10-05 Thread Ghaith Bannoura
Hello Dag, Sorry for that but I founded the two logs and I attached them . Also I use the local storage as primary storage and three secondary shares (two of them on centos NFS and one another in xenserver that have the error) Can you please advise if you able to find anything useful in the

Re: Error in creating new instances

2016-10-05 Thread Dag Sonstebo
Hi Ghait, It seems very odd that you don’t have a /var/log/SMlog file – this should be present. Lacking that also check your /var/log/xensource.log and messages files. Can you also explain what provides your NFS secondary and primary shares? Regards, Dag Sonstebo On 04/10/2016, 20:09, "Ghaith