871 karma · joined January 28, 2011
“I believe in the rkt model,” said Lennart Poettering, systemd lead developer. “Integrating container and service management, so that there’s a 1:1 mapping between containers and host services is an excellent idea. Resource management, introspection, life-cycle management of containers and services – all that tightly integrated with the OS; that’s how a container manager should be designed.”
Once you're up and running on the AWS platform with any significant infrastructure setup, you're basically locked in for life. I hope there are counter-examples, but I'm unaware of any significant migrations off of AWS in the last few years. Some of that is due to their overall pretty high service level, but it's also incredibly hard to replicate the AWS infrastructure on your own because the tooling either doesn't exist or is immature.
I think there's a really under-served niche of startups with AWS spends of greater than $200K/year that would love to move some or most of their infra off of AWS to achieve greater cost saving or unlock different product possibilities that can come with running in a datacenter or across different cloud providers. And would be willing to pay for services and tools to fill that need. I'm finding myself in that situation now, and even though we've been careful to not get tied in to most of the managed AWS services, we're still facing lock-in due to heavy integration with cloudformation. Without a good open-source or managed service alternative to just cloudformation, we're basically faced with needing to completely re-architect our systems if we move off of AWS. And full re-architecture initiatives tend to stay near the bottom of the Devops backlog if things are working.
"Future development on the Linux containers framework is now based on the docker command-line interface. libvirt-lxc tooling may be removed in a future release of Red Hat Enterprise Linux (including Red Hat Enterprise Linux 7) and should not be relied upon for developing custom container management applications."
Have you looked into using reserved instances?
AWS may be more expensive, but perhaps instead of migrating away from AWS to another provider, you can start using AWS more efficiently. Most people I've helped out in similar situations were able to reduce their AWS bills between 50-75%.
How big is this cluster? Are you writing and reading to the entire cluster, or do you have certain nodes that you write to and others that you read from?
And re:memory, it's pretty tight on most end-user machines. By default, most laptops only come with 4-8GB of RAM. And in the cloud, memory cost is perhaps even more expensive. On ec2, a 'large' instance usually has only between 4-8GB of RAM. The default small instances have only 2GB of RAM, which doesn't give much room left over for applications after you account for the OS and various utilities.
It can definitely add up.
Even though you're young, try and still go to the doctor every once in a while for checkups. But even if you don't like going to doctors, don't just ignore pain in your body. For example, ignoring a sore wrist or back, or ignoring digestive and sleep issues can easily lead to life-long disabilities.
It's also common for people to experience mental health issues (in a way that starts to impact relationships and work performance) for the first time in their early 30s...
It's a fairly common event, but it's generally really scary for everyone involved. Getting stable with medication and then also working with a trained therapist can help you pull through this.
It's not possible to run a Docker container with systemd, upstart or sysvinit working without major workarounds. So while it is possible to use a custom and hacked environment to get a docker container that simulates a regular linux system, out of the box it's simply not possible.
I think it's entirely accurate to call Docker a system for managing application containers. LXC can be run with various options, but by reading the lxc docs (one example here: https://wiki.debian.org/LXC) you can see that it supports various normal init systems and not just the process managers that can run under Docker.
It appears that Canonical is positioning LXD as more of a drop-in and simple alternative to VMs. It's also nice to see that LXD containers will support running docker containers within them. So you can have your 'pod' of application containers all running within one big LXD container if you want. Good times.
Some good comments on both sides here:
http://www.quora.com/Python-Web-Frameworks/What-are-the-adva...
http://www.reddit.com/r/Python/comments/ktjm2/jinja2_or_mako...
I've felt for a long time that with the right tooling, smartOS/Illumos would make an ideal Container OS. Glad to see that they're moving hard in this direction.
Some companies are crazier than others... a lot crazier.
Would definitely prefer BTRFS to be stable over having additional features...
However it's clear from the docs that you can grow zfs pools by adding new vdevs. Shrinking a pool is not possible.
In practice I haven't seen the inability to shrink pools as an issue. I simply do not create pools from entire disks and use partitions instead. For example each drive is split into 5 partitions. And if I need to grow a pool I add another partition across all my disks to the pool as a new vdev.
This also allows me to have multiple pools on each system that have different Raid-z levels based on different app reqs.
I was definitely impressed by the pulldocker err... now pullcontainer project and think it'd be great to see how you secure your containers and handle networking.