Gopher  China  2015  Resource  Scheduling  &  Container  Technology  for  Financial  Service  动态资源管理和容器技术  在金融行业的架构探索和明天  余军  Gopher  China  2015  Gopher  China  2015  China  2015  求解之路的探索  n 他们是否解决了我们的问题?  n No   ① Mesos  采用了DRF(Dominant  Resource  Fairness)  调度机制。 YARN自带FIFO、Capacity  Scheduler和Fair  Scheduler(借鉴了 Mesos的DRF)。  ② Mes oop中Capacity  Scheduler的调度机制，将所有资源分成若干个queue，每个 queue分配一定量的资源，每个user有一定的资源使用上限。  ③ Mesos采用了Resource  Offer机制，这种调度机制面临着资源碎 片问题，即：每个节点上的资源不可能全部被分配完，剩下的一 点可能不足以让任何任务运行，这样，便产生了类似于操作系统 中的内存碎片问题。 

7.5.1. 资源请求和过量使用 7.5.2. 使用 Cluster Resource Override Operator 的集群级别的过量使用 7.5.2.1. 使用 Web 控制台安装 Cluster Resource Override Operator 7.5.2.2. 使用 CLI 安装 Cluster Resource Override Operator 7.5.2.3. 配置集群级别的过量使用 logs ruby-58cd97df55-mww7r $ oc logs -f ruby-57f7f4855b-znl92 -c ruby $ oc logs /<resource_name> 1 $ oc logs deployment/ruby OpenShift Container Platform 4.9 节 节点 点 18 作为管理员，您可以为 pod pod 数量进行扩展的数量。扩展 pod 数量的默认值为 4%。 按 pod 百分比扩展的数量。按百分比扩展的默认值为 100%。 缩减 缩减策略示例 策略示例 name: hpa-resource-metrics-memory namespace: default spec: behavior: scaleDown: 1 policies: 2 -

7.5.1. 资源请求和过量使用 7.5.2. 使用 Cluster Resource Override Operator 的集群级别的过量使用 7.5.2.1. 使用 Web 控制台安装 Cluster Resource Override Operator 7.5.2.2. 使用 CLI 安装 Cluster Resource Override Operator 7.5.2.3. 配置集群级别的过量使用 logs ruby-58cd97df55-mww7r $ oc logs -f ruby-57f7f4855b-znl92 -c ruby $ oc logs /<resource_name> 1 $ oc logs deployment/ruby 第 第 2 章 章 使用 使用 POD 17 作为管理员，您可以为 pod 创建和维护高效的集群。 通过确保集群 config apiVersion: autoscaling/v2beta2 kind: HorizontalPodAutoscaler metadata: name: hpa-resource-metrics-memory namespace: default spec: 第 第 2 章 章 使用 使用 POD 23 1 2 3 4 5 6 7 8 9 10

以结束当前会话。 使用oc logout命令。 输 输出示例 出示例 这将从服务器中删除已保存的身份验证令牌，并将其从配置文件中删除。 $ oc create --help Create a resource by filename or stdin JSON and YAML formats are accepted. Usage: oc create -f FILENAME [flags] Pod VERSION: v1 DESCRIPTION: Pod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts. FIELDS: apiVersion APIVersion running nginx' # Update pod 'foo' only if the resource is unchanged from version 1 oc annotate pods foo description='my frontend running nginx' --resource-version=1 # Update pod 'foo' by removing an

Request a new project new-app Create a new application ... $ oc create --help Create a resource by filename or stdin JSON and YAML formats are accepted. Usage: oc create -f FILENAME [flags] Pod VERSION: v1 DESCRIPTION: Pod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts. FIELDS: apiVersion APIVersion running nginx' # Update pod 'foo' only if the resource is unchanged from version 1 oc annotate pods foo description='my frontend running nginx' --resource-version=1 # Update pod 'foo' by removing an

Request a new project new-app Create a new application ... $ oc create --help Create a resource by filename or stdin JSON and YAML formats are accepted. Usage: oc create -f FILENAME [flags] Pod VERSION: v1 DESCRIPTION: Pod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts. FIELDS: apiVersion APIVersion running nginx' # Update pod 'foo' only if the resource is unchanged from version 1. oc annotate pods foo description='my frontend running nginx' --resource-version=1 # Update pod 'foo' by removing an

of the files on disk. rotatelogs May now create a link to the current log file. May now invoke a custom post-rotate script. htpasswd, htdbm Support for the bcrypt algorithm (available in 2.4.4 and later) in the cache, this can be determined easily and without the overhead of transferring the entire resource. Secondly, a well designed origin server will be designed in such a way that conditional requests as long as that content has not expired. If, for example, your configuration permits access to a resource by IP address you should ensure that this content is not cached. You can do this by using the CacheDisable

of the files on disk. rotatelogs May now create a link to the current log file. May now invoke a custom post-rotate script. htpasswd, htdbm Support for the bcrypt algorithm (available in 2.4.4 and later) in the cache, this can be determined easily and without the overhead of transferring the entire resource. Secondly, a well designed origin server will be designed in such a way that conditional requests as long as that content has not expired. If, for example, your configuration permits access to a resource by IP address you should ensure that this content is not cached. You can do this by using the CacheDisable

of the files on disk. rotatelogs May now create a link to the current log file. May now invoke a custom post-rotate script. htpasswd, htdbm Support for the bcrypt algorithm (available in 2.4.4 and later) in the cache, this can be determined easily and without the overhead of transferring the entire resource. Secondly, a well designed origin server will be designed in such a way that conditional requests as long as that content has not expired. If, for example, your configuration permits access to a resource by IP address you should ensure that this content is not cached. You can do this by using the CacheDisable

of the files on disk. rotatelogs May now create a link to the current log file. May now invoke a custom post-rotate script. htpasswd, htdbm Support for the bcrypt algorithm (available in 2.4.4 and later) in the cache, this can be determined easily and without the overhead of transferring the entire resource. Secondly, a well designed origin server will be designed in such a way that conditional requests as long as that content has not expired. If, for example, your configuration permits access to a resource by IP address you should ensure that this content is not cached. You can do this by using the CacheDisable