[PL #6755] planetlab in a box discussion

Tue Jul 26 13:56:40 EDT 2005

Aaron

Thanks for taking care of this
Please find attached a couple of patches I'd like to commit in this area :

-- changes in setup_plc.sh and config

. config reordered so as to ease customization
. new config variable for disabling hardware checks at install-time
. new config variable for setting site name (instead of 'default')
. root at DNS_SERVER_NAME gets PI role granted as well 

-- also please note that
$BASE_DIR/plc/scripts/gen-static-content.py
keeps complaining that:
No input file specified.
this is part of setup_plc.sh's output (probably unnoticed so far) 
but also spams root's mailbox now that it is cron-enabled

Please review this patch before you check it in.

Additional notes
- at boot-time the running node complains about a missing file /etc/ipod.conf
- it also fails to start service ntpd for some reason
- otherwise everything went without a glitch, I could upload a key and it was 
propagated correctly

Thanks - Thierry

On Wednesday 13 July 2005 11:56 pm, Aaron Klingaman via RT wrote:
> Email Recipients (see http://www.planet-lab.org/Support)
>        Owner: alk
>        Requestor: alk at absarokasoft.com
>        Ticket Ccs: Thierry.Parmentelat at sophia.inria.fr,
> alk at absarokasoft.com, devel-community at lists.planet-lab.org,
> jeff.sedayao at intel.com, renault.john at epfl.ch, winson.c.chan at intel.com
>
> ==================================================
>
> If you are having problems with creating and accessing slices after
> setting up a node and plc, then you need to rerun
> /planetlab/plc/scripts/gen-slices-xml-05.py and
> /planetlab/plc/scripts/gen-slices-xml-04.py
>
> These create the xml files that the node manager uses to create slices
> on the node and associate users with.
>
> You'll notice the bottom of the setup_plc.sh script mentions this, but
> doesn't create any cron entries.
>
> To avoid future confusion, I'll modify the script to create these cron
> entries, so the files are recreated every 5 minutes or so.
>
> Aaron
>
>
> _______________________________________________
> Devel-community mailing list
> Devel-community at lists.planet-lab.org
> https://lists.planet-lab.org/mailman/listinfo/devel-community
-------------- next part --------------
A non-text attachment was scrubbed...
Name: setup_plc.sh
Type: application/x-shellscript
Size: 17582 bytes
Desc: not available
Url : http://lists.planet-lab.org/pipermail/devel/attachments/20050726/2bd12b9e/setup_plc.bin
-------------- next part --------------
### -*-sh-*-
#
# primary plc configuration values. changes here get copied to the appropriate
# files when setup_plc.sh is run
#

#################### Please review this section

# short name of this PlanetLab, used for naming the default site
PLC_NAME='test-plc'

# fully qualified name of this server.
SERVER_DNS_NAME='test-plc.yourdomain.org'
# related IP address
SERVER_IP='127.0.0.1'

# if the name in SERVER_DNS_NAME doesn't resolve to SERVER_IP,
# set this to 0, and /etc/hosts will be updated for this entry
SERVER_NAME_RESOLVES='0'

# root password to use for root admin account and root bootcd
# account. this is 'root' without the quotes.
ROOT_PASSWORD_UNENC=root
ROOT_PASSWORD='$1$X2yDJ8RH$9ifDU73T.VsQ1opbkzyyF.'

# which boot server / management authority to pull built rpm packages
# from.
PACKAGE_SOURCE=http://boot.planet-lab.org

# and, for the above server, don't hammer it, so this is the rate
# limit in bytes per second at which the packages will be pulled via wget
# to disable, set to blank.
PACKAGE_SOURCE_RATE_LIMIT=100k

# if set to non-zero, skips hardware checking on nodes at install-time
# default is to perform the check 
# see also $BASE_DIR/bootmanager/source/configuration for details
SKIP_HARDWARE_REQUIREMENT_CHECK=0

# various email addresses

# primary support address
PLANETLAB_SUPPORT_EMAIL_ADDR='root@$SERVER_DNS_NAME'
PLANETLAB_SUPPORT_EMAIL="PlanetLab $PLC_NAME Support <$PLANETLAB_SUPPORT_EMAIL_ADDR>"

# where bootmanager/install emails are cced to
INSTALL_MSGS_EMAIL_ADDR='root@$SERVER_DNS_NAME'
INSTALL_MSGS_EMAIL="BootManager $PLC_NAME <$INSTALL_MSGS_EMAIL_ADDR>"

#################### miscellaneous - defaults should be OK

# how to check out the source code, defaults to anonymous.
# if you have developer privledges, and plan on checking code it,
# change this to :ext:username, and make sure your ssh-agent has the
# appropriate keys to access the cvs server, or setup will fail
CVS_CO_USER=":pserver:anon"

# this may need to be uncommented if you use cvs over ssh
#export CVS_RSH='ssh'

# where all the web content and api will be located
BASE_DIR='/planetlab'

# where to store the password files. should be outside of the 
# document root for www. $PASSWORD_FILE_DIR/php/ will be created
# and added to the php search path
PASSWORD_FILE_DIR='/etc/planetlab'

# connection constants to main plc database
PLC_DB_HOST=$SERVER_DNS_NAME
PLC_DB_USER='pgsqluser'
PLC_DB_PASSWORD='plc-db-password'
PLC_DB_NAME='planetlab3'

# connection constants for api
PL_API_SERVER=$SERVER_DNS_NAME
PL_API_PATH='/PLCAPI/'
PL_API_PORT='80'
PL_API_CAPABILITY_AUTH_METHOD='capability'
PL_API_CAPABILITY_PASS='1234567890'
PL_API_CAPABILITY_USERNAME="maint@$SERVER_DNS_NAME"
PL_API_CAPABILITY_SOURCES="127.0.0.1 0.0.0.0 $SERVER_IP"
PL_API_TICKET_KEY_FILE='/etc/planetlab/slice-ticket-key-nopass.pem'

# base name of web server
WWW_BASE=$SERVER_DNS_NAME

# enable debugging output on web pages
DEBUG='0'

# enable debugging output on web pages for xml rpc calls
API_CALL_DEBUG='0'

# allow website to send email out to users for operations that can
SENDMAIL='1'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gen-static-content.py
Type: application/x-python
Size: 16835 bytes
Desc: not available
Url : http://lists.planet-lab.org/pipermail/devel/attachments/20050726/2bd12b9e/gen-static-content.bin