lp:~tealeg/landscape-client/plugins-respect-scopes

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

706. By Geoff Teale on 2013-07-05

Merge scope handling in monitoring plugins.

705. By Geoff Teale on 2013-07-05

Merge keystone resynchronisation changes.

704. By Geoff Teale on 2013-07-05

Fix up session_id tests for scoped resynch.

703. By Geoff Teale on 2013-07-05

Merge in message_schemas.py

702. By Geoff Teale on 2013-07-05

Merged in test_server.py

701. By Geoff Teale on 2013-07-05

Merged in test_registration.py

700. By Geoff Teale on 2013-07-05

Merged in test_exchange.py

699. By Geoff Teale on 2013-07-05

Merged in registration.py

698. By Geoff Teale on 2013-07-05

Merged in exchange.py

697. By Geoff Teale on 2013-07-05

Merged add-session-ids-to-activity-responses [r=jseutter,free.ekanayaka] [f=1158822].

This branch implements the client side parts of a mechanism described here: https://wiki.canonical.com/Landscape/SpecRegistry/0047

In landscape.broker.store.MessageStore I've added three methods, get_session_id, is_valid_session_id, and drop_session_ids, they respectively create and store a new ID (with optional scope), check for existence of a given ID in the store, and delete all IDs within a certain scope. As I write this I suspect it might be sensible to remove scope as the work that requires it is unlikely to get scheduled soon (currently it always uses the default scope, None).

landscape.broker.server.BrokerServer has a get_session_id method that essentially is a pass-through to the MessageStore method. The send_message method on the BrokerServer has been modified to always require a session_id, which it will validate. If the session_id is not known to the message store then the message will be dropped, silently.

landscape.broker.exchange.MessageExchange will now drop all session-ids when it handles a resynchronize request. This means that any messages that are sent with IDs generated before that request will simply be dropped.