kevina at cs.utah.edu
Tue Aug 8 17:38:56 EDT 2006
[Put devel at planet-lab.org back on the CC list]
On Tue, 8 Aug 2006, Mark Huang wrote:
> Kevin Atkinson wrote:
>> It is down by a script. Does it matter?
> Yes. Your script must also parse /etc/planetlab/default_config.xml, as well
> as the configuration fragments in /etc/planetlab/configs/*, which are all
> merged together to form /etc/planetlab/plc_config.xml. See
> myplc/plc_config.py and myplc/plc-config for how this works.
> This is the way that new variables are introduced, as well as the way that
> local customizations are supported.
> The reason you are getting the errors is that new variables have been
> introduced in RC2 and the nightlies. But in the process of tracking this
> down, I found a different, more horrible situation, under which this occurs,
> which is basically just upgrading from RC1 to RC2.
I thought the idea was that all local changes should go in the file
plc_config.xml. So are you saying that now when ever we upgrade, we have
to make a note of the local changes we made to plc_config.xml. Remove it.
Allow it to be recreated, than put the local changes back in? I hope you
are planning to fix this.
For now I will update my template to use the new plc_config.xml.
More information about the Devel