Add Bind Mount Option

correction, wrong line.
added the possibility to set the dump and pass option

dump
    The dump value to be passed into the fstab, Default is 0
pass_num
    The pass value to be passed into the fstab, Default is 0

added the possibility to set the dump and pass option

dump
    The dump value to be passed into the fstab, Default is 0
pass_num
    The pass value to be passed into the fstab, Default is 0

Since salt now also supports LV extend and reduce, the option Force must be used with care.

The changes include that force is only set if the corresponding LV does not yet exist (check via Grains) in order to overwrite any FS signatures (Wiping fs signature).

If the LV already exists (check via Grains), Force is set to False unless this is explicitly set to True in the pillars.

The new syntax has been supported since ~2017.
From the docs, in case they change:

! New Style
test.random_hash:
  module.run:
    - test.random_hash:
      - size: 42
      - hash_type: sha256

! Legacy Style
test.random_hash:
  module.run:
    - size: 42
    - hash_type: sha256

The new syntax has been supported since ~2017.
From the docs, in case they change:

! New Style
test.random_hash:
  module.run:
    - test.random_hash:
      - size: 42
      - hash_type: sha256

! Legacy Style
test.random_hash:
  module.run:
    - size: 42
    - hash_type: sha256

See salt issues #48309 #51925

* update lvm to create lv´s first

* add force: true  for "Wiping fs signature"

* update mount first

* Add ability to disable some swap entities and enable others

Change-Id: Ic2f947f7b9fc6f29411a9171d68eb0836fce29ed
Related-task: #PROD-23150 (PROD:23150)

iteritems() was dropped in recent Python3 releases and items() is compatible
with Python 2.7.

This patch fixes issue with duplicate task IDs when multiple
loopback devices should be added, and they stored in the same
directory.

Change-Id: Iae0027b6ee187f5366967e667380dfb3eae232fc
Related-Prod: PROD-17620

Change-Id: If76a9d1aa3d23f3c38ec2135b42d63f64c4b1332

Change-Id: Iba8126cadc80c0de04baf3cc65d0868aa147bc01

Change-Id: I06994fec6f4771317f540d3e4339ff4460a5a493

Change-Id: I6d1ba01efff16d41c5e91973d46aaaa7ea3caca5

Change-Id: I3a6a8fc227cb9abd785b342584038e34d57a4175

Change-Id: I1c35eb045a46b95f75c7101567d4c4f340b787ab

Change-Id: I92b5e7b09f6478c190e96819aa279022364f1730

Ability to create partitions on empty disks.

Change-Id: I0a71da9d62d8f7df3fa03e3f34d49bad6988ba6d

Usually you need define order for mounting volumes in one path like mount first /opt and then /opt/cms etc.

Change-Id: I556ab82a1dc0ce711958404165e419275ff5ce19

Change-Id: I9967f867b8695e4a5bc4759ca81eebe5ef2309c1

Change-Id: I93e135a9366c1f7c93397dfa0c342428fb64eb1c

Change-Id: Ib4cb70615af8da2f1037b0a43520c215365979ba

"names" makes a separate call to the package management frontend to
install each package, whereas "pkgs" makes just a single call so that it
improves performance.

This state allows to configure loopback device(s). This isn't meant to
be used in production but offers a cheap way to test Cinder with LVM
volumes.