As a follow up, I did following 1) Build the zip file without metainfo.xml 2) slider install 3) slider create xxx added option --metainfo metainfo.xml
The create command gave a stack trace in json processing after reading HDFS file from /user/xxx/.slider/cluster/ms_no_meta/appdef/appPkg.zip 4) Unzipping the HDFS file appPkg.zip shows metainfo.json (!!!) whereas I had given metainfo.xml on command line Question - when using command line option --metainfo, it seems the metainfo should be JSON, not XML ... Can someone confirm this ??? The info about this is very sparse ... Thanks again !!! On Mon, Nov 30, 2015 at 6:12 PM, Manoj Samel <manojsamelt...@gmail.com> wrote: > Hi, > > Looking at the slider example app memcached README.txt, it seems that it > is required to package metainfo.xml when creating the jmemcached-1.0.0.zip > file. It is not required to package appConfig.json or resources.json (even > the appConfig-default.json or resourses-default.json), as these are given > later as command line parameters > > 1: When the cluster is created, I can see files > /xxx/.slider/cluster/<cluster name>/app_config.json and resources.json (as > well as internal.json etc.). I could not locate any HDFS file corresponding > to metainfo.xml packaged in the .zip. Is metainfo used to generate any > slider files in HDFS ? > > 2: I need to add components dynamically to cluster. The # of components > and their names are not known before hand. One way to do is when a > component is to be added, add the component entry on local copy of > metainfo.xml, regenerate the .zip and re-install the package > with --replacepkg and then do a slider upgrade with appConfig and resources > file containing the new component as well. Is there any other way to add a > new component where I can *** avoid *** rebuilding the .zip file ? > > Thanks, >
