Florent Vennetier

After PR #1250, versioning is still not enforced, but you can purge exceeding versions by running `openio container purge`. I see 3 possible evolutions: 1. refuse to add a new...

Hello. For `ECLIBEC63D1` you need 9 rawx services. The internal load balancer won't accept to send 2 chunks on the same service. Look for "no service polled from" in the...

`tests.utils.BaseTestCase` also uses **requests**, which can probably be replaced by **urllib3**.

Hello. I did some investigation. Here is a recap. Operation | Event type | Contains user metadata | Contains chunks | Used by -------------|---------|--------------------------------|-----------------------|----------- Object create | storage.content.new | yes...

oio-proxy is indeed caching service entries (unless `proxy.cache.enabled=off`). We could set `resolver.cache.srv.ttl.default=15s` to still benefit from the cache at service startup, but refresh the entry from time to time.

Hello. You can try `openio account refresh XXXXXXXXXX`. This will ask all containers to send their current state to the account service (where the list of containers is stored).

If you have only one inconsistent container, you can simply run `openio container touch XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` (assuming `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` is the name of the container).

The account update relies on the event system. `openio container touch` will ask the `meta2` service to send an event to a `beanstalkd` queue. `oio-event-agent` will eventually read that event...