一．配置
[OSEv3:children]
masters
nodes
etcd
[OSEv3:vars]
ansible_ssh_user=root
# Ifansible_ssh_user is not root, ansible_become must be set to true
#ansible_become=true
openshift_deployment_type=openshift-enterprise
openshift_master_identity_providers=[{'name':'htpasswd_auth', 'login': 'true', 'challenge': 'true', 'kind':'HTPasswdPasswordIdentityProvider', 'filename': '/etc/origin/master/htpasswd'}] #外部認證方式選擇htpassd
openshift_disable_check=memory_availability,disk_availability,docker_image_availability,package_availability,docker_storage
openshift_docker_options="--selinux-enabled--insecure-registry 172.30.0.0/16 --log-driver json-file --log-opt max-size=10M--log-opt max-file=3 --insecure-registry harborone.ultraapp.com --add-registryharborone.ultraapp.com"
openshift_master_default_subdomain=apps.develop.com
openshift_hosted_router_selector='infra=true'
openshift_hosted_registry_selector='infra=true'
openshift_release=3.7.9
oreg_url=harborone.ultraapp.com/openshift3/ose-${component}:${version}
[masters]
master.develop.com
[etcd]
master.develop.com
[nodes]
master.develop.com
node1.develop.comopenshift_node_labels="{'region': 'primary', 'zone':'node1','infra':'true'}"
node2.develop.comopenshift_node_labels="{'region': 'primary', 'zone': 'node2'}"
二．命令
ansible-playbook /usr/share/ansible/openshift-ansible/playbooks/byo/config.yml
三．基於rpm安裝包的高級安裝部署openshift報錯總結
1. 無法解析域名；錯誤的ip地址。有明顯的報錯指示
2. ssh問題（報錯也有明顯的提示）：安裝過程中遠程node失敗，ssh-keygen；ssh-copy-idmaster/node的IP
注意：本主機與本主機也必須互信，自己ssh遠程自己也不能出現“yes/no”,否則也會報錯。
3．Master服務器沒有啓動（待解，嘻嘻）。
Jan 02 12:57:14master.develop.com dockerd-current[1408]: time="2018-01-02T12:57:14....
Jan 02 12:58:23master.develop.com oci-register-machine[93545]: 2018/01/02 12:58:23 ...
Jan 02 12:58:23master.develop.com oci-umount[93552]: umounthook <debug>: prestart ...s
Jan 02 12:58:24master.develop.com oci-register-machine[93583]: 2018/01/02 12:58:24 ...
Jan 02 13:03:39master.develop.com oci-register-machine[94207]: 2018/01/02 13:03:39 ...
Jan 02 13:03:39master.develop.com oci-register-machine[94233]: 2018/01/02 13:03:39 ...
Jan 02 15:25:50master.develop.com oci-register-machine[94808]: 2018/01/02 15:25:50 ...
Jan 02 15:25:50master.develop.com oci-umount[94814]: umounthook <debug>: prestart ...s
Jan 02 15:25:50master.develop.com oci-umount[94814]: umounthook <error>: 9ffd07af7...y
Jan 02 15:25:50master.develop.com oci-register-machine[94833]: 2018/01/02 15:25:50 ...
Hint: Some lineswere ellipsized, use -l to show in full.
2.catalog installfailed
TASK[ansible_service_broker : create ansible-service-broker service]*****************
fatal: [master.develop.com]: FAILED! =>{"changed": false, "failed": true, "msg":{"cmd": "/usr/bin/oc replace -f /tmp/asb-OVCnHW -nopenshift-ansible-service-broker", "results": {},"returncode": 1, "stderr": "The Service\"asb\" is invalid: spec.clusterIP: Invalid value: \"\":field is immutable\n", "stdout": ""}}
toretry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/config.retry
PLAY RECAP****************************************************************************
localhost : ok=12 changed=0 unreachable=0 failed=0
master.develop.com : ok=567 changed=83 unreachable=0 failed=1
node1.develop.com : ok=184 changed=27 unreachable=0 failed=0
node2.develop.com : ok=172 changed=14 unreachable=0 failed=0
INSTALLER STATUS **********************************************************************
Initialization : Complete
Health Check : Complete
etcd Install : Complete
MasterInstall : Complete
Master AdditionalInstall : Complete
Node Install : Complete
HostedInstall : Complete
Service Catalog Install : In Progress
a． 可能是因爲安裝了atomic，導致catalog 安裝失敗。卸載atomic，重新安裝，或者快照處理還原環境。或者重新設置maser。
b． 因爲重複安裝的問題，catalog.Server無法覆蓋原有的文件。
4.node節點沒有啓動docker，導致安裝錯誤，oc get pod無法獲取node節點。
方案:啓動節點的docker，發現無法自動獲取node，重新安裝。