qstack_qstack_release
Facebooktwittergoogle_pluslinkedinmail

From the moment we began developing Qstack, our on-premise cloud management platform, our goal has been to address and solve the real problem that is fragmentation of infrastructure and cloud management without any specific lock-in, other than quality of the product.

We took the approach very early on to decouple the Qstack management node from the running workload, meaning that the Qstack management node can be upgraded, rebooted or shut down without affecting the workload.  That means, if you are not happy with Qstack, you can quite simply terminate the contract, uninstall or delete the Qstack management server and you can still have your base KVM, VMware, Hyper-V or bare metal environments running. Easily replaceable is a value proposition, in our opinion.

Being hardware and hypervisor agnostic (KVM, VMware and Hyper-V) was step one;  supporting not only hypervisors but bare-metal (dedicated server) provisioning was step two. Step three was to have built-in native hybrid cloud capabilities  that allow you to not only manage your internal infrastructure and private cloud with Qstack, but manage your public cloud usage – AWS and Azure (and GCE, which is coming soon) – from the same Qstack management server.

Now with our latest release, which includes a fully integrated Kubernetes-based container and application orchestration layer, we took a giant step towards our dream of a full stack solution.  Our customers now have the freedom to choose the perfect platform for their workloadwhether it be a bare-metal server, virtual machine or a containeron-premise or in a public cloud of their choice from within the same CMP.  That, in our opinion, is the “True Cloud Concept.”

We took a different approach when it comes to Kubernetes. We want to make it extremely easy for the average user to use our UI without inhibiting the power-user who might want to use the Kubernetes API or the kubectl cli. We also give a full overview of your Kubernetes cluster and how the applications are performing, and of course, all events and logs are accessible through the UI.

Overview of your running applications from the Qstack UI.
Overview of your running applications from the Qstack UI.
Three different ways of creating an application, from a YAML configuration, create from image from any docker repository or directly from a Helm Blueprint.
Three different ways of creating an application, from a YAML configuration, create from image from any docker repository or directly from a Helm Blueprint.
Manage your application from the Qstack UI.
Manage your application from the Qstack UI.
Cluster overview.
Cluster overview.

We are incredibly proud of the latest release of Qstack and how perfectly Kubernetes plays into our overall strategy. The ability to spin up your own personal Kubernetes cluster or have a centralized, operations managed Kubernetes Cluster gives you that added flexibility we keep jabbering about. If you want to know more we would of course be more then happy to jump on conference call for technical deep dive or just a quick demo…

For more information on Qstack’s new container and application orchestration module and other features included in this release, please see the release notes.