Wednesday, 20 May 2015

HP Cloud Service Automation - Part 1

HP Cloud Service Automation - Part 1


I've been working with HP OO & HP CSA as part of HP CloudSystem 8.1. They form an integral part of the Catalog function that tells Openstack and VMware what to produce. Understanding these components is crucial to developing a good Catalog but they are not easy products to get to grips with!

While you can deploy the whole CloudSystem suite to get at the contained OO / CSA products, they are also available as a separate bundled appliance for trial purposes.
http://www8.hp.com/us/en/software-solutions/server-automation-software/try-now.html

I've been lucky enough to get my hands on the windows versions and used a SQL database. I've taken some notes in case you head down this road that will save you some time:

HP OO 10.20 Deployed - SQL 2014 not currently supported so I tested with SQL 2012 without issue. The Database needs a few specific advanced settings:
ALLOW_SNAPSHOT_ISOLATION ON
READ_COMMITTED_SNAPSHOT ON
AUTO_CREATE_STATISTICS ON
AUTO_SHRINK OFF

Use only the following database collation for English:
English: SQL_Latin1_General_CP1_CS_AS

There was a patch for HP OO to 10.21 but it prevented me integrating CSA 4.2 and I'd to roll back. Just in case you want to try this for some reason (!) the upgrade is as follows:

Place extracted upgrade folder into the install path:
E:\Program Files\Hewlett-Packard\HP Operations Orchestration\upgrade\10.21.0001\bin
Run the apply-upgrade.bat as admin just in case and press y (there is also a rollback file if needed)

There is a community edition of HP OO which is free but limited to 100 flows a month but this will NOT integrate with CSA as I found out!

The HP Live Network below contains a link to the HP OO community edition
https://hpln.hp.com/group/operations-orchestration
The site above also has links to download updated content packs that you can import into HP OO. Or you can have some fun creating your own with OO Studio from CloudSystem!

Note: The trial version below seems to be that same community edition so try the appliance link at the top of this post above:
http://www8.hp.com/us/en/software-solutions/operations-orchestration-it-process-automation/try-now.html

I'm not sure the CSA windows software is available easily, it's easier for me to work with but again the appliance seems to bundle both OO & CSA but its Linux. From my deployment, I didn't install the feature .NET 3.51 before installing and the CSA portal worked fine but the Marketplace didn't. I did get an error about .Net being missing but the install completed anyway so after enabling this feature I uninstalled and reinstalled CSA and Marketplace started working fine.

The versions in CloudSystem 8.1 are HP Operations Orchestration 10.10 and Cloud Service Automation 4.10 for reference.

Currently HP OO is up to 10.21 and CSA 4.20 so the Windows versions and screenshots may look a bit different in later blogs.

So what use is HP OO & CSA without Openstack and the rest of CloudSystem? Well, it's still very useful software and was around long before CloudSystem took advantage of it. It can talk to Active Directory, Deploy VMs to Amazon Cloud, deploy applications and lots more. The licensing terms in CloudSystem need to be understood however so don't go running off and plugging it into anything - talk to your HP Sales Rep to understand how this operates in a Corporate setting. I'm just focused on learning for myself in a small Lab and by connecting CSA directly to VMware vCenter I can still request VMs and then mess with the Catalog settings to understand how the flows in OO work and see when they break. Using this I can get to understand items like:
  • Pricing
  • Approvals
  • Publishing
  • Look and Feel of different options (including documents and screenshots with offerings)
  • How to present choices to customers and reflect those choices in the VM that is built
  • Configure LDAP integration
  • Try different Providers and Content Packs and develop custom ones in OO Studio
  • How versioning works with Designs vs Offerings - when you have to start from scratch!
  • Changing options after a VM is deployed (Operational changes)
  • Topology vs Sequence Designer
These are just a few of the things I feel need to be understood when designing a good Catalog. The customer will of course have definite ideas also so you can start by building something basic, show it to the customer and then see how their operational experience shapes the solution. It may impact things such as:
  • VM naming conventions (VM name vs GUID shown in hypervisor which will confuse VMware admins if they haven't used Cloud systems before)
  • Choices for CPU, Ram, Disk, Network - how are these presented? How many options do you offer? How do you prevent someone choosing unreasonable virtual hardware?!
  • Do you have 1 VM per subscription or allow multiple instances, how does VM name generation work in that situation? Can you search for VM names easily in CSA afterwards when VMs are nested below single subscriptions?
There is a lot to decide in advance with Clouds, all the choices have to be carefully thought out. I hope to show some of those choices in later posts as it's the "meat & gravy" of a Cloud solution after the deployment is completed. Sometimes it's fun, other times frustrating but as you succeed in getting things to work it increases your confidence but remember that those skills may be product specific. Keeping Openstack & Hypervisor skills is very important as they are more likely to stand to you long-term as your career and experience develops.

One document I recommend you read is the concepts guide below:
https://docs.hpcloud.com/automation/
Try the link below but it may change as new versions are released:
http://support.openview.hp.com/selfsolve/document/KM01061671/binary/CSA_410_Concepts_Guide.pdf

So, there we leave it. I'll show you a basic catalog in the next post and the simpler options you can configure in CSA.



Monday, 18 May 2015

vCenter 6.0 C# Performance Overview Missing?!

vCenter 6.0 C# Performance Overview Missing?!

Just noticed something when I was on a call with a colleague and wanted to talk him through some performance spot checks. He was using vCenter 5.1, I was on vCenter 6.0. I went to view the performance information in the older C# client side by side when I noticed that the Overview option was missing. Remember the nice one that gave you a summary? Gone!! Vanished!!

Well, you've to head to the Web Client now it seems, it's there. To be expected but it would have been nicer if they left the old C# client views alone!! I'm sure you'll spot other things vanishing in the future as this client is left behind but that one surprised me!







Friday, 13 March 2015

VMware error: Could not fix soft vm/host affinity rule violation

The Cluster contains no hosts satisfying the soft VM/host affinity rules constraint for VM


I came across this error recently that baffled me for a few minutes. I've several DRS Rules which cover Stretched Cluster Datastore/Site Affinity to ensure Uniform configuration but also some Database specific ones to pin VMs that use Application level replication and don't need to move around as much. I had a few test VMs and two were affected:

I checked the Rules and everything seemed fine but then I remembered I had a problem with hung VMTool Upgrades and sure enough the two VMs had the issue. I manually ended the VMTools installation so it released the CDROM and ran the DRS job and both VMs migrated to where they should have been. As they were mounting Host specific ISOs they couldn't go anywhere until this was rectified.

Might help someone else out! I've since updated the VMTools in the Template where they came from the resolve once and for all!

Cheers
Michael.

Friday, 13 February 2015

CloudSystem Foundation 8.1 Active Directory integration

LDAP integration with CloudSystem Foundation 8.1


I've been struggling with LDAP integration with OneView and CloudSystem Foundation for a while but had some success with OneView recently and planned to crack CSF 8.1 also!

I took some time in the lab today to validate the error message I kept getting. Often with customer environments you have a number of restrictions which you never encounter in the PDFs you read, like all life is a Lab! At least in my lab I've control over users, groups etc so I can get it working and then gradually change things until it gets close to the Production environment I'm working with. The usual generic errors aren't helpful in diagnosing this but there are some logs that can help if you're stuck:

If you create & download the Foundation Appliance support dump and rename it .tar.gz you can open it with winzip or a similar tool to extract the following file:
/ci/logs/ciDebug.01.log
Then read through and check the time of the LDAP configuration error with the timestamp in the file for a pointer.

In my lab I used the following settings to get the LDAP to work:

The User you use and any Groups you want to configure have to be in the same OU. Great news for Production usage, you can't add in AD Users and grant them permissions, only Groups!!!

My Lab OU Structure I tested was :

OU=Cloud,OU=Users,OU=Lab,DC=lab,DC=local

Basically it's 3 levels deep and I've the following users & groups here:
Users: admintest, clouduser1 - admintest seems to need Domain Admin group membership if possible or you will run into trouble.
Groups: Cloud Users - clouduser1 is a member
The remaining settings are as follows:
Now you should be able to add in the group. If the admintest doesn't have Domain Admin rights this is where I get rejected until I assign membership to that user.

You should be allowed click Connect and search for that Group. You have to have the groups in the SAME OU however for this to work. Now when you log in you get the drop down option of the Domain and a member of the group can access the Foundation site, in my case clouduser1

Have Fun!

Edit 15/02/15:
I wondered if having a space in the OU name would make any difference or if quotes would be needed. I went back to my Lab today just to check this out:

OU=Bottom OU,OU=Middle OU,OU=Top OU,DC=lab,DC=local
I created a new cloudadmin2 account with Domain Admin privileges and a clouduser3 which was a member of the Cloud Test Users group. All three of these objects were located in the "Bottom OU". I modified the existing settings and was able to configure the new LDAP search path and add the Group. Clouduser3 could log in fine, clouduser1 and clouduser2 were no longer able to log in as they were not in the configured LDAP search path.

So - Results, spaces in the OU path name does not matter!

Update 13/03/15: Note: You need to use your CN to login which may be longer than your NT Logon - i.e. "Joe Soap" as opposed to jsoap etc. Check your Active Directory for the exact CN Attribute.

Sunday, 25 January 2015

CloudSystem Enterprise LDAP Integration

CloudSystem Enterprise LDAP Integration


I had a chance to play around with Organizations in CloudSystem Enteprise 8.1 and found the help and default values rather misleading and unhelpful for Active Directory Environment. I eventually captured the right values I was happy with and thought I'd share them here for reference as I'm going to have do this again someday!!

LDAP Server Information
Hostname: lab.local
Port: 389
Connection Security: SSL box unchecked
Base DN: DC=lab,DC=local
User ID (Full DN): CN=cloudsystem_service,OU=Service Accounts,DC=lab,DC=local
Password: XXXX
ReType Password: XXXX

LDAP Attributes:
User Email: mail
Group Membership: member
Manager Identifier: manager
Manager Identifier Value: dn
User Avatar: avatar

User Login Information:
User Name Attribute: sAMAccountName
User Search Base: OU=Department X Users,OU=Cloud Users
User Search Filter: sAMAccountName={0}
Search Option: Search Subtree Selected
Save first, then select Look Up User and put in username such as “jsoap” to validate

Access Control:
Add AD Group to Service Consumer Role
Enter a name for the group or organizational unit DN: CloudSystem Admins
Enter a group or organizational unit DN: CN=CloudSystem Admins,OU=Department X Groups,OU=Cloud Groups
Click Add / Update

I've still to add the Domain Controller SSL certs to the Java keystore and trust them to enable secure LDAP but otherwise the steps above work fine. I've still to test the email integration. Just need to find a lab server with 8 cores!! Hope this helps out anyone struggling with this area.

Use Sysinternals AD Explorer to connect and show the exact DN attributes to help you out! Available here:
https://technet.microsoft.com/en-ie/sysinternals/bb963907.aspx

Friday, 9 January 2015

OneView and Active Directory integration

OneView Active Directory Integration


Hi, busy today. I've been bashing my head around trying to get AD integration with OneView 1.10 working for weeks now! I kept getting the same old error:

"Cannot authenticate the server with the given credentials, search context and certificate.
Verify that the server is active and the user credentials, search context and certificate are correct."

Failed Configuration:


I got time to lab this today and after checking a few guides I decided to try a slightly different value for the second field below and use CN for it, and it worked! As this was not reflective of the Production Environment I was working on I backtracked and created a similar structure and tested that too.

Working Configuration:

Now I needed to reference an OU two levels down, if I try and JUST reference my OU's it fails but I can combine a few here and I know CN=Users works. So I used this:

Working Final Configuration:


Now I can make the Active Directory the default login option and add any group under the Lab OU. I only have two levels but if I ALSO add the sub OU Groups, I can't see any of the groups inside it so choose an OU one level up (CN=Users+OU=Lab) instead of (CN=Users+OU=Lab,OU=Groups) for this to work as shown above. Now you can search for groups under that structure and add them in with appropriate permissions.

I wish I had this post weeks ago!


HP iLO 4 - LDAP and SSL Certificate Implementation

HP iLO 4 - LDAP and SSL Certificate Implementation

I had the opportunity to integrate a BL460c Gen8 Blade running iLO 4 firmware version 2.00 this week with Active Directory and replace the default SSL certificate it uses. The Blade is integrated with OneView 1.10 also to make things more interesting!! I've captured the steps more or less below and though I'd share them as it can be quite frustrating sometimes to get these things to work from product to product and version to version. I can also look back at it myself and recall it for future work!

Replacing the Default SSL iLO Certificate


Firstly you need to edit the network settings in the iLO Configuration page (https iLO administration page, not the POST iLO configuration!).

Open OneView and browse to the Server Hardware section.

Under Hardware click on the iLO IPv4 address to log into the Server’s iLO
Under Overview / Information the iLO Hostname is using a logical serial number, this must be changed to the iLO FQDN before generating the Certificate Signing Request.

Click Network on the left, then iLO Dedicated Network Port

Click the IPv4 Tab and unselect the Enable DHCPv4 option so it and the 6 sub options are ALL deselected. For the Primary, Secondary & Tertiary DNS Server fields enter is appropriate values.
Click Submit

Select the SNTP Tab next and select “Propagate NTP or OA Time to Host” and choose the Primary Time Server as 10.35.80.1 for Telehouse or 10.33.80.1 for Knock. Select the Time Zone “Europe/London (GMT)” and Click Submit
 
 
Go to the General Tab and enter the iLO Subsystem Name (Host Name) and Domain Name as the example below shows:

iLO Subsystem Name (Host Name)
mylovelyilo
Domain Name
lab.local

Click Submit
Information,Overview,iLO Hostname value should now display mylovelyilo.lab.local
Refresh the Blade in OneView to see the Hostname FQDN change to the new value (This didn't always work for me but should update after replacing the SSL cert later I hope!)
The SSL Certificate Process is more straightforward ONCE you've fixed the iLO Hostname. Otherwise after you import the certificate file and reset you'll find the iLO has regenerated the default HP self signed certificate and you've to start over!
In the iLO Click Administration, Security. Click the SSL Certificate Tab. Click Customize Certificate. Under the Certificate Signing Request Information enter the required information based on the following example:

Country (C)
IE
State (ST)
Leinster
City or Locality (L)
Craggy Island
Organization Name (O)
Father Ted
Organizational Unit (OU)
Parochial House
Common Name (CN)
mylovelyilo.lab.local*

* This field will be pre-populated with correct iLO Hostname and does not need to be changed.

Click Generate CSR, wait a few minutes and Click it again and copy the CSR text to Notepad and save using the filename <ilo hostname>.csr and send it to your Certificate Authority.
Once the Certificate is issued, open the CER file and copy the text contents, in the iLO screen Click Import Certificate, paste the details and Click Import and reset the iLO. You can open the certificate to check the iLO Hostname is reflected in the certificate CN.
Refresh the Host in OneView and you should be there.
 
Active Directory Integration
This is bit more straightforward as you've already got the networking setup. One item to get ready in advance is you're only allowed a single Domain Controller entry so HP recommends asking that a DNS round Robin entry be created. This means you get an alias such as mylovelydcs.lab.local which returns one of two or four IP Addresses each time it's queried preventing a loss of service if one should go down. You can still get it with a local iLO account and I'd recommend leaving this option enabled but the AD integration is handy for auditing and tracking purposes.
You'll need an Advanced iLO License to use this feature and I'm sticking with the Schema-free directory integration option here which is much simpler.
Now, create a new AD Group for this purpose and add any users you want to have iLO access into this group. You need to get the LDAP value and SID - I recommend AD Explorer from Sysinternals for this purpose. You point it at your AD with a valid AD user account, search for the new group and copy the LDAP OU structure and SID from the tool.
Now in the iLO administration screen once more go to Administration, Security and Click the Directory Tab. Check the following values:
LDAP Directory Authentication: Use Directory Default Schema
Directory Server Address: <ip of DC for Lab or DNS Alias for round robin DC IPs for Production>
Directory Server LDAP Port: 636 (assumes you've certificates on your DCs or use 389 if in a lab only)
Directory User Context 1: OU=Administrative Users,OU=Testing Lab,DC=Lab,DC=Local
This OU is where the user accounts are all located in my example. If you've a few locations enter each one in turn to capture all the user account locations.
Click Apply Settings, then Click Administer Groups
Edit the default authenticated users group as some point to remove all their privileges as if left ANY AD user can log into iLO, even if they can't make any changes that's unnerving when I encountered this! Add in the AD group (Click New) you plan on using and assign all iLO permissions to it. You'll need the CN of the Group and I recommend adding the SID also. Now log out and test.
CN=iLO User Group,OU=Administrative Groups,OU=Testing Lab,DC=Lab,DC=Local
The SID Value might be:
S-1-6-21-2703213456-12345678910-10987654321-132456
That's it! iLO Configured. I might reset the iLO one more time to check the settings are held and refresh the OneView Server Hardware page of the server to make sure but that's you done!