- Add possibility to remove prereq. packages installation BEFORE
     * Crucial logic violation - if we don't have any repo\
       have them configured in wrong way - stage will always fail.
     * install prereq. packages after all - sounds stupid, but correct.
     * By default - it will still try to install prereq. We don't want to
       broke OLD logic.See readme, how-to overide such behaviour.
   - don't update cache per-repo - it's simply useless and may fail due p1.
     Run update only once - after all repos configured\reconfigured
   - Add new option at system:refresh_repos_meta - for case, when update
     should not be run in any case. By default - true.
   - remove 99proxies-salt-{{ name }} along with disabled repo
   - fix duplicate 'clean_file' option

Closes-Bug: PROD-15992 (PROD:15992)

Change-Id: I4b312f82f65be80e7726f62482978f68c25746a3

* Make system.repo more readable

Change-Id: I0f28e71f4b00422a70006559525e5be24c4cb065

related bug: PROD-21512

Change-Id: I874535dbc6882ad49f133999209ae6a4c3bde403

Fixes: PROD-21350

Change-Id: If5a4473296e4d2cb6a80cb7397ac38a66011f39d

nscd is recommended package for libpam-ldapd and libnss-ldapd, but
since we disabled Install-Recommends for apt in
https://gerrit.mcp.mirantis.net/14431 we need to specify this package in
linux formula.
nscd is a daemon which handles passwd, group and host lookups for
running programs and caches the results for the next query.

Change-Id: Ia17441da2b3072d943d0e9225721dc9921de2514

Change-Id: Id9ffc5cbbbb10fd6136d459ed461151a1800e857
related-bug: PROD-21205

PROD-20944

Change-Id: I9ef98b529d57171cf17c33597fd6af69d2f43a41

As we resign to develop full-stack solution to monitor cron jobs

This reverts commit 697ce4bf04.

Change-Id: Icab6008011141bb658c836897a05018dd6ce2984

Change-Id: I710b65decf6697d0bb5d21fc3fc2d332b78119c5
Closes-bug: PROD-21073

Change-Id: I6b21bed3dd2c632af8274769b562f366c4057b82
Closes-Prod: PROD-20090

Change-Id: I41f6e9c4feed93d03ac0479f9bd3626e48ad8063
Co-Authored-By: Michael Polenchuk <mpolenchuk@mirantis.com>
Closes-Bug: PROD-20729

We create custom hugepages mount point for KVM/DPDK with custom
parameters (ownership flags/hugepages size). Need to disable default
mount point, because it can be unexpectedly used by DPDK.

Change-Id: Ibee95422213260e544406391c7a0922f1a41c5c2
Closes-Bug: PROD-14325

- fixed pkgrepo.manage to use/prefer key_url for salt >= 2017.7
- updated syntax for key verificatoin
- fix, avoid curl for salt:// schema (as in #156)

Change-Id: I1b50c287a4030a9cefa1b819017d59cc5fb1c197

Commit totally broke all deployment CI job.

This reverts commit 24477c590b.

Change-Id: Idce0954f0bd363095069e91edc6941ca78b22c60

Change-Id: Id5b5a44f3dfbbdd60442fd2f273b72557fa9e191

Change-Id: I9e8464e3ee5ef28ca5eb7eb84e645e42fb6576cd
Closes-bug: PROD-20466

Change-Id: I2d374a589e18f38f91beac9514ff5bf3c034d637

Add support file.serialize in linux:system:file

Ensure presence of file to be serialized through one of the serializer modules
(see: https://docs.saltstack.com/en/latest/ref/serializers/all/index.html):

* Currently, 'key' was processed only for default repos
  * Remove double-definition
  * Re-use idempotent fix

Co-Authored-By: Dennis Dmitriev <ddmitriev@mirantis.com>

Change-Id: Ic733f671b39e7b4a8d8e0a83515b6b0632c3a41b

Workaround for fetching repo keys via proxy.

Fixed https apt proxy to same host as http

Change-Id: I016a0737e700162e41a39cf5643d5ee3c42c2cc5
Prod-Related: PROD-20467

Add check for existing key for idempotency.

routes: Skip network restart on 'noifupdown'

Change alerts names, severity and descriptions.

Closes-bug: PROD-19718
Change-Id: I238fbcd51cf48389b504ccb531ba9b2bc9dd4be6

- ldap
  - mkhomedir

* Fixing dependency for mkhomedir refresh
* Adding an ability to disable and enable moules

Prod-Related: EME-220

Change-Id: I94feab03cef82c515c9c430b9828653e87100425

Change-Id: I32c83d63e7f359704ab6cc77dec07a1617880fbb
Prod-Related: PROD-20137

The patch adds ability to configure variety logging options
for OVS. In order to configure OVS log options the below pillar
sctructure should be used:

  linux:
    network:
      openvswitch:
        enabled: true
        logging:
          enabled: true
          ovsdb:
            console: emer
            syslog: err
            file: info
            facility: local0
          vswitchd:
            console: emer
            syslog: err
            file: info
            facility: local1

Change-Id: I59ef0636447a974215d872259a26beb858495cfb
Related-PROD: PROD-19980

When we use the upstart, setup-loopback should be running as a
service to pass the salt linux.storage.loopback state
(service.running).

Change-Id: I9b19a94126b497d89bd6d05f43dca1df0304c0c6
Closes-bug: PROD-19847

Change-Id: I562455b281f1a92f674e859fa237b38f3432df7b
Closes-Bug: PROD-19728