Juju vs Openshift

Giuseppe Attardi giuseppe.attardi at garr.it
Tue Jun 27 09:00:00 UTC 2017

I found this quick comparison between Openshift and Kubernetes:
	https://medium.com/levvel-consulting/the-differences-between-kubernetes-and-openshift-ae778059a90e <https://medium.com/levvel-consulting/the-differences-between-kubernetes-and-openshift-ae778059a90e>
It points out that OpenShift adds routes, projects and configuration.
Projects provide authentication and resource management, that seems what you already get with O~S projects.

Then there is Deployment Configuration:

	https://docs.openshift.com/container-platform/3.3/dev_guide/deployments/how_deployments_work.html <https://docs.openshift.com/container-platform/3.3/dev_guide/deployments/how_deployments_work.html>

that looks quite similar to what Juju does.
Then the question is: can Juju deal with configuration of Kubernetes pods?


> On 27 giu 2017, at 10:31, Ante Karamatić <ante.karamatic at canonical.com> wrote:
> Hi Giuseppe
> On Tue, Jun 27, 2017 at 9:32 AM Giuseppe Attardi <giuseppe.attardi at garr.it <mailto:giuseppe.attardi at garr.it>> wrote:
> Some Italian public administration are considering purchasing cloud services for Big Data analytics deployed on Openshift.
> How this solution would compare with using a Kubernetes cluster deployed through Juju?
> More in general, what is the strategic outlook of container platforms vs virtualization platforms?
> Are the former ones going to overcome the latter?
> There is never a solution that fits all. Some will prefer cloud, some will like application containers, some will prefer machine containers. We are already in container world, while the cloud is still around. And obviously, bare metal machines are still here. So is VMware.
> In the end, one should not limit its own business to one specific infrastructure technology. In fact, one should look to be as flexible as possible with infrastructure. Obviously, there is a lot of cost in maintaining flexible anything.
> The way it looks today, Kubernetes is currently shaping up to be the the leader in docker orchestration. But, who knows what future brings, right?
> With juju there is one thing you can be sure of - whatever future brings, juju will be there, capable of connecting different infrastructure solutions. I know it sounds questionable coming from a Canonical employee, but It really is a unique strength. Being able to preserve operations knowledge and people while the world is rapidly changing around you is very cost effective.
> -- 
> Ante Karamatić
> ante.karamatic at canonical.com <mailto:ante.karamatic at canonical.com>
> Canonical

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20170627/542fa3d7/attachment.html>

More information about the Juju mailing list