delta/openstack/nova.git/nova, branch folsom-eol

Windows instances require the timezone to be "localtime"

2013-10-14T02:50:14+00:00

This was relatively simple to fix, assuming that the image used
to boot the windows instance has the os_type set to "windows".
The use of os_type in this manner is consistent with the
existing use in the Xen hypervisor driver.

DocImpact: if you're booting windows instances, then you need to
set the os_type image property in glance to "windows". Otherwise
your instances will have their clock timezone set to UTC, which
has unexpected side effects in windows.

(cherry picked from commit 280a336a07006b2c998719f2f9033d43289ec7ef)
(cherry picked from commit 18de64748c645b32253901aa704c353e5705eadb)

Conflicts:
	nova/virt/libvirt/driver.py

Note that the unit test had to be tweaked to work in the backport.
There are no functional changes however.

Change-Id: Id6759a290ed25c9add97ac61bb7d165b3fb908b2
Closes-Bug: 1231254

Merge "Return empty list when listing servers with bad status value" into stable/folsom

2013-09-09T18:01:14+00:00

Fix problem with long messages in Qpid (from oslo)

2013-09-06T13:16:22+00:00

This is commit 478ac3a3e in oslo-incubator

Qpid has a limitation where it cannot serialize a dict containing a
string greater than 65535 characters. This change alters the Qpid
implementation to JSON encode the dict before sending it, but only if
Qpid would fail to serialize it. This maintains as much backward
compatibility as possible, though long messages will still fail if they
are sent to an older receiver.

Even though this change will modify the message format, it will only do
it when messages are longer than 65K which would be broken anyway and
could cause serious bugs like the one linked below.

Fixes bug 1215091

Change-Id: I2f0e88435748bab631d969573d3a598d9e1f7fef

Enforce flavor access during instance boot

2013-08-22T14:19:45+00:00

The code in the servers API did not pass the context when retrieving
flavor details.  That means it would use an admin context instead,
bypassing all flavor access control checks.

This patch includes the fix, and the corresponding unit test for the v2
API.

Closes-bug: #1212179

(cherry picked from commit 4054cc4a22a1fea997dec76afb5646fd6c6ea6b9)

Conflicts:
	nova/api/openstack/compute/plugins/v3/servers.py
	nova/api/openstack/compute/servers.py
	nova/tests/api/openstack/compute/plugins/v3/test_servers.py
	nova/tests/api/openstack/compute/test_servers.py

Change-Id: I681ae9965e19767df22fa74c3315e4e03a459d3b

Merge "Use cached nwinfo for secgroup rules" into stable/folsom

2013-08-01T19:03:55+00:00

Merge "Make flavors is_public option actually work" into stable/folsom

2013-08-01T13:31:50+00:00

Use cached nwinfo for secgroup rules

2013-07-31T23:33:10+00:00

This stops a potential DOS with source security groups by using the
db cached version of the network info instead of calling out to
the network api multiple times.

Fixes bug 1184041

Change-Id: Id5f24ecf0e8cce60c27a9aecbc6e606c4c44d6b6
(cherry picked from commit 85aac04704350566d6b06aa7a3b99649946c672c)

Fixed deleting instance booted from invalid vol

2013-07-26T18:06:40+00:00

1. Translated the exception (NotFound) raised from Cinder client to
Nova's native exception (VolumeNotFound).
2. Added unit test coverage.

Fixes LP: #1087214.

Change-Id: I3cee31a9fd068b65a4097f3f3054aebb69d9ba61
(cherry picked from commit 921eec91abee56ea69e1b8b2bff59379b68bff87)

Make flavors is_public option actually work

2013-07-23T16:03:18+00:00

When you create a flavor, you can set an is_public flag to be True or
False.  It is True by default.  When False, the intention is that the
flavor is only accessible by an admin, unless you use the flavor_access
API extension to grant access to specific tenants.

Unfortunately, the only place in the code where this was being enforced
was when listing flavors through the API.  It would filter out the
non-public ones for a non-admin.  Otherwise, the flavor was accessible.
You could get the details, and you could boot an instance with it, if
you figured out a valid flavor ID.

This patch adds enforcement down in the db layer.  It also fixes one
place in the API where the context wasn't passed down to enable the
enforcement to happen.

Fix bug 1194093.

master -> grizzly
(cherry picked from commit b65d506a5f9d9b2b20777a9aceb44a8ffed6a5de)

Conflicts:
	nova/api/openstack/compute/contrib/flavor_access.py
	nova/api/openstack/compute/contrib/flavormanage.py
	nova/api/openstack/compute/flavors.py
	nova/compute/api.py
	nova/db/sqlalchemy/api.py
	nova/tests/api/openstack/compute/contrib/test_flavor_access.py
	nova/tests/api/openstack/compute/contrib/test_flavor_disabled.py
	nova/tests/api/openstack/compute/contrib/test_flavor_manage.py
	nova/tests/api/openstack/compute/contrib/test_flavor_rxtx.py
	nova/tests/api/openstack/compute/contrib/test_flavor_swap.py
	nova/tests/api/openstack/compute/contrib/test_flavorextradata.py
	nova/tests/api/openstack/compute/test_flavors.py
	nova/tests/db/test_db_api.py

grizzly -> folsom
(cherry picked from commit 6df1b7a2a1413a98bffc8b8e0b947f3c90e3bbf5)

Conflicts:
	nova/db/sqlalchemy/api.py
	nova/tests/api/openstack/compute/test_flavors.py

Change-Id: I5b37fa0bb19683fe1642fd81222547d4a317054e

Return empty list when listing servers with bad status value

2013-06-26T02:46:50+00:00

API indicates the status parameter is a string, hence status=BALONEY is a valid
filter that should return zero records since no records match that status. The
return should be an empty list and 200 OK.

Fixes bug 1061712

Change-Id: If796110a18dd75ab5c5d4ba41e9c3b58180341f8
(cherry picked from commit e142d21b47e8895a013c468936e69ba0e7e66041)