The information contained in these pages is the property of the Mid-Atlantic Crossroads (MAX).
If you have questions or comments, please contact MAX Administration
mirror.centos.org for the 'Website Name', and centos/5.2/os/i386 for the 'CentOS Directory'.
dmesg later on because you will be booting a vserver-enabled kernel, which does not include Xen support. If you accidentally select 'Xen', you will want to turn off libvirtd using chkconfig.
planetlab1.domain.org
planetlab1.domain.org is an A record pointing to the IP address 192.168.100.133.
myplc.domain.org is an A record pointing to the IP address 192.168.100.131.
/etc/yum.repos.d/dhozac-vserver.repo and populate it with the following:
[dhozac-vserver] name=Linux-VServer related packages for CentOS $releasever - $basearch baseurl=http://rpm.hozac.com/dhozac/centos/$releasever/vserver/$basearch gpgkey=http://rpm.hozac.com/conf/keys/RPM-DHOZAC-GPG-KEY
yum -y update yum and yum -y install kernel
/boot/grub/menu.lst (is actually a symlink to grub.conf in CentOS)
yum command should have added something like this (it should be the first kernel entry):
title CentOS (2.6.22.19-vs2.3.0.34.1)
root (hd0,0)
kernel /vmlinuz-2.6.22.19-vs2.3.0.34.1 ro root=/dev/VolGroup00/LogVol00
initrd /initrd-2.6.22.19-vs2.3.0.34.1.img
default=0 in order to boot this kernel by default
/etc/ssh/sshd_config, change ListenAddress to the IP address configured eth0 (would block any guest's attempt to run sshd if you do not do this because sshd binds to '*:22' by default)
/etc/sysconfig/selinux, set SELINUX=disabled
[root@planetlab1 ~]# uname -a Linux planetlab1 2.6.22.19-vs2.3.0.34.1 #1 SMP Mon Mar 17 05:32:04 EDT 2008 i686 i686 i386 GNU/Linux
[root@planetlab1 ~]# yum install util-vserver-core [root@planetlab1 ~]# yum install util-vserver-lib [root@planetlab1 ~]# yum install util-vserver-sysv [root@planetlab1 ~]# yum install util-vserver-build
yum -y install util-vserver instead of the four commands above.
[root@planetlab1 ~]# /etc/init.d/vprocunhide start Fixing /proc entries visibility... [ OK ] [root@planetlab1 ~]# chkconfig vservers-default on [root@planetlab1 ~]# chkconfig --list vservers-default vservers-default 0:off 1:off 2:on 3:on 4:on 5:on 6:off
myplc-native will run inside a vserver
[root@planetlab1 ~]# cd /root [root@planetlab1 ~]# svn co http://svn.planet-lab.org/svn/build/trunk svn-build
vbuild-fedora-mirror.sh commands below, we found the first one to give the best performance from MAX:
[root@planetlab1 ~]# cd /root/svn-build [root@planetlab1 svn-build]# ./vbuild-fedora-mirror.sh -v -l -f f8 -u rsync://fedora.mirror.iweb.ca/fedora [root@planetlab1 svn-build]# ./vbuild-fedora-mirror.sh -v -l -f f8 -u rsync://rsync.gtlib.gatech.edu/fedora-enchilada/linux [root@planetlab1 svn-build]# ./vbuild-fedora-mirror.sh -v -l -f f8 -s
planetlab1.domain.org server.
planetlab1.domain.org and serve up Fedora/CentOS RPMs so that vservers can quickly be instantiated.
[root@planetlab1 ~]# /etc/init.d/httpd start
[root@planetlab1 ~]# chkconfig --level 2345 httpd on [root@planetlab1 ~]# chkconfig --list httpd httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@planetlab1 ~]# cd /var/www/html [root@planetlab1 html]# ln -s /mirror mirror
/etc/httpd/conf/httpd.conf to only listen on 127.0.0.1:80 and root context's public IP, for example:
Listen 127.0.0.1:80 Listen 192.168.100.133:80 ServerName planetlab1.domain.org
iptables rules to the RH-Firewall-1-INPUT chain in /etc/sysconfig/iptables. For example, we limit incoming requests on TCP port 80 and 443 to our local network (206.196.176.0/21):
-A RH-Firewall-1-INPUT -s 206.196.176.0/21 -p tcp --dport 80 -j ACCEPT -A RH-Firewall-1-INPUT -s 206.196.176.0/21 -p tcp --dport 443 -j ACCEPT
/etc/init.d/iptables restart to apply the changes
/etc/vservers/.distributions/[f8|centos5]/yum.repos.d/building.repo so that baseurl points to http://planetlab1.domain.org/mirror/ instead of http://localhost/mirror/
[root@planetlab1 ~]# cd /root/svn-build/mirroring/ [root@planetlab1 mirroring]# ./mirror.sh -f f8 -u http://planetlab1.domain.org/mirror/ init [root@planetlab1 mirroring]# ./mirror.sh -f centos5 -u http://planetlab1.domain.org/mirror/ init
mirror.sh -a looks like the following (check that baseurl is correct):
[root@planetlab1 mirroring]# ./mirror.sh -a ==================== Contents of /etc/vservers/.distributions/f8/yum.repos.d/ ==> /etc/vservers/.distributions/f8/yum.repos.d//building.repo <== [fedora] name=Fedora 8 - $basearch baseurl=http://planetlab1.domain.org/mirror/fedora/releases/8/Everything/$basearch/os/ enabled=1 gpgcheck=1 gpgkey=http://redhat.download.fedoraproject.org/pub/fedora/linux/releases/8/Everything/$basearch/os/RPM-GPG-KEY-fedora http://redhat.download.fedoraproject.org/pub/fedora/linux/releases/8/Everything/$basearch/os/RPM-GPG-KEY [updates] name=Fedora 8 - $basearch - Updates baseurl=http://planetlab1.domain.org/mirror/fedora/updates/8/$basearch/ enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora [updates-newkey] name=Fedora 8 - $basearch - Updates Newkey baseurl=http://planetlab1.domain.org/mirror/fedora/updates/8/$basearch.newkey/ enabled=1 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-8-and-9 ==================== /etc/vservers/.distributions/f9/yum.repos.d/ does not exist ==================== Contents of /etc/vservers/.distributions/centos5/yum.repos.d/ ==> /etc/vservers/.distributions/centos5/yum.repos.d//building.repo <== [base] name=CentOS 5.2 - $basearch - Base baseurl=http://planetlab1.domain.org/mirror/centos/5.2/os/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 [updates] name=CentOS 5.2 - $basearch - Released Updates baseurl=http://planetlab1.domain.org/mirror/centos/5.2/updates/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 [epel] name=Extra Packages for Enterprise Linux 5 - $basearch baseurl=http://planetlab1.domain.org/mirror/epel/5/$basearch/ gpgcheck=1 gpgkey=http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL
myplc-native is a software package that includes everything you need to manage and slice PlanetLab nodes. It will run inside a vserver on planetlab1.domain.org. We will call that vserver myplc.domain.org.
planetlab1.domain.org) has an IP address of 192.168.100.133. We will use a different IP address and hostname for the vserver running myplc-native, in this case, it will be myplc.domain.org with an IP address of 192.168.100.131.
vtest-init-vserver.sh script:
[root@planetlab1 ~]# cd /root/svn-build [root@planetlab1 svn-build]# ./vtest-init-vserver.sh -p linux32 myplc http://build.planet-lab.org/planetlab/f8/planetlab-f8-linux32-4.2-rc24/RPMS/ -- \ --interface eth0:192.168.100.131 --hostname myplc.domain.org &> myplc.log &NOTE: Visit http://build.planet-lab.org/planetlab/f8/?C=M;O=D to find the latest release and change the URL which you pass to the
vtest-init-vserver.sh script. If you are interested in running the OneLab build of the PlanetLab software, begin by visiting http://build.onelab.eu/ to find a suitable URL to pass to vtest-init-vserver.sh.
myplc-native package:
[root@planetlab1 svn-build]# vserver myplc enter [myplc] / # yum -y install myplc-native
plc service:
[myplc] / # service plc start [myplc] / # service plc stop
chkconfig to make sure it comes up when this vserver is started:
[myplc] / # chkconfig plc on [myplc] / # chkconfig --list plc plc 0:off 1:off 2:on 3:on 4:on 5:on 6:off
plc-config-tty
[myplc] ~ # plc-config-tty
Enter command (u for usual changes, w to save, ? for help) u
== PLC_NAME : [My Domain PlanetLab Central]
== PLC_SLICE_PREFIX : [myplc]
== PLC_ROOT_USER : [pl-admin@domain.org]
== PLC_ROOT_PASSWORD : [root] password
== PLC_MAIL_ENABLED : [true]
== PLC_MAIL_SUPPORT_ADDRESS : [pl-admin@domain.org]
== PLC_DB_HOST : [localhost.localdomain] myplc.domain.org
== PLC_API_HOST : [localhost.localdomain] myplc.domain.org
== PLC_WWW_HOST : [localhost.localdomain] myplc.domain.org
== PLC_BOOT_HOST : [localhost.localdomain] myplc.domain.org
== PLC_NET_DNS1 : [192.168.1.1]
== PLC_NET_DNS2 : [192.168.2.1]
Enter command (u for usual changes, w to save, ? for help) w
Wrote /etc/planetlab/configs/site.xml
Merged
/etc/planetlab/default_config.xml
and /etc/planetlab/configs/site.xml
into /etc/planetlab/plc_config.xml
+ service plc reload
You might want to type 'r' (restart plc) or 'q' (quit)
Enter command (u for usual changes, w to save, ? for help) r
==================== Stopping plc
...
==================== Starting plc
...
planetlab1.domain.org (the root context), you will see messages like this:
> vxW: [<BB>crond<AB>,12389:#40056|40056|40056] messing with the procfs.
sed -i -e 's/.*pam_loginuid.*/#\0/' /etc/pam.d/*
is_public variable in the sites table of the planetlab4 postgresql database must be set to 't' (true) to allow new users to be created.
[root@planetlab1 ~]# vserver myplc enter [myplc] ~ # su -l postgres -bash-3.2$ psql planetlab4 planetlab4=# update sites set is_public='t'; UPDATE 1 planetlab4=#
/usr/share/bootmanager/source/configuration
SKIP_HARDWARE_REQUIREMENT_CHECK=1
service plc stop and service plc start within the myplc vserver
admin@domain.org (see above - set by running plc-config-tty)
password (see above - set by running plc-config-tty)
ssh-keygen -t dsa. Then upload the file ~/.ssh/id_dsa.pub.
You will need to use this SSH key to login to "slices" that are created for you in later steps.
planetlab2.domain.org and planetlab3.domain.org.
Once the node is added, you must download the boot materials for that node. Click on "My Nodes" on the left bar, then click on the hostname of the node you just added. On this page, you will be able to download an ISO image (for burning to CD), a USB image, the planetlab config file, or a generic ISO/USB image.
Burn the ISO image to a CD-ROM. Boot the node off of that CD.
You can control the 'boot state' of each node from the MyPLC web interface. Click on "My Nodes" on the left bar, click a hostname, and then examine the first option 'Boot State'. The link to the right of it ("What's this?") explains what each boot state option means.
If all goes well, after you boot up the CD the machine should register itself with MyPLC. It will ask you for confirmation before wiping the entire machine. The boot state in MyPLC should eventually come up to 'boot' if all goes well. The node should be "sliceable" at this point.
testing for the name field in our examples below)
planetlab2 and planetlab3, then click "Add Nodes"
myplc_testing and have associated node planetlab2.domain.org and user admin@domain.org with that slice.
What actually happens when you use "create slice" above is this:
myplc_testing is created on planetlab2.domain.org (NOTE: in the root context! not the vserver!)
admin@domain.org are copied to planetlab2.domain.org:/home/myplc_testing/.ssh/authorized_keys (NOTE: in the root context! not the vserver!)
myplc_testing is created (see /etc/vservers/myplc_testing/...)
pl_sshd on which somehow logs users into their vservers automatically. Take a look at the sshd processes running on a PlanetLab node:
[root@planetlab2 ssh]# ps auxwww | grep sshd | grep sbin root 1263 0.0 0.2 6880 1060 ? Ss Nov06 0:52 /usr/sbin/sshd root 1289 0.0 0.2 6880 1056 ? Ss Nov06 0:00 /usr/local/sbin/pl_sshd -o PidFile /var/run/pl_sshd.pid -p 806 [root@planetlab2 ssh]# lsof -i -U -P | grep ^sshd | grep LISTEN sshd 1263 root 3u IPv6 4467 TCP *:22 (LISTEN) sshd 1289 root 3u IPv6 4512 TCP *:806 (LISTEN)Note that 'sshd' listens on port 22, but 'pl_sshd' listens on port 806. Whenever I login as user
myplc_testing using the SSH key for admin@domain.org, I am transferred into the myplc_testing vserver:
somehost% ssh myplc_testing@planetlab2.domain.org [myplc_testing@planetlab2 ~]$ sudo -s [root@planetlab2 ~]# ps auxwww USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND 508 26605 0.5 0.2 2632 1416 ? Ss 19:32 0:00 /bin/bash -l root 26617 2.0 0.2 2632 1424 ? S 19:32 0:00 /bin/bash root 26621 0.0 0.1 2456 824 ? R+ 19:32 0:00 ps auxwwwNote that I cannot "see" my SSH
.authorized_keys file -- because that actually lives in the root context, not the vserver!
[myplc_testing@planetlab2 ~]$ ls -l ~/.ssh ls: cannot access /home/myplc_testing/.ssh: No such file or directory
/etc/planetlab/root_ssh_key.rsa. NOTE: If the node has come up in debug mode (either intentionally or otherwise) you must use the /etc/planetlab/debug_ssh_key.rsa private key. For example:
[root@planetlab1 ~]# ssh root@planetlab1.domain.org [root@planetlab1 ~]# vserver myplc enter [myplc] / # ssh -i /etc/planetlab/root_ssh_key.rsa root@planetlab2.domain.org [root@planetlab2 ~]# uname -a Linux planetlab2.domain.org 2.6.22.19-vs2.3.0.34.29.planetlab #1 SMP Fri Oct 17 12:33:05 EDT 2008 i686 i686 i386 GNU/Linux
vconfig add eth1 3000 and configured with an IP address by running ifconfig eth1.3000 inet A.B.C.D. However, this method will not work for vservers.
--interface ethX.YYYY directly to the vserver build command. For example, this could be passed into the vtest-init-vserver.sh script:
./vtest-init-vserver.sh [...] -- --interface eth0:10.1.1.1/24 --interface eth1.3000:10.2.2.1/24 --hostname [...]
[root@planetlab1 ~]# vconfig add eth1 1234 Added VLAN with VID == 1234 to IF -:eth1:- [root@planetlab1 ~]# ifconfig eth1.1234 inet 10.1.1.1 netmask 255.255.255.0
[root@planetlab1 ~]# vserver test-vlan enter
bash-3.2# ifconfig eth1.1234
eth1.1234 Link encap:Ethernet HWaddr 00:30:48:9A:D3:89
inet addr:10.30.30.1 Bcast:10.30.30.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:8286 (8.0 KiB)
plcsh is a command-line interface to the PlanetLab API
plcsh using subversion:
[root@planetlab1 ~]# svn co http://svn.planet-lab.org/svn/plcmdline/trunk plcsh A plcsh/plcapilib.py A plcsh/setup.py A plcsh/plcapilib.spec A plcsh/plcsh A plcsh/Makefile A plcsh/plcmdline.py Checked out revision 12695.
plcsh as follows, using -h to point it to your PLCAPI and -u to specify the user that you created above:
[root@planetlab1 ~]# cd plcsh [root@planetlab1 plcsh]# ./plcsh -h https://myplc.domain.org/PLCAPI/ -r user -u admin@domain.org Password: [enter password here] PlanetLab Central API server at https://myplc.domain.org/PLCAPI/ admin@domain.org connected as user using password authentication Type "system.listMethods()" or "help(method)" for more information. [chris@maxgigapop.net user]>>>
[root@planetlab2 ~]# grep interval /usr/share/NodeManager/nm.py
parser.add_option('-p', '--period', action='store', dest='period', default=600, help='Polling interval (sec)')
parser.add_option('-r', '--random', action='store', dest='random', default=301, help='Range for additional random polling interval (sec)')
/etc/init.d/nm and add these options to the command line.
/etc/init.d/nm and tweak this line: options=${OPTIONS-"-d -s -p 30 -r 1"}
/etc/init.d/nm stop
/etc/init.d/nm start
ps auxwww|grep nm to make sure you see the new options -p 30 -r 1 listed on the command line
/usr/lib/python2.5/site-packages/vserverimpl.so binary can be found in http://svn.planet-lab.org/svn/util-vserver-pl/ (see vserverimpl.c)
yum install pyOpenSSL (necessary to run python code)
yum install m2crypto (also necessry to run python code)
yum install make (geniwrapper now requires make package)
[max-myplc] /usr/local/share/geniwrapper/geni # python gimport.py Base Directory: /usr/local/share/geniwrapper/ Import: creating top level authorities Hierarchy: creating authority: plc Segmentation fault
gcc installed in the myplc vserver was not as easy as it should be. yum install gcc kept complaining with "Error: Missing Dependency: kernel-headers is needed by package glibc-headers-2.7-2.i386"
yum install kernel-headers for some reason. I did the following to install the kernel-headers package and finally install gcc so that I could build pyOpenSSL v0.8:
% vserver myplc enter [myplc] ~ # wget http://planetlab1.domain.org/mirror/fedora/releases/8/Everything/i386/os/Packages/kernel-headers-2.6.23.1-42.fc8.i386.rpm [myplc] ~ # rpm -i kernel-headers-2.6.23.1-42.fc8.i386.rpm [myplc] ~ # yum install gcc
yum install openssl-devel. Now I could build pyOpenSSL using python setup.py build. I removed pyOpenSSL v0.6 with yum erase pyOpenSSL and the installed v0.8 with python setup.py install.
python gimport.py succeeds without any segfaults, but it fails to import a user:
[max-myplc] /usr/local/share/geniwrapper/geni # python gimport.py
Base Directory: /usr/local/share/geniwrapper
Import: creating top level authorities
maxplc :
testing :
Import: adding maxplc to trusted list
Import_Site: importing site testing.maxpl
Import: importing person testing.maxpl.chris
XXX: DSA key encountered, ignoring
Failed to import: {'bio': '', 'first_name': 'Default', 'last_name': 'Administrator', 'last_updated': 1239288497, 'roles': ['admin', 'pi', 'user', 'tech'], 'title': 'Engineer', 'url': '', 'key_ids': [1], 'enabled': True, 'slice_ids': [], 'phone': '240-687-1498', 'peer_person_id': None, 'role_ids': [10, 20, 30, 40], 'person_id': 2, 'date_created': 1225830970, 'site_ids': [1], 'peer_id': None, 'email': 'chris@maxgigapop.net'}
...
gimport.py:
[max-myplc] /usr/local/share/geniwrapper/geni # python gimport.py Base Directory: /usr/local/share/geniwrapper Import: creating top level authorities Hierarchy: creating authority: maxpl maxpl : Import: creating table for authority maxpl NOTICE: table "geni$maxpl" does not exist, skipping inserting authority record for maxpl maxpl : Import: adding maxpl to trusted list Import_Site: importing site maxpl.maxpl Hierarchy: creating authority: maxpl.maxpl inserting authority record for maxpl.maxpl Import: importing person maxpl.maxpl.chris Import: creating table for authority maxpl.maxpl NOTICE: table "geni$maxpl$maxpl" does not exist, skipping /usr/share/keyconvert/keyconvert /tmp/tmp9PeVdQ /tmp/tmp1Q8B7f keytype = ssh-rsa completed inserting user record for maxpl.maxpl.chris /usr/share/keyconvert/keyconvert /tmp/tmpXt8DJE /tmp/tmpAgJ2Xp keytype = ssh-rsa completed updating user record for maxpl.maxpl.chris Import: importing person maxpl.maxpl.poneil person maxpl.maxpl.poneil does not have a PL public key inserting user record for maxpl.maxpl.poneil Import: importing person maxpl.maxpl.tlehman person maxpl.maxpl.tlehman does not have a PL public key inserting user record for maxpl.maxpl.tlehman Import: importing person maxpl.maxpl.jflidr person maxpl.maxpl.jflidr does not have a PL public key inserting user record for maxpl.maxpl.jflidr Import: importing slice maxpl.maxpl.netflow inserting slice record for maxpl.maxpl.netflow Import: importing slice maxpl.maxpl.sirius inserting slice record for maxpl.maxpl.sirius Import: importing node maxpl.maxpl.planetlab2 inserting node record for maxpl.maxpl.planetlab2 Import: importing node maxpl.maxpl.planetlab3 inserting node record for maxpl.maxpl.planetlab3 Import: importing node maxpl.maxpl.planetlab5 inserting node record for maxpl.maxpl.planetlab5 Import: importing node maxpl.maxpl.planetlab4 inserting node record for maxpl.maxpl.planetlab4
gimport.py did, try rm -rf trusted_roots/ authorities/ then su -l postgres, psql planetlab4, type \dt, drop any tables starting with geni$ using drop table [tablename]
[max-myplc] /usr/local/share/geniwrapper # export DESTDIR=/ [max-myplc] /usr/local/share/geniwrapper # make ... [max-myplc] /usr/local/share/geniwrapper # make install ...
[max-myplc] /usr/local/share/geniwrapper # ls -l /etc/geni/geni_config -rw-r--r-- 1 root root 1809 2009-05-27 11:36 /etc/geni/geni_config [max-myplc] /usr/local/share/geniwrapper # ls -l /etc/init.d/geniwrapper -rw-r--r-- 1 root root 1351 2009-05-27 11:17 /etc/init.d/geniwrapper [max-myplc] /usr/local/share/geniwrapper # ls -l /usr/bin/plc.py -rwxr-xr-x 1 root root 4602 2009-05-27 11:36 /usr/bin/plc.py [max-myplc] /usr/local/share/geniwrapper # ls -l /usr/bin/sfi.py -rwxr-xr-x 1 root root 20776 2009-05-27 11:36 /usr/bin/sfi.py
/etc/geni/geni_config has not been configured, run geni-config-tty
/etc/init.d/geniwrapper:
[max-myplc] /usr/local/share/geniwrapper # chmod +x /etc/init.d/geniwrapper
[max-myplc] /usr/local/share/geniwrapper # /etc/init.d/geniwrapper start Starting GENIWrapper: Registry Aggregate [ OK ] SliceMgr [ OK ]
plc.py is running and listening on TCP ports 12345, 12346, 12347:
[max-myplc] /usr/local/share/geniwrapper # lsof -P | grep plc.py | grep LISTEN plc.py 10210 root 5u IPv4 8126880 TCP *:12345 (LISTEN) plc.py 10223 root 5u IPv4 8126891 TCP *:12346 (LISTEN) plc.py 10236 root 5u IPv4 8126903 TCP *:12347 (LISTEN)
[max-myplc] /usr/local/share/geniwrapper/cmdline # cat configSfi.sh export SFI_AUTH=maxpl.maxpl export SFI_USER=$SFI_AUTH.chris export SFI_REGISTRY=http://max-myplc.dragon.maxgigapop.net:12345/ export SFI_SM=http://max-myplc.dragon.maxgigapop.net:12346/ [max-myplc] /usr/local/share/geniwrapper/cmdline # source configSfi.sh
[max-myplc] /usr/local/share/geniwrapper # mkdir ~/.sfi [max-myplc] /usr/local/share/geniwrapper # cd ~/.sfi [max-myplc] ~/.sfi # cat > chris.pkey -----BEGIN RSA PRIVATE KEY----- [ NOTE!!! this must be an RSA key! ] -----END RSA PRIVATE KEY-----
CertMissingParent: u'testing' in /var/log/geni.daemon
[max-myplc] /usr/local/share/geniwrapper/geni # cp authorities/maxpl/maxpl.pkey server.key
/var/log/geni.daemon (or 'sslv3 alert handshake failure' in the sfi.py traceback)
[max-myplc] /usr/local/share/geniwrapper/geni # cp authorities/maxpl/maxpl.gid server.cert
sfi.py now, for example:
[max-myplc] /usr/local/share/geniwrapper/cmdline # ./sfi.py slices
maxpl.maxpl.netflow
maxpl.maxpl.sirius
[max-myplc] /usr/local/share/geniwrapper/cmdline # ./sfi.py show maxpl.maxpl.chris
RECORD maxpl.maxpl.chris
hrn: maxpl.maxpl.chris
type: user
gid:
hrn: maxpl.maxpl.chris
uuid: 97506516643947256837792453982171939435
pointer: 2
geni_info:
email : admin@domain.org
pl_info:
bio :
first_name : Default
last_name : Administrator
last_updated : 1243443965
roles : ['admin', 'pi', 'user', 'tech']
title : Engineer
url :
slices : []
enabled : True
sites : ['maxpl.maxpl']
phone : 123-456-7890
keys : ['...']
date_created : 1225830970
email : admin@domain.org