1

Release Components

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

-

3

-

-

-

-

-

-

1.1

Identify components to release

-

1

-

-

-

-

-

-

1.2

Release components

1.1

2

-

-

-

-

-

-

2

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 the default, ipa, and simp_lite acceptance test suites pass.

You must set the SIMP_FULL_MATRIX variable to have all the tests run in a GitLab.

simp-core

1

3

-

-

-

-

-

-

2.1

Update files and build ISOs for supported OSs

You may need to update package lists for the ISO builds.

-

2

-

-

-

-

-

-

2.2

Verify acceptance tests

Verify the default, ipa, and simp_lite acceptance tests pass with new components. No major test revisions should be needed.

2.1

1

-

-

-

-

-

-

2.3

Review updates

Make sure to verify versions in Puppetfile.pinned, metdata.json and src/assets/simp/build/simp.spec.

2.2

1

-

-

-

-

-

-

3

Create test ISO, and publish the ISO and its tar file

simp-core

2

2

Y

Y

-

-

-

-

3.1

Build ISO

Use official RPM signing keys when the artifacts are to be published anywhere at simp-project.com.

-

1

-

-

-

-

-

-

3.2

Publish artifacts

Interim artifacts may be published to unstable folders at simp-project.com or other unofficial shared locations.

3.1

1

-

-

-

-

-

-

4

Validate ISO by building packer boxes

Use simp-packer to build SIMP server packer boxes. Basic bootstrap validation is done as part of the packer build.

3

Y

Y

-

-

-

-

4.1

Build BIOS boot box with FIPS enabled and encrypted disk

-

-

-

-

-

-

-

4.2

Build BIOS boot box with FIPS enabled and unencrypted disk

-

-

-

-

-

-

-

4.3

Build BIOS boot box with FIPS disabled and encrypted disk

-

-

-

-

-

-

-

4.4

Build BIOS boot box with FIPS disabled and unencrypted disk

-

-

-

-

-

-

-

4.5

Build UEFI boot box with FIPS enabled and encrypted disk

-

-

-

-

-

-

-

4.6

Build UEFI boot box with FIPS enabled and unencrypted disk

-

-

-

-

-

-

-

4.7

Build UEFI boot box with FIPS disabled and encrypted disk

-

-

-

-

-

-

-

4.8

Build UEFI boot box with FIPS disabled and unencrypted disk

-

-

-

-

-

-

-

5

Verify installation from RPMs in tar file

Run simp-core’s install_from_tar test

simp-core

2

-

-

-

-

-

-

-

This test can be omitted if there are no changes to component packaging since the previous candidate. Component behavior is already tested by the simp-core default suite with each simp-core check-in.

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

1

Y

Y

-

-

-

-

6

Update Changelog for bug fixes

simp-doc

2

3

-

-

-

-

-

-

6.1

Identify bug fixes and update changelog

-

2

-

-

-

-

-

-

6.2

Review changes

6.1

1

-

-

-

-

-

-

7

Dogfood released modules and assets

Use released modules in development environments that exercise as many of the modules as possible. Install RPMs of released assets on SIMP servers.

2

Y

Y

-

-

-

-

7.1

Deploy modules to development environments

Update Puppetfiles for development environments and deploy the modules.

-

-

-

-

-

-

7.2

Install asset RPMs on SIMP server

Install RPMs and watch for any RPM installation error messages.

-

-

-

-

-

-

7.3

Examine logs for issues

-

-

-

-

-

-

8

Benchmark with SCAP scan

This test is intended to find deficiencies in the enforced DISA STIG security settings for SIMP modules

Y

Y

-

-

-

-

8.1

Execute scan and analyze results

Execute the SCAP scan on a FIPS-enabled, disk-encrypted SIMP server packer box for which compliance has been enforced and then analyze the results for any SIMP deficiencies. Looking for system configuration that is not correctly configured for which the compliance report does not indicate an exception. Check may reveal component behavior or component compliance data that needs to be updated.

8.2

Create tickets for deficiencies

Create tickets for any component deficiencies found.