> On 17 Aug 2015, at 1:30 pm, Andrei Borzenkov <arvidj...@gmail.com> wrote: > > 17.08.2015 02:26, Andrew Beekhof пишет: >> >>> On 13 Aug 2015, at 7:33 pm, Andrei Borzenkov <arvidj...@gmail.com> wrote: >>> >>> On Thu, Aug 13, 2015 at 11:25 AM, Ulrich Windl >>> <ulrich.wi...@rz.uni-regensburg.de> wrote: >>>> And what exactly is your problem? >>> >>> Real life example. Database resource depends on storage resource(s). >>> There are multiple filesystems/volumes with database files. Database >>> admin needs to increase available space. You add new storage, >>> configure it in cluster ... pooh, your database is restarted. >> >> “configure it in cluster” hmmm >> >> if you’re expanding an existing mount point, then I’d expect you don’t need >> to update the cluster. >> if you’re creating a new mount point, wouldn’t you need to take the db down >> in order to point to the new location? >> > > No. Those database I worked with can use multiple storage locations at the > same time and those storage locations can be added (and removed) online.
Nice. In that case, you could try adding it as a resource but waiting until it is active before creating the ordering constraint. > > > > _______________________________________________ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
