Go to file

Matt Riedemann 29dab997b4 Hyper-V: Adds Hyper-V UEFI Secure Boot

Hyper-V supports UEFI SecureBoot since the 2012 R2 version
for Windows guests and this has been extended to Linux
guests as well with the upcoming release. This blueprint
implements UEFI SecureBoot for Linux guests.

DocImpact: The nova flavor extra specs docs needs to be updated
to include 'os:secure_boot' and its possible values. The
image metadata property docs needs to be updated to include
"os_secure_boot" property and its possible values.

Co-Authored-By: Claudiu Belu <cbelu@cloudbasesolutions.com>

Implements: blueprint hyper-v-uefi-secureboot

Change-Id: I1ea96930018d997820df2b7b4640fe1f241ee8d6

2016-09-26 20:14:43 -04:00

api-guide/source

Merge "Remove last sentence"

2016-09-26 13:12:57 +00:00

api-ref/source

Add more description when service delete

2016-09-21 20:18:18 +08:00

contrib

Merge "changed quantum to neutron in vif-openstack"

2014-03-05 10:45:05 +00:00

devstack

Add RC file for excluding tempest tests for LVM job

2016-05-17 10:25:45 -04:00

doc

docs: Clarify sections & note on filter scheduler

2016-09-23 14:22:16 -06:00

etc/nova

Add bigswitch command to compute rootwrap filters

2016-09-02 14:01:38 -02:30

nova

Hyper-V: Adds Hyper-V UEFI Secure Boot

2016-09-26 20:14:43 -04:00

plugins/xenserver

plugins/xenserver: Add '.py' extension

2016-09-21 10:56:39 +01:00

releasenotes

Hyper-V: Adds Hyper-V UEFI Secure Boot

2016-09-26 20:14:43 -04:00

tools

Remove locals() for formatting strings.

2016-08-22 17:32:38 +07:00

.coveragerc

Change ignore-errors to ignore_errors

2015-09-21 14:34:39 +00:00

.gitignore

Ignore generated merged policy files

2016-08-31 08:54:25 -07:00

.gitreview

Add .gitreview config file for gerrit.

2011-10-24 15:07:19 -04:00

.mailmap

Add mailmap entry

2014-05-07 12:14:26 -07:00

.testr.conf

[placement] Adjust the name of the gabbi tests

2016-09-20 19:14:44 +00:00

babel.cfg

Get rid of distutils.extra.

2012-02-08 19:30:39 -08:00

bandit.yaml

Add bandit for security static analysis testing

2015-07-02 09:17:48 -07:00

bindep.txt

List system dependencies for running common tests

2016-08-24 06:49:32 +02:00

CONTRIBUTING.rst

Workflow documentation is now in infra-manual

2014-12-05 03:30:37 +00:00

HACKING.rst

hacking: Always use 'assertIs(Not)None'

2016-09-23 15:40:35 +01:00

LICENSE

initial commit

2010-05-27 23:05:26 -07:00

MAINTAINERS

Add a maintainers file

2015-05-23 03:22:07 +10:00

README.rst

Refresh README and its docs links

2016-08-08 10:26:08 +01:00

requirements.txt

Remove nova.image.s3 and configs

2016-09-22 19:29:47 -04:00

run_tests.sh

Add description on how to run ./run_test.sh -8

2016-01-11 13:17:04 +00:00

setup.cfg

Merge "Adds nova-policy-check cmd"

2016-09-01 17:56:56 +00:00

setup.py

Updated from global requirements

2015-09-17 16:41:48 +00:00

test-requirements.txt

Updated from global requirements

2016-09-22 20:30:27 +00:00

tests-py3.txt

Merge "Enable py3 tests for unit.api.openstack.compute.test_console_output"

2016-09-26 18:17:43 +00:00

tox.ini

Revert "tox: Don't create '.pyc' files"

2016-09-14 10:45:44 +01:00

README.rst

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 and OpenStack Ironic.

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.

API

To learn how to use Nova's API, consult the documentation available online at:

http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/

For more information on OpenStack APIs, SDKs and CLIs, please see:

http://www.openstack.org/appdev/ http://developer.openstack.org/

Operators

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

http://docs.openstack.org

For information about the different compute (hypervisor) drivers supported by Nova, please read:

http://docs.openstack.org/developer/nova/feature_classification.html

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

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:

http://docs.openstack.org/developer/nova/