Updated openstack/openstack
Project: openstack/oslo.messaging  15bfa35e0ccdf5e12d70208192edebc547560491
null
Implements notification listener and dispatcher

This patch allows to quickly create a listener to receive
notification messages.

Example of the api:

class Endpoint(object):
    def warn(self, ctxt, publisher_id, event_type, payload):
        do_something(payload)

target = messaging.Target(topic='notifications', exchange='cinder')
listener = notify.get_notification_listener(transport, [target],
                                            [Endpoint()],
                                            executor,
                                            serializer)

Implements blueprint notification-subscriber-server

Change-Id: I434bc487c382a2048670df726d9bebd640150bb9
Updated openstack/openstack
Project: openstack/ceilometer  c7e75b7645ddf58f990d48b91f30cf8fcff9df69
null
Rename Openstack to OpenStack

Change-Id: I35692f6800febbb71555e9d5fe28ddc12c25f6a4
Updated openstack/openstack
Project: openstack/ceilometer  4261de74a88bbe2009f10826de5bda05c2075ded
null
Adds gettextutils module in converter

Change-Id: I6f0270067a034dfbe38ecb8fb8916509b36fd7eb
Updated openstack/openstack
Project: openstack/horizon  16a22952c5c8cfc9eb27fc642614132a7544960a
null
Get instance networking information from Neutron

project/instances, admin/instances and the instance details page
all get networking information from Nova. However, with Neutron
enabled, floating IP associations are done direcly with Neutron,
meaning that Nova's DB will fall out of sync and thus the GUI
won't reflect successful floating IP associations until Nova
polls Neutron again and updates its DB. The polling can take
up to several minutes to complete for consecutive floating IP
operations.

The solution is to update instances' networking information from
Neutron immediately after the call to list Nova instances.

Closes-Bug: #1265032
Change-Id: I0382fa9a4a9fff21e7b4d05cd3b76783f826735f