On 05/25/2015 01:09 PM, Pedro Sousa wrote:

Hi all,

I've deployed rdo-manager in a virt env and everything is working fine
except the vnc console which is alreday an open bug for that.

Now I would like to change some parameters on my deployment, let's say I
wan't to disable NeutronTunneling, I wan't to use VLAN for tenants and
use 1500 MTU on dnsmasq.

So I downloaded the plan:

#tuskar plan-templates -O /tmp uuid

changed plan.yaml, environment.yaml, provider-Controller-1.yaml,
provider-Compute-1.yaml.

than I ran the stack:

# heat stack-create -f tmp/plan.yaml -e tmp/environment.yaml overcloud

The overcloud is deployed fine but the values aren't changed. What I'm
missing here?

hi,

if you launch stack-create manually the newly created overcloud is not reprovisioned with the initial keystone endpoints/users/roles ... to get an usable overcloud you should launch instack-deploy-overcloud again

so you can change the defaults for the various params by patching the tuskar plan with 'tuskar plan-update' see [1]

yet some of these are automatically parsed from ENV vars, like NEUTRON_TUNNEL_TYPES and NEUTRON_NETWORK_TYPE see [2]

the NeutronDnsmasqOptions param instead is not parsed from any ENV var, so you're forced to use 'tuskar plan-update'

I'm adding a couple of guys on CC who migh help but, let us know how it goes!

1. https://github.com/rdo-management/instack-undercloud/blob/master/scripts/instack-deploy-overcloud#L274

2. https://github.com/rdo-management/instack-undercloud/blob/master/scripts/instack-deploy-overcloud#L205-L208
--
Giulio Fidente
GPG KEY: 08D733BA