Becoming an IAAS provider

1. How to be Amazon
BECOMING AN IAAS PROVIDER

2. Introduction
 This presentation tells about the efforts of IT in my company,
to become an IAAS provider.
 Of course, you cannot be Amazon. BUT, you can emulate in
your own modest scale the approach of being a cloud
provider.
 Speaker: Jaime Valero.
 Sysadmin at Expert Productivity Group, Telefonica R&D
.

3. Summary
 Introduction & previous presentation
 Master Plan
Scripting
Encapsulate
Cost Modelling
E-commerce solution
OpenCart Jenkins Integration
 Conclusions

4. You may remember me from :
In our previous presentation “How
to be google”, we learnt how to…

5. Index all your data sources in elastics search.- Index all your data sources in elastic search.

6. - Make your IT universe searchable with a single point of entry.

7. Next Step: A single point of entry to manage your IT universe.

8. Feature Evolution
Google
- Index all your data
Amazon
- Self provisioning
infraestructure
IFTTT
- Events interrelation

9. Tenemos un plan
We have a plan :

10. • Scripts:
Manage your object
by scripts only
Repo
collection
• Encapsulate your
script as jenkins jobs.
Bussines API
• Cost Estimation
Cost report
• Sync OpenCart /
Jenkins
Provisioning
portal
Plan phases:

11. Phase I: Scripts

12. Fase I: Scripts
The life cycle of our objects should be managed by scripts
only.
We do not create nor destroy objects directly.
E.G: Create DNS alias script.

13. Phase II : Encapsulate scripts as jenkins jobs.

14. Phase II: Encapsulate scripts as jenkins
job.
 Create a job for each script that you want to publish
 Benefits:
 We have created a centralized API with permissions, audit log.
 Anyone in the team could execute the script.
 This bussiness API could be invoked from other platforms. E.G from Slack.

15. Phase III : Cost estimation.

16. Phase III: Costs calculation.
Calculate the costs of the service we provide to
the organization.
Showback : providing management with an
analysis of the IT costs due to each department
for each delivered services, without actually
cross-charging.

17. • Invoices
Chargeback
Billing
• Infraestructure
cost.
Unit pricing.
• Usage
report per
proyect and
department
• Data Inventory
+ Events
Capacity
planning What items do
I have ?
( servers …)
Whet proyects
are in the
company ?
ChargeBack
and showback
How much the
infraestructure
cost ?
How to do a model cost for IT

18. We generate usage reports.

19. Phase IV: Making a self provisioning portal

20. Phase IV: e-commerce solution
We have a services catalog, and their relates
prices, so we offer it in a human friendly way, a
shop.
We use the web app opencart
https://www.opencart.com/ , dockerized.
Why Opencart ?
 It is an standard, opensource lamp.
Easy customization

21. Our provisioning portal

22. Jenkins  Opencart synchronization
 Given any jenkins job, we have an script to export it to an opencart
product.
 For each pending order in opencart, we trigger a build in the related
jenkins job, with the arguments provided.

23. Sincronización Jenkins  tienda

24. Conclusions
By making a portal to offer to the company a service
catalog with prices and self provisioing, we have
became an IAAS provider.
Now we have an unified API. This allow us to
interconnect third party platforms to enchance service
provided.
Also, the organization has visibility of the service IT
delivers. The departments could use it, with predictable
costs.