<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hello Steven,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I just tested the method as you provided and it worked well.<br></div><span class="gmail-im"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">parameter_defaults:<br>
    ComputeExtraConfig:<br>
         nova::cpu_allocation_ratio: 10.0<br>
         nova::ram_allocation_ratio: 1.0</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div></span><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Thank you so much!</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Best regards,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Cody</div></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 11, 2018 at 6:27 AM Steven Hardy <<a href="mailto:shardy@redhat.com">shardy@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Oct 11, 2018 at 4:26 AM Cody <<a href="mailto:codeology.lab@gmail.com" target="_blank">codeology.lab@gmail.com</a>> wrote:<br>
><br>
> Hi everyone,<br>
><br>
> If I wish to define CPU and RAM allocation ratios at the time of deployment for the Queens release, which one of the following methods is correct?<br>
><br>
> # Method 1<br>
> parameter_defaults:<br>
>     ComputeExtraConfig:<br>
>         nova::compute::cpu_allocation_ratio: 10.0<br>
>         nova::compute::ram_allocation_ratio: 1.0<br>
<br>
This is the right approach but the hiera keys you're using are wrong I<br>
think - check:<br>
<br>
<a href="https://github.com/openstack/tripleo-heat-templates/blob/stable/queens/puppet/services/nova-scheduler.yaml" rel="noreferrer" target="_blank">https://github.com/openstack/tripleo-heat-templates/blob/stable/queens/puppet/services/nova-scheduler.yaml</a><br>
<a href="https://github.com/openstack/puppet-nova/blob/master/manifests/init.pp#L385" rel="noreferrer" target="_blank">https://github.com/openstack/puppet-nova/blob/master/manifests/init.pp#L385</a><br>
<br>
So something like:<br>
<br>
  parameter_defaults:<br>
     ComputeExtraConfig:<br>
         nova::cpu_allocation_ratio: 10.0<br>
         nova::ram_allocation_ratio: 1.0<br>
<br>
is probably neeeded - for *ExtraConfig overrides the hiera keys must<br>
always align with the interfaces exposed by the underlying puppet<br>
modules.<br>
<br>
><br>
> # Method 2<br>
> parameter_defaults:<br>
>     NovaCpuAllocationRatio: 10.0<br>
>     NovaRamAllocationRatio: 1.0<br>
<br>
I don't think this will work because no parameters with these names<br>
are exposed via tripleo-heat templates (see the link to<br>
nova-scheduler.yaml above for example).<br>
<br>
Such an interface could be added though, but we don't expose every<br>
puppet/hiera option as heat parameters (a case can probably be made<br>
for these being common enough to add though).<br>
<br>
Hope that helps,<br>
<br>
Steve Hardy<br>
</blockquote></div>