2015 was a remarkable year for Docker, the hugely popular container technology. Here at Flexiant, we have long argued for the long-term importance of containers. So much so that, as recently announced, we have launched the Kubernetes Orchestration as a Service feature within Flexiant Concerto, making it simple to orchestrate clusters of Docker containers, which is where we believe the industry is headed. Let’s take a look at what Docker has achieved over the past year.
Last week we announced the Flexiant Kubernetes Orchestration as a Service feature in Flexiant Concerto. We also demonstrated the new service in a short six minute video and showed how easy it is to the launch the guestbook feature in Kubernetes using Concerto.
This week we go into more detail to show you how to execute the guestbook example using the Concerto command line. Through the command line we will create a Kubernetes cluster and deploy these microservices from the guest book to the command line.
Need some help with your cloud strategy? You’ve come to the right place. Our blog combines insights from experts across the cloud industry with a focus on telcos and service providers to help you grow your business. If you missed some of our blogs this year, check out our top 15 cloud blog posts of 2015.
This week we announced Flexiant Kubernetes Orchestration as a Service (KOaaS). Enabling DevOps to use Kubernetes on any cloud, in minutes, Flexiant Concerto lets you get creative without any pain.
I’ve prepared a short six minute video for you to see KOaaS in action. Kubernetes Orchestration as a Service allows you to get Kubernetes on any cloud, easily leaving more time to focus on the creative side of Kubernetes. This video shows you how easy it is to launch the ‘hello world’ guestbook feature in Kubernetes.
Today’s Flexiant Cloud Orchestrator Deep Dive focuses on Jade APIs that provide the entire Business Logic layer for our cloud management software. Jade is the top level management structure in the software stack. Jade contains and manages the following elements:
Jade talks to the Cluster Coordinator (Tigerlily) to then control each individual cluster of resources.
Jade provides three APIs:
1. A user API, used by end users for manipulating virtual resources on the platform (available by REST and SOAP)
Jade’s user API allows end users of the platform to manipulate their own virtual resources. Authentication is by user and customer, meaning that a user who is so permitted can manipulate resources of different customers using the appropriate authentication credentials.
Administrators can use the user API, authenticating as the administrator but passing the UsernameToken SOAP header (SOAP) or X-AssumeToken HTTP header (REST) set to the authentication username (the login username, a slash, and the customer UUID) of the customer concerned; see Authenticating to the APIs for more details.
2. An admin API used by administrators for various administrative functions (available by REST and SOAP)
Jade’s admin API provides a means for users with administrative access to perform administrative functions on the platform. Users with administrative access are:
Jade provides an interface to allow authenticated administrators to perform administrative functions only within the Billing Entities they are authorized to use. For instance, they can:
Jade’s admin API does not permit administrators to manipulate the virtual resources of customers directly. In order to manipulate customer resources, administrators should use the User API, authenticating as the administrator but passing the UsernameToken SOAP header (SOAP) or X-AssumeToken HTTP header (REST) set to the authentication username (the login username, a slash, and the customer UUID) of the customer concerned. For more details see Authenticating to the APIs.
3. An open API, available unauthenticated for retrieving objects prior to authentication (available by REST only).
Jade’s open API provides a means for unauthenticated users to retrieve in a read-only manner certain resources without authentication. For instance, to allow the sign-on screen in Skyline to retrieve login graphics, blobs are retrieved which are marked as public.