OpenShift Container Platform 4.10 可伸缩性和性能
canary 更新的集群。 apiVersion: ran.openshift.io/v1alpha1 kind: ClusterGroupUpgrade metadata: name: cgu-upgrade-complete namespace: default spec: clusters: 1 - spoke1 enable: false managedPolicies: 2 UpgradeNotStarted status: "False" type: Ready copiedPolicies: - cgu-upgrade-complete-policy1-common-cluster-version-policy - cgu-upgrade-complete-policy2-common-pao-sub-policy managedPoliciesForUpgrade: placementBindings: - cgu-upgrade-complete-policy1-common-cluster-version-policy - cgu-upgrade-complete-policy2-common-pao-sub-policy placementRules: - cgu-upgrade-complete-policy1-common-cluster-version-policy0 码力 | 315 页 | 3.19 MB | 1 年前3Centos6.x升级至7.2
Centos6.x 升级至 7.2 前言: Centos6.x 的系统版本只能直接升级到 centos7.2 的版本,因为 centos7.3 开始,其安装 镜像文件里就没有 upgrade.img 等文件,无法直接升级了,所以要想从 6.x 升级到 7.8 等新 的版本,也要先升级至 7.2,再在 7.2 里 yum update 升级至最新版本。 Centos6 的小版本(如 6.4 本文档先以 centos6.5 最小化安装版本 为例讲一下通常的升级步骤: 1.下载 redhat-upgrade-tool 升级工具及相关依赖包 2.下载 centos7.2 的安装包.iso 文件,并上传到目标服务器(运行 centos6.x 的) 3.安装 redhat-upgrade-tool 及依赖包,运行升级检查命令 4.检查后无重大问题,则可升级 5.升级完成,若能正常进入新系统 个包:(建议放在同一目录下,如 /centos6_upgrade_tools ) 2.如果目标服务器不能访问互联网,则要准备 centos6.10 的安装镜像 iso 文件,需要用到里 面的 18 个依赖包(可以提取出来,也可不提取,直接把 6.10 的 iso 挂载目录做成 Yum 源) 也可到这里下载:https://limaofu.github.io/centos6_upgrade_depens.zip 上面0 码力 | 9 页 | 641.45 KB | 1 年前3OpenShift Container Platform 4.14 更新集群
OpenShift Container Platform 集群。平台管理员可以通过转至 web 控制台中的 Administration → Cluster Settings 或查看 oc adm upgrade 命令的输出来查看新的更新选项。 红帽托管了一个公共 OpenShift Update Service (OSUS),它根据官方 registry 中的 OpenShift Container 参数包括可用的更新,但不推荐因为应用到 集群的已知风险而不建议这样做。 输出示例 出示例 oc adm upgrade 命令查询 ClusterVersion 资源以获取可用更新的信息,并以人类可读格式显示 它。 直接检查 CVO 创建的底层可用性数据的一种方法是,使用以下命令查询 ClusterVersion 资源: $ oc adm upgrade --include-not-recommended Cluster version 14 candidate-4.14 如果您不希望 Cluster Version Operator 从升级建议服务获取可用的更新,您可以使用 OpenShift CLI 中 的 oc adm upgrade channel 命令配置空频道。例如,当集群有受限网络访问且没有本地可访问的升级 建议服务时,这个配置很有用。 警告 警告 红帽建议升级到 OpenShift Update Service0 码力 | 149 页 | 1.94 MB | 1 年前3Debian 快速參考手冊
libdb2 debconf # apt-get install apt apt-utils dselect dpkg 接下來請升級系統到 Woody。 # apt-get upgrade # apt-get dist-upgrade 2.2 升 升 升級 級 級前 前 前的 的 的準 準 準備 備 備 您可以透過網路安裝來升級目前的發行版本到另外一個。以下說明完成的方法。 首先取得 stable 以上動作會更新檔案庫中最新的套件列表 • aptitude upgrade (或 apt-get upgrade 或 aptitude dist-upgrade 或 apt-get dist-upgrade) 這樣會跟隨testing版本 — 他們會安裝目前testing版本上可提供升級的套件以及其相 依的軟體。 2 • apt-get dselect-upgrade 這會跟隨testing版本 — 上述指令 4-1 安裝 foo 套件的特定版本 2.2.4-1 。 2upgrade與dist-upgrade不 同 的 地 方 是 對 於 那 些 升 級 套 件 的 相 依 性 問 題 的 處 理 方 式 。 請 參 閱apt-get(8)來了解更多細節。 aptitude upgrade 和 aptitude dist-upgrade 是aptitude 的組合指 令。按下 e可以全螢幕顯示。 Chapter0 码力 | 29 页 | 862.98 KB | 1 年前3openEuler 21.03 技术白皮书
switched to Linux kernel 5.10 but also incorporated multiple new features such as live kernel upgrade and tiered memory expansion. These highlights improve multi-core performance and deliver thousand-core management of various memory and storage media, and smooth expansion of system capacity • Live kernel upgrade: quick, hitless fixes of kernel vulnerabilities Cloud base: • iSula: iSulad supports local volume Compilers Apps Desktops UKUI/DDE/Xfce DB Web Resource orchestration Messaging middleware Live kernel upgrade File systems Chips and peripheral drivers Linux Kernel 5.10 Computing architecture Process mgmt0 码力 | 21 页 | 948.66 KB | 1 年前3OpenShift Container Platform 4.7 更新集群
{ "channel": "stable-4.7", "clusterID": "990f7ab8-109b-4c95-8480-2bd1deec55ff" } $ oc adm upgrade Cluster version is 4.1.0 Updates: VERSION IMAGE 4.1.2 quay.io/openshift-release-dev/ocp- re release@sha256:9c5f0df8b192a0d7b46cd5f6a4da2289c155fd5302dec7954f8f06c878160b8b $ oc adm upgrade --to-latest=true 1 $ oc adm upgrade --to=1 $ oc get clusterversion -o json|jq ".items[0].spec" 第 第 6 章 acknowledge the start of an upgrade # file=/home/user/openshift-ansible/hooks/pre_compute.yml - name: note the start of a compute machine update debug: msg: "Compute machine upgrade of {{ inventory_hostname 0 码力 | 62 页 | 716.72 KB | 1 年前3QCon北京2017/智能化运维/Self Hosted Infrastructure:以自动运维 Kubernetes 为例
I hate to OPERATE Kubernetes! Kubernetes Architecture Operating Kubernetes ● Installation ● Upgrade ● Healing ● Scaling ● Security ● Monitoring ● ... Installation - SSH - Install kubelet - $pkgmanager node1 node2 node3 Upgrade - SSH - Upgrade container runtime - Upgrade Kubelet Upgrade - master - SSH - Upgrade master components Upgrade - etcd - SSH - Upgrade etcd Upgrade kops AWS, GCP API should be v1.4.5 ● Scheduler should be v1.4.5 How to get there ● Upgrade all API servers Daemons to v1.4.5 safely one-by-one ● Upgrade all Scheduler Deployments to v1.4.5 ● Update status to v1.4.5 The0 码力 | 73 页 | 1.58 MB | 1 年前3Weblate 4.2 用户文档
This needs to be done in the configuration and the compression has to be triggered on every Weblate upgrade. The configuration switch is simple by enabling django.conf.settings.COMPRESS_OFFLINE [https://django- The official Docker image (see 使用 Docker 安装) has all upgrade steps integrated. There are no manual step besides pulling latest version. Generic upgrade instructions Before upgrading, please check the current specific instructions before upgrade. In case you are skipping some versions, please follow instructions for all versions you are skipping in the upgrade. Sometimes it’s better to upgrade to some intermediate0 码力 | 648 页 | 9.34 MB | 1 年前3Weblate 4.2.1 用户文档
This needs to be done in the configuration and the compression has to be triggered on every Weblate upgrade. The configuration switch is simple by enabling django.conf.settings.COMPRESS_OFFLINE [https://django- The official Docker image (see 使用 Docker 安装) has all upgrade steps integrated. There are no manual step besides pulling latest version. Generic upgrade instructions Before upgrading, please check the current specific instructions before upgrade. In case you are skipping some versions, please follow instructions for all versions you are skipping in the upgrade. Sometimes it’s better to upgrade to some intermediate0 码力 | 650 页 | 9.34 MB | 1 年前3Weblate 4.2.2 用户文档
This needs to be done in the configuration and the compression has to be triggered on every Weblate upgrade. The configuration switch is simple by enabling django.conf.settings.COMPRESS_OFFLINE [https://django- The official Docker image (see 使用 Docker 安装) has all upgrade steps integrated. There are no manual step besides pulling latest version. Generic upgrade instructions Before upgrading, please check the current specific instructions before upgrade. In case you are skipping some versions, please follow instructions for all versions you are skipping in the upgrade. Sometimes it’s better to upgrade to some intermediate0 码力 | 650 页 | 9.34 MB | 1 年前3
共 313 条
- 1
- 2
- 3
- 4
- 5
- 6
- 32