Go to file

Vladik Romanovsky 1a0778d280 Adding vlans field to Device tagging metadata

Handle the network interface new vlans field and expose it in the devices
metadata
The vlan tag will be exposed to the instance through the metadata API and
on the config drive.

Implements: blueprint sriov-pf-passthrough-neutron-port-vlan
Change-Id: Id7b9f3f1c2107ec604e7f0ef4fbfd31a9e05d0b0

2017-01-26 23:05:07 +00:00

api-guide/source

docs: cleanup wording for 'SOFT_DELETED' in api-guide

2016-11-28 11:51:00 -05:00

api-ref/source

api-ref: Fix parameters and response in os-quota-sets.inc

2017-01-16 00:12:20 +00: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

Merge "Remove nova-manage image from man pages"

2017-01-17 17:44:38 +00:00

etc/nova

Add CORS filter to versions pipeline

2016-12-02 11:44:09 -05:00

gate

move gate hooks to gate/

2017-01-04 11:05:16 +00:00

nova

Adding vlans field to Device tagging metadata

2017-01-26 23:05:07 +00:00

plugins/xenserver

XenAPI Remove useless files when use os-xenapi lib

2017-01-10 18:06:17 -08:00

releasenotes

Adding vlans field to Device tagging metadata

2017-01-26 23:05:07 +00:00

tools

XenAPI Use os-xenapi lib for nova

2017-01-10 17:26:23 -08:00

.coveragerc

Remove nova/openstack/* from .coveragerc

2016-10-12 16:20:49 -04:00

.gitignore

doc: Integrate oslo_policy.sphinxpolicygen

2016-10-20 10:31:01 +01: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

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: Use uuidutils or uuidsentinel to generate UUID

2016-11-29 11:49:24 +05:30

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

Show team and repo badges on README

2016-11-25 13:55:29 +01:00

requirements.txt

Updated from global requirements

2017-01-17 01:13:35 +00:00

run_tests.sh

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

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

setup.cfg

Add nova-status upgrade check command framework

2016-12-19 16:40:50 -05:00

setup.py

Updated from global requirements

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

test-requirements.txt

Updated from global requirements

2017-01-15 09:25:44 +00:00

tests-functional-py3.txt

Fixes to get all functional tests working on py35

2017-01-14 13:06:56 -05:00

tests-py3.txt

Merge "Enable TestOSAPIFixture.test_responds_to_version on Python 3"

2017-01-16 03:14:45 +00:00

tox.ini

Add Python 3.5 functional tests in tox.ini

2016-12-14 13:33:07 +08:00

README.rst

Team and repository tags

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/