search

osism / issues

This repository is used for bug reports that are cross-project or not bound to a specific repository (or to an unknown repository).
https://www.osism.tech
1 stars 1 forks source link

osism manage images - How to customize? #1081

Open flyersa opened 3 months ago

flyersa commented 3 months ago

Hi,

maybe im to stupid to find this in the documentation. It seems like some container comes pre-bundled with the config such as /etc/images/cirros.yml

Where do i override this to only have them use my own configuration? There is a shitload of super old images by default which i dont really want. And yes i could install image manager myself from the pip, but i think it should be customizable with the bundled command, and i cant find anything in the docs about this, nether can i find this in my config repository.

berendt commented 3 months ago

It‘s not customizable at the moment. If you want customize the image defintions you have to install it on your own at the moment. You can use the --filter parameter to only import specific images when using the OSISM CLI.

We can make it possible to add custom image definitions in the configuration repository.

berendt commented 3 months ago

There is a shitload of super old images by default which i dont really want.

I disabled some old images (Debian 10, Ubuntu 20.04), disabled the Kubernetes CAPI images by default and removed some older Gardenlinux images.

berendt commented 2 months ago

This will be possible with 7.2.0 by placing files in /opt/manager/data.

osism manage images --images /data/cirros.yml --cloud admin

I will extend this to make it possible to add image definitions in the configuration repository, too. Probably this is already possible with something like osism manage images --images /opt/configuration/data/images/cirros.yml --cloud admin.