Great work Ajay!

Something you should keep in mind, since we are porting what we learned
in ansible-openwisp2 to docker, we should somewhat follow the path we
learned there and offer a similar feature set.

In your diagram, I see different boxes for PostgreSQL, I'm not sure if
that's good, could you expand on that? Are those different postgresql
server instances? How are they synced?
Is there a better way? Have you found some information about best practices
around this subject?

There's a diagram with nginx and django-freeradius, this doesn't seem to
make sense to me. OpenWISP Radius is based on django-freeradius and that's
our radius module, we won't run django-freeradius alone (you can consider
django-freeradius as a base library / django reusable app).

I see gunicorn being mentioned, I'm pretty happy with uWSGI and I would
like to continue using that as our application server.

Would be great to see the different containers/services being listed in the
diagram example:

   - OpenWISP Dashboard: admin + openwisp-users views
   - OpenWISP Controller (connections branch) views and APIs
   - OpenWISP Network Topology views and APIs
   - OpenWISP Radius views and APIs
   - websocket server of OpenWISP
   - celery worker
   - celery-beat
   - OpenVPN management VPN
   - freeradius instance

And do not forget to indicate the mounted volumes that allow to store
persistently files that are uploaded by users (eg: floor plan images).

Federico


On Sat, Mar 30, 2019 at 4:47 AM Ajay Tripathi <[email protected]> wrote:

> Hi,
>
> I made a small edit to the previous architecture[1].
> Instead to keeping many services in one pod, I've moved all the services
> to different pods because, say, If radius module is receiving a lot of
> requests, then
> we can simply scale the radius service without needing to create a new
> nginx server as well.
> The nginx in this case will send requests on ClusterIP service and
> kubernetes will do the load balancing and send the request to appropriate
> radius instance.
>
> In anycase, at the level of designing the docker containers, I don't think
> there will be any change. Here is the new diagram[2].
> Let me know if my line of thought is going in the correct direction or not.
>
> Thanks,
> Ajay
>
> ---
> Ref:
> [1]: https://i.ibb.co/Qp9HsZT/dock-hori-gsoc.png
> [2]: https://i.ibb.co/3FVpQd5/dock-horizontal2-gsoc.png
>
> --
> 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.

Reply via email to