Change of mtu is not handled by reclass. Example interface:
```
br_ctl:
enabled: true
type: bridge
proto: static
mtu: 1450
address: ${_param:single_address}
gateway: ${_param:ctl_gateway}
netmask: ${_param:control_network_netmask}
use_interfaces:
- ${_param:primary_first_nic}
```
Currently when Salt starts setup-loopback-device service
systemd executes losetup command and even if it worked
successfully, systemd marks service as inactive(dead).
And Salt considers service as dead. In order to fix
this behavior, we need to add RemainAfterExit=true to
loopback systemd unit template.
Other changes:
.gitreview added
Related Prod: https://mirantis.jira.com/browse/PROD-11760
Change-Id: I6d0c3baf1c22d0a626ff1fd6aaab802c08fb029e
This enables a more fine tuned dpdk for better performance.
More details on pmd-rxq-affinity config:
http://docs.openvswitch.org/en/latest/howto/dpdk/
Change-Id: I630c6af94ff733619fb175f522fc515984862ff6
* RIL-267 Adding cpu governor and kernel module opts
* RIL-267 Adding cpu governor and kernel module opts
* RIL-267 Adding cpu governor and kernel module opts
Fix for https://mirantis.jira.com/browse/PROD-10786
Option "gid=kvm" is actually not needed now, since we didn't merge
change to apparmor config that will require this option.
Change-Id: Ib377444a01d097151d9a3a3b4a16e2ac75b868ab
- Disable sudo for kitchen tests
- No update grub on docker/lxc
- Avoid changing hostname in docker based tests
Change-Id: Ic93ecc4680fb9a44388f494259de28ea9e8a0fc0
To configure:
* set system.netconsole.enabled to true
* create system.netconsole.target dict
* set a record with IP address and MAC and interface as subdict
It works with both static and DHCP interfaces, and applies online.
You could use bash-scripting in netconsole.conf.
You could override the MAC.
See tests/pillar/system.sls for further information.
Change-Id: I1cbde47575eb5d32a34cd6d79a063f42dbea7643
Need to remove useless semicolon because it is not working properly.
For example:
root@node:~# grep http_proxy /etc/environment
http_proxy="http://10.0.0.1:8080";
root@node:~# env | grep http_proxy
http_proxy=http://10.0.0.1:8080";
root@node:~# curl http://google.com
curl: (7) Failed to connect to 10.0.0.1 port 80: Connection refused
root@node:~# export http_proxy=http://10.0.0.1:8080;
root@node:~# curl http://google.com
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="http://www.google.co.in/?gfe_rd=cr&ei=_WTaWKLuD4iI8QfC0azABw">here</A>.
</BODY></HTML>