Changes between Version 1 and Version 2 of WeeklyMinutes20091203


Ignore:
Timestamp:
Dec 8, 2009, 4:47:59 PM (8 years ago)
Author:
shane
Comment:

Fix line length

Legend:

Unmodified
Added
Removed
Modified
  • WeeklyMinutes20091203

    v1 v2  
    2121On Thu, 2009-12-03 at 15:12 +0100, Shane Kerr wrote:
    2222Jeremy spent some time thinking about the agenda for today's call, and
    23 > listed some possibilities in the Jabber room.
    24 >
     23listed some possibilities in the Jabber room.
     24
    2525>       * Roll call
    2626>       * Status checkpointing:
    2727>               * DNS message API
    28 >
     28
    2929Checked in with new style.
    3030Completing name class with this style.
    3131
    32 Shane: so when this style is done then it will be ready for review and end-user use?
     32Shane: so when this style is done then it will be ready for review and
     33end-user use?
    3334Jinmei: open question - how this will be done
    34 Shane: ISC way is that someone else on the team reviews... review each part or entire package?
    35 Jinmei: have name class reviewed when completed, and then each class as it is done... otherwise reviewed part is very large
    36 Shane: don't want review to go to list and sit without knowing who is responsible... contact me and we'll figure out who is the best person
     35Shane: ISC way is that someone else on the team reviews... review each
     36part or entire package?
     37Jinmei: have name class reviewed when completed, and then each class
     38as it is done... otherwise reviewed part is very large
     39Shane: don't want review to go to list and sit without knowing who is
     40responsible... contact me and we'll figure out who is the best person
    3741Jinmei: any tools...?
    3842Shane: ticket system from Trac site should be good enough
     
    4246              * c-channel
    4347>
    44 Michael: re-wrote msgq in Python... slow in comparison to C version (about 1/25 the speed)... implements all the features we need it. Minor change to way messages are delivered... messages addressed to person are always delivered.
     48Michael: re-wrote msgq in Python... slow in comparison to C version
     49(about 1/25 the speed)... implements all the features we need it.
     50Minor change to way messages are delivered... messages addressed to
     51person are always delivered.
    4552Jelte: new wire format?
    4653Michael: message now encoded separately - not in header
     
    4855Michael: no change to API!
    4956
    50 Shane: language issues, how widely accepted?, think we should use the msgq stuff for now, and maybe change later...
     57Shane: language issues, how widely accepted?, think we should use the
     58msgq stuff for now, and maybe change later...
    5159Michael: tend to agree
    5260
     
    5462Michael: cooked
    5563Shane: ready for review, then move into main trunk?
    56 Michael: code is kind of wacky... some changes would like to make... maybe note those and submit for review... some unit tests!
     64Michael: code is kind of wacky... some changes would like to make...
     65maybe note those and submit for review... some unit tests!
    5766Shane: try to wrap it up...
    5867Michael: will add TODO... then ready for review
     
    6372
    6473              * Configuration
    65 >
    66 Jelte: committed a few things today, invading on BigTool territory, so using own branch for now.
     74
     75Jelte: committed a few things today, invading on BigTool territory, so
     76using own branch for now.
    67771. positional arguments, rather than named arguments
    68782. bigtool can edit configuration as defined by configuration file
     
    7181Can then merge into parking lot, then ready for review.
    7282
    73 Lots of open issues... in BigTool can add value to a list, but no wire protocol for that, not sure if I should make it.
     83Lots of open issues... in BigTool can add value to a list, but no wire
     84protocol for that, not sure if I should make it.
    7485
    7586Shane: note them, then move on!
    76 Jelte: expect to be finished & merged next week, but all hands will reduce productivity
     87Jelte: expect to be finished & merged next week, but all hands will
     88reduce productivity
    7789
    7890              * BigTool
    79 >
    80 Likun: 2 points... almost finished code about login to Command & Control module... want to commit next week... prefer to use XML-RPC to communicate between BigTool and C&C module. REST is probably not usable... too complex. Need to install some HTTP server on command module. For first version prefer to use XML-RPC.
    81 
    82 Michael: NO! Please don't!!! XML-RPC is okay, but would rather not complicate things with an RPC layer. Would rather see a simple HTTP server than use REST if we can avoid it.
    83 
    84 Likun: Only message is for the command. So I think it is not very difficult if we have new commands to support.
    85 
    86 Jelte: Maybe we have different ideas about what these things were going to do.
     91
     92Likun: 2 points... almost finished code about login to Command &
     93Control module... want to commit next week... prefer to use XML-RPC to
     94communicate between BigTool and C&C module. REST is probably not
     95usable... too complex. Need to install some HTTP server on command
     96module. For first version prefer to use XML-RPC.
     97
     98Michael: NO! Please don't!!! XML-RPC is okay, but would rather not
     99complicate things with an RPC layer. Would rather see a simple HTTP
     100server than use REST if we can avoid it.
     101
     102Likun: Only message is for the command. So I think it is not very
     103difficult if we have new commands to support.
     104
     105Jelte: Maybe we have different ideas about what these things were
     106going to do.
    87107Michael: I thought we were just going to use the msgq library...
    88108Shane: no, not in this way...
     
    90110Michael: REST-ful interface has a certain feel to it.
    91111
    92 AP: Michael to mail link with PDF for the DLV web site, which uses REST-ful interface. Wikipedia is probably best to start with.
     112AP: Michael to mail link with PDF for the DLV web site, which uses
     113REST-ful interface. Wikipedia is probably best to start with.
    93114
    94115Michael: Must be a simple way to do this
     
    105126Kambe: investigating PySNMP library
    106127
    107 Jeremy: I was just curious, didn't look at code in there, was wondering how it will tell other components what it will receive. Do we have this listed out? Is it using the command channel? I assume it is. How we are going to keep track of this and how we are going to share it. Maybe we need to start a wiki page?
     128Jeremy: I was just curious, didn't look at code in there, was
     129wondering how it will tell other components what it will receive. Do
     130we have this listed out? Is it using the command channel? I assume it
     131is. How we are going to keep track of this and how we are going to
     132share it. Maybe we need to start a wiki page?
    108133Shane: None worked out.
    109134Jeremy: Assume all things will have statistics.
    110 Michael: Everything has something that it does. Even the stats server has stats.
     135Michael: Everything has something that it does. Even the stats server
     136has stats.
    111137
    112138AP: Jeremy to add page to Wiki about this.
     
    118144>
    119145Shane: TODO file created.
    120 Jelte: Please commit the TODO file, there may be other things to add to it.
     146Jelte: Please commit the TODO file, there may be other things to add
     147to it.
    121148
    122149* Progress, dependencies, time estimates:
     
    125152Jeremy: What is our actual progress. Can we discuss that?
    126153
    127 Shane: main items are: 1) data source, 2) everything else... ISC coders looking at data source now, Evan and these will look at "everything else" ASAP... schedule not (yet) in jeopardy
     154Shane: main items are: 1) data source, 2) everything else... ISC
     155coders looking at data source now, Evan and these will look at
     156"everything else" ASAP... schedule not (yet) in jeopardy
    128157
    129158Jinmei: possible to convert timeline to graphical output?
     
    135164
    136165      * First public deliverable
    137 >
    138 Jeremy: AS112 server. Wiki page called "first release" which lists the components for that.
    139 Jeremy: please look at this, then timelines, then we need some other things done... for example, parking lot used wrong API for efficiency in speed, some developers to look into that part
    140 Jelte: on most levels as far as we can take the whole system without having the data source... does need quite a bit of work on some fronts, I agree
     166
     167Jeremy: AS112 server. Wiki page called "first release" which lists the
     168components for that.
     169Jeremy: please look at this, then timelines, then we need some other
     170things done... for example, parking lot used wrong API for efficiency
     171in speed, some developers to look into that part
     172Jelte: on most levels as far as we can take the whole system without
     173having the data source... does need quite a bit of work on some
     174fronts, I agree
    141175Shane: should we go over this face-to-face next week? Good use of time?
    142176
    143 Jeremy: can create documentation for operator to install and turn on... should be short & sweet since this is simple! I could also edit the parking lot so it provides the zones we want to serve... should be easy since that is just NS records.
    144 Michael: AS112 document hasn't been changed since May 2003 and recommends using BIND 8!
    145 
    146 Hankins: folks who observe AS112 in the wild think it is an attack... so if there is anything untoward in this server's output it might make people's jobs hard if they have weird output
     177Jeremy: can create documentation for operator to install and turn
     178on... should be short & sweet since this is simple! I could also edit
     179the parking lot so it provides the zones we want to serve... should be
     180easy since that is just NS records.
     181Michael: AS112 document hasn't been changed since May 2003 and
     182recommends using BIND 8!
     183
     184Hankins: folks who observe AS112 in the wild think it is an attack...
     185so if there is anything untoward in this server's output it might make
     186people's jobs hard if they have weird output
    147187Michael: would be nice to have a packet capture of AS112 traffic
    148188Shane: Do you know if we have a separate server for this?
     
    155195
    156196      * Official name of BigTool
    157 >
     197
    158198Jeremy: I didn't know that was the real name...
    159199Michael: it's the working name...
     
    163203Jelte: don't care...
    164204Michael: don't care... could even be bind-ctrl
    165 Jinmei: bind-control is more clear, but my general impression is that "BIND control" sounds like just a command line tool rather than an interactive session. Is that only me?
     205Jinmei: bind-control is more clear, but my general impression is that
     206"BIND control" sounds like just a command line tool rather than an
     207interactive session. Is that only me?
    166208Michael: I think it would be both.
    167209
    168 Hankins: Are you talking the command line invocation name? Needs to be very nice and short. "rndc" and "nsdc" are both good examples.
     210Hankins: Are you talking the command line invocation name? Needs to be
     211very nice and short. "rndc" and "nsdc" are both good examples.
    169212Michael: bindctl
    170213Hankins: a little wordy... prefer bctl
     
    176219
    177220      * "user" installation/usage documentation
    178 >
    179 Jeremy: In Docbook format for each component, was going to provide a description of usage, and then provide some shell scripts to render those into man and HTML.
    180 
    181 Michael: needs to be simple for first release, prefer install guide and a "detailed" install guide (if necessary)
     221
     222Jeremy: In Docbook format for each component, was going to provide a
     223description of usage, and then provide some shell scripts to render
     224those into man and HTML.
     225
     226Michael: needs to be simple for first release, prefer install guide
     227and a "detailed" install guide (if necessary)
    182228
    183229* data source
     
    186232
    187233      * Next week's call
    188 >
     234
    189235AP: Shane to propose a new time for the call.
    190236
    191237* AOB
    192 >
    193 Hankins: time to get thoughts together about DHCP, will write rough draft about what the problems are, then we can talk about solutions
     238
     239Hankins: time to get thoughts together about DHCP, will write rough
     240draft about what the problems are, then we can talk about solutions
    194241
    195242Shane: bye... will see most of you next week!