There also a very interesting sub-discussion about bundling Notary and TUF together, an what the implications are for pairing image signing and package signing into a single request. While TUF can be seen as a next gen tool for signing groups of digital content, it's relationship at this point to Notary is yet to be solidified.
It's been through three rucks and has been my daily partner for three years now.
As a bike commuting New Yorker, I'm frequently carrying my whole life around plus laptop, and it's been perfect. It looks as new as the day I purchased it.
They're two entirely different classes of programs. In my mind, a good to-do lists has the feature set of being able to manage both 'evergreen' (i.e., informational stores) or ephemeral (i.e., time-logging / task completion) with ease.
The first thing that stuck out at me was it was browser only. I want my information close at hand. I use a tiling window-manager, so I can just keep Chrome open 24/7 and within a day or two be a key-stroke away from Tdo, so that's not too much of an issue, I suppose, but being able to `tmux attach` from any console and hit `1 (my leader key is `) to get to my main emacs instance is far more convenient. (In fact, I've xmodmap'd my Windows key to swap to that screen with a permanent instance of my terminal with my pane containing nothing but org-mode, so I'm never more than a keystroke away from reading my notes/adding a task/jotting something down, but I digress)
Second, it claims to be 'keyboard driven' but none of the GNU Readline (standard bash/emacs bindings) or vim hkjl's work. The second I have to leave my homerow, my workflow is broken. The arrow keys along with F5 through F8 on my laptop are keys which immediate "no gos"* I can't muscle-memory-hit.
Thirdly, it's not nearly as feature rich as TaskWarrior (which, despite being a time-tracking tool in name, has enough functionality re: tags and search, that I consider it to be an information store).
Not that it's trying to be as far as I can tell. To use an analogy from a bygone era, its functionality is oriented more towards what you'd put onto Post-its rather than what you'd write on your legal pad.
* Pro-tip, map R_alt + hkjl to the arrow keys and you won't ever have to use the arrow keys again.
From the design goals outlined in the FAQ, it seems clear to me that Google expects there to be a great deal more bandwidth hungry devices in the home speaking first to each other, and then out to the WAN, in the near term.
Including Bluetooth, Weave, and Thread, along with up to 128 devices, gives me a rough sense of the scale of connected devices they anticipate in each home. Given that it also has a reasonable compute capabilities and cooling as one of the highlights, I think it's far to say that it could do a lot of processing on its own before reaching back home to the GOOG DCs.
One of my favorite parts of living in this (at-points) expensive, overcrowded, noisy, competitive, shallow, and brutal metropolis is the extensive walking culture that we share. My walk/bike commute to work could meander along the same main and side streets, with every one of the ~251 trips taken being uniquely constructed.
Furthermore, that ignores the wiggling route I enevitably travel, pushed left by a honking cab and similarly colored stoplight, or nudged right by the inevitable crowded side street filled with movie sets or construction vehicles.
Putting aside the health benefits of human-powered-travel, it's both a refreshing and invigorating way to spool up my mind on the way into the office, and also a way to decompress and release the day's aspirational steam that's best not blown out all at once, just inside your apartment.
The walkability of New York -- or rather the non-walkability of every other city in America -- is what keeps me here. So many other cities with nicer weather, more beautiful landscapes, but all of them depend on vehicles to varying degrees.
SF is only 7x7 miles. Completely walkable if you have good, strong hips for those 42 or so hills ;) And when you've decided to stop walking, make your way to House of Prime Rib for a hearty meal and 2000 calories...
Even during brutal weather, the subway was active - it has never let me down. Sure it is crowded, you'll have to deal with rudeness etc. But the public transit here is comprehensive and reliable. Can't say the same about other big cities in the U.S. It is also awesome to walk, especially during summer (only prob is too many tourists taking pictures all over the place blocking your way)
Sometimes when I'm stuck on a bug, I just go on a ride on my motorcycle. I'd be too afraid to ride a motorcycle in New York (lane splitting actually saves lives, and this is prohibited in NYS), but I do this around SF, Marin, and around the bay. Being on two wheels or on your feet allows you to enjoy the scene. For whatever reason, there's something about 4-wheels that doesn't allow you to do so.
But drivers in both cities still suck. The image of a cyclist being thrown into the air 10 feet on Folsom and 15th still sticks in my memory. I later learned he died. Never ever take the road for granted, even wearing Kevlar gear and a full-faced helmet; still no match for any steel framed vehicle. I'm always dumbstruck every time I peer into someone's window and I see the driver's head down, looking at a phone...
I think it'll be quite interesting to see how the smaller players organize themselves around the multitude of cluster resource management tools emerging as a natural reaction to Kubernetes growing out of the work Google's done on Borg.
I am curious to see how long of a shake-out period will exist before there's either a de facto stack of "compute resource" tooling, or if there's always going to be a highly fragmented and diverse way to accomplish your goals. Just off the top of my head (and there's way more) I'm thinking about Tectonic[1], Mesosphere[2], Rocket [3], Kismatic [4] as a few examples.
As a technologist and a planner, it's been challenging to see far enough into the future to decide on what tools to devote myself to learning at this point. I do think we're certainly in a "post-public cloud" timeline where we're getting good enough (or will be in 6-12 months) at abstracting virtualization right up to a millimeter or two below the application layer of our stacks. How we choose to do so seems to be currently up in the air.
In my mind, this opens up the possibility of compute as a resource much wider than had previously been possible. We'll be less reliant upon Azure, AWS, and GCP's mixture os Paas and Iaas and much more interested in compute as a resource, likely from bare metal or private cloud providers.
I'm looking forward to the increased efficiency (both through compute power and cost) and security available in moving from a application-level virtualization to operating system-level virtualization.
Disclosure: I work at Google and was a co-founder of the Kubernetes project.
I think your observations are interesting. From my (somewhat biased) viewpoint I don't think we will enter into a 'post cloud' world. There are very real efficiency gains from running at public cloud provider scale, and the economics you see right now are not what I would consider 'steady state'. Beyond that the systems we are introducing with Kubernetes are focused on offering high levels of dynamism. They will ultimately fit your workload precisely to the amount of compute infrastructure you need, hopefully saving you quite a lot of money vs provisioning for peak. It will make a lot of sense to lease the amount of 'logical infrastructure' you need vs provisioning static physical infrastructure.
There are however legitimate advantages to our customers in being able to pick their providers and change providers as their needs change. We see the move to high levels of portability as a great way to keep ourselves and other providers honest.
Since we have someone who worked on these projects here, there was a report a couple of years ago about Borg and its successor, then called Omega. Is Kubernetes related to / a renamed Omega?
Omega is a separate system than both Borg and Kubernetes.
Kubernetes is heavily inspired by both Borg and Omega, and incorporates many of the ideas from both, as well as lessons learned along the way. And many of the engineers who work on Kubernetes at Google, also worked on Omega and Borg.
Please feel free to respond to me at your leisure, but are you * sure * we will never enter a post-cloud world?
Not to say that there will be no cloud infrastructure, per se, just as mainframes still exist today.
On the other hand, I imagine someday we will have "datacenter in your pocket" type devices. The challenge will be who has the data -- obviously Google has already identified this as a key strategic advantage. The challenge will * not * be who has enough resources to compute it.
These pocket devices seem natural as a way to place strong AI at your fingertips, Siri-like agents, autonomous robots, etc. The first ones, which we have now, either use a data connection or are optimized to have small data sets, but the need for larger data sets is obvious. Once it becomes the primary limiter, I think it will only be a matter of time before "big data" is decoupled from the cloud and personal computing retakes its dominant position. Some will use laptops, some will use phones, but the effect will be the same.
There are also the privacy benefits from managing large datasets on your own device -- solutions are already available for things like how to back up your data, how to sync large sets of common data among a network of untrusted peers, and how to curate that data.
good AI tends to run on massive clusters. Barring some quantum leap in computing technology, I don't see how computation on local devices would fill our computing requirements.
Can you comment a little bit more on where you see the steady state economics of public cloud going? From where we are today, what factors (other than the dynamic provisioning you mentioned) will lead to better economics?
Yeah, I think that sadly, there is going to be a little bit of an inevitable equivalent to the unix wars of the early 80s. The sooner we can reach a standard place, the better it's going to be for the container community and developers more generally.
One of the reasons that I pushed hard to get Kubernetes open sourced, is the hope that we could get out in front of this, and allow the developer community to rally around Kubernetes as an open standard, independent of any provider or corporate agenda.
We've spent a lot of time working with the Kubernetes community. I can only speak to our experience, but Brendan, Craig, and the rest of the team at Google have 100% lived up to the commitment of treating the Kubernetes project as truly open and independent.
Our Kubernetes dashboard was recently merged into Kubernetes [1]. We brought our own vision of a web ui to the project, and we could have gotten bogged down defending technology decisions, and philosophical nits. Instead, the response from Google, RedHat, and others in the community, was basically "Awesome! How soon can we get it in?"
All of the key players have the right approach, and that gives me confidence in the project's longevity.
I'm curious, @caniszczyk why would it need to become independant outside of Google? It's already an Apache licensed open-source project hosted on GitHub.
In essence, having diversity in ownership can help the project have a long life instead of being governed by one entity. There's a lot of risk that the main entity in charge will do things in its self interest instead of the self interest of the project (and its constituency) over the long term.
Independent ownership and proper governance will setup the project for long term success and as a small company, you should prefer it to be that way.
I'm extremely pleased that Kubernetes has been open sourced by Google. It truly seems to me that the developer community is and will remain to be able to rally around Kubernetes as an open standard both today and in the future without fear of any outside agendas; as Brendan so eloquently stated. I for one applaud Google's level of transparency when it comes to the future of the project and the overall product vision.
I'm wondering if it was intentional or subconsciously accidental that you went with the "I, for one" construction... which is of course usually suffixed with "welcome our new [adjective] overlords".
I'm also very curious which direction things will move. I think I'm less convinced than you are that it'll be away from AWS and the like though, they're innovating at least as fast as the open-source container cluster tools (at least it seems that way to me).
I can imagine a future where it gets easier and more common to build an arbitrarily complex backend by just hooking together AWS services, using Lambda (or something that evolves from it) to write all your custom business logic without ever thinking about a server, VM, or container. I'm working on a greenfield app and very seriously considered this route now we but ended up deciding the uncertainty vs doing it the way we know wasn't quite worth it. It feels very close to the tipping point to me though.
>just hooking together AWS services, using Lambda (or something that evolves from it) to write all your custom business logic without ever thinking about a server, VM, or container.
you're risking to awaken the ghost of Application Server.
This was linked elsewhere in the thread https://github.com/etsy/cdncontrol/ and Etsy seemed to be up through the entire thing. So perhaps they're doing something right :)
AWS Status shows Cloudfront DNS issues, which is reflected in our page's assets not loading. Kinda makes me wish we were using something like https://github.com/etsy/cdncontrol/ but that's a fight for another day!
<title type="text">Informational message: DNS Resolution errors </title>
<link>http://status.aws.amazon.com</link>
<pubDate>Wed, 26 Nov 2014 17:00:39 PST</pubDate>
<guid>http://status.aws.amazon.com/#cloudfront_1417050039</guid>
<description>We are currently investigating increased error rates for DNS queries for CloudFront distributions. </description>
-------
- FEMA is moving to level 1.
- The DPA was last invoked during the cold war
- Links to FEMA [1] and Wikipedia [2]
- Doctors may now practice across state lines
- A 100 page plan has been recently published which references an 18 month cycle for the pandemic [3]
- There was a reference to a "significant proportion" of serious infection rates in the millennial generation based on early reports from India
Links:
-------
[1] https://www.fema.gov/defense-production-act-overview
[2] https://en.wikipedia.org/wiki/Defense_Production_Act
[3] https://int.nyt.com/data/documenthelper/6819-covid-19-respon...