vROps Management Pack for vCD – NOW Tenant App!

I recently did a blog on the Management Pack for vCD on vROps – great way of a vCD admin to manage their vCD solution.

VMware just released the vRealize Operation Tenant App for vCloud Director 1.0 – this now allows you to provide tenant access to their org/VDC and provide tenant-level metrics! Very excited about this.

What’s New?

  1. Tenant Admin specific views to enable Operations Management solving monitoring, troubleshooting and capacity planning use cases
  2. Provider Admin can pick and choose the tenants to whom access it to be provided
  3. Photon OS based Virtual appliance (OVA) for easier installation
  4. HTML5 Client based on VMWare Clarity

Get it here: https://marketplace.vmware.com/vsx/solutions/management-pack-for-vcloud-director

vCloud Usage Meter 3.6 Tips

I’ll be updating this post with things I learn about 3.6 as time progresses.

Change IP / Gateway / Hostname / DNS / Proxy Server

  1. This *could* be done within your standard Linux commands, however, Tomcat is running in the background and does require manipulations also.
  2. The recommended process is using a bash shell script named “vami_config_net” – this is under /opt/vmware/share/vami/
  3. Run the script from your console to get the menu:
  4. Pretty self-explanatory on what it requires after you select a sub-menu.

SSH and Root Logins

  1. SSHD is not started by default nor can you log in with the root credentials. IF it is required (by VMware Support), this is the process on enabling access.
  2. To enable root, edit /etc/ssh/sshd_config and look for line “PermitRootLogin” – change this from no to yes
  3. Then start (or restart) the sshd service – “service sshd restart/start”
  4. NOTE – This should be a TEMPORARY solution if you need to access the shell via root. Follow all security practices when possible!

Root account locked

  1. Yeah, don’t ask how I did this – but had to figure out the procedure on unlocking the root account.
  2. Simple instructions here on getting into the bash shell from GRUB – https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2147190
  3. From there, you’ll need to use the “pam_tally2” command to reset the lock on the root account.
  4. So… “pam_tally2 –user=root –reset”
  5. Ensure your path is set if it errors out: “export PATH=”/sbin:/usr/sbin:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin”

Migrating from vCloud Usage Meter 3.5 to 3.6

December 20th Update – this procedure works for upgrades to the newest version of Usage Meter 3.6.1. The migration process remains the same. 

With our new release of vCloud Usage Meter 3.6, I have several SP’s requesting the work effort for migrating from 3.5 to 3.6 Usage Meter. I am doing this in my lab environment and showing the steps required for the data migration.

Official Instructions: https://docs.vmware.com/en/vCloud-Usage-Meter/3.6/com.vmware.vcum.usersguide.doc/GUID-88DD4D6B-B357-46D5-A6B7-AC1EDB7F423E.html

Pre-requisites:

  1. Usage Meter 3.6 appliance stood up and IP’d – you do not need to point it to your Products (migration tool will take care of that)
  2. Snapshot BOTH UM appliances
  3. SSH turned on both 3.5 and 3.6 appliances.
  4. Timezone is the SAME on both appliances
  5. Under Manage -> Provider, ensure the Contract, Phone, Partner ID, Contract Number, and Site ID MATCH

Steps:

  1. SSH to both appliances as “usgmtr” – NOT root – this is to test to ensure I can log in successfully to both Usage Meter appliances.
  2. Run “migrateum <hostname-of-UM3.5>” on the new Usage Meter appliance.
  3. And if you forgot to SSH as the usgmtr account, you’ll get this!! 🙂
  4. OK, SSH now as usgmtr on the 3.6 appliance – running “migrateum usage35.corp.local”
  5. IF you met the pre-reqs above, you should get a confirmation screen like this:
  6. After confirming, you should see the copy operation start. I didn’t have much data on my UM instance, so this was pretty quick.
  7. Let’s log into the 3.6 instance….
  8. You’ll get the confirmation page again to accept the terms:
  9. Accept the certificate for any product (I had vROps pop up):
  10. vCD was not showing up for me also – I had to check the box “Show inactive” and Activate:
  11. What’s great is all of my Customers and Rules moved over…
  12. And previous Report data is there!

Once you verify everything looks good, DON’T FORGET TO REMOVE YOUR SNAPSHOTS!!!

Not a very tough migration – just ensure your 3.6 UM is configured exactly the same way as the 3.5 instance or the migration tool will error out.

Happy migrating!

vROps Management Pack for vCloud Director

This is a nice little jewel available in the VMware Solution Exchange – ability to monitor vCD objects and provide potential tenant integration for monitoring their org.

More info here: https://marketplace.vmware.com/vsx/solutions/management-pack-for-vcloud-director

To install it – it’s pretty easy:

  1. Download the PAK file
  2. Toggle to Administration -> Solutions in vROps
  3. Hit the + Button on Solution
  4. Select your PAK file and click Upload
  5.  
  6. Accept the EULA
  7. Let vROps do it’s thing – installing…
  8. Click Finish once it’s complete.
  9. Now find the Management Pack for vCloud Director under Solutions. Go ahead and click on the gear icon to configure your connection.
  10. Add your instance along with the Display Name, org you want to connect to, and credentials. Pretty similar to other connections. Note – ensure Auto Discovery is set to “True” if you want new objects to propagate to vROps!
  11. Test your connection – if successful, you should start seeing Data Receiving under the Collection Status
  12. Toggle over to Dashboards -> you will see several new vCD dashboard available from All Metrics, vApp Utilization, Alerts, etc.
  13. From here, one could provide tenant access to a specific dashboard and/or org from vROps that provides a vCD view.

Yet another great addition for vROps 6.6 – definitely check it out if you are a vCD user!

Installation Guide is here.