Ghanshyam da3a02243d Correct the keypairs-get-resp.json API sample file
Current keypair sample files 'keypairs-get-resp.json/xml contain
'keypairs' as the first key and that means its sample response
of "list keypairs" API not "get keypair" API.

The tests don't pass a keypair id, so current tests also are for
"list keypairs" API.

Details-
Below API sample files- from their name it looks like these are for
get keypair API. But in actual content of these files are written as
List keypair API response. So it create the confusion that for which
API these API sample file are. Name suggest for GET and content
suggest for LIST Keypair.

    /nova/tests/integrated/api_samples/os-keypairs/
    keypairs-get-resp.json.tpl
    /nova/tests/integrated/api_samples/os-keypairs/
    keypairs-get-resp.xml.tpl

Their API sample test cases are written corrosponding to list keypair
APIs.

This patch correct the above API sample file name from get to list
Keypair APIs.
API Sample test cases names are also modified accordingly.

Partial-Bug: 1298769

Change-Id: I88d894ff9b0f6236221fa922601b641f26a87301
2014-04-01 08:57:06 +09:00
2013-09-02 16:03:34 +02:00
2014-03-27 11:57:42 -07:00
2014-02-15 09:59:26 +08:00
2012-02-08 19:30:39 -08:00
2010-05-27 23:05:26 -07:00
2012-07-05 09:11:37 -05:00
2014-03-31 11:36:43 -04:00
2013-09-05 11:12:57 -04:00

OpenStack Nova README
=====================

OpenStack Nova provides a cloud computing fabric controller,
supporting a wide variety of virtualization technologies,
including KVM, Xen, LXC, VMware, and more. In addition to
its native API, it includes compatibility with the commonly
encountered Amazon EC2 and S3 APIs.

OpenStack Nova is distributed under the terms of the Apache
License, Version 2.0. The full terms and conditions of this
license are detailed in the LICENSE file.

Nova primarily consists of a set of Python daemons, though
it requires and integrates with a number of native system
components for databases, messaging and virtualization
capabilities.

To keep updated with new developments in the OpenStack project
follow `@openstack <http://twitter.com/openstack>`_ on Twitter.

To learn how to deploy OpenStack Nova, consult the documentation
available online at:

   http://docs.openstack.org

For information about the different compute (hypervisor) drivers
supported by Nova, read this page on the wiki:

   https://wiki.openstack.org/wiki/HypervisorSupportMatrix

In the unfortunate event that bugs are discovered, they should
be reported to the appropriate bug tracker. If you obtained
the software from a 3rd party operating system vendor, it is
often wise to use their own bug tracker for reporting problems.
In all other cases use the master OpenStack bug tracker,
available at:

   http://bugs.launchpad.net/nova

Developers wishing to work on the OpenStack Nova project should
always base their work on the latest Nova code, available from
the master GIT repository at:

   http://github.com/openstack/nova

Developers should also join the discussion on the mailing list,
at:

   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Any new code must follow the development guidelines detailed
in the HACKING.rst file, and pass all unit tests. Further
developer focused documentation is available at:

   http://nova.openstack.org/

For information on how to contribute to Nova, please see the
contents of the CONTRIBUTING.rst file.

-- End of broadcast
S
Description
No description provided
Readme 258 MiB
Languages
Python 97.5%
Smarty 2.3%
Shell 0.2%