Hi devs! During the OpenContrail days (in marge of Vancouver OpenStack summit), we talked about the Juniper/contrail-puppet¹ module, some of puppet deployers said they rewrite from ground this module for multiples reasons (style non compliant with others modules, mostly assimilated to a composition layer²³, a plenty of execs for all resources, i dont remember other points :p).
¹https://github.com/Juniper/contrail-puppet ²https://github.com/Juniper/contrail-puppet/tree/master/contrail/environment/modules/contrail ³https://github.com/Juniper/contrail-puppet/issues/24 Some puppeters said they would publish their modules, but nothing has changed⁴ (or it's not on Github 0:-)) ⁴https://github.com/search?utf8=✓&q=contrail+puppet So we decided at eNovance/RedHat to rewrite the module, using type/provider for ini configuration (as it's made in other puppetlabs and openstack modules), and also to minimizing use of exec resource as much as possible, get a directory and file structure as puppetlabs recommend (with unit and tests), and finally configure only contrail, and let the composition layer do the rest of the job. Our work is available on Github, here⁵, feel free to take a look. ⁵https://github.com/enovance/puppet-contrail And our composition layer, is available on StackForge⁶⁷ (OpenStack) ⁶https://github.com/stackforge/puppet-openstack-cloud ⁷https://github.com/stackforge/puppet-openstack-cloud/tree/master/manifests/network/contrail Ps: This module is used in production (for the moment only on RedHat, and with the contrail packages) but we plan to support also opencontrail and other distro :-) Feel free to contribute, and as an effort to the community if you want to migrate this module under Juniper namespace, it's also possible for us. Yanis and Seb -- Sebastien Badia
signature.asc
Description: Digital signature
_______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
