validation labs with openstack
play

Validation Labs with OpenStack Shuquan Huang, Intel IT Engineering - PowerPoint PPT Presentation

Intel IT OpenStack Practice Validation Labs with OpenStack Shuquan Huang, Intel IT Engineering Computing Weibo: @ Intel Information Technology Intel Confidential Do Not Forward Agenda About Me Intel IT with OpenStack


  1. Intel IT OpenStack Practice Validation Labs with OpenStack Shuquan Huang, Intel IT Engineering Computing Weibo: @ 黄舒泉 Intel Information Technology Intel Confidential — Do Not Forward

  2. Agenda • About Me • Intel IT with OpenStack • The way we do Cloud • OpenStack Practice • Integration with Intel Validation Cloud • Q & A Intel Information Technology Intel Information Technology 2 Intel Confidential – for internal use only Intel Confidential – for internal use only

  3. Huang, Shuquan • Joined Intel in 2011 • Software Engineer, Certified Scrum Master • Leads IT Engineering Computing OpenStack Team • Focus on Cloud Solution and Agile Coming from Intel IT Engineering Computing • Focus on Intel private cloud solution – Intel Validation Cloud • Start OpenStack journey from 2011 Intel Information Technology Intel Information Technology 3 Intel Confidential – for internal use only Intel Confidential – for internal use only

  4. OpenStack – Intel IT Convergence Platform Silicon Design Validation Cloud Hosting Cloud Cloud OpenStack Existing Infrastructure New Infrastructure Intel Information Technology Intel Information Technology 4 Intel Confidential – for internal use only Intel Confidential – for internal use only

  5. The Way we do Cloud Our Developers Snapshot Improvement Deployment Solution Cloud Data Analysis customization Build Pre-Release Production Production Local Git Tempest Launcher One-Stop-Shop Admin Portal Intel Information Technology Intel Information Technology 5 Intel Confidential – for internal use only Intel Confidential – for internal use only

  6. Continuous Delivery Continuous Delivery (CD) is a pattern language used in software development to automate and improve the process of software delivery. - wiki Intel Information Technology Intel Information Technology 6 Intel Confidential – for internal use only Intel Confidential – for internal use only

  7. Problem Statement • Configuration is easy to lose • It takes a long time to get feedback after developers make customized changes in OpenStack • Track and try the latest update from community • Automated test runs after each code changed Intel Information Technology Intel Information Technology 7 Intel Confidential – for internal use only Intel Confidential – for internal use only

  8. Solution • Refer to http://ci.openstack.org/ and build our own system • Configuration as Code • Version Control: Code, Configuration, Environment and anything else Deploy new cluster by using some version source code and cluster topology Internet Daily update Puppet Master GitHub OpenStack and Tempest Repository After deployment, run Tempest to validate changes Polling changes OpenStack Bug fixed & new features Cluster Our Developers Local Git Repo Jenkins Manual Trigger CI or Define topologies of Configure polling stratigies OpenStack Cluster Deployment Admin Engineer Intel Information Technology Intel Information Technology 8 Intel Confidential – for internal use only Intel Confidential – for internal use only

  9. Challenges • Installation by source code • Environment cleanup before each build • Upgrade • Rebuild totally • Configuration as Code Intel Information Technology Intel Information Technology 9 Intel Confidential – for internal use only Intel Confidential – for internal use only

  10. Snapshot Improvement Reduce the time of original OpenStack Snapshot Intel Information Technology Intel Information Technology 10 Intel Confidential – for internal use only Intel Confidential – for internal use only

  11. Problem Statement & Objective • Snapshot in OpenStack • Takes 20 mins for the snapshot of a 20GB VM • Fast Snapshot in OpenStack • Self-customized feature • Takes less than 1 min for the snapshot of a 20GB VM Intel Information Technology Intel Information Technology 11 Intel Confidential – for internal use only Intel Confidential – for internal use only

  12. Solution • Analyze each step of original snapshot. • Reduce the time consuming stage. • Optimized the workflow to fit our requirements. Intel Information Technology Intel Information Technology 12 Intel Confidential – for internal use only Intel Confidential – for internal use only

  13. Fast Snapshot Diagram Nova Glance IMG0 IMG0 copy IMG1 IMG1 IMG2 IMG2 Linked VM Instances IMG0 VM1 VM2 VM3 IMG1 VM1 VM2 VM3 This is the relation between VM Instances, Nova and Glance. • When we launch an instance, the image from Glance, eg IMG0 will be copied into Nova. • Then the nova will create a linked image as “disk” for VM Instances. • Intel Information Technology Intel Information Technology Intel Confidential – for internal use only Intel Confidential – for internal use only

  14. Fast Snapshot Diagram Nova Glance IMG0 IMG0 IMG0 IMG1 IMG1 VM1 IMG2 IMG2 VM Instances IMG0 copy VM1 VM2 VM3 IMG1 VM1 VM2 VM3 When user run fast snapshot for VM1- IMG0, the instances “disk” will be copied and stored in Glance. • The speed of this process is depend on the size of linked image. Size = VM1 which is smaller if we compare to • the original snapshot, Size = VM1 + IMG0 Intel Information Technology Intel Information Technology Intel Confidential – for internal use only Intel Confidential – for internal use only

  15. Fast Snapshot Diagram Nova Glance IMG0 IMG0 IMG0 IMG0 copy IMG1 IMG1 VM1 VM1 IMG2 IMG2 VM Instances IMG0 VM1 VM2 VM3 IMG1 VM1 VM2 VM3 When the user launch the created snapshot, the image from Glance will be copied into Nova. • The speed of the copy is depending on the size of the image. • Intel Information Technology Intel Information Technology Intel Confidential – for internal use only Intel Confidential – for internal use only

  16. Fast Snapshot Diagram Nova Glance IMG0 IMG0 IMG0 IMG0 IMG1 IMG1 VM1 VM1 IMG2 IMG2 copy and resize VM Instances IMG0 VM1 VM2 VM3 VM4 IMG1 VM1 VM2 VM3 The VM1 from the Nova will be copied into a newly created VM (VM4) instance folder as a “disk”. • The resize of the instance also being done during this process if the user pick bigger “flavor” for their • instance The speed in creating a new VM is depending on the size of IMG0-VM1 • Intel Information Technology Intel Information Technology Intel Confidential – for internal use only Intel Confidential – for internal use only

  17. Deployment Solution Rapid deployment of different topologies OpenStack from bare metal Intel Information Technology Intel Information Technology 17 Intel Confidential – for internal use only Intel Confidential – for internal use only

  18. Solution • Open Source Solution: • PXE boot up • puppet/dodai deployment • Fast Deployment • Deploy full stack of OpenStack on Live USB: Ubuntu 12.04 • mult nodes bare-metal with Essex Customized • Package several mins Dodai server • • Auto deployment: • Only one 4G U-Disk is needed Intel Information Technology Intel Information Technology 18 Intel Confidential – for internal use only Intel Confidential – for internal use only

  19. Tempest Launcher Tempest more stable and visible to verify cloud functionalities Intel Information Technology Intel Information Technology 19 Intel Confidential – for internal use only Intel Confidential – for internal use only

  20. Problem Statement & Objective • Problem Statement: • Result is not user unfriendly and exception may happen during running tempest scripts in batch directly • Objective • Address the problems mentioned above • Improve and enhance the capability of tempest automatic launching and handling of tests in batch execution Intel Information Technology Intel Information Technology Intel Confidential – for internal use only Intel Confidential – for internal use only

  21. Problem 1 Dirty test environment when previous test teardown function is skipped for unexpected errors Test environment will be cleaned up tearDo Down wn() () setUp Up() () testFu Func nc() () in tearDown() function Normal test execution flow Test environment cannot be cleaned up Err rror r happe ppens ns tearDo Down wn() () setUp Up() () testFu Func nc() () And the dirty test environment will impact Exit t Script following test . Test execution flow with exception Intel Information Technology Intel Information Technology Intel Confidential – for internal use only Intel Confidential – for internal use only

  22. Problem 2 Test script requires test pre-environment TEST PASS Test A 0 A 2 A Available Available ilable Netw ilable Netw tworks tworks rks rks Test B TEST FAIL Test A didn’t release the networks from the test specific tenant Test B failed since no available network Intel Information Technology Intel Information Technology Intel Confidential – for internal use only Intel Confidential – for internal use only

  23. Problem 3 Cannot provide fully customized or prioritized test execution plan …… when run test in batch. It’s hard to run the tests across folders or scripts at one time. Run the tests from 1 script: root@hostname:~/tempest# nosetests -v tempest.tests.compute.test_images Run the tests from 1 folder: root@hostname:~/tempest# nosetests -v tempest.tests.compute Intel Information Technology Intel Information Technology Intel Confidential – for internal use only Intel Confidential – for internal use only

Recommend


More recommend