Landscape Client

Landscape-client should allow for several different juju-units on the same machine

Bug #1325599 reported by Chris Glass on 2014-06-02

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Landscape Client	Fix Released	High	Chris Glass

Bug Description

Right now, we only consider a single json file for juju information.

It is possible that several juju units are deployed on the same machine (rare, but possible).

We need the landscape client to consider a set of juju-info files instead of just one, so that the landscape-client charm can output one json file per unit installe don the machine.

Tags:

Related branches

lp:~tribaal/landscape-client/multiple-juju-unit-files

Merged into lp:~landscape/landscape-client/trunk at revision 769

Alberto Donato (community): Approve on 2014-06-03

Free Ekanayaka (community): Approve on 2014-06-03

lp:~tribaal/landscape-client/revert-weird-merge-error

Merged into lp:~landscape/landscape-client/trunk at revision 770

Björn Tillenius (community): Approve on 2014-06-11

Alberto Donato (community): Approve on 2014-06-09

lp:~adam-collard/charms/trusty/landscape-client/landscape-client-multiple-juju-files

Merged into lp:charms/trusty/landscape-client at revision 39

Данило Шеган (community): Approve on 2014-06-13

Geoff Teale (community): Approve on 2014-06-13

Adam Collard: Abstain on 2014-06-13

🤖 Landscape Builder (landscape-builder) on 2014-06-02

tags:

removed: kanban

🤖 Landscape Builder (landscape-builder) on 2014-06-05

Changed in landscape-client:
status:	In Progress → Fix Committed

Revision history for this message

Chad Smith (chad.smith) wrote on 2014-06-05:

Branch was reverted because we made an backward-incompatible changes in message_schemas.py and that prevented all tarmac builds/merges for landscape-server code from landing as well as general landscape-test runs. Because we dropped an existing schema message type JUJU_INFO server could no longer import it. https://ci.lscape.net/job/tarmac-lander/1139/consoleFull