also, there are script(s) packaged with the distribution that should be useful. The one-click 3node cluster setup that Alexis pointed you to consumes those as well, iirc.
http://docs.opendaylight.org/en/latest/getting-started-guide/common-features/clustering.html?highlight=clustering#clustering-scripts JamO On 02/22/2017 11:27 AM, Alexis de Talhouët wrote: > > > 2017-02-22 6:25 GMT-05:00 bjb <bjb2...@163.com <mailto:bjb2...@163.com>>: > > Hello All: > > I see the steps to deploy a cluster > in > http://docs.opendaylight.org/en/latest/getting-started-guide/common-features/clustering.html?highlight=clustering > > <http://docs.opendaylight.org/en/latest/getting-started-guide/common-features/clustering.html?highlight=clustering> > > I need to modify *.conf(akka.conf, modules.conf, module-shards.conf) > on each cluster member and then start karaf. For > convenience, configure_cluster.sh is provided to automatic generate > *.conf in configuration/initial. But it also need to > deploy on each cluster member. When the cluster members are huge, e.g 32 > members form a cluster, the depoly will be > inconvenient. > > > AdT: Checkout this setup that was merge recently in packaging repo: > https://github.com/opendaylight/integration-packaging/tree/master/tutorials/cluster-nodes > It could help achieve what you're seeking, to some extend. Basically, > configure your cluster once, and delpoy it once and for > all. > > > > Is there any other plans for easily deploying? I thinked two ways to > depoly a cluster, is it feasible? > 1) Add a new feature in odl to manage cluster, it includes "create > cluster" "destroy cluster" "dynamic add member" > and so on. All the controllers start karaf in standalone mode without > cluster configuration. We just need to send request > to one cluster member, the member transfer configuration to akka.conf > module-shard.conf, clean old journal and snapshots. > Then the member send request to all the other cluster members. The other > members do the same thing, after that, all > members restart karaf to apply cluster configuration. In this way, user > add easily do cluster management. > > 2) If odl will not support dynamic add or remove cluster member, > deploying cluster in advance will be less difficult. > We can use some depoly tools like ansible to distribute *.conf on all > cluster members. > > Hope to get your help. > Thanks > > > > > > > > > > > > > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > <mailto:controller-dev@lists.opendaylight.org> > https://lists.opendaylight.org/mailman/listinfo/controller-dev > <https://lists.opendaylight.org/mailman/listinfo/controller-dev> > > > > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
