perfsonar-dev - [SSHTELNET MP] design flaw fixed for 3.1
Subject: perfsonar development work
List archive
- From: Stijn Melis <>
- To: "" <>, Michael Michalis <>, Panagiotis Prokopiou <>,
- Cc: Nicolas Simar <>, , Loukik Kudarimoti <>
- Subject: [SSHTELNET MP] design flaw fixed for 3.1
- Date: Thu, 12 Jun 2008 16:49:40 +0200
Hi all,
I fixed the design flaw for the SSHTELNET MP. All respective commands for both cisco and juniper now expect the same parameters (i.e. if a cisco command expects an ip address, then so does the equivalent juniper command).
I had to change some JAVA code for this, but mostly it's just the list of commands which has slightly changed.
Nothing has changed to the structure of the XML messages: the SetupDataRequest/Response, the MetadataKeyRequest/Response and the metadata configuration file are all still the same in regard to the elements. The only thing that changed is that some commands now expect a different parameter.
I will now list the commands, and what has changed:
Cisco:
IP_BGP_NEIGHBOUR_ADVERTISED: no longer needs "advertised-routes" as a parameter
IP_BGP_NEIGHBOUR_RECEIVED: no longer needs "received-routes" as a parameter
IP_OSPF_DB_EXT: no longer has a parameter
IPv6_BGP_TABLE: changed from <IPv6 prefix> [<length>] to <IPv6 prefix/length>
IPv6_BGP_NEIGHBOUR_ADVERTISED: no longer needs "advertised-routes" as a parameter
IPv6_BGP_NEIGHBOUR_RECEIVED: no longer needs "received-routes" as a parameter
IPv6_MULTICAST_ROUTE: no longer has a parameter
Juniper:
IP_INTERFACE: no longer needs "extensive" as a parameter
IP_ROUTE: changed from <prefix> /[<length>] to <ip adddress>
IP_MULTICAST_SDP_PEER: no longer needs "detail" as a parameter
IPv6_ROUTE: added <IPv6 address> as a parameter
IPv6_MULTICAST_BGP_TABLE: changed from <IPv6 prefix> [<prefix-length>] to <IPv6 prefix/length>
IPv6_INTERFACE: no longer needs "extensive" as a parameter
IPv6_MULTICAST_ROUTE: no longer has a parameter
IPv6_MULTICAST_RPF: changed <IPv6 prefix> [<prefix-length>] to <IPv6 prefix>
I also updated the list of commands on the SVN (in the doc/commands directory), as well as the configuration files for the configuration scripts.
I don't think the documentation (Functional, Interface and Metadata Configuration specification documents) has to be changed, because neither the schema, nor the functionality has changed. If anybody feels otherwise, feel free to let me know what has to be changed..
For the testing scripts: I don't think a lot has to be changed either. If you use one of the commands I mentioned above, you will have to changed the parameters, but nothing else.
I won't yet make a new release for this, because some other stuff for 3.1 still has to be implemented.
Best regards,
Stijn
- [SSHTELNET MP] design flaw fixed for 3.1, Stijn Melis, 06/12/2008
Archive powered by MHonArc 2.6.16.