BIND 10 #2062: bind10-showtech initial version

[BIND 10 Development]

#2062: bind10-showtech initial version
-------------------------------------+-------------------------------------
                   Reporter:  shane  |                 Owner:  vorner
                       Type:  task   |                Status:  reviewing
                   Priority:         |             Milestone:
  medium                             |  Sprint-20120703
                  Component:         |            Resolution:
  Unclassified                       |             Sensitive:  0
                   Keywords:         |           Sub-Project:  Core
            Defect Severity:  N/A    |  Estimated Difficulty:  5
Feature Depending on Ticket:         |           Total Hours:  0
  bind10-showtech                    |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => vorner


Comment:

 Replying to [comment:13 vorner]:
 > > > While I agree it is good to have network information, routing info,
 list of open connections with process names and list of processes (as
 suggested on the wiki page), these information may be considered sensitive
 by some admins and they would not like to share them. Unless we provide
 some kind of switch, like `--no-sensitive`, it could lead to them not
 providing the output of `b10-showtech` at all.
 > >
 > > I agree with the idea, but it needs more discussion. If we cut out the
 entire data when `--no-sensitive` is specified, then the `b10-showtech`
 output won't be very useful as these are the data that support staff would
 want to see. We may want to filter or anonymize data. The format of the
 data varies from system to system, but this should not be problematic as
 it can be done in the implementations of `SysInfo`. I think we should
 create a separate ticket for it to be done after #2085.
 >
 > Would you start the discussion on the mailing list or should I?

 Please do so. I need to sort out my ISC email sending before posting there
 (my emails get flagged for admin approval).

 > > > Should the generated man page be in git?
 > >
 > > This follows the convention of all other bin programs whose manpages
 are also checked in.
 >
 > Right, maybe I don't complain loud enough about the other programs too
 O:-).

 Hehe.. agreed that these should not be in the repo. Every time I build
 with `--enable-man`, the tool versions get into the generated manpages and
 `git status` reports diffs. No idea why these are in the repo, as they can
 be dist'd instead.

 > I don't agree here. There's quite some processing (like a bunch of
 regular expressions for the memory information). These really need to be
 tested. We don't need to test if the system functions are called, we just
 need to fake them so they return some known value. Note that python is
 cool and it is easy to do so, like this:
 >
 > {{{#!python
 > def fake(param):
 >       return 42
 >
 > tested_module.sys.function = fake
 > }}}
 >
 > The fact that the test is implementation-specific is a drawback, but not
 a really big problem. When I tried to argue we should test the interface
 only and never touch the internals, I was told this is not true at least
 for us.

 In the pursuit of moving the bug along, I've closed my eyes and checked in
 such tests. :) (But it was weird writing them.)

-- 
Ticket URL: <http://bind10.isc.org/ticket/2062#comment:14>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development