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

Playbooks should have a clear distinction between application and platform #544

Closed
adborden opened this issue Dec 14, 2018 · 2 comments
Closed

Comments

@adborden
Copy link
Contributor

Our playbooks currently deploy all the components of data.gov and each component is very customized. If we consider the playbooks to be more about setting up a platform, then the playbooks can be simplified. This means moving the application setup logic into the applications themselves.

This moves us much closer to a platform based deployment that fits with docker or kubernetes. It simplifies playbooks, because it's more about providing services to be consumed by applications rather than having to know how to configure applications.

Examples of responsibilities that should be in the application:

  • Solr collection creation and configuration should be handled by the app (e.g. catalog-app, inventory-app)
  • Database migrations should be done by the application (e.g. catalog-app, dashboard-web, crm-web)
  • Installing dependencies (e.g. catalog-app, dashboard-web)

Examples of responsibilities that should be in the platform:

  • Provisioning nginx, and providing the application which socket or port to listen on
  • Provisioning Solr and providing connection information to the application
  • Securing the environment and ensuring file permissions are set appropriately
  • Providing a directories or paths to where applications should install themselves
@adborden
Copy link
Contributor Author

This is still somewhat squishy, but wanted to start writing some things down. This is related to our conversation yesterday @jbrown-xentity. Let me know if it makes sense.

@nickumia-reisys
Copy link
Contributor

Superseded by new Solr Deployment,

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

No branches or pull requests

3 participants