Hi, On Tuesday, March 26, 2019 at 9:55:42 PM UTC+5:30, Federico Capoano wrote: > > A demo on Kubernetes and using some kind of tool that makes it easy to > provision (Marco Giuntini suggested https://github.com/ansible/awx, if > you know something equivalent you could suggest) would be a big win. >
I am getting started with Kubernetes with kubeadm (very close to deploying a sample.). :) However, docker swarm has been really convinent and fast to implement our stack, while kubernetes is taking more resources to get started. (Didn't even work on my laptop, I had to move to a different machine!) So, That got be thinking about the advantages of using kubernetes in our usecase but the best I could find was that kubernetes is a more "production-ready" solution. So, Can you please point me to read about the advantages of using kubernetes in our development setup, thanks! > Helping out in writing tests (using some sort of mock SSH server) for > https://github.com/openwisp/openwisp-controller/pull/31 is also a big > plus, because if the students really understand the code of that branch it > will have an easier time to understand how to deploy it, I have some > automated test samples that I can show if needed. > Sure, I'll start with it ASAP, thank you. The samples will be very helpful. :) On Wednesday, March 27, 2019 at 1:58:06 AM UTC+5:30, 2stacks wrote: > > That's what made me think to mention Terraform. You can still leverage > your ansible playbooks for configuration and use Terraform's Kubernetes > integration to handle the infrastructure complexity. Of course this is all > easier said than done. I've done something sort of similar with Terraform > and docker-compose on different cloud providers but haven't made the jump > to Kubernetes yet. A simple non-scaling example is here; > > https://github.com/2stacks/terraform-openvpn > I'll checkout Terraform ASAP. Many thanks, Samples really help save time when learning new things. :) I have small question from the project list: - Provide the OpenWISP Admin interface and the views managing account information (password reset, email confirmation) in a dedicated container. What all is constituted in the "OpenWISP Admin interface"? On Wednesday, March 27, 2019 at 1:14:31 AM UTC+5:30, Federico Capoano wrote: > > - we can manage most configurations of the services in some textual format > - we can manage the django settings easily for a single installation (in > which different containers may have mostly identical django settings with > some minor differences, django has a way to specify default settings, we > could use that low level feature for example) > - we can store all these configs under git in private repos > Okay, the good news is that I finally understand the problem with a better prespective now. :) Ajay -- 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.
