Overall these are great (thanks for the screenshots), a few things I've seen that could improve the understanding :
1) a few objects are not really pictured that are pre requisites to run the procedure. like how to define the OAM network, how to add a keypair, how to define a security group and what is needed in it.
2) Once all the scripts are run and the VMs are up, we have noticed that Openstack does not always enable the secondary network interface, we had to modify the VM config to enable it
3) In the Rancher UI, once you copy the docker run command from the add-host UI. The copy button works ok for the first time, but then when you want to re use it (if you update the host IP for example when adding another node) it won't update the clipboard correctly. This will still allow the docker run command to work, but the host won't be seen in the Rancher UI
3 Comments
Jorge Hernandez
These instructions worked perfectly for me, Mike Elliott. Very helpful, thank you.
Ran Pollak
Yang Xu
Christophe Closset
A few comments on the instructions :
Overall these are great (thanks for the screenshots), a few things I've seen that could improve the understanding :
1) a few objects are not really pictured that are pre requisites to run the procedure. like how to define the OAM network, how to add a keypair, how to define a security group and what is needed in it.
2) Once all the scripts are run and the VMs are up, we have noticed that Openstack does not always enable the secondary network interface, we had to modify the VM config to enable it
3) In the Rancher UI, once you copy the docker run command from the add-host UI. The copy button works ok for the first time, but then when you want to re use it (if you update the host IP for example when adding another node) it won't update the clipboard correctly. This will still allow the docker run command to work, but the host won't be seen in the Rancher UI