| #cloud-config | |
| coreos: | |
| fleet: | |
| etcd_servers: http://192.168.12.10:2379 | |
| metadata: role=node | |
| units: | |
| - name: etcd.service | |
| mask: true | |
| - name: fleet.service |
| { | |
| "title": "VMware", | |
| "services": { | |
| "query": { | |
| "list": { | |
| "0": { | |
| "query": "*", | |
| "alias": "", | |
| "color": "#7EB26D", | |
| "id": 0, |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
You can now find this packaged up nicely in a rubygem as rollout-zk.
I've implemented a zookeeper-based storage adapter for [rollout][] that does not require any network roundtrips to check if a feature is active for a user.
| mysqladmin ext -i1 | gawk '/Queries/{q=$4-ql;ql=$4; printf("%s QPS: %s\n", strftime("%H:%M:%S"), q)}' |
Adrian -
I appreciate that you spent time in writing this post. I know I've been up until 2am writing similarly long ones as well. I will take responsibility for having what is likely an irrational response (I blame Twitter for that) to the term "NoOps", but I invite you to investigate why that might be. I'm certainly not the only one who feels this way, apparently, and thus far have decided this issue is easily the largest distraction in my field I've encountered in recent years. I have had the option to simply ignore my opposition to the term, and just let the chips fall where they may with how popular the term "NoOps" may or may not get. I have obviously not taken that option in the past, but I plan to in the future.
You're not an analyst saying "NoOps". Analysts are easy (for me) to ignore, because they're not practitioners. We have expectations of engineering maturity from practitioners in this field of web engineering, especially those we consider leaders. I don't have any expectations from analysts,
For a moment, I'm going to throw away my automation and configuration management hat. I'll let you know when I put it back on. Also, let's ignore that we're talking about Riak specifically for a moment. Also also, let's ignore any (for a brief moment) the proper role of a package manager.
If you're writing server software, you have two target markets. The system administrator/operations team and the developer.
The main reason you want autostart is to get people up and running quickly. To do this, you need to ship safe and sane defaults. This means something like a default configuration that listens only on localhost.
| # Pipe Ars Technica's live Apple event coverage into a Campfire room. | |
| # http://arstechnica.com/apple/news/2010/01/tablet-live-event-liveblog.ars | |
| # | |
| # Usage: | |
| # $ gem install -r hpricot tinder | |
| # $ ruby -rubygems ars_live.rb -ssl mysubdomain myroomid myapikey | |
| require "hpricot" | |
| require "open-uri" | |
| require "tinder" |