| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Change-Id: I992dc0c1d40f563ade56a833162d409b02be90a0
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| | |
Reviewed by:
Lars Wirzenius
Daniel Silverstone (on IRC)
Sam Thursfield (v4 of patch)
Richard Maw (on IRC)
|
| |/
|
|
|
|
|
| |
With this we can request the state of a set of artifacts
in a single request. Artifacts are sent as a json array.
We check whether each artifact is in the cache or not
and send our findings back to the client as a json object.
|
| | |
|
| |\
| |
| |
| |
| |
| | |
Reviewed by:
Pedro Alvarez
Daniel Silverstone
|
| |/
|
|
|
|
|
|
| |
lighttpd does not support WSGI, so we need to be able to run
the server in FCGI mode. The flup package provides one.
Running with the default bottle server is still useful
for testing purposes.
|
| |\
| |
| |
| | |
Reviewed-by: Lars Wirzenius <lars.wirzenius@codethink.co.uk
|
| |/ |
|
| |\
| |
| |
| | |
'origin/jannispohlmann/add-batch-sha1-and-file-queries'
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds support for resolving multiple refs into SHA1s and
requesting multiple files at once, each using a single POST request.
The (repo, ref) and (repo, ref, filename) parameters are passed to
the POST requests as JSON dictionaries in a list. The response to
both types of requests is a JSON list with the same dictionaries
again, to which a "sha1" and "data" field are added, respectively.
The file contents returned by "POST /1.0/files" requests are
base64-encoded and need to be decoded at the receiver's end. This
is because the contents may be binary or contain quotes and
therefore cause JSON syntax errors.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
'git show-ref' returns multiple results where there are partial matches
for the given ref, which creates the possibility that we might resolve
a ref incorrectly. 'git rev-list' is also overkill for verifying that a
SHA1 is valid.
|
| |
|
|
|
|
|
|
| |
This bug has been present since the initial commit to the cache
server. Due to the missing repo_dir argument to rev_list(), resolving
SHA1s rather than symbolic refs via /1.0/sha1s fails. This feature,
however, is absolutely required for morph to resolve petrified system
branches.
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In order to allow the artifact cache to be cleaned up, this patch allows for a
/delete method which can remove artifacts from the cache. It takes the
following arguments:
artifact=artifactname
The artifact will be deleted and a JSON object returned in the form:
{
"status": errno,
"reason": strerror
}
Where errno is zero on success, 1 on EPERM, 2 on ENOENT etc. and reason is the
strerror of the errno, in case the architectures differ between caller and
cache.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rather than pushing artifacts to the cache, this method allows the caller to
specify a host and artifact which the cache server will then fetch into its
local cache. It takes the following arguments:
host=hostname:port
artifact=artifactname
This is transformed into a fetch to:
http://hostname:port/artifacts?basename=artifactname
Which is then fetched into the cache under the given name.
The return from this is a JSON object of the form:
{
"filename": artifactname,
"size": NBYTES_SIZE_OF_FILE,
"used": NBYTES_DISK_SPACE_USED
}
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When --enable-writes is set, we provide a /list target which produces
a JSON dictionary of information about the state of the artifact cache.
The dictionary is of the form:
{
"freespace": NBYTES_OF_SPACE,
"files": {
"artifact-filename": {
"atime": ATIME_AS_NUMBER,
"size": NBYTES_SIZE_OF_FILE,
"used": NBYTES_USED_ON_DISK
},
...
}
}
This allows a controller to decide which artifacts have not been requested in
some time and also how big artifacts are, not only in terms of their 'byte'
size, but also the space they consume on disk. System images in particular may
differ in this respect since they should be sparsely stored.
|
| | |
| |
| |
| |
| |
| |
| | |
Since we need to be able to update the cache from builders, this patch
introduces a --enable-writes argument to morph-cache-server and also adds a
@writable decorator to the class ready for marking particular paths which are
only available when --enable-writes is set.
|
| | |
| |
| |
| |
| | |
In order to allow multiple morph-cache-server instances to run on
a single system, we need to support running on different ports.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Morph now expects the tree SHA1 in addition when resolving references
using the cache server. This is to better facilitate correct cache
key computation since commits can be made which have no tree changes
and thus nothing to usefully affect the build. (For example the morph
branch and build features)
|
| | |
| |
| |
| |
| |
| |
| | |
Direct-mode, when enabled, causes morph-cache-server to assume a more
Trove-like structure for the repositories, rather than the morph-cache
structure which it was originally written for. This means that for
the workers, we can use the original code and for Trove, the direct mode.
|
| |/
|
|
|
| |
To reduce the noise when I run 'git status' this gitignore will mean
that git won't notify me of repocache.pyc and __init__.pyc
|
| |
|
|
| |
This reverts commit f1fba299bd07510346082ef985ef08a494dca9d9.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/trees queries take repo URI, a SHA1 ref and an optional path parameter.
The result is a JSON dictionary of the form
{
"repo": "<repo URI>",
"ref": "<SHA1 ref>",
"tree": {
"filename1": {
"mode": "100644",
"kind": "blob",
"sha1": "FOOBARBAZ"
},
...
}
}
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Resolving a ref may result in a different SHA1 between any two requests,
so we simply should never allow the results to be cached by an HTTP
cache.
|
| | |
|
| |
|
