Skip to main content

Hybrid cloud - Missing automation link Part 2

If you read my previous post (part 1), I kind of concluded that you had 2 choices. Of course the answer is somewhere less binary and perhaps in between the two options. This post is another discussion about where we are headed in an non-technical way, I hope.
 

"Reflecting on my future" - A scenario

"So you are sitting there enjoying your coffee and analyzing what has happened in your datacenter the last couple of years. You have "virtualized" the network and the load balancers (you do use Citrix Netscalers right). Your Netscalers are happily living their life as virtual appliances on your hypervisor along with the rest of the windows/linux servers. Your clients are being served by System Center Configuration Manager. The users can deploy their new laptops from SCCM and use the Software Catalog to install the software packages they need. Your servers and SNMP network devices are monitored by System Center Operations Manager and you have implemented System Center Service Manager with ITIL-processes throughout the enterprise. Of course SCSM is using System Center Orchestrator to provide automation for all those self-service options you have deployed in SCSM-web portal. Creating new virtual machines is a breeze with the standard template you have available in your tool that manages your hypervisor environment. You are happy, the users are happy and most importantly the “El Presidente” is happy. Life is good, however you wonder about the future. What will it bring in the next couple of years?"

Overall I bet a huge number of companies are in a very similar context or "location" in regards to how their IT-solution is setup/configured/running. Some will have linux computers/servers, some will have additional client management solutions present, some will have huge Citrix/Terminal-servers farms and some is already running their system on Azure.
 

The future

Two things will happen going forward:
  1. Windows Azure Pack (WAP) and/or VMM or some other product like it with similar features
  2. "Efficiently manage and configure your datacenter"
Some will do the first item and live happily with it further into the future. Others will do both and be very happy and never look back. WAP with System Center is Hybrid Cloud. It is super flexible and crazy powerful. Wait, why does not WAP give us efficiency in the datacenter? Glad you asked.
First and foremost let's dive into WAP/Virtual Machine Manager and look at a few things from the IaaS perspective:
  • You can create templates and deploy VMs with roles/features etc
  • You can create VMroles (VM Gallery) which defines the basis for creating VMs (Resource Definitions) and installation of applications, roles/features, deployment script (pre/post). This is very powerful and plugs right into the Azure Portal where you assign it to a "plan" your tenants subscribe to.
Screenshot from Azure:
image

Now what happens when you need to upgrade one of those gallery items (new versions and stuff). Sure, you create a new definition based upon the previous version, upload it to VMM/WAP and your tenants can do an upgrade right in the tenants portal:

image

You can even downgrade after you upgraded if you are not happy with the new version. As I said, it is super powerful. Here is a screenshot of the Virtual Machine Role Authoring Tool:

image

I have probably not even scratched the surface of what is possible in WAP. Please check it out for your self.

Like with Azure, if you consume an standalone web-site (Paas), you are not responsible for maintenance of the underlying VM(s) required to host your web-site. If you decide to order an virtual machine (VM) and configure IIS with all the bells and whistles it requires, you may be responsible for updates related to the operating system, features, IIS-components, .net etc. Actually if you buy a VM (Iaas) on Microsoft Azure, you are responsible for applying updates to that VM. Microsoft will not do it for you.

Ask yourself one question. How are Microsoft capable of maintaining/updating all those VMs hosting the standalone Azure websites, since they are responsible for keeping it up to date? You probably guessed it, they use automation everywhere, on everything all the time.
 

The missing link and challenge

Now here is the puzzle that is troubling me. Why does WAP/VMM NOT give us a efficient way of controlling the configuration of our datacenter? How can you make sure that the configuration laid out in your templates/VMroles stays the way you said it should? That is where our good friend Desired State Configuration (DSC) walks in the door and saves the day. Why? Because that is what DSC does. It configures your node(s) using a declarative language and makes sure that that configuration is applied ALL the time. So with WAP/VMM and DSC you have fulfilled both items on our list and you can regain your focus on other important business development projects.
 

Summary

It is hard not like the huge opportunities that comes with this combination. I challenge you to investigate an come up with an better mixture of tools that enables you to take control of the datacenter to the same extent. Next post coming up will talk about general strategy in automation and why you should automate you infrastructure.
















Comments

Popular posts from this blog

Developing PowerShell modules for REST APIs – Part1

Over the years I have developed different PowerShell modules for different web APIs. I thought it would be a good idea to write a 2 series post about how you could go about to do this. This will be a 2 part blog series where we will run through the entire process of building a module for a REST API. I will try my best to keep this as simple as possible and leave more advanced stuff for a follow up post if the interest is there.What you needDepending on your experience with source control and PowerShell in general, you might want to use GIT or some other software repro for the code. In addition we are going to create a test REST API using the splendid UniversalDashboard PowerShell module created by Adam Driscoll. It is available on the PowershellGallery. Other prerequisites are built-in to Powershell. I will assume that you will be following along using at least PowerShell version 5 or greater.
What is HTTP metods for REST API.The primary or most common HTTP verbs used are POST, GET, PU…

Serialize data with PowerShell

Currently I am working on a big new module. In this module, I need to persist data to disk and reprocess them at some point even if the module/PowerShell session was closed. I needed to serialize objects and save them to disk. It needed to be very efficient to be able to support a high volume of objects. Hence I decided to turn this serializer into a module called HashData.



Other Serializing methods

In PowerShell we have several possibilities to serialize objects. There are two cmdlets you can use which are built in:
Export-CliXmlConvertTo-JSON
Both are excellent options if you do not care about the size of the file. In my case I needed something lean and mean in terms of the size on disk for the serialized object. Lets do some tests to compare the different types:


(Hashdata.Object.ps1)

You might be curious why I do not use the Export-CliXML cmdlet and just use the [System.Management.Automation.PSSerializer]::Serialize static method. The static method will generate the same xml, however we …

Developing PowerShell modules for REST APIs – Part2

This is part 2 of the REST API blogpost. In part1 we successfully setup two REST API endpoints using the UniversalDashboard PowerShell module. In this part we are going to create a simple module that support some CRUD operation against our API. As we are trying to keep things as simple as possible, we will not use any fancy framework (like Plaster) to build our module. We are also going to skip a very important step you should familiarize yourself with, Pester tests. Lets get to it.


The moduleWe will build a module called FilesAPI. The module folder will look like this:



In the functions folder I have already added the 2 helper functions from part 1, Get-AuthorizationHeader and ConvertTo-Base64. The other folders are just placeholders for important stuff like classes, private functions that you do not want to make available for the module consumer and tests for Pester tests. For such a small module that we are going to create, one could argue that it is much easier to just add the functi…