The DevOps Handbook
discovery: only 50% of the source code in Dev/Test environments matched Prod. They fixed forward, but changes not put back into version control. Focused on version control and automated environment creation environments (Prod, pre-prod(s), dev, & new) iv. Immutable Infrastructure 1. Once created no changes are allowed 2. Changes must be put into version control and then new infrastructure is created 3. To prevent that learning into future work d. Google Web Server (GWS) team was struggling with changes – Hard line: no changes would be accepted into GWS without accompanying automated tests. Spread Testing Grouplet0 码力 | 8 页 | 23.08 KB | 5 月前33 Key Elements for Your GitOps strategy
application repo trigger processes with your CI/CD tooling to update the config repo. The config changes are then pushed/pulled to the deployment environment. Git Repo 1 Git Repo 2 CI/CD Infrastructure re-architecting applications fit into a standardized and vendor-agnostic workflow. It often requires breaking down monolithic applications into microservices, which can be a complex and resource-intensive repository to detect when the Kubernetes cluster resources should automatically update based on config changes. GitOps Operator Infrastructure Code Application Code Transitioning to a cloud-native architecture0 码力 | 14 页 | 761.79 KB | 1 年前3MITRE Defense Agile Acquisition Guide - Mar 2014
to transform IT acquisition by delivering capabilities faster and responding more effectively to changes in operations, technology, and budgets. This guide provides DoD acquisition professionals with details releases Valuing working software over comprehensive documentation Responding rapidly to changes in operations, technology, and budgets Actively involving users throughout development to ensure effectively measure progress, reduce technical and programmatic risk, and respond to feedback and changes more quickly than traditional methods. Programs can adopt Agile practices within current policy0 码力 | 74 页 | 3.57 MB | 5 月前3Zabbix 6.0 Manual
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 9 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421 Appendix 2. Changes from 5.4 to 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426 Zabbix API changes in 6.0 . . . . . . . . . . . . . this design it is possible to create a very flexible setup. 5 What’s new in Zabbix 6.0.0 See breaking changes for this version. High availability cluster for Zabbix server The new version comes with a0 码力 | 1681 页 | 23.19 MB | 1 年前3Cilium v1.5 Documentation
BPF runs inside the Linux kernel, Cilium security policies can be applied and updated without any changes to the applica�on code or container configura�on. Why Cilium? The development of modern datacenter individual containers ge�ng started or destroyed as the applica�on scales out / in to adapt to load changes and during rolling updates that are deployed as part of con�nuous delivery. This shi� toward highly As a precau�on, we will use Is�o’s service rou�ng feature to canary the v2 deployment to prevent breaking the end-to-end applica�on completely if it is faulty. Before deploying v2 , to prevent any traffic0 码力 | 740 页 | 12.52 MB | 1 年前3This Debian Reference (version 2.109)
an X application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 9.3.9 Recording changes in configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 9 permissions (before the full security review) • Don’t leave your root shell until you TEST your changes • Always have an alternative boot media (USB memory stick, CD, …) Some quotes for new users Here before power can safely be turned off. This is to maintain the integrity of files, by forcing all changes in memory to be written to disk. If the software power control is available, the shutdown procedure0 码力 | 266 页 | 1.25 MB | 1 年前3Zabbix 2.2 Manual
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 7 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773 Appendix 2. Changes from 2.0 to 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779 Zabbix API changes in 2.2 . . . . . . . . . . . . . . items have gained the optional0 码力 | 918 页 | 11.28 MB | 1 年前3Zabbix 6.2 Manual
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 9 Template changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1443 Appendix 2. Changes from 6.0 to 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1448 Zabbix API changes in 6.2 . . . . . . . . . . . . . SHA256 hash types are supported, e. g.: • hmac('md5',key,string) • hmac('sha256',key,string) Breaking changes PHP version PHP versions below 7.4.0 are no longer supported. The minimum required PHP version0 码力 | 1689 页 | 22.82 MB | 1 年前3Ubuntu Desktop Training 2009
Canonical Limited 5. Select the language that you want set as default, and click OK. 6. For the changes to take effect, log off and then log on again. Nice to Know: You can change the language as many user, the previous user screen is locked by default, so the other person cannot make any profile changes. 38 Chapter 2. Exploring the Ubuntu Desktop Ubuntu Desktop Course Copyright © 2009 Canonical Limited continue making the changes required to resolve the dependencies, click Mark. 6. To confirm that you want to make the marked changes, click Apply. Figure 3.34. Confirming Changes 7. The Summary dialogue0 码力 | 428 页 | 57.45 MB | 1 年前3Cilium v1.6 Documentation
BPF runs inside the Linux kernel, Cilium security policies can be applied and updated without any changes to the application code or container configuration. Why Cilium? The development of modern datacenter individual containers getting started or destroyed as the application scales out / in to adapt to load changes and during rolling updates that are deployed as part of continuous delivery. This shift toward highly a precaution, we will use Istio’s service routing feature to canary the v2 deployment to prevent breaking the end-to-end application completely if it is faulty. Before deploying v2, to prevent any traffic0 码力 | 734 页 | 11.45 MB | 1 年前3
共 139 条
- 1
- 2
- 3
- 4
- 5
- 6
- 14