|
il y a 7 ans | |
---|---|---|
.. | ||
adhoc | il y a 7 ans | |
aws | il y a 7 ans | |
byo | il y a 7 ans | |
common | il y a 7 ans | |
gcp | il y a 7 ans | |
init | il y a 7 ans | |
openshift-checks | il y a 7 ans | |
openshift-etcd | il y a 7 ans | |
openshift-glusterfs | il y a 7 ans | |
openshift-hosted | il y a 7 ans | |
openshift-loadbalancer | il y a 7 ans | |
openshift-management | il y a 7 ans | |
openshift-master | il y a 7 ans | |
openshift-metrics | il y a 7 ans | |
openshift-nfs | il y a 7 ans | |
openshift-node | il y a 7 ans | |
openshift-prometheus | il y a 7 ans | |
openshift-provisioners | il y a 7 ans | |
openshift-service-catalog | il y a 7 ans | |
openstack | il y a 7 ans | |
README.md | il y a 7 ans | |
prerequisites.yml | il y a 7 ans |
In summary:
byo
(Bring Your Own hosts) has the most actively maintained
playbooks for installing, upgrading and performing others tasks on OpenShift
clusters.common
has a set of playbooks that are included by playbooks in
byo
and others.And:
adhoc
is a generic home for playbooks and tasks that are community
supported and not officially maintained.Refer to the README.md
file in each playbook directory for more information
about them.