This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| osm_controller_args: | |
| cloud-provider: | |
| - "vsphere" | |
| cloud-config: | |
| - "/etc/origin/cloudprovider/vsphere.conf" | |
| osm_api_server_args: | |
| cloud-provider: | |
| - "vsphere" | |
| cloud-config: | |
| - "/etc/origin/cloudprovider/vsphere.conf" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [root@e2e-vsphere1:~] vim-cmd vmsvc/get.guest 388 | |
| Guest information: | |
| (vim.vm.GuestInfo) { | |
| toolsStatus = "toolsOk", | |
| toolsVersionStatus = "guestToolsUnmanaged", | |
| toolsVersionStatus2 = "guestToolsUnmanaged", | |
| toolsRunningStatus = "guestToolsRunning", | |
| toolsVersion = "10277", | |
| toolsInstallType = "guestToolsTypeOpenVMTools", |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Post cloud provider 3.7 | |
| status: | |
| addresses: | |
| - address: 10.19.114.241 | |
| type: ExternalIP | |
| - address: 10.19.114.241 | |
| type: InternalIP | |
| - address: master-0 | |
| type: Hostname |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| user = "[email protected]" | |
| password = "xxxxxxx" | |
| server = "10.x.x.25" | |
| port = 443 | |
| insecure-flag = 1 | |
| datacenter = Boston | |
| datastore = ose3-vmware-prod | |
| working-dir = /Boston/vm/ocp36/ | |
| [Disk] | |
| scsicontrollertype = pvscsi |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [root@master-0 ~]# cat cloud-provider-storage-class.yaml | |
| kind: StorageClass | |
| apiVersion: storage.k8s.io/v1 | |
| metadata: | |
| name: "ose3-vmware-prod" | |
| provisioner: kubernetes.io/vsphere-volume | |
| parameters: | |
| diskformat: zeroedthick | |
| datastore: "ose3-vmware-prod" | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Keeping your OpenShift Container Platform HAproxy Highly Available with Keepalived | |
| A typical OpenShift Container Platform deployment will have multiple master, app and infra nodes for high availability. In this case, there is no single point of failure for the cluster, unless you have a single HAproxy server configured. The following article will discuss how to configure keepalived for maximum uptime for HAproxy. In the vsphere on OCP reference architecture, [https://access.redhat.com/documentation/en-us/reference_architectures/2017/html/deploying_a_red_hat_openshift_container_platform_3_on_vmware_vcenter_6/] two HAproxy virtual machines are configured and the ansible playbooks set up keepalived using a virtual IP address for Virtual Router Rendundancy Protocol or VRRP. | |
| This article will discuss the entire process of adding another haproxy server and configuring them both for high availability with keepalived. Keepalived is routing software written in C. In this configuration there will be a backup and mas |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Keeping your OpenShift Container Platform HAproxy HA with Keepalived | |
| A typical OpenShift Container Platform deployment will have multiple master, app and infra nodes for high availability. In this case, there is no single point of failure for the cluster, unless you have a single HAproxy server configured. The following article will discuss how to configure keepalived for maximum uptime for HAproxy. In the vsphere on OCP reference architecture, [https://access.redhat.com/documentation/en-us/reference_architectures/2017/html/deploying_a_red_hat_openshift_container_platform_3_on_vmware_vcenter_6/] two HAproxy virtual machines are configured and the ansible playbooks set up keepalived using a virtual IP address for Virtual Router Rendundancy Protocol or VRRP. | |
| Load Balancer Options | |
| The load balancer will distribute traffic accross two different groups. HAproxy serves ports 8443 for the masters and 80, 443 for the infra nodes for the routers. The reference architecture provides a couple of different options f |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| --- | |
| - name: Copy cloud provider storage class file | |
| template: | |
| src: cloud-provider-storage-class.yaml.j2 | |
| dest: ~/cloud-provider-storage-class.yaml | |
| - name: Copy cloud provider storage class file to single master | |
| fetch: | |
| src: ~/cloud-provider-storage-class.yaml | |
| dest: ~/cloud-provider-storage-class.yaml |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| module: | |
| auth: | |
| community: syseng | |
| apcups: | |
| walk: | |
| - 1.3.6.1.2.1.1.3 | |
| - 1.3.6.1.2.1.2 | |
| - 1.3.6.1.4.1.318.1.1.1.12 | |
| - 1.3.6.1.4.1.318.1.1.1.2 | |
| - 1.3.6.1.4.1.318.1.1.1.3 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| juniper-vc0 Seconds: 18 Time: 09:11:18 | |
| Interface Link Input packets (pps) Output packets (pps) | |
| vcp-255/2/0 Up 45089328 50190651 | |
| vcp-255/2/1 Up 55175351 50212182 | |
| vcp-255/2/2 Up 0 116052758 | |
| vcp-255/2/3 Up 53943464 54021580 | |
| xe-0/0/0 Up 2762942629 (6) 36828292384 (47) | |
| xe-0/0/1 Up 5636261784 (37) 39518591337 (53) | |
| xe-0/0/2 Up 3912375 (0) 35208779032 (52) |