Add an AMP-based BrokerProtocol class to expose broker server methods
Bug #499176 reported by
Free Ekanayaka
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Fix Released
|
Low
|
Free Ekanayaka | ||
Bug Description
The some of the methods provided by the landscape.
class need to be exposed to the broker clients (the monitor and the
manager).
We need a BrokerServerPro
used by connected clients to remotely call those methods and get their
return values back.
affects landscape-client
status inprogress
importance low
assignee free.ekanayaka
milestone 1.4.3
Related branches
lp:~free.ekanayaka/landscape-client/broker-protocol
- Sidnei da Silva (community): Approve
- Kevin McDermott (community): Approve
-
Diff: 368 lines (+277/-4)6 files modifiedlandscape/broker/amp.py (+57/-0)
landscape/broker/server.py (+2/-1)
landscape/broker/tests/helpers.py (+36/-0)
landscape/broker/tests/test_amp.py (+176/-0)
landscape/tests/helpers.py (+6/-2)
landscape/tests/test_deployment.py (+0/-1)
| Changed in landscape-client: | |
| milestone: | 1.4.3 → 1.4.4 |
| Changed in landscape-client: | |
| milestone: | 1.4.4 → 1.4.5 |
| Changed in landscape-client: | |
| status: | In Progress → Fix Committed |
| tags: | added: testing |
| tags: | added: needs-testing |
| tags: | removed: testing |
| Changed in landscape-client: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is not easy to test in staging, removing the needs-testing tag.