Red Hat Enterprise Linux
OpenStack Platform Certification
Test Suite 4
User Guide
Using The Red Hat Enterprise Linux OpenStack Platform Certification
Test Suite
Edition 1
Sankarshan MukhopadhyayZac Dover
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4
User Guide
Using The Red Hat Enterprise Linux OpenStack Platform Certification
Test Suite
Edition 1
Sankarshan Mukhopadhyay
[e-mail]
Zac Dover
[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
How to use the Red Hat Enterprise Linux OpenStack Platform Certification Test Suite
Table of Contents
Table of Contents
. . fa. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . .
Pr.e. . ce
1. Document Conventions 3
1.1. Typographic Conventions 3
1.2. Pull-quote Conventions 4
1.3. Notes and Warnings 5
2. Getting Help and Giving Feedback 5
2.1. Do You Need Help? 5
2.2. We Need Feedback! 6
. ha.pt.e. . . . . . oduct . . .
C. . . . r 1.. Int.r . . . . . . ion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7. . . . . . . . . .
. ha.pt.e. . . . . . . . . . .he. Re.d Ha . . . . . e.r.pr.ise. Linux. . pe.nSt . . Pla.t.for . . . . e.r . . . . . ion T .e.st . . . . . . . . . . . . . .
C. . . . r 2.. Using t . . . . . . . . t Ent . . . . . . . . . O. . . . . . a.ck. . . . . . m C . tifica.t . . . . . . .
Suite 8
2.1. Prerequisites 8
2.2. Raising a Request Using the Bugzilla Interface 8
2.3. Running a Test 9
2.4. Next Steps 14
. ha.pt.e. . . . . . . lea.se. . . . .es. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C. . . . r 3. Re . . . . Not . . 1.5. . . . . . . . . .
3.1. 4.0 15
. . vision Hist.ory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Re. . . . . . . . . . . . . 1.9. . . . . . . . . .
1
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4 User Guide
2
Preface
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 my_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
3
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4 User Guide
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:
4
Preface
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?
If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer
5
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4 User Guide
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 Test Suite.
When submitting a bug report, be sure to mention the manual's identifier: User_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.
6
Chapter 1. Introduction
Chapter 1. Introduction
Welcome to the User Guide for Red Hat Enterprise Linux OpenStack Platform Certification Test Suite.
This guide explains how to obtain and install the Test Suite, and the testing process itself. This User
Guide is intended for members of the Red Hat Cloud Infrastructure Partner Network who are interested
in obtaining certification for their OpenStack drivers or plugins.
The Test Suite ascertains that a third-party component is compatible with Red Hat OpenStack
technology. It checks the compliance of these components with documented OpenStack APIs, on the
specific version of Red Hat Enterprise Linux OpenStack Platform for which certification is being pursued.
The current release of the tool collects information about the usage of the APIs for the Networking and
Block Storage services. The tool also allows users to send the data to Red Hat for review and sign-off.
This User Guide is intended for the Red Hat Enterprise Linux OpenStack Platform Certification Test
Suite version 4.0 which is required to be used in conjunction with Red Hat Enterprise Linux OpenStack
Platform v4.0.
Report a bug
7
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4 User Guide
Chapter 2. Using the Red Hat Enterprise Linux OpenStack
Platform Certification Test Suite
This chapter explains how to use the Red Hat Enterprise Linux OpenStack Platform Certification Test
Suite.
Report a bug
2.1. Prerequisites
The Partner will need to fulfill these prerequisites to use the Red Hat Enterprise Linux OpenStack
Certification Test Suite.
Membership in the Red Hat Cloud Infrastructure Partner Network
A Red Hat corporate account
A Bugzilla account at https://bugzilla.redhat.com/
Partners interested in pursuing a certification must send their Bugzilla and Red Hat account information
to [e-mail], to obtain entitlement to Red Hat Enterprise Linux OpenStack
Platform and the corresponding Certification Test Suite, as well as the right Bugzilla privileges to file
certification requests. Before proceeding with the certification process, partners should verify that
rhoscert_enter has been added to the Permissions of their bugzilla account.
For confidentiality reasons, a certification request will only be visible to the account that created it.
Partners are advised to use a single Bugzilla account to submit and track all their certification activity.
Further interaction with the Red Hat Certification team will be conducted through Bugzilla as described in
the next section.
Once the software entitlement is granted, partners should install Red Hat Enterprise Linux OpenStack
Platform as well as the driver or plugin to be certified. Instructions for Red Hat Enterprise Linux
OpenStack Platform installation are included in the product's documentation.
Report a bug
2.2. Raising a Request Using the Bugzilla Interface
1. Log in to the Red Hat Bugzilla page.
a. the step assumes that the partner has a valid account on the Red Hat Bugzilla
b. the step also assumes that the partner account is configured with the appropriate privileges
to submit a bug/request
2. Ensure that the new bug is filed against the Red Hat OpenStack Certification product and the
appropriate component from the list below.
a. certification-networking-plugin (For certification requests of Networking plugins / drivers)
b. certification-blockstorage-plugin (For certification requests of Block Storage plugins /
drivers)
3. Select the other detail in the form as appropriate.
4. Complete the Summary and Description fields with relevant detail regarding the request.
Additionally, please provide as much detail as possible about the plugin in the text area.
a. For example, using a format like "Partner_Name: Plugin/Driver_Name Plugin_Version
on Red Hat Enterprise Linux OpenStack Platform Version" in the summary would aid the
8
Chapter 2. Using the Red Hat Enterprise Linux OpenStack Platform Certification Test Suite
team reviewing your submissions.
5. Use the Attachment button to add any relevant attachments.
6. Submit the completed report to obtain a new request/bug number.
Please select the Red Hat OpenStack Certification Program product if you would like to file a bug against
the following components:
1. rhoscts (For any defect or enhancement requests against the Red Hat Enterprise Linux
OpenStack Platforfm Certification Test Suite)
2. doc_User-Guide (For any defect or enhancement request against the User Guide for the Red Hat
Enterprise Linux OpenStack Platform Certification Test Suite)
3. certification-catalog (For any defect or enhancement request against the public listing of Red Hat
Enterprise Linux OpenStack Platform certified components)
Important
DISCLAIMER:
During the test, the tool will collect data for the system infrastructure under test. Such data would
include, but not be limited to
hostnames of machines on the systems under test
IP addresses of machines on the systems under test
API calls and system calls
configuration files required to set up OpenStack services
The above will be included in the results log which will be uploaded to bugzilla.redhat.com for
audit, review, and analysis by Red Hat. The logs will be retained in bugzilla.redhat.com, and will
only be visible to Red Hat Certification Team and members of the partner-specific group used to
file the certification.
Report a bug
2.3. Running a Test
The Red Hat Enterprise Linux OpenStack Certification Test Suite is provided as a framework with the
tests for the individual components available by means of options (or a configuration file). The current
release of the Test Suite is configured to test and certify a plugin for the Networking and Block Storage
services, and it must be installed and configured on the hardware on which these services are running.
In order to run the Test Suite, the user must have root user privileges.
The Red Hat Enterprise Linux OpenStack Platform Certification Test Suite can be installed by the
following command:
# yum install openstack-cts
Once the Test Suite is downloaded and installed, the following files must be appropriately modified:
api.conf - this file helps the user to enable/disable tests by setting appropriate values
bugzilla.conf - this file has the appropriate URL to the Red Hat Bugzilla already filled in; the user
must input the username for the Bugzilla account which has the appropriate group permissions to file
the bug
9
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4 User Guide
network.ini - this file requires the username, password, and tenant name for both admin and
normal users; the IP address of the machine on which the tests are to be invoked, and other aspects
which are commented in the file.
storage.ini - this file requires the username, password, and tenant name for both admin and
normal users, the IP address of the machine on which the tests are to be invoked, and other aspects
which are commented in the file.
All the files contain sections with comment blocks to aid the user in providing the required values.
Additionally, the kind of expected values are provided by means of an example below.
In network.ini, the vlan and gre keys are expected to contain the ID's (in a numeric format) as
configured in the plugin file. For example, in case of openvswitch, the vlan_id is specified as
tenant_network_type = vlan
network_vlan_ranges = physnet1:100:110
In this case the vlan key in network.ini can have value in the range of 100 and 110.
Similarly gre_id is specified as
enable_tunneling = True
tunnel_id_ranges = 1:1000
And thus the gre key in network.ini can have value in the range of 1 and 1000
Subsequent to these changes, the test suite run is initiated with the following commands:
For running tests pertaining to checking the Networking plugin:
# rhoscts --certify-network
For running tests pertaining to checking the Block Storage plugin:
# rhoscts --certify-storage
Running a Specific Subset of the Tests
The latest release of the Red Hat Enterprise Linux OpenStack Platform Certification Test Suite allows a
specific subset of the tests to be invoked. This is useful in cases where the plugin/driver has
successfully completed all but a few of the tests or the certification reviewer would require specific
additional detail subsequent to a previous run of the test. The user need not run the entire set of tests
in the test suite and instead run a selected subset.
This feature is enabled by commenting out appropriate sections of the configuration file ie. the
api.conf file present in /etc/rhoscts directory. The certification reviewer will provide guidance for
the specific sections to be disabled by means of commenting out and request that the tests be repeated
for the specific component. Users can enable or disable tests by setting flags in this file. Setting a flag to
1 will enable tests. To disable a test run, the flag has to be set to 0. Users can thus control which
specific test suite they need to run.
The file contains two sections - [network] and [storage] each controlling their respective tests.
10
Chapter 2. Using the Red Hat Enterprise Linux OpenStack Platform Certification Test Suite
Example 2.1. Network Section
[network]
network_check=1
subnet_check=1
port_check=1
ipam=1
security_groups=1
provider_networks=1
Tests Under network_check
test_create_admin_network
test_update_admin_network
test_admin_create_public_network
test_create_public_network
test_update_network
test_list_networks
test_mixed_list_networks
test_admin_bulk_create
test_bulk_create
Tests Under subnet_check
test_create_subnet_admin
test_subnet_dns_nameservers
test_subnet_dhcp_status
test_subnet_host_routes
test_subnet_list
test_subnet_mixed_list
test_create_subnet
test_admin_bulk_create
test_bulk_create
test_allocation_pools_admin
test_allocation_pools
Tests Under port_check
test_create_admin_port
test_create_port
test_admin_bulk_create
test_bulk_create
test_port_admin_list
test_port_list
test_port_mixed_list
test_port_admin_update_state
test_port_update_state
Tests Under ipam
11
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4 User Guide
test_admin_ipam_empty
test_ipam_empty
test_admin_ipam_first
test_ipam_first
test_admin_ipam_specific
test_ipam_specific
test_admin_ipam_multiple
test_ipam_multiple
test_admin_ipam_subnet
test_ipam_subnet
test_admin_ipam_update
test_ipam_update
Tests Under security_groups
test_security_group
test_security_group_rules
Tests Under provider_networks
test_create_provider_network_local
test_create_provider_network_flat
test_create_provider_network_vlan
test_create_provider_network_gre
12
Chapter 2. Using the Red Hat Enterprise Linux OpenStack Platform Certification Test Suite
Example 2.2. Storage Section
[storage]
volume_check=1
volume_cloning=1
volume_image_creation=1
isci=1
snapshots=1
Tests Under volume_check
test_create_volume
test_list_volumes
test_delete_volume_early
test_delete_volume_twice
test_volume_from_snapshot
Tests Under volume_cloning
test_volume_cloning
Tests Under volume_image_creation
test_image_volume
Tests Under isci
test_isci_initialization
Tests Under snapshots
test_create_snapshot
test_list_snapshots
test_delete_snapshot_twice
test_delete_snap_volume
The Red Hat Enterprise Linux OpenStack Platform Certification Test Suite is then invoked to collect
relevant data/logs.
If a bugzilla request has not been created, the tool provides an option to do it automatically and attach
the run logs to it. It prompts the user to provide the password associated with the Bugzilla account.
Before uploading the results to Bugzilla, the user is prompted to provide consent. The user is presented
with the following text
By using this tool to upload data to Red Hat, you consent to Red Hat's receipt, use
and analysis of this data. Type 'Y' to continue and, 'N' to cancel.
Upon selection of Y the upload proceeds successfully and, a URL to the request filed/bug is provided in
response.
If a request has already been created manually prior the test run, the user should opt to upload the
result log to the bugzilla manually, as an attachment to the existing request/bug.
13
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4 User Guide
Choosing N after a successful test run causes the logs to be packaged into an archive and made
available at /tmp.
Report a bug
2.4. Next Steps
Once the logs of the system under test are uploaded to Red Hat Bugzilla, they will be reviewed and
analyzed. Further queries, if any, will be posted to the request/bug. If the logs successfully pass the
review, the submission will be signed-off, the transaction will be marked CLOSED CURRENT RELEASE,
and the component is considered certified for Red Hat Enterprise Linux OpenStack Platform.
Report a bug
14
Chapter 3. Release Notes
Chapter 3. Release Notes
Release notes of rhos-cts
Report a bug
3.1. 4.0
This section contains important information pertaining to release candidate 4.0 of the Red Hat
Enterprise Linux OpenStack Platform Certification Test Suite, including known problems, resources, and
other issues. Read this document before using this release. Bugs should be filed against certification-
blockstorage-plugin and certification-networking-plugin instead of certification-cinder-plugin and
certification-quantum-plugin of OpenStack Certification Test Suite.
4.0 provides these enhancements:
BZ#989617
The previous version of rhoscts as made available for the Red Hat OpenStack
Certification Program takes an all-or-none approach to test runs. That is,
all tests for a specific component are invoked even if particular APIs are
not relevant/supported for a plugin provided by the partner. The feature
enables a partner to skip specific tests which have already been invoked
earlier and, thus provide a smaller sub-set of tests to be run if required.
BZ#994 611
When the Red Hat Enterprise Linux OpenStack Platform Certification Test
Suite tool is used during the process of certification, the result log will
also contain the version of the tool used during the certification run.
Previously this was not recorded as it was implicitly understood that the
partner will use the current and latest version of the tool available via
RHN/CDN. Now, the version is recorded in order to provide the ability to
handle multiple versions of the tool available to the partner.
BZ#994 622
Previous versions of the tool did not propose a standard format for the
description of the field. This created an inconsistent set of descriptions.
The current version of the tool aims to resolve that by standardizing the
description made available for reviewers. Bugs filed using the new version
of the Red Hat Enterprise Linux OpenStack Platform Certification Test Suite
tool will have the Summary field as " :
on Red Hat Openstack "
BZ#986702
Previous versions of the binary did not provide any notifications or visual
indicators of progress of the test. With this feature, a visual indicator of
the progress of the test is made available to the reviewer, providing the
end-user with a method to estimate whether the tool is functional and
active.
15
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4 User Guide
BZ#104 084 9, BZ#104 0851
This feature implements the tests for the API which creates a subnet
available to the admin or regular user, with allocation pools.
BZ#989587
The current release of the tool now allows the partner name to be part of
the summary description of the filing. This is an aid to the reviewer or
any other individual watching the filed bug.
BZ#996890
The existing test for logging snapshots in Cinder was displaying snapshots
that were known to be deleted. This fix ensures that deleted snapshots are
not logged when using the API for listing snapshots.
BZ#101714 8, BZ#1017152, BZ#1017150, BZ#1017155
This feature implements the tests for the API which enable creating and
deleting bootable volumes, and listing summary information for all Block
Storage volumes that the tenant who submits the request can access.
BZ#1017160
This feature implements the test for creating volumes from snapshot as
provided via an API.
BZ#1017165
This feature implements the test for the API which pertains to the
initialization of an iSCSI device.
BZ#1017166
This feature implements the test for the API which initiates the cloning of
a volume that the tenant who submits the request can access.
BZ#1017178, BZ#1017187, BZ#1017188, BZ#1017189, BZ#1017206
This feature implements the tests for the API which enables creating and
deleting a snapshot (a point-in-time copy of a volume) and lists the
summary information for all Block Storage snapshots that the tenant who
submits the request can access.
BZ#1019074 , BZ#1019080, BZ#1019082, BZ#101914 9, BZ#1019093, BZ#1019136
16
Chapter 3. Release Notes
This feature implements the tests for the API which creates, updates, and
lists networks available either to the admin or regular users.
BZ#1019290, BZ#1019291, BZ#1019292, BZ#1019293
This feature implements the tests for the API which creates a network with
the following types: flat, local, vlan, or gre.
BZ#101914 1, BZ#1019077
This implements the tests for listing the networks to which a tenant has
access, depending on whether the tenant has admin or regular user
privileges. The response logged indicates whether the administrative state
of the network is up or down; the network ID; the network name; whether this
network is shared across all tenants; the network status; the associated
subnets and the tenant ID.
BZ#1022615, BZ#1022619, BZ#104 0837, BZ#104 084 3
This feature implements the tests for the API which creates and deletes a
subnet on a specified network that is available to regular or admin users.
BZ#104 0855, BZ#104 0865, BZ#104 0863, BZ#104 0869, BZ#104 0854
This feature implements the tests for the API which creates a subnet in a
specific network, and updates the host route, DNS server, and DHCP status
for the subnet.
BZ#104 0911
This implements the test for a normal user and provides a listing of the
subnets to which the specified tenant has access. This update implements the
feature targeted at Red Hat Enterprise Linux OpenStack Platform 4.0 (Havana
release). Now, default policy settings exclusively return subnets owned by
the tenant submitting the request, unless the request is submitted by an
user with administrative rights.
BZ#104 0793, BZ#104 0796
This feature implements the tests for the API which deletes a specified
network and its associated resources available to admin and regular users.
BZ#1019089, BZ#101914 3, BZ#104 0797, BZ#104 0833, BZ#104 0834 , BZ#104 084 7
This feature implements the tests for the API which creates multiple
networks and subnets in a single request that is made by admin or regular
users.
17
Red Hat Enterprise Linux OpenStack Platform Certification Test Suite 4 User Guide
BZ#1019187, BZ#1019188, BZ#1019192, BZ#1019201, BZ#1019210, BZ#1019212,
BZ#104 0894 , BZ#104 0895, BZ#104 0905, BZ#104 0907, BZ#104 0799, BZ#104 0800
This feature implements the tests for the API which creates and deletes
ports on a specified network available to the admin and regular users,
lists ports to which the tenant has access, and updates the specified port
accessible to the tenant who submits the request.
BZ#1019206, BZ#1019207, BZ#104 0805
This feature implements the test for the API which creates multiple ports
across a set of specified subnets in a single request.
BZ#104 0881, BZ#104 0882, BZ#104 0885, BZ#104 0887
This implements the tests for the API which creates a port that is available
to the admin or normal user making the request, and is allocated the first
IP address in subnet, or a specific IP address in subnet.
BZ#104 0888, BZ#104 0890, BZ#104 0901, BZ#104 0903
This implements the tests for the API which creates an admin or regular
user port with multiple IP addresses allocated from a specified network,
and tests for updates to the IP within a network providing static IP.
BZ#102074 6, BZ#102074 7, BZ#102074 9, BZ#1020751, BZ#1020753, BZ#1020754
This feature implements the tests for the API which creates and deletes
security groups, creates and deletes security group rules, and lists
summaries of all security groups or security group rules that the specified
tenant can access.
BZ#1052788
This update provides detail about the api.conf file and, provides some
recommended values to be input to initiate the test run
Report a bug
18
Revision History
Revision History
Revision 1.0-1 Thu Jan 16 2014 Sankarshan Mukhopadhyay
Addition of configuration file example and, detail.
Revision 1.0-0 Sun Jan 6 2013 Cheryn Tan
Publication for 4.0 release.
19