From cec7a732ff16f97b56b894ac3a3b7ced84e4d495 Mon Sep 17 00:00:00 2001 From: Thierry Parmentelat Date: Fri, 11 Aug 2006 18:28:44 +0000 Subject: [PATCH] dummy 1.11 for cathing up with the xml numbering --- doc/myplc.php | 565 +++++++++++++++++++++++++++----------------------- 1 file changed, 304 insertions(+), 261 deletions(-) diff --git a/doc/myplc.php b/doc/myplc.php index 0dce9ad..53ebf98 100644 --- a/doc/myplc.php +++ b/doc/myplc.php @@ -13,7 +13,7 @@

-MyPLC User's Guide

+MyPLC User's Guide

Mark Huang

@@ -45,33 +45,39 @@

Table of Contents

-
1. Overview
-
1.1. Purpose of the myplc-devel +
1. Overview
+
1.1. Purpose of the myplc-devel package
2. Requirements
-
3. Installation
-
4. Quickstart
+
3. Installating and using MyPLC
-
4.1. Changing the configuration
-
4.2. Installing nodes
-
4.3. Administering nodes
-
4.4. Creating a slice
+
3.1. Installing MyPLC.
+
3.2. QuickStart
+
3.3. Changing the configuration
+
3.4. Installing nodes
+
3.5. Administering nodes
+
3.6. Creating a slice
+
3.7. Understanding the startup sequence
+
3.8. Files and directories + involved in myplc
-
5. Rebuilding and customizing MyPLC
+
4. Rebuilding and customizing MyPLC
-
5.1. Installation
-
5.2. Fedora Core 4 mirror requirement
-
5.3. Building MyPLC
-
5.4. Updating CVS
+
4.1. Installation
+
4.2. Files and directories + involved in myplc-devl
+
4.3. Fedora Core 4 mirror requirement
+
4.4. Building MyPLC
+
4.5. Updating CVS
-
A. Configuration variables (for myplc)
-
B. Development configuration variables (for myplc-devel)
-
Bibliography
+
A. Configuration variables (for myplc)
+
B. Development configuration variables (for myplc-devel)
+
Bibliography

-1. Overview

+1. Overview

MyPLC is a complete PlanetLab Central (PLC) portable installation contained within a chroot jail. The default installation consists of a web server, an @@ -94,7 +100,7 @@

-1.1.  Purpose of the myplc-devel +1.1.  Purpose of the myplc-devel package

The myplc package comes with all required node software, rebuilt from the public PlanetLab CVS @@ -121,7 +127,7 @@

However, things are never that simple and there indeed are some known limitations to this, so here are a couple notes as a recommended reading before you proceed with the installation.

-

As of August 2006 9 (i.e myplc-0.5) :

+

As of 9 August 2006 (i.e myplc-0.5) :

  • The software is vastly based on Fedora Core 4. Please note that the build server at Princeton @@ -148,231 +154,77 @@ need to check your firewall configuration since you need, of course, to open up the http and https ports, so as to accept connections from - the managed nodes, and from the users desktops.

    • + the managed nodes and from the users desktops.

-3. Installation

+3. Installating and using MyPLC

Though internally composed of commodity software subpackages, MyPLC should be treated as a monolithic software application. MyPLC is distributed as single RPM package that has no external dependencies, allowing it to be installed on - practically any Linux 2.6 based distribution:

-
-

Example 1. Installing MyPLC.

-
# If your distribution supports RPM
-rpm -U http://build.planet-lab.org/build/myplc-0_4-rc1/RPMS/i386/myplc-0.4-1.planetlab.i386.rpm
-
-# If your distribution does not support RPM
-cd /tmp
-wget http://build.planet-lab.org/build/myplc-0_4-rc1/RPMS/i386/myplc-0.4-1.planetlab.i386.rpm
-cd /
-rpm2cpio /tmp/myplc-0.4-1.planetlab.i386.rpm | cpio -diu
-
-

MyPLC installs the following files and directories:

+ practically any Linux 2.6 based distribution.

+
+

+3.1. Installing MyPLC.

    -

  • /plc/root.img: The main - root filesystem of the MyPLC application. This file is an - uncompressed ext3 filesystem that is loopback mounted on - /plc/root when MyPLC starts. This - filesystem, even when mounted, should be treated as an opaque - binary that can and will be replaced in its entirety by any - upgrade of MyPLC.

    • -

  • /plc/root: The mount point - for /plc/root.img. Once the root filesystem - is mounted, all MyPLC services run in a - chroot jail based in this - directory.

  • -

    /plc/data: The directory where user - data and generated files are stored. This directory is bind - mounted onto /plc/root/data so that it is - accessible as /data from within the - chroot jail. Files in this directory are - marked with %config(noreplace) in the - RPM. That is, during an upgrade of MyPLC, if a file has not - changed since the last installation or upgrade of MyPLC, it is - subject to upgrade and replacement. If the file has changed, - the new version of the file will be created with a - .rpmnew extension. Symlinks within the - MyPLC root filesystem ensure that the following directories - (relative to /plc/root) are stored - outside the MyPLC filesystem image:

    -
      -

    • /etc/planetlab: This - directory contains the configuration files, keys, and - certificates that define your MyPLC - installation.

      • -

    • /var/lib/pgsql: This - directory contains PostgreSQL database - files.

      • -

    • /var/www/html/alpina-logs: This - directory contains node installation logs.

      • -

    • /var/www/html/boot: This - directory contains the Boot Manager, customized for your MyPLC - installation, and its data files.

      • -

    • /var/www/html/download: This - directory contains Boot CD images, customized for your MyPLC - installation.

      • -

    • /var/www/html/install-rpms: This - directory is where you should install node package updates, - if any. By default, nodes are installed from the tarball - located at - /var/www/html/boot/PlanetLab-Bootstrap.tar.bz2, - which is pre-built from the latest PlanetLab Central - sources, and installed as part of your MyPLC - installation. However, nodes will attempt to install any - newer RPMs located in - /var/www/html/install-rpms/planetlab, - after initial installation and periodically thereafter. You - must run yum-arch and - createrepo to update the - yum caches in this directory after - installing a new RPM. PlanetLab Central cannot support any - changes to this directory.

      • -

    • /var/www/html/xml: This - directory contains various XML files that the Slice Creation - Service uses to determine the state of slices. These XML - files are refreshed periodically by cron - jobs running in the MyPLC root.

      • -
    +

    If your distribution supports RPM:

    +
    # rpm -U http://build.planet-lab.org/build/myplc-0_4-rc1/RPMS/i386/myplc-0.4-1.planetlab.i386.rpm
  • -

    /etc/init.d/plc: This file - is a System V init script installed on your host filesystem, - that allows you to start up and shut down MyPLC with a single - command. On a Red Hat or Fedora host system, it is customary to - use the service command to invoke System V - init scripts:

    +

    If your distribution does not support RPM:

    +
    # cd /tmp
+# wget http://build.planet-lab.org/build/myplc-0_4-rc1/RPMS/i386/myplc-0.4-1.planetlab.i386.rpm
+# cd /
+# rpm2cpio /tmp/myplc-0.4-1.planetlab.i386.rpm | cpio -diu
    +
    • +
+

The Section 3.8, “ Files and directories + involved in myplc” below explains in + details the installation strategy and the miscellaneous files and + directories involved.

+
+
+

+3.2.  QuickStart

+

On a Red Hat or Fedora host system, it is customary to use + the service command to invoke System V init + scripts. As the examples suggest, the service must be started as root:

-

Example 2. Starting and stopping MyPLC.

-
# Starting MyPLC
-service plc start
-
-# Stopping MyPLC
-service plc stop
+

Example 1. Starting MyPLC:

+
# service plc start
-

Like all other registered System V init services, MyPLC is - started and shut down automatically when your host system boots - and powers off. You may disable automatic startup by invoking - the chkconfig command on a Red Hat or Fedora - host system:

-

Example 3. Disabling automatic startup of MyPLC.

-
# Disable automatic startup
-chkconfig plc off
-
-# Enable automatic startup
-chkconfig plc on
+

Example 2. Stopping MyPLC:

+
# service plc stop
- -

  • /etc/sysconfig/plc: This - file is a shell script fragment that defines the variables - PLC_ROOT and PLC_DATA. By default, - the values of these variables are /plc/root - and /plc/data, respectively. If you wish, - you may move your MyPLC installation to another location on your - host filesystem and edit the values of these variables - appropriately, but you will break the RPM upgrade - process. PlanetLab Central cannot support any changes to this - file.

    • -

  • /etc/planetlab: This - symlink to /plc/data/etc/planetlab is - installed on the host system for convenience.

    • -
    +

    In Section 3.7, “Understanding the startup sequence”, we provide greater + details that might be helpful in the case where the service does + not seem to take off correctly.

    +

    Like all other registered System V init services, MyPLC is + started and shut down automatically when your host system boots + and powers off. You may disable automatic startup by invoking the + chkconfig command on a Red Hat or Fedora host + system:

    +
    +

    Example 3. Disabling automatic startup of MyPLC.

    +
    # chkconfig plc off
    -
    -

    -4. Quickstart

    -

    Once installed, start MyPLC (see Example 2, “Starting and stopping MyPLC.”). MyPLC must be started as - root. Observe the output of this command for any failures. If no - failures occur, you should see output similar to the - following:

    -

    Example 4. A successful MyPLC startup.

    -
    Mounting PLC:                                              [  OK  ]
-PLC: Generating network files:                             [  OK  ]
-PLC: Starting system logger:                               [  OK  ]
-PLC: Starting database server:                             [  OK  ]
-PLC: Generating SSL certificates:                          [  OK  ]
-PLC: Configuring the API:                                  [  OK  ]
-PLC: Updating GPG keys:                                    [  OK  ]
-PLC: Generating SSH keys:                                  [  OK  ]
-PLC: Starting web server:                                  [  OK  ]
-PLC: Bootstrapping the database:                           [  OK  ]
-PLC: Starting DNS server:                                  [  OK  ]
-PLC: Starting crond:                                       [  OK  ]
-PLC: Rebuilding Boot CD:                                   [  OK  ]
-PLC: Rebuilding Boot Manager:                              [  OK  ]
-PLC: Signing node packages:                                [  OK  ]
-
    +

    Example 4. Re-enabling automatic startup of MyPLC.

    +
    # chkconfig plc on
    +
    -

    If /plc/root is mounted successfully, a - complete log file of the startup process may be found at - /plc/root/var/log/boot.log. Possible reasons - for failure of each step include:

    -
      -

    • Mounting PLC: If this step - fails, first ensure that you started MyPLC as root. Check - /etc/sysconfig/plc to ensure that - PLC_ROOT and PLC_DATA refer to the - right locations. You may also have too many existing loopback - mounts, or your kernel may not support loopback mounting, bind - mounting, or the ext3 filesystem. Try freeing at least one - loopback device, or re-compiling your kernel to support loopback - mounting, bind mounting, and the ext3 filesystem. If you see an - error similar to Permission denied while trying to open - /plc/root.img, then SELinux may be enabled. See Section 2, “ Requirements ” above for details.

      • -

    • Starting database server: If - this step fails, check - /plc/root/var/log/pgsql and - /plc/root/var/log/boot.log. The most common - reason for failure is that the default PostgreSQL port, TCP port - 5432, is already in use. Check that you are not running a - PostgreSQL server on the host system.

      • -

    • Starting web server: If this - step fails, check - /plc/root/var/log/httpd/error_log and - /plc/root/var/log/boot.log for obvious - errors. The most common reason for failure is that the default - web ports, TCP ports 80 and 443, are already in use. Check that - you are not running a web server on the host - system.

      • -

    • Bootstrapping the database: - If this step fails, it is likely that the previous step - (Starting web server) also failed. Another - reason that it could fail is if PLC_API_HOST (see - Section 4.1, “Changing the configuration”) does not resolve to - the host on which the API server has been enabled. By default, - all services, including the API server, are enabled and run on - the same host, so check that PLC_API_HOST is - either localhost or resolves to a local IP - address.

      • -

    • Starting crond: If this step - fails, it is likely that the previous steps (Starting - web server and Bootstrapping the - database) also failed. If not, check - /plc/root/var/log/boot.log for obvious - errors. This step starts the cron service and - generates the initial set of XML files that the Slice Creation - Service uses to determine slice state.

      • -
    -

    If no failures occur, then MyPLC should be active with a - default configuration. Open a web browser on the host system and - visit http://localhost/, which should bring you - to the front page of your PLC installation. The password of the - default administrator account - root@localhost.localdomain (set by - PLC_ROOT_USER) is root (set by - PLC_ROOT_PASSWORD).

    -4.1. Changing the configuration

    +3.3. Changing the configuration

    After verifying that MyPLC is working correctly, shut it down and begin changing some of the default variable values. Shut down MyPLC with service plc stop - (see Example 2, “Starting and stopping MyPLC.”). With a text + (see Section 3.2, “ QuickStart ”). With a text editor, open the file /etc/planetlab/plc_config.xml. This file is a self-documenting configuration file written in XML. Variables @@ -408,16 +260,16 @@ PLC: Signing node packages: [ OK ] preferred FQDN and external IP address of your host system.

    -

    After changing these variables, save the file, then - restart MyPLC with service plc start. You - should notice that the password of the default administrator - account is no longer root, and that the - default site name includes the name of your PLC installation - instead of PlanetLab.

    +

    The full set of applicable variables is described in Appendix B, Development configuration variables (for myplc-devel). After changing these variables, + save the file, then restart MyPLC with service plc + start. You should notice that the password of the + default administrator account is no longer + root, and that the default site name includes + the name of your PLC installation instead of PlanetLab.

    -4.2. Installing nodes

    +3.4. Installing nodes

    Install your first node by clicking Add Node under the Nodes tab. Fill in all the appropriate details, then click @@ -441,12 +293,12 @@ PLC: Signing node packages: [ OK ]

    -4.3. Administering nodes

    +3.5. Administering nodes

    You may administer nodes as root by using the SSH key stored in /etc/planetlab/root_ssh_key.rsa.

    -

    Example 5. Accessing nodes via SSH. Replace +

    Example 5. Accessing nodes via SSH. Replace node with the hostname of the node.

    ssh -i /etc/planetlab/root_ssh_key.rsa root@node
    @@ -469,7 +321,7 @@ PLC: Signing node packages: [ OK ]

    -4.4. Creating a slice

    +3.6. Creating a slice

    Create a slice by clicking Create Slice under the Slices tab. Fill in all the appropriate details, then click Create. Add @@ -484,7 +336,7 @@ PLC: Signing node packages: [ OK ] to determine if it needs to create or delete any slices. You may accelerate this process manually if desired.

    -

    Example 6. Forcing slice creation on a node.

    +

    Example 6. Forcing slice creation on a node.

    # Update slices.xml immediately
 service plc start crond
 
@@ -493,10 +345,185 @@ ssh -i /etc/planetlab/root_ssh_key.rsa root@node \
 vserver pl_conf exec service pl_conf restart
    +
    +

    +3.7. Understanding the startup sequence

    +

    During service startup described in Section 3.2, “ QuickStart ”, observe the output of this command for + any failures. If no failures occur, you should see output similar + to the following:

    +
    +

    Example 7. A successful MyPLC startup.

    +
    Mounting PLC:                                              [  OK  ]
+PLC: Generating network files:                             [  OK  ]
+PLC: Starting system logger:                               [  OK  ]
+PLC: Starting database server:                             [  OK  ]
+PLC: Generating SSL certificates:                          [  OK  ]
+PLC: Configuring the API:                                  [  OK  ]
+PLC: Updating GPG keys:                                    [  OK  ]
+PLC: Generating SSH keys:                                  [  OK  ]
+PLC: Starting web server:                                  [  OK  ]
+PLC: Bootstrapping the database:                           [  OK  ]
+PLC: Starting DNS server:                                  [  OK  ]
+PLC: Starting crond:                                       [  OK  ]
+PLC: Rebuilding Boot CD:                                   [  OK  ]
+PLC: Rebuilding Boot Manager:                              [  OK  ]
+PLC: Signing node packages:                                [  OK  ]
+
    +
    +

    If /plc/root is mounted successfully, a + complete log file of the startup process may be found at + /plc/root/var/log/boot.log. Possible reasons + for failure of each step include:

    +
      +

    • Mounting PLC: If this step + fails, first ensure that you started MyPLC as root. Check + /etc/sysconfig/plc to ensure that + PLC_ROOT and PLC_DATA refer to the + right locations. You may also have too many existing loopback + mounts, or your kernel may not support loopback mounting, bind + mounting, or the ext3 filesystem. Try freeing at least one + loopback device, or re-compiling your kernel to support loopback + mounting, bind mounting, and the ext3 filesystem. If you see an + error similar to Permission denied while trying to open + /plc/root.img, then SELinux may be enabled. See Section 2, “ Requirements ” above for details.

      • +

    • Starting database server: If + this step fails, check + /plc/root/var/log/pgsql and + /plc/root/var/log/boot.log. The most common + reason for failure is that the default PostgreSQL port, TCP port + 5432, is already in use. Check that you are not running a + PostgreSQL server on the host system.

      • +

    • Starting web server: If this + step fails, check + /plc/root/var/log/httpd/error_log and + /plc/root/var/log/boot.log for obvious + errors. The most common reason for failure is that the default + web ports, TCP ports 80 and 443, are already in use. Check that + you are not running a web server on the host + system.

      • +

    • Bootstrapping the database: + If this step fails, it is likely that the previous step + (Starting web server) also failed. Another + reason that it could fail is if PLC_API_HOST (see + Section 3.3, “Changing the configuration”) does not resolve to + the host on which the API server has been enabled. By default, + all services, including the API server, are enabled and run on + the same host, so check that PLC_API_HOST is + either localhost or resolves to a local IP + address.

      • +

    • Starting crond: If this step + fails, it is likely that the previous steps (Starting + web server and Bootstrapping the + database) also failed. If not, check + /plc/root/var/log/boot.log for obvious + errors. This step starts the cron service and + generates the initial set of XML files that the Slice Creation + Service uses to determine slice state.

      • +
    +

    If no failures occur, then MyPLC should be active with a + default configuration. Open a web browser on the host system and + visit http://localhost/, which should bring you + to the front page of your PLC installation. The password of the + default administrator account + root@localhost.localdomain (set by + PLC_ROOT_USER) is root (set by + PLC_ROOT_PASSWORD).

    +
    +
    +

    +3.8.  Files and directories + involved in myplc

    +

    MyPLC installs the following files and directories:

    +
      +

    1. /plc/root.img: The main + root filesystem of the MyPLC application. This file is an + uncompressed ext3 filesystem that is loopback mounted on + /plc/root when MyPLC starts. This + filesystem, even when mounted, should be treated as an opaque + binary that can and will be replaced in its entirety by any + upgrade of MyPLC.

      2. +

    2. /plc/root: The mount point + for /plc/root.img. Once the root filesystem + is mounted, all MyPLC services run in a + chroot jail based in this + directory.

      3. +
    3. +

      /plc/data: The directory where user + data and generated files are stored. This directory is bind + mounted onto /plc/root/data so that it is + accessible as /data from within the + chroot jail. Files in this directory are + marked with %config(noreplace) in the + RPM. That is, during an upgrade of MyPLC, if a file has not + changed since the last installation or upgrade of MyPLC, it is + subject to upgrade and replacement. If the file has changed, + the new version of the file will be created with a + .rpmnew extension. Symlinks within the + MyPLC root filesystem ensure that the following directories + (relative to /plc/root) are stored + outside the MyPLC filesystem image:

      +
        +

      • /etc/planetlab: This + directory contains the configuration files, keys, and + certificates that define your MyPLC + installation.

        • +

      • /var/lib/pgsql: This + directory contains PostgreSQL database + files.

        • +

      • /var/www/html/alpina-logs: This + directory contains node installation logs.

        • +

      • /var/www/html/boot: This + directory contains the Boot Manager, customized for your MyPLC + installation, and its data files.

        • +

      • /var/www/html/download: This + directory contains Boot CD images, customized for your MyPLC + installation.

        • +

      • /var/www/html/install-rpms: This + directory is where you should install node package updates, + if any. By default, nodes are installed from the tarball + located at + /var/www/html/boot/PlanetLab-Bootstrap.tar.bz2, + which is pre-built from the latest PlanetLab Central + sources, and installed as part of your MyPLC + installation. However, nodes will attempt to install any + newer RPMs located in + /var/www/html/install-rpms/planetlab, + after initial installation and periodically thereafter. You + must run yum-arch and + createrepo to update the + yum caches in this directory after + installing a new RPM. PlanetLab Central cannot support any + changes to this directory.

        • +

      • /var/www/html/xml: This + directory contains various XML files that the Slice Creation + Service uses to determine the state of slices. These XML + files are refreshed periodically by cron + jobs running in the MyPLC root.

        • +
      +
      4. +

    4. /etc/init.d/plc: This file + is a System V init script installed on your host filesystem, + that allows you to start up and shut down MyPLC with a single + command, as described in Section 3.2, “ QuickStart ”.

      5. +

    5. /etc/sysconfig/plc: This + file is a shell script fragment that defines the variables + PLC_ROOT and PLC_DATA. By default, + the values of these variables are /plc/root + and /plc/data, respectively. If you wish, + you may move your MyPLC installation to another location on your + host filesystem and edit the values of these variables + appropriately, but you will break the RPM upgrade + process. PlanetLab Central cannot support any changes to this + file.

      6. +

    6. /etc/planetlab: This + symlink to /plc/data/etc/planetlab is + installed on the host system for convenience.

      7. +
    +

    -5. Rebuilding and customizing MyPLC

    +4. Rebuilding and customizing MyPLC

    The MyPLC package, though distributed as an RPM, is not a traditional package that can be easily rebuilt from SRPM. The requisite build environment is quite extensive and numerous @@ -513,7 +540,7 @@ vserver pl_conf exec service pl_conf restart repository.

    -5.1. Installation

    +4.1. Installation

    Install the MyPLC development environment similarly to how you would install MyPLC. You may install both packages on the same host system if you wish. As with MyPLC, the MyPLC development @@ -521,17 +548,24 @@ vserver pl_conf exec service pl_conf restart application, and any files present in the chroot jail should not be modified directly, as they are subject to upgrade.

    -
    -

    Example 7. Installing the MyPLC development environment.

    -
    # If your distribution supports RPM
-rpm -U http://build.planet-lab.org/build/myplc-0_4-rc2/RPMS/i386/myplc-devel-0.4-2.planetlab.i386.rpm
-
-# If your distribution does not support RPM
-cd /tmp
-wget http://build.planet-lab.org/build/myplc-0_4-rc2/RPMS/i386/myplc-devel-0.4-2.planetlab.i386.rpm
-cd /
-rpm2cpio /tmp/myplc-devel-0.4-2.planetlab.i386.rpm | cpio -diu
    +
      +
    • +

      If your distribution supports RPM:

      +
      # rpm -U http://build.planet-lab.org/build/myplc-0_4-rc2/RPMS/i386/myplc-devel-0.4-2.planetlab.i386.rpm
      +
      • +
    • +

      If your distribution does not support RPM:

      +
      # cd /tmp
+# wget http://build.planet-lab.org/build/myplc-0_4-rc2/RPMS/i386/myplc-devel-0.4-2.planetlab.i386.rpm
+# cd /
+# rpm2cpio /tmp/myplc-devel-0.4-2.planetlab.i386.rpm | cpio -diu
      +
      • +
    +
    +

    +4.2.  Files and directories + involved in myplc-devl

    The MyPLC development environment installs the following files and directories:

      @@ -565,14 +599,14 @@ rpm2cpio /tmp/myplc-devel-0.4-2.planetlab.i386.rpm | cpio -diu snapshot of the PlanetLab source code is stored as a CVS repository in this directory. Files in this directory will not be updated by an upgrade of - myplc-devel. See Section 5.4, “Updating CVS” for more information about updating + myplc-devel. See Section 4.5, “Updating CVS” for more information about updating PlanetLab source code.

    • /build: Builds are stored in this directory. This directory is bind mounted onto /plc/devel/root/build so that it is accessible as /build from within the chroot jail. The build scripts in this - directory are themselves source controlled; see Section 5.3, “Building MyPLC” for more information about executing + directory are themselves source controlled; see Section 4.4, “Building MyPLC” for more information about executing builds.

    @@ -584,7 +618,7 @@ rpm2cpio /tmp/myplc-devel-0.4-2.planetlab.i386.rpm | cpio -diu

    -5.2. Fedora Core 4 mirror requirement

    +4.3. Fedora Core 4 mirror requirement

    The MyPLC development environment requires access to a complete Fedora Core 4 i386 RPM repository, because several different filesystems based upon Fedora Core 4 are constructed @@ -616,13 +650,13 @@ rpm2cpio /tmp/myplc-devel-0.4-2.planetlab.i386.rpm | cpio -diu such as wget or rsync to download the RPMS from a public mirror:

    -

    Example 8. Setting up a local Fedora Core 4 repository.

    -
    mkdir -p /plc/devel/data/fedora
-cd /plc/devel/data/fedora
+
    Example 8. Setting up a local Fedora Core 4 repository.
    
+
    # mkdir -p /plc/devel/data/fedora
+# cd /plc/devel/data/fedora
 
-for repo in core/4/i386/os core/updates/4/i386 extras/4/i386 ; do
-    wget -m -nH --cut-dirs=3 http://coblitz.planet-lab.org/pub/fedora/linux/$repo
-done
    
+# for repo in core/4/i386/os core/updates/4/i386 extras/4/i386 ; do
+>     wget -m -nH --cut-dirs=3 http://coblitz.planet-lab.org/pub/fedora/linux/$repo
+> done

    Change the repository URI and --cut-dirs level as needed to produce a hierarchy that resembles:

    @@ -634,17 +668,25 @@ done

    -5.3. Building MyPLC

    +4.4. Building MyPLC

    All PlanetLab source code modules are built and installed as RPMS. A set of build scripts, checked into the build/ directory of the PlanetLab CVS repository, eases the task of rebuilding PlanetLab source code.

    +

    Before you try building MyPLC, you might check the + configuration, in a file named + plc_config.xml that relies on a very + similar model as MyPLC, located in + /etc/planetlab within the chroot jail, or + in /plc/devel/data/etc/planetlab from the + root context. The set of applicable variables is described in + Appendix B, Development configuration variables (for myplc-devel).

    To build MyPLC, or any PlanetLab source code module, from within the MyPLC development environment, execute the following commands as root:

    -

    Example 9. Building MyPLC.

    +

    Example 9. Building MyPLC.

    # Initialize MyPLC development environment
 service plc-devel start
 
@@ -667,11 +709,11 @@ make -C $DATE
    /plc/devel/data/build/$DATE/RPMS/ that you may copy to the /var/www/html/install-rpms/planetlab - directory of your MyPLC installation (see Section 3, “Installation”).

    + directory of your MyPLC installation (see Section 3, “Installating and using MyPLC”).

    -5.4. Updating CVS

    +4.5. Updating CVS

    A complete snapshot of the PlanetLab source code is included with the MyPLC development environment as a CVS repository in /plc/devel/data/cvs. This CVS repository may @@ -699,7 +741,7 @@ make -C $DATE execute the following commands as root from within the MyPLC development environment:

    -

    Example 10. Updating /data/cvs from /data/cvs-0.4-3.

    +

    Example 10. Updating /data/cvs from /data/cvs-0.4-3.

    Warning: This may cause severe, irreversible changes to be made to your local repository. Always tag your local repository before @@ -729,7 +771,7 @@ rm -rf $TMP

    -A. Configuration variables (for myplc)

    +A. Configuration variables (for myplc)

    Listed below is the set of standard configuration variables and their default values, defined in the template /etc/planetlab/default_config.xml. Additional @@ -1328,7 +1370,7 @@ rm -rf $TMP

    -B. Development configuration variables (for myplc-devel)

    +B. Development configuration variables (for myplc-devel)
    PLC_DEVEL_FEDORA_RELEASE
    @@ -1380,10 +1422,11 @@ rm -rf $TMP

    -Bibliography

    +Bibliography

    [1] Mark Huang. PlanetLab Technical Contact's Guide.

    +dummy 1.11 for cathing up with the xml numbering -- 2.47.0
    Revision History