Tectonic from CoreOS is an enterprise-grade Kubernetes solution which simplifies management operation of a k8s environment by leveraging CoreOS, fleet, Rkt and Flannel. In this article we’ll manually build a cluster of three CoreOS nodes on top of VMware Fusion to see how all of this fits together.
For years Google is driving its infrastructure using containers with a system named Borg, they are now sharing their expertise with an Open Source container cluster manager named Kubernetes (or helmsmen in ancient greek) abreviated k8s. Briefly said Kubernetes is a framework for building distributed systems.
Release 1.0 went public in July 2015 and Google created at the same time, in partnership with the Linux Foundation, the Cloud Native Computing Foundation (CNCF).
If you want to know more, read on.
Software Defined Networking (SDN) is often qualified as immature and tagged as complicated. Amongst the many solution available on the market, some of them can do a tremendous job of decoupling physical networking from logical networks used by cloud consumers. It then empower end users to deploy whatever architecture they need on their own. So deploying OpenStack without making sure to tackle the networking requirements of your team could be a recipe for failure.
In this article we’ll show you one way to address such a SDN requirement by showing you, step by step, the way to deploy Juniper Contrail 3.0 on top of Mirantis OpenStack 7.0 (Kilo).
In the Enterprise world, user authenticates over an Lightweight Directory Access Protocol (LDAP) most of the time. Openstack Keystone, the identity service, integrates natively with LDAP directories for authentication and authorization services. The configuration of Keystone can be automated using Mirantis LDAP Fuel Plugin.
This article is a step by step guide to integrate Keystone to OpenLDAP but any other LDAP directory including Active Directory could do a perfect job too.
In large datacenters it’s common for each rack to live in its own broadcast domain. Fuel allows to deploy nodes on different networks by leveraging its Node Groups functionnality. In this article we’ll details the required steps to make this possible using Mirantis OpenStack 7.0 and we’ll also review Node Groups support improvements coming in MOS 8.0.
Mirantis OpenStack 7.0 got released few days ago and brings OpenStack Kilo and lots of innovation. I’m happy to share with you today a really nice feature, Reduced Footprint offers a way to deploy OpenStack on a small footprint as its name implies, two servers would be a good start. But three servers are still the bare minimum to achieve control plane HA.
Fuel will start by deploying a KVM node and then instantiate VMs to deploy OpenStack Controller within it. Fuel can also move itself to the same KVM hypervisor to free up one more physical node. In the end you’ll have a controller and fuel running on one machine, and the other bare metal server will be used as a compute node. That’s exactly the objective of this article so lets get started.
Imagine if you could easily get a virtual load balanced IP address for your fleet of web servers hosted on OpenStack as soon as you need it without having to wait for the networking team who’s managing the hardware load balancer to handle your request ?
That’s exactly what OpenStack Neutron is offering with its Load Balancing as a Service (LBaaS) technnology which first appeared as an experimental feature in the Grizzly release. It’s built on the same model as the Network as a Service solution, an OpenStack operator can choose whatever load balancing technology which provides an OpenStack Neutron driver. Major load Balancing players like F5 or Citrix offers or will offer LBaaS Neutron drivers. I don’t have such devices in my backyard, so I’ll use the Open Source reference implementation instead (HAproxyNSDriver), based on HAProxy and supported by a french company headquartered in Jouy-en-Josas by the way ! To make things even simpler, I’ll also leverage the Mirantis OpenStack Fuel Plugin for LBaaS which makes installing and configuring LBaaS a breeze.
VMware released on march 23rd NSX-v 6.1.3 which now support vSphere 6.0. I was waiting for this release to upgrade my Bulb lab to the latest and greatest, so here am I. In this article, I’ll describe the upgrade process. I’ll start by upgrading NSX to 6.1.3 and continue on by upgrading vCenter Appliance to 6.0. I’m eager to get the latest improvement that both vSphere 6.0 and NSX 6.1.3 offers.
For years a big gap existed between embedded OS for smartphone and server operating system. Mark Shuttleworth and his team have been working for quite some time on optimizing their Ubuntu operating system for the smartphone world. Beginning of december, they’ve announced a new transactionnally updated version of Ubuntu optimized for the cloud, the result of their years of working for the embedded world. Snappy is a minimal server image where applications can be upgraded and rolled back atomically. It’s not the only similar initiative, it started with CoreOS, a reachitected Linux OS to run modern infrastructure stacks, but RedHat is also trying to keep up with project Atomic. Snappy can be used to run Docker containers but not only, it’s one of the main differentiator of Canonical solution.
Unfortunately Canonical doesn’t offer a VMDK version of their Snappy technology, which we need to deploy it on our OpenStack vSphere environment. This article we’ll show you how to proceed then.