SIMP 6.4: Map old/new files and capabilities
- 1 Description
- 2 Brief Summary of SIMP 6.4
- 3 Summary of SIMP ≥ 6.4 changes, by component
- 3.1 simp-cli commands
- 3.1.1 `simp environment [COMMAND]`
- 3.1.2 `simp config`
- 3.2 simp-environment (RPM)
- 3.3 simp-adapter (RPM)
- 3.4 simp-rsync (RPM)
- 3.5 simp-core (ISO)
- 3.6 simp-core (RPM)
- 3.7 simp-utils (RPM)
- 3.1 simp-cli commands
- 4 Mapped capabilities: SIMP ≤ 6.3 to SIMP ≥ 6.4
- 5 Further steps
- 6 Reference
Description
This article is an artifact of:
It tracks:
Capabilities/files/actions provided by the old (SIMP ≤ 6.3) versions of:
simp-environment (6.3.0)simp-rsync(6.2.1)simpthe ISO
auto.cfg
What / how / if these capabilities will be handled in the new (SIMP ≥ 6.4) ecosystem.
Goals:
Understand what responsibilities the components in the new SIMP ≥ 6.4 ecosystem will have
See article: SIMP 6.4+: Design `simp environment` command
Ensure no capabilities are missed during the transition
Document/create issues for anything we don't have a solution for
Brief Summary of SIMP 6.4
Starting with 6.4, SIMP's philosophy of handling SIMP Environments is changing:
Don't modify an actual environment, unless explicitly requested by the user
This prohibits unexpected automatic environment updates
"Explicitly requested by the user" includes the initial simp config after an ISO installation.
Summary of SIMP ≥ 6.4 changes, by component
This section summarizes the changes mapped in the sections above, to collect requirements for each component:
Legend:
WHITE | Mapped, but relevant Jira issues have not been researched |
|
|
ISSUE TBD: reason | Not Jira us |
YELLOW | Jira issues are still being researched for this mapping |
BLUE | Jira issues exist to address this mapping |
PRs have been submitted to address this mapping's Jira Issues | |
GREEN | Mapping + Jira Issues are complete |
simp-cli commands
`simp environment [COMMAND]`
Related article
Related article: SIMP 6.4+: Design `simp environment` command
| Mapping | Jira Issues | Notes |
|---|---|---|---|
| A1.2: | Secondary Env | |
A2.2: |
| OMNI Controller Secondary Env | |
A2.3: |
| Secondary Env | |
A3.2: (Related: A2.2) |
| OMNI Controller | |
| Puppet Env | ||
| Secondary Env | ||
| Writable Env | ||
A5.2: The |
| Secondary Env | |
A6.3: create new Extra/Omni environments on demand with simp environment new. |
| Puppet Env Secondary Env Writable Env | |
| A7.2: Environments can be removed with | Puppet Env Secondary Env
| |
B3.2: The
| DUPLICATE See A3.2 + children
| Puppet Env Secondary Env Writable Env | |
C1.2: The command
| Secondary Env Related to A1.2, but focuses on | ||
C2.1 The command
|
| Secondary Env | |
C3.2: The |
Secondary Env | ||
| C5.2: The | Secondary Env | |
D1.2: | Secondary Env |
`simp config`
| Mapping | Jira Issues | Notes |
|---|---|---|---|
A6.2: move the initial ISO install environment deploy logic into an early stage of | Uncomment |
|
simp-environment (RPM)
| Mapping | Jira Issues | Notes |
|---|---|---|---|
A1.1: simp-environment.spec installs all files to |
| ||
A2.1: simp-environment.spec still provides SELinux policies for
|
|
| |
| A3.1: | https://simp-project.atlassian.net/browse/SIMP-6614
|
|
| A4.1: (Related: E1) Consolidate %post's yum repo creation logic into the existing script simp-utils:scripts/sbin/updaterepos | See: E1.1 | |
| A4.1.1: The two have slight differences between them that should be carried over into | See: simp-utils RPM/ E1.2 | |
A4.1.2: Remove logic from RPM |
| ||
A5.1: remove cacertkey ensure logic from | |||
A6.1: remove `/usr/local/sbin/simp_rpm_helper --rpm_dir=%{prefix} --rpm_section='post' --rpm_status=$1 --preserve --target_dir='.'` from |
| ||
A7.1: remove `/usr/local/sbin/simp_rpm_helper --rpm_dir=%{prefix} --rpm_section='post' --rpm_status=$1 --preserve --target_dir='.'` from |
simp-adapter (RPM)
| Mapping | Jira Issues | Notes |
|---|---|---|---|
B1: keep this for now? (see discussion) | |||