Plans for the coming month or two
Having been off for most of the week with a stinking head-cold has let me take a step back and figure out what I need to be doing over the next six weeks:
- RT updates: need to polish these and get back on track. This is prompted by the LTSS/ESU requirement. Time to do a first pass and get the RT installations under build-script control. I’d also like to sort out “scratch” targets that can potentially consume the production databases; and getting sufficient rights that I can clone a production DB to development, whilst I’m at it.
- NFS service: this has been hanging around now for some time. At least get a first pass put to bed, with Graham and Nick on board. I’ve needed a solid file service to underpin the application server work for a while now - that’s been somewhat stymied by management refusal to admit there was something wrong with the current NFS servers. At least everyone’s on board now. I’m reminded of the RDF Core work - spent a long time writing the infrastructural bits that were required in order to actually write applications.
- One the NFS work is done, I need to seriously revisit the appinf farm work: Adam wants a separate DB instance to build spam machines off the back of. I’d rather have the MBS backed by solid NFS rather than have it directly SAN-attached, if possible. It’ll also give me the opportunity to pick off some of the cleanup work and produce service-layer scripts for some of the other use cases. Whilst I’m at it, I’d like to revisit the Apache front-end setup: perhaps taking advantage of our new, improved cygnus.
- Finally, I’m going to chase the zoned NFS project at OpenSolaris, see if I can’t help out there. The code looks well-structured and reasonably well-baked. NFS4 complicates matters a bit but not to an extreme.
- There’s all the background noise that’ll also be going on: the LDAP and Grouper work. Again, this is stuff that we desparately need but nobody has really been doing.