> > I would like to add an additional node to the cluster without using > ansible. > (We have modified our cluster in many ways and don't dare running ansible > because it might break our cluster.)
The scale up playbooks take this into account. They will query the master, generates and distributes the new certificates for the new node, and then runs the config playbooks on the new nodes only. To take advantage of this, you will need to add a group to your inventory called [new_nodes] and configure the hosts as you would for a new install under the [nodes] group. Then you would run the playbooks/byo/openshift-cluster/scaleup.yml playbook. On Thu, Feb 4, 2016 at 9:55 AM, v <[email protected]> wrote: > All right, looks like it works. These are the commands for the master with > 3.1: > > oadm create-api-client-config \ > --certificate-authority=/etc/origin/master/ca.crt \ > --client-dir=/root/xyz4 \ > --master=https://xyz1.eu:8443 <https://oshit01.rosm.eu:8443> \ > --signer-cert=/etc/origin/master/ca.crt \ > --signer-key=/etc/origin/master/ca.key \ > --signer-serial=/etc/origin/master/ca.serial.txt \ > --groups=system:nodes \ > --user=system:node:xyz4.eu > > oadm create-node-config \ > --node-dir=/root/xyz4 \ > --node=xyz.eu \ > --hostnames=xyz4.eu,123.456.0.5 \ > --certificate-authority /etc/origin/master/ca.crt \ > --signer-cert /etc/origin/master/ca.crt \ > --signer-key /etc/origin/master/ca.key \ > --signer-serial /etc/origin/master/ca.serial.txt \ > --master=https://xyz1.eu:8443 <https://oshit01.rosm.eu:8443> \ > --node-client-certificate-authority /etc/origin/master/ca.crt > > > Then I copied all the created files to /etc/origin/node on the new node. > Took node-config.yaml from an old, working node, edited the hostnames and > used it as node-config.yaml on the new node. > > It seems to work. The only thing that bugs me is that I'm being spammed > with the following error on the new node: > manager.go:313] NetworkPlugin redhat/openshift-ovs-subnet failed on the > status hook for pod 'xy-router-2-imubn' - exit status 1 > manager.go:313] NetworkPlugin redhat/openshift-ovs-subnet failed on the > status hook for pod 'ipf-default-1-dp4vc' - exit status 1 > Do you mind submitting a PR or an issue to the openshift-docs repo for these steps? https://github.com/openshift/openshift-docs > > Can anyone tell me if this is something important or whether there are > additional steps needed that I have missed? > It sounds like you are missing the -sdn-ovs package on the new node host. If you are running Origin, then it would be origin-sdn-ovs, otherwise it is atomic-enterprise-sdn-ovs. > > Regards, > v >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
