Content Comparison

1

Release Components

Identify components to be released, verify tests pass, push annotated tags. https://simp.readthedocs.io/en/latest/contributors_guide/maintenance/Tagging_and_Releasing_Components.html

3

Y

Y

Y

-

-

-

-

-

-

-

-

-

1-1

Identify components to release

1

Y

Y

Y

-

-

-

-

-

-

-

-

-

1-2

Release components

2

Y

Y

Y

-

-

-

-

-

-

-

-

-

2

Update simp-core pre-release tests

Update simp-core default, ipa, and install_from_tar acceptance test suites for release-impacting changes. This includes updating the nodesets for the supported OSs.

simp-core

5

Y

N

N

-

-

-

-

-

-

-

-

-

Tests will be executed for the appropriate OSs permutations in the nodeset, but separate tickets per OS should not be created.

2-1

Update tests and nodesets

4

Y

N

N

-

-

-

-

-

-

-

-

-

2-2

Review updates

1

Y

N

N

-

-

-

-

-

-

-

-

-

3

Update simp-core with released components

Update simp-core files (Puppetfile.pinned, metadata.json, src/assets/simp/build/simp.spec) and verify ISOs can be built and default acceptance test suite passes. Pushing to GitLab will execute the

simp-core

1

3

Y

Y

Y

-

-

-

-

-

-

-

-

-

3-1

Update files and test

2

Y

Y

Y

-

-

-

-

-

-

-

-

-

3-2

Review updates

1

Y

Y

Y

-

-

-

-

-

-

-

-

-

4

Create ISOs and publish the ISOs and tar files

simp-core

3

Y

Y

Y

-

-

-

-

-

-

-

-

-

Only the child should be replicated for OSs for which we build an ISO

4-1

Build ISO4

-

-

-

N

Y

Y

N

N

N

N

N

N

5

Verify installation from RPM

Run simp-core’s install_from_tar test

simp-core

4

Y

Y

Y

-

-

-

-

-

-

-

-

-

Only the child should be replicated for OSs for which there is a nodeset for the install_from_tar test

5-1

Execute test

See https://github.com/simp/simp-core/blob/master/spec/acceptance/suites/README.md for description of environment variables that can be set to point to the tar file

-

-

-

N

Y

Y

N

N

N

N

N

N

7

Create upgrade instructions

Document any steps that are needed outside of the generic upgrade instructions. 

simp-doc

N

Y

Y

N

N

N

N

N

N

First time we deliver an EL8 ISO, we will only have upgrade instructions for EL7

Manual tests for now. Will migrate to simp-integration_test for automated upgrade test.

7-1

Manually execute upgrade with FIPS enabled

7-2

Manually execute upgrade with FIPS disabled

7-2

Write upgrade instructions

7-3

Review instructions

Review the instructions for clarity, grammar, spelling, formatting, etc. Verification will be done in a separate ticket

8

Verify upgrade instructions

Verify upgrade instructions and make any necessary adjustments to them.

simp-doc

8-1

Execute instructions

8-2

Update instructions

8

Create initial SIMP changelog

simp-doc

8

Y

N

N

-

-

-

-

-

-

-

-

-

This addresses STIG updates and Compliance Markup modules changes.

Update changelog with bug fixes

4

'Upgrading SIMP' has an entry for the latest version and is correct

simp-doc

8-1

Create changelog

6

8-2

Review changes

2

9

Update Changelog for bug fixes

simp-doc

3

N

Y

Y

-

-

-

-

-

-

-

-

-

9-1

Identify bug fixes and update changelog

2

9-2

Review changes

1

5

SIMP server upgrade from RPM using the upgrade instructions.  Document any steps that are needed outside the ordinary upgrade.  Then, if there are additional steps, have someone else use the docs to do the upgrade to verify.Manual tests for now. Will migrate to simp-integration_test for automated upgrade test.

this should be done for servers in both FIPS and NOFIPS mode.

7

RPMs have been uploaded to packagecloud

in simp-core run

• SIMP_BEAKER_OS=oel beaker:suites[install_from_rpm]

• beaker:suites[install_from_rpm]

• beaker:suites[install_from_rpm,el6_server]

• SIMP_BEAKER_OS=oel beaker:suites[install_from_rpm,el6_server]

and then do it all again with BEAKER_fips=yes