[xen-tools] Re: Looks like nothing left to do

[Steve Kemp]

On Tue, Feb 13, 2007 at 07:12:29AM +0000, Steve Kemp wrote:

>  I have a few private role scripts which I use
>  internally which might get added

  And now I remember why these weren't added.  I have several role
 scripts which are very simple and just do one-off jobs.  One of
 these is "nis-client", which is designed to setup a new host as
 an NIS client - so that password authentication comes from
 an external server.

  This works perfectly for me, it just adds the "nis" package,
 adds "+::::::" to the end if /etc/passwd, etc.

  However the bit which makes it none-portable is that it
 configures the NIS master server as a hardwired IP address,
 valid for me, but not for anybody else.

  Before adding this I'd need to update the system so that role
 scripts could access arguments in a better fashion than:

    YPSERVER=192.168.1.1 xen-create-image --role=nis-client ...

  (This probably applies to the CFEngine role script which
 is already in the CVS repository/release.  If it knew the
 IP of the cfmaster server it could do more configuration.)

  I figured "--role-args='--foo --bar'" might be an option since
 it allows multiple arguments to be specified, but it feels
 unwieldy.  Almost as bad is "--role-args='foo=bar,baz=xxx'"

  Right now I could get by with "--extra=192.168.1.1", but
 I'm not keen on limiting myself to one argument for future
 role scripts - it seems that that would work for me right now,
 but for other role scripts there might be more choice such
 as "--mysql" vs. "--postresql", etc.

  If there is an insanely obvious solution which I'm missing
 now would be a good time to let me know ..

Steve
--