Linux command line for you and me Documentation Release 0.1 Kushal Das Sep 01, 2023 Contents: 1 Shell commands 1 1.1 Terminal emulators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . so please do not get confused at the date.) 1 Linux command line for you and me Documentation, Release 0.1 $ date -u Mon May 21 01:43:47 UTC 2018 If you want to see yesterday’s date, or a 10 days ago (continues on next page) 2 Chapter 1. Shell commands Linux command line for you and me Documentation, Release 0.1 (continued from previous page) July 2017 Su Mo Tu We Th Fr Sa 1 2 3 4 5 6 7 8 9 10 11 12 13

com/kushaldas/verybad $ cd verybad $ cargo build --release ... $ ls -l target/release/verybad -rwxrwxr-x. 2 almalinux almalinux 8193040 Mar 16 04:21 target/release/verybad Now, we will copy the executable to /usr/sbin and also copy the service file and then start & enable the service. $ sudo cp ./target/release/verybad /usr/sbin/ $ sudo cp verybad.service /etc/systemd/system/ $ sudo mkdir -p /web/amazing $ of the Operating system via /getos call, which internally returning us the content of the /etc/os-release file. $ curl http://localhost:8000/getos NAME="Fedora Linux" VERSION="35 (Cloud Edition)" ID=fedora

i Approved for Public Release; Distribution Unlimited. 14-0391ii Executive Summary The Department of Defense (DoD) needs an acquisition framework for information technology (IT) that all of the DoD’s IT acquisition challenges, but offers a set of principles that can help reduce cycle times and risks to deliver IT in a complex environment. “The US joint force will be smaller and never know less than on the day you begin your new project. Each incremental delivery / review cycle adds knowledge and provides insights that the team could have never known when initial requirements

pre-production environments. The changes can then, with the approval of the oper- ation teams or release managers, get deployed to production. This aspect of CD is an answer to the problem of poor visibility 5]. Argo CD was created to fill a need in the company’s infrastructure. Later, Intuit decided to release the Argo Project toolsets as open source. Since then, many companies, including Akuity, BlackRock parameters defined in the templates, and Helm injects these values into the manifests to create a release. A release is the end- Chapter 3 – Templating The Path to GitOps | 20 state representation of the YAML

to 2.2.1 2.4 - 2.6 Beyond Outro Stability Release stability Every single release since 2.0.0 has had issues Some bugs and some human mistakes in the release process Always running latest is the cloud-native stable release in the 2.x train Richard Hartmann & Frederic Branczyk @TwitchiH & @fredbrancz Prometheus Deep Dive Introduction Intro 2.0 to 2.2.1 2.4 - 2.6 Beyond Outro Release cycle Fixed release cycle cycle Every six weeks, we mark a new RC Cycle is relative to previous RC, not previous release RC is published and iterated upon as long as there are issues Release handling cycles between team members

Deployment & Release are distinct with different purposes ii. Deployment – installing a specified version to a given environmentiii. Release – when a feature is made available to customers. 1. Release of functionality actions, release becomes a business decisions, not a technical decision v. Environment-based Release Pattern – multiple environments available, only one is receiving live traffic. Release performed Application-based Release Pattern – modify application to selectively release functionality by small configuration changes. Feature flags, dark launching h. ENVIRONMENT-BASED RELEASE PATTERNS i. Enables

GitOps tools are sometimes marketed as the one-size-fits-all solution that will solve all your release problems and this is simply not true. First of all, GitOps requires that your deployment artifacts Classic pipeline With GitOps you can keep your CI process pristine (by just preparing a candidate release) and end it with a Git commit instead of a deployment. The Git commit is picked up by a deployment and your cluster for environment X is now getting the new version. But how do you promote this release to environment Y? Every time somebody declares that adopting GitOps is an easy process, I

. . . . . . 61 2.5.2 Top level ”Release” file and authenticity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 2.5.3 Archive level ”Release” files . . . . . . . . . . . . . the unstable release). The reported size is in KiB (Kibibyte = unit for 1024 bytes). Note A package with a small numerical package size may indicate that the package in the unstable release is a dummy package size followed by ”(*)” indicates that the package in the unstable release is missing and the package size for the experimental release is used instead. Bug reports on this document Please file bug reports

this case the period of outdated history deleted in one housekeeping cycle will be 4 times the period since the last housekeeping cycle, but not less than 4 hours and not greater than 4 days. The automatic {b}{t}{nn} format where: • {b} - source (1 - feature or release, 2 - tag) • {t} - type (1 - alpha, 2 - beta, 3 - release candidate, 4 - release) • {nn} - sequence number for the ’type’ For example: example: Tag Branch Version Result 3.0.28 Zabbix 3.0.28 3.0.28.2400 release/3.0 Zabbix 3.0.28rc3 3.0.28.1303 feature/ZBX-16074 Zabbix 3.0.28rc1 3.0.28.1301 34 What’s new in Zabbix 3.0.29 This minor version

not required for minor upgrades, such as from 1.8.x to 1.8.x, unless specifically stated so in the release notes of the version. Before running upgrade scripts drop the following indexes: MySQL alter Improvements for larger installations Zabbix is being used in larger and larger environments every day. 1.8 release introduces several changes that are specifically useful in average and above setups. 4.1 Performance 5.6 Supported PHP version changes Zabbix frontend is based on PHP. Since the last stable Zabbix release there have been major changes in PHP versions, and Zabbix frontend has been changed accordingly