Second vSphere Client (HTML5) update in vSphere 6.5U1

With the release of vSphere 6.5U1, we are proud to announce the second update to the vSphere Client!

Just like last time, with vSphere 6.5.0b, those that have been using our Flings will not be surprised by the list of functionality updates for the vSphere Client. Now for well over a year a year we’ve been releasing updates to the vSphere HTML5 Web Client Fling on a (roughly) weekly basis, adding support for features, new user experiences, and more. As these changes have matured due to the excellent feedback we’ve received from the Fling’s users, we’re able to make further improvements and incorporate those into the vSphere Client included with 6.5.U1.

New Features

The online documentation for supported functionality has been updated to vSphere 6.5U1, available here (https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-client-65-html5-functionality-support.html), but for comparison sake, the bits are around Fling v3.15, give or take a few things.

This is the list of some of the additional functionality included. Same as last time, some of these features are presented in a partially complete manner (such as SPBM).  The plan is to fill out all features, but the more feedback we get from you regarding what is most important will help us deliver faster.

  • DRS/HA VM overrides
  • SDRS rules
  • Content Library – further actions
  • Roles and Global Permissions
  • Download multiple files as zip
  • Distributed Switch – further actions
  • Fault Tolerance
  • SPBM
  • VM Hardware – further items
  • Apply Customize Guest OS during Clone
  • VM Migration – further actions (compute+storage, Cross VC, batch)

Some of these flows may have had minor tweaks to make them easier to use and learn. If you have feedback about any of the new behavior, or missing portions of features, of course let us know using the integrated feedback tool by clicking on the smiley face in the upper righthand corner.

Calling for volunteers!

We would like to connect with users one-on-one to understand how much you’re using the vSphere Client either via vSphere HTML5 Web Client Fling or the vSphere Client (HTML5) bundled in 6.5 (6.5 GA, 6.5.0b and now 6.5U1).  If you’re interested, please fill out this form:

https://goo.gl/forms/TiJ0lAuYtW4ZTQ063

Still need your feedback!

With this release, we believe we can cover almost all of your regular operations.  It is vitally important that we get your feedback on this release on what the remaining high-priority gaps are so that we can get them into the next quarterly release.  In particular, letting us know specific times when you find yourself jumping from the vSphere Client back to the vSphere Web Client would be extra helpful.  Provide feedback through the above link, on the Flings page, or comments below.  We have a new hashtag too!  Please use #vsphereclient wherever you have feedback.

You can sign up to receive an email every time we release a new Fling version by signing up here: http://goo.gl/forms/IqGJ5twYHf

Thank you all for your feedback so far, and thank you in advance for all the feedback to come!

The post Second vSphere Client (HTML5) update in vSphere 6.5U1 appeared first on VMware vSphere Blog.

Source: VMware vSphere Blog

vSphere 6.5 Update 1 – Under the Hood

I’m excited to announce that vSphere 6.5 Update 1 is now available and it has some great enhancements. While we have seen 5 patch releases so far, 6.5 Update 1 rolls all of those updates together as well as includes some long awaited functionality. Without further ado, let’s take a look under the hood of this highly anticipated release!

General Updates and Enhancements

First and foremost, vSphere 6.5 Update 1 allows customers who are currently on vSphere 6.0 Update 3 to upgrade to vSphere 6.5 Update 1. All of the security and bug fixes that were part of 6.0 U3 are now included in 6.5 U1 whereas before, upgrading from 6.0 U3 to 6.5 prior to U1 would have put customers in a more risky position due to the timing of the releases. That concern is a thing of the past now, though, and we anticipate even more customers will begin their upgrade journeys.

vSphere 6.5 Update 1 Upgrade Path

Speaking of upgrades, it is important to note that customers who are still on vSphere 5.5 will need to be on at least vSphere 5.5 U3b in order to upgrade to vSphere 6.5 U1. This may mean a two-step process for some customers to get to vSphere 6.5 U1 but this is necessary in order to ensure the best possible outcome for the upgrade.

Another item that has been signaled for quite some time is the removal of 3rd party switch support. This means that customers using 3rd party virtual switches such as the IBM DVS 5000v, HPE 5900v, and Cisco Nexus 1000v will need to migrate off of those switches prior to upgrading to vSphere 6.5 U1. For more information on this you can visit https://kb.vmware.com/kb/2149722.

Many customers and home lab users like to use Mac hardware in order to virtualize macOS in an officially supported manner. I’m happy to announce that vSphere 6.5 Update 1 adds full support for ESXi on MacPro 6,1 hardware! So, if virtualizing macOS is your thing you can now do it on the latest hardware and without workarounds.

vCenter Server

There are some exciting enhancements to vCenter Server in this release as well. First, lets talk about scale numbers as that has been a frequent ask and challenge for some customers. In vSphere 6.5 Update 1 we’re increasing some of the maximums related to vSphere Domains (also known as SSO Domains). In this release we have a new maximums guide that can be found here: http://vmw.re/65u1max. Note that these maximums are specific to vSphere 6.5 Update 1 and are _not_ retroactive. vSphere 6.5 releases prior to Update 1 are still bound by the maximums published here: http://vmw.re/65max.

Here are some of the increased vSphere 6.5 Update 1 numbers:

  • Maximum vCenter Servers per vSphere Domain: 15 (increased from 10)
  • Maximum ESXi Hosts per vSphere Domain: 5000 (increased from 4000)
  • Maximum Powered On VMs per vSphere Domain: 50,000 (increased from 30,000)
  • Maximum Registered VMs per vSphere Domain: 70,000 (increased from 50,000)

Hopefully these new scale numbers are welcome improvements!

Another exciting improvement is full support for the vCenter Server Appliance installer on macOS Sierra (10.12). Due to the timing of the release of Sierra and vSphere 6.5, changes to Sierra’s security model were causing problems with the installer. I’m happy to say that the installer now works great on Sierra so no more workarounds required.

vSphere Client

The vSphere Client also sees a big leap forward in this release. We’ve added too much functionality to list, but we have focused more on host-centric operations. So Virtual Distributed Switch (VDS) management, datastore management, and host configuration are areas that have seen a big increase in functionality. This means that the vSphere Client now has about 90% of general workflows completed. We’re pushing hard towards 100%!

As a reminder, the vSphere Client can be accessed via https://<vcenterfqdn>/ui and it is completely built on HTML5, requires no plugins, and it lightning fast. If you’ve been following along with the Fling version, the version in vSphere 6.5 Update 1 is roughly equivalent (actually a bit newer) than the bits in v3.15 of the Fling. You can view the items that we’re still working on getting into the vSphere Client here. Dennis Lu, the Product Manager for the vSphere Client also has a blog with a few more details.

vSAN

vSAN 6.6.1 is also here and adds some exciting new capabilities involving vSAN and vSphere Update Manager (VUM). This new integration helps streamline and simplify vSphere upgrades on vSAN-enabled clusters by consulting several sources and recommending updates including firmware, drivers, and vSphere software. You can learn more about this new functionality in Pete Flecha’s blog over on the Virtual Blocks blog.

Getting Started with vSphere 6.5

vSphere 6.5 Update 1 includes some great new enhancements to an already solid release. Along with the enhancements above there are numerous bug fixes that should make your experience even better. If you’ve been waiting to upgrade to vSphere 6.5 then wait no longer! Please review the full release notes and I’d also recommend Emad’s blog series on upgrading to vSphere 6.5 if you need help getting started.

We also have a number of click-by-click walkthroughs that can help in the actual upgrade process. And don’t forget about the Hands On Labs if you want to kick the tires prior to your upgrade.

Happy upgrading!

The post vSphere 6.5 Update 1 – Under the Hood appeared first on VMware vSphere Blog.

Source: VMware vSphere Blog

VMware Announces General Availability of vSphere 6.5 Update 1

vSphere 6.5 Update 1 is the Update You’ve Been Looking For!

Today, VMware is excited to announce the general availability of vSphere 6.5 Update 1.  This is the first major update to the well-received vSphere 6.5 that was released in November of 2016.  With this update release, VMware builds upon the already robust industry-leading virtualization platform and further improves the IT experience for its customers.  vSphere 6.5 has now been running in production environments for over 8 months and many of the discovered issues have been fixed in patches and subsequently rolled into this release.  Many customers, including ACI Specialty Benefits, have already benefited from upgrading to vSphere 6.5 to help address the challenges of digital transformation. For customers who have yet to upgrade, vSphere 6.5 Update 1 serves as a validation milestone signaling to them product stability and that now the right time to upgrade.  For others, it will correspond with their natural upgrade cycle.  Regardless of the reason, if you are not yet on vSphere 6.5, you are missing out!

vSphere 6.5 focuses on 4 areas of innovation directly targeted at the challenges customers face as they digitally transform their businesses.

  • Simplified customer experience – Re-architected vCenter Server Appliance, streamlined HTML5-based GUI, and simple rest-based APIs for automation.
  • Comprehensive Built in Security – Policy-driven security at scale to secure data, infrastructure, and access.
  • Universal App Platform – A single platform to support any application, anywhere.
  • Proactive Data Center Management – Predictive analytics to address potential issues before they become serious problem.

A recap of key capabilities offered in vSphere 6.5 can be found here.

vSphere 6.5 Update 1 further refines vSphere 6.5 while also adding key additional support and enhancements including:

vSphere Client Now Supports 90% of General Workflows

The HTML5-based vSphere Client now can support up to 90% of general workflows.  This is welcomed news as VMware pushes towards 100% parity between the various clients.

vCenter Server Foundation Now Support 4 Hosts

In discussions with customers with smaller environments, VMware has received feedback that 3 host environments were too small in many cases.  If VMware vCenter Server Foundation could just support 1 additional host that would make all the difference.  This is why with vSphere 6.5 Update 1 VMware is now increasing the number of hosts that vCenter Server Foundation will support from 3 host to 4.

vSphere Support and Interoperability Across Ecosystems

VMware prides itself on having one of the broadest ecosystems across any industry.  As with any new product, at initial release, some partners were not ready with compatible versions of their products.  Many of these incompatibilities are now a thing of the past, as we have worked with our partners to test and ensure interoperability.  Furthermore, the ecosystem is also expanding as we forge new alliances to add vendor support for things such as Security Key Management and Proactive HA, to name a few.

vSphere 6.5 General Support Has Been Extended

VMware understands that upgrading infrastructure can be a lengthy process.   One consideration for whether or not to upgrade is how long the new product will be supported.  VMware wants to make the customer’s decision to upgrade easier by extending general support for vSphere 6.5 for a full 5 years.  This means that support for vSphere 6.5 will now end November 15, 2021.

Upgrade from vSphere 6.0 Update 3 Now Supported

Customers who are on vSphere 6.0 Update 3 now have a supported upgrade path to vSphere 6.5.

Preparing for the future

vSphere 6.5 Update 1, not only advances your IT initiatives today, but it also prepares your company for the future.  Customer interest for VMware Cloud on AWS has been soaring since it was announced just prior to VMworld EMEA.  While customers can’t use the product until it is generally available, they can take steps today to prepare their environment in anticipation for its availability.   To take full advantage of VMware Cloud on AWS and VMware’s cross-cloud architecture, customers will have to have vSphere 6.5 in their on-premises environment. So, while getting ready for VMware Cloud on AWS, why not prepare your on-prem environment today?

For more details on vSphere 6.5 and its capabilities, please visit the vSphere 6.5 Blog Series .

Additional Resources

The post VMware Announces General Availability of vSphere 6.5 Update 1 appeared first on VMware vSphere Blog.

Source: VMware vSphere Blog

Spork! An Open Source Fork Utensil

Recently at the Open Source Summit in Tokyo, I was on the kernel panel where someone asked us, “Why hasn’t Linux forked?” The entire panel looked at each other, sorta laughed and we all said the same thing:

“What do you mean? It has forked several times, and it is still forking!”

A Little History

The term “fork” in software is similar to a fork in the road: one base and two branches with that common base. Back in the ’80s, Unix was a popular alternative to the mainframe. Unix has its roots back to research done by MIT, Bell Labs and General Electric. In the 70s and 80s, Unix was used by several universities and was sold off to different commercial startups (AIX, Solaris, HP-UX, Xenix and more). Eventually, Unix had several different proprietary flavors. All were able to do mostly the same operations, but each had their own flavor and were not totally compatible with the other.

Eventually the different flavors (forks) of Unix created its downfall.

Unix was cheaper than a mainframe, but was much more expensive than a common PC. When a customer needed to use Unix, they needed to decided which fork to use, and that also usually meant lock-in to a specific vendor. One might believe that customer lock-in is good for the vendor, but this can have adverse effects. When another fork of Unix has a new feature that would benefit the customer better, they could not easily switch to that version; they may also depend on some feature of the fork of Unix they are currently using.

The different forks of Unix were always trying to add more value than their competitors. This split the user base. It also allowed for a much less expensive operating system that ran on the common PC to start to eat away at their market share. As the PC became more powerful, it became less of a need to use the hardware that Unix ran on. Customers started to move toward the cheaper alternative.

I was first introduced to Linux in 1996. That was also when I was first introduced to an open source license. The Linux distribution I was reading had a clause saying, “Most software licenses prevent you from sharing the applications. Our license encourages you to share.” That was quite a culture shock to me, as I have never heard of such a thing.

Now, open source licenses have been around much longer than Linux, but it was Linux that brought it to the mainstream. Linux was not a clone of Unix, although many people believed that it was and they believed it would suffer the same fate of Unix. Linux was not a fork of Unix. It was written from scratch, but it tried to implement the same Application Programming Interface (API) as Unix. People would incorrectly call Linux another Unix, because it looked the same. But it had a completely different code base and license, one that not only allowed the sharing of the code, but made it a requirement if you ever forked Linux and distributed it.

I would say that Linux started to become noticed by the industry in 1998.

Related: The Road to Real Time Linux

Linux & Open Source Forks

I was asked by the company I worked for at the time to give a presentation to explain Linux and this open source license. Several people told me at the time that Linux will suffer the same fate as Unix, as it allows for forks. I told them that forks will only make Linux stronger. The reason was that the forks can freely merge when, in a proprietary environment, that is prohibited.

In a proprietary environment, when you have a fork, each fork will try to give its own value-add and be unique from the rest. If one fork creates something that the others can’t, it will have an advantage. Those that are not locked into the other forks can move. But then the customers that are locked in will be at a disadvantage.

In an open source environment, when you have a fork, and one of the forks produces a great feature that beats the features of the other forks, their customers can ask for that feature. Since the code is freely available and free to use, the other forks can simply merge that code into its own fork and improve. In fact, whenever any fork improves the code, the other forks can take advantage of it, and all forks become a better project. As stated above, forks will only make Linux stronger.

Every Distribution Has its Own Fork of Linux

Sometimes, it takes forking Linux to prove that a feature is worth merging. If you can add a feature to Linux and get it accepted in one of the forks, you can show its usefulness as people will start asking for it. The Android phone uses its own forked Linux kernel. Several of the Android features came into the Linux mainline exactly because of this. Android was able to show that it had millions of users of a specific feature. That’s pretty convincing to get a feature into the Linux kernel.

The Linux kernel isn’t the only open source project that has examples of improvements via forks. The GNU C Compiler (gcc) had an instance where the developers disagreed on the future of the project, and the developers created a true fork. The two projects remained separate for years.

One would think that something like that would cause the project to fail. Eventually, the two found a common ground and merged back into a single project—one that was better than either of the two separate projects.

I like to think that open source does not fork, but instead it “sporks.”

Spork! An Open Source Fork Utensil

Image courtesy of Flickr user goblinbox: https://www.flickr.com.

If you know of the spork, it is a spoon and a fork combined as one, where it looks like a spoon with short prongs sticking out of the end. A true fork has prongs that stay separated all the way down to the base. This is true with proprietary software. When a fork occurs, it never merges back.

An open source fork, will only stay separated for a small duration, and then it merges back together that has more features (like a spork has the features of both a spoon and fork).

Forks are dangerous and can kill a proprietary project. But nothing has ever been killed by a spork.

Because you liked this blog:

The post Spork! An Open Source Fork Utensil appeared first on Open Source @VMware.

Source: Open Source @VMware

Learn about vSphere 6.5 at VMworld

Ever since VMware released vSphere 6.5 late last year, the response from customers has been overwhelming positive.  Customers have been especially excited by features such as enterprise-grade vCenter Server Appliance (VCSA), built-in encryption features, and a modern API set.  Now that people have learned about these new capabilities, we decided for this year’s VMworld to present breakout sessions that focus more on the operation aspects of vSphere 6.5, such as architecture, deployment, and planning your upgrade.  Of course, we still have a wide range of sessions covering such staple topics such as performance, troubleshooting, operations management, the new HTML5-based vSphere Client, PowerCLI, and more.

To help you plan your VMworld, we’ve put together a page that organizes all vSphere related sessions into topic areas and orders them by technical level.  By consulting the VMworld 2017 vSphere course catalog, you’ll be able to find the sessions that are of interest to you and add them to your schedule.  The list also includes Group Discussions, which are a great way to learn how your peers are using vSphere and provide feedback directly to product developers.  We’ve also include both VMworld US and VMworld Europe sessions in the same list.

For quick reference, you can find this catalog at blogs.vmware.com/vsphere/vmworld.

We look forward to seeing you, whether in Las Vegas or Barcelona!

The post Learn about vSphere 6.5 at VMworld appeared first on VMware vSphere Blog.

Source: VMware vSphere Blog

Integrating Log Insight Alerts into vSphere with Operations Management

vRealize Log Insight for vCenter is a fantastic utility on all on its own. However, when you combine it with the power of vSphere with Operations Management you really get some fireworks! Alerting is one of the areas where this dynamic combination shines. This happens to be because of Log Insight’s ability to take any query and send that data as an alert to vRealize Operations Manager!

Here is an example of what an alert sent from Log Insight to vRealize Operations Manager, which is included as part of vSphere with Operations Management, looks like:

vROps Alert View from Log Insight Integration

The above alert contains both information forwarded from Log Insight as well as some automatically integrated objects from vRealize Operations Manager. First, we can see that the alert was received from Log Insight and has detected an SSH session started on the given host. We can also see a custom description and recommendation, which happens to include sample links for both internal and external resources. Furthermore, in the symptoms section, there’s the actual source event for the alert. The event shows us additional information such as the IP address where the session originated and the exact timestamp for when it occurred. Lastly, the ‘More Information’ section can be used to further diagnose the object, within the respective areas, in vRealize Operations Manager.
Example: Clicking ‘View additional metrics’ would take us to the ‘All Metrics’ tab.

We will now walkthrough how these alerts can easily be setup in Log Insight.

Log Insight Alert Configuration

Log Insight alerts can be created against any event Log Insight receives. To keep it simple, we will repeat the process to create the example alert from the above section.

To begin creating an alert, we will first want to log into our Log Insight instance. From there, head over to the ‘Interactive Analytics’ tab.

Log Insight Interactive Analytics Dashboard

We will then want to search for the event of ‘sshd accepted’.
Note: The time frame may need to be modified to find events for the specific query. In this instance, I changed the timeframe to be ‘Latest 6 hours of data’.

Log Insight Event Query

These events returned have a specific event type ID. We will want to create a filter based on that specific ID. We do this to avoid any other events from potentially creating a false alert. To create the event filter, we will want to click the blue ‘event_type’ link. This pops out a menu where we can create a filter. We then select the ‘Events Like This’ within the ‘Add Filter’ section.

Log Insight Event Filter Creation

The view will refresh after adding the new filter based on the event type. At this point, we are ready to create the alert. Click on the ‘Alert’ icon (red bell) and then select the ‘Create Alert from Query’ option.

Log Insight Alert Creation from Query

We are now greeted with the ‘New Alert’ screen. Here we will customize the alert with things such as a new name, description, recommendations, as well as where and how often the alert should be sent.

Each setting can be filled in as follows:

  • Name: Here we will want to enter the desired alert name of ‘Host: SSH Session Started’
  • Description: Enter a description that makes sense, in this case we used ‘An ESXi host has started an SSH session. This action should be inspected as soon as possible”
  • Recommendation: This section can then be used to enter further information such as any instructions, web links to either internal or external URLs, and so forth.

NOTE: Clicking the blue ‘Edit’ link beneath each of the following sections will allow for a WYSIWYG (what you see is what you get) editor to allow for the inclusion of text formatting, web links, bullets, and numbered lists.

After populating those sections, we will want to focus on the ‘Notify’ area. Here we want to configure the alert to send the notification to vRealize Operations Manager. We do this by clicking the indicated checkbox.

Once checked, there are a few new configuration options available to us.

  • Failback Object: configures the alert for a specific item within vRealize Operations Manager
    • Example: Log Insight sees the object as an IP address while vRealize Operations Manager sees the object as a DNS name. The alert can be configure to point to the proper object.
  • Criticality: none, info, warning, immediate, and critical
  • Auto Cancel: cancels the alert automatically after 10 minutes

The last section we will want to configure is the ‘Raise an alert’ area. Here we can choose how Log Insight processes the initial alert and any additional alert. The option is to forward an alert to vRealize Operations Manager with every match, when a match is new for a set period of time, or if there are a specific number of matches found for a specific amount of time. In this example, we will leave the setting on the default of ‘On any match’.

Clicking ‘Save’ will then create the new alert!

Log Insight New Alert Creation

Alerts in vRealize Operations Manager

We have now created the alert, so we should take a look at how they look when in the vRealize Operations Manager console.

Here’s how the alert will show up in the ‘Recommended Actions’ dashboard:

Log Insight inside vR Ops Dashboard

If we click on the alert, we arrive at the alert page we viewed at the top of this post.

Summary

As shown above, combining the power of vSphere with Operations Management with Log Insight for vCenter allows for some terrific integration. This continues to make vSphere environment operations activities like discovery, diagnosis, and root cause analysis that much easier!

Download your free copy of vRealize Log Insight for vCenter today for use with vSphere with Operations Management!

The post Integrating Log Insight Alerts into vSphere with Operations Management appeared first on VMware vSphere Blog.

Source: VMware vSphere Blog

Exciting lineup of VMware Cloud on AWS sessions at VMworld 2017

VMworld is right around the corner and we have an exciting line up of VMware Cloud on AWS sessions! VMware Cloud on AWS will bring VMware’s enterprise class Software-Defined Data Center technologies to AWS, with seamless access to the broad portfolio of AWS offerings and is scheduled to be available in summer 2017.

VMware Cloud on AWS is built from industry-leading VMware vSphere®, VMware vSANTM and VMware NSX®, and is operated as a service. This service seamlessly integrates with existing customer datacenters already running on vSphere. Further, vSphere runs on elastic, bare-metal AWS infrastructure and the familiar vCenter Server management environment eliminates retraining staff that would normally be required to benefit from the public cloud.

With the schedule builder going live, we have compiled a list of VMware Cloud on AWS sessions featuring well known speakers from VMware and AWS including Frank Denneman, Paul Bockelman, Brian Graf, Emad Younis, Wen Yu, Principal Engineers Robert Bosch, Chris Wagner and many more!

Refer to the US content catalog and EU content catalog and start building your schedule now!

Sessions:

ID Title
Breakouts and Panel Discussions
US: LHC3159SU
EU: LHC1403BE
Accelerate the Hybrid Cloud with VMware Cloud on AWS
US: LHC1547BU
EU: LHC1547BE
Creating Your VMware Cloud on AWS Data Center: VMware Cloud on AWS Fundamentals
US: LHC2971BU Managing Your Hybrid Cloud with VMware Cloud on AWS
US: LHC3371BUS
EU: LHC3371BES
VMware Cloud on AWS – The Painless Path to Hybrid Cloud
US: LHC3174BU
EU: LHC3174BE
VMware Cloud on AWS: An Architectural and Operational Deep Dive
US: LHC2281BU Intriguing Integrations with VMware Cloud on AWS, EC2 and More
US: LHC3376BUS
EU: LHC3376BES
AWS Native Services Integration with VMware Cloud on AWS: Technical Deep Dive
US: LHC1910BU Using vRealize with VMware Cloud on AWS
US: LHC1882BU
EU: LHC1882BE
Service Overview for VMware Cloud on AWS
US: LHC2103BU NSX and VMware Cloud on AWS: Deep Dive
US: LHC3375BUS
EU: LHC3375BES
VMware Cloud on AWS Hybrid Cloud Architectural Deep Dive: Networking and Storage Best Practices
US: LHC1755BU
EU: LHC1755BE
VMware Cloud for AWS Storage and Availability: Keeping Your Bits Safe for Humanity
US: LHC1748BU VMware Cloud for AWS and the Art of Software-Defined Data Centers: API, CLI, and PowerShell
US: LHC2105BU
EU: LHC2105BE
NSX and VMware Cloud on AWS: The Path to Hybrid Cloud
US: LHC3016PU
EU: LHC3016PE
VMware Cloud on AWS: A View of the World from Our Customers
US: LHC3178BU
EU: LHC3178BE
Operating a Hybrid Environment with Hybrid Linked Mode and Content Library
US: LHC3175BU VMware Cloud on AWS Partner Solutions Showcase
US: LHC2386BU True Costs Savings – Modeling and Costing A Migration to VMware Cloud on AWS
US: LHC1158BU Architecture and Tooling for the Brownfield Hybrid Cloud
US: SER2283BU
EU: SER2283BE
Migrate to Cloud Securely While Optimizing Copy Data: vMotion Has You Covered
US: STO1890BU
EU: STO1890BE
VMware Cloud on AWS: Storage Deep Dive
US: STO3194BU
EU: STO3194BE
Protecting Virtual Machines in VMware Cloud on AWS
Group Discussions
US: LHC3177GU Securing Workloads on VMware Cloud on AWS
US: LHC3176GU
EU: LHC3176GE
VMware Cloud on AWS Ready: Preparing Your Environment for the Best VMware Cloud on AWS Experience!
Quick Talks
US: LHC2403QU Business Value of VMware Cloud on AWS
US: LHC3173QU VMware Cloud on AWS ISV Tech Program
HOL
US: ELW188701U
EU: ELW188701E
VMware Cloud on AWS Expert Led Workshop

The post Exciting lineup of VMware Cloud on AWS sessions at VMworld 2017 appeared first on VMware vSphere Blog.

Source: VMware vSphere Blog

VMworld 2017: Introducing the Digital Transformation Track

It’s almost VMworld time of year again! And this year, I’m excited to personally invite all who are now, or will someday be, leaders of IT to our newly introduced “Leading the Digital Transformation” track at this year’s show.

Led by VMware IT leaders, practitioners, and customers, the track has more than 30 sessions. They’re loaded with pragmatic guidance on topics like implementing a transformation strategy, modernizing the data center, integrating public clouds, empowering digital workspaces, and transforming security.

Given the current necessity to digitize businesses, the timing couldn’t be better. As technology evolves at light speed, so too should management. IT practitioners must begin to look at themselves as IT leaders of the future. Our goal is to prime these emerging leaders and inspire innovation.

Check some additional thoughts of mine on why empowering people is so important for the future of IT.

Take advantage of our Leading Digital Transformation Track to learn about how customers like you are building and executing strategies for transformation across cloud, mobility and security to meet their business goals.

Register now for VMworld U.S. 2017, August 27–31 in Las Vegas, or September 11–14 in Barcelona, and sign up today for an indispensable series of sessions created specifically for you as IT leaders.

/Bask

On Twitter: @baskiyer

The post VMworld 2017: Introducing the Digital Transformation Track appeared first on VMware CIO Exchange.

Source: VMware CIO Exchange

Big Data Video – Benefits of Virtualizing Big Data on vSphere

We often get questions from people who are new to big data about the reasons for virtualizing these newer infrastructures and applications. People are also interested in knowing the benefits you can gain from doing so. This video provides a set of answers to those questions. Summarizing the main points discussed in the video, the benefits you get when you decide to virtualize your big data infrastructure are:

(a) higher flexibility of management

(b) rapid provisioning of clusters through cloning

(c) freedom from dedicating groups of hardware to individual clusters

(d) performance that can equal that of native deployment and

(e) isolation of your workloads by grouping your virtual machines with resource pool boundaries.

Of course, virtualizing your big data workload also makes it ready for the cloud, as virtualization is the key technology underlying private or public clouds. The video concentrates on Spark as one example of a big data environment, but these principles apply to all distributed platforms, Hadoop and others, that support big data and analytics.

The video shows an outline architecture for a Spark-based system, which is growing very rapidly in the Hadoop market – and gives a short recipe for virtualizing that architecture.  You can learn much more about this subject by going to the VMware Big Data site

The post Big Data Video – Benefits of Virtualizing Big Data on vSphere appeared first on VMware vSphere Blog.

Source: VMware vSphere Blog