SIMP 6.3.3-0

Table of Contents

Release Notes for SIMP 6.3.3-0

• JIRA Release Page RELEASED
• Work is proceeding on the 6.3.X Branch of simp-core

How to use this page

• Go to the row of your module
• If the "proposed version" is green, then it has been released and tagged
• If the "proposed version" is blue, verify that the tests have all passed, bold the text
• If the "proposed version" is bold, tag and release the component, and color the column green

Component Selection

Release Testing Procedure

The full release testing procedure is documented in the Official SIMP Docs.

Puppet Versions Testing

Puppet version for GitLab and TravisCI

Puppet modules will be tested in GitLab and TravisCI with the following versions:

Puppet version for simp-core (integration) and SIMP ISO testing

OS Versions For Testing

• SIMP acceptance tests will be executed with the following OS versions:
  • CentOS 7.5
  • CentOS 6.10
  • RedHat 7.5
  • RedHat 6.10
  • OracleLinux 7.5
  • OracleLinux 6.10
• SIMP 6.3.3-0 ISOs for CentOS 7.5 and CentOS 6.10 will be built and tested.
• If licenses are available, SIMP 6.3.3-0 ISOs for RedHat 7.5 and RedHat 6.10 will be built and tested.

Tests - New/Changed Features

The tests in this section focus on new features or major, SIMP-wide changes.

Legend:

- Means this version needs to be tested

- This version does not need to be tested.

- Testing probably sufficient from other versions.

- Testing has failed.

- Testing completed and Passed.

blank - This test is not OS specific

	Component	Required Tasks	Test	EL7	EL6	OL7	OL6	RH7	RH6	Status	Notes
1	simp-core		Verify Puppet File matches release versions							SIMP-6154 - Getting issue details... STATUS	This must be completed before any other tests are done
2	installation		Verify installation from ISO							SIMP-6166 - Getting issue details... STATUS SIMP-6167 - Getting issue details... STATUS
3	installation		Verify installation from RPM
4	simp-core		Create and verify Changelog.rst							SIMP-6154 - Getting issue details... STATUS	This addresses STIG updates and Compliance Markup modules changes.
5	simp-doc,		'Upgrading SIMP' has an entry for the latest version and is correct							SIMP-6155 - Getting issue details... STATUS
6	simp-integration_test		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.							N/A Tiny change and no ISO updates	See simp-integration_test for automated upgrade test. this should be done for servers in both FIPS and NOFIPS mode.
7	RPMs and Released Modules		Dogfooding							SIMP-6157 - Getting issue details... STATUS	Or "drink your own home brew", which ever you prefer. CentOS 7: SIMP server and SIMP client CentOS 6: SIMP client only
8	Final RPM testing	RPMs have been uploaded to packagecloud	Run the simp-core install_from_rpm test and versify that it passes.   This will pull the packages from packagecloud.io and do an install.								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
9	Puppet Forge Testing	After modules have been tag with an annotated tag	run the simp-core test install_from_core_module test to test the modules pushed to Puppet Forge							N/A	in simp-core run beaker:suites[install_from_core_module] SIMP_BEAKER_OS=oel beaker:suites[install_from_core_module] beaker:suites[install_from_core_module,el6_server] SIMP_BEAKER_OS=oel beaker:suites[install_from_core_module,el6_server] and then do it all again with BEAKER_fips=yes

Tests - Regression/Integration Testing

The tests in this section are regression tests to ensure unmodified capabilities still function.  These tests should use the packer boxes created in the New/Changed Feature tests, were applicable.

Open Issues Assigned to Release