1. I'm pretty sure they need to share user table information but I'll defer to Federico. Do you know the exact issue?
2. I've been researching this lately as it pertains to running django-admin on a seperate instance (container). Its recommended best practices that migrations only be run from one container when multiple containers share a code base or models. 3. I use a combination of shell scripts and docker entry points. Check out https://github.com/eficode/wait-for and https://github.com/2stacks/freeradius-django/blob/master/compose/django/entrypoint. It's also possible in Terraform to create things with implicit dependencies. I haven't tried with Kubernetes but I'm sure it can be done https://learn.hashicorp.com/terraform/getting-started/dependencies.html. Hope this helps. On Sat, Apr 6, 2019, 8:30 AM Ajay Tripathi <[email protected]> wrote: > Hi, > > *Update:* I've added documentation for testing and building the > containers.. > > *Questions/Discussion:* > 1. About Database: > It looks like openwisp-radius and openwisp-controller can't migrate to the > same database. > Unlike the network-topology module which migrated to the same database as > the openwisp-controller, > I had to change the database name for the radius module. > Is this an expected behaviour or do we need to make openwisp-controller > database compatible with > the openwisp-radius database in the final version? > > 2. Migration problem with docker-compose: > When we run docker-compose for the first time. All the containers start > migrating parallelly which causes some containers > to fail in migrating. If we re-run the containers everything works fine > because the rest of the containers get a chance to migrate, > I think we need some kind of flag for the containers to communicate about > migrations in the first run. Please suggest on the same. > > 3. Terraform creating order: > When the database server starts, it takes a while to allow connections on > port 5432. > But since terraform starts all the pods parallelly, some pods that try to > connect before postgresql is ready > and the pods fail, re-running the pods solve the problem but I could not > find how I can communicate to > terraform to let it know that database server is accepting connections and > dependand pods can be > created. Please advice how is it usually done. :) > > Thanks, > Ajay Tripathi > > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
