Managix sort of splices the cluster.xml with the existing asterix-configuration.xml to produce a new asterix-configuration.xml that then gets put into the asterix-app jar inside of asterix-server. The user has to know about the base asterix-configuration.xml because that is where you change some important memory parameters. You can also edit it without deleting the cluster itself (managix alter).
On Wed, Jun 29, 2016 at 1:05 AM, Chris Hillery <[email protected]> wrote: > My understanding of how Managix-based deployment currently works is as > follows: > > - User composes a cluster.xml > > - Managix consumes this and produces an asterix-configuration.xml, which > contains some of the same data as cluster.xml as well as some things > derived from that data (such as composing the <iodevices> directories with > the <store> subdirectory name to produce <storeDirs>) > > - Managix places both the original cluster.xml and the generated > asterix-configuration.xml onto the CLASSPATH of the NCs and CCs > > - The user is never directly aware of asterix-configuration.xml, and > certainly does not edit it in the normal course of operation > > Is this an accurate summary? > > Ceej > aka Chris Hillery >
