Updated openstack/openstack
Project: openstack/swift  7f456ef35f15ca9f1d23f9206f0037ef6c6d49c5
null
change the last-modified header value with valid one

the Last-Modified header in Response didn't have a suitable
value - an integer part of object's timestamp.
This leads that the the if-[un]modified-since header with the
value from last-modified is always earlier than timestamp
and results the content is always newer than value of these
conditional headers.
Patched code returns math.ceil() of object's timestamp
in Last-Modified header so the later conditional header works
correctly

Closes-Bug: #1248818
Change-Id: I1ece7d008551bf989da74d23f0ed6307c45c5436
Updated openstack/openstack
Project: openstack/ceilometer  19e06732b720e72139758f9a1831d32aa54d5669
null
Don't assume alarms are returned in insert order

The previous implentation of the tests assure than the db backends
return the alarms into the insert order. This is false for mysql.

The patch rewritte the tests to make it compatible to mysql

Change-Id: I146de0d8cef78b6c734bc6742238b939422645b9