Mirroring Infrastructure

[garloff]

As an operator, I want to be able to build artifacts and deploy and maintain SCS environments without access to public internet resources. Therefore software needs to be created allowing mirroring deb, pypi, container and ansible role/collection assets. Initially these assets need to be mirrored to internal mirrors delivering to our CI-CD systems.

Definition of Ready:

• Acceptance criteria are defined
• Acceptance criteria are clear and understood by the whole team

Definition of Done:

• [ ] infrastructure: prepare fully fledged mirror osism/issues#88
• Mirror our Git repositories to a local Git server (git.services.osism.tech) osism/issues#186
• [ ] Mirror our used Ansible/Container images/PyPi/APT packages to a local repository server (pulp.services.osism.tech)  osism/issues#187
• Create visualization for air gap installation osism/issues#330
• Prepare a list of Pulp alternatives osism/issues#348
• get github repo list from https://github.com/osism/github-manager osism-archive/public-services#28
• Create ansible-galaxy mirror software: https://github.com/osism/python-ansible-wormhole
• Create bandersnatch api frontend software: https://github.com/osism/python-banderctl
• Changes have been reviewed
• CI tests have run successfully
• Documentation has been updated
• Blogpost on Air-Gapped has been published
• Release Notes have been updated

[garloff]

Package mirrors (distro repos, language package mirrors), image mirrors, git(hub) mirrors, etc., also test this via testbed deployments.

[berendt]

Tim has started with it. but is now on vacation for the time being.

[berendt]

This is nearly finished. I will check the pending reviews the next days. Maybe this can be merge just before R3.

[fkr]

next step: re-evaluate pulp

[garloff]

January

[fkr]

It is planned to finalize this epic for R4, so that R4 ships with air gapped install support.

[tibeer]

@tibeer provide an overview of the status (open points, done stuff, etc.)

[tibeer]

Intermediate architecture view:

[tibeer]

ToDo's:

• Deploy infrastructure mirros
• Modify testbed to use squid: squid points to infrastructure mirrors
• Extend testbed with own mirror services (real airgap)

[fkr]

Split this epic into two:

1. Mirroring Infrastructure
2. Transparent usage of proxy and mirroring infrastructure

[berendt]

This needs to be prioritised. Should already be in the last release. At least the mirror infrastructure must be prepared.

[fkr]

Discussed in todays IaaS call: Blogpost will be updated to reflect the changed requirements and then is ready to go.

[fkr]

Blogpost has been updated by @tibeer. @fkr to review and merge today.