Not really. Just bring some stuff up. Even if the routers are messed up the
compute instances won't get hurt.
The snat stuff sounds right.
On Sep 25, 2017 2:45 PM, "Turbo Fredriksson" wrote:
On 21 Sep 2017, at 04:45, Kevin Benton wrote:
> If you wanted to do it purely with an SQL hack you mig
Thanks for explain Jeremy! Very clear.
I think systems with cloud-init enabled, like most images, can be easily
configured to disable this feature.
Thank you!
:)
> On 28 Sep 2017, at 21:37, Jeremy Stanley wrote:
>
> On 2017-09-28 20:29:38 -0300 (-0300), Jorge Luiz Correa wrote:
>> It would
On 2017-09-28 20:29:38 -0300 (-0300), Jorge Luiz Correa wrote:
> It would be good if developers could know about that because
> privacy extension is becoming the default on every operate
> systems. I've tested last version of *ubuntu and some FreeBSD
> kernels, all operating with privacy extension
Nice!
It would be good if developers could know about that because privacy extension
is becoming the default on every operate systems. I've tested last version of
*ubuntu and some FreeBSD kernels, all operating with privacy extension by
default.
So, this way of creating the iptables rules nee
I really appreciate your help Jorge and David!
After far to many hours of troubleshooting the root cause ended up being
caused by the IPv6 Privacy Extensions (RFC 4941) that is on with Windows by
default... Had I mentioned these issues were happening on a Windows
instance, you guys would have undo
I ran "fuel2 node update -H blade13 20" just to get out of the node-*
naming convention, as someone suggested
The deploy still names the node node-11 and provisioning fails.
digging a little more, i see it might have to do with the fuel-agent
cloud-init scripts.
in the cloud-init.log on the n
On 28/09/17 17:06, Kim-Norman Sahm wrote:
> Hi,
>
> i'm currently testing designate and i have a question about the
> architecture.
> We're using openstack newton with keystone v3 and thus the keystone
> domain/project structure.
>
> I've tried the global nova_fixed and neutron_floating_ip hand
Hi,
i'm currently testing designate and i have a question about the architecture.
We're using openstack newton with keystone v3 and thus the keystone
domain/project structure.
I've tried the global nova_fixed and neutron_floating_ip handlers but all dns
records (for each domains/projects) are
