Tuesday, September 22, 2015

VMware vForum 2015 - Brazil



VMworld Americas and Europe are not the only events you can attend. VMware holds local events called vForum, where you can interact and listen from specialists about Cloud Management, optimization, real use cases, network and storage virtualization along with technical and business sessions.

On October 13th will be São Paulo – Brazil time , come and join this free one-day event that offers a unique opportunity. Ohh yes, you hear, it’s FREE !!

All you need to do is make your registration !!!

Bellow you can find vForums around the world

See you there !!!
 

Tuesday, September 15, 2015

VMware’s releases after VMworld 2015

Past week VMware released updates to a variety of products, the majority of them were driven by VMworld 2015 announcements while others carry compatibility enhancements, new features and even bug fixes.

I’ll highlight the features I think are the coolest ones, but you are welcome to read the full release notes.
I don’t expect you guys to read it all, but focus on the products you have deployed on your environment today. I’m sure you will find some great news…

This release of vCenter brings some security enhancements like, disabling support for SSLv3 and vCSA Kerberos authentication against AD supporting only AES256-CTS/AES128-CTS/RC4-HMAC encryption along with vSAN and Fault Tolerance compatibility.

The host ESXi leverage the same security enhancement listed for vCenter above, but the most commented feature seems to be the Stretch Cluster support with vSAN 6.0 U1.

That’s just amazing, Stretched Cluster support based on vSAN Datastores, how great is to protect your work load across two geographic locations ?!?
Also a welcome to branch officers all around the word is the ability to have vSAN clusters of only two nodes. Last but not least the integrated Health Check service that monitors your vSAN cluster for hardware compatibility, network configuration and operations.

That’s just a minor release to support some new endpoints as:
- OpenStack Juno
- vCloud Director 5.5.2
- Orchestrator 6.0.3
- vSphere 5.5 U3 and 6.0 U1
What about this minor new feature ?!?! The ability to disable snapshot for all users including business group managers and support users.

This release brings support to vSphere 6 along with NSX 6.1.4.
But more interesting is the feature of creating Organization Virtual Data Centers Templates that can be offered on a self-service basis.

SRM 6.1 is aligned with vSphere 6.0 U1 support, but it also debuts the storage policy base protection, protecting VMs based on their policies and not their underling datastores.

Along with some UI enhancements to provide more simplified wizard the greatest news is the 5 minutes RPO (only when you have both source and destination vSAN datastores).

This release of VIO comes with Kilo release, the last one for Openstack and also the capability of upgrade roll-back in case of anything goes wrong. Load Balance as a Service with Neutron service has been add to this release as well. Resource Measurement and utilization has been added as TechPreview based on Ceilometer service. Auto Scaling service through Heat is also there, nice, right ?!?

I think the most notable news here is that Hyperic functionality is built in on vROps core product, meaning you don’t need to deploy and configure the Hyperic Appliance anymore, but you still need to install the agent on the VMs you want to monitor.

With more than 20 bug fixes this release focus on stability and reliability, check the list of fixes, it might has one that will solve a problem on your environment.

The price and details of deleted VMs can now be viewed on the current month. Another feature is the capability of mapping business units to vRA Tenant Administrator.

This version on Log insight was focus more on scalability, supporting now two times more ingest data per second, 15.000 events per second per node and the number of nodes per cluster has doubled, this is huge.

New extensibilities over here, invoke published Blueprints from release pipeline and Code Stream plug-in for Jenkins continuous integration dashboard have been added..

Microsoft Windows 10 support as host as long as a guest operation system. Support for USB 3.0 redirect and Microsoft DirectX10 support are just a sample of the Horizon Flex features.

Hard to download all these new releases ? Take a look at VMware Software Manager...

Friday, September 11, 2015

Big Data Extension – The Basics

Do you know that 90% of the world’s data has been produced in the past two years ? That’s an impressive number, right ?!

 

Companies of all sizes understand that there are opportunities to enhance their customer relationships, product quality and to understand trends through analyzing this huge amount of data (that’s why the term “Big Data”). The problem is that many of those data sources are unstructured data that cannot be analyzed with traditional tools. For instance the data can be in form of text, video, images, social medias, you name it.

 

Driven by this challenge, a new application platform has been born, Hadoop.              In a nutshell, this platform uses a divide and conquers approach, using distributed components to allow the processing of large amount of data. 

 

The main roles within Haddop 1.0 architecture are:

NameNodes: in charge of managing the Hadoop File System namespace (HDFS) and data block placement;

DataNodes: are the ones storing the data and retrieving them when necessary, you can scale the nodes to storage more data and provide data resiliency;

JobTracker: Jobs are submitted to JobTracker, which splits the job into tasks and send them to the TaskTracker for execution, controlling and scheduling the jobs execution;

TaskTracker: runs on each worker node, processing the tasks and requesting the data results from the DataNodes.

 

This architecture had some scalability and efficiency problems, that’s why an architectural change has been made with Hadoop 2.0; The main architectural change was the split of JobTracker functionalities into two new roles: 

 

ResourceManager: is now in charge of tracking resource usage, node liveness, enforces allocation invariants and contention among tenants;

ApplicationMaster: is responsible for coordinating job execution plans, requesting resources from the ResourceManager and coordinating the execution of tasks.

 

Of course there's more about the architecture and how it works behind the scenes, if you want to know more here's a good paper to digest

 

As you could imagine creating those Hadoop clusters, with dozens of nodes, followed by installation and configuration of the application on each one, takes a lot of time !! That’s where VMware comes into play.

 

VMware vSphere Big Data Extensions (BDE), is the VMware’s solution to the problems of managing and deploying Hadoop efficiently and in an agile way. No matter how complex your Hadoop solution could be, BDE can deploy it,  automating the nodes creation, application installation and configuration in a much shorter time than the traditional way, saving you hours if not days of manual tasks.


To make it even better, BDE can work with the distribution of your taste: Apache Hadoop, Cloudera, Pivotal, Hortonworks and MapR.

 


Now that we know the basics of BDE, we are ready to explore more advanced topics:

- Hadoop default template password

- Graphical Interface vs command line

- Managing Disks and Controller Types

- Topology Matters

 

 Coming Soon

- IP Allocation and Name resolution

 

Tuesday, September 1, 2015

vSphere Fault Tolerance - Redundant Storage


vSphere Fault Tolerance (FT), one of the most cool and less implemented feature of VMware vSphere had a significant improvement on vSphere 6, at this point you probably know what FT is about, just in case you don’t know yet, here’s a brief explanation: 

FT is a feature that enables you to protect your mission critical applications creating a secondary VM and keep them synchronized, so in case of a failure of the primary VM the secondary VM will take place almost instantly. Cool right ?!?

 

Problem was, until vSphere 5.5, you could only protect VMs with a single vCPU !!! Good luck finding a mission critical VM running with a single vCPU.

As you could imagine, support for multiple vCPUs VM has been asked for years and finally on vSphere 6 it’s now possible.

But this post is not to talk about FT on multiple vCPUs, there is a bunch of blogs about it already, I wanna talk about another new resource of FT, Redundant Storage.

Now with vSphere 6 you have the option to also replicate the data to another datastore, eliminating the single point of failure that datastores has been being so far.

 

 FT will create a secondary copy of vmdk, vmx and the Tie Breaker file on a separate datastore and keep the data synchronized between them, so in case of a datastore failure the secondary VM will take place without any problem.

 

There's not trick to use it, just Turn On Fault Tolerance on the VM.

 

 

Then browse for the datastore where will want to place each file.


FT is a precious and limited resource, be aware of it’s limitation of 4 VMs per host or 8 vCPUs, on this sum take into account primary and secondary VMs.

 

Are you willing to use FT more often now ???

 

Who am I

My photo
I’m an IT specialist with over 15 years of experience, working from IT infrastructure to management products, troubleshooting and project management skills from medium to large environments. Nowadays I'm working for VMware as a Consulting Architect, helping customers to embrace the Cloud Era and make them successfully on their journey. Despite the fact I'm a VMware employee these postings reflect my own opinion and do not represents VMware's position, strategies or opinions.

Most Viewed Posts

Blog Archive