Bug 1042133 - [RFE][oslo]: Support for distro release information
Summary: [RFE][oslo]: Support for distro release information
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/oslo...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:07 UTC by RHOS Integration
Modified: 2015-03-19 16:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 16:51:03 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 21:07:33 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/distro-release-info.

Description:

Nova has support for an /etc/nova/release file which, in Red Hat packaging, contains e.g.

 [Nova]
 vendor = Red Hat Inc.
 product = OpenStack Nova
 package = 1.el6

This was introduced by https://review.openstack.org/18082

It would make sense for all projects to use this

One place this could live is pbr.

The only sticking point is we use ConfigOpts.find_file() to locate the release file. The main reason for this is because cfg knows the project name, so it knows to look in /etc/${project} ... but pbr knows this too.

However, if you do e.g. --config-file /tmp/nova.conf it will also look in /tmp. It's this latter behaviour we'd lose by not using cfg, but it doesn't seem essential either.

Specification URL (additional information):

None
Note You need to log in before you can comment on or make changes to this bug.