Commit graph

172 commits

Author SHA1 Message Date
7a143f46fc
Bump to version 1.0.1 2024-09-22 14:25:32 +02:00
Benjamin von Mossner
222674432b This commit adds an environment dict to garage helm chart. Using it, env variables can be set into the garage container environment, useful to set eg. GARAGE_ADMIN_TOKEN or GARAGE_METRICS_TOKEN 2024-07-25 11:42:13 +02:00
bodaciousbiscuits
39b37833c5 adding the ability to change the default podManagementPolicy for StatefulSets 2024-05-19 21:31:19 -05:00
ff093ddbb8
Merge branch 'main' into next-0.10 2024-04-10 14:38:14 +02:00
7dd7cb5759
[rel-0.9.4] upgrade version to v0.9.4 2024-04-08 11:18:19 +02:00
c051db8204 jepsen testing of Garage v1.0.0-rc1 2024-04-05 22:57:00 +02:00
50669b3e76
[next-0.10] bump helm chart version 2024-04-03 14:19:59 +02:00
afad62939e
[next-0.10] bump version number to 1.0 2024-03-28 15:19:44 +01:00
44454aac01
[rm-sled] Remove the Sled database engine 2024-03-08 14:11:02 +01:00
fa4878bad6
[sse-c] Testing for SSE-C encryption 2024-03-07 15:43:48 +01: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