Hey Wido,
What do you mean by unset?
When the disk offering is created i do not specify disksize so it is
defaulted to 0.
Moreover when custom disk offering is created and a disksize value is
defined ACS reports an error that this value is not allowed to be defined.
This is the command:
createDiskOffering isMirrored=false name=custom-disk2
displaytext=custom-disk2 storageType=local cacheMode=none
provisioningType=thin customized=true disksizestrictness=false disksize=20
The error:
Error: (HTTP 431, error code 4350) Disksize is not allowed for a customized
disk offering
Regards,
Jordan
On Fri, Nov 4, 2022 at 2:59 PM Wido den Hollander <w...@widodh.nl> wrote:
>
>
> Op 04-11-2022 om 09:30 schreef jordan j:
> > Yes CPU/RAM are fixed!
> >
> > Code for disk and service offering:
> >
> > createDiskOffering isMirrored=false name=custom-disk
> > displaytext=custom-disk storageType=local cacheMode=none
> > provisioningType=thin customized=true disksizestrictness=false
> > {
> > "diskoffering": {
> > "cacheMode": "none",
> > "created": "2022-11-04T09:27:03+0100",
> > "disksize": 0,
>
> Have you tried to simply unset the disksize? If you don't specify it,
> it's custom and something you can define yourself.
>
> Wido
>
> > "disksizestrictness": false,
> > "displayoffering": true,
> > "displaytext": "custom-disk",
> > "hasannotations": false,
> > "id": "c7d11a8d-29eb-44b0-811c-fb57dbaac2a5",
> > "iscustomized": true,
> > "name": "custom-disk",
> > "provisioningtype": "thin",
> > "storagetype": "local"
> > }
> > }
> >
> > createServiceOffering issystem=false name=fixed-compute
> > displaytext=fixed-compute customized=false offerha=false
> limitcpuuse=false
> > dynamicscalingenabled=true cpunumber=2 cpuspeed=2000 memory=2048
> > diskofferingid=c7d11a8d-29eb-44b0-811c-fb57dbaac2a5
> > {
> > "serviceoffering": {
> > "cacheMode": "none",
> > "cpunumber": 2,
> > "cpuspeed": 2000,
> > "created": "2022-11-04T09:28:52+0100",
> > "defaultuse": false,
> > "diskofferingdisplaytext": "custom-disk",
> > "diskofferingid": "c7d11a8d-29eb-44b0-811c-fb57dbaac2a5",
> > "diskofferingname": "custom-disk",
> > "diskofferingstrictness": false,
> > "displaytext": "fixed-compute",
> > "dynamicscalingenabled": true,
> > "hasannotations": false,
> > "id": "f5a61b2f-9b03-4322-9d10-bb69033a87dd",
> > "iscustomized": false,
> > "issystem": false,
> > "isvolatile": false,
> > "limitcpuuse": false,
> > "memory": 2048,
> > "name": "fixed-compute",
> > "offerha": false,
> > "provisioningtype": "thin",
> > "rootdisksize": 0,
> > "storagetype": "local"
> > }
> > }
> >
> > Regards,
> > Jordan
> >
> > On Fri, Nov 4, 2022 at 3:22 AM Harikrishna Patnala <
> > harikrishna.patn...@shapeblue.com> wrote:
> >
> >> Can you please share the CLI list responses of the service offering and
> >> disk offering (fixed-compute-with-custom-disk) that you have used in
> your
> >> case 2, so that I’ll create the exact same offerings and try to deploy
> the
> >> VM.
> >>
> >> When you say “Create any service offering (used fixed for the test)”, do
> >> you mean fixed compute details like CPU, RAM ?
> >>
> >> Thanks,
> >> Harikrishna
> >>
> >> From: jordan j <yordan...@gmail.com>
> >> Date: Thursday, 3 November 2022 at 2:06 PM
> >> To: users@cloudstack.apache.org <users@cloudstack.apache.org>
> >> Subject: Re: compute cannot be used if rot disk size is 0
> >> Hi Harikrishna!
> >>
> >> Upgraded to 4.17.1 and did some more tests.
> >>
> >> 1. Create any service offering mapped to disk offering with fixed size -
> >> this works
> >> 2. Create any service offering (used fixed for the test) mapped to disk
> >> offering with custom size - this brings the error mentioned during
> instance
> >> creation.
> >>
> >> During case 2 when in GUI there is Root disk size (GB) option but it
> does
> >> not matter to what it is set, the error always appears.
> >> This case is similar to what you do in case 3. The question is what is
> it
> >> that you do that makes it work on your side and fail on mine.
> >>
> >> Here is a link with the error message and the options selected during
> >> instance creation: https://imgur.com/l3WktFg
> >> DIsk offering is custom and I set it to 50 but ACS does not take it into
> >> account and still thinks it is 0.
> >>
> >> Regards,
> >> Jordan
> >>
> >> On Thu, Nov 3, 2022 at 9:26 AM Harikrishna Patnala <
> >> harikrishna.patn...@shapeblue.com> wrote:
> >>
> >>> Hi Jordan,
> >>>
> >>> I’ve tried these scenarios in 4.17.1 and it seems to be working fine.
> >> This
> >>> might be an issue in 4.17 but it is working fine in 4.17.1
> >>>
> >>> I tried the following scenarios,
> >>>
> >>> 1. Created a service offering with an existing disk offering and
> >>> deployed VM with it from GUI. It worked fine.
> >>> 2. Tried the same from CLI (without rootdisksize). It worked fine.
> >>> 3. Created a service offering with an existing CUSTOM disk offering
> >> and
> >>> deployed VM with it from GUI. It worked fine too.
> >>>
> >>> Can you please try upgrading your environment to 4.17.1 ?
> >>>
> >>> Also I did not understand your scenario why rootdisksize comes to
> picture
> >>> when diskoffering is mapped to a service offering ? Is that a custom
> disk
> >>> offering ?
> >>>
> >>> Thanks,
> >>> Harikrishna
> >>> From: jordan j <yordan...@gmail.com>
> >>> Date: Wednesday, 2 November 2022 at 8:01 PM
> >>> To: users@cloudstack.apache.org <users@cloudstack.apache.org>
> >>> Subject: compute cannot be used if rot disk size is 0
> >>> Hey everyone,
> >>>
> >>> I found a bug (4.17.0.1).
> >>>
> >>> if you try to create an instance from compute offering that has root
> disk
> >>> size = 0 the following error appears:
> >>> VM Creation failed. Volume size: -1GB is out of allowed range. Max:
> 1024
> >>> Min:1
> >>>
> >>> A few examples when rootdisk size is set as 0:
> >>> - when compute offering is created and matched to existing disk
> offering
> >>>
> >>> --> via GUI same thing as CLI
> >>> If a compute offering is created by specifying existing disk offering,
> >>> the root disk size is set as 0
> >>> Workaround: When creating Compute offering, enable "Compute only disk
> >>> offering" option, change the root disk size to a value larger than 0.
> >> After
> >>> that disable "Compute only disk offering" and attach to existing disk
> >>> offering.
> >>>
> >>> --> via CLI - in the example below the rootdisk is defined as 10 but it
> >>> will not be set as diskofferringid overrides it. So 0 will be the end
> >>> result.
> >>> create serviceoffering name=infra-compute displaytext=infra-compute
> >>> customized=true dynamicscalingenabled=true cpuspeed=2000 mincpunumber=1
> >>> maxcpunumber=4 minmemory=512 maxmemory=2048
> >>> diskofferingid=851dd105-77ee-45d9-8094-807c9824a053 rootdisksize=10
> >>>
> >>> Is there any workaround for cli on how to update the rootdisksize ?
> >>> update serviceoffering does not allow such modification.
> >>>
> >>> Regards,
> >>> Jordan
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
>
