Cloudify Service Binding For Kubernetes
This is the third post in a series about exploring the integration of Cloudify with Kubernetes via the Service Catalog feature. The first post explored the foundational concepts and set the stage for a project to develop a service broker for Cloudify. The second post described the architecture of the project, and provided a basic capability to list and provision services from and
How to Manage All Your Legacy, Network, Container, and Serverless Services Directly from Kubernetes
Kubernetes is at the top of the container food chain these days and we are seeing organizations run, or rather sprint, to migrate their services over to the ubiquitous platform. Cloudify is a service orchestrator that glues together legacy, network, container, serverless, and all your other services and ensures full control over your environments without
Kubernetes From The Inside Out
This post is part 1 of a 3-part series. You can find part 2 and part 3 linked here. Kubernetes is famously known for having an opinionated architecture; most notably container orientation, networking idioms, and declarative orchestration. As Kubernetes development has progressed, an increasing number of features have been added to accommodate and integrate with
Migrating Pods With Containerized Applications Between Nodes In The Same Kubernetes Cluster Using Cloudify
Kubernetes is decidedly the DevOps tool of 2018 for those companies already deep in the cloud-native game. More and more we’re hearing about companies moving to a container- and Kubernetes-driven architecture. We definitely see the draw for utilizing Kubernetes in a larger role – we recently updated our Kubernetes plugin and unleashed a new Kubernetes Provider –
Introducing the Cloudify Kubernetes Multi-Cloud Provider
In my previous blog post about the Kubernetes Plugin for Cloudify, I broke down the reasoning behind the need to orchestrate Kubernetes – the main reason being the need to orchestrate across diverse workloads. It’s no easy feat to get multiple Kubernetes clusters on different public and private clouds to talk with each other in
Edge computing workloads: VMs, containers, or bare metal?
This article originally appeared in Enterprise IOT Insights on October 11, 2017. We live in an era of connected and smart devices. With their proliferation, the growth of data has mushroomed to new heights. This data reaches all the way from the end user to your cloud or on-site data center for processing, storage, and
Orchestrating A Kubernetes Managed Virtual Network Function With Cloudify
This post explores the process of containerizing Quagga and deploying it using Kubernetes.
Support for FCO in Cloudify
This article was originally published on the DICE blog. Matej and Tadej Borovšak work at XLAB. The article is being re-published with the consent of the authors. Cloudify is an important component of the DICE deployment tool. It enables that the users can describe their applications in a human-readable text format YAML, using a TOSCA
Cloudify 3.4 Has Dropped – Orchestrate All Clouds!
Team Cloudify is very excited to announce the Cloudify 3.4 GA release! This was definitely the most packed release of Cloudify ever and brings with it some major improvements, all of which culminates in support for hybrid environments, with any stack, and on any workload, and covering more than 90% of infrastructures and workloads
Scaling Kubernetes Microservices on OpenStack With TOSCA Orchestration Pt I of II
In a previous post, I converted a Fabric-based plugin implementation to an Openstack agent-based implementation. In this episode, I finally reached one of the key goals of this long running effort; to automate scaling on Kubernetes using Cloudify native means. The path to this goal leads through some of the more exotic parts of