Automatic verification technology of virtual machine software patch on IaaS cloud

Transcription

1 Automatic verification technology of virtual machine software patch on IaaS cloud 2015/01/23 Yoji Yamato Software Innovation Center, NTT Corporation

2 Agenda Background Problems of existing methods Proposal of automatic verification Evaluation of proposed method Conclusion 2

3 Background IaaS Cloud services have been progressed and users can use virtual resources easily. Users can install OS and middleware to VMs(virtual machines) and customize VMs. When new patches are released, users need to distribute patches to their VMs and verify their systems health. This increases users operation costs. 3

4 Needs for patch verification by providers If providers verify each user patches, users operation costs can be decreased. However, it needs a lot of effort to verify because each user environment is different. Today, we propose an automatic verification technology of software patches for user virtual environments on IaaS cloud. 4

5 Agenda Background Problems of existing methods Proposal of automatic verification Evaluation of proposed method Conclusion 5

6 Existing automatic verification technologies Jenkins is a Continuous Integration tool. Selenium repeats web browser actions. However, in these existing technologies i) Providers cannot conduct fixed test cases for plural user virtual environments with different configurations. ii) Preparing test cases for each user environment beforehand is not realistic. 6

7 Agenda Background Problems of existing methods Proposal of automatic verification Evaluation of proposed method Conclusion 7

8 Proposed automatic verification flow User 8. Delete a replicated tenant 7. Gather test cases results Operator 1. Specify User tenant ID, a patch to be distributed Heat Nova Neutron LR OpenStack API OpenStackDB OpenStack LR 2. Replicate User tenant 5. Distribute patches 6. Conduct test cases Automatic Verification Functions (AVF) 3. Get tenant information 4. Extract test cases VM VOL VM VOL VM VOL VM VOL Test case DB User tenant Operator tenant OVS Hyper visor OVS Hyper visor OVS Hyper visor 8

9 Test case DB diagram for effective test cases Verification test cases need to confirm behaviors of each installed software on VM. To reduce prepared test cases, we propose a 2-tier abstraction method of software and related test case. example: OS, DB, Web, Mail, AP server Function group Function group Test case example: Ping communication, Mail send/ receive example: Windows, MySQL, JBoss Software group Software group Test case example: Windows file CRUD CRUD by phpmyadmin EJB execution on JBoss example: Windows2012, MySQL5.1 JBoss5.1 Software Software Test case 9

10 Prepared test case DB data by providers Service providers prepare software relation data and test case data in test case DB before patch verifications. Software relation Function group Software group Software OS Windows Windows Server 2012 Windows 8.1 RHEL RHEL 7.0 RHEL 6.1 DB Oracle Oracle11g Oracle 10g MySQL MySQL 5.0 MySQL 4.0 Web Apache Apache 2.1 Apache 2.2 IIS IIS 8.0 IIS 8.5 Test case information Function group Software group Software Test case DB Table CRUD DB Japanese character garbling check DB Oracle DB MySQL Access by phpmyadmin DB Postgre SQL Test case Test case class target subject Table CRUD DB function group function Japanese character garbling check DB function group data Oracle software group Access by phpmyadmin MySQL software group dunction Postgre SQL software group 10

11 Test case extraction method Firstly, AVFs extract software information of VM. Secondly, AVFs search what software group and what function group the software is belong to. Lastly, AVFs select corresponding test cases respectively for each installed software. 11

12 Agenda Background Problems of existing methods Proposal of automatic verification Evaluation of proposed method Conclusion 12

13 Performance measurement conditions Processing steps of automatic verification: Case 1; Replicate tenant and conduct tests. Case 2; Only conduct verification test cases. Selected test cases number: for DB function group and 5 for MySQL software group or PostgreSQL software group. Concurrent thread numbers: 1 thread, 3 threads, 5 threads 13

14 3:21:36 Performance measurement results (a) shows that image extraction and template deployment take much time in automatic verifications. (b) shows that it takes only 5 minutes for automatic verifications when we skip tenant replications. (a) Case 1 (b) Case 2 virtual resources deletion 0:05:02 2:52:48 2:24:00 test case conduction 0:04:19 0:03:36 test case conduction patch distribution 1:55:12 0:02:53 patch distribution 1:26:24 0:57:36 environment information acquisition 0:02:10 tester resources preparation 0:01:26 environment information acquisition 0:28:48 template deployment 0:00:43 0:00:00 1 thread 3 threads 5 threads template/image extraction 0:00:00 1 thread Copyright threadsntt 5 corp. threads All Rights Reserved. 14

15 Agenda Background Problems of existing methods Proposal of automatic verification Evaluation of proposed method Conclusion 15

16 Conclusion We propose an automatic verification technology of software patch for user virtual environment on IaaS cloud. Our proposed method replicates user tenants, extracts test cases from test case DB, distributes patches and conducts test cases. Performance measurements show that automatic verifications of patch and test cases conductions take only 5 minutes with 5 threads. 16