Description of problem: The Sahara data processing project for OpenStack requires the usage of virtual machine images that are purpose constructed. Although a selection of images can be found through the Sahara documentation, the power to create new images is contained within the sahara-image-elements project. This project contains a diskimage-builder script and several elements files to inform construction of the Sahara images. Currently there is no official source for sahara-image-elements within Red Hat OpenStack. This package should contain the upstream sahara-image-elements[1], and provide a script to facilitate the image creation. There are several factors to consider when packaging sahara-image-elements, primarily that diskimage-builder will attempt to modify the locally installed packages during it execution, also in it's current form the image creation scripts must be run as the root user. The script provided in this package should address these issues and ensure that the host system is not damaged or permanently modified after execution. [1]: https://github.com/openstack/sahara-image-elements
sahara-image-elements-2015.1.0-2.el7ost corrects several minor issues in the original build: 1) option oracle-java is both nonfunctional and unpackaged; this version removes -j option and always uses openjdk. 2) -x option added to enable trace debugging.
The package is available in RHEL-OSP7 (it was already available in RHEL-OSP6). The sahara-disk-image-create script has been updated and can generate images for the plugins/versions enabled in this release: HDP 2.0.6 and CDH 5.3.0. The generated images pass scenario integration tests for Sahara. Verified with: sahara-image-elements-2015.1.0-3.el7ost.noarch Sahara packages used by the cluster and for testing purpose: openstack-sahara-common-2015.1.0-4.el7ost.noarch openstack-sahara-engine-2015.1.0-4.el7ost.noarch openstack-sahara-api-2015.1.0-4.el7ost.noarch python-saharaclient-0.9.0-1.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1548