Database selection and design

[TheWall89]

Entities to store in the database:

• NFVO generic info
• NFVO credentials
• Catalogue subscriptions
• NSI subscriptions

Storing credentials SECURELY on client side is a hard problem to solve. Some refs:

• https://stackoverflow.com/questions/12937641/handling-passwords-used-for-auth-in-source-code
• https://stackoverflow.com/questions/4155187/securing-a-password-in-source-code
• https://stackoverflow.com/questions/1214582/ways-around-putting-a-password-in-code
• https://stackoverflow.com/questions/14570989/best-practice-for-storing-and-protecting-private-api-keys-in-applications
• https://stackoverflow.com/questions/28609526/store-client-secret-securely?noredirect=1&lq=1

[TheWall89]

About credentials: in WP3/WP4 we talked about having some key manager/vault to handle this authentication/authorization problems. Maybe we should not be too much concerned about this for now.

[TheWall89]

As the things to store are few and our software is basically a client, I would go with one of these two:

• SQLite (SQL, file-based): link
• Couchbase Lite (NoSQL-JSON, file-based): link

edit: Couchbase lite does not have a python library :(

[TheWall89]

First draft, relational:

[TheWall89]

This can be a candidate: https://pypi.org/project/tinydb/

It's document based and entirely written in python.

[TheWall89]

We select SQLlite. We start development after completing int-tests.