Hi Hean,

With ansible I create the offerings like this (in 4.14)

   - name: Create a customizable LS SSD disk
      cs_disk_offering:
        name: ls-ssd-custom
        display_text: Custom Size Local Storage SSD 
        customized: yes
        storage_type: local

    - name: Create Local Storage Instances
      cs_service_offering:
        name: micro-ls
        display_text: micro local storage 
        cpu_number: 1
        cpu_speed: 500
        memory: 512
        storage_type: local




But I tested before with the UI and it was possible too.

As you select this offering when creating a new instance, local storage will be 
used.

I don't have any other setting apart of asking for System VMs to use local 
storage too, but I believe that is unrelated:
system.vm.use.local.storage



Are you also using 4.14 for this?

Rafael

On Wed, 2020-09-23 09:20 AM, Hean Seng <[email protected]> wrote:
> I created compute offering , select Local, but after created the offering,
> i click back and see the detail
> 
> Storage Type
> shared
> 
> It still show Storage Type Share, may be update to db wrong ?
> 
> 
> 
> On Wed, Sep 23, 2020 at 3:13 PM Rafael del Valle " 
> target="_blank"><[email protected]>
> wrote:
> 
> > Hi Hean,
> >
> > Did you create a Compute offering with local storage?
> >
> > I found that I had to create both compute and storage offerings with local
> > storage enabled, and this was not obvious in documentation. At least in
> > 4.14. This was before managed through configuration, i think.
> >
> > Rafael
> >
> > On Wed, 2020-09-23 09:09 AM, Hean Seng " 
> > target="_blank"><[email protected]> wrote:
> > > Hi
> > >
> > > I creating another cluster with 1 hpervisor host and local storage.
> > >
> > > After successfully added hypervisor, the localstorage is automatically
> > > recognized at Primary Storage , it show up .
> > >
> > > I proceed to create a VM, and choose to the this new cluster that just
> > > create, and seems VM is not successfully create. Following is log , seems
> > > unable to find storage.
> > >
> > > Any one know what is the issue of ?
> > >
> > > 2020-09-23 03:03:13,205 DEBUG [c.c.n.NetworkModelImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Service SecurityGroup is not supported in the network id=229
> > >
> > > 2020-09-23 03:03:13,212 DEBUG [c.c.n.NetworkModelImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Service SecurityGroup is not supported in the network id=229
> > >
> > > 2020-09-23 03:03:13,216 DEBUG [c.c.v.UserVmManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Destination Host to deploy the VM is specified, specifying a deployment
> > > plan to deploy the VM
> > >
> > > 2020-09-23 03:03:13,239 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > DeploymentPlanner allocation algorithm: null
> > >
> > > 2020-09-23 03:03:13,239 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Trying to allocate a host and storage pools from dc:4, pod:4,cluster:10,
> > > requested cpu: 500, requested ram: 524288000
> > >
> > > 2020-09-23 03:03:13,239 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > Is
> > > ROOT volume READY (pool already allocated)?: No
> > >
> > > 2020-09-23 03:03:13,239 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > DeploymentPlan has host_id specified, choosing this host and making no
> > > checks on this host: 9
> > >
> > > 2020-09-23 03:03:13,240 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Looking for suitable pools for this host under zone: 4, pod: 4, cluster:
> > 10
> > >
> > > 2020-09-23 03:03:13,244 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Checking suitable pools for volume (Id, Type): (65,ROOT)
> > >
> > > 2020-09-23 03:03:13,244 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > We
> > > need to allocate new storagepool for this volume
> > >
> > > 2020-09-23 03:03:13,246 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Calling StoragePoolAllocators to find suitable pools
> > >
> > > 2020-09-23 03:03:13,248 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > LocalStoragePoolAllocator trying to find storage pool to fit the vm
> > >
> > > 2020-09-23 03:03:13,248 DEBUG
> > [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > ClusterScopeStoragePoolAllocator looking for storage pool
> > >
> > > 2020-09-23 03:03:13,248 DEBUG
> > [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Looking for pools in dc: 4  pod:4  cluster:10. Disabled pools will be
> > > ignored.
> > >
> > > 2020-09-23 03:03:13,250 DEBUG
> > [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Found pools matching tags: []
> > >
> > > 2020-09-23 03:03:13,251 DEBUG
> > [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > No
> > > storage pools available for shared volume allocation, returning
> > >
> > > 2020-09-23 03:03:13,251 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > ZoneWideStoragePoolAllocator to find storage pool
> > >
> > > 2020-09-23 03:03:13,255 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > No
> > > suitable pools found for volume: Vol[65|vm=54|ROOT] under cluster: 10
> > >
> > > 2020-09-23 03:03:13,255 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > No
> > > suitable pools found
> > >
> > > 2020-09-23 03:03:13,255 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Cannot deploy to specified host, returning.
> > >
> > > 2020-09-23 03:03:13,258 DEBUG [c.c.v.UserVmManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Destroying vm VM[User|i-2-54-VM] as it failed to create on Host with Id:9
> > >
> > > 2020-09-23 03:03:13,263 DEBUG [c.c.c.CapacityManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > VM
> > > state transitted from :Stopped to Error with event:
> > > OperationFailedToErrorvm's original host id: null new host id: null host
> > id
> > > before state transition: null
> > >
> > > 2020-09-23 03:03:13,294 DEBUG [c.c.r.ResourceLimitManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Updating resource Type = volume count for Account = 2 Operation =
> > > decreasing Amount = 1
> > >
> > > 2020-09-23 03:03:13,302 DEBUG [c.c.r.ResourceLimitManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Updating resource Type = primary_storage count for Account = 2 Operation
> > =
> > > decreasing Amount = 8589934592
> > >
> > > 2020-09-23 03:03:13,321 WARN  [c.c.a.AlertManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > AlertType:: 8 | dataCenterId:: 4 | podId:: null | clusterId:: null |
> > > message:: Failed to deploy Vm with Id: 54, on Host with Id: 9
> > >
> > > 2020-09-23 03:03:13,331 DEBUG [c.c.r.ResourceLimitManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Updating resource Type = user_vm count for Account = 2 Operation =
> > > decreasing Amount = 1
> > >
> > > 2020-09-23 03:03:13,343 DEBUG [c.c.r.ResourceLimitManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Updating resource Type = cpu count for Account = 2 Operation = decreasing
> > > Amount = 1
> > >
> > > 2020-09-23 03:03:13,351 DEBUG [c.c.r.ResourceLimitManagerImpl]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > Updating resource Type = memory count for Account = 2 Operation =
> > > decreasing Amount = 500
> > >
> > > 2020-09-23 03:03:13,357 DEBUG [c.c.a.ApiServlet]
> > > (qtp1710989308-21:ctx-99782efd) (logid:f32fadd3) ===START===
> > 27.122.58.158
> > > -- GET
> > >
> > jobId=cce85213-4ca1-4e2f-a6b3-55a18c85abf3&command=queryAsyncJobResult&response=json
> > >
> > > 2020-09-23 03:03:13,364 DEBUG [c.c.a.ApiServer]
> > > (qtp1710989308-21:ctx-99782efd ctx-8a293ba6) (logid:f32fadd3) CIDRs from
> > > which account 'Acct[f6e6a1e8-da2a-11ea-97be-422b027e31b6-admin]' is
> > allowed
> > > to perform API calls: 0.0.0.0/0,::/0
> > >
> > > 2020-09-23 03:03:13,370 INFO  [o.a.c.a.c.u.v.DeployVMCmd]
> > > (API-Job-Executor-6:ctx-8a914274 job-740 ctx-b8369f5d) (logid:cce85213)
> > > com.cloud.exception.InsufficientServerCapacityException: Unable to
> > create a
> > > deployment for VM[User|i-2-54-VM]Scope=interface com.cloud.dc.DataCenter;
> > > id=4
> > >
> > >
> > >
> > >
> > > --
> > > Regards,
> > > Hean Seng
> > >
> 
> 
> 
> --
> Regards,
> Hean Seng
> 

Reply via email to