Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
apiserver: Remove charm get cache #6309
Conversation
mjs
added some commits
Sep 21, 2016
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Does not match ['fixes-1544796'] |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
|
Build failed: Tests failed |
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit db061a3
into
juju:1.25
Sep 23, 2016
mjs
deleted the
mjs:1626304-remove-charm-get-cache-1.25
branch
Sep 23, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mjs commentedSep 23, 2016
(this is a backport from 2.0 - see also: #6302)
The filesystem cache used when retrieving charms has been removed. It was implemented when charms lived in a remote S3 bucket and is no longer necessary now that charm live in MongoDB's GridFS store. This helps to reduce disk space usage in the controllers and is one less thing that needs cleaning up when models are removed.
An upgrade step was also added. Now that the apiserver's charm get cache is no longer used it is removed to free up disk space.
This is part of the fix for https://bugs.launchpad.net/juju/+bug/1626304