| 1 |
Minutes of Meeting, 01/11/2000 @ 15:00 |
| 2 |
Location: UKC Computer Science Meeting Room |
| 3 |
|
| 4 |
Present: ab11, ajm4, pjm2, tdb1 |
| 5 |
|
| 6 |
It was decided that we should aim to start programming in |
| 7 |
the Project Week, which we believe is week 8. This gives us |
| 8 |
a week and a half to work out what we need to do before we |
| 9 |
can start the implementation, and do it. |
| 10 |
|
| 11 |
Discussion on UDP packets, and whether we really want to use |
| 12 |
it for host to server communication. Need to find out more |
| 13 |
about how Java implements UDP, and whether jc wants to take |
| 14 |
this route. |
| 15 |
|
| 16 |
ajm4 leaves after about 10 minutes, because he doesn't want |
| 17 |
to walk home.... |
| 18 |
|
| 19 |
It was decided that regardless of whether we used TCP or |
| 20 |
UDP, we would format the data sent between the host and the |
| 21 |
server in XML. |
| 22 |
|
| 23 |
This is a rough list of the things we think we'll be needing |
| 24 |
to monitor, although some will not come until at least after |
| 25 |
the first main release. |
| 26 |
|
| 27 |
Solaris |
| 28 |
- IP Address or Hostname |
| 29 |
- MAC Address |
| 30 |
- OS Name |
| 31 |
- OS Version |
| 32 |
|
| 33 |
- CPU(s) % Usage |
| 34 |
- Load (3 values) |
| 35 |
- Memory Total |
| 36 |
- Memory Free |
| 37 |
- Swap Total |
| 38 |
- Swap Free |
| 39 |
|
| 40 |
- Disk Space Total (per partition) |
| 41 |
- Disk Space Free (per partition) |
| 42 |
- Number of users |
| 43 |
|
| 44 |
- Open sockets (how many etc) |
| 45 |
- List "greedy processes" (ie. those that have consumed too |
| 46 |
many resources. |
| 47 |
|
| 48 |
Windows NT |
| 49 |
- IP Address or Hostname |
| 50 |
- MAC Address |
| 51 |
- OS Name |
| 52 |
- OS Version |
| 53 |
|
| 54 |
- CPU(s) % Usage |
| 55 |
- Memory Total |
| 56 |
- Memory Free |
| 57 |
|
| 58 |
- Disk Space Total (per partition) |
| 59 |
- Disk Space Free (per partition) |
| 60 |
|
| 61 |
- Shares in use |
| 62 |
- User connected to resources |
| 63 |
|
| 64 |
The discussion then side-tracked on to the host to server |
| 65 |
communication. It was discussed that having the server |
| 66 |
retain all configuration ifnromation would make management |
| 67 |
easier. The host would know about the "well known port" that |
| 68 |
the Filter Manager is runing on (maybe using /etc/services). |
| 69 |
Also, it could be possible to use a DNS CNAME (aka wpad!) to |
| 70 |
locate the machine that the server is running on. This would |
| 71 |
mean that the host has no configuration information sotred |
| 72 |
locally, at least initially anyway. The configuration would |
| 73 |
be sent from the server to the host during the initial TCP |
| 74 |
communications between the host and the Filter Manager (or |
| 75 |
maybe initial communication with it's assigned host). |
| 76 |
|
| 77 |
This is a very rough idea of the XML encoding we could use. |
| 78 |
It may not be 100% XML compliant, but that's not something |
| 79 |
we need to worry about right at the start. This first one |
| 80 |
was produced by pjm2. |
| 81 |
|
| 82 |
<?xml version="1.0" encoding="????????" ?> |
| 83 |
<data> |
| 84 |
<ip_address>###</ip_address> |
| 85 |
<mac_address>###</mac_address> |
| 86 |
<os_name>###</os_name> |
| 87 |
<os_ver>###</os_ver> |
| 88 |
<cpu>###</cpu> |
| 89 |
<load1>###</load1> |
| 90 |
<load5>###</load5> |
| 91 |
<load15>###</load15> |
| 92 |
<mem_total>###</mem_total> |
| 93 |
<mem_free>###</mem_free> |
| 94 |
<swap_total>###</swap_total> |
| 95 |
<swap_free>###</swap_free> |
| 96 |
<disk_total>###</disk_total> |
| 97 |
<disk_free>###</disk_free> |
| 98 |
<users>###</users> |
| 99 |
<open_sockets>###</open_sockets> |
| 100 |
<greedy>###</greedy> |
| 101 |
</data> |
| 102 |
|
| 103 |
tdb1 decided to put this forward, but doesn't have a clue |
| 104 |
about XML compliance... he just thinks it looks nicer. :) |
| 105 |
|
| 106 |
<?xml version="1.0" encoding="????????" ?> |
| 107 |
<data> |
| 108 |
<identity> |
| 109 |
<ip_address>###</ip_address> |
| 110 |
<mac_address>###</mac_address> |
| 111 |
<os_name>###</os_name> |
| 112 |
<os_ver>###</os_ver> |
| 113 |
</identity> |
| 114 |
<system> |
| 115 |
<cpu>###</cpu> |
| 116 |
<load> |
| 117 |
<1>###</1> |
| 118 |
<5>###</5> |
| 119 |
<15>###</15> |
| 120 |
</load> |
| 121 |
<mem_total>###</mem_total> |
| 122 |
<mem_free>###</mem_free> |
| 123 |
<swap_total>###</swap_total> |
| 124 |
<swap_free>###</swap_free> |
| 125 |
</system> |
| 126 |
<disk> |
| 127 |
<part> |
| 128 |
<name>###</name> |
| 129 |
<total>###</total> |
| 130 |
<free>###</free> |
| 131 |
</part> |
| 132 |
</disk> |
| 133 |
<procs> |
| 134 |
<users>###</users> |
| 135 |
<open_sockets>###</open_sockets> |
| 136 |
<greedy>###</greedy> |
| 137 |
</procs> |
| 138 |
</data> |
| 139 |
|
| 140 |
Things we need to do before we can commence implementation; |
| 141 |
|
| 142 |
- Investigate XML & Java |
| 143 |
- Find out about UDP, and how it works in Java |
| 144 |
- UML diagrams for the server and host |
| 145 |
|
| 146 |
Meeting was concluded @ 5pm. Next meeting arranged for |
| 147 |
Monday, in the meeting room. Someone needs to book it soon. |
| 148 |
|
