6 ms·
I like this a lot, and I love the term DebOps. The way developers somehow think DevOps is (or should be) an abbreviation of "Developers doing/replacing Operati
by stephenr 11y ago
I like this a lot, and I love the term DebOps.
The way developers somehow think DevOps is (or should be) an abbreviation of "Developers doing/replacing Operations" is terrifying to me.
I'm also in the same boat as the author, in that I recommend and target Debian Stable + Backports (and some vendor/community repos when required).
- quanticle 11y agoThe problem with targeting Debian Stable + Backports is that your packages are going to perpetually out of date unless you go to the trouble of packaging up your dependencies as .debs and running your own apt server. Targeting Debian stable is fine if you can get away with using three year old libraries. But for a lot of languages, like Python, 3 year old libraries are at a significant feature disadvantage when compared to their current counterparts.
- calpaterson 11y agoDebian stable includes pip and virtualenv. If you want to manage your python dependencies for yourself that road is definitely open to you.
- icebraining 11y agoMixing pip and debs loses some of the advantages of having a standard system, though. I think you're better off producing deb packages from PyPI in your build server.
- chei0aiV 11y agoThere are some tools to help out with that: https://wiki.debian.org/AutomaticPackagingTools https://wiki.debian.org/AutomaticPackagingTools https://summit.debconf.org/debconf15/meeting/257/automatic-packaging/ https://summit.debconf.org/debconf15/meeting/257/automatic-p...
- justizin 11y agoI typically rec installing virtualenv systemwide, if a reasonable version is available by package, and managing per-app dependencies in a requirements.txt that's platform agnostic. The Debian ecosystem is great, but I would never recommend a developer marry an app to it.
- icebraining 11y agoBut there's no reason you can't have the cake and eat it too; you can create a virtualenv from a requirements.txt file on your build server, then package it up in a deb package that installs those files in a custom directory (not in the shared Python modules path). That way, you get static artifacts you can deploy (instead of deploying using pip, which requires compiling any non-pure-python package on the server), you get to use apt's dependencies for non-Python packages, like system libraries, and you can easily rollback by simply pushing the previous version of the deb package, which is cleaner than rolling back with pip, in my experience.
- annnnd 11y agoWhen you say "out of date", you probably mean feature wise, not security and stability wise? For me that is an acceptable tradeoff for most of the packages. Most of the stuff doesn't evolve at such pace that I should have the latest and greatest (I am talking about core libs and similar). And the packages where I miss some new functionality, I can just upgrade them manually. Take Firefox for instance - if you don't like/trust Iceweasel, you can just install FF to /opt/ and trust Mozilla for upgrades. For me this is win-win situation. You have a stable and secure foundation and you put bleeding edge stuff on it when you need it.
- tankenmate 11y agoIndeed, for myself I prefer stable releases (Debian, Ubuntu LTS, etc) and use apt pinning so that I can use newer versions of apps that I need to use. Very rarely will I have a problem; in fact the few times there is a problem it is normally solved by apt-get source ; dpkg-buildpackage.
- stephenr 11y agoDo you just use pinning straight out the gate, or do you check backports (or whatever equivalent Ubuntu has) first?
- tankenmate 11y agoIt depends, normally in order of preference LTS, LTS backports, then latest release. So then if you want the newer version you can do apt-get install <package>/<release>. I typically use Apt::Default-Release "<release>" in a separate apt.conf.d file.
- XorNot 11y agoJust yesterday I had a problem which was some combination of Debian Jessie's incredibly outdated Python CFFI library (0.8.6) and its interaction with OpenSSL which took a script from taking milliseconds to launch to over 1.5 seconds, purely due to that import.
- bbrazil 11y agoA bit over a year ago I researched what "Devops" means, and the answer seemed to be Developers being able to push code to production without having to involve Operations. This sounds like a good goal to have (presuming you've got good unittests etc.) as it removes an unnecessary friction for developers. What it doesn't include is all the higher-value work the people on the Operational side tend to provide, like thinking about rollbacks, machine failure, network failure, provisioning, capacity planning, change/configuration management, security, monitoring etc - which is not to say that all developers don't think about these things, their focus tends to be on developing product rather than these non-functional requirements. I'm presently in a world of Ubuntu LTS+a few manual backports for similar reasons as the authors. My home systems are ansible managed, giving me things like wireshark installed everywhere if I need it and new machines automatically hooked into Prometheus monitoring (which is much easier with my debs). I've seen what happens if you try to manually manage machines, and know that a small bit of upfront work will bring dividends later. Writing the core code is just one critical step in running software long term, let's not forget the rest of the critical steps to keep it running in a sane way in the future.
- chei0aiV 11y agohttps://packages.debian.org/prometheus https://packages.debian.org/prometheus
- bbrazil 11y agohttp://deb.robustperception.io/ http://deb.robustperception.io/ is my nightly build. It's one of the few things I want to run on the very bleeding edge of.
- stephenr 11y agoMany people have different interpretations of the term 'DevOps', but what you're describing in that first paragraph is Continuous Deployment. Yes, it's related to (in that it's often a beneficial result of) but it's not explicitly the same as DevOps, by any definition I've seen, good or bad.
- skarap 11y ago> The way developers somehow think DevOps is (or should be) an abbreviation of "Developers doing/replacing Operations" is terrifying to me. And what about the way management thinks that's when you don't have to pay Operations people (those guys who always try to stop progress in your company)?
- stephenr 11y agoSounds like another way of saying the same thing to me, no? No one says "we don't need someone to setup/maintain our servers". DevOps is, in every interpretation I've seen, about who/how it's done.
- skarap 11y ago> No one says "we don't need someone to setup/maintain our servers". Of course they do. And there are a lot of products which are marketed using that idea: "AWS Elastic Beanstalk is the fastest and simplest way to get an application up and running on AWS. Developers can simply upload their application code and the service automatically handles all the details such as resource provisioning, load balancing, auto-scaling, and monitoring." The configuration management/orchestration tools also help with that (you don't need anyone to provision the servers, take care of dependencies etc., you can just include these 15 Chef cookbooks, and everything will be done automatically). Btw: I'm not saying configuration management tools are bad - they are a must-have, I'm just saying - nothing will replace a person who knows what they are doing.
- stephenr 11y ago> Developers can simply upload their application code and the service automatically handles all the details In this situation, you've basically traded your own Ops staff for a combination of your developers and whatever support AWS provides you - so you're back to a managed service like every man and his dog was using in the 90s.