System modules are enables by default. But they should only be enables if
in pillars defined and supported by os_family.

Support for Redhat os_family systems is missing in at and cron #174

Ovs native bonding

Match server hostname in Open_vSwitch table

Multi-Factor Authentication (MFA) for sshd+PAM
https://duo.com/product/multi-factor-authentication-mfa

Related-Prod: PROD-24422
Change-Id: Iddec5a5e99e7db5d7f173ad939d3fd0cac1cd22b

Linux bridges are automatically set UP when
any parent interface is UP.

But for OVS bridges it doesn't work.

For dpdk and non-dpdk bridges, always create a
config file in /etc/network/interfaces.u/ and
bring the bridge interface up after it is configured,
even if it doesn't have IP address.

Change-Id: I92888ce0d373e412dfb7ed2e2398c0d4d008e301
Closes-Bug: https://mirantis.jira.com/browse/PROD-24343

Issue description:

  PXE interfaces, which are used by salt should not be restarted
during salt calls, otherwise communication between salt master and
salt minion would be interrupted.
  Therefore it is possible to specify "noifupdown: True" in pillars
for this interface or group of interfaces, which are used for PXE
network.
  This pillar structure will remain until one removes it manualy.
  It is not possible to remove it during deploy and enforce network
state without touching the model.

  It is possible to override pillars from CLI like:
  # salt ctl01* state.apply linux.network.interface \
    pillar='{"linux":{"network":{"interface":{"ens3":{"noifupdown":True}}}}}'

  However it is not easy/possible to predict all interfaces for PXE
network.

Solution:
  Provide global noifupdown pillar value check.
  If it exists, noifupdown will take effect and not otherwise.
  So our deployment would have next steps:
  - Execute: linux.network.interface pillar='{"linux":{"network":{"noifupdown":True}}}'
  - Reboot node to enable kernel params like hugepages etc.
  - Execute: linux.network.interface with no params to ensure PXE.

Pipelines may pass this parameter to control noifupdown behavior.

Change-Id: I8863f972c7805e4bf4f9e104d6c0ddf055c39cb1

Change-Id: Ifb45b2cf72d71caa9c8a63f8e7684fd15b81e450
Implements: jira/CLOUDB-487
Signed-off-by: Gabor Orosz <gabor.orosz@ericsson.com>

change logic when I define user.gid

Current thresholds don't matche real warning/minor values for
the time_squeeze numbers. As a result we have false positive.

Change-Id: I6990c101fe671c05d75d0640fd6799667b5f3fa1
Related-PROD: PROD-24406 (PROD:24406)

- in inspec >= 3.0.0 there are changes in schema
	  which require to have tests/integration dir
	  to contain tests, otherwise fails
	- this is temporary workaround until we decide
	  proper fix

Change-Id: Ie251c093e3d66532d027a47a56272936cf3cbcb3

Change-Id: I3338950ed3726a750149d849d33813b0eeed50c0

* Add ability to disable some swap entities and enable others

Change-Id: Ic2f947f7b9fc6f29411a9171d68eb0836fce29ed
Related-task: #PROD-23150 (PROD:23150)

Useful during environment setup.

Change-Id: Ic8d4d82cc6f6afb0ac2a6e4285c3b681bb895b6d

This typo mistake affects behavior of user.present module function
as it uses 'useradd' linux utility under the hood.
Missing USERGROUPS_ENAB parameter == do not create user groups by default.
This change in behavior of useradd util breaks all states, which are relaying
on creation of user group during new user creation procedure, e.g. set up
cassandra backups.

Change-Id: Ie17aae58fc6673b9c5d53bb68f681446f30d0a1a
Related-bug: PROD-23741

https://gerrit.mcp.mirantis.com/25351/ was merged but linux.system.shell
state wasn't included into init.yml and was never used.

This commit fixes this.

Related-Prod: PROD-23581

Change-Id: I89e09247dd2566b8a5b0c0e67e8ca9c789ed57f6

CIS 5.4.1.4 should be configured in /etc/default/useradd

cis-5-4-1-4.yml attempts to configure this item in
pillar that relates to /etc/login.defs and should be removed.

Related-Prod: PROD-23600

Change-Id: Iea93a54a44df919c07001fc02e3551276ef9583c

To simplify filtering in Kibana change
systemd.source prefix to record field "source".

Change-Id: I7729ae6721a1050a938370a588d35313f91f971a
Related-bug: PROD-21827 (PROD:21827)

Previous implementation was not able to add port 'dpdk0' to bridge
'br-dpdk0' since both matches 'grep' condition. To fix this we need to
look for port in a particular bridge

Change-Id: Ie83cebc3ab73c45a48f68fae2d6f474743215908

Change-Id: Ia8690d3968aa6c8491ec62b73f78afd6b2361c60

* 5.4.4 Ensure default user umask is 027 or more restrictive (Scored)

Change-Id: Idc219e7f6e8ab4b7e3d24a36f95f8aab4eff3160
Related-Prod: PROD-18386

Change-Id: If1bbd97b5719c53193f6287c4a025e6ef0dafbb0
Related-Prod: PROD-18386

* CIS 5.4.1.1 Ensure password expiration is 90 days or less (Scored)
* CIS 5.4.1.2 Ensure minimum days between password changes is 7 or more (Scored)
* CIS 5.4.1.3 Ensure password expiration warning days is 7 or more (Scored)
* CIS 5.4.1.4 Ensure inactive password lock is 30 days or less (Scored)

Related-Prod: PROD-18386

Change-Id: I42697c31823c631acb1528ca917b39c069fb72bf

The following parameters defined in /etc/login.defs can
be overridden per-user:

* PASS_MAX_DAYS
* PASS_MIN_DAYS
* PASS_WARN_DAYS
* INACTIVE

Related-Prod: PROD-18386

Change-Id: I5b182128f9dd8a043b48fb86e61febb2fd5c7e0a

* apt tool sensetive for tralling spaces, and 2 files
    aka:
    cat -E mcp_saltstack
    $
    Package: libsodium18$
    Pin: release o=SaltStack$
    Pin-Priority: 50$
      $
    Package: *$
    Pin: release o=SaltStack$
    Pin-Priority: 1100$
      $
    # VS
    cat -E mcp_saltstack
    $
    Package: libsodium18$
    Pin: release o=SaltStack$
    Pin-Priority: 50$
    $
    Package: *$
    Pin: release o=SaltStack$
    Pin-Priority: 1100$
    $
    Make's different logic for apt

Change-Id: Ia5fdbe319a65b0fa017c8c065905db1837f9f982

Prod-Related: EME-405

Change-Id: Id9a8ebefb227c4b0a99d8cdd955c39401720bbee

as it will fail because dbus service is not running

Change-Id: I498f5b09b146c643f4d53ab0cb65146274f12b5d

* Ubuntu pinning params allow to be used
     multiply times. In same time, old `list`
     format now allowing to be predictable
     iterated inside jinja

Related-Bug: PROD-21604 (PROD:21604)

Change-Id: If1c0f0f834a296b9a19d0af5fc7673c9229a7ac5

Fixes: PROD-23149 (PROD:23149)

Change-Id: I14c68a0a519a63951571f966fae72fd01ec2e556

Change-Id: Ibbbb99511544ab3bb1532b71942fea15ae0f34a1