 Consul及Consul
Connect介紹Copyright © 2019 HashiCorp Consul及Consul Connect介紹 Service Mesh Made Easy 劉宇雷-Hashicorp Solutions Engineer Agenda 1. 服務網格是什麼? 簡要歷史回顧 2. 什麼是Consul,它如何工作? 3. 演示: 如何在非容器化的環境下使用Consul的服 務網格 4. 問&答 Algorithm Consul Connect Architecture 通過intentions實現 聲明式網絡安全互 聯 Consul Connect Architecture 基於PKI Certificate 的服務認證 ⁄ Demo Time! ⁄ Additional thoughts � Walk Turn on Consul Connect and secure Crawl Deploy Consul, register some services, start using it for service discovery. � Run Connect multiple datacenters, incorporate both Kubernetes and legacy environments, etc. Crawl-Walk-Run0 码力 | 26 页 | 6.71 MB | 1 年前3 Consul及Consul
Connect介紹Copyright © 2019 HashiCorp Consul及Consul Connect介紹 Service Mesh Made Easy 劉宇雷-Hashicorp Solutions Engineer Agenda 1. 服務網格是什麼? 簡要歷史回顧 2. 什麼是Consul,它如何工作? 3. 演示: 如何在非容器化的環境下使用Consul的服 務網格 4. 問&答 Algorithm Consul Connect Architecture 通過intentions實現 聲明式網絡安全互 聯 Consul Connect Architecture 基於PKI Certificate 的服務認證 ⁄ Demo Time! ⁄ Additional thoughts � Walk Turn on Consul Connect and secure Crawl Deploy Consul, register some services, start using it for service discovery. � Run Connect multiple datacenters, incorporate both Kubernetes and legacy environments, etc. Crawl-Walk-Run0 码力 | 26 页 | 6.71 MB | 1 年前3
 OpenShift Container Platform 4.14 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry0 码力 | 3881 页 | 39.03 MB | 1 年前3 OpenShift Container Platform 4.14 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry0 码力 | 3881 页 | 39.03 MB | 1 年前3
 OpenShift Container Platform 4.8 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry 默认 认 AWS 限 限值 值 描述 描述 platform: aws: region: us-gov-west-1 serviceEndpoints: - name: ec2 url: https://ec2.us-gov-west-1.amazonaws.com - name: elasticloadbalancing url: htt0 码力 | 2586 页 | 27.37 MB | 1 年前3 OpenShift Container Platform 4.8 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry 默认 认 AWS 限 限值 值 描述 描述 platform: aws: region: us-gov-west-1 serviceEndpoints: - name: ec2 url: https://ec2.us-gov-west-1.amazonaws.com - name: elasticloadbalancing url: htt0 码力 | 2586 页 | 27.37 MB | 1 年前3
 OpenShift Container Platform 4.10 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry0 码力 | 3142 页 | 33.42 MB | 1 年前3 OpenShift Container Platform 4.10 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry0 码力 | 3142 页 | 33.42 MB | 1 年前3
 OpenShift Container Platform 4.13 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry 该文件类似于以下示例: "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry0 码力 | 4634 页 | 43.96 MB | 1 年前3 OpenShift Container Platform 4.13 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry 该文件类似于以下示例: "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry0 码力 | 4634 页 | 43.96 MB | 1 年前3
 Apache Karaf Decanter 1.x - Documentation…). This Map is sent to the appenders. The collector allows you to remotely use Decanter. For instance, you can have an application running on a different platform (spring-boot, application servers means that you can add your own custom data, and easily create queries bases on this data. For instance, instead of the log collector, you can create the following etc/ org.apache.karaf.decanter.collector property is the MBeanServer to connect. "local" is reserved keyword to specify the local MBeanServer. Instead of "local", you can use the JMX service URL. For instance, for Karaf version 3.0.0, 3.0.10 码力 | 67 页 | 213.16 KB | 1 年前3 Apache Karaf Decanter 1.x - Documentation…). This Map is sent to the appenders. The collector allows you to remotely use Decanter. For instance, you can have an application running on a different platform (spring-boot, application servers means that you can add your own custom data, and easily create queries bases on this data. For instance, instead of the log collector, you can create the following etc/ org.apache.karaf.decanter.collector property is the MBeanServer to connect. "local" is reserved keyword to specify the local MBeanServer. Instead of "local", you can use the JMX service URL. For instance, for Karaf version 3.0.0, 3.0.10 码力 | 67 页 | 213.16 KB | 1 年前3
 OpenShift Container Platform 4.7 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry large 和 m5.xlarge 实例。 platform: aws: region: us-gov-west-1 serviceEndpoints: - name: ec2 url: https://ec2.us-gov-west-1.amazonaws.com - name: elasticloadbalancing url: htt0 码力 | 2276 页 | 23.68 MB | 1 年前3 OpenShift Container Platform 4.7 安装"quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry "quay.io": { "auth": "b3BlbnNo...", "email": "you@example.com" }, "registry.connect.redhat.com": { "auth": "NTE3Njg5Nj...", "email": "you@example.com" }, "registry large 和 m5.xlarge 实例。 platform: aws: region: us-gov-west-1 serviceEndpoints: - name: ec2 url: https://ec2.us-gov-west-1.amazonaws.com - name: elasticloadbalancing url: htt0 码力 | 2276 页 | 23.68 MB | 1 年前3
 OpenShift Container Platform 4.9 网络Cloud (Amazon EC2) 实例创建公共 IP 地址。为了可以 SSH 到 OpenShift Container Platform 主机,您必须按照以下步骤操作。 流程 流程 1. 创建一个安全组,允许 SSH 访问由 openshift-install 命令创建的虚拟私有云 (VPC) 。 2. 在安装程序创建的某个公共子网中创建 Amazon EC2 实例。 3. 将公共 IP IP 地址与您创建的 Amazon EC2 实例相关联。 与 OpenShift Container Platform 安装不同,您应该将您创建的 Amazon EC2 实例与 SSH 密钥对 关联。这与您为这个实例选择的操作系统无关,因为它只是一个 SSH 堡垒将互联网桥接到 OpenShift Container Platform 集群的 VPC。它与您使用的 Amazon Machine Image (AMI) 相 关。例如,在 Red Hat Enterprise Linux CoreOS(RHCOS) 中,您可以像安装程序一样通过 Ignition 提供密钥。 4. 一旦置备了 Amazon EC2 实例并可以 SSH 到它,您必须添加与 OpenShift Container Platform 安 装关联的 SSH 密钥。这个密钥可以与堡垒实例的密钥不同,也可以相同。 注意 注意 直接通过0 码力 | 388 页 | 4.04 MB | 1 年前3 OpenShift Container Platform 4.9 网络Cloud (Amazon EC2) 实例创建公共 IP 地址。为了可以 SSH 到 OpenShift Container Platform 主机,您必须按照以下步骤操作。 流程 流程 1. 创建一个安全组,允许 SSH 访问由 openshift-install 命令创建的虚拟私有云 (VPC) 。 2. 在安装程序创建的某个公共子网中创建 Amazon EC2 实例。 3. 将公共 IP IP 地址与您创建的 Amazon EC2 实例相关联。 与 OpenShift Container Platform 安装不同,您应该将您创建的 Amazon EC2 实例与 SSH 密钥对 关联。这与您为这个实例选择的操作系统无关,因为它只是一个 SSH 堡垒将互联网桥接到 OpenShift Container Platform 集群的 VPC。它与您使用的 Amazon Machine Image (AMI) 相 关。例如,在 Red Hat Enterprise Linux CoreOS(RHCOS) 中,您可以像安装程序一样通过 Ignition 提供密钥。 4. 一旦置备了 Amazon EC2 实例并可以 SSH 到它,您必须添加与 OpenShift Container Platform 安 装关联的 SSH 密钥。这个密钥可以与堡垒实例的密钥不同,也可以相同。 注意 注意 直接通过0 码力 | 388 页 | 4.04 MB | 1 年前3
 Apache RocketMQ on Amazon Web Services.......................................................................... 13 APACHE ROCKETMQ 在 EC2 上部署所在目录说明: .......................................................................... 13 Nameserver: AMAZON WEB SERVICES 客户需要在 AMAZON WEB SERVICES 上 使用 RocketMQ 的需求,我们开发了一键部署的方案,帮助客户快速的在自己的账号 部署一个基于 EC2 的高可用的 RocketMQ 集群。 架构 AMAZON CloudFormation 提供了一种创建和管理相关 AMAZON WEB SERVICES 资源的简 便方法,并通过有序 且 Nameserver 互为备份,三个 Broker Instance 每个 Broker Instance 上面启动三个 Broker 实例,每个 Broker 实例会在 三个 Broker Instance 之间形成一个基于 Raft 的高可用 dledger 集群,如果其中一个 Broker 实例因故障无法提供服务,Raft 协议会自动在另外两个 Instance 中选择一个作 为 Master 继续0 码力 | 18 页 | 1.55 MB | 1 年前3 Apache RocketMQ on Amazon Web Services.......................................................................... 13 APACHE ROCKETMQ 在 EC2 上部署所在目录说明: .......................................................................... 13 Nameserver: AMAZON WEB SERVICES 客户需要在 AMAZON WEB SERVICES 上 使用 RocketMQ 的需求,我们开发了一键部署的方案,帮助客户快速的在自己的账号 部署一个基于 EC2 的高可用的 RocketMQ 集群。 架构 AMAZON CloudFormation 提供了一种创建和管理相关 AMAZON WEB SERVICES 资源的简 便方法,并通过有序 且 Nameserver 互为备份,三个 Broker Instance 每个 Broker Instance 上面启动三个 Broker 实例,每个 Broker 实例会在 三个 Broker Instance 之间形成一个基于 Raft 的高可用 dledger 集群,如果其中一个 Broker 实例因故障无法提供服务,Raft 协议会自动在另外两个 Instance 中选择一个作 为 Master 继续0 码力 | 18 页 | 1.55 MB | 1 年前3
 快速部署高可用的Apache RocketMQ 集群 - Amazon S3.......................................................................... 15 APACHE ROCKETMQ 在 EC2 上部署所在目录说明: ..................................................................... 15 Nameserver . 具有低延迟,金融级高可用以及厂商中立的特点,目前广泛使 用于国内外的互联网公司。针对亚马逊云科技客户需要在亚马逊云科技上使用 RocketMQ 的需求,我们开发了一键部署的方案,帮助客户快速的在自己的账号部署 一个基于 EC2 的高可用的 RocketMQ 集群。 架构 Amazon CloudFormation 提供了⼀种创建和管理相关 AMAZON WEB SERVICES 资源的简便⽅法,并通过有序 且可 Nameserver 互为备份,三个 Broker Instance 每个 Broker Instance 上面启动三个 Broker 实例,每个 Broker 实例会在三个 Broker Instance 之间形成一个基于 Raft 的高可用 dledger 集群,如果其中一个 Broker 实例 因故障无法提供服务,Raft 协议会自动在另外两个 Instance 中选择一个作为 Master 继续0 码力 | 21 页 | 2.57 MB | 1 年前3 快速部署高可用的Apache RocketMQ 集群 - Amazon S3.......................................................................... 15 APACHE ROCKETMQ 在 EC2 上部署所在目录说明: ..................................................................... 15 Nameserver . 具有低延迟,金融级高可用以及厂商中立的特点,目前广泛使 用于国内外的互联网公司。针对亚马逊云科技客户需要在亚马逊云科技上使用 RocketMQ 的需求,我们开发了一键部署的方案,帮助客户快速的在自己的账号部署 一个基于 EC2 的高可用的 RocketMQ 集群。 架构 Amazon CloudFormation 提供了⼀种创建和管理相关 AMAZON WEB SERVICES 资源的简便⽅法,并通过有序 且可 Nameserver 互为备份,三个 Broker Instance 每个 Broker Instance 上面启动三个 Broker 实例,每个 Broker 实例会在三个 Broker Instance 之间形成一个基于 Raft 的高可用 dledger 集群,如果其中一个 Broker 实例 因故障无法提供服务,Raft 协议会自动在另外两个 Instance 中选择一个作为 Master 继续0 码力 | 21 页 | 2.57 MB | 1 年前3
共 358 条
- 1
- 2
- 3
- 4
- 5
- 6
- 36














 
  
 