Mark Huang <mlhuang@cs.princeton.edu>
Copyright (C) 2006 The Trustees of Princeton University
-$Id: plc_config.xml,v 1.14 2006/06/23 20:31:09 mlhuang Exp $
+$Id: plc_config.xml,v 1.21 2007/08/24 07:19:27 mef Exp $
-->
<!DOCTYPE configuration PUBLIC "-//PlanetLab Central//DTD PLC configuration//EN" "plc_config.dtd">
</variablelist>
</category>
- <category id="plc_ma_sa">
- <name>Management and Slice Authority</name>
- <description>These variables control how your site interacts
- with other PlanetLab sites as a Management Authority (MA) and/or
- Slice Authority (SA).</description>
-
- <variablelist>
- <variable id="namespace" type="ip">
- <name>Namespace</name>
- <value>test</value>
- <description>The namespace of your MA/SA. This should be a
- globally unique value assigned by PlanetLab
- Central.</description>
- </variable>
-
- <variable id="ssl_key" type="file">
- <name>SSL Private Key</name>
- <value>/etc/planetlab/ma_sa_ssl.key</value>
- <description>The SSL private key used for signing documents
- with the signature of your MA/SA. If non-existent, one will
- be generated.</description>
- </variable>
-
- <variable id="ssl_crt" type="file">
- <name>SSL Public Certificate</name>
- <value>/etc/planetlab/ma_sa_ssl.crt</value>
- <description>The corresponding SSL public certificate. By
- default, this certificate is self-signed. You may replace
- the certificate later with one signed by the PLC root
- CA.</description>
- </variable>
-
- <variable id="ca_ssl_crt" type="file">
- <name>Root CA SSL Public Certificate</name>
- <value>/etc/planetlab/ma_sa_ca_ssl.crt</value>
- <description>If applicable, the certificate of the PLC root
- CA. If your MA/SA certificate is self-signed, then this file
- is the same as your MA/SA certificate.</description>
- </variable>
-
- <variable id="ca_ssl_key_pub" type="file">
- <name>Root CA SSL Public Key</name>
- <value>/etc/planetlab/ma_sa_ca_ssl.pub</value>
- <description>If applicable, the public key of the PLC root
- CA. If your MA/SA certificate is self-signed, then this file
- is the same as your MA/SA public key.</description>
- </variable>
-
- <variable id="api_crt" type="file">
- <name>API Certificate</name>
- <value>/etc/planetlab/ma_sa_api.xml</value>
- <description>The API Certificate is your MA/SA public key
- embedded in a digitally signed XML document. By default,
- this document is self-signed. You may replace this
- certificate later with one signed by the PLC root
- CA.</description>
- </variable>
- </variablelist>
- </category>
-
<category id="plc_net">
<name>Network</name>
<description>Network environment.</description>
<variable id="name" type="string">
<name>Database Name</name>
- <value>planetlab3</value>
+ <value>planetlab4</value>
<description>The name of the database to access.</description>
</variable>
<variable id="port" type="int">
<name>Port</name>
- <value>80</value>
+ <value>443</value>
<description>The TCP port number through which the API
- should be accessed. Warning: SSL (port 443) access is not
- fully supported by the website code yet. We recommend that
- port 80 be used for now and that the API server either run
- on the same machine as the web server, or that they both be
- on a secure wired network.</description>
+ should be accessed.</description>
</variable>
<variable id="path" type="string">
<packagelist>
<!-- Basics -->
<packagereq type="mandatory">dev</packagereq>
+ <packagereq type="mandatory">findutils</packagereq>
+
<!-- kernel-vserver is intended for the vserver-reference, but
serves the same useful purpose for MyPLC, namely, to
<!-- Almost all scripts are written in Python -->
<packagereq type="mandatory">python</packagereq>
-
- <!-- For various Python scripts that access the API -->
- <packagereq type="mandatory">plcapilib</packagereq>
+ <packagereq type="mandatory">python-devel</packagereq>
<!-- Database server -->
<packagereq type="mandatory">postgresql</packagereq>
access the DB directly. -->
<packagereq type="mandatory">php</packagereq>
<packagereq type="mandatory">php-pgsql</packagereq>
- <packagereq type="mandatory">php-xmlrpc</packagereq>
+ <!-- PLCAPI replaces php-xmlrpc -->
+ <!-- <packagereq type="mandatory">php-xmlrpc</packagereq> -->
<!-- Need GD for ImageCreate(), etc. -->
<packagereq type="mandatory">gd</packagereq>
<packagereq type="mandatory">php-gd</packagereq>
+ <packagereq type="mandatory">perl-GD</packagereq>
<!-- API server is implemented in mod_python -->
<packagereq type="mandatory">mod_python</packagereq>
<!-- API server uses a few non-standard packages -->
+ <packagereq type="mandatory">PLCAPI</packagereq>
+ <packagereq type="mandatory">SOAPpy</packagereq>
<packagereq type="mandatory">PyXML</packagereq>
- <packagereq type="mandatory">PlanetLabAuth</packagereq>
<!-- API server uses SSL to sign tickets -->
<packagereq type="mandatory">xmlsec1</packagereq>
git://git.onelab.eu / myplc.git / blobdiff