Don't need session.flush in context managed by session

Within the scope of a single method, keeping all the reads and writes within
the context managed by a single session. In this way, the session's __exit__
handler will take care of calling flush() and commit() for you.
If using this approach, you should not explicitly call flush() or commit().
See http://docs.sqlalchemy.org/en/rel_0_7/orm/session.html#committing

Closes-Bug: #1258044
Change-Id: I1125c72712203f1594ef245761dbfc25ed31eab2
Sync oslo-incubator rpc	module

Sync oslo-incubator rpc module with oslo-incubator commit
f8f6fd46b3b9264c21c0ee5547a4e8236cb257ac

Updates consist in using six.iteritem and fixing some typos.

Remove securemessage.py, which in not used anywhere, and dropped from
oslo-incubator since commit f88d59ab8a456e7d2d5a22fc5591491d2f85bdf4

$ python update.py --nodeps --base keystone --dest-dir ../keystone/ --modules rpc
$ git rm keystone/openstack/common/rpc/securemessage.py

Change-Id: I890cf1ce89ce5946522f7891be71a3e58ecc1af3
Merge "Sync oslo-incubator rpc	module"
Merge "Don't need session.flush in context managed by session"