23david

16 ms·

121.
by 23david 12y ago
DevOps tools are rapidly evolving. Now that they've basically finished with machine provisioning, dependency management and orchestration, all major DevOps automation frameworks are going into managing reactive infrastructure. Enforcin
122.
by 23david 12y ago
Curious why you wouldn't consider Openstack to be a Datacenter OS? :-)
123.
by 23david 12y ago
Task distribution primitives are handled by Mesos and implemented in the various apps running on Mesos (Marathon, Chronos, etc.) It seems inaccurate to call this a feature of DCOS. Puppet and the like can easily configure and manage Mesos a
124.
by 23david 12y ago
lol. mind blown. "Mesosphere Announces First Data Center OS And $36M In Funding" - Techcrunch "Mesosphere’s new data center mother brain will blow your mind" - GigaOM
125.
by 23david 12y ago
They're general purpose devops automation frameworks... you can choose to take any of them and make this 'deep integrated' layer you speak of. For example, Openstack deployments are commonly automated using Puppet scripts. (R
126.
by 23david 12y ago
Having 2000+ VMs without automation or monitoring in place is pretty unusual. Especially for a site like healthcare.gov which must have had all sorts of HIPAA and data security requirements. But it's honestly not hard to hook all those
127.
by 23david 12y ago
Master Controller to Minions... configure thyselves... Datacenter Controller maybe, but calling this an OS?
128.
by 23david 12y ago
Chef/Puppet/Saltstack/Ansible/CFEngine/Nix OS
129.
by 23david 12y ago
Part of the problem here could definitely be communication. For whatever reason, it's been incredibly hard to follow what is going on with the Docker project. Keeping info in one place would definitely help. I'm not able to find
130.
by 23david 12y ago
Not sure. Never heard of an official partnership program either, so I'm interested to know details about how this partnership program works. Could be innocent, but something about it smells like a OSS shakedown to me. Just 'cause
131.
by 23david 12y ago
You're more than fair. They made the rules, and I guess they can break the rules. But really, the value of the project lies in the community's continued support and backing of the project. The good thing is that this is open-sourc
132.
by 23david 12y ago
would be great if the other Docker employees were as clear as you are about that. Are you willing to share the contract details involved in these partner agreements? What do partners have to agree to in order to be an official partner?
133.
by 23david 12y ago
Speaking for the DevOps, a large part of the job is being responsible for building trusted systems from trusted components. I want to continue considering Docker to be part of that trusted stack, but from looking at the minutes, it seems th
134.
by 23david 12y ago
Benevolent dictator can work. But here Docker has said they want to make it possible for the project to be community led and run over time. Actions on the ground speak otherwise. Hard to restore trust once lost.
135.
by 23david 12y ago
AWS started as an open-source community project boasting contributions from over 650 contributors? Recent post by Docker CEO Golub: There are over 650 contributors (95% of whom do not work for Docker, Inc.). http://blog.do
136.
by 23david 12y ago
Many many solutions have been meeting that need just fine and many new ones are still in the works. Adding a new solution will not help things.
137.
by 23david 12y ago
This is a completely new product and really should be differentiated as such via new packages: apt-get install docker.io-platform Just don't put any of this stuff into the docker.io or lxc-docker packages and mostly things will
138.
by 23david 12y ago
Agreed. I'm very confused about how the concerns from the advisory board are (not) being addressed in an open manner. From reading the minutes, it seemed to me like one of the clear conclusions (based on concerns raised by big stakehol
139.
by 23david 12y ago
With their (current) control of the main docker index and namespace, they could have stuck with a simple GitHub model (pay for private indexes) and would have been fine. With the community goodwill that they had, it would have been impossib
140.
by 23david 12y ago
Systemd is a fair comparison. Systemd is a modular system, and it's also possible to not install different components if you want. Most of the components aren't strictly necessary. I think your community is begging you to continue
141.
by 23david 12y ago
If it's an open/pluggable system why the need for these 'partnerships'? Any OSS project can just quickly hack in support for Docker, just as they've been doing for almost 2 years now. This is getting ridiculous.
142.
by 23david 12y ago
Docker Machine looks to be a revision/rebrand of your docker hosts proposal made in the last 1-2 days or so. Very confusing. The proposal discussion: https://github.com/docker/docker/issues/8681 Rename &
143.
by 23david 12y ago
They sound like a closed-source vendor at this point. I'm surprised to see an open-source project mention "ecosystem partners": Each one is implemented with a “batteries included, but removable” approach which, thanks t
144.
by 23david 12y ago
These aren't new projects... just rebranded versions of half-baked feature proposals that I thought were still being reviewed/discussed. I guess somewhere a decision was made to move forward regardless of community concerns? Bakin
145.
by 23david 12y ago
I definitely wouldn't consider Mesos to be anything like an operating system for the datacenter. That's just marketing language and confuses things. Mesos is basically an application scheduler. It doesn't manage the base ope
146.
by 23david 12y ago
I consider Twitter to be an open-source company. The amount of open-source work they sponsor and incubate surpasses that of most traditional vendors. Their business model is also a lot better. They have a nice unrelated service they make mo
147.
by 23david 12y ago
Ops (particularly in Enterprise) doesn't want batteries included by default. Principle #3 and #5 are incompatible IMO. Do one thing and do it well... Seems to me that post-Docker 1.2, the Docker team has taken Ops concerns much less se
148.
by 23david 12y ago
This is great news, particularly for Enterprise customers adopting containers. IMO, Docker's 'new' direction completely ignored the tremendous amount of support they had from the sysadmin and devops communities. But crucially
149.
by 23david 12y ago
Interesting... Didn't think that avahi would work across subnets. I hope it works with the OSX firewall turned on and set to secure settings. Will need to test, but there are workarounds I've had to use in similar situations.
150.
by 23david 12y ago
Can you give some examples of TOML-based Rust package configurations that you think are good? My experience using TOML for config files has been very different. IMO, using YAML for the config format is still the best option for most use-cas

More ›