Looks good to me.
Rob
On 9/8/15, 4:40 AM, "Steven Hardy" wrote:
>Hi all,
>
>So, lately we're seeing an increasing number of patches adding integration
>for various third-party plugins, such as different neutron and cinder
>backends.
>
>This is great to see, but it also poses the question of h
I like where this is going. I've been asked a number of times where to
put things and we never had a solid convention. I like the idea of
having that docced somewhere.
I like either of the proposed solutions. My biggest concern is that they
don't capture how you actually use them. I know that
On 8.9.2015 13:47, Jiří Stránský wrote:
Apart from "cinder" and "neutron-ml2" directories, we could also have a
"combined" (or sth similar) directory for env files which combine
multiple other env files. The use case which i see is for extra
pre-deployment configs which would be commonly used tog
On 8.9.2015 10:40, Steven Hardy wrote:
Hi all,
So, lately we're seeing an increasing number of patches adding integration
for various third-party plugins, such as different neutron and cinder
backends.
This is great to see, but it also poses the question of how we organize the
user-visible inte
Hi all,
So, lately we're seeing an increasing number of patches adding integration
for various third-party plugins, such as different neutron and cinder
backends.
This is great to see, but it also poses the question of how we organize the
user-visible interfaces to these things long term.
Origin
