Prod-Related: PROD-20747

Change-Id: Id7822963ab45ff7db3252f5329a9376aa4bf10d6

Change-Id: I602338811610d4ff08dfb8b2b3aed9dc46f5b3b0

- LOG_FILE
  - LOG_LEVEL
  - LOG_LEVEL_LOGFILE

Change-Id: Ic8c0c3bb2a4a80ba0590ca79d8e491dd4f840897

[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

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: I685de4207f1f7f17264cc4ad2d81c3348ca20074

Change-Id: I3ddfb01dd785f559e4bbf197bc164b8d0389a4f1

PROD-16375

Change-Id: I758d38701cdf0e1cc6fa99c38192de2f9052468c

Change-Id: I5c88d22589ec1fa6a9806c1a625b752dd4fc8b54

Change-Id: I8dee93ffd4441391a5b26ba2c5b46e43357a0ca7

Change-Id: I336b0825712218e2381e1654251765a24581da00

Example:

parameters:
  salt:
    control:
      size: #RAM 4096,8192,16384,32768,65536
        openstack.control:
          cpu: 8
          ram: 32768
          disk_profile: small_two_disks
          net_profile: default

  virt:
    disk:
      small_two_disks:
        - system:
            size: 50000
            image: http:/path/to/image.qcow2
        - cinder-volume:
            size: 50000

Change-Id: Ie092b77627cb2b1d36ba4b7a2a7d749ad91881c8

Exposing CA keys in a mine creates a security flaw, thus such
should be avoided.
This change removes code responsible for putting and retrieving
CA key from a mine and changes the ca.sls state to allow configuring
where CA cert and its key would be generated as well as their owners.

Fixes PROD-13439

Change-Id: I6d78b13dcb3754c51606edd7e2d8158e128244a4

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: I73a4a14734651f6483fae169a2290e9c5b377d76

Change-Id: Ic64656c6fc3d4f561226d884b8bfb535dd537e14

Change-Id: I2aba1213b1dda46aee929b8ea583c41316e3eb0b