On 8/17/06, Steve Kemp <[EMAIL PROTECTED]> wrote:
< [...]
> like --template-vars="mac=00:00:E0:11:11, thingy=hello, myvar=anothervalue"
But this doesn't.
Since the template values need to go into different places. WHich
means it needs special handling.
I could imagine:
--add-vars "foo=bar\nx = ['test', 'test2']"
Which would add that text literally. But with your example we'd
need to parse out the different options to know where to place
them. (eg. mac has to go inside the "vif" section.)
I don't understand the problem here. Why does xen-create-image need
to know where to place the values of a variable? It (or: the template
language)replaces variables at every occurence in the template.
What we have now in the templates is that I have some simple key/value
pairs, and the template language even gives the possibility to make
parts of the template conditional.
I determine where the value of mac has to go by placing the string
{$mac} into the template. The correct place for a config file to
function is a vif entry, but that has to be done right by the template
writer, not xen-create-image..
I *will* add the --mac processing. (Presumably you'd want that
for every IP address?)
I can imagine people doing static IP's will need that - for now, I
mainly do dhcp.
Henning
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
