Next Hop

Goals

Next generation of parent and origin selection

#	Title	User Story	Importance	Notes
1	Parent health status	As of now Parent Status (UP/DOWN) is updated internally when a request to a parent results in a connection failure. ATS should be able to examine & modify the status of Parent using a plugin interface & external mgmt interface.		Use hostdb as the source of health status NextHop API: 1) TSNextHopListGet() 2) TSNextHopListSet() 3) TSNextHopHealthCheckGet() 4) TSNextHopHealthCheckSet() 5) TSNextHopStatusGet() 6) TSNextHopStatusSet()
2	Health check plugin	Once we have the ability to update the parent status, there should be an example plugin to check the health of next hop and update the status.	Must Have	List_continuation: 1. Periodically get the list of nexthops that needs to be health checked using GetNextHopList() 2.for a new nexthop or manually marked up nexthop, create a continuation and call tsnetconnect 3. delete the continuation for currently, health checked Next Hop if does not appear in the current list or if it manually marked down. health_check_continuation: 4. if the connection fails, call SetNextHopStatus()
3	External health check process	External process for health checking and updating the status of the Next Hop	Must Have	Requires management API to update hostb health record status (WIP).
4	Self detection	Ability to detect the request that is going to end up on the same server and direct the request to next server.	Must have	Issue 2269, update parent selection findParent()

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome