HPE Verity
June 8th, 2016 by NerdBlurt

Last week Hewlett Packard Enterprise announced HPE Verity. Now I work for HPE in the business unit and am responsible for the social media. To me it is exciting to see the behind the scenes of what happens when you are launching a product or an update with new features, to be able to finally talk about something you have known about for months. Today is that day I get to talk to you about HPE Verity.

What is HPE VeHPE Verityrity?

HPE Verity is a next-generation, unified IM&G framework that provides a single source of truth

  • Information management & governance applications and services are integrated within a common framework.
  • Built on a SaaS architecture it can be deployed in virtually any geography to support data sovereignty requirements
  • With native, in-place analytics information is not moved from application to application but is available directly within Verity

HPE Verity’s set of applications and services will uniquely help organizations comprehensively manage, govern, and extract actionable insights from enterprise information.

So really what you are looking at is the start of what HPE is touting it’s Next-Gen Information and Governance framework, the stepping stone to many new products. Now working for the group I have insider knowledge and the greater vision but I like paying my bills so I will only talk about what I can when I can.

In a session during HPE Discover the company’s Semi-annual conference David Jones and Stephen Spellicy gave folks a closer look at HPE Verity. You can read a recap of that session here

Nerd’s Blurt

I am excited for for is to come! I will also be writing some more posts hopefully on here on some of the things I am learning about in the information governance space. I am going to stop here now as I want to write up a quick day one recap of HPE Discover from Las Vegas.

I would also like to note I wrote this on my own as HPE is my employer this is my blog and any writing on here is solely my own opinion or that of any guest writers.

Posted in Tech Tagged with: , , , , , , , , , , ,

May 7th, 2015 by JFrappier

Jonathan Frappier Virtxpert

**Disclaimer: I am an EMC employee, this post was not sponsored or in any way required by my employer, it is my experience getting to know this particular product.**

Up until now I went through a basic ViPR SRM installation, getting a basic single VM environment setup. What I want to show in this post is my favorite ViPR SRM feature – topology maps. To understand why these are useful, lets step back and give some scenarios:

You are the personal responsible for supporting the storage within your environment, you may support other things but ultimately when there is a storage related problem your name is called. An application own comes to you and says their application is slow, and that the network team said everything on their end is fine so its probably the storage. Great – now what?

  1. You come into a new organization – whether as an internal IT person or a var and you’ve inherited an environment cabled by 3 monkeys and a cat with no documentation – now what?

This is where topology maps can be very useful. The topology maps is that end-to-end visualization and monitoring component I mentioned in previous posts. I see from my virtual machine or even some applications such as SQL Server all the way through to the underlying storage, and drill down on each component. Let me shows you some examples.

To access the topology maps, click on Explore >> Hosts – small aside here – host could be any physical or virtual server in the environment discovered by ViPR SRM, not just ESXi hosts. So this could be an ESXi host, a virtual machine, or a physical host running its own OS.

vipr-srm-explore-reports-hosts

From this report, you can see a list of all the hosts in the environment, which for some could be a very extensive list. I should mention that the filter field is not a search field, so you cannot type the end of a machine name; for example maybe all your VM names end in OS type or some other identifier, you couldn’t just type W2K8 to find a server name myserver-w2k8, you would have to start with myserver, but would then see a list of all servers starting with that string. You can filter on any column that has the funnel icon, so for example I could filter on just physical hosts, or virtual machines by clicking the funnel icon in the host type column;

vipr-srm-filter

Using the example above, let’s say an application owner has complained about performance and you need to investigate to see if storage could be the problem. Filter on the host name, in this case I will pick on mhmbd078-W2K8, as you can see below I start typing that name and can select it from a the list or type it in full and hit enter to filter on that one host

vipr-srm-filter-hostname

 

Now I just see that specific host, in this case a virtual machine as you can see here with 16GB of memory and 4 vCPU:

vipr-srm-single-host-explore

This much information is available in just a few clicks, now there are many places you could get this information but as I continue to drill deeper, you will start to see just how much information we have at hand. With just what is available so far, you might be able to say to the application owner who issued the complain that there is not enough memory, for example maybe you know that this particular application needs 32GB of memory, so disk I/O could be a problem if the application and OS are constantly swapping to disk. But, maybe so far everything checks out, if I click on any of the text here, it will take me into the detail of that virtual machine.

Now, this is where it gets interesting; what you see below is the topology map for mbmbd078-w2k8, we can see the host, the datastore it is on, the host it is on, the VSANs it is connected to and the arrays connected to those VSANs. Also, notice to the right we have different reports related to the host, we can see attributes about the host which is show by default, you can also see:

  • Capacity information about the hosts local disks, in this case VMDKs and since it is a virtual machine, the datastore
  • Path details for the disks attached to the host
  • Related storage performance
  • Events related to the host

vipr-srm-topology-map

You can click on any element in the map to see details specific to that item, for example if you click on the datastore – DS_Bootcamp_D you can see reports about the datastore, or on the host – you guessed it, reports about the host. You may have also noticed the + icon next to some of the elements, this is because there are additional components, using VSAN0040 as an example, we can click on the + sign to see switches in that VSAN

vipr-srm-exapanded-element

Now I see two switches, each with their own + icon, I can keep drilling down and see ports on that switch as well. I can expand different elements and hover over different components to see how they are connected. For example I have expanded my host to see my HBAs, I can see that the particular HBA I am interested in is connected to VSAN mptb023 so I have expanded that as well and drilled down to see the switch ports. While I have some limited lab resolution available, you can see here that when I hover over the HBA from the host it highlights the path to the port on the switch – in this case fc1/6 (as shown by the blue highlighted line)

vipr-srm-show-details

This is just one specific report, and I have only skimmed the surface of the data available in this report. Imagine being able to show this to an application owner as you troubleshoot each component, and explain how/why any particular piece of the infrastructure supporting the application is, or isn’t doing what it is supposed to. For those folks who worked in a silo’d type group, I’d urge you not use this information to punt back over your wall to someone else, but rather be the person to start poking some pinholes in the silo, call up a virtualization, OS, or network person depending on what you might think the problem is and work with them, sharing knowledge and help the application owner be a happy customer. After all, even if you are “internal” IT – you are still providing a service to the business – they are you customers, treat them like it. Silos will only fall if someone starts poking holes, no reason it can’t be you.

If you haven’t done so, chat with your EMC rep (they can likey get you in touch with an SE who can help if you have any setup questions) and head over to support.emc.com to sign up for an account and download ViPR SRM which comes with a 30 day license.

ViPR SRM Explore Reports and Topology Maps

Posted in Tech Tagged with: , , , , , , , , , , , , , , , ,

May 7th, 2015 by JFrappier

Jonathan Frappier Virtxpert

**Disclaimer: I am an EMC employee, this post was not sponsored or in any way required by my employer, it is my experience getting to know this particular product.**

There were two software related announcements at EMC World this week which I found very exciting. Building on the free for no production use of RecoverPoint for Virtual Machines from VMworld 2014, EMC announced the same for ScaleIO. ScaleIO allows you build your own Hyperconverged Infrastructure solution (HCI). This is the same software used in the new VxRack from VCE which was also announced at EMC World.

CoprHDIn addition to ScaleIO, EMC also announced CoprHD which is an open source version of EMC ViPR (@coprhd). ViPR (which is also free for non production use) is a solution that allows you to manage multiple arrays and present those as virtual volumes to hosts. In addition to managing the arrays, it also provides a self-service and automation at the storage layer. EMC ViPR also supports ScaleIO, assuming this carries over to CoprHD you could deploy a fully managed, and automated storage solution on commodity hardware for test/dev or QA (I hope they publish more specific guidelines on just what they mean by “non-production”).

Last, but not least, the community version of the VNXe which you can use to provide full block and file servers on commodity hardware. The vVNX will later come in a supported ROBO and cloud edition.

My hope is that CoprHD, ScaleIO, and the community edition of the vVNX will lead to more solutions being open sourced and offered in a free to use model. CoprHD should be available on GitHub by June, ScaleIO by the end of May, whereas the vVNX is available now for download.

 

New free software from EMC to build your own SDS solution

Posted in Tech Tagged with: , , , , , , , , , , , , , , , , , , , , , , , , ,

April 23rd, 2015 by JFrappier

Jonathan Frappier Virtxpert

**Disclaimer: I am an EMC employee, this post was not sponsored or in any way required by my employer, it is my experience getting to know this particular product.**

One of the upcoming tools I will be working with is ViPR SRM. ViPR SRM is a storage management tool that allows for monitoring the end-to-end health of your environment. I know what you’re thinking, “C’mon now Frapp that sounds awfully marketingy” and you’re right – it does, BUT let me give you an example of why some of the tools in ViPR SRM interest me.

network-is-fineHave you ever went over to a friends cube to chat and they say the app it ain’t no good? The reports are slow, the app keeps crashing, and the chicken taste like wood. Okay, but seriously how many times has someone walked over and said “my application is slow/down/broken” with no further detail, leaving it up to you to isolate what is going on? It has happened to me often. Worse is when you are the personal responsible for storage and someone else responsible for networking does the Jedi hand wave and says the network is fine, it must be storage.

 

That is where ViPR SRM comes it, it can show you the relation from virtual machine, through the hypervisor, datastore, data path to the storage array hosting the virtual machine. Further, for heterogeneous it supports multiple types of applications, operating systems, hypervisors and storage arrays. Of course it supports more EMC products, since it is an EMC product but you don’t necessarily have to run an EMC array to leverage ViPR SRM.

Below are some of the systems supported by ViPR SRM, an updated list can always be found at emc.com.

vipr

While getting ready for the installation, know that you can deploy as either a pre-packed vApp or install the application on 64-bit versions of RedHat, CentOS, SUSE, or Windows; during my post I will be deploying the vApp version which includes 4 virtual machines. The 4 virtual machines each have unique roles as a typical multi-tier application would – there is a web front end for UI and reporting, database backend for storing data, and collector for, well, collecting data. In large environments with multiple arrays you may deploy multiple collectors.

vipr-srm-components

In my next few blog posts I’ll be reviewing the installation of ViPR SRM, and review some of the dashboards and how they might help you in the day to day monitoring, and troubleshooting of your environment. If you’d like to learn along with me check out the ViPR SRM free e-Learning on ECN.

Getting to know ViPR SRM

Posted in Tech Tagged with: , , , , , , , , , , , , ,

April 23rd, 2015 by JFrappier

Jonathan Frappier Virtxpert

*Disclaimer: I am an EMC employee, this post was not sponsored or in any way required by my employer, it is my experience getting to know this particular product.**

In my last ViPR SRM post, I introduced you to some of the features if you were not already aware of them. In this post, I will look at installing ViPR SRM 6.5.2. I downloaded ViPR SRM from support.emc.com; while I am an EMC employee, I logged into the support site with my personal email account to download the files. Once logged in, search for ViPR SRM and click on the downloads menu, as I mentioned I will be going with the vApp option versus a binary installation.

vipr-srm-search-support

Once downloaded, extract the content of the zip file – you’ll have 2 OVF’s. One is the 4 VM vApp I mentioned in my last post, the other, a 1VM vApp useful for lab and evaluation purposes. Given I have limited resources in my home lab, I will be deploying the 1 VM vApp.

info

Important note here, you will need to deploy the OVF to vCenter, not a stand-alone ESXi host as some of the OVF properties will not be exposed properly, causing the deployment to fail.

Follow the OVF deployment wizard, when prompted select the All-In-One configuration:

vipr-srm-all-in-one-ovf

By default, the VM deploys with 4 vCPU – adjust according to your lab, I have set mine to 2, 16GB RAM and removed the reservation (performance here would not be ideal obviously, but this is for lab purposes only). Once the OVF has been deployed, you should be able to log into http://:58080/APG. Login as admin/change me to access ViPR SRM.

vipr-srm-UI

sadfsadf

By default, you are in the “User” interface, if you click on “Administration” in the upper right corner, you will go to the administration screen. Go ahead and click on Administration >> Centralized Management (on the left nav menu) >> License Management (also on the left nav menu). As you can see you have a 30 day trial license to test out ViPR SRM.

vipr-srm-trial-license

Close the license window/tab. Notice where the “Administration” menu was, you now see a “User Interface” menu, this will (like the administration link did) take you to the User interface (where you initially landed when you logged in.

In the next post, I will look at connecting ViPR SRM to vCenter and, in my case, XtremIO.

Installing ViPR SRM

Posted in Tech Tagged with: , , , , , , , , , , , , ,