Andrei Kvapil
Andrei Kvapil
> We need to wait for the Kubernetes Steering Committee to approve the WG creation request. Once we get approval, we will have regular WG Meeting, e.g bi-weekly. Got it!...
Hey I just wanted to inform that we have weekly comunity meetings for developing [aenix-io/etcd-operator](https://github.com/aenix-io/etcd-operator), we'll have one of these tomorrow: **When:** every Tuesday at 16:00 CET **Where:** Google meet...
In case if WG decide to take our etcd-operator code base, we can transfer ownership of our mailing list: ``` https://groups.google.com/g/etcd-operator-dev/ ``` as it will not be needed anymore
Thank you I have solved this already by removing defect resources from the db
@ghernadi haven't you thought about some kind of fsck tool for the database? I think it might be useful as these problems are not new for linstor-controller
I meant a tool that would help fix the database in some way, just to make it functional. For example, it could check the database’s integrity and attempt to fix...
Let's keep it open until new images release
In LINSTOR the volumes have different ``` "allocated_size_kib": 20976040, "usable_size_kib": 20971528 ``` Is it possible to order volumes in LINSTOR using usable_size, not allocated_size?
I just tried to use `--gross` but created volume even smaller than without this flag
Is there ant reliable way to request LINSTOR create a DRBD volume with exact size `1Gi` (1073741824 bytes) that can be 100% usable by the client application?