helloiamaperson

take a look at my post from earlier: https://news.ycombinator.com/item?id=13031870 . I'd be interested to hear your (and others') thoughts.

Since you're doing research in this area, have you taken a look at something like https://www.dyadicsec.com/ at all? I looked at the whitepaper a while ago, and it seemed to make sense, though I was way out of my depth.

Check out concourse.ci [example pipeline at https://ci.concourse.ci/]. It fully supports building docker images - https://github.com/concourse/docker-image-resource

I'd love to hear more about your solution. Are you saying that you've created an algorithm distinct from paxos/raft/zab that's more robust?

Being able to rebuild critical infrastructure from source, and know that you'll be able to reliably deploy it, is a _huge_ win for security.

In that case, you might be interested in bosh: http://bosh.io/docs/problems.html (the tool that enables the workflow jacques_chester was describing). It embraces the idea of reliably building from source for the exact reasons you've mentioned.

You should take a look at https://bosh.io/ . It does what you want wrt devs being responsible for defining how the software runs, environment reproducibility, etc. Unfortunately, the learning curve is pretty steep.

As Titanous said, BOSH operates at a lower level than Flynn. You could use BOSH to deploy Flynn, hypothetically. A more direct comparison would be Cloud Foundry.

There's a foundation that's a separate entity that owns the IP: https://www.cloudfoundry.org/membership/members/

I'm pretty sure it's quite valuable, though I'm also unclear what people would be willing to pay.

Your solution probably works great for your needs, but this stuff is expensive to productize. See https://www.openshift.org/

One PaaS with developers in mind is https://nodechef.com It would be interesting to see how they do.

Is this your product? All of your comments are about it.

The most production ready versions of this kind of thing are http://geode.incubator.apache.org and https://ignite.apache.org .

Terraform's model (local state files) is not something that works well, in my opinion. Since AWS doesn't know that you want some operations done "transactionally" (like with CloudFormation), you can easily end up with a half built env that needs to be cleaned up. PaaSTa is more of a CF competitor, as far as I know, not really at the same abstraction level. I think that it would be a lot easier to clean up the UX/marketing of BOSH than doing the opposite.

Oh, so kind of like: http://concourse.ci/?

You mention Puppet and Chef, but how does it compare to more holistic tools like terraform, juju, and bosh?

https://news.ycombinator.com/item?id=10333576

https://news.ycombinator.com/item?id=10333576

I'd love to hear more about your use case and what I could do to improve the situation. You can contact me with the email address in my profile if you're interested. Thanks!

Hell, you need a separate VM just to install it.

I'm not sure why that's a problem. If you want something that's actually like heroku like in terms of uptime and what not, you need something that can manage the health of the cluster. Dokku's cool, but it doesn't make sense for anything you actually need to depend on. If it doesn't make sense to pay for the overhead of running your own paas, just use Heroku instead.

http://www.openshift.org/ or http://cloudfoundry.org/index.html, both used in production by f500 companies

Or use cloud foundry (http://cloudfoundry.org/index.html) if you have a burning desire to stand up your own paas vs. just using heroku.

With Nix it seems like the technology is there. It works. It has a superior model compared with other systems. However, it lacks a corporate sponsor or large community to make it "professional-grade". Canonical and RedHat make their money from people depending on their packages being continuously up to date.

Check out bosh: http://bosh.cloudfoundry.org/ . It has a somewhat similar philosophy with respect to immutable instances and systems at large, and has strong corporate backing.

There is. It's called Cloud Foundry: http://www.cloudfoundry.org/index.html

Take a look at bosh: http://drnicwilliams.com/2012/05/15/bosh-what-how-when/ . It has its own problems, but it does exactly what you want, and is used for large scale deployments.

You can run databases inside of cf as well: https://github.com/cloudfoundry/cf-mysql-release

It sounds like you want Cloud Foundry (or OpenShift, which I have no experience with). (http://www.cloudfoundry.org/about/index.html)