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

2015-02-26 Thread Aviram Bar Haim
Hi Andrey, IMO the first choice (adding a new structure) is better because of the following reasons: 1. The only source of truth for the networks allocations by the user can be the new roles_meta structure, while transformations can be changed in future versions or by plugins, according

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

2015-02-26 Thread Evgeniy L
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 ada...@mirantis.com wrote: Hi,

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

2015-02-25 Thread Andrey Danin
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