[Rdo-list] RDO-Manager ovecloud change existing plan, how?

Wed May 27 10:01:17 UTC 2015

Hi Jay,

thank you for you answer, in fact I was running instack-deploy-overcloud
after those commands, I didn't realize it deleted the plan, so a couple of
questions:

- Should I run something like "heat stack-create -f
tuskar_templates/plan.yaml -e  tuskar_templates/environment.yaml" instead?
Will it work?
- Or should I wait for that to be ready in UI, if I understood correctly,
and test it from there?

Thanks,
Pedro Sousa

On Tue, May 26, 2015 at 8:07 PM, Jay Dobies <jason.dobies at redhat.com> wrote:

>
>
> On 05/26/2015 02:19 PM, Pedro Sousa wrote:
>
>> Hi Hugh,
>>
>> I've tried to change the plan:
>>
>> # tuskar plan-update -A Compute-1::NeutronEnableTunnelling=False
>> c91b13a2-afd6-4eb2-9a78-46335190519d
>> # tuskar plan-update -A Controller-1::NeutronEnableTunnelling=False
>> c91b13a2-afd6-4eb2-9a78-46335190519d
>> # export NEUTRON_NETWORK_TYPE=vlan
>>
>> But the stack failed, I also see that plan-update doesn't work:
>>
>
> It depends on what you did between the lines above and the line below.
>
> If you're making the updates above and then running
> instack-deploy-overcloud, it's not going to work. That script deletes the
> plan and recreates it, losing your updates in the process.
>
> That logic (role addition and plan create) is being moved out of
> instack-deploy-overcloud to an installation-time step to enable this sort
> of thing (not fully sure the state of that, but the UI needs the plan
> create to be done during install as well).
>
>  [stack at instack ~]$ heat stack-show 4dd74e83-e90f-437f-b8b5-ac45d6ada9db
>> | grep Tunnel
>> |                       |   "Controller-1::NeutronEnableTunnelling":
>> "True",
>>
>> Regards
>> Pedro Sousa
>>
>>
>>
>>
>> On Tue, May 26, 2015 at 6:39 PM, Hugh Brock <hbrock at redhat.com
>> <mailto:hbrock at redhat.com>> wrote:
>>
>>     It should be... But we haven't really tested it yet, to my
>>     knowledge. It's an important configuration that we want to support.
>>
>>     If you are able to sort it out and past your results here, that
>>     would be great!
>>
>>     -Hugh
>>
>>     Sent from my mobile, please pardon the top posting.
>>
>>     *From:* Pedro Sousa <pgsousa at gmail.com <mailto:pgsousa at gmail.com>>
>>     *Sent:* May 26, 2015 7:28 PM
>>     *To:* Giulio Fidente
>>     *Cc:* Marios Andreou;rdo-list at redhat.com
>>     <mailto:Andreou%3Brdo-list at redhat.com>;Jason Dobies
>>     *Subject:* Re: [Rdo-list] RDO-Manager ovecloud change existing plan,
>>     how?
>>
>>
>>     Hi all,
>>
>>     thanks to Giulio recommendations in #rdo I've managed to change some
>>     parameters:
>>
>>     #heat stack-delete overcloud
>>     #export NEUTRON_TUNNEL_TYPES=vxlan
>>     #export NEUTRON_TUNNEL_TYPE=vxlan
>>     #export NEUTRON_NETWORK_TYPE=vxlan
>>     #instack-deploy-overcloud --tuskar
>>
>>     This works for TUSKAR_PARAMETERS contained in the
>>     instack-deploy-overcloud script (please correct me if I'm wrong).
>>
>>     My question is if it's possible to use VLAN for tenants, using a
>>     VLAN range and disable GRE/VXLAN tunneling.
>>
>>     Thanks,
>>     Pedro Sousa
>>
>>
>>     On Mon, May 25, 2015 at 12:36 PM, Giulio Fidente
>>     <gfidente at redhat.com <mailto:gfidente at redhat.com>> wrote:
>>
>>         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
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20150527/57f09f7c/attachment.html>