Virtualisation with vCloud-Director and...
Transcript of Virtualisation with vCloud-Director and...
Virtualisation with vCloud-Director and HP-ALM
Markus Lobreyer
Status 20.06.2013
QK-Engineering
Seite 2
Speaker
Markus Lobreyer is Senior Test Engineer in the Quality Control domain at
Haufe-Lexware in Freiburg
He is responsible for topics such as test environment virtualization, PLS tests
(performance, load and stress tests) and is the deputy team leader in QC
Engineering.
Contact information:
Markus Lobreyer
Haufe-Lexware GmbH & Co. KG
Munzinger Str. 9
79111 Freiburg
Telephone +49 761 898-5839
E-Mail [email protected]
Web http://www.haufe-lexware.com/
Seite 3
Organization Chart
Seite 4
Agenda
vCloud-Directory (VMWare)
vCloud - ALM Connector
How to use the new Functionality
Next Steps
Discussion and Questions
vCloud Director VMWare
Seite 6
VMWare vCloud-Director Advantages
It provides virtual test environments for qualitycontrol, development and requirements-
management
About 160 standard images as templates for the different operating systems XP, Vista,
Win 7, Win 8 with or without MS Office
Self service web portal for all SWD employees (take the MSDN licensing rules into
account!)
Network configuration with multiple, serperate clients can be controlled from one
workplace
Browser access to the systems (IE or Firefox), respectively RDP (Remote Desktop)
Easily made available: A user can clone and start his individual machine within a couple
of minutes
Daily provision of actual product installations from the TFS build process
Seite 7
vCloud Director – Management Interface
Console
Start
Pause
Stop
Collaborate
Copy
Add to catalogue
Properties
e.g.: Lease Time
Link to the vCloud-Director: https://10.12.101.161/cloud/org/QA/
Seite 8
About 50 automatic product installations per day
Nightly-Build on the TFS build server
vCloud Directory
Each morning, the user can find pre-installed products on virtual machines (Win 7 and Win XP).
Installation via VMware vCloud API
Seite 9
Manual and further information in Sharepoint
Access through Sharepoint http://mylexware/bereiche/pe/QS/virtualisierung/default.aspx
Up-to-date documents and learning material
Responsibilities and contact persons
Newest FAQs
Links towards further information
vCloud-ALM Connector
Seite 11
Usecases - Virtualization
Earlier (before the virtualization)
Setup from „nightly build“ on the network directory technical test
starts
Tester installs the setup locally on the test machine
Tester performs a smoke test on his local installation
03:00 hours 08:00 hours 09:00 hours 08:30 hours
Setup from „nightly build“ on the network directory technical test
starts
Automated installation and central smoke test
Tester installs the setup locally on the test machine
Setup from „nightly build“ on the network directory technical test
starts
Automated installation and central smoke test
AND automatic deployment on
virtualtest machine
03:00 hours 08:00 hours 09:00 hours 08:30 hours
After virtualization
Seite 12
Starting position
Over 100 nightly Product Installations
Test Engineer
Seite 13
Only ONE integrated
environment for everything
(ALM)
Automated tests use
the image farm of
the virtual environment
Test Engineer
Rough Requirements
Request the needed image from ALM
Automatic Execution the scripts after the nightly installation
UC 1
UC 2
Over 100 nightly Product Installations
Implementation
Seite 15
Technical Implementation - API functions
ALM
API
vCloud
Nico
Seite 16
Technical Implementation – Schedule Server Task Scheduler
Database
vCloud
HP-UFT
HP-ALM
Result
Test planing
When?
Task Scheduler Server
vCloud Operations in ALM
Seite 18
How to enable vCloud operations in a HP ALM Test Set
To execute a test with the vCloud the user field “Testplatform” has to be changed to “vCloud”
Seite 19
How to enable vCloud operations in a HP ALM Test Set
Manage Tasks
Select vApp template
Start vApp
Seite 20
vCloud operations: Select vApp Template
1. vCloud
Authentication
2. Loading vCloud
Information
3. Select vApp
Template
4. Click Add-
Button
Seite 21
vCloud operations: Start vApp
1. Click “Start
vApp”-Button
2. Click “OK”- Button
3. “Deploy vApp”-
Dialog appears
4. With the button
“Remote exec.”
you can establish
an RDP-
connection to the
vApp
Seite 22
vCloud operations: Manage Tasks
1. Click “Manage
Tasks”-Button
2. The “Create Task
Wizard” appears
3. Select the
execution time and
date
4. Select User for test
execution
5. Click the “Finish”-
Button
Seite 23
Run a test-set on a vApp
1. Click the “Run Test
Set” button
2. Click “Yes” to
deploy a vApp
3. The automatic
Runner appears
with the IP address
of the deployed
machine
4. Click the “Run” or
“Run All” - Button
Next Steps
Seite 25
Next Steps
30.06.2013 Complete the implementation of the vCloud-ALM-Connector
01.07.2013 Acceptancetest of the extended ALM functionality with selected users
01.08.2013 Evaluation of the test phase and decision on the roll-out of the new
functionality
Release the new functionality with ALM 11.50 and vCloud 5.1 an training of the
users
The release-date will be announced in time
Discussion and Questions
Seite 27
Thank You!
Contact information:
Markus Lobreyer
Haufe-Lexware GmbH & Co. KG
Munzinger Str. 9
79111 Freiburg
Tel. +49 761 898-5839
E-Mail: [email protected]
Web: http://www.haufe-lexware.com/
Backup
Challenges
Seite 30
Challenges
How the scheduled automated tests are executed?
Which user data is user for the login in the vCloud?
Problem: The users use different login data in the ALM and virtualization environment
How can we store the user information so that we enable a cost calculation related to the use in projects?
Limiting the vCloud vApp selection possibilities in ALM (so that only the vApps that are
relevant for a certain project are selectable)
The IP address of the vApp in the vCloud is only known at runtime.
It can’t be entered by the use when he’s planing the test task.
The version number of the build (TFS-Nightly Build) is not known the previous day.
This means the system needs to search for the latest installed productversion
Seite 31
Technical Implementation - API functions/accesses
All the methods that are addressed through the vCloud API are implemented in a COM
component
This COM component needs to be installed on each local client which wants to use the
functionallity
It’s possible to install the component interactive or over netinstall
If the component is missing, the system will encounter the following error message:
Seite 32
vCloud Directory System Architecture
vCloud Directory
Data center VG2
vCloud Directory 1.5
vCloud Directory 5.1
Network
Haufe Group workspaces
Storage 7TB
Storage 8TB
Seite 33
Projects and Products in the Quality Control
About 1000 different software products (desktop, web, mobile) in the product range
About 50 running projects in HP ALM
About 400 registered ALM users
About 90 simultaneous users in ALM (internal and external)
About 600 standard images in the virtual test environment
Over 100 nightly product installations (desktop products) in the virtual test environment
Seite 34
Usecases – ALM Integration
Before the Integration of ALM Virtualization
After Integration
Tester Login ALM Login vCloud Search for Image
Connect to Image Start ALM tests
Tester Login ALM Start tests in ALM
Automatic login in vCloud
Automatic start of the image Automatic RDP
connection with image
UC 1
UC 2
Seite 35
Improvements and requirements in the IT ticket system
Access via the IT ticket system http://myhmg/mysupport/default.aspx
Category: Select “Rund um SWD-Virtualisierungsumgebung und TFS”
Topic: Select the SWD-Virtualisierungsumgebung
Fill in the fields and send the ticket
The workflow is analogue to other IT tickets
Seite 36
Technical Implementation - UI Adaptations
In the ALM module Test-Plan, we added information fields for describing the test
environment of the test-cases
In the ALM module Test-Lab, we have added the dialog to select the vApp from the
vCloud
In the test-lab we added the Buttons for „Select vApp Template“, „Start vApp“ and
„Manage Tasks“
We built a wizard in ALM to schedule the automated tests
We added Tabs for “vCloud Automation”, “TLC Filter criteria” and “vCloud
Automation log”
Seite 37
Technical Implementation – Schedule Server
Tasks for the time-controlled administration/start of automatic scripts are created
by using a wizard.
The task administration runs on a separate (scheduler) machine in a unique
database
The scheduler machine then carries out the tests from ALM and starts the
corresponding machine in vCloud
Seite 38
Technical Implementation – ALM-DB expanded
The implementation is done by using the current REST API of the VMWare vCloud
Directory Version 5.1
The accesses on the vCloud are documented in the memo field „vApp Automation
Log“, which is part of each test set in ALM
The ID of the created vApp is stored in the „vApp-ID“ field of the ALM test set.
This makes it usable through the following functionalities, such as the VAPI-XP-Test
for stopping the vApp.
Seite 39
Technical Implementation - Basic Functionality
HP ALM - vCloud connection assures the following operations
User login and logout
Access to organisation structures and catalogues (read-only)
Find an image in the catalogue by searching for its name
Deploy and start an vApp from the catalogue
Shutdown the vApp
Delete an vApp to release the resources
New templates for virtual machines are requested in the existing workflow through the
IT-Ticketsystem
Seite 40
Open Tasks
ALM needs to be connected to LDAP
Otherwise, another solution needs to be found for transmitting the vCloud account,
so that the process can be executed automated in the background.
How can we store the user information so that we enable a cost calculation related
to the use in projects?
Seite 41
Changes in the QC Hardware Structure
Previous workplace of a QC employee
1x desktop as workstation machine
1-n Desktops as test machines
Current workplace of a QC
employee
1x Laptop with 2 monitors
HW investment costs about 2.500 EUR HW investment costs about 1.900 EUR
-> minus 24%*
* additinally savings for software/OS, electricity consumption, office space etc.
Seite 42
vCloud-HP-ALM Connector
VMware vCloud-HP-ALM Connector
"We’re using the vCloud as a self-service
portal for testing environments.
After the nightly build process, the Lexware
products are installed AUTOMATICALLY on
virtual machines in the vCloud.
The test cases for automated testing are
stored in HP-ALM.
By combining the two systems, it is possible
to program automated tests in the vCloud
and store the results in the HP-ALM