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

AIAP: Document the requirements for the infrastructure builder image #651

Open
ian-howell opened this issue Oct 6, 2021 · 4 comments
Open
Assignees
Labels
enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release
Milestone

Comments

@ian-howell
Copy link
Contributor

Problem description (if applicable)
Airship-in-a-Pod uses the infra-builder container, which sets up 3 VMs (one used as the ephemeral node, one as a control plane node, and one as a worker node). While this works great for basic testing, we would like to be able to specify different architectures for different needs (e.g. 3 control planes and 2 workers).

AIAP is currently configured such that the task containers are decoupled, i.e. there is nothing stopping a user from swapping out the infra-builder image with their own image. Doing so allows the above desired behavior, however there is currently no documentation on the requirements for the infra-builder container.

Proposed change
Update the AIAP documentation to include the requirements for the infra-builder. This should include pre-reqs (such as required services) as well as outputs (VMs). Furthermore, this should include basic instructions for copying and modifying the default infra-builder image.

This is likely dependent on #648, since fixing it will simplify creating multi-node containers

@ian-howell ian-howell added enhancement New feature or request triage Needs evaluation by project members labels Oct 6, 2021
@jezogwza jezogwza added this to the v2.1 milestone Oct 13, 2021
@jezogwza jezogwza added priority/critical Items critical to be implemented, usually by the next release and removed triage Needs evaluation by project members labels Oct 13, 2021
@pallavgupta
Copy link
Contributor

I think this issue is dependent on issue #652

@lb4368 lb4368 modified the milestones: v2.1, v2.2 Oct 27, 2021
@gtsteffaniak
Copy link

Could you assign to me?

@gtsteffaniak
Copy link

@gtsteffaniak
Copy link

@eak13 This PS is still active and needs reviews, but I have moved away from the feature team working on this. Someone else may need to take ownership for merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release
Projects
None yet
Development

No branches or pull requests

5 participants