File size: 5,823 Bytes
51c7367 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 | Technology,Multi-Vendor,Developer self-service,Scaling support,Linux Support,Multi-language,Host failure recovery,Maximise availability during failure,Zero downtime deploys,Multi-tenancy,Access to raw stdout / stderr logs,Deployment process,Will maintenance / ops be easy?,Hosted Option,Deployable without PaaS,Level of documentation - does it seem enough? is it kept up-to-date?,Commercial support / consulting,Is there a sufficient level of access permissions?,Is it Open Source?,Is there a database service?,What language / tech?,API Access?,Production ready?,Any associated cost?,Resource profiling?,Is data backup possible?,Constraints,Date of evaluation
Deis 1.3.1,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,"The application must have its build pack present on Deis, have a docker file or be inside a docker image
The user install the deis client, registers, logins to the cluster (http://docs.deis.io/en/latest/using_deis/deploy-application/)
Using buildpacks, from the application main folder:
deis create <appname>
git push deis master
",Yes,No,Yes,Yes,No,Yes,Yes,Yes,Go,Yes,Yes,No,Yes,Yes,"Additional (not yet supported) languages may need an extra buildpack to be made
Deis requires wildcard DNS entries as access point to the apps, that may be an issue when using multiple cloud providers.",March 2015
Kubernetes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Partial,No,Yes,"Create a Dockerfile that has the right runtime and method of running your appliction.
Publish the docker image to a registry.
Create a pod or replicationController configuration.
Start it with `kubectl create -f <config>.json`
",No,No,Yes,No,No,[MISSING],Yes,No,Go,Yes,No,No,Yes,No,Very little - anything that can run in a container.,March 2015
CloudFoundry 2.0.0,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,"Step-by-step instructions and guidelines here: http://docs.cloudfoundry.org/devguide/deploy-apps/deploy-app.html
The application must have its build pack present on Cloudfoundry, or a new build pack must be made available for the given language
The user install the “cf” client,logins to the cluster
from the application main folder, the application can be created and deployed and eventually scaled:
cf push <appname>
cf scale <appname> <number of workers>
",Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,"mostly ruby, some go",Yes,Yes,No,Yes,No,"Cloudfoundry is pretty dynamic, allows for additions of language packs however running customer binaries may not be allowed.
Services can be pretty modular and customizable, in particular the ability to use services that are external to CF adds a layer of flexibility
",March 2015
OpenShift 2.0,Yes,Yes,Yes,Yes,Yes,No,No,Partial,Yes,Yes,"Install software (ie, ruby, JBoss, Play) required on each node, and then git push it.",No,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Ruby,Yes,Partial,No,Yes,Partial,"Additional languages may need an extra cartridge to be run
",March 2015
"Mesosphere - Mesos 0.2.1.1, Marathon 0.8.0, Chronos 2.3.2",Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,No,Yes,"The interested app should be containerized (in a Docker container) available through a repo chain
App deployment can happen very easily through one POST HTTP call to the Marathon REST API, based on a json template as simple as this:
""container"": {
""type"": ""DOCKER"",
""docker"": {
""image"": ""dcarley/example-go:latest"",
""network"": ""BRIDGE"",
""portMappings"": [
{ ""containerPort"": 31000,
""hostPort"": 31000,
""servicePort"": 1234,
""protocol"": ""tcp"" }
] },
""env"": [{
""name"": ""PORT"",
""value"": ""5001""
}]
},
""id"": ""go"",
""instances"": 1,
""cpus"": 0.50,
""mem"": 512,
""uris"": []
}",Yes,Yes,Yes,,Yes,No,Partial,No,Language: Mesos: C++. Marathon: Scala. Chronos: Scala,Yes,Yes,No,No,No,"Docker containers allow the flexibility to run different sorts of code and binaries
Lack of db as a service can be a limitation
Lack of granular credentials management can be a limitation
",March 2015
OpenShift 3.0,Yes,Yes,Yes,Yes,Yes,Yes,No,No,Yes,Yes,"Deploy from Docker image:
Create a Dockerfile that has the right runtime and method of running your application.
Publish the docker image to a registry.
Create a pod, service, route configuration file. [sample].
Start it with `osc create -f <config>.json`
Deploy from Git repository
Not tested: https://blog.openshift.com/builds-deployments-services-v3/
",No,Yes,Yes,No,Yes,Yes,Yes,No,Go,Yes,No,No,Yes,No,Very little - anything that can run in a container.,March 2015
Aurora + Mesos,Yes,No,No,,,,,,No,Yes,,,,,,,,,,,,,,,,,March 2015
Panamax on CoreOS,Yes,Yes,Yes,Yes,Yes,,,,No,Partial,,,,,,,,,,,,,,,,,March 2015
Rancher,Yes,Yes,No,Yes,Yes,Yes,No,No,Yes,Yes,"Create a Dockerfile that has the right runtime and method of running your application.
Publish the docker image to a registry.
Choose the host that you want to deploy it to from the UI.
Enter details such as image name, environment variables, and ports.
",Yes,No,Yes,No,No,Yes,Yes,No,"Java (API)
Javascript (web)
Go (some backend components)",Yes,No,No,Yes,Not tested,Very little - anything that can run in a container,March 2015
Tsuru,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,"Steps:
Make sure the appropriate platform or Heroku buildpack support is installed to the cluster.
Create a Procfile
Create the application with `tsuru app-create <name> <platform>`
Add a git remote with `git remote add tsuru <url from tsuru app-info>`
Push to the remote with `git push tsuru master`
References:
http://tsuru.readthedocs.org/en/latest/using/quickstart.html
http://tsuru.readthedocs.org/en/latest/using/go.html
",Yes,No,Yes,Yes,No,No,Yes,Yes,Go,Yes,Yes,No,Yes,Yes,"Additional (not yet supported) languages may need an extra buildpack to be made
",March 2015
|