Jan Provaznik

We don't enforce (anti-)affinity for openshift nodes, only for master nodes - https://github.com/redhat-openstack/openshift-on-openstack/blob/master/openshift.yaml#L83 . We could add similar server group/policy for openshift_nodes too (but by default this policy should not...

The problem with anti-affinity rule is that if there are not enough compute nodes, whole deployment fails (IOW you can't scale up beyond compute node count), this is quite restrictive...

Update: actually it seems that soft-anti-affinity policy has been already implemented - I think this is ideal default - if possible, use different host, but don't fail if no different...

@ioggstream I wonder whether it's a feature or a race issue on heat side - I would expect that replacing node means deleting the node first (which should make volume...

@ioggstream I don't think that there is much active development on this project so I wouldn't expect this (or other features) to be done though.

@ioggstream I'm not on this project for a while, but with ceph-ansible I suppose you can define customized playbook for replacing a node (which does exactly what you want -...

@ioggstream this is a really old RFE which came from testing scalability of these templates. IIRC the problem was that by default nova instance boots from image, which means that...

-P skip_dns=true (which is considered in the linked OSv3 file - https://github.com/redhat-openstack/openshift-on-openstack/blob/master/templates/var/lib/ansible/group_vars/OSv3.yml#L14) should satisfy this RFE In README it's mentioned only in the NOTE in https://github.com/redhat-openstack/openshift-on-openstack#setting-dns, we should make this...

is skip_dns is used, then OpenShift cluster hostnames are written into /etc/hosts on bastion node, this file is copied to each node (also when new nodes are added): https://github.com/redhat-openstack/openshift-on-openstack/blob/master/templates/var/lib/ansible/playbooks/dns.yml#L5 /etc/resolv.conf...

Hi @zhangjunli177 , thanks for reporting this. This issue is tracked also in https://bugzilla.redhat.com/show_bug.cgi?id=1337400 and the fix has been merged to upstream already - https://github.com/kubernetes/kubernetes/pull/25907/commits/6744a7417aa846f89f4bb6e25c49561709f06dff . It's fixed in RHEL...