Marc requested the ability to turn off bwlimits in NM. Also, since some nodes will have gigE connections to the outside world, moving from byte limits measured in KB to MB would probably be a good idea.
NM in head is currently broken. IIRC, dhozac was the last to play with it and I'm not certain what he did and didn't do. I've been careful to merge changes I've made to the branch into head so, hopefully, the code isnt THAT different. Regardless, I foresee at least a week of testing a tweaking before i can sign off on it.
SVN and Trac, running on poppins, uses LDAP for authentication. I've created user accounts for most of PLC, if not all. There are no API calls to grab passwords from the PL API and making a backdoor to sync PL passwords with LDAP passwords doesn't really appeal to me. So, in order for PLC to log in to trac, please do the following:
$ ssh root@poppins
# passwd <your username>
You should now be able to log in to http://svn.planet-lab.org/ and create/edit content.
i hate drupal
To Check Out:
$ svn co svn+ssh://svn.planet-lab.org/svn/NodeManager/trunk NodeManager
$ svn co https://svn.planet-lab.org/svn/NodeManager/trunk NodeManager
There were some hundred nodes with hung NMs. /var/log/nm<.gz.*> would look like the following:
Sat Sep 15 10:01:50 2007: bwmon: Found 271 running HTBs
After perusing OneLab's SVN and talking to dhozac on IRC, I like the idea of seperating out modules in our repository from their vanilla upstream versions and what exists in the trunk. So, preliminary structure for modules in SVN will be as follows.
I've given OneLab notice that we're taking the CVS down in order to upgrade cvs.planet-lab.org to something a little more modern. I'm taking the machine down after 5am UTC to begin the upgrade.
Marc weeded through CVS and removed the need to build PL using
July 12, 2007 PLC server maintenance, et. al.
I've been working on making all PLC services redundant and have been pretty successful except for the database. PostgreSQL does not support the notion of a "database cluster" out of the box. Third party patches claim to have solved this problem, but we have yet to investigate them.
I'm moving www to the backup database machine (cassidy). When we ordered new machines, I went ahead and asked for 1 extra to serve as a hot spare (for the database because of the above problem). The rationale is that if a machine misbehaves, I can grab the latest database dump and mix and match services and machines as needed.
PlanetLab software consists of the core system that runs at PLC and on individual nodes (available via SVN, with ongoing efforts outlined in a development roadmap), user-contributed software tools that can be used to manage PlanetLab slices, and user-contributed services that support a user community.