...

• add() provides a netid, nodename, other arguments to create a node
• delete() provide a nodename, tell NetBill to delete the record
• getBilling() provide a netid, receive whether or not PTAEO required
• getNodesetgetNodeList() provide a netid, receive a list of nodes containing zero or more nodename(s) that are associated with that netid (we could collapse the two get methods down to a single query method that returns billing status and nodeset). Whichever seems more sensible for Rod.
• getNodeDetails() provide a nodename, receive the details for that nodename
• update() provide a nodename, provide arguments to change on the node

add()

Arguments for add:
netid of owner
nodename (needs to be unique, and NOT exist already in the system)
client category (DS,MW,WS)
Client OS (Windows, Mac, Unix)
interval (backup time, or never)
PTAEO, passed as six separate strings

...

whether a PTAEO is required

...

getNodeList()

Arguments for getNodesetgetNodeList:
netid of owner

getNodeset getNodeList method needs to return an error code indicating whether or not the getNodeset request was accepted. If no error, also needs to return:

• a count of nodes. zero or more.
• a comma-delimited list, containing zero or more nodenames
  each node containsnodename is received in a single string, comma separated, no spaces

Sample nodename strings

• "tanner,cooper,radar"
• "" (empty set)
• "zuse"

getNodeDetails()

Arguments for getNodeDetails:
nodename of node

getNodeDetails method needs to return an error code indicating whether or not the getNodeDetails request was accepted. If no error, also needs to return:

• returns:
  nodename (needs to be unique, and NOT exist already in the system)
  client category (DS,MW,WS)
  Client OS (Windows, Mac, Unix)
  interval (backup time, or never)
  PTAEO, passed as six separate strings

...