Upgrading the osg-client to Testing

Another lively blog post about upgrading a set of packages to testing.  Last time it was the osg-wn-client, this time it's the OSG-Client.  I will use a jira task to track my time and progress on it.

Again, I looked at tickets by component for the osg-client.  First, there are no bugs, only tasks.  Second, the tasks are major or below (and the major one is a documentation task really).

So, I went to the osg-client koji page, copied the dependencies to a text document, and started the pushing the dependencies to osg-testing.  One by one.  Really, a whole lot of:

koji tag-pkg el5-osg-testing owamp-3.2rc4-1

I found an extraneous package, the osg-voms-compat.  It is no longer needed since we distribute LSC files.  I removed it as a dependency of osg-client, and rebuilt the osg-client.

First iteration... only missed 2 dependencies of dependencies.  web100_userland and I2Util (both from Internet 2).  Second iteration... Success!

We now have osg-client in the testing repo.  Took less than an hour.

Upgrading OSG Software from Development to Testing

In the OSG-software team, there has been a lot of discussion when the right time to upgrade packages to testing from the developer playground.  I'm not going to go into the discussion much, other than it should be tracked in Jira.

I'm going to go through my process (as I do it) of upgrading the osg-wn-client from development to testing.

Check Jira for tickets by component.  For the osg-wn-client, I look at: osg-wn-client:

• Major: SOFTWARE-30: Add LSC files to the vomses.  This bug has a first draft of the documentation done.  It also is not a functional show stopper, rather it only affects the packagers.
• Minor: SOFTWARE-78: Pegasus RPM cleanup / FHS.  This is a feature request/task really.  Though nice to have, it doesn't change the functionality of the package.

After the bugs have been reviewed, (only 2), and especially since there are no 'blocker' bugs, we start the koji work.  First, I look at the osg-wn-client meta package.  I will upgrade the dependencies before upgrading the metapackage.  For each package in the the dependencies (some are from EPEL, so I don't need to do anything), I will go to the package's koji page, looking for the name of the latest build (or latest tested build).  The koji command is similiar to:

koji tag-pkg el5-osg-testing bestman2-2.1.1-5

It's important to note that these are just the first level dependencies of the osg-wn-client.  I will also need add packages that are dependencies of the dependencies such as the jdk (srm clients).

Once you have tagged all the builds that are dependencies of osg-wn-client, you can upgrade the meta-package.  Then it's time to pull out the VM.  I need to test the install, see if I caught all the packages.  Since we're upgrading so many packages all at once (likely a one time thing), we need to test the install along the way.

Luckily, I have mash running on a local server, so I can just execute mash to pull the latest from the testing repo.  If you want my mash configs, they're on github: https://github.com/djw8605/osg-mash.  I needed to edit the /etc/yum.repos.d/osg-testing.repo file in the VM in order to point to my local mash repo.

I did have missing dependencies: gfal, libglite_data_delegation_api_simple_c.so, libglite_data_util.so.0, libglite-sd-c.so.2, vdt-ca-certs.  Another iteration (after yum clean all)... Missing libglite_data_delegation_api_simple_c.  Another iteration... success!

To find what package provides what library, I just use the web interface, clicking on the RPM's info, to find what the package Provides.  I'm sure there is a clever yum command to do most of this for me, but this didn't take me much time anyways.

So, we now have a osg-wn-client in the osg-testing repo.  Stay tuned next week for the upgrading of the osg-client.  Just need to resolve the blocker ticket for the osg-client.

OSG Site Admin meeting: Day 2

Another beautiful (read: HOT) day in Lubbock.

Last night we ate at the National Ranching Heritage Center as part of social get together.  The food was great!  I had a great time talking other CMS collaborators as well.  I talked with some T3 admins from UC Riverside and Baylor, learning about what is like to run a T3 (and talking some Big Bang Theory).

I also talked with Horst from OU to find out that they are no longer running the CoLinux cluster on their desktop machines.  Rather, they are using VMWare to run Linux inside Windows on their desktops.  Something like 1600 cores.

The heritage center had a number of historical buildings from around the area.

(Credit: Horst Severini more)

The talks have been good.  Here's a quick picture from Doug's Globus Online talk.

OSG Site Admin meeting: Day 1

Hello from the hot, hot, hot Lubbock.

Had a good morning of broad plenary talks.  The indico schedule  gives links to the talks.

In the afternoon, I gave my 2 talks: GlideinWMS Frontend install and Campus Factory install.  We had one person install and get the campus factory up and working (though, only one was trying to install).  We had to add some custom pbs commands for their cluster in the pbs_local_submit_attributes.sh file.

Meanwhile, Jose was installing the glideinwms-vofrontend from RPMs.  He had a conflict with an igtf rpm of certificates.  Was solved by removing the igtf rpm, and allowing OSG to own the certificates.

Here's a picture from Marco's talk.  I'll upload more pictures later.

And from Greg's Talk:

And from my Hands-On:

Testing Release of OSG-Client RPM

It's finally here!  The first official testing release of the osg-client in RPM form.  We're asking anyone and everyone to go out there and start testing.  The official instructions are on the OSG Twiki.  We even made a Testing Client page if you want to run through some simple commands.

The instructions are simple, install EPEL, then install the VDT repo:

rpm -Uvh http://vdt.cs.wisc.edu/repos/3.0/el5/development/x86_64//vdt-release-3.0-2.noarch.rpm 

Install the osg-client (expect a lot of dependencies). My latest build downloaded 140MB of dependencies.

yum install --enablerepo=vdt-testing --nogpgcheck osg-client 

Then, go and do your normal workflows.  Create proxies, run globus-job-run's, start condor and run jobs.  Whatever, just test.  If you have any issues, email osg-software@opensciencegrid.org.  Or join me on the OSG jabber, osg@conference.indiana.edu.

All current bugs (I'm happy with how few there are) with the osg-client can be found on Jira.

Go forth and test...