Hide Forgot
Pursuant to the Red Hat Insights for OpenStack offering, the Insights team would like to have the the redhat-access-insights client RPM[1] included by default on the RHOS overcloud image (overcloud-full.qcow2)so that we can begin monitoring RHOS installations with Insights. The redhat-access-insights RPM[1] delivers some python code (the Insights client[2]) which collects various logs and other information that we analyze at Red Hat and use to alert customers to potential problems. On average, this information is about 100kb (much much smaller than a SoS report). The insights client will not spawn any persistent tasks or processes. An external program will invoke the program (redhat-insights-coordinator-rhos[3]) over SSH, the output will be sent to STDOUT, any artifacts will be cleaned up, and the connection will be closed. Specifically, this BZ requests that the redhat-access-insights client RPM be included by default on all overcloud images. [1] https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=489175 [2] https://github.com/redhataccess/insights-client [3] https://gitlab.cee.redhat.com/proactive-support/insights-coordinator-rhosp
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Based on discussions with Keith R., there is request to only include rpm into the overcloud images - no configuration, heat templates or puppet functionality is needed. This is approved by PM. This needs a QE testing coverage to make sure that enabled Insights don't break any OSP functionality. There will be cooperation with Insight's QE. Thanks -- Jarda
Upstream we have a new tool called tripleo-build-images that lives in tripleo-common. Instead of hard coding the package names into python-tripleoclient this tool is YAML driven and can merge values from multiple config files: $tripleo-build-images --help.... Image build options: --image-config-file IMAGE_CONFIG_FILE Path to configuration file. Can be specified multiple times --image-noskip The inverse of --skip --image-output-directory IMAGE_OUTPUT_DIRECTORY output directory for images. Defaults to $TRIPLEO_ROOT, or current directory --image-skip Skip build if cached image exists. ---- So for product things like this we could go with a layered approach where we build overcloud images by layering the relevant distro and overcloud YAML files from : http://git.openstack.org/cgit/openstack/tripleo-common/tree/image-yaml and then downstream we can also add in other "extra" files as well. How does this sound? We really need to move towards using tripleo-build-images as soon as possible.
Verified on OSP 9.0 GA (0-day puddle), the RPM does exist on the overcloud post deployment of overcloud: [root@overcloud-controller-0 ~]# rpm -qa | grep insights redhat-access-insights-1.0.6-0.el7.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://rhn.redhat.com/errata/RHEA-2016-1762.html