Adventures & Challenges building an OpenStack public cloud. Walter Heukels, Koert van der Veer en Pim van Riezen

Transcription

1 Adventures & Challenges building an OpenStack public cloud Walter Heukels, Koert van der Veer en Pim van Riezen

2 The Sysadmin Experience Walter Heukels

3 About Me Walter Heukels Senior Engineer at CloudVPS Working on OpenStack Infra

4 About OpenStack Free sojware (Apache License) WriOen in Python Big project Very flexible

5 OpenStack AssumpSons Flexible, but it does have a philosophy CaOle servers, not pets Makes certain assumpsons We came up against some of those Don't go against the grain

6 OpenStack AssumpSons Flexible, but it does have a philosophy CaOle servers, not pets Makes certain assumpsons We came up against some of those Don't go against the grain Unless you really want to

7 OpenStack Structure Lots of sub- projects Nova SwiJ Quantum / Neutron Keystone... Distributed architecture

8 Our Cloud Object Store Since April 2013 Very Cool Compute Started free public beta ZFS Storage KVM VirtualisaSon

9 Lessons Learned: Technical People are mostly running private clouds at the moment Not much informason available on running a public cloud Examples MulSple external networks Keystone (authenscason) performance

10 Lessons Learned: ExpectaSons Customers make assumpsons Especially our customers Examples: IP spoof protecson ( my VPN router doesn't work ) HA for VM's..we're working on this!

11 Security groups?!? Bitcoins!! Lessons Learned: ExpectaSons Some customers don't know what to expect Will my Wordpress site scale automascally?

12 Distributed system Race condisons can occur Lessons Learned: Debugging Hard to find the logging you need Graph everything

13 The Road Ahead New features LBaaS VPNaaS Database as a Service PaaS

14 The Dev Experience Koert van der Veer

15 About Me Koert van der Veer Senior Developer at CloudVPS Working on OpenStack features

16 My Role Before OpenStack Development responsible for every detail of cloud management system Large CompeStors are moving incredibly quickly High pressure to add new features No Sme to fix technical debt

17 My Role With OpenStack Responsible for custom features only Bugs are usually fixed by others Large acsve community helps diagnosing problems ContribuSng is very sassfying and results in goodwill

18 Our Work on OpenStack Core features (contributed) ZFS block storage SwiJ features Bugfixes Deployment Billing Interfacing

19 Development Tools Python with geventlet, kombu, sqlalchemy, etc. DevStack Unit tests Tempest Grenade

20 Development Environment ProducSon close to git head Rapidly re- deployable testcluster pip instell e.

21 Development Work Flow PreparaSon Write code Review Merge Maintain

22 Step 1 - PreparaSon Launchpad blueprints Launchpad bugs IRC Mailinglist

23 Step 2 - Write Code Create feature branch Write code Write unit tests Run unit tests and stasc analysis Commit

24 Step 3 - Review Submit to Gerrit Jenkins tests Other reviews Core reviewer approves

25 Zuul reviews and audits code Jenkins merges code Step 4 & 5 Merge and Maintain

26 Bug detected (Jan 7th) Bug fixed (Jan 9th) Case Study 1: Bug in Cinder- Rootwrap SubmiOed to Gerrit (Jan 9th, Jan 10th) Approved (Jan 14th) Zuul rejected (Jan 15th) SubmiOed to Gerrit (Jan 16th) Approved (Jan 17th) Zuul accepted (Jan 19th)

27 Goal Challenges Case Study 2: Custom Bug in cinder- rootwrap Feature completeness Unit tests Progress Cinder Driver

28 High availability for VMs Per- port IP spoofing control Extra security msg queue Requests? Future Plans for ContribuSon

29 The Frontend Experience Pim van Riezen

30 About Me Pim van Riezen Senior developer at CloudVPS Working on OpenStack GUI

31 Interfacing Goal Goal: Make it easy to get started with a first VM

32 Interfacing Challenges Lots of dependencies: Create a keypair Create a private network Create a NAT router Create security groups and rules Create Server

33 Interfacing Challenges Decisions to make: Networking Key management..

34 Interfacing Challenges Security group abstracson: The double funcson as membership tag and access rule grouping confuses users It takes a lot of words to actually explain the concept

35 Interfacing Challenges API documentason: Hard to figure out what extensions are relevant Different parts of an openstack cloud may be out of sync A lot of perculiar choices made in v1 APIs ssll leak through in v2 Most command line tools also default to v1 APIs Lots of documentason lacks basic descripsons of parameters CombinaSon of tracing command line client, making wild guesses, luck

36 Interfacing SoluSons SoluSons: Comprehensive wizard Clear choices Image metadata Predefined security groups