4,059 karma · joined September 3, 2010
We've already done paid support contracts on the enterprise side and are developing the management service into a SaaS offering.
Our managed service is for users who want to outsource the management of the cluster to us. There's no secret extra technology (it's just Flynn underneath), what you pay for is a professional ops team to manage your cluster. The service is also freemium (and free for the vast majority of users).
https://www.youtube.com/watch?v=ePOWsePB8zY (part 1) https://www.youtube.com/watch?v=u5D83SpbTXM (part 2) https://www.youtube.com/watch?v=EcgV-lsQUwo (part 3)
In the first few days after we released the first Tent proof of concept we were swamped with user feedback and a variety of discussions. We addressed many architectural questions in detail from "why not use a custom binary protocol" to "consider using ostatus, microformats" and "Consider not making claims about REST". If you're still interested in any of these topics I'd be happy to explain in greater detail the reasons for our choices.
Tent has evolved a great deal since the initial release. We've discussed most of the reasons behind the choices we made in great detail on Tent, IRC, and during monthly office hours, recording of all are available online.
We're actively working on 0.4. The big challenge right now is that a number of organizations are considering using Tent is very large scale deployments for sensitive data, so we're making the transition from move fast and break things to enterprise grade reliability.
This includes everything from a solid protocol validator (future versions of the protocol will have complete validation coverage before we release a reference implementation) and a highly scalable multi-tenant server that large service providers can easily deploy. We're refactoring the server we use for hosting Cupcake users and releasing it under a permissive license in the next few months to make that transition easier.
So it's an exciting time for the core team but there isn't a ton happening on the surface just yet.
Our goal has always been to get Tent to a solid 1.0 after which the APIs could remain unmodified for several years at least (similar to HTTP and SMTP). The tradeoff is that we then need the freedom to break things between versions of the pre-1.0 versions. It's frustrating for early app developers (one of the reasons we don't encourage adoption) but will pay off once we hit 1.0
Flynn is a single platform that runs all your services from databases to applications to individual Linux processes. With Flynn ops teams can stop being consultants and start providing a single product to their internal "customers". Basically you can deploy and scale whatever you want all in one place on any infrastructure without having to think about individual hosts.
I haven't looked closely at Deis in several months, but Flynn doesn't use Chef (or anything similar) anywhere and don't plan to.
You can add any route to any app in Flynn, so different subdomains, domains, and TCP ports are pretty easy.
I feel like the projects have very different prospective user bases and communities (Mesos is an Apache project, hundreds of thousands of lines of C++; Flynn Layer 0 is run by a startup and only a few thousand lines of Go) and will likely develop in very different directions to service those communities.
That being said, we've explored creating a version of Flynn layer 1 components that run on Mesos instead of Flynn Layer 0 for users who are already deeply invested in the Mesos ecosystem.
Most of the development on Flynn (nearly all of the 2014 work) was done by Jonathan Rudenberg (@titanous), one of the founders of Cupcake. We brought in Jeff as a contractor and paid him out of the crowdfunding campaign. He contributed to the initial architecture and prototypes but stepped back in December.
I don't want to speak for Jeff (@progrium) but my understanding is that he'll keep evangelizing the project at conferences and may be working on a proprietary version/components at Digital Ocean.
The Cupcake team (especially Jonathan) will keep developing Flynn (of course with open source contributions) full time in the future.
Flynn Dashboard: At least some part of this will end up as open source in the not distant future, we're trying to figure out the best strategy for additional tools like the dashboard and what parts should be packaged.
This happens so often it would be great to have a standard and clear expectations.
Social systems can be broken in a way that won't manifest until a certain type of discussion comes up. So while I trust HN/YC to do their best to protect and promote discourse, I don't know that the types of conversation that come up during the evaluation period will be representative of all future conversation on HN
[1]http://dduane.tumblr.com/post/79161065289/the-amtrak-residen...
A 16 year old cable company is barely a startup, and highly unrelatable to the startup community at large. The same story about a US company wouldn't get coverage here unless there was a major strategic element. Kudos to the founders and funders, but it's not a particularly inspirational story for other entrepreneurs. The kinds of companies that get the most coverage here are very young and generally have a global reach. A regional company (which most telcos are) in say New England wouldn't get much coverage in the pacific northwest. This isn't a regional or even a cultural issue, just a significance issue.
However other organizations can and do work towards the same goals. I'm one of the creators of Tent[1] which shares a lot in common with Persona (including some community members) but is more ambitious in many ways.
In the Persona AAR Mozilla identified several reasons for Persona's failure to gain adoption[2] including that Persona " can't offer the same [as Facebook Connect] incentives (access to user data)". Tent's primary purpose is as a user data store and also supports features like address changes automatically (which Persona never did).
We were fans of and friendly with the Persona team, but I believe the best solutions to these problems will come from teams that aren't afraid to think bigger than Mozilla's strategy at the time allowed.
The work of federated identity solutions will continue on Tent and other projects, many of which are probably better suited for a wide variety of users and products than Persona would have been. Of course none of us have (or are likely to gain) the level of institutional (or financial) support that Persona had.
[1] https://tent.io
edit: Valleywag's already got it http://valleywag.gawker.com/startup-flying-dateable-women-to...