c051db8204
jepsen testing of Garage v1.0.0-rc1
2024-04-05 22:57:00 +02:00
8670140358
[rel-0.9.3] Bump version to 0.9.3
2024-03-04 14:00:55 +01:00
6a7623e90d
[rel-0.9.2] Bump version to v0.9.2
2024-03-01 16:54:39 +01:00
a36248a169
[fix-signed-headers] aws signatures v4: don't actually check Content-Type is signed
...
This page of the AWS docs indicate that Content-Type should be part of
the CanonicalHeaders (and therefore SignedHeaders) strings in signature
calculation:
https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html
However, testing with Minio Client revealed that it did not sign the
Content-Type header, and therefore we broke CI by expecting it to be
signed. With this commit, we don't mandate Content-Type to be signed
anymore, for better compatibility with the ecosystem. Testing against
the official behavior of S3 on AWS has not been done.
2024-03-01 13:12:18 +01:00
ee57dd922b
Bump version to 0.9.1
2024-01-16 16:28:17 +01:00
fa9247f11b
jepsen: updated results, confirming that task3 works
2023-12-14 16:23:48 +01:00
92dd2bbe15
jepsen: nlnet task3a seems to fix things
2023-11-16 18:09:13 +01:00
18e5811159
jepsen: add patch and use more complete names
2023-11-16 12:57:21 +01:00
5b1f50be65
jepsen: testing
2023-10-25 14:43:24 +02:00
9df7fa0bcd
jepsen: use 7 nodes
2023-10-25 14:04:39 +02:00
fd85010a40
jepsen: failures with set2 test in --scenario r
2023-10-25 12:13:27 +02:00
cfbfa09d24
jepsen: fix set2 test omg finally this is so stupid
2023-10-25 11:50:16 +02:00
db921cc05f
jepsen: reconfigure nemesis + add db nemesis
2023-10-25 11:41:34 +02:00
4fa2646a75
jepsen: got a failure with set1
2023-10-24 17:45:22 +02:00
d7ab2c639e
jepsen: fix nemesis to actually generate many operations
2023-10-24 16:39:50 +02:00
d13bde5e26
jepsen: set1 and set2 don't fail anymore ??
2023-10-24 15:44:05 +02:00
d2c365767b
jepsen: more testing
2023-10-24 11:39:45 +02:00
fb6c9a1243
jepsen: update readme
2023-10-20 15:55:09 +02:00
9030c1eef8
jepsen: code path for nemesis final generator
2023-10-20 15:53:46 +02:00
654775308e
jepsen: add cluster reconfiguration nemesis
2023-10-20 15:48:37 +02:00
f5b0972781
jepsen: register crdt read-after-write is fixed with deleteobject patch
2023-10-20 15:00:10 +02:00
d148b83d4f
jepsen: reg2 failure seems to happen only with deleteobject
2023-10-20 13:36:48 +02:00
4b93ce179a
jepsen: errors in reg2 workload under investigation
2023-10-20 12:56:55 +02:00
4ba18ce9cc
jepsen: wip checker for register-like behavior
2023-10-20 12:13:11 +02:00
ef662822c9
jepsen: fix the list-objects call (?)
2023-10-19 23:40:55 +02:00
da8b170748
jepsen: investigating listobjects error
2023-10-19 16:45:24 +02:00
74e50edddd
jepsen: refactoring
2023-10-19 14:34:19 +02:00
b3bf16ee27
make jepsen test more robust: handle errors and timeouts, fixed access key
2023-10-18 17:51:34 +02:00
ddd3de7fce
refactor jepsen code
2023-10-18 16:30:45 +02:00
84d43501ce
refactor jepsen setup logic
2023-10-18 15:34:12 +02:00
012ade5d4b
jepsen: update jepsen and fix garage key info
2023-10-18 14:06:32 +02:00
ef5ca86dfc
jepsen: update to garage 0.9.0
2023-10-18 14:01:18 +02:00
9ec4cca334
reformatting
2023-10-18 12:03:12 +02:00
18ee8efb5f
Check read-after-write property for sets
2023-10-18 12:03:12 +02:00
55eb4e87c4
set tests with independant tests together
2023-10-18 12:03:11 +02:00
0bb1577ae1
two set workloads with different checkers
2023-10-18 12:03:11 +02:00
6eb26be548
Add garage set test (this one works :p)
2023-10-18 12:03:11 +02:00
eb86eaa6d2
refactor jepsen test
2023-10-18 12:03:11 +02:00
80d7b7d858
remove useless files
2023-10-18 12:03:11 +02:00
93a7132b4c
the fix for increasing timestamps does not make things linearizable
2023-10-18 12:03:11 +02:00
dc5245ce65
even without nemesis, s3 get/put/delete is not linearizable (is this normal?)
2023-10-18 12:03:11 +02:00
70c1d3db46
better match exceptions
2023-10-18 12:03:11 +02:00
bc11701999
jepsen: s3 gets and puts
2023-10-18 12:03:11 +02:00
ca4cc7e44f
jepsen connects to vagrant vms
2023-10-18 12:03:11 +02:00
17ebb65273
jepsen ssh into containers seem to work ?
2023-10-18 12:03:11 +02:00
7011b71fbd
jepsen: wip
2023-10-18 12:03:11 +02:00
952c9570c4
bump version to v0.9.0
2023-10-10 14:08:11 +02:00
2e656b541b
Merge branch 'main' into next
2023-10-03 18:40:37 +02:00
cb359b4434
doc: update endpoint_url documentation
...
Since `awscli` `>=1.29.0` or `>=2.13.0` it is now possible to use the
`AWS_ENDPOINT_URL` environment variable, or the `endpoint_url` config
key to override the endpoint URL. This means, the aws bash function to
wrap with --endpoint-url is not necessary anymore. Update invocations to
reflect that.
https://docs.aws.amazon.com/sdkref/latest/guide/feature-ss-endpoints.html
https://github.com/aws/aws-cli/issues/4454#issuecomment-1626116607
2023-10-02 17:16:11 +03:00
9ac1d5be0e
add upgrade test for garage 0.8 -> 0.9
2023-09-27 14:57:37 +02:00
