1. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Domain Quotas (DRAFT) Leandro Rosa Tiago Martins

2. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 2 Context Problem: Cloud Admin is not able to limit resources usage within a domain Solution: Domain Quotas – Constraints Services (e.g. nova) should continue enforcing quotas Keystone should concentrate the public APIs – Issue: How Keystone can distribute domain quotas to services?

3. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 3 Approaches Cross-Region Domain Quotas (based on Update and Usage) – Cloud Admin sets domain quotas – Services exchange quotas usage – Keystone continuously distributes domain quotas to regions Keystone-centric Collaborative (Voucher) Per-Region Domain Quotas (based on Update) – Cloud Admin sets domain quotas – Keystone distributes domain quotas to services Global assignment Individual assignment

4. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Cross-Region Domain Quotas

5. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 5 Cross-Region Domain Quotas: Use Cases Pre-requisite: Default domain quotas are in place Cloud Admin sets domain quotas (UPDATE) Cloud Admin views domain quotas Cloud Admin views domain quotas usage Cloud Admin views domain quotas usage per region Cloud Admin deletes domain quotas – back to default values

6. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 6 Cross-Region Domain Quotas: Distribution Keystone Region 1 Nova Glance Region n Nova Glance... Domain “A” vCPUs: 100 vCPUs: 10vCPUs: 20 Services exchange quotas usage Keystone continuously distributes domain quotas to regions

7. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 7 Cross-Region Domain Quotas: Approaches Keystone-centric – Distribution intelligence is in Keystone only Approach #1: Polling “Service, how many quotas are you using?” Collaborative – Distribution intelligence is spread over Keystone and services Approach #1: Vouchers (Service request) “Keystone, I need a quota voucher now/in a short-term” Note: We are not considering a Distributed Database (e.g. MongoDB) neither Message Queue Protocol (e.g. RabbitMQ)

8. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 8 Cross-Region Domain Quotas Advantages – Automated distribution – Domain quotas are shared – Global usage view Disadvantages – Cloud Admin does not control quota distribution – Not suitable for regions that have different infrastructure (e.g. KVM and ESX) Recommended for similar regions (e.g. same hypervisor type)

9. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Per-Region Domain Quotas

10. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 10 Per-Region Domain Quotas: Use Cases Pre-requisite: Default domain quotas are in place Global Assignment – Cloud Admin sets domain quotas (UPDATE) – Cloud Admin views domain quotas – Cloud Admin views domain quotas usage – Cloud Admin deletes domain quotas – back to default values Individual Assignment – Cloud Admin sets domain quotas for each region (UPDATE) – Cloud Admin views domain quotas per region – Cloud Admin views domain quotas usage per region – Cloud Admin deletes domain quotas per region – back to default values

11. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 11 Per-Region Domain Quotas: Global Assignment Keystone Region 1 Nova Glance Region n Nova Glance... Domain “A” vCPUs: 100 vCPUs: 100 Keystone distributes domain quotas to services (on update only) vCPUs: 100

12. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 12 Per-Region Domain Quotas: Individual Assignment Keystone Region 1 Nova Glance Region 4 Nova Glance... Domain “A” Region 1 vCPUs: 100 vCPUs: 100 Keystone distributes domain quotas to services (on update only) vCPUs: 200 Domain “A” Region 4 vCPUs: 200

13. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 13 Per-Region Domain Quotas Advantages – Cloud Admin controls the domain quota distribution per region Fine-grained region control – Suitable for regions that have different infrastructure (e.g. KVM and ESX) Disadvantages – No domain quotas sharing – No global domain quota usage view Global Assignment: Recommended for similar regions (e.g. same hypervisor type) Individual Assignment: Recommended for different regions (e.g. unlike hypervisor types)

14. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Planning

15. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 15 Effort Estimate ApproachEffort Estimate (EW) Cross-Region Domain Quotas (Voucher)12 Per-Region Domain Quotas6

16. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 16 Cross-Region Domain Quotas (Voucher) Use Case / Underlying FunctionalityEffort Estimate (EW) Distributor: middleware with responsability of quota distribution, revocation. Tracking of quotas, quota expiration control. 4 Domain Quota Driver: check, reserve, commit, rollback and enforcement of quotas. Decides when to ask for more quotas to Distributor. Developed as expecting a plugin to predict quota usage. Keep quota consumation to feed predictor plugin. 4 Predictor Plugin: decides how much quota the Domain Quota Driver must ask for the Distributor. 1 CRUD – how to update quotas and how to inform the services. Deletion – back do defaults and sanity checks 2 Unit testing, code review, etc1 Total12

17. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 17 Per-Region Domain Quotas Use Case / Underlying FunctionalityEffort Estimate (EW) CRUD – update quotas and sanity check, delete quota: back to default values 2 Domain Quota Driver: check, reserve, commit, rollback and enforcement of quotas. 3 Unit testing, code review, etc1 Total6

18. © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Thank you