Red Hat Enterprise Linux
OpenStack Platform Certification
1.0
Policy Guide
The Policies and Procedures of Certification
Sankarshan MukhopadhyayHugo Rivero
Red Hat Enterprise Linux OpenStack Platform Certification 1.0 Policy
Guide
The Policies and Procedures of Certification
Sankarshan Mukhopadhyay
[e-mail]
Hugo Rivero
[e-mail]
Legal Notice
Copyright © 2014 Red Hat.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported
License. If you distribute this document, or a modified version of it, you must provide attribution to Red
Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be
removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section
4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo,
and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.
Java ® is a registered trademark of Oracle and/or its affiliates.
XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States
and/or other countries.
MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other
countries.
Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or
endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/service marks or
trademarks/service marks of the OpenStack Foundation, in the United States and other countries and
are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or
sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Abstract
The Red Hat Enterprise Linux Hardware Certification Program Policy Guide covers the procedural,
technical and policy requirements for achieving Red Hat Enterprise Linux Hardware Certification.
Table of Contents
Table of Contents
. . . face 2
Pre. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`
1. Document Conventions 2
`
1.1. Typographic Conventions 2
`
1.2. Pull-quote Conventions 3
`
1.3. Notes and Warnings 4
`
2. Getting Help and Giving Feedback 4
`
2.1. Do You Need Help? 4
`
2.2. We Need Feedback! 5
` . . pt r 1. O.ve. .view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.ha. . .e. . . . . . r . . . 6
` . . pt r 2. C.e.r. . . . . . . . . . . . . . . . 7
C.ha. . .e. . . . . tification Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` . . pt r 3. Product . . . . . . . . . . 8
C.ha. . .e. . . . . . . . . . . .Require.me.nts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` . . pt r 4 . Life.cycle. . . . tifica. . . . 9
C.ha. . .e. . . . . . . . . . . of C.e.r. . . . tion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` . . pt r 5. C.e.r. . . . . . . . . . . . . . . . . . . . s 10
C.ha. . .e. . . . . tification Policy Cha.nge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
` . . pt r 6. Exce.pt. . . . 11
C.ha. . .e. . . . . . . . . ions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. tification Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.e.r. . . . . . . . . . . . . 12
. . . . . . . . . . . . . 13
Re.vision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
Red Hat Enterprise Linux OpenStack Platform Certification 1.0 Policy Guide
Preface
1. Document Conventions
This manual uses several conventions to highlight certain words and phrases and draw attention to
specific pieces of information.
In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation
Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but
equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later include the Liberation Fonts
set by default.
1.1. Typographic Conventions
Four typographic conventions are used to call attention to specific words and phrases. These
conventions, and the circumstances they apply to, are as follows.
Mono-spaced Bold
Used to highlight system input, including shell commands, file names and paths. Also used to highlight
keys and key combinations. For example:
To see the contents of the file my_next_bestselling_novel in your current working
directory, enter the cat m y_next_bestselling_novel command at the shell prompt and
press Enter to execute the command.
The above includes a file name, a shell command and a key, all presented in mono-spaced bold and all
distinguishable thanks to context.
Key combinations can be distinguished from an individual key by the plus sign that connects each part of a
key combination. For example:
Press Enter to execute the command.
Press Ctrl+Alt+F2 to switch to a virtual terminal.
The first example highlights a particular key to press. The second example highlights a key combination: a
set of three keys pressed simultaneously.
If source code is discussed, class names, methods, functions, variable names and returned values
mentioned within a paragraph will be presented as above, in mono-spaced bold. For example:
File-related classes include filesystem for file systems, file for files, and dir for
directories. Each class has its own associated set of permissions.
Proportional Bold
This denotes words or phrases encountered on a system, including application names; dialog-box text;
labeled buttons; check-box and radio-button labels; menu titles and submenu titles. For example:
Choose System Preferences Mouse from the main menu bar to launch Mouse
Preferences. In the Buttons tab, select the Left-handed mouse check box and click
Close to switch the primary mouse button from the left to the right (making the mouse
suitable for use in the left hand).
To insert a special character into a gedit file, choose Applications Accessories
2
Preface
Character Map from the main menu bar. Next, choose Search Find& from the
Character Map menu bar, type the name of the character in the Search field and click
Next. The character you sought will be highlighted in the Character Table. Double-click
this highlighted character to place it in the Text to copy field and then click the Copy
button. Now switch back to your document and choose Edit Paste from the gedit menu
bar.
The above text includes application names; system-wide menu names and items; application-specific
menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all
distinguishable by context.
Mono-spaced Bold Italic or Proportional Bold Italic
Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable
text. Italics denotes text you do not input literally or displayed text that changes depending on
circumstance. For example:
To connect to a remote machine using ssh, type ssh [e-mail] at a shell
prompt. If the remote machine is example.com and your username on that machine is john,
type ssh [e-mail].
The mount -o remount file-system command remounts the named file system. For
example, to remount the /home file system, the command is mount -o remount /home.
To see the version of a currently installed package, use the rpm -q package command. It
will return a result as follows: package-version-release.
Note the words in bold italics above: username, domain.name, file-system, package, version and release.
Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the
system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and
important term. For example:
Publican is a DocBook publishing system.
1.2. Pull-quote Conventions
Terminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in mono-spaced roman and presented thus:
books Desktop documentation drafts mss photos stuff svn
books_tests Desktop1 downloads images notes scripts svgs
Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows:
3
Red Hat Enterprise Linux OpenStack Platform Certification 1.0 Policy Guide
static int kvm_vm_ioctl_deassign_device(struct kvm *kvm,
struct kvm_assigned_pci_dev *assigned_dev)
{
int r = 0;
struct kvm_assigned_dev_kernel *match;
mutex_lock(&kvm->lock);
match = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head,
assigned_dev->assigned_dev_id);
if (!match) {
printk(KERN_INFO "%s: device hasn't been assigned before, "
"so cannot be deassigned\n", __func__);
r = -EINVAL;
goto out;
}
kvm_deassign_device(kvm, match);
kvm_free_assigned_device(kvm, match);
out:
mutex_unlock(&kvm->lock);
return r;
}
1.3. Notes and Warnings
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
Note
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have
no negative consequences, but you might miss out on a trick that makes your life easier.
Important
Important boxes detail things that are easily missed: configuration changes that only apply to the
current session, or services that need restarting before an update will apply. Ignoring a box labeled
 Important will not cause data loss but may cause irritation and frustration.
Warning
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
2. Getting Help and Giving Feedback
2.1. Do You Need Help?
4
Preface
If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer
Portal at http://access.redhat.com. Through the customer portal, you can:
search or browse through a knowledgebase of technical support articles about Red Hat products.
submit a support case to Red Hat Global Support Services (GSS).
access other product documentation.
Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and
technology. You can find a list of publicly available mailing lists at https://www.redhat.com/mailman/listinfo.
Click on the name of any mailing list to subscribe to that list or to access the list archives.
2.2. We Need Feedback!
If you find a typographical error in this manual, or if you have thought of a way to make this manual better,
we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/ against the
product Red Hat Enterprise Linux OpenStack Platform Certification.
When submitting a bug report, be sure to mention the manual's identifier: Policy_Guide
If you have a suggestion for improving the documentation, try to be as specific as possible when
describing it. If you have found an error, please include the section number and some of the surrounding
text so we can find it easily.
5
Red Hat Enterprise Linux OpenStack Platform Certification 1.0 Policy Guide
Chapter 1. Overview
The Red Hat Enterprise Linux OpenStack Platform Certification is a formal program introduced by Red Hat
to certify partners' products that deliver OpenStack services. It offers customers assurance that a specific
OpenStack solution has been tested and is fully supported by Red Hat and Red Hat's partners.
The primary focus of the certification program is to validate components that implement OpenStack APIs,
such as Networking (Neutron) plugins or Block Storage (Cinder) drivers. Certification of other type of
OpenStack software is available on a case-by-case basis, and must be requested directly to openstack-
[e-mail].
Red Hat also offers certification for Hardware, and systems capable of running Red Hat OpenStack
technology are listed in the catalog. Hardware partners interested in pursuing this option should consult
the Red Hat Hardware Certification Policy Guide. The rest of this document covers software certification ,
and provides details about the process and policies.
Through the Certification process, Red Hat OpenStack partners receive a number of benefits:
Access to every release of Red Hat Enterprise Linux OpenStack Platform, including access to pre-
released software
Developer support
Listing on Red Hat's Marketplace
Promotion through Marketing and Sales campaigns
Greater exposure to Red Hat Sales, and to Channel Partners
Partner's product information is shared with Red Hat's Global Support organization, facilitating problem
resolution for joint customers
PRE-REQUISITES
To pursue a certification, a vendor must:
Be a member of the Red Hat OpenStack Cloud Infrastructure Partner Network. To inquire about this
partner program, send an email to [e-mail].
Have a support relationship with Red Hat. This can be fulfilled through the multi-vendor support
network of TSANet, or through a custom support agreement.
The vendor must have a solid working knowledge of Red Hat Enterprise Linux OpenStack Platform, and be
familiar with the installation and configuration process . Detailed product documentation is published on the
Customer Portal, and OpenStack courses are also available from Red Hat Training.
Report a bug
6
`
Chapter 2. Certification Process
Chapter 2. Certification Process
Partners are responsible for executing the certification tests. The steps for this process are outlined
below.
1. Partner informs the intent to certify through an email to [e-mail] ,
including the following information :
Partner name
Partner certification contact
Product name and version
Product overview
Link to product documentation
Link to download for software product, if not already included in OpenStack
List of all dependencies that are not included in Red Hat Enterprise Linux OpenStack Platform
2. Red Hat grants partner access to the software needed for testing.
To assist with testing, Red Hat has developed a certification test tool, called rhoscts. This tool
contains a series of tests that assess how the software-under-test consumes and makes use of
the OpenStack APIs on Red Hat Enterprise Linux OpenStack Platform. For Red Hat Enterprise Linux
OpenStack Platform 4, rhoscts covers the Neutron and Cinder APIs.
Partners pursuing certification of Neutron plugins or Cinder drivers would use of this tool, and follow
the steps specified in the User Guide.
Partners pursuing Certification of products implementing other OpenStack APIs will contact Red Hat
for information on the test plan specific to their OpenStack service.
3. Partner executes the certification tests in their own premises, and submits the results to Red Hat for
review. If any issues are identified, Red Hat and partner's designated contact collaborate to resolve
them in a timely manner.
4. Partner documents and publishes any installation and configuration steps that are specific to Red
Hat Enterprise Linux OpenStack Platform.
5. Once the review is completed, Red Hat will create a certification page on the Red Hat Marketplace,
allowing the partner to review the listing before its publication.
Report a bug
7
Red Hat Enterprise Linux OpenStack Platform Certification 1.0 Policy Guide
Chapter 3. Product Requirements
The product to be certified must comply with the following criteria:
If the software under test is not already included in the OpenStack platform, it must be generally
available by the time the certification is published. The version available to customers must match the
version that was certified.
Software-under-test must not override or modify any packages, system services or security profiles
available as part of the release of Red Hat Enterprise Linux OpenStack Platform. provided by Red Hat
Enterprise Linux OpenStack Platform
Any additional package repositories that are required to be added to an installation of Red Hat
Enterprise Linux OpenStack Platform should be specifically identified and described.
The packages/dependencies provided by such non-Red Hat package repositories cannot contravene
the criteria listed in the second point above.
Packages/dependencies required for complete functionality of the product, if not already provided for by
the Red Hat Enterprise Linux OpenStack Platform, will be subject to Red Hat's policies on third-party
software as documented at https://access.redhat.com/site/articles/1067.
Such packages/dependencies described in the previous point shall be distributed by the partner,
preferably through an RPM package repository. Instructions for downloading, installing and
configuration is also required to be provided.
Report a bug
8
`
Chapter 4. Lifecycle of Certification
Chapter 4. Lifecycle of Certification
Certifications are specific to a major release of Red Hat Enterprise Linux OpenStack Platform, and are
considered compatible with all subsequent minor releases/updates of that version. Partners are expected
to go through the certification process upon every major product release, which correspond to the
upstream OpenStack releases every 6 months.
Partners indicate the specific version of their software being certified. It is their responsibility to resubmit
results for review, when changes in their own product  such as a new major release or a significant
feature or functionality change - warrant additional testing.
Partners may have access to pre-released software and may begin their engagement with the Certification
team before the Red Hat software is generally available to customers, to expedite the process. However,
final tests must be conducted on the released packages.
Red Hat will accept certification requests on a given Red Hat Enterprise Linux OpenStack Platform version
(release "N") for up to 90 days after a new version ( release "N+1") is generally available . An EOL
notification will be sent to partners participating in the program.
For information on the release and end-of-support dates for Red Hat OpenStack technology, see the
Platform Life Cycle document.
Report a bug
9
Red Hat Enterprise Linux OpenStack Platform Certification 1.0 Policy Guide
Chapter 5. Certification Policy Changes
The current policy is effective upon its release and immediately supersedes all previous versions.
Changes to the policy or criteria will be sent as an email notification to the designated partner contacts. All
certifications are subject to the definition and terms of the current policy.
Report a bug
10
`
Chapter 6. Exceptions
Chapter 6. Exceptions
Exceptions or waivers on a specific policy item may be requested to [e-mail],
and will be granted at the sole discretion of Red Hat.
Report a bug
11
Red Hat Enterprise Linux OpenStack Platform Certification 1.0 Policy Guide
Certification Form
To complete the certification process, partners must complete this information.
1. a. Partner name
b. Partner certification contact
c. Product name and version
d. Product overview
e. Product availability date
f. Link to product documentation, including -if applicable- installation and configuration steps
specific to Red Hat Enterprise Linux OpenStack Platform
g. Link to
a. Upstream blueprint, if the software (plugin/driver) is part of OpenStack
b. Software download URL, if not already included in OpenStack
h. List of all dependencies that are not included in Red Hat Enterprise Linux OpenStack Platform.
For each component, indicate:
a. Name
b. Version
c. URL
i. Settings for system services
j. Link to installation/configuration/orchestration scripts (Puppet, Chef or similar)
k. Location of software log files, if they are not located in the service's default log directory
(under /var/log).
l. Any other comments to be included in certification page
Report a bug
12
Revision History
Revision History
Revision 1.0.0-3 Wed May 07 2014 Gemma Sheldon
BZ-1089813: Requested changes implemented.
Corrected orderedlist formatting as previous rendering issue in Publican has been resolved.
13