bxkvdzvzv

Trac is up. Please create a password.

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>
Changing password for user tmack.
New UNIX password:
Retype new UNIX password:
LDAP password information changed for <your username>
passwd: all authentication tokens updated successfully

You should now be able to log in to http://svn.planet-lab.org/ and create/edit content.

i hate drupal

i hate drupal

SVN cheat sheet

To Check Out:

(over ssh)

$  svn co svn+ssh://svn.planet-lab.org/svn/NodeManager/trunk NodeManager

(over https)

$ svn co https://svn.planet-lab.org/svn/NodeManager/trunk NodeManager

Tagging

SVN structure

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.

Module/trunk
  /tags
  /imports
  

 

4.1 rc2 Complete. Downtime announced.

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
myplc-devel, which provides a chroot fedora-core 4 environment to build
against. My major task for the next week is moving from CVS to SVN,
attic'ing old projects that are still in our repo. I had a conversation
with Thierry a few months ago concerning how we tag all of planetlab for
every release and how we should move to a scheme were we only tag a
single build package, and specify versions of subpackages needed for
building a particular tag. This will move us away from rebuilding all
of planetlab with each release and allow us to back track and bug fix
without overriding tags when HEAD has moved forward (as was the case
when there was a bug in 4.0 when Daniel was here and the wrong code was
pushed causing slivers to be deleted). This requires a large amount of
plumping to be rerouted but work now will save us headache in the
future. I'm going to tentatively say that this should take a week but
this may change.

Syndicate content