Automatyczne skalowanie w OpenStack. Rafał Szmigiel OpenStack Solution Architect/Red Hat

Transcription

1 Automatyczne skalowanie w OpenStack Rafał Szmigiel OpenStack Solution Architect/Red Hat

2 Cześć! Rafał Szmigiel Red Hat OpenStack Solutions Architect od Grudnia 2015 Poprzednio: OpenStack Operations Rackspace Systems Wydawnictwo Naukowe PWN S.A.

3 What is CLOUD COMPUTING?

4 Cloud Computing Cloud computing is a type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand. It is a model for enabling ubiquitous, on-demand access to a shared pool of configurable computing resources (e.g., computer networks, servers, storage, applications and services), which can be rapidly provisioned and released with minimal management effort. Source:

5 Cloud Computing Cloud computing is a type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand. It is a model for enabling ubiquitous, on-demand access to a shared pool of configurable computing resources (e.g., computer networks, servers, storage, applications and services), which can be rapidly provisioned and released with minimal management effort. Source:

6 The problem.

7 Workload underestimation Load capacity 20 0 Monday Tuesday Wednesday Thursday Friday Saturday Sunday

8 Workload overestimation Load capacity 20 0 Monday Tuesday Wednesday Thursday Friday Saturday Sunday

9 The solution: auto-scaling infrastructure Load capacity 20 0 Monday Tuesday Wednesday Thursday Friday Saturday Sunday

10 Heat. ( The orchestrator )

11 OpenStack Orchestrator - Heat Provides human and machine accessible orchestration service Managing the entire life cycle of cloud infrastructure and applications Uses templates to describe and configure components and... relations and dependencies between them.

12 It is HOT Heat Orchestration Template HOT is a template format supported by the Heat along with the other template format, i.e. the Heat CloudFormation-compatible format (CFN). It is expressed in YAML format. The structure of a Heat Orchestration Template has three main sections: Parameters - These are settings passed to heat, which provides a way to customize a stack, and any default values for parameters without passed values. These are defined in the parameters section of a template. Resources - These are the specific objects to create and configure as part of a stack. OpenStack contains a set of core resources that span across all components. These are defined in the resources section of a template. Output - These are values passed from heat after the stack s creation. You can access these values either through the heat API or client tools. These are defined in the output section of a template.

13 Simple Heat template heat_template_version: description: Simple template to deploy a single compute instance resources: my_instance: type: OS::Nova::Server properties: key_name: my_ssh_key image: RHEL7-x86 flavor: m1.small

14 Heat resources $ openstack orchestration resource type list OS::Glance::Image OS::Neutron::FloatingIP OS::Neutron::FloatingIPAssociation OS::Neutron::Net OS::Neutron::NetworkGateway OS::Neutron::Port OS::Neutron::ProviderNet OS::Neutron::RBACPolicy OS::Neutron::SecurityGroup OS::Nova::Flavor OS::Nova::FloatingIP OS::Nova::FloatingIPAssociation OS::Nova::HostAggregate OS::Nova::KeyPair OS::Nova::Server OS::Glance::Image

15 Heat stack s lifecycle management Create a stack $ openstack stack create -t autoscaling.yaml -e autoscalingenvironment.yaml stack-wordpress Field Value id b8-39aa af-0f db stack_name stack-wordpress description AutoScaling Wordpress creation_time T17:54:30 updated_time None stack_status CREATE_IN_PROGRESS stack_status_reason Stack CREATE started

16 List stacks Heat stack s lifecycle management $ openstack stack list ID Stack Name Stack Status Creation Time stack-wordpress CREATE_COMPLETE T17:54: Get stack s resources $ openstack stack resource list ${STACK_NAME_OR_UUID} resource_name resource_type resource_status lb OS::Neutron::LoadBalancer CREATE_COMPLETE cpu_alarm_high OS::Ceilometer::Alarm CREATE_COMPLETE lb_floating OS::Neutron::FloatingIP CREATE_COMPLETE db OS::Nova::Server CREATE_COMPLETE monitor OS::Neutron::HealthMonitor CREATE_COMPLETE

17 Heat stack s lifecycle management Few other example commands to manage stack s lifecycle: $ openstack stack resource show ${STACK_NAME_OR_UUID} ${RESOURCE_ID} $ openstack stack output list ${STACK_NAME_OR_UUID} $ openstack stack suspend ${STACK_NAME_OR_UUID} $ openstack stack resume ${STACK_NAME_OR_UUID} $ openstack stack update --dry-run ${ARGS} ${STACK_NAME_OR_UUID} $ openstack stack delete ${STACK_NAME_OR_UUID}

18 OpenStack s telemetry services.

19 OpenStack Telemetry Ceilometer data collection service Aodh alarming service Gnocchi time-series DB and resource indexing service

20 Auto-scaling ( automagically )

21 Heat auto scaling group asg: type: OS::Heat::AutoScalingGroup properties: min_size: 1 max_size: 6 resource: type: OS::Nova::Server properties: flavor: {get_param: flavor} image: {get_param: image} key_name: {get_param: key_name} metadata: {get_param: metadata} user_data: {get_param: user_data} user_data_format: RAW networks: [{network: {get_param: network} }] (...)

22 Heat auto scaling policy web_server_scaleup_policy: type: OS::Heat::ScalingPolicy properties: adjustment_type: change_in_capacity auto_scaling_group_id: {get_resource: asg} cooldown: 60 scaling_adjustment: 1 web_server_scaledown_policy: type: OS::Heat::ScalingPolicy properties: adjustment_type: change_in_capacity auto_scaling_group_id: {get_resource: asg} cooldown: 60 scaling_adjustment: -1

23 cpu_alarm_high: type: OS::Ceilometer::Alarm properties: Heat alarm definition description: Scale-up if the average CPU > 50% for 30 seconds meter_name: cpu_util statistic: avg period: 30 evaluation_periods: 1 threshold: 50 alarm_actions: - {get_attr: [web_server_scaleup_policy, alarm_url]} matching_metadata: {'metadata.user_metadata.stack': {get_param: "OS::stack_id"}} comparison_operator: gt

24 Autoscaling at a very high level

25 Externally triggered scaling action It is as easy as HTTP POST query: curl -X POST %3A%3A00cac25bdaae4d20b e2dbe4%3Astacks%2Fstack-wordpress %2F6a5308ec-8dee-4b9e-9d8d-0f473e2fce85%2Fresources %2Fweb_server_scaleup_policy?Timestamp= T19%3A41%3A34Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=df7b944c180a 47c9a958fb504f0d6590&SignatureVersion=2&Signature=dGrYqZsnOdgtjzG9XNuSi qwawpl1jmx1cryfn16%2b1oq%3d

26 What s happening there?! ( And why I got 1000 instances on Sunday morning? )

27 Heat $ openstack stack event list ${STACK_NAME_OR_UUID} :56:16 [web_server_scaledown_policy]: SIGNAL_COMPLETE alarm state changed from alarm to alarm (Remaining as alarm due to 1 samples outside threshold, most recent: ) :57:17 [web_server_scaledown_policy]: SIGNAL_COMPLETE alarm state changed from alarm to alarm (Remaining as alarm due to 1 samples outside threshold, most recent: ) :59:30 [web_server_scaleup_policy]: SIGNAL_COMPLETE alarm state changed from ok to alarm (Transition to alarm due to 1 samples outside threshold, most recent: ) :03:32 [web_server_scaleup_policy]: SIGNAL_COMPLETE alarm state changed from alarm to alarm (Remaining as alarm due to 1 samples outside threshold, most recent: ) :04:40 [web_server_scaleup_policy]: SIGNAL_COMPLETE alarm state changed from alarm to alarm (Remaining as alarm due to 1 samples outside threshold, most recent: )

28 Aodh $ aodh alarm list alarm_id type name state severity enabled da8- threshold stack-cpu_alarm_lo alarm low True a54bc325- threshold stack-cpu_alarm_hi ok low True $ aodh alarm-history show a54bc325-3bdb-4745-bbcc-3419d3a13f56 timestamp type detail :05:04 state transition {"state": "ok"} 22:59:03 state transition {"state": "alarm"} 20:59:03 state transition {"state": "ok"}

29 Ceilometer $ ceilometer statistics -m cpu_util -a avg -p 60 Period Start Avg Duration 60 22:53: :54: :55: :56: :57: :58: :59: :00: :01: :02: :03: :04: :05: :06: :07: :08: :09:

30 Questions?

31 Thank you

32