From: Mark Huang Date: Wed, 19 Jul 2006 17:06:53 +0000 (+0000) Subject: regenerate X-Git-Tag: planetlab-4_0-rc1~126 X-Git-Url: http://git.onelab.eu/?a=commitdiff_plain;h=0eb8899f63b2ae58b5b5a78fdf1144dcdb62da88;p=myplc.git regenerate --- diff --git a/doc/myplc.pdf b/doc/myplc.pdf index f8a636c..5937bd9 100644 Binary files a/doc/myplc.pdf and b/doc/myplc.pdf differ diff --git a/doc/myplc.php b/doc/myplc.php index fbc314c..d70807b 100644 --- a/doc/myplc.php +++ b/doc/myplc.php @@ -22,9 +22,13 @@ April 7, 2006 MLH - -

Initial draft.

- +

Initial draft.

+ +Revision 1.1 +July 19, 2006 +MLH + +

Add development environment.

Abstract

@@ -41,30 +45,30 @@

Table of Contents

-
1. Overview
+
1. Overview
2. Installation
-
3. Quickstart
+
3. Quickstart
3.1. Changing the configuration
-
3.2. Installing nodes
-
3.3. Administering nodes
-
3.4. Creating a slice
+
3.2. Installing nodes
+
3.3. Administering nodes
+
3.4. Creating a slice
-
4. Rebuilding and customizing MyPLC
+
4. Rebuilding and customizing MyPLC
-
4.1. Installation
-
4.2. Fedora Core 4 mirror requirement
+
4.1. Installation
+
4.2. Fedora Core 4 mirror requirement
4.3. Building MyPLC
4.4. Updating CVS
-
A. Configuration variables
-
B. Development environment configuration variables
-
Bibliography
+
A. Configuration variables
+
B. Development environment configuration variables
+
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 @@ -95,7 +99,7 @@ no external dependencies, allowing it to be installed on practically any Linux 2.6 based distribution:

-

Example 1. Installing MyPLC.

+

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
 
@@ -194,7 +198,7 @@ service plc stop
the chkconfig command on a Red Hat or Fedora host system:

-

Example 3. Disabling automatic startup of MyPLC.

+

Example 3. Disabling automatic startup of MyPLC.

# Disable automatic startup
 chkconfig plc off
 
@@ -219,13 +223,13 @@ chkconfig plc on

-3. Quickstart

+3. 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.

+

Example 4. A successful MyPLC startup.

Mounting PLC:                                              [  OK  ]
 PLC: Generating network files:                             [  OK  ]
 PLC: Starting system logger:                               [  OK  ]
@@ -356,7 +360,7 @@ PLC: Signing node packages:                                [  OK  ]

-3.2. Installing nodes

+3.2. Installing nodes

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

-3.3. Administering nodes

+3.3. 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
@@ -408,7 +412,7 @@ PLC: Signing node packages: [ OK ]

-3.4. Creating a slice

+3.4. Creating a slice

Create a slice by clicking Create Slice under the Slices tab. Fill in all the appropriate details, then click Create. Add @@ -423,7 +427,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
 
@@ -435,7 +439,7 @@ vserver pl_conf exec service pl_conf restart

-4. 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 @@ -452,7 +456,7 @@ vserver pl_conf exec service pl_conf restart repository.

-4.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 @@ -461,15 +465,15 @@ vserver pl_conf exec service pl_conf restart chroot jail should not be modified directly, as they are subject to upgrade.

-

Example 7. Installing the MyPLC development environment.

+

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
+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 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

The MyPLC development environment installs the following files and directories:

@@ -523,7 +527,7 @@ vserver pl_conf exec service pl_conf restart

-4.2. Fedora Core 4 mirror requirement

+4.2. 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 @@ -555,7 +559,7 @@ vserver pl_conf exec service pl_conf restart such as wget or rsync to download the RPMS from a public mirror:

-

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

+

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

mkdir -p /plc/devel/data/fedora
 cd /plc/devel/data/fedora
 
@@ -583,7 +587,7 @@ done
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
 
@@ -638,7 +642,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 @@ -668,7 +672,7 @@ rm -rf $TMP

-A. Configuration variables

+A. Configuration variables

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

-B. Development environment configuration variables

+B. Development environment configuration variables
PLC_DEVEL_FEDORA_RELEASE
@@ -1319,7 +1323,7 @@ rm -rf $TMP

-Bibliography

+Bibliography

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