Automate your daily container workflows using Podman's systemd, top, auto-update, pull, and API-compatibility flags and commands.
via Enable Sysadmin https://ift.tt/yzsAltk
via Enable Sysadmin https://ift.tt/yzsAltk
Enable Sysadmin
5 cool features to automate Podman containers and pods
Automate your daily container workflows using Podman's systemd, top, auto-update, pull, and API-compatibility flags and commands.
Use iperf3 to troubleshoot bandwidth, timing, protocol, and other problems on your TCP/IP network.
via Enable Sysadmin https://ift.tt/E43oGRc
via Enable Sysadmin https://ift.tt/E43oGRc
Enable Sysadmin
Automate network testing with this open source Linux tool
Use iperf3 to troubleshoot bandwidth, timing, protocol, and other problems on your TCP/IP network.
Automation lets you work smarter, not harder. Learn Ansible basics so you're ready to start bringing automation into your workflows.
via Enable Sysadmin https://ift.tt/a4l6Iov
via Enable Sysadmin https://ift.tt/a4l6Iov
Enable Sysadmin
Ansible: A beginner's guide to IT automation
Automation lets you work smarter, not harder. Learn Ansible basics so you're ready to start bringing automation into your workflows.
docs_openshift_com_Differences_between_OpenShift_Container_Platform.pdf
134.3 KB
تفاوت های بین openshift 3 و openshift 4 .
نکته : در این مستند قویا توصیه شده . آپگرید از۳ انجام نشود و بطور مستقل پیاده سازی گردد . چرا که در نسخه جدید ، شاهد ویژگی های جدیدی در معماری هستیم .
در حوزه پشتیبانی storage ها هم شاهد تعغییراتی هستیم .
#openshift
نکته : در این مستند قویا توصیه شده . آپگرید از۳ انجام نشود و بطور مستقل پیاده سازی گردد . چرا که در نسخه جدید ، شاهد ویژگی های جدیدی در معماری هستیم .
در حوزه پشتیبانی storage ها هم شاهد تعغییراتی هستیم .
#openshift
👍2
https://linux-ip.net/html/routing-tables.html
Linux kernel 2.2 and 2.4 support multiple routing tables . Beyond the two commonly used routing tables (the local and main routing tables), the kernel supports up to 252 additional routing tables.
The multiple routing table system provides a flexible infrastructure on top of which to implement policy routing. By allowing multiple traditional routing tables (keyed primarily to destination address) to be combined with the routing policy database (RPDB) (keyed primarily to source address), the kernel supports a well-known and well-understood interface while simultaneously expanding and extending its routing capabilities. Each routing table still operates in the traditional and expected fashion. Linux simply allows you to choose from a number of routing tables, and to traverse routing tables in a user-definable sequence until a matching route is found.
Any given routing table can contain an arbitrary number of entries, each of which is keyed on the following characteristics (cf. Table 4.1, “Keys used for hash table lookups during route selection”)
destination address; a network or host address (primary key)
tos; Type of Service
scope
output interface
For practical purposes, this means that (even) a single routing table can contain multiple routes to the same destination if the ToS differs on each route or if the route applies to a different interface
Linux kernel 2.2 and 2.4 support multiple routing tables . Beyond the two commonly used routing tables (the local and main routing tables), the kernel supports up to 252 additional routing tables.
The multiple routing table system provides a flexible infrastructure on top of which to implement policy routing. By allowing multiple traditional routing tables (keyed primarily to destination address) to be combined with the routing policy database (RPDB) (keyed primarily to source address), the kernel supports a well-known and well-understood interface while simultaneously expanding and extending its routing capabilities. Each routing table still operates in the traditional and expected fashion. Linux simply allows you to choose from a number of routing tables, and to traverse routing tables in a user-definable sequence until a matching route is found.
Any given routing table can contain an arbitrary number of entries, each of which is keyed on the following characteristics (cf. Table 4.1, “Keys used for hash table lookups during route selection”)
destination address; a network or host address (primary key)
tos; Type of Service
scope
output interface
For practical purposes, this means that (even) a single routing table can contain multiple routes to the same destination if the ToS differs on each route or if the route applies to a different interface
It is straightforward to reconfigure ODF to add or remove Ceph functionalities or change parameters. Here's how to do it.
via Enable Sysadmin https://ift.tt/uZGqokh
via Enable Sysadmin https://ift.tt/uZGqokh
Enable Sysadmin
How to reconfigure Ceph storage in OpenShift Data Foundation
It is straightforward to reconfigure ODF to add or remove Ceph functionalities or change parameters. Here's how to do it.