x
/
gantt
Code Issues Proposed changes
RETIRED, Common scheduler for OpenStack
16,664 Commits 1 Branch 0 Tags 28 MiB
Go to file
Joe Gordon a4883260df Minimal changes to get gantt passing the gate 
This is the smallest set of changes needed to unwedge the gate. Because
the gate is wedged all these changes need to be in a single patch in
order to fix it.

* point .gitreview at correct repo

pep8
* Don't run tools/config/check_uptodate.sh, we don't even have a config
  file to check yet.
* gantt, doesn't have any local hacking checks yet so remove that
  section from tox.ini
* Update import_exceptions in tox.ini

pylint
* copy lintstack code in from nova.

docs
* add gantt version code, copied in from nova

Change-Id: I1d7adb5bf1bf383a2f8543dda6eb4cdeb26f3b9a
 		2013-12-26 22:36:27 -08:00
doc Minimal changes to get gantt passing the gate 2013-12-26 22:36:27 -08:00
gantt Minimal changes to get gantt passing the gate 2013-12-26 22:36:27 -08:00
tools Minimal changes to get gantt passing the gate 2013-12-26 22:36:27 -08:00
.coveragerc Port Cheetah templates to Jinja2 2013-09-02 16:03:34 +02:00
.gitignore add .idea folder to .gitignore pycharm creates this folder 2013-03-07 17:00:22 -06:00
.gitreview Minimal changes to get gantt passing the gate 2013-12-26 22:36:27 -08:00
.mailmap Update my mailmap 2013-10-25 16:09:38 +08:00
.testr.conf Fix tests to work with mysql+postgres concurrently 2013-10-27 09:46:45 +11:00
CONTRIBUTING.rst Add a CONTRIBUTING file. 2012-11-21 17:04:48 -05:00
HACKING.rst Updates OpenStack Style Commandments link 2013-10-16 21:52:11 +05:30
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MANIFEST.in Finish AUTHORS transition. 2012-07-05 09:11:37 -05:00
README.rst Update references with new Mailing List location 2013-07-28 11:28:46 -07:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
openstack-common.conf Sync middleware audit, base, and notifier from oslo 2013-12-08 18:45:11 +00:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
requirements.txt Merge "Updated from global requirements" 2013-12-11 09:10:32 +00:00
run_tests.sh Add testr concurrency option for run_tests.sh 2013-10-16 09:31:45 +08:00
setup.cfg Minimal changes to get gantt passing the gate 2013-12-26 22:36:27 -08:00
setup.py Updated from global requirements 2013-09-05 11:12:57 -04:00
test-requirements.txt Updated from global requirements 2013-12-10 18:02:18 -05:00
tox.ini Minimal changes to get gantt passing the gate 2013-12-26 22:36:27 -08:00

README.rst

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 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