Skip to content

Conversation

@rjpmestre
Copy link

@rjpmestre rjpmestre commented Oct 7, 2025

This RFC proposes extending the autoinstallation profile mechanism to support multiple files per profile and storing them in the database (instead of relying on Cobbler).

See the rendered version.

Remove duplicated question and rephrasings
@rjpmestre rjpmestre force-pushed the multi-file_autoinstallation_support branch from b619470 to bcb4a41 Compare October 7, 2025 13:43
@rjpmestre rjpmestre self-assigned this Oct 7, 2025
- Number of files per type?
- File size?

- Should list the allowed file types (in the UI)?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If so, what are the allowed file types we want to support?

# Alternatives
[alternatives]: #alternatives

- Keep only one file per profile - too restrictive for complex setups.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could make sense to allow either a single normal file, either a compressed tgz file?
So, if we upload a compressed file, we will decompress it when running the profile to be used during the autoinstallation and we will store it in database as a single file too.
We can then avoid thinking about allowed file types and so on, being more flexible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants