The basic syntax of the file you'll pass to wallaby feature-import is the same as the basic syntax of a Condor configuration file; in fact, you can import many Condor configuration files without modification. (Only the NAME = VALUE syntax is supported at this time; you can't use the NAME = +VALUE syntax for DC_DAEMON_LIST.) However, there are some special directives that you can pass to the configuration file as comments:
- #name NAME
- Indicates that this feature should be named NAME. (Note that you must supply a name for the feature, either on the command line, via -n NAME, or in the file itself.)
- #includes FEATURE
- Indicates that this feature should include FEATURE, which must exist in Wallaby.
- #dependson FEATURE
- Indicates that this feature should depend upon FEATURE, which must exist in Wallaby.
- #default PARAM
- Indicates that this feature should include PARAM, and set it to its default value.
Because Condor ignores these comments, it is possible to use the same file both as a Condor configuration file and as a Wallaby feature description. (Other comments will be ignored by wallaby feature-import, but they may generate harmless warnings.) wallaby feature-import will automatically create any parameters referenced in the file that don't already exist in Wallaby's database; this can be a great time-saver for migrating to Wallaby from a custom configuration-management system.
The following example file is a feature that defines eight startds on a single node: