Jia Ni wrote: >> Two choices either use SMF properties for all of the configuration >> options of pen - this is the idea case. Or create a smaller set of SMF > When Huafeng and I doing the porting, we actually once thought about > this method. > > But the difficulty is we can't set every argument with a default value. > Eg, you can't image which hostname/ip will the back-end server be. > So, if a user want to start 'pen', he should first set several SMF > properties correctly (and maybe he should understand what these > properties represent before that).
You don't need to have default values for properties, for example the hostname/ip would just be empty. The method script just needs to know what the property names are and translate the property name values that are set into pen cli flags. >> properties including one that gives the location of a pen.cf file, the > Yes. > I think a configure file is really easy for user to setup and start > 'pen', rather than SMF properties. Depends on your definition of easier, I would much prefer to see this done as SMF properties on the instance. >> method script would use that property to find pen.cf instead of being >> hardcoded to /etc/pen.cf as it would in the original spec. > I agree. Thanks! Please provide an updated spec using one of the above to methods. -- Darren J Moffat
