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
Salt states/network supports "noifupdown" as a parameter for each interface.
Adjust linux.network.interface by extending the "interface_params".
Change-Id: Ie23b1a361a452dd0410871acdd0483806fb0bd92
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Signed-off-by: Charalampos Kominos <Charalampos.Kominos@enea.com>
Signed-off-by: Guillermo Herrero <Guillermo.Herrero@enea.com>
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
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
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
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
- skip_verify: {{ true if package.verify else false }}
will be true when package:verify is set to true
And that confuses.
"skip verify" means "skip any verify process" and package should
not be verified during installation
Currently, for disabling verification we use:
linux:
system:
package:
netapp-offload-tool:
verify: true
And anyone who is reading reclass model can be easily perplexed.
Patchset fixes that issue.
Change-Id: I38d60ff3dbe651e14898c4937fc7dddad36204be
Filip Pytloun
tomas kamm
chnyda
Consatntine Kalinovskiy
Andrei Danin
Michael Polenchuk
Dmitry Stremkouski
Jakub Pavlik
Martin Polreich
car-da
Dmitry Kalashnik
Petr Michalec
Oleg Bondarev
Bartosz Kupidura
Dennis Dmitriev
Ales Komarek
Serhiy Ovsianikov
Vasyl Saienko
Simon Pasquier
Olivier Bourdon
Jaymes Mosher
Aleš Komárek
Jakub Josef
Martin Polreich
Ales Komarek
Tomáš Kukrál
Yuriy Taraday
mcp-jenkins
Petr Michalec
Ondrej Smola