Add verification that directory pillar is not empty

fix(storage): Define LVM serive list for Debian 10

* Update file.sls

add replace

* Update file.sls

update replace

* Allow uid change

* feat(formula/group): enable the use of members in group.present

Add posibility to disable SELinux

Update job.sls

cron.absent   with the right user (default is root)

Fix missing json filter to support salt v2019.2

See salt issues #48309 #51925

Create user home parent dir if makedirs is True

Use json serializer instead of yaml to fix serialization of long lines

feature commit #186 - set transparent_hugepage as kernel parameter in…

Fix for issue #183 Compile issue in linux.system.repo

Add SELinux to README and test pillars (/linux/system/selinux.sls).

Fix for issue #179. In linux/system/profile.sls, profile scripts alwa…

Fix issue #177. In system/grub.sls we manage owner and permissions bu…

This is a fix for issue #174 regarding at and cron system modules. Cu…

* update lvm to create lv´s first

* add force: true  for "Wiping fs signature"

* update mount first

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