Re: issue with compute offering using custom disk offering

s/7070. ;-) > > -Ursprüngliche Nachricht- > Von: Wei ZHOU > Gesendet: Donnerstag, 19. Januar 2023 11:25 > An: users@cloudstack.apache.org > Betreff: Re: issue with compute offering using custom disk offering > > Hi Swen, > > Can you create a github issue with some detail

AW: issue with compute offering using custom disk offering

Sure, I will. I also opened https://github.com/apache/cloudstack/issues/7070. ;-) -Ursprüngliche Nachricht- Von: Wei ZHOU Gesendet: Donnerstag, 19. Januar 2023 11:25 An: users@cloudstack.apache.org Betreff: Re: issue with compute offering using custom disk offering Hi Swen, Can you

Re: issue with compute offering using custom disk offering

stag, 19. Januar 2023 10:34 > An: users@cloudstack.apache.org > Betreff: Re: issue with compute offering using custom disk offering > > Hi, > > This issue should have been fixed in 4.17.1 > > see > https://github.com/apache/cloudstack/pull/6441 > https://github.com/apache/clou

AW: issue with compute offering using custom disk offering

Hi Wei, I am using 4.17.2.0 and still run into this. It is not fixed. Swen -Ursprüngliche Nachricht- Von: Wei ZHOU Gesendet: Donnerstag, 19. Januar 2023 10:34 An: users@cloudstack.apache.org Betreff: Re: issue with compute offering using custom disk offering Hi, This issue should

Re: issue with compute offering using custom disk offering

ot;Override root > disk > size" in the Template/ISO section. This will add rootdisksize to the api > call to create the VM. > > > > Is this a situation we want a typical user of the UI to be in with in the > first place? Any idea how to take care of this kind of situation? &g

Re: issue with compute offering using custom disk offering

n the > first place? Any idea how to take care of this kind of situation? > > > > Here are the steps to reproduce this situation: > > 1. Add a new Disk Offering > > > /client/api/?isMirrored=false=Test+Custom+Disk+Offering=Tes > > t+Custom+Disk+Offering=share

issue with compute offering using custom disk offering

? Here are the steps to reproduce this situation: 1. Add a new Disk Offering /client/api/?isMirrored=false=Test+Custom+Disk+Offering=Tes t+Custom+Disk+Offering=shared=none=th in=true=false=createDiskOffering nse=json 2. Create a new Compute Offering with diskofferingstrictness=true (pleas

Re: IOPS limit on compute offering and disk offering

ivek Kumar wrote: > Hello Folks, > > We have option to define the custom IOPS in compute and disk offering as > well. So we have 2 kind of quota while creating the offerings - > 1st - > Storage ( where we can define Min and Max IOPS ) and 2nd - Hypervisor where > we also define

IOPS limit on compute offering and disk offering

Hello Folks, We have option to define the custom IOPS in compute and disk offering as well. So we have 2 kind of quota while creating the offerings - > 1st - Storage ( where we can define Min and Max IOPS ) and 2nd - Hypervisor where we also define - Disk Read Rate and disk write rate. I h

Re: Disk Offering

thank you my friend Best regards, On Thu, May 26, 2016 at 11:04 AM, Mohd Zainal Abidin Rabani < zai...@nocser.net> wrote: > Hi, > > > > On primary storage I have set NFS. The question is how to set use NFS when > creating disk size under Disk Offering under Service Offerings? > > > > Thanks. > >

RE: Disk Offering

First we need to create disk offering with type shared and then create disk with this disk offering. Disk will be created on NFS storage. Best Regards, Sanjeev N Chief Product Engineer, Accelerite Off: +91 40 6722 9368 | EMail: sanjeev.neelar...@accelerite.com -Original Message- From

Disk Offering

Hi, On primary storage I have set NFS. The question is how to set use NFS when creating disk size under Disk Offering under Service Offerings? Thanks.

RE: change cache option in existing disk offering

Hi Andrei, It is not possible to modify the existing disk offering values. You can create another disk offering with cache option enabled and update the disks with the new offering. Best Regards, Sanjeev N Chief Product Engineer, Accelerite Off: +91 40 6722 9368 | EMail: sanjeev.neelar

change cache option in existing disk offering

Hello guys, I've got a bunch of existing vms which were created before the ACS cache option could be configured. The existing disk offerings show cache=none and I would like to change that. The GUI doesn't give me that option when I am editing the disk offering. Can I simply change

Re: custom size of disk offering.

21:25 To: users@cloudstack.apache.org Subject: Re: custom size of disk offering. Hi, Andrija, Here is the result: ubuntu@node100GB:~$ sudo fdisk -l Disk /dev/vda: 107.4 GB, 107374182400 bytes 16 heads, 63 sectors/track, 208050 cylinders, total 209715200 sectors Units = sectors

Re: custom size of disk offering.

VM disk size is fixed by the template, when the template is created as 20GB, the VM has it as 20GB. Setting disk offering does not change it at all. It is the ROOT disk we are talking about, for DATA disk, it does work. On 13 March 2015 at 15:41, Andrija Panic andrija.pa...@gmail.com wrote: I

Re: custom size of disk offering.

not the case... On 13 March 2015 at 16:36, Dan Dong dongda...@gmail.com wrote: Hi, All, I found when I create a new VM from a template, no matter how I set disk offering, the created new VM always has the same original size. For Example, although I specified 100GB of hard disk, the actual disk size

custom size of disk offering.

Hi, All, I found when I create a new VM from a template, no matter how I set disk offering, the created new VM always has the same original size. For Example, although I specified 100GB of hard disk, the actual disk size remains ~20GB, which should come with the template itself: name = Large id

Re: custom size of disk offering.

... On 13 March 2015 at 16:36, Dan Dong dongda...@gmail.com wrote: Hi, All, I found when I create a new VM from a template, no matter how I set disk offering, the created new VM always has the same original size. For Example, although I specified 100GB of hard disk, the actual disk

RE: custom size of disk offering.

-by-adding-a-new-disk/ -Original Message- From: Dan Dong [mailto:dongda...@gmail.com] Sent: 13 March 2015 21:25 To: users@cloudstack.apache.org Subject: Re: custom size of disk offering. Hi, Andrija, Here is the result: ubuntu@node100GB:~$ sudo fdisk -l Disk /dev/vda: 107.4 GB

Re: custom size of disk offering.

of the developers might confirm...we had discussion about weather CS will also resize partition and FS - which is I guess not the case... On 13 March 2015 at 16:36, Dan Dong dongda...@gmail.com wrote: Hi, All, I found when I create a new VM from a template, no matter how I set disk offering

RE: Changing disk offering for existing volumes

Root volume resize is not yet supported. -Original Message- From: Andrei Mikhailovsky [mailto:and...@arhont.com] Sent: Friday, July 18, 2014 1:36 AM To: users@cloudstack.apache.org Subject: Re: Changing disk offering for existing volumes Alena, Thanks, I didn't realise that the Resize

Disk offering QOS issues / question

Hello guys, I've been playing around with disk QOS on ACS 4.2.1 and KVM and noticed several issues. The first issue that I've discovered is that if you attach a QOS enabled disk to a _running_ vm the QOS settings on the disk are not passed on to the hypervisor. Example of the xml file using

Changing disk offering for existing volumes

Hello guys, I am planning to change the disk offering for the existing guest volumes to accommodate for QOS. I am unable to find the required option in ACS GUI. How does one go about achieving this? Is it simply a matter of doing the changes in the database and restarting the guest vm

Re: Changing disk offering for existing volumes

, I am planning to change the disk offering for the existing guest volumes to accommodate for QOS. I am unable to find the required option in ACS GUI. How does one go about achieving this? Is it simply a matter of doing the changes in the database and restarting the guest vm? Or is there a more

Re: Changing disk offering for existing volumes

Hi Andrei, I'm afraid database hacking is required - I had to become efficient in this :( Sent from Google Nexus 4 On Jul 17, 2014 5:48 PM, Andrei Mikhailovsky and...@arhont.com wrote: Hello guys, I am planning to change the disk offering for the existing guest volumes to accommodate

Re: Changing disk offering for existing volumes

Alena, Thanks, I didn't realise that the Resize option does allow one to change the disk offering and not simply the size of the volume. However, this option doesn't work for the root volumes. I guess db hacking is needed here. Cheers -- Andrei Mikhailovsky Director Arhont Information

set disk on compute or disk offering ?

Hello All, Disk based limitations like iops and others are presented on compute offering and disk offering and looks like collision here Generally how people use it ? I mean leave all network and disk options empty on compute and set it everything on disk and network offerings ? What

Re: Identifying a VM's ROOT disk offering via the database

The Service Offering isn't a DISK Offering though, it only specifies CPU, RAM etc. How do you find the DISK Offering (I feel like I'm going around in circles here lol!) On 25 June 2013 13:59, Koushik Das koushik@citrix.com wrote: For ROOT disk the service offering gets used. For data

RE: Identifying a VM's ROOT disk offering via the database

As I had mentioned in my last mail ROOT disk is created based on the service offering. There is NO separate disk offering associated with a ROOT disk. Disk offering is only for DATA disks. What specific properties are you interested in for the ROOT disk? -Original Message- From: Andy

Re: Identifying a VM's ROOT disk offering via the database

. There is NO separate disk offering associated with a ROOT disk. Disk offering is only for DATA disks. What specific properties are you interested in for the ROOT disk? -Original Message- From: Andy Coates [mailto:andy.coa...@gmail.com] Sent: Tuesday, June 25, 2013 1:27 PM To: users

Identifying a VM's ROOT disk offering via the database

Hey, Does anyone know where in the database you can find out what Disk Offering a VM's ROOT disk is based on? To follow on from that, if you made a template from a new VM (via ISO image) that, for example, used MyDiskOfferingA, would further instances of that template also use the same Disk

RE: Identifying a VM's ROOT disk offering via the database

Andy, If you are deploying a VM from an ISO, the DATA DISK you select becomes the ROOT DISK for that VM and if you are deploying a VM from a template, then the size of template becomes the size of ROOT DISK and you can select additional DISK as DATA DISK from disk offering for the VM

Re: Identifying a VM's ROOT disk offering via the database

Hi Sanjay, That may be the case, but how do you identify what Disk Offering those ROOT disks are based on? After you create a VM you can identify its Service Offering, but not its Disk Offering - and that's what I'm trying to establish here. Some of our Disk Offerings use SATA disks, some use

RE: Identifying a VM's ROOT disk offering via the database

:43 PM To: users@cloudstack.apache.org Subject: Re: Identifying a VM's ROOT disk offering via the database Hi Sanjay, That may be the case, but how do you identify what Disk Offering those ROOT disks are based on? After you create a VM you can identify its Service Offering, but not its