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

Devfile registry air gap/offline installation #329

Closed
4 tasks done
elsony opened this issue Jan 27, 2021 · 7 comments
Closed
4 tasks done

Devfile registry air gap/offline installation #329

elsony opened this issue Jan 27, 2021 · 7 comments
Assignees
Labels
2023Q3 area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues R&D

Comments

@elsony
Copy link
Contributor

elsony commented Jan 27, 2021

A devfile refers to various resources, e.g. container images, projects, and starter projects. The current devfile registry currently does not store those supporting resources as part of the registry. This means that the user will need to have access to those resources when using those devfiles. This item adds support to install a devfile registry in an air-gapped environment.

Design doc: https://docs.google.com/document/d/15PpUGiWOXjfQ5GtJFPHp0cG73jtpmw1H9AkCrnJVD2E/edit?usp=sharing

Acceptance criteria:

  1. Implement according to the design on the design doc so that the offline installation is self-contained and can be installed without internet access
  2. Testing to verify the implementation according to the design doc
  3. Document on how to do air gap installation

Related Issues
Child issues for this EPIC:

@elsony elsony added kind/epic A high level requirement that can/should be split into smaller issues area/registry Devfile registry for stacks and infrastructure labels Jan 27, 2021
@rkratky
Copy link
Collaborator

rkratky commented Mar 26, 2021

Docs JIRA issue: https://issues.redhat.com/browse/RHDEVDOCS-2872

@nickboldt
Copy link

Support for offline/airgap is a vital requirement for getting any of this new registry stuff into CRW, as CRW registry builds are by default offline so they can be used behind an airgap/proxy.

Please don't forget about this requirement when designing how to build your registries.

@kim-tsao
Copy link
Contributor

We should also review how the devfile library can access offline parent resources from the registry, especially since a git clone is being done

@michael-valdron
Copy link
Member

Adding this to triage as there seems to be criteria still being worked out.

cc: @elsony

@elsony
Copy link
Contributor Author

elsony commented Jul 11, 2023

We should also review how the devfile library can access offline parent resources from the registry, especially since a git clone is being done

It is already documented in the design doc. See section 1 i.

@elsony
Copy link
Contributor Author

elsony commented Jul 11, 2023

Adding this to triage as there seems to be criteria still being worked out.

Added acceptance criteria

@mike-hoang
Copy link
Contributor

#1203 - merged which now allows starter projects to be downloaded and the devfiles updated to use the offline starter projects

#1220 - will take into consideration all the uri paths and download them to the stack directory

devfile/registry#197 - entry point for creating the offline registry image and will be merged after all the child tasks are completed

@mike-hoang mike-hoang moved this from To Do 📝 to In Progress 🚧 in Devfile Project Aug 28, 2023
@mike-hoang mike-hoang moved this from In Progress 🚧 to Done ✅ in Devfile Project Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2023Q3 area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues R&D
Projects
Status: Done ✅
Development

No branches or pull requests

6 participants