Related PROD-23040 (PROD:23040)

Change-Id: I6cf2cb5ff66dcffb1532343a58416fb242703322

Spawning AArch64 VMs using salt.control.virt requires a few extra
domain configuration items to be configurable:
- libvirt xml: pass loader param to vm
  Based on upstream commit [1].
- libvirt xml: pass virt machine type
- libvirt xml: pass cpu mode to vm
- virt module: Allow NVRAM unlinking on DOM undefine
  UEFI-enabled VMs usually have pflash (NVRAM) devices attached,
  which require one additional libvirt flag to be passed at 'undefine'.
  This is usually the case for AArch64 (arm64) VMs, where AAVMF (AA64
  UEFI) is the only supported guest bootloader.

[1] https://github.com/saltstack/salt/commit/9cace9adb

Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>

This patchset obsoletes switching from "dhcp" to "static" during
deployment.

Example pillars:
salt:
  control:
    enabled: true
    virt_enabled: true
    size:
      small:
        cpu: 1
        ram: 1
    cluster:
      infra:
        domain: example.com
        engine: virt
        config:
          engine: salt
          host: master.domain.com
        cloud_init:
          network_data:
            links:
            - id: ens2
              name: ens2
              type: phy
          user_data:
            disable_ec2_metadata: true
            resize_rootfs: True
            timezone: UTC
            ssh_deletekeys: True
            ssh_genkeytypes: ['rsa', 'dsa', 'ecdsa']
            ssh_svcname: ssh
            locale: en_US.UTF-8
            disable_root: true
            apt_preserve_sources_list: false
            apt:
              sources_list: ""
              sources:
                ubuntu.list:
                  source: ${linux:system:repo:ubuntu:source}
                mcp_saltstack.list:
                  source: ${linux:system:repo:mcp_saltstack:source}
        node:
          ctl01:
            provider: kvm01.example.com
            image: ubuntu-16.04.qcow2
            size: small
            cloud_init:
              network_data:
                networks:
                - id: private-ipv4
                  ip_address: 192.168.0.161
                  link: ens2
                  netmask: 255.255.255.0
                  routes:
                  - gateway: 192.168.0.1
                    netmask: 0.0.0.0
                    network: 0.0.0.0
                  type: ipv4

Change-Id: I087518404c61e0bab2303e40957bacca94692102

Change-Id: I3ac728f84a0a63973ca7d90a679c096378eee7c8
Related-PROD: https://mirantis.jira.com/browse/PROD-20392

Change-Id: Ia9410364a82ac84889b80b30380ec5f897c7165c

Change-Id: Iea79e2c8c9f29ddc5903a97c104e013878f63cd7

Prod-Related: PROD-20747

Change-Id: Id7822963ab45ff7db3252f5329a9376aa4bf10d6

Change-Id: I602338811610d4ff08dfb8b2b3aed9dc46f5b3b0

The patch adds ability to configure REDIS as cache
backed for salt-master to be used as distibuted cache
further.

Change-Id: I62a29713c23ad3f591f6e937bfc5b13eba92f402
Related-PROD: PROD-20581

Change-Id: I9d834d67e29d7c6d0b11599b0b543427cf1d7706

related to bug: PROD-20139

Change-Id: I32fee91f22e0963ec60de63b4c6e020df92f9f3b

- LOG_FILE
  - LOG_LEVEL
  - LOG_LEVEL_LOGFILE

Change-Id: Ic8c0c3bb2a4a80ba0590ca79d8e491dd4f840897

Change-Id: I28bbc7a6b5810dfb56b8391a557aecd1fa523385

[Fix] Doc

Issue: - It is not possible to pass [R]andom [N]umber [G]enerator
         device to libvirt guest xml in order to control entropy.

       - Doc has no information on how to provision vms using salt

Solution: - Pass rng parameters via kwargs from node: pillar
            Attach rng xml object to generated xml.

          - Provide with an example

Prod-Related: PROD-19214
Customer-Found
Change-Id: Iea111f2d927edf46f06bb7ccfad06d37b752fba9

Change-Id: Idf6c18597a222e6c1b60bf940eadb1d6d8a611c7

PROD-18191

Change-Id: I15c2cc66f0c0010408863b46c0dccf84730f31d9

Change-Id: Idf6a88ca1ac0b6b5fd3976f2e27d8cb24d7a1b3d

salt-minion started via upstart is not using /etc/environment to
source variables therefore is not using system wide http_proxy parameters if
they are set there. With this patch if salt.minion.env_vars is set to engine:
file salt will set envvars in /etc/default/salt-minion and will use them for
all commands executed remotely via salt. Since /etc/default is not used on
systems with systemd override for salt-minion to use /etc/environmnet will be
set.

Change-Id: Icfe122de2486a83820a0bd2e2aeea4be3796c6aa
Closes-bug: PROD-16676

Change-Id: I96e16a3b203f9b3c9c150db1cb85e966bd14b573

Change-Id: I685de4207f1f7f17264cc4ad2d81c3348ca20074

Change-Id: I3ddfb01dd785f559e4bbf197bc164b8d0389a4f1

Change-Id: I5c88d22589ec1fa6a9806c1a625b752dd4fc8b54

Change-Id: I336b0825712218e2381e1654251765a24581da00

Change-Id: Ic9decbeaf57e9aba2f95c3dd616393dc32763fcc

Change-Id: Ifac3f5e03099e8190db0a3af62a7be1f762f87be

Change-Id: Ia3b1e93e5f0b3da7097a285122d24c5b1d2b20e2

Change-Id: I07e86cb5d132a83b2460deda08b8a7e65f379d33

This is useful when using proxies. The default Tornado backend does not
utilize proxy environment variables and isn't able to set no_proxy variable.

Change-Id: I4a51c6fc9abe65d46ed4f3adeb30f7a25337857e

Change-Id: I9e48e113656dd9f1ce644e98650276b36e444009

Change-Id: I3f8ada34bf7e6e356bf6805d98eb0fa4bd66d8d3

Change-Id: I73a4a14734651f6483fae169a2290e9c5b377d76

Change-Id: Ic64656c6fc3d4f561226d884b8bfb535dd537e14

Terse output is not enough for debugging.

Change-Id: Ida9a4ef0a2ad053fc370d3833d716d9e8d38d814

This option can configure default output of state calls. Terse (default
option) will make each call to be on single line and make salt output
better.

Change-Id: Id0987561e34a84fb26a796729d6ab3de3b9ae8e5

Change-Id: I2aba1213b1dda46aee929b8ea583c41316e3eb0b

source:engine metadata created - defaults to pkg
installation, pip installation alternative added