1. VSHN AG
The DevOps Company
Basel Drupal Meetup
4.8.2016
Aarno Aukia
CTO & Partner
2. 10.6.2016 VSHN AG | http://vshn.ch 2
About me
●
MSc Computer Science ETH Zurich
●
Security Operations @ Google
●
Co-Founder & CTO @ Atrila GmbH (Security Operations)
●
Co-Founder & CTO @ VSHN AG (DevOps & Cloud-Ops)
●
@aarnoaukia
●
http://about.me/aarno
●
Aarno.aukia@vshn.ch
●
Talk to me !
3. 10.6.2016 VSHN AG | http://vshn.ch 3
About VSHN
●
Swiss DevOps & Ops Company, 14 people in Zurich
●
Building the tools and work9ows for self-service
●
Managing web applications in any cloud
We are cloud-agnostic: we run on AWS, MSA, GCE, DO,
Hetzner, OVH, SafeSwissCloud, Cloudscale, Exoscale and on
any on-premises Enterprise private cloud
5. 10.6.2016 VSHN AG | http://vshn.ch 5
What the heck is DevOps?
●
Collaboration: Development (Dev) and Operations (Ops)
●
Bring agile software engineering methods to operations
– Automation: infrastructure as a code, versioning/rollback
– Testing: continuous integration/testing/deployment
●
Bring operations engineering experience to developers
– Scalability: independent microservices
– Production insight: monitoring/logging/metrics
●
Together: make the application's owner happier
10. What is amazee.io?
Drupal Platform as a Service (PaaS)
Big differences:
1. Hosting anywhere
Already operating in 4 countries (CH, USA, SA, UK) and clients server
300+ Sites
From small to big
2. Local Development Environment
Exactly the same as development and production sites
12. Local Development Environment
Based on Docker
Lightweight and faster than Vagrant/Virtual Machines
Very easy to use, no knowledge of Docker required
Exact same configurations as development and production servers:
Drush, Drupal Console, Composer, Node.js
PHP 5.6, PHP 7, Nginx, Varnish, MariaDB MySQL, Apache Solr
14. Connect and synchronize site to local
Leverages Drush and Drush site aliases
Drush connects to amazee.io API to get information about sites
Everything via ssh public/private keys (no passwords)
No need to know username, passwords, server names
Site Names = Git Branch names
Your own names of sites!
16. Deployments
Based on GIT
Use own Git Hosting (Github, Gitlab, Bitbucket, own Git Server)
Only requirement: Git read access & Webhook on Git push
Additional deployment tasks definable inside .amazeeio.yml file
Or: Use your own Continuous Deployment Infrastructure
19. Deployment workflows
No forced merging or branching workflows by amazee.io
Complete freedom for Developers (GitFlow, GitHubFlow)
Integration with TravisCI, CircleCI, Jenkins or other build systems possible
Bonus: Start amazee.io Docker container inside TravisCI build and run automated tests!
27. Pricing Part A
Flat fee per month based on amount of production sites
Includes two development sites
Additional development sites for small fee
28. Pricing Part B
Volume based pricing (pay what you use)
Based on combined hits of all production sites
Not based on CPU or RAM or Pageviews
Every single request on servers count as a hit
Servers will instruct browsers to cache assets and not request them again
29. Pricing
Pricing allows to scale to any size (no Enterprise levels)
No cost per Developer
Apache Solr for free
HTTPs and SSL Certificates for free
See pricing sheet on https://www.amazee.io
31. amazee.io on-premises
Complete amazee.io hosting stack on any server in the world
Client’s datacenter
Cloud provider of your choice (AWS, Digital Ocean, Rackspace, you name it)
Ubuntu LTS
Completely integrated into amazee.io deployment system
Pricing per instance instead of sites and hits, see pricing sheet on
https://www.amazee.io
