Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(4976)

Issue 7363061: state: Service.SetCharm endpoints check (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
11 years, 2 months ago by dimitern
Modified:
11 years, 2 months ago
Reviewers:
mp+150835
Visibility:
Public.

Description

state: Service.SetCharm endpoints check With this change, SetCharm will ensure the new charm that's about to be set is compatible with the current service's charm, i.e. implements all endpoints the service is currently in (extra relations are ok). Fixes LP bug #1032557 https://code.launchpad.net/~dimitern/juju-core/006-upgrade-charm-handle-relations/+merge/150835 (do not edit description out of merge proposal)

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+150 lines, -6 lines) Patch
A [revision details] View 1 chunk +2 lines, -0 lines 0 comments Download
M state/conn_test.go View 1 chunk +14 lines, -0 lines 0 comments Download
M state/service.go View 1 chunk +19 lines, -0 lines 0 comments Download
M state/service_test.go View 3 chunks +115 lines, -6 lines 0 comments Download

Messages

Total messages: 2
dimitern
Please take a look.
11 years, 2 months ago (2013-02-27 16:13:42 UTC) #1
dimitern
11 years, 2 months ago (2013-02-27 17:03:32 UTC) #2
On 2013/02/27 16:13:42, dimitern wrote:
> Please take a look.

As discussed on the hangout, the following things need to happen in addition to
what's there already:
1) Only active relations have to be considered, not potential endpoints. This
has to be done carefully to make sure the relations snapshot we got from state
is most recent, checking the relation count is the same and making sure all
relation docs still exist by the time we set the charm.
2) New peer relations should be created in the same transaction (at the end).

So this is still WIP for now.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b