The OOF-OSDF is provides the following functionality to support OOF-HAS:

1. Provide an end point for SO to make homing requests
2. Ensure authentication and validate the incoming request payload based on a model (Python Schematics model based on the SO-OOF API)
3. Fetch policies relevant to the SO's request (e.g. based on specific use case such as vCPE) and ensure that the policies are valid (well formed and contain required attributes)
4. Send response to SO that the request is accepted and is in processing (or send an error response)
5. Create a "template" (request payload) for OOF-HAS and submit the request to OOF-HAS
6. Periodically poll OOF-HAS for request processing status and optimization solution (with a configurable timeout) and validate the response based on a model (Python Schematics model)
7. Post the optimization solution in the format defined by SO-OOF API (or send an error response)

The following abbreviations are used in the functional test case description below since there is substantial repetition and notes associated with some terms.

1. HTTP-200-TRUE

   1. Component (or all components) should return health status