Subject: [TOOLS-DEVELOPMENT] Tools Call: 19 Jan 2011

From: Steve Conte <[email-masked]>
Date: Wed, 19 Jan 2011 08:51:27 -0800

Hi all.. standard disclaimers apply.. all errors are my own, please correct if necessary.

-----

IETF Tools Call - 19 Jan 2011

Attendees:

Ray Pelletier
Bob Hinden
Henrik Levkowetz
Robert Sparks
Ron Bonica
Glenn Barney
Karen Moreland
Alice Hagens
Russ Housley
Matt Larson?

Agenda:

1.  xml2rfc sow

RH: Sent out draft v04 which received one comment.  Waiting for other comments, but 
nothing else.  Has anyone on the call had a chance to look at new one?
AH: Yes, read and discussing comments with Sandy to pass along shortly.  Nothing major.  
RjS: hasn't read current version but doesn't anticipate any new changes
RH: Will be introduced to IAOC call 20 Jan 
AH: Comments about maintainer to make release to web converter.  No mention about 
experimental.
RH: Reason is received a lot of pushback about the tool being different than website
and website is not part of this sow.
AH: Pointing out that the current version is disconnected from web converter and 
is important to make sure that new application doesn't stray versions.

2.  DB Conversion - next steps

RP: IOLA working on it, at least 2-3 work orders which should take us into Feb-Mar 
timeframe, so will be very close to Prague.  Will some webex sessions be valuable
prior to Prague?
HL: Who'll be attendees?
RP: Agenda to go over changes that are occuring so people can see what's happening
to structure
HL: Structure has no real bearing on new schema.  To do some kind of tutorial would
probably make it much more attractive for people to participate and write code.  To 
do it in one session
RP: Subcommittee to determine how/where to do this.  Sounds like it would not be helpful
to do this in Prague

HL: IOLA is progressing well and is happy with progress 

3.  Prague Code Sprint - 64 days

SC to secure space for sprint.  Term room and space for F&B
RjS: a bit early for sprint agenda but will use the standard pattern from 
past sprints
RP: will "regular" crew be there?  RjS: Yes, will start asking who'll attend to 
get a better idea of who'll be there 
RP: Overview to database conversion while there?
HL: Yes, but wondering if it's the right place to do it.  Will require a fair 
amount of time and will impact the time to do active coding.  Better to be able
to do it at a separate session, provided people will attend and if IESG feels it's 
worthwhile 
RP: What kind of time will be needed
HL: 2 hours is optimal.  Should invite IOLA to talk
RjS: Do we anticipate people to code to new schema.  If yes, then Prague is too 
late and should do it prior to Prague
HL building wiki signup pages

4.  Asia Server

HL: Anthony has been working on setting up everything, only thing pending is some testing.
Should be online within a week or so.

5.  Failover Test

RP: Looking for opportunity/time to perform failover test.  
RH: Sometime April?
GB: IETF is running on 2 different server locations, 3 different servers. Pri/Backup
in Fremont.  Also in Orlando, FL USA.  Sync takes place for database, rsync run 
continuously between servers.  Takes about 2 hours to sync to Orlando.

RH: If computer fails in Fremont, then switch is Primary to Backup, but last failure
was the connection of Fremont to the Internet.
BH: Last failure was "soft" , ie performance failure more than service failure

GB: If there's a failure of primary, then DNS records would change to point to backup 
servers.  Process is pretty clean.  Failover process can be done quickly. But if 
that is done, then any data that is not yet sync'd to FLA server would be lost.  Suggested
failover test would be to bring the Fremont server down to do a graceful shut to 
sync remaining data.

Would need to bring IETF down for approx 2 hours to do clean failover for each direction.
Return trip may take longer to ensure accuracy and integrity.

Need to schedule a time that is both convienent and where physical bodies in both location

Current OS is 3-4 years old.  Working on upgrading servers to newer OS versions.  Backup
servers are already running on new OS

current: OpenSuSe 10.3
moving to: 11.1
Python 2.5 -> 2.6
updating mailman

Would like to invite key people to help test against the backup servers prior to 
failover test.

Would like the backup in FLA to be primary for at least 2 weeks.

RH: would like to see at least one IESG telechat to run on one of the backup machines.

GB: Would need some IPv6 tunnels for FLA.

RjS: Would there be a way to provide a way to notify Datatracker users that they would
be working on a backup server and that data has the *potential* of loss.  Thinking more
on this.

6.  IT Update

RP: Datatracker projects (8), Secretariat Projects (11), Community Projects (3)
and RFC Projects (3).  Ray has a page that shows estimated times of completion.
AH: What is RFC Management?
KM: Coldfusion tool replaced by Django
GB: IETF tool that RFC doesn't use.  Allows Secretariat to mirror RFC data
AH: Could have impact for dataexchange between RFC Ed and Secretariat?
GB: This is after the RFC Ed actions
RjS: Is all coldfusion being replaced?
GB: Yes
RjS: Is it only Secretariat facing or is some of it community facing?
GB: Secretariat facing only
RjS: One of the things that the tools does is the assignment of documents to WGs.  This
would be nice to introduce to some of the community tools
GB: Interested in introducing some of the Sec tools to the appropriate groups

6.  Other

Hardware needs: HL: One of the production servers is too weak/slow and needs to order a
new server.

-----
Steve Conte
[email-masked]