VMware announces App Volumes 3.0 with healthy dose of new features

It looks like VMware is preparing some new EUC nuggets for everyone to consume soon. Today marks the announcement of App Volumes 3.0 and with other events planned in February there seems to be other news coming also.

1av-new-features

 

AppToggle – This feature introduces the idea of app cloaking or the ability to hide applications within a layer if the user is not entitled to them. This provides the option for organizations to create fewer application layers containing multiple applications rather than a larger amount of layers with single apps. In the briefing it was explained that VMware is not just simply hiding the application from the user, they are preventing individual apps from being layered on at the time of the layering being attached to the OS based on individual user entitlements. This sounds pretty interesting and I look forward to getting some hands-on time with this feature.

AppCature with AppIsolation – This feature is integrating ThinApp with the App Volumes capture process. Through a CLI in your capture VM you can enable the application to be isolated, which creates a ThinApp package as part of the process. This allows for applications to enjoy the benefits of isolation where needed and have it all happen in the same workflow. In the past you were able to separately create ThinApps and then include them in a layer, VMware is streamlining the process here.

AppScaling with Multizones – This feature is about working on improving the recovering and multi-site alternatives that App Volumes can support. In the past I’ve been pretty critical of several VMware products for not having a mature story around DR and Active-Active designs. I won’t know if this is a solid alternative or just a good enough one. What is now possible is the ability to use external file servers as the central point to pull AppStacks from. The external file servers has an association with each vCenter server and allows for flexibility in dealing with multiple sites. The idea allows for designs to use DFSR or NAS devices and take advantage of their replication functions, rather than build a replication engine into App Volumes.

Linux-based management VM – The previous versions of App Volumes required Windows for the install of the management console. This new version moves this to Linux which aligns with what VMware is doing for other products and allows for opening up API’s and the unified console story.

Other misc features to mention

  • Layer merging – the ability to merge multiple AppStacks into a single layer (Stack).
  • CLI – A command line interface has been added, which would primarily be used in the capturing and building of AppStacks.
Read More

Radical VMware EUC business ideas

We are almost a month into 2016 and the stream of 2015 recap and 2016 prediction articles and blog posts have finally stopped. But out of these and some recent thoughts, I came up with a few radical ideas for the VMware EUC business unit.I’m well aware that these have pretty much no chance at coming true, but I thought they would make for some interesting conversations. Who knows maybe the right person will read this and it will all come true.

I’m well aware that these have pretty much no chance at coming true, but I thought they would make for some interesting conversations. Who knows maybe the right person will read this and it will all come true.

 

Create an open alternative 

Divorce VMware EUC products from only working on vSphere as the hypervisor platform. This does not mean that the pair is not a good match, it just means that it could be a great opportunity to open up to other hypervisors. Today this is the approach that Citrix offers by supporting multiple hypervisors and offering their customers the choice of platform to deploy on. This flexibly helps by allowing others to drive innovation and offer different cost alternatives when it comes to licensing. With VMware working on building Project Enzo as the future of EUC, which is being built from the code from the Desktone DaaS product. The original Desktone product supported multiple hypervisors, so the code and support was already there to start with.VMware Workspace can still work closely with VMware on vSphere integrations, but they would be focused on using API’s and should be loosely tied to specific vSphere versions. Today if you deploy the whole horizon suite stack with vSphere and maybe even VSAN. Well if you need to update vSphere for a bug or new feature or want the latest VSAN release a hypervisor upgrade is required.

VMware Workspace can still work closely with VMware on vSphere integrations, but they would be focused on using API’s and should be loosely tied to specific vSphere versions. Today if you deploy the whole horizon suite stack with vSphere and maybe even VSAN. Well if you need to update vSphere for a bug or new feature or want the latest VSAN release a hypervisor upgrade is required. A Horizon upgrade usually forces a hypervisor upgrade usually forces a Horizon upgrade unless it’s just a maintenance release. These updates may also force a database version update if you were lagging in your SQL version already. As the stack continues to grow the cascading dependencies has gotten very long and upgrade one later can force a number of other upgrades that you were not interested in doing.

By offering a more open integration with vSphere this could be reduced, also by support other hypervisors you open up a number of other alternatives. VMware has been focused on trying to build the ultimate EUC product suite offering and giving customers a single vendor to deploy. But the reality is that most customers usually are still deploying at least another vendor for profile management (UEM) and monitoring tools. It’s a long a hard process for a single company to build a perfect product suite offering. This does not mean VMware should stop trying but by offering

It’s a long a hard process for a single company to build a perfect product suite offering. This does not mean VMware should stop trying but by offering a all VMware and an open alternative they can give customers the ultimate choice. By having more freed around the

By having more freed around the hypervisor VMware Workspace could build their next generation management layer in any cloud service. This means that they could host or allow customers to build Enzo management layers in AWS or Azure rather than being stuck with VMware Cloud offerings that are not as widely adopted. Below are the current VMware suite offerings, there are a number of options and you can see as you move up there are a large number of products.

Below are the current VMware suite offerings, there are a number of options and you can see as you move up there are a large number of products.

vmware suites.001

 

The open alternatives would allow customers to seek out the best products in the supporting products and not have to pay for VMware legacy products when they want other alternatives.

open suites.001

 

Spin out EUC Business unit

The idea here is that VMware would spin out the EUC business unit into it’s own private or publicly traded company. This idea would make the first idea a lot more feasible. We will call this new entity VMware Workspaces, nobody better register that domain name before I get the chance.

VMware workspaces would own the Horizon (Apps & VDI), App Volumes, UEM, Mirage, workspace, ThinApp, and AirWatch products. They should probably also own and control the Workstation and Fusion products since they are desktop related also.

The new entity can still work closely with the VMware hypervisor team and other teams to continue to build integration between the core products and the EUC products. But the new VMware workspace company is free of any legacy core data center baggage and roadblocks that keep them from innovating and moving to market faster. I think this new freedom could greatly benefit the existing products, processes and allow for the new entity to advance their solutions faster.

VMware Workspace would also be free to offer integrations with 3rd party solutions and provide greater options for customers to build solutions from as discussed earlier. They would still have an all VMware option, but by offering the open option the product licensing can be reduced.

I also think that a separate EUC entity would be free to innovate without having to conform to legacy VMware products. A good example around this would be EUC monitoring. The existing vROPS monitoring tool is heavily deployed for core VM management, but does not do a great job for EUC monitoring. It also is very polluted when you are forced to load different management plug-ins to support different platforms. By being free to create their own monitoring tool a better product could be released.

In the past, this probably would not even be possible, but in the last 2 years VMware has built a great leadership team in the EUC business unit. Along with acquiring several products in this time period they have also grabbed up some excellent leaders, ones that are better to lead a company rather than a business unit. The executive team for a future VMware Workspace entity could be Sanjay Poonen as CEO, Harry Labana a VP, Noah Wasmer a VP, Shawn Bass CTO. Also with growth of the EUC product sales and AirWatch purchase there is now probably plenty of revenue to support a separate entity.

 

Read More

Everyone in the US does not have good internet options!

This topic may come to a surprise to many or maybe not. I apologize to my regular readers as this is a bit off topic. We live about an hour or so outside of Chicago and about 8 miles past the last major suburb. This is not the end of the world, or well maybe it is for technology and communication companies. But for our family, it makes sense because we like the space that crowded neighborhoods cannot provide. I can ride motocross in the backyard, shoot guns and archery, the wife has plenty of space to garden and I don’t have 5 neighbors staring at me while I grill hamburgers. But for these luxuries I live in the 1990’s when it comes to internet service.

The need for better internet with faster speeds and no bandwidth limits is only getting greater each year if not faster. I have not been able to watch a Youtube video without it buffering for 10 years. If we get a new game for PS4 or Xbox One and it requires an update of 1-2gb or more this might force us to wait days before playing. Oh and all this with the console companies wanting to get rid of physical media and go only to downloading games. Using streaming TV and movie services is also extremely difficult.

Sure I’ve tried every possible solution that might exist and so has all of the other people that suffer from these same problems. But the telco, cellular and cable companies do not care about what I would call the “Reverse 1%” when it comes to internet options. There are several cellular companies that provide decent 4G LTE service in our area but to get enough bandwidth to make it usable on a monthly basis would cost hundreds and hundreds of dollars.

We were customers of a new service called Karma and they offered 4G LTE server with a 5Mb cap but unlimited bandwidth per month. Well that only lasted a few months before the idiots running things over there decided to change things. You can read about it here. They took what was a pretty good option that made it unusable for the people that really needed it. It was good enough that we even paid for two accounts there, one of which was a Christmas gift for our kids. The gift of sort of usable internet, it’s what every kid wants as a present in 2015. This Karma screw up and years of pain is what motivated me to write this.

There is a business opportunity here for someone and they are ignoring it. Back in the early DirecTV days they were not allowed to sell satellite TV service into areas that you could get cable in, until the laws changed. Companies like Verizon, ATT, Sprint, T-Mobile ext. could do the reverse of this. Offer a 4G LTE service with unlimited bandwidth to people in areas that have no or only terrible internet options for a reasonable rate. This does not seem like rocket science, and you don’t have to offer it en masse to others that have good options already. I don’t expect 1Gb internet for $10 a month, but would be willing to pay $150 for unlimited 4G LTE without speed limits.

Sure we could move and after this long it’s something that we are considering. But to find another area that we like that also has good internet will require some time and effort. This problem won’t go away for everyone else because not everyone can or is willing to move. So common man, let’s get this fixed. It’s 2016 and everyone should be able to binge watch their favorite show from Netflix.

bush-hates

 

Read More

Migrate VMs from vSphere to Acropolis Hypervisor – AHV

When it comes to building out a new Acropolis (AHV) cluster you are either starting out with new VMs or looking to migrate existing VMs from a vSphere environment. I have covered the process of creating new VMs in the “Creating VMs on AHV” post in this series. But if you are moving from vSphere to AHV, then there are two challenges that must be planned for. The first one is what will the conversion process look like and second, what will the migration process look like. With each of these are multiple choices and it will be up to the project team to decide which is the best choice for the project. There are likely other options that I might not mention here either.

Converting vSphere VMs

The task of converting a vSphere VM to a VM that runs on AHV is not that different than other hypervisors or even the P2V days when you were moving from physical servers. You have a VM that is in a vSphere format and must be converted to a different format. It will also have VMware tools and drivers installed into the operating system. After the conversion these will need to be cleaned up, just like they would be when migrating to other platforms.

For this there potentially two viable candidates. The first would be grabbing the virtual disk file (VMDK) from a datastore and using the image management feature in AHV to import and convert the disk. There would still be cleanup to be done, but it’s a simple one-off way. This method would not be ideal for doing a bunch of VMs, it however might be a simple method if you just have a hand full of template VMs that you want to populate on the new cluster.

The second and leading choice is to use the following method. In short with this method you are installing the VirtIO drivers in advance, think of them as the drivers that VMware tools install. Storage vMotion the VMs to a shared Nutanix datastore, power off the VM and create a new VM on AHV using the vDisks that were moved over. A fellow Nutant and VCDX has already created a detailed blog post about converting a vSphere VM to run on AHV. You can read the full details here as written by Artur Krzywdzinski.

In the future I would like to see something like Double-Take offer a solution that would offer help with these cross-platform conversions and migrations. This is something they have working for cloud migrations today. I see this becoming a common task in the future and demand is only going to increase for organizations wanting to move workloads between different resource pools whether they are on-premises or off-premises and very few of these moves will support a single VM format.

 

Migrating the VMs

The conversion process was just covered for what is available at the time this was published. I also touched on the option of sharing out a datastore from the AHV cluster to an existing vSphere cluster. This would allow you to Storage vMotion any VMs to that shared datastore before shutting them down to complete the conversion process. This method will likely be the most heavily used, since its familiar for other legacy types of migrations between old and new infrastructure.

A second option is available if both the vSphere and AHV clusters are running on Nutanix gear. You can create a Protection Domain (PD) on the vSphere cluster to replicate all of the VMs to the AHV cluster. This will get the data over to the AHV cluster in an efficient manner, this would be a great option if moving between sites also.

 

Read More

Live Migration on Acropolis Hypervisor – AHV

Live migration is the ability to move a running VM from one host (node) to another without any downtime or loss of connectivity. Some vendors call this live migration, if your a VMware person this is known as a vMotion. Live migration is supported on an Acropolis Hypervisor (AHV) cluster, whether it is initiated manually or through an automatic process.

There are several ways for VMs to be live migrated to other hosts, the most common is for someone to use Prism to select the VM and choose to migrate it. They can also occur when a host is placed in maintenance mode which evacuates all VMs, from the Acropolis CLI or via the REST API.

 

How to live migrate an AHV VM

Acropolis managed virtual machines can be manually migrated to other hosts within the cluster through the VM portion of the Prism interface. First you select VM option from the top menu. Then choose the table view,  then select VM to be moved and click the migrate option.

migrate steps

 

The migration action window will present the admin with the option to let the system automatically select the target host based on resource utilization or via the drop down option, allow the admin to manually select the target host from the list of nodes in the cluster.

migrate VM

 

The following image shows that you can easily select the target host to move the VM to, if you do not want to let the system make the selection for you. Click the Migrate button and the VM is on its way to the new host.

migrate options

 

API Migrate Option

I still have very little experience with API’s but wanted to show that the option is available.

migrate api

 

ACLI Migrate Option

The ACLI option offers the ability to specify a max bandwidth for the move along with the expect destination options.

migrate cli

 

Conclusion

I know that live migrating a VM is pretty boring these days as it should be. But educating the community that this feature is available and showing how easy and flexible it is to use is also need.

 

Read More

Nutanix Acropolis Hypervisor for beginners series – AHV

I started my life in IT with MS-DOS and then moved into Windows when that became a thing. Then the wonders of VMware were introduced to me about a decade ago and I never looked back. Along the way, I have had limited exposure to Linux and related systems and it was always something that I wanted to learn more about, but other things always came first.

Since joining Nutanix recently, I will be learning a lot more about the Acropolis Hypervisor (AHV) offering that is built from KVM roots. This will be a new challenge for someone with my background and I’m looking forward to it. To help others with a similar background, I thought that a series of blog posts covering topics on getting started and operational tasks would be a good place to begin. These posts should help others that are new to virtualization or are experienced with VMware vSphere or Hyper-V already.

In the upper right margin of each post is an index of the posts in this series for easier access.

 

Creating networks on AHV

Configuring HA on AHV

Live Migration on AHV

Migrate VMs from vSphere to AHV

Managing VMs on AHV

Monitoring VMs on AHV

Image Service

Creating VMs on AHV

Using the Acropolis CLI (ACLI)

Upgrading AHV Hosts to new version

 

If there are other topics that you would like to see, drop me a note in the comments or via another method and I’ll consider it. If this series is well received I may do an Advanced AHV series at a later date.

 

 

Read More

Creating VM networks on Acropolis hypervisor – AHV

If you are building a new Acropolis Hypervisor (AHV) cluster there will likely be several networks that will need to be configured for VMs to consume. Also for existing AHV clusters, we all know that as environments mature and grow, typically additional networks are introduced. For these reasons a walkthrough on how to configure these networks on AHV is part of these series.

The Acropolis Hypervisor (AHV) leverages Open vSwitch (OVS) for all VM networking. When creating a new AHV cluster the management and Nutanix CVM networking paths are configured automatically. On a newly created AHV cluster there are no VM networks created automatically, VM networks are configured through Prism or the Acropolis CLI (ACLI). When networks are created within Prism they are automatically configured on all AHV hosts within the cluster to ensure compliance.

 

Creating VM networks in Prism

The process to create a new VM network through Prism is a simple pop-up form to fill in with the network name and corresponding VLAN ID. Once a network is created, it will be available for assignment to existing and newly created virtual machines. To get started once in Prism there are two options for getting to the network config. The first is to click on the gear in the upper right and select Network Configuration. The other option is when you are on the VM screen in prism in the upper right there is a green button for Network Config. Both options are shown in the image below. 

network config

 

Read More
Page 1 of 5012345...102030...Last »
%d bloggers like this: