The ansible scripts should be reentrant (if you didn't change your config files on disk after install), and adding a new node is just adding the machine to the ansible inventory and rerunning.
Pods today don't automatically reschedule once placed - there is a feature planned in the future called the rebalancer that would do that. However, if you trigger a rolling deployment all new pods are created, so you should see your app be cleanly spread across the new node and old node after deploying. > On Feb 20, 2016, at 10:55 AM, Candide Kemmler <[email protected]> wrote: > > I now have the 7 pods of my application running and easily deployable. Next > is learning how to scale it. Being able to multiply pods is great but it > doesn't help if you only have one low-performance machine to deploy them on. > My provider (ovh) makes it super easy to add vps's with various cpu/ram > characteristics. > > How can I turn them into nodes and make sure that pods are getting deployed > to them? > > Is it possible to create a server, use ansible to turn it into a node and > then decide exactly which pods will run on it? > > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
