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

installation: CNF Installation (6) New installation process #2165

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

kosstennbl
Copy link
Collaborator

Description

Create new CNF installation process, that will support multiple deployments, be more comprehensible and easier to maintain.

Don't replace the old one yet, both installation methods should exist simultaneously

Issues:

Refs: #2161

svteb and others added 2 commits October 10, 2024 09:30
Refs: #2095
- In attempt to set up a different CNF the user gets a warning and is
blocked from proceeding.
- There were some changes necessary in the ran_spec.cr tests to forego
using two cnf_setups (auxiliary function was created to deploy 5g
through helm instead). This should be changed in the future when
cnf_manager.cr is rehauled.
- This change also removes two spec tests that were considered
unnecessary/non-conformant with the new approach to only having a
single CNF set up at any given time.
- Spec test to verify functionality was added.
- group manifests from several CNFs into one
  common_manifests.yaml file
- add functionality in cleanup.cr to remove this file
- depends on PR in helm library:
  cnf-testsuite/helm#4
- common_manifest functionality: used common_manifest
  instead of templates
- remove methods related to templates
- update generated manifest: add namespace to each
  resource

Signed-off-by: barmull <[email protected]>
Create new CNF installation process, that will support multiple deployments,
be more comprehensible and easier to maintain.
Don't replace the old one yet, both installation methods
should exist simultaneously

Refs: #2161
Signed-off-by: Konstantin Yarovoy <[email protected]>
@kosstennbl kosstennbl force-pushed the #2161-new-installation-process branch from 75b78ff to f37ad11 Compare October 15, 2024 08:27
@kosstennbl kosstennbl marked this pull request as draft October 15, 2024 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants