News for hackers. Stuff that matters.
Re:Scalable and resilient Django with Kubernetes by danpalmer on Saturday April 02, 2016 @02:08PM (#11412533)
As someone who does pretty much this for my personal sites, and has a level slightly above at work, I can say anecdotally that your caveat is important. The way you describe works well for me on personal projects, but at work we're really starting to see the benefit of the automation and reproducibility that things like Docker and Kubernetes provide. Ansible is great, but it's still easy to end up with non-reproducible environments, and that's something we've been bitten by quite a few times.
Re:Scalable and resilient Django with Kubernetes by clebio on Saturday April 02, 2016 @02:15PM (#11412565)
Can you expand a bit on how you still end up with non-reproducible environments? Not that I doubt it! Just would like to here some details, or a specific example.
Re:Scalable and resilient Django with Kubernetes by luos on Saturday April 02, 2016 @02:31PM (#11412650)
Usually when you ssh into the machine to fix something broken then forget to backport the changes to the ansible script.
Re:Scalable and resilient Django with Kubernetes by merb on Saturday April 02, 2016 @03:00PM (#11412791)
The same thing could happen with docker, too.
Re:Scalable and resilient Django with Kubernetes by vetinari on Saturday April 02, 2016 @05:43PM (#11413620)
You usually can't ssh into docker container because:

1) it usually doesn't have sshd

2) you change would be thrown away at nearest container restart or migration.

The only way for it to persist is to do the right thing, i.e. apply the change where you should and have the container rebuilt.

Re:Scalable and resilient Django with Kubernetes by merb on Sunday April 03, 2016 @03:00AM (#11415230)
You don't need ssh to get into a docker container.
Re:Scalable and resilient Django with Kubernetes by danpalmer on Sunday April 03, 2016 @12:49PM (#11416719)
Definitely what luos said, but also you typically run repeatedly against the same machines, with changes on each run. This can lead to having a different environment depending on whether you ran once or multiple times. Conversely with Docker, you're essentially recreating from scratch every time you build the image, with some caching to make it fast though.
Re:Scalable and resilient Django with Kubernetes by TheIronYuppie on Sunday April 03, 2016 @03:20PM (#11417233)
How about just when your current machine (e.g. Mac) has a different supported version of Python?

Disclosure: I work at Google on Kubernetes.

Re:Scalable and resilient Django with Kubernetes by metafunctor on Wednesday April 13, 2016 @05:25PM (#11492345)
Umm, you install the version of tools and libraries you've standardized on, and check them in your unit tests?