Kashyap Chamarthy
0b1548a988
In commit 28d337b[1], we advertized that the NEXT_MIN_LIBVIRT and
NEXT_MIN_QEMU_VERSION for "Stein" will be:
libvirt 3.0.0 and QEMU 2.8.0
Now that we are in the development cycle for "Stein", bump the
MIN_{LIBVIRT,QEMU}_VERSION to the above agreed-upon versions.
As part of this clean-up:
- Remove the _create_file_device() function and the calls to it; it is
a "no-op" when 'virtlogd' is available. As a result of this, in
_create_consoles_s390x(), this patch entirely removes the "sclplm"
serial console device — otherwise 'virtlogd', which is now always
available, will create a duplicate 'pty' devices ("sclplm" and
"sclp") pointing to the same log, which results in instance creation
failure; we don't want that.
- Remove the requirement for extra serial device (added in commit:
1f65925: "libvirt: virtlogd: use virtlogd for char devices"), that
"allows access to a Nova instance via `virsh console <guest>`" in
_create_pty_device() — it is not required. I also double-checked
with libvirt and QEMU developer Daniel Berrangé, who said (slightly
paraphrasing):
"Nova should not allow `virsh console` to guests behind its back
at all. And especially it should not care about `virsh console`
working with "tcp". The point of using "tcp" consoles in Nova
is that it provides tunneling via the Nova "serial console
server". You can only have 1 thing connected to a console at a
time — so if the Nova serial console is present, `virsh console`
can't be used anyway."
- The unit test noise is largely mechanical: remove the superflous
serial device, and lower the index of the devices by 1.
The following version constants (and corresponding tests), that are now
no longer required, will be removed in separate patches:
MIN_LIBVIRT_PARALLELS_SET_ADMIN_PASSWD,
MIN_LIBVIRT_POSTCOPY_VERSION, MIN_{LIBVIRT,QEMU}_LUKS_VERSION,
MIN_QEMU_FILE_BACKED_VERSION, MIN_LIBVIRT_PERF_VERSION
[1] http://git.openstack.org/cgit/openstack/nova/commit/?id=28d337b --
Pick next minimum libvirt / QEMU versions for "Stein"
Change-Id: I408baef12358a83921c4693b847a692f6c19e36f
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
========================
Team and repository tags
========================
.. image:: https://governance.openstack.org/tc/badges/nova.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on
OpenStack Nova
==============
OpenStack Nova provides a cloud computing fabric controller, supporting a wide
variety of compute technologies, including: libvirt (KVM, Xen, LXC and more),
Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
---
To learn how to use Nova's API, consult the documentation available online at:
- `Compute API Guide <https://developer.openstack.org/api-guide/compute/>`__
- `Compute API Reference <https://developer.openstack.org/api-ref/compute/>`__
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
- `OpenStack for App Developers <https://www.openstack.org/appdev/>`__
- `Development resources for OpenStack clouds
<https://developer.openstack.org/>`__
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the documentation
available online at:
- `OpenStack Nova <https://docs.openstack.org/nova/>`__
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:
- `Bug Tracker <https://bugs.launchpad.net/nova>`__
Developers
----------
For information on how to contribute to Nova, please see the contents of the
CONTRIBUTING.rst.
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:
- `Official Nova Documentation <https://docs.openstack.org/nova/>`__
- `Official Client Documentation
<https://docs.openstack.org/python-novaclient/>`__
Other Information
-----------------
During each `Summit`_ and `Project Team Gathering`_, we agree on what the whole
community wants to focus on for the upcoming release. The plans for nova can
be found at:
- `Nova Specs <http://specs.openstack.org/openstack/nova-specs/>`__
.. _Summit: https://www.openstack.org/summit/
.. _Project Team Gathering: https://www.openstack.org/ptg/