Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Elastic{ON} 2018 - Elastic Cloud.(next)

Elastic Co
March 01, 2018

Elastic{ON} 2018 - Elastic Cloud.(next)

Elastic Co

March 01, 2018
Tweet

More Decks by Elastic Co

Other Decks in Technology

Transcript

  1. • Different importance, versions, SLAs, workloads, backup policies • Noisy

    neighbours • Upgrades and maintenance • Reducing blast radius
  2. Backups • Automatic backups • Every 30 minutes • 48

    hours retention • Single click restore
  3. • Isolating clusters. • Different teams have different needs. •

    Availability vs. resource usage on cluster change. • Over-provisioning.
  4. • Available just milliseconds away in • North Virginia •

    Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress • Available just milliseconds away in • North Virginia • Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress
  5. • Available just milliseconds away in • North Virginia •

    Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress • Available just milliseconds away in • North Virginia • Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress
  6. • Available just milliseconds away in • North Virginia •

    Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress • Available just milliseconds away in • North Virginia • Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress
  7. • Available just milliseconds away in • North Virginia •

    Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress • Available just milliseconds away in • North Virginia • Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress
  8. • Available just milliseconds away in • North Virginia •

    Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress • Available just milliseconds away in • North Virginia • Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress
  9. • Available just milliseconds away in • North Virginia •

    Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress • Available just milliseconds away in • North Virginia • Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress
  10. • Available just milliseconds away in • North Virginia •

    Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress • Available just milliseconds away in • North Virginia • Oregon • North California • Iowa • Ireland • Frankfurt • Belgium • São Paulo • Sydney • Tokyo • Singapore • + 5 more regions in 2018 • AWS and GCP • Azure in progress
  11. ECE 1.0: Turning a SaaS into a product • Elastic

    Cloud Enterprise 1.0.0 launched May 2017. • Focus: Easy installation and maintenance.
  12. host-A $ ./elastic-cloud-enterprise.sh install [ progress info, … eventually: ]

    Elastic Cloud Enterprise installation completed successfully [ details on how to log in + token to add new servers ] Then, on another host: host-B $ ./elastic-cloud-enterprise.sh install \ --coordinator-host host-A \ --roles 'roles_for_new_host' --roles-token 'token' \
  13. host-A $ ./elastic-cloud-enterprise.sh install [ progress info, … eventually: ]

    Elastic Cloud Enterprise installation completed successfully [ details on how to log in + token to add new servers ] Then, on another host: host-B $ ./elastic-cloud-enterprise.sh install \ --coordinator-host host-A \ --roles 'roles_for_new_host' --roles-token 'token' \
  14. host-A $ ./elastic-cloud-enterprise.sh install [ progress info, … eventually: ]

    Elastic Cloud Enterprise installation completed successfully [ details on how to log in + token to add new servers ] Then, on another host: host-B $ ./elastic-cloud-enterprise.sh install \ --coordinator-host host-A \ --roles 'roles_for_new_host' --roles-token 'token' \ --roles 'roles_for_new_host' --roles-token 'token' \ Optional, but let's you automate deployment (We do that on our SaaS)
  15. 100% of its Elasticsearch workloads on ECE. 50 nodes on

    10 hosts. See use case for more details.
  16. "We were quite happy with Elastic Cloud, but Elastic Cloud

    Enterprise gave us all of those same features in a way that also allowed us to have full management control over the entire server and underlying software." – Edwin Law Data Engineering and Database Operations Lead, Grab
  17. ECE 1.1: Upgradability and 6.0 • X-pack Security and 6.0:

    • Encryption required between nodes. • Certificates managed behind the scenes. • Upgrade all the things with little impact.
  18. • ECE 1.0: Launch, installation and maintenance. • ECE 1.1:

    Upgrades and 6.0 • ECE 1.2: Get the most out of your hardware. • ECE 1.3: ( described soon too )
  19. Different is different • SSDs: Great for hot data, but

    (still) expensive. • Dense storage: Cheaper storage for archiving. • High CPU: Ingest, machine learning, high query rates • Lots of memory: Analytics, "instant search", ... • Cheap memory: Kibana, master nodes, ...
  20. At different times • SSDs: Today's data. Maybe last week's.

    • Dense storage: Last 90 days data. • High CPU: • Burst-y usage vs. sustained. • Overcommitting can be acceptable.
  21. For different products • Elasticsearch wants memory, CPU, storage, and

    bandwidth: lots and fast. • Kibana / APM: A little bit of memory and some CPU. • ML: CPU and memory.
  22. Kibana Elasticsearch Logstash Beats / APM Elastic Cloud Enterprise will

    package and manage Elasticsearch, Kibana, Logstash, Beats, APM, Swiftype's ( site + app + enterprise ) search
  23. Kibana Elasticsearch Logstash Beats / APM Elastic Cloud Enterprise will

    package and manage Elasticsearch, Kibana, Logstash, Beats, APM, Swiftype's ( site + app + enterprise ) search
  24. Elastic Cloud Enterprise will package and manage Elasticsearch, Kibana, Logstash,

    Beats, APM, Swiftype's ( site + app + enterprise ) search
  25. • Last 7 days' data on hot nodes. • Last

    90 days' data on cold nodes. • … in the same cluster and dashboards. In the same cluster
  26. Demo summary • View and manage infrastructure. • Easily create

    hot/warm deployments. • Machine Learning + APM coming to Cloud. Soon.
  27. Demo summary • View and manage infrastructure. • Easily create

    hot/warm deployments. • Machine Learning + APM coming to Cloud. Soon.
  28. Talk at 2:30 today. Covers this in more detail. Stretching

    the Cloud: Flexibility in Cloud Deployments Jonathan Halterman Cloud Engineer, Elastic Uri Cohen Director of Product Management, Elastic
  29. Scheduling stateful nodes • Changing Kibana is simple as it's

    stateless. • Changing Elasticsearch … • … takes >50 steps … • … with many different strategies.
  30. Elasticsearch on Kubernetes • Kubernetes with stateful sets? • Helps,

    but it's a small piece of the puzzle. • ECE complements Kubernetes.
  31. ECE 1.3: Role Based Access Control • 1.2 lets you

    slice and dice your infrastructure. • 1.3's focus is Role Based Access Control: • SAML, LDAP, … • Tagging + RBAC = private infrastructure
  32. ECE 1.3 • Usage metering/auditing • Track which user runs

    what. • Cross Cluster Search • Search many clusters as if they were one.
  33. And More • Index lifecycle management. • Audit logging. •

    Quality of life improvements. • More snapshot targets.
  34. Meet us at the AMA booth. Thanks! Talks by Cloud

    team members: 1:30: Logging and Metrics in Elastic Cloud 2:30: Stretching the Cloud
  35. Meet us at the AMA booth. Thanks! Talks by Cloud

    team members: 1:30: Logging and Metrics in Elastic Cloud 2:30: Stretching the Cloud
  36. Except where otherwise noted, this work is licensed under http://creativecommons.org/licenses/by-nd/4.0/

    Creative Commons and the double C in a circle are registered trademarks of Creative Commons in the United States and other countries. Third party marks and brands are the property of their respective holders. 107 Please attribute Elastic with a link to elastic.co