Re: [PATCH 0/2] kdevops: add milvus with minio support
Luis Chamberlain <[email protected]>
| Newsgroups | dev.linux.lists.kdevops |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Aug 27, 2025 at 02:31:59AM -0700, Luis Chamberlain wrote: > This adds the ability to test milvus on minio with different filesystem > configuration targets. There's a basic configuration you can run which > will just support one default filesystem, which will be used where you > place your docker image and also where we place the minio instance. Then > there is multifs support where just as with fstests support on kdevops > you can select a slew of different filesystem targets to try to test. > > Recommendation is to stick to 40 iterations at 1,000,000 tests unless > you have more than 100 GiB per guest to spare. If you have space to > spare then you know how to ballpark it. > > On High Capacity SSDs, the world is our oyster. > > You can see a demo of results here: > > https://github.com/mcgrof/demo-milvus-kdevops-results > > These are just demos. On guests. Nothing really useful. > I should point out this has AB testing automated as well so we can > leverage this to test for instance ... parallel writeback in an > automated way ;) > > If you want to test this you can also use this branch on kdevops: > > https://github.com/linux-kdevops/kdevops/tree/mcgrof/20250827-milvus > > I am in hopes someone will just prompt an AI for bare metal support > while I sleep. It should be... easy. Just create the partitions already, > use one host and ask the prompt to not mkfs for you. So don't use > multi-fs support at first. Just use the option to create the storage > partition where you place docker. In fact you can copy and paste this > prompt the the AI, and I think it will know what to do. You just skip > some steps as the filesystems can be created and mounted for you. You > just need the host file created by you manually for the target node. > That and infer user and group id support (WORKFLOW_INFER_USER_AND_GROUP). Pushed. Luis