nathans wrote:
> [...]
> 3. Lastly we discussed where the SNMP PMDA was up to, with a
> specific focus on the concept of transparent proxying to make
> both client tool experience and PMDA implementation a little
> more sane.
> [...]
> - Strawman put forward: pass hostname used in pmNewContext
> along with credentials PDU to pmcd, which can then make it
> available to PMDAs as well (this would piggyback onto any
> security extensions, likely to pass username, keys, etc on
> to PMCD/PMDAs - pcp4 stuff) so that the PMDA can use host
> name that individual clients are interested in to tailor
> the namespace and values made visible, per connection.
Sounds like the HTTP Host: header; piggybacking with User/Password
etc. sounds natural.
> DNS CNAMEs or other multiple name/address alias convention
> can then be used to allow PMDAs transparently (to clients)
> to tailor exported information.
Plus SRV entries to map to separate pmcd port numbers or whatnot if
multiple distinct servers are needed.
> [...]
> - Mark very keen on the idea that we go further and make
> libpcp able to switch protocols, directly, in the client
> tools. [...]
> Some further discussion around a URL-like syntax for host,
> protocol and port specification (pcp://hostname:port, and
> snmp://hostname:port). [...]
(It may be possible to rely on zeroconf and/or SRV to map a plain
hostname to port #161 (snmp), and let the pmapi client library adapt
based upon that.)
- FChE
|