[Rdo-list] RDO Manager Liberty DVR

[Dan Sneddon]

On 02/24/2016 03:41 PM, Charles Short wrote:
> Thanks for the reply.
> 
> Sorry I should have been more explicit and mentioned that I actually created new altered files enabling DVR and used the override to reference them , leaving the originals untouched ( as I had already done with network config files for the nodes).
> I will try creating a custom environment file and see if I have more luck implementing the changes 
> 
> Regards
> 
> Charles
> 
> Sent from my iPhone
> 
>> On 24 Feb 2016, at 23:10, Dan Sneddon <dsneddon at redhat.com> wrote:
>>
>>> On 02/24/2016 02:24 PM, Charles Short wrote:
>>> Hi,
>>>
>>> I am trying to deploy DVR with RDO manager.
>>> I can find template references to DVR in -
>>>
>>> /usr/share/openstack-tripleo-heat-templates/puppet/controller.yaml
>>> /usr/share/openstack-tripleo-heat-templates/puppet/compute.yaml
>>>
>>> I altered the defaults to enable DVR  and deployed the Overcloud
>>> successfully.
>>> Unfortunately the DVR changes I made do not appear in the config files
>>> on the nodes.
>>>
>>> Has anyone managed to deploy DVR with RDO Manager?
>>>
>>> Thanks
>>>
>>> Charles
>>
>> That's not how you want to go about customizing your deployment.
>>
>> Rather than altering the original files, or the defaults, you want to
>> set parameters or defaults in environment files.
>>
>> So, create an environment file with three sections:
>>
>> resource_registry:
>>
>> parameters:
>>
>> parameter_defaults:
>>
>> In these sections, you can override settings that appear in
>> overcloud.yaml and overcloud-resource-registry-puppet.yaml (in the
>> T-H-T root).
>>
>> You include your environment file on the deployment command line with
>> -e <file>.
>>
>> To help you with a basic understanding of how parameters are set:
>>
>> overcloud-resource-registry-puppet.yaml is the source for where the
>> various resource files are found. These are occasionally overridden
>> when you want specific features enabled, such as when using network
>> isolation and you specify your NIC config YAMLs.
>>
>> overcloud.yaml (in the T-H-T root) is where the parameters are all set.
>> If you want to override these, add the needed parameters to the
>> parameter_defaults: section. Sometimes it is necessary to put
>> parameters into the parameters: section (overriding their definition),
>> but usually adding parameter_defaults for the parameter is sufficient.
>>
>> For examples, look in the environments directory inside
>> /usr/share/tripleo-heat-templates.
>>
>> -- 
>> Dan Sneddon         |  Principal OpenStack Engineer
>> dsneddon at redhat.com |  redhat.com/openstack
>> 650.254.4025        |  dsneddon:irc   @dxs:twitter
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/rdo-list
>>
>> To unsubscribe: rdo-list-unsubscribe at redhat.com

The thing is, where you modify the default matters. If there is a
default set, or if the parameter is set, inside overcloud.yaml, then
you need to either change it there, or (better) override it in the
environment file.

In other words, changing the default on a parameter won't have any
effect if the parameter default is already set higher up the
inheritance chain.

overcloud.yaml is the root of the inheritance, so everything below it
inherits the settings from overcloud.yaml, which is 'false' in the case
of NeutronDVR.

-- 
Dan Sneddon         |  Principal OpenStack Engineer
dsneddon at redhat.com |  redhat.com/openstack
650.254.4025        |  dsneddon:irc   @dxs:twitter