You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: