Mark McLoughlin 8eaf4a0b33 Use latest version of SQLAlchemy ...

Fedora 16 has SQLAlchemy-0.7.2 and it seems to work fine with Nova,
modulo these occassional migration errors that crop up. The
foreign_keys set in 047 issue is the third such problem fixed lately.

Is there any particular reason to stick with 0.6.3?

Change-Id: Ia65bc1f6035917b5aec84ad51d6504543256f7ca

2011-09-28 15:03:33 +01:00

ajaxterm

Changed broken perms

2011-07-11 15:31:39 -05:00

esx

Multi-NIC support for vmwareapi virt driver in nova.

2011-09-05 12:51:07 +05:30

clean-vlans

Changed broken perms

2011-07-11 15:31:39 -05:00

euca-get-ajax-console

Changed broken perms

2011-07-11 15:31:39 -05:00

install_venv.py

removing compute monitor

2011-08-02 10:09:58 -04:00

nova-debug

Changed broken perms

2011-07-11 15:31:39 -05:00

pip-requires

Use latest version of SQLAlchemy

2011-09-28 15:03:33 +01:00

rfc.sh

Fix rfc.sh's check for the project

2011-09-23 12:21:29 +01:00

setup_iptables.sh

Make nova work even when user has LANG or LC_ALL configured

2010-12-16 12:35:46 +01:00

with_venv.sh

Fixes to the virtualenv installer

2010-07-26 18:57:24 -07:00

Description

RETIRED, further work has moved to Debian project infrastructure

937 KiB