In a similar way of what's done on openSUSE and Fedora, let's have an "unknown" entry for CaaSP that would cover any possible future release while the proper release is not added to our db. Signed-off-by: Fabiano Fidêncio <fidencio@xxxxxxxxxx> --- Already pushed as trivial/build fix. --- data/os/suse.com/caasp-unknown.xml.in | 37 +++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 data/os/suse.com/caasp-unknown.xml.in diff --git a/data/os/suse.com/caasp-unknown.xml.in b/data/os/suse.com/caasp-unknown.xml.in new file mode 100644 index 0000000..363c55a --- /dev/null +++ b/data/os/suse.com/caasp-unknown.xml.in @@ -0,0 +1,37 @@ +<libosinfo version="0.0.1"> +<!-- Licensed under the GNU General Public License version 2 or later. + See http://www.gnu.org/licenses/ for a copy of the license text --> + <os id="http://suse.com/caasp/unknown";> + <short-id>caasp-unknown</short-id> + <_name>SUSE CaaS Platform Unknown</_name> + <version>unknown</version> + <_vendor>SUSE</_vendor> + <vendor xml:lang="fr">SUSE</vendor> + <family>linux</family> + <distro>caasp</distro> + <upgrades id="http://suse.com/caasp/3.0"/> + <derives-from id="http://suse.com/caasp/3.0"/> + + <media arch="x86_64"> + <iso> + <system-id>LINUX</system-id> + <volume-id>SUSE-CaaS-Platform-([4-9]|[1-9][0-9]).0-DVD-x86_64.*</volume-id> + </iso> + <kernel>boot/x86_64/loader/linux</kernel> + <initrd>boot/x86_64/loader/initrd</initrd> + </media> + + <resources arch="all"> + <minimum> + <cpu>500000000</cpu> + <ram>2147483648</ram> + <storage>21474836480</storage> + </minimum> + <recommended> + <cpu>2400000000</cpu> + <ram>8589934592</ram> + <storage>42949672960</storage> + </recommended> + </resources> + </os> +</libosinfo> -- 2.19.1 _______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
