Pulp

I know i'm not really involved in pulp's day to day anymore, but I may have some info relevant here:

When I was involved in the data modeling effort, great care was taken to write the models in a manner that would hopefully allow any of the supported django orm database providers to be used with the app in the environment users chose. If this same care has been used since, it hopefully shouldn't be to hard to just allow other django orm providers to act as the backing database.

I will say caution should probably be used though in determining which databases are supported in a production environment. Databases are fickle creatures, and each behaves differently under stress situations. For this particular issue, this link may be of help in determining the support level of sqlite databases.

https://www.sqlite.org/whentouse.html

Sqlite3 is a fine DB for users who want to try pulp and for plugin development environments. pcreech made some good points and linked a good guide for users to make the proper DB choice. The issue as written describes what users want but needs clarity regarding the specific changes being proposed and what the deliverables are. +1 moving forward on this.

Thanks for all the responses. To clarify the details of the change, I made this example PR here: https://github.com/pulp/pulp/pull/3344/files

The right db for a production install is an important choice. Users in production environments need to think about what is the right database for them. Django supports 4 databases directly and 5 more through 3rd party support. https://docs.djangoproject.com/en/1.11/ref/databases/

I expect that the Ansible installer will allow a user to choose between sqlite and postgresql in terms of what it can configure. The defaults for the Ansible roles for Pulp is also something we should figure out, but that is a separate discussion specifically for the installer.