[openstack-dev] [Fuel] [plugins] A simple network to interface mapping in astute.yaml

Evgeniy L eli at mirantis.com
Thu Feb 26 17:24:21 UTC 2015


Hi Andrey,

I don't have enough details to make some conclusions, but if the
problem can be solved with some python script which gets the data
and converts it into more readable format, lets do it this way.

Thanks,

On Wed, Feb 25, 2015 at 10:59 PM, Andrey Danin <adanin at mirantis.com> wrote:

> Hi, fuelers,
>
> As you may know, we have a rich and complex network_transformations
> section in astute.yaml. We use it to describe which OVS/Linux network
> primitives should be created and how they should be connected together.
> This section is used by "l23network" Puppet module during the deployment
> stage.
>
> The problem is that from plugin developer's stand point it's hard to parse
> a full transformation graph to find which interface/vlan is used for each
> network (Public, Private, etc.). I see two ways to fix that.
>
> 1) Add a new structure to astute.yaml with a simple mapping of networks to
> interfaces/vlans. Example: http://paste.openstack.org/show/181466/ (see
> roles_meta section).
> Pros: it's very easy for plugin developers.
> Cons: there are two sources of truth (roles_meta and transformations). If
> one plugin patch transformations but forget to patch roles_meta, another
> plugin, which relies on roles_meta, fails the deployment.
>
> 2) Provide a some kind of SDK - functions/libraries for
> Puppet/Python/Bash, which can be used in plugin's tasks to operate with
> graph of transformations.
> Pros: single point of truth. One and controlled way to do things right.
> Cons: a new piece of software will be issued. It must be written, tested,
> documented, and incorporated into CI/CD infrastructure.
>
>
> I prefer the second way. Do you?
>
> --
> Andrey Danin
> adanin at mirantis.com
> skype: gcon.monolake
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150226/2a794a59/attachment.html>


More information about the OpenStack-dev mailing list