From da4755e01dcea6d030602a6f614b31a84bd86e38 Mon Sep 17 00:00:00 2001 From: Erwan Velu Date: Mon, 30 Apr 2018 18:02:05 +0200 Subject: [PATCH] rhel7: Adding content_sets.yml This is a file defining which content sets (yum repositories) are needed to update content in this image. Data provided here helps determine which images are vulnerable to specific CVEs. Co-Authored-By: Ken Dreyer Signed-off-by: Erwan Velu --- .../ALL/rhel7/daemon-base/content_sets.yml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 ceph-releases/ALL/rhel7/daemon-base/content_sets.yml diff --git a/ceph-releases/ALL/rhel7/daemon-base/content_sets.yml b/ceph-releases/ALL/rhel7/daemon-base/content_sets.yml new file mode 100644 index 000000000..a2a7b4918 --- /dev/null +++ b/ceph-releases/ALL/rhel7/daemon-base/content_sets.yml @@ -0,0 +1,19 @@ +# This is a file defining which content sets (yum repositories) are needed to +# update content in this image. Data provided here helps determine which images +# are vulnerable to specific CVEs. Generally you should only need to update this +# file when: +# 1. You start depending on a new product +# 2. You are preparing new product release and your content sets will change +# +# See https://mojo.redhat.com/docs/DOC-1023066 for more information on +# maintaining this file and the format and examples +# +# You should have one top level item for each architecture being built. Most +# likely this will be x86_64 and ppc64le initially. +--- +x86_64: +- rhel-7-server-rpms +- rhel-7-server-extras-rpms +- rhel-7-server-rhceph-3-tools-rpms +- rhel-7-server-rhceph-3-mon-rpms +- rhel-7-server-rhceph-3-osd-rpms