3 ms·

So is this a PaaS or an orchestrator? Those terms have some very specific meanings to people, and being a PaaS to me means supporting a huge pile of things like

by aimless 12y ago

So is this a PaaS or an orchestrator? Those terms have some very specific meanings to people, and being a PaaS to me means supporting a huge pile of things like taking deep control of the user's application language stack and architecture, while hiding all the orchestation details as much as possible. There is mention of CD, which is often taken to mean some sort of plugin architecture with other services that automates the whole deployment pipeline, but I don't see that in the documentation. There is also mention of "No special code required in your services" as well as "service discovery", but Docker doesn't really have a way to specify service discovery (the closest thing might be Compose). Wouldn't that mean there's "special code required" for our services, or is there some magic under the hood? Finally, "Zero-downtime deployments" sounds like a killer feature that I don't feel anyone else has gotten right. I'd love to learn more about the tech strategy, especially with regard to bringing hosts up and down and migrating services. Neat stuff.

lukebond 12y ago
paz documentation, presentations and (now out of date) website mention CD and environments a lot because it has always been a design goal of Paz to enable a CD workflow and give you quick and easy developer environments. as it currently stands it's far from having achieved that. i ripped out the environments stuff before open-sourcing it because it was half-baked and hacky. expect these things to start coming back into paz in the coming months. what remains that's related to CD is really just that it can receive webhooks from the docker hub / quay.io so you can have a pipeline like git push -> webhook to CI server -> run tests -> docker build -> docker push -> webhook to paz for deployment. as for orchestration and traditional PaaS functionality, i tend to agree with you and it's arguable whether or not Paz is actually a PaaS in the sense most people use that term. Paz is a platform that can run your services with a PaaS-like workflow. that's probably a more accurate way of putting it. re "no special code", there is a little magic. paz creates a sidekick unit for your services that will announce them in Etcd. it uses Confd to watch for changes to announcements and reconfigures HAProxy under the hood. i need to document this :)

by aimless 12y ago

lukebond 12y ago

paz documentation, presentations and (now out of date) website mention CD and environments a lot because it has always been a design goal of Paz to enable a CD workflow and give you quick and easy developer environments. as it currently stands it's far from having achieved that. i ripped out the environments stuff before open-sourcing it because it was half-baked and hacky. expect these things to start coming back into paz in the coming months. what remains that's related to CD is really just that it can receive webhooks from the docker hub / quay.io so you can have a pipeline like git push -> webhook to CI server -> run tests -> docker build -> docker push -> webhook to paz for deployment. as for orchestration and traditional PaaS functionality, i tend to agree with you and it's arguable whether or not Paz is actually a PaaS in the sense most people use that term. Paz is a platform that can run your services with a PaaS-like workflow. that's probably a more accurate way of putting it. re "no special code", there is a little magic. paz creates a sidekick unit for your services that will announce them in Etcd. it uses Confd to watch for changes to announcements and reconfigures HAProxy under the hood. i need to document this :)