Change-Id: I1e190f1f5b34a049335efbecffad3dddf7c41644

Change-Id: Id9d9178ca7417df1b8a83110e92cf4a62907982d

Change-Id: Icbbd64144e6619eaa56e02c6c9362c7bcad9dd96

Change-Id: Ifa2787d76cf18e29f54583046349c071c5e9a25e

Pull Request for selinux.sls issue #125

Change-Id: Ib7f34360b7580cbc4260b826d1eb21d443801fa5

Change-Id: I64a93135daebe7d55430adc51de2c9186c7a5ad7

Change-Id: I715f78983c69084c81d4efd4a5625d5dfe0f276f

fix adding ca certs to ca trust on centos/redhat

Change-Id: Ida91f545cc705457d1bc567fbee483e14a202a3a

Change-Id: I3a2a0ac5518701b4c9de28437e9aefd1307ca01b

Change-Id: I7919ef2273185081d56a40af1e8fb4e602da41a2

Change-Id: I41f63e70ad4bd30dc478eeafeaf2823fa7508373

A minus at the end of a block prevents whitespace to be added.
In this particular case a new line between the last parameter in a section
and the next section is ommitted. The result looks like this:

[Section1]
Param1=Value
Param2=Value[Section2]
Param3=Value

Change-Id: I9faba3857f46f70ec0ddc380e6b84f72a5dc16e4

If ovs port is virtual, we use OVSIntPort to create it.
Otherwise it should be OVSPort.
I've added new key: ovs_port_type to not intersect with current
deployments and not hurt anyone.

I've updated doc to have an example of ovs peering patch.
Customer-Found

Change-Id: Ieddb5fcc02d410c3cc14c89737992690cb5f3975

* make all change in selinux mode persistent

* rework code to correspond with comments obtain from review about duplicity and useless code

* repair bad indent, remove bracket

Raise severity from warning to critical

Partial-Bug: PROD-15203
Change-Id: I32f19b5520bc200d61280da57f4ab5842b060454

Fixes: #120
Change-Id: Idc3b239418630a6d7cb8d5451726095c70fb6247

Current logic does not apply n_rxq, pmd_rxq_affinity and mtu
for a dpdk port in case it is attached directly to a bridge
(not bonded).
This patch makes formula apply parameters in both cases.

Change-Id: I5b19999b1ac8a80d1e31b266fede7dad0d7fd0d4

Change-Id: I67531b6ad15a2e96ee05178f17aae2504b3362bf

This workaround is required until salt with the patch [1] is not
used.

- use 'ifenslave' tool to enslave necessary interfaces only if bond
  interface has been changed
- install package that provides 'ifenslave' tool

[1] https://github.com/saltstack/salt/pull/39912

Change-Id: I65b607f26cf7319efb60f154951855d1334e1640

Non-destructive patch, won't affect anything because this
option is not used in any model yet.

Official guide for network.managed state provides an example:
bond0:
  network.managed:
    - type: bond
    - slaves: eth2 eth3
    - require:
      - network: eth2
      - network: eth3
    ...
without parameter: '- use:'

* add a new option 'require_interfaces' that allows to set
  '- require:' not only for 'bridge' interfaces
* using 'require_interfaces' allows to fix the order for states
  that create bonds (do not try to create bond0 before slave
  interfaces are configured!)
* using 'require_interfaces' allows to fix the order for states
  that create VLANs (do not try to create tagged interfaces before
  parent interface is created, it locks the parent interface
  creation!), example: bond0.2516 created before bond0
* using 'require_interfaces' allows to fix the order for states
  that depend on OVS interfaces

Change-Id: Id4539a7e24f2c55fb62afe5d47e485effc9a882b

Change-Id: I59297736406469e5314236cb40851d9a6f94386e

Add linux.network.systemd support

Change-Id: I430f9ed46ebd72ed66eeb9508e95d7c5970d678e

Change-Id: I94f09359f976ccd0f207277da52d20e659b36a69

The other disk alerts use predict_linear() to trigger before a disk gets
full but they don't trigger when the disk is effectively (or nearly)
full.

Change-Id: I8e6794d35bf96378ca3e3d527db4315d2b3a868d

Change-Id: I130d81ee954e001b7f79a25c5390c36bb37670d7

Change-Id: I2c5e4a75ac84099c063bb2c2259ace9c9c80635a