[openstack-dev] [Neutron] Multiple template libraries being used in tree
Mike Bayer
mbayer at redhat.com
Tue Feb 3 01:43:41 UTC 2015
Sean Dague <sean at dague.net> wrote:
> On 02/02/2015 06:06 PM, Mike Bayer wrote:
>> Sean Dague <sean at dague.net> wrote:
>>
>>> On 02/02/2015 04:20 PM, Mark McClain wrote:
>>>> You’re right that the Mako dependency is really a side effect from Alembic. We used jinja for tempting radvd because it is used by the projects within the OpenStack ecosystem and also used in VPNaaS.
>>>
>>> Jinja is far more used in other parts of OpenStack from my recollection,
>>> I think that's probably the prefered thing to consolidate on.
>>>
>>> Alembic being different is fine, it's a dependent library.
>>
>>
>> there’s no reason not to have both installed. Tempita also gets installed with a typical openstack setup.
>>
>> that said, if you use Mako, you get the creator of Mako on board to help as he already works for openstack, for free!
>
> Sure, but the point is that it would be better to have the OpenStack
> code be consistent in this regard, as it makes for a more smooth
> environment.
stick with Jinja if that’s what projects are already using.
More information about the OpenStack-dev
mailing list