adds VM fulfillment architecture documentation#19
Open
mhrivnak wants to merge 2 commits intoosac-project:mainfrom
Open
adds VM fulfillment architecture documentation#19mhrivnak wants to merge 2 commits intoosac-project:mainfrom
mhrivnak wants to merge 2 commits intoosac-project:mainfrom
Conversation
Documents the complete VM fulfillment architecture including the Fulfillment Service API, OSAC Controller, Ansible Automation Platform integration, VM templates, and execution flow. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Adds info about when UserDefinedNetworks get created Co-authored-by: Adrien Gentil <adrien.gentil@free.fr>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the complete VM fulfillment architecture including the Fulfillment Service API, OSAC Controller, Ansible integration, VM templates, and execution flow.
This documents the current status only, and I assume we'll update it as we make upcoming changes to the API and implementation.