Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce API based DAL #57

Open
JeffreyDevloo opened this issue Aug 16, 2017 · 2 comments
Open

Introduce API based DAL #57

JeffreyDevloo opened this issue Aug 16, 2017 · 2 comments

Comments

@JeffreyDevloo
Copy link
Contributor

Feature description

To keep the automation library completely standalone from the code of the framework, we should only rely on the ovs-extensions package (for logging, lightweight) and the api.
Currently a lot of helper calls are ugly wrappers around certain api tasks and all information is still being fetched from the DAL itself instead of the API

This will be the basis of QA 2.0

@wimpers
Copy link

wimpers commented Aug 23, 2017

@jake9050 could you investigate if all necessary api calls are available before starting with this way to go direction. Please use this ticket to list what is missing.

@JeffreyDevloo
Copy link
Contributor Author

All calls to support the current tests are sufficient for the improvement I was keen on.
The reason for this ticket is to have a 'model' which completely relies upon the api and work from that instead of calling 1001 helper functions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants