Hi Felipe,
thanks for your reply.
I now forced the values to be strings (like you suggested), but it’s still
being ignored… I still wonder where the actual value is coming from. The config
options does not seem to have a default (at least not documented). I’m using
the lxd provider.
Any other idea?
Thanks!
---
Andreas Scheuring (andreas_s)
On 30. Nov 2017, at 12:39, Felipe Reyes <felipe.re...@canonical.com> wrote:
Hi Andreas,
On Thu, Nov 30, 2017 at 09:50:31AM +0100, Andreas Scheuring wrote:
> Hi,
> I’m working on deploying a juju based OpenStack Pike. I’m using the bundle
> [1]. In this bundle I’m setting the config options
> * bridge-mappings: provider:br-provider physnet1:br-ex
> * data-port: br-provider:eth2 br-ex:eth
>
> But for some reason those values do not get applied. Some other values are
> set instead (no clue where those are coming from):
The format is not correct, those options are strings and the presence of the
colons is confusing the yaml parser, force the values to be interpreted as
strings like this:
bridge-mappings: "provider:br-provider physnet1:br-ex"
data-port: "br-provider:eth2 br-ex:eth1"
Best,
PS: this mailing list is deprecated, please use the OpenStack development
mailing list or the operators one, more details at
https://docs.openstack.org/charm-guide/latest/mailing-list.html
--
Felipe Reyes
# Email: felipe.re...@canonical.com (GPG:0x9B1FFF39)
# Launchpad: ~freyes | IRC: freyes
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
