Changes between Version 10 and Version 11 of GpoLab/MyplcReferenceImplementation


Ignore:
Timestamp:
04/15/11 13:14:59 (8 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GpoLab/MyplcReferenceImplementation

    v10 v11  
    44
    55== Purpose ==
    6 The purpose of this document is to provide a reference implementation for the installation of MyPLC-based PlanetLab deployment at GENI sites.  The contents of this document are based on experiences of setting up MyPLC-based PlanetLab deployments at the GPO.  Following this document exactly should give you a working MyPLC-based PlanetLab deployment that supports the GENI AM API using the SFA software; however, this document is intended only to be an example configuration. 
     6The purpose of this document is to provide a reference implementation for the installation of MyPLC-based !PlanetLab deployment at GENI sites.  The contents of this document are based on experiences of setting up MyPLC-based !PlanetLab deployments at the GPO.  Following this document exactly should give you a working MyPLC-based !PlanetLab deployment that supports the GENI AM API using the SFA software; however, this document is intended only to be an example configuration. 
    77
    88== Scope ==
     
    1313'''Important note:''' When choosing values for login_base variables (<mgmt_login_base> and <public_login_base>), you must choose the value carefully.  After setting these values, it is strongly recommended not to change them.  Furthermore, it is known that including a dash or an underscore in the values of the login_base variables can cause problems.  For these reasons, the GPO recommends that you choose an ''alphanumeric'' value for the login_base variables.[[BR]][[BR]]
    1414'''Important note:''' When setting values for the PLC variable PLC_DB_HOST and the SFA variable SFA_PLC_DB_HOST, unless you ''explicity'' modify the PLC configuration to not manage DNS, you must set PLC_DB_HOST to localhost.localdomain.  This tutorial assumes that you will use localhost.localdomain for the value of PLC_DB_HOST.
     15
     16If you choose to use the [#PathA:OneSingleSite Single Site configuration], then you will need to define the following variables in addition to the variables above.
     17
    1518|| '''Variable''' || '''GPO Values''' || '''Description''' || '''Important Notes''' ||
    1619|| <base_os> || Fedora 8 ||  The OS which you are installing MyPLC on ||  ||
    1720|| <myplc_distribution> || planetlab-f8-i386-5.0 || The MyPLC distribution which you are using, comprised of base OS, architecture, and PLC version ||  ||
    1821|| <myplc_baseurl> || http://build.planet-lab.org/planetlab/f8/planetlab-f8-i386-5.0-rc14/RPMS || URL of the MyPLC repository which you will be using ||  ||
    19 || <myplc_name> ||  || Name for your MyPLC instance and default site ||  ||
    20 || <myplc_shortname> ||  || Abbreviated name for your MyPLC instance ||  ||
    21 || <mgmt_login_base> ||  || The prefix for usernames associated with all slices at a site || This variable should '''not''' be changed after you set it.[[BR]]We recommend using only alphanumeric names for the login base. ||
    2222|| <myplc_root_user> || root@gpolab.bbn.com || MyPLC application's initial administrative user of a MyPLC instance || Do not use a plus character here, or sfa_import.py will fail later ||
    2323|| <myplc_root_password> ||  || MyPLC application's password for <myplc_root_user> ||  ||
     
    2828|| <public_site_name> || myplc.gpolab.bbn.com || Full name of public site ||  ||
    2929|| <public_site_shortname> || myplc || Abbreviated name of public site ||  ||
    30 || <public_login_base> || gpolab || Prefix for usernames of PlanetLab slices || This variable should '''not''' be changed after you set it.[[BR]]We recommend using only alphanumeric names for the login base. ||
     30|| <public_login_base> || gpolab || Prefix for usernames of !PlanetLab slices || This variable should '''not''' be changed after you set it.[[BR]]We recommend using only alphanumeric names for the login base. ||
    3131|| <myplc_deployment> || planetlab-f8-i386 || Deployment string containing base OS and architecture information ||  ||
    3232|| <site_latitude> || 42.3905 || Latitude of machine hosting MyPLC site || This should be in double format with no quotes surrounding it ||
     
    3434|| <sfa_git_tag> || sfa-geni-gec9 || Latest recommended stable tag of SFA software in the git repository ||  ||
    3535
     36If you choose to use the [#PathB:TwoSites Two Site configuration], then you will need to define the following variables in addition to the variables above.
     37
     38|| '''Variable''' || '''GPO Values''' || '''Description''' || '''Important Notes''' ||
     39|| <myplc_name> ||  || Name for your MyPLC instance and default site ||  ||
     40|| <myplc_shortname> ||  || Abbreviated name for your MyPLC instance ||  ||
     41|| <mgmt_login_base> ||  || The prefix for usernames associated with all slices at a site || This variable should '''not''' be changed after you set it.[[BR]]We recommend using only alphanumeric names for the login base. ||
     42
    3643= Installing MyPLC from Scratch =
    3744
    3845== Step 1: Install the Base OS ==
    39 The PlanetLab team also currently supports Fedora 8 and Fedora 12 as the base OS for MyPLCs.  If you choose to use a different Fedora distribution from the distribution that the GPO lab uses, some of the following steps in this section may not apply.
     46The !PlanetLab team also currently supports Fedora 8 and Fedora 12 as the base OS for MyPLCs.  If you choose to use a different Fedora distribution from the distribution that the GPO lab uses, some of the following steps in this section may not apply.
    4047
    4148=== SELinux ===
     
    4653 * TCP port 80 access is needed access to the MyPLC web interface and the PLC API
    4754 * TCP port 443 access is needed access to the MyPLC web interface and the PLC API
    48   * Needed by PlanetLab nodes
     55  * Needed by !PlanetLab nodes
    4956  * Useful for MyPLC administrators
    5057  * Can be used by experimenters
     
    7178== Step 3: Configuring MyPLC Default Site ==
    7279There are two paths you can take in terms of setting up your MyPLC sites.
    73  * Path A: set up one single site for both management of MyPLC and management of PlanetLab nodes. 
     80 * Path A: set up one single site for both management of MyPLC and management of !PlanetLab nodes. 
    7481 * Path B:
    7582  * Let PLC create a default site for administrators to manage PLC
    76   * Manually create another site for managing PlanetLab nodes. 
     83  * Manually create another site for managing !PlanetLab nodes. 
    7784
    7885A full explanation on these two choices can be found at [https://svn.planet-lab.org/wiki/MyPLCUserGuide#CreatingasiteandPIaccount].  GPO currently follows path A and only uses one site on its MyPLC machines; however this increases the amount of work that one must do to maintain the site.  Below, both paths are outlined.
     
    117124
    118125==== A Part 2: Setting the site as public ====
    119 Every time the plc service gets restarted (e.g. on boot), the site will be set as private.  The site that controls the PlanetLab nodes must be public for experimenters to use it.  ''Contact gpo-infra@geni.net if you'd like the workaround we use to automate this.''
     126Every time the plc service gets restarted (e.g. on boot), the site will be set as private.  The site that controls the !PlanetLab nodes must be public for experimenters to use it.  ''Contact gpo-infra@geni.net if you'd like the workaround we use to automate this.''
    120127
    121128Set the default site as public:
     
    280287Boot the node from the boot media you just downloaded, and verify that the MyPLC web interface shows that the node is in boot state.
    281288
    282 === Important Notes on PlanetLab Node Interfaces ===
     289=== Important Notes on !PlanetLab Node Interfaces ===
    283290If you have used <base_url>=http://build.planet-lab.org/planetlab/f8/planetlab-f8-i386-5.0-rc14/RPMS, then you will need to downgrade your `util-vserver-pl` package:
    284291 * Version packaged with this repository: util-vserver-pl-0.3.31.planetlab