Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for outputting OSTree-based Execution Environments #269

Open
shanemcd opened this issue Aug 11, 2021 · 0 comments
Open

Add support for outputting OSTree-based Execution Environments #269

shanemcd opened this issue Aug 11, 2021 · 0 comments

Comments

@shanemcd
Copy link
Member

Context

While #268 exists for the purposes of operating within the confines of existing processes and systems, Ansible Builder should ideally produce artifacts that are ready to run / deploy.

While container-based Execution Environments work for the vast majority of use cases, there are scenarios where they will not be suitable. (See: RHEL for Edge)

Proposal

We should investigate the possibility of generating OSTree-based Execution Environments. OSTree is the the technology at the heart of Red Hat CoreOS (and formerly Project Atomic). Think of it as git for filesystems.

Building a custom OSTree based image is essentially what RHEL for Edge is.

The tools provided for producing these images live under the umbrella name of OSBuild. OSBuild is comprised of:

We've had a brief conversation with the OSBuild team about both a short-term solution and potentially a deeper integration long-term.

The short-term solution would be adding support to OSBuild to build on top of a custom OSTree commit. This can be thought of as a "base image" in some ways.

The long-term solution might be the ability to upload an execution-environment.yml to OSBuild / Image Builder and have it produce an OSTree-based Execution Environment.

Potentially Helpful links

I realize that some of this is very hand-wavy and forward-looking. We can further expand upon this idea as things move forward, but I wanted to go ahead and create this issue as a place for us to begin a discussion.

@samdoran samdoran added the needs_triage New item that needs to be triaged label Nov 1, 2021
@samdoran samdoran removed the needs_triage New item that needs to be triaged label Nov 16, 2021
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

No branches or pull requests

2 participants