[openstack-dev] [murano] Berkshelf/Chef/Puppet installation on Murano images
Hi all, Some months ago, I started to work on a Murano integration with Berkshelf [1] to manage Chef cookbooks dependencies when Murano deploys a Chef cookbook (cf spec [2]). The main work is in murano-agent and was merged in last November [3]. However, I still haven't finalize the work with the integration tests (review on hold [4]) because it requires having Berkshelf installed on the image (and the latest murano-agent). I still wonder what is the best way to install Berkshelf. Currently, Chef and Puppet are installed along with Murano agent in the DIB elements [5] However, the murano-apps examples using Chef and Puppet contain additional DIB elements to install Chef/Puppet [6]; I suppose they aren't needed anymore. Of course, we can install Berkshelf in Murano agent DIB elements. But do we really want this additional software coming up in Murano images even if neither Berkshelf nor Chef is used? An other solution is to install Berkshelf at runtime using cloud-init, like Henar Muñoz did for Chef and Puppet last month [7]. However, I'm a little bit confused by all these solutions. Is there a recommended solution? And which solution should I use to make my functional tests work [4]? One more thing: the recommended way to install Berkshelf is now to use ChefDK (Chef Development Kit), which includes multiple tools [8]. An Ubuntu image with murano-agent installed with DIB elements (including Chef & Puppet) is 438 MB. If I add ChefDK, the image is 794 MB... It is possible to install Berkshelf only using Ruby gems [9] but it's not the recommended way. Any thought? [1] http://berkshelf.com/ [2] http://murano-specs.readthedocs.org/en/latest/specs/mitaka/support-chef-berkshelf.html [3] https://review.openstack.org/#/c/240808/ [4] https://review.openstack.org/#/c/248027/ [5] https://github.com/openstack/murano-agent/blob/master/contrib/elements/murano-agent/install.d/74-murano-agent#L5 [6] https://github.com/openstack/murano-apps/tree/master/Chef/GitChef/elements [7] https://review.openstack.org/#/c/230381/16 [8] https://downloads.chef.io/chef-dk/ [9] https://rubygems.org/gems/berkshelf -- Olivier Lemasle Software Engineer *Apalia*™ Mobile: +33-611-69-12-11 *http://www.apalia.net <http://www.apalia.net> <olivier.lema...@apalia.net>olivier.lema...@apalia.net <olivier.lema...@apalia.net>* __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [murano] Visibility consistency for packages and images
Hi all, Ekaterina Chernova suggested last week to discuss the matter of visibility consistency for murano packages and glance images, following my bug report on that subject [1]. The general idea is to make sure that if a murano package is public, it should be really available for all projects, which mean that: - if it depends on other murano packages, these packages must be public, - if it depends on glance images, these images must be public. In fact, I created this bug report after Alexander Tivelkov's suggesion on a review request [2] I did to fix a related bug [3]. In this other bug report, I focused on images visibility during the initial import of a package, because dependant murano packages are already imported with the same visibility. It seemed to me most confusing that packages are made public if the images are private. So I did a fix in murano-dashboard, which is already merged [4], and another one for python-muranoclient, still in review ([2]). What are your thoughts on this subject? Do we need to address first the general dependency issue? Is this a murano, glance or glare subject? Do we still need to do something specific for the initial import (currently, dependency resolution for packages and images is done both in murano-dashboard and in python-muranoclient)? Thank you for your inputs, [1] https://bugs.launchpad.net/murano/+bug/1509208 [2] https://review.openstack.org/#/c/236834/ [3] https://bugs.launchpad.net/murano/+bug/1507139 [4] https://review.openstack.org/#/c/236830/ -- Olivier Lemasle Software Engineer Apalia™ Mobile: +33-611-69-12-11 http://www.apalia.net olivier.lema...@apalia.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
