<div dir="ltr">Hi Jay,<div><br></div><div>thank you for you answer, in fact I was running <span style="font-size:13px">instack-deploy-overcloud after those commands, I didn't realize it deleted the plan, so a couple of questions:</span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">- Should I run something like "heat stack-create -f tuskar_templates/plan.yaml -e </span><span style="font-size:13px"> </span><span style="font-size:13px">tuskar_templates/environment.yaml" instead? Will it work? </span></div><div><span style="font-size:13px">- Or should I wait for that to be ready in UI, if I understood correctly, and test it from there?</span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">Thanks,</span></div><div><span style="font-size:13px">Pedro Sousa</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 26, 2015 at 8:07 PM, Jay Dobies <span dir="ltr"><<a href="mailto:jason.dobies@redhat.com" target="_blank">jason.dobies@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 05/26/2015 02:19 PM, Pedro Sousa wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Hugh,<br>
<br>
I've tried to change the plan:<br>
<br>
# tuskar plan-update -A Compute-1::NeutronEnableTunnelling=False<br>
c91b13a2-afd6-4eb2-9a78-46335190519d<br>
# tuskar plan-update -A Controller-1::NeutronEnableTunnelling=False<br>
c91b13a2-afd6-4eb2-9a78-46335190519d<br>
# export NEUTRON_NETWORK_TYPE=vlan<br>
<br>
But the stack failed, I also see that plan-update doesn't work:<br>
</blockquote>
<br></span>
It depends on what you did between the lines above and the line below.<br>
<br>
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.<br>
<br>
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).<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
[stack@instack ~]$ heat stack-show 4dd74e83-e90f-437f-b8b5-ac45d6ada9db<br>
| grep Tunnel<br>
| | "Controller-1::NeutronEnableTunnelling":<br>
"True",<br>
<br>
Regards<br>
Pedro Sousa<br>
<br>
<br>
<br>
<br>
On Tue, May 26, 2015 at 6:39 PM, Hugh Brock <<a href="mailto:hbrock@redhat.com" target="_blank">hbrock@redhat.com</a><br></span><span class="">
<mailto:<a href="mailto:hbrock@redhat.com" target="_blank">hbrock@redhat.com</a>>> wrote:<br>
<br>
It should be... But we haven't really tested it yet, to my<br>
knowledge. It's an important configuration that we want to support.<br>
<br>
If you are able to sort it out and past your results here, that<br>
would be great!<br>
<br>
-Hugh<br>
<br>
Sent from my mobile, please pardon the top posting.<br>
<br></span>
*From:* Pedro Sousa <<a href="mailto:pgsousa@gmail.com" target="_blank">pgsousa@gmail.com</a> <mailto:<a href="mailto:pgsousa@gmail.com" target="_blank">pgsousa@gmail.com</a>>><br>
*Sent:* May 26, 2015 7:28 PM<br>
*To:* Giulio Fidente<br>
*Cc:* Marios <a href="mailto:Andreou%3Brdo-list@redhat.com" target="_blank">Andreou;rdo-list@redhat.com</a><br>
<mailto:<a href="mailto:Andreou%253Brdo-list@redhat.com" target="_blank">Andreou%3Brdo-list@redhat.com</a>>;Jason Dobies<br>
*Subject:* Re: [Rdo-list] RDO-Manager ovecloud change existing plan,<span class=""><br>
how?<br>
<br>
<br>
Hi all,<br>
<br>
thanks to Giulio recommendations in #rdo I've managed to change some<br>
parameters:<br>
<br>
#heat stack-delete overcloud<br>
#export NEUTRON_TUNNEL_TYPES=vxlan<br>
#export NEUTRON_TUNNEL_TYPE=vxlan<br>
#export NEUTRON_NETWORK_TYPE=vxlan<br>
#instack-deploy-overcloud --tuskar<br>
<br>
This works for TUSKAR_PARAMETERS contained in the<br>
instack-deploy-overcloud script (please correct me if I'm wrong).<br>
<br>
My question is if it's possible to use VLAN for tenants, using a<br>
VLAN range and disable GRE/VXLAN tunneling.<br>
<br>
Thanks,<br>
Pedro Sousa<br>
<br>
<br>
On Mon, May 25, 2015 at 12:36 PM, Giulio Fidente<br></span><div><div class="h5">
<<a href="mailto:gfidente@redhat.com" target="_blank">gfidente@redhat.com</a> <mailto:<a href="mailto:gfidente@redhat.com" target="_blank">gfidente@redhat.com</a>>> wrote:<br>
<br>
On 05/25/2015 01:09 PM, Pedro Sousa wrote:<br>
<br>
Hi all,<br>
<br>
I've deployed rdo-manager in a virt env and everything is<br>
working fine<br>
except the vnc console which is alreday an open bug for that.<br>
<br>
Now I would like to change some parameters on my deployment,<br>
let's say I<br>
wan't to disable NeutronTunneling, I wan't to use VLAN for<br>
tenants and<br>
use 1500 MTU on dnsmasq.<br>
<br>
So I downloaded the plan:<br>
<br>
#tuskar plan-templates -O /tmp uuid<br>
<br>
changed plan.yaml, environment.yaml, provider-Controller-1.yaml,<br>
provider-Compute-1.yaml.<br>
<br>
than I ran the stack:<br>
<br>
# heat stack-create -f tmp/plan.yaml -e tmp/environment.yaml<br>
overcloud<br>
<br>
The overcloud is deployed fine but the values aren't<br>
changed. What I'm<br>
missing here?<br>
<br>
<br>
hi,<br>
<br>
if you launch stack-create manually the newly created overcloud<br>
is not reprovisioned with the initial keystone<br>
endpoints/users/roles ... to get an usable overcloud you should<br>
launch instack-deploy-overcloud again<br>
<br>
so you can change the defaults for the various params by<br>
patching the tuskar plan with 'tuskar plan-update' see [1]<br>
<br>
yet some of these are automatically parsed from ENV vars, like<br>
NEUTRON_TUNNEL_TYPES and NEUTRON_NETWORK_TYPE see [2]<br>
<br>
the NeutronDnsmasqOptions param instead is not parsed from any<br>
ENV var, so you're forced to use 'tuskar plan-update'<br>
<br>
I'm adding a couple of guys on CC who migh help but, let us know<br>
how it goes!<br>
<br>
1.<br>
<a href="https://github.com/rdo-management/instack-undercloud/blob/master/scripts/instack-deploy-overcloud#L274" target="_blank">https://github.com/rdo-management/instack-undercloud/blob/master/scripts/instack-deploy-overcloud#L274</a><br>
<br>
2.<br>
<a href="https://github.com/rdo-management/instack-undercloud/blob/master/scripts/instack-deploy-overcloud#L205-L208" target="_blank">https://github.com/rdo-management/instack-undercloud/blob/master/scripts/instack-deploy-overcloud#L205-L208</a><br>
--<br>
Giulio Fidente<br>
GPG KEY: 08D733BA<br>
<br>
<br>
<br>
<br>
<br></div></div><span class="">
_______________________________________________<br>
Rdo-list mailing list<br>
<a href="mailto:Rdo-list@redhat.com" target="_blank">Rdo-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/rdo-list" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
<br>
To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com" target="_blank">rdo-list-unsubscribe@redhat.com</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
_______________________________________________<br>
Rdo-list mailing list<br>
<a href="mailto:Rdo-list@redhat.com" target="_blank">Rdo-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/rdo-list" target="_blank">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
<br>
To unsubscribe: <a href="mailto:rdo-list-unsubscribe@redhat.com" target="_blank">rdo-list-unsubscribe@redhat.com</a><br>
</div></div></blockquote></div><br></div>