On Fri, Sep 11, 2015 at 5:43 PM, Fabian Deutsch <[email protected]> wrote:
> Hey, > > I'd like to make it easier to discover what oVirt release is > installed, and what potential variant (i.e Node) is used. > Currently we are using some Node specific files to identify this "variant". > > With this patch [0] I'm suggesting to add the /etc/ovirt-release file, > with the following contents: > > NAME=oVirt > ID=ovirt > VERSION="4.0 (master)" > VERSION_ID=4.0 > PRETTY_NAME="oVirt 4.0" > CPE_NAME="cpe:/a:ovirtproject:ovirt:4.0:dev" > VARIANT="" > VARIANT_ID= > > The variables are close to what is used by Fedora and CentOS. > The variant field is left empty by default, but can be populated with > defined values for variants like Node or i.e. a container variant. > what if multiple ovirt-releaseX are installed? for example, upgrading from 3.5 to 3.6 keeping rollback support during the upgrade requires to have ovirt-release35 and ovirt-release36 installed side by side. > > A CPE [1] is also included for convenience. > > Thoughts? > > - fabian > > -- > [0] https://gerrit.ovirt.org/#/c/46067/ > [1] http://cpe.mitre.org/ > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
