Commit Graph

11 Commits

Author SHA1 Message Date
James Rodewig bd4439be24
[DOCS] Replace hard-coded admons with cloud-only attribute (#70864) 2021-03-25 09:21:35 -04:00
James Rodewig 5c75d004fa
[DOCS] Replace `put` with `create or update` in API names (#70330)
Co-authored-by: debadair <debadair@elastic.co>
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2021-03-15 14:49:44 -04:00
James Rodewig d51a04cd8c
[DOCS] Add operator privileges to APIs and settings (#69903) 2021-03-15 09:20:09 -04:00
Henning Andersen cc30ae8c16
Autoscaling APIs not experimental (#67202)
We no longer regard the autoscaling APIs experimental though they are
only intended for use by ESS/ECE/ECK. This commit updates the docs
to reflect this and adds a minimal set of documentation for the
feature.

Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
2021-01-12 22:03:18 +01:00
Henning Andersen c91a4d8d2b
Autoscaling remove feature flags (#65973)
Removed the autoscaling feature flags, autoscaling is now on by default
(though it requires an external system to handle the autoscaling
events). Added experimental notice to all autoscaling related
documentation pages.

Relates #51191
2020-12-14 19:06:09 +01:00
Henning Andersen 54911ace97
Autoscaling policy roles specification (#64222)
Add a roles specification to autoscaling policies. This is used to map
the policy to a set of nodes governed by the policy. The list of roles
is mandatory when adding a policy, optional on updates.

This commit also removes the outer level "policy" element from autoscaling
policy PUT and GET requests.
2020-11-02 07:30:31 +01:00
Henning Andersen d573fdefd3
Autoscaling capacity API and structure (#63905)
Renamed decision API to capacity. Responses now prefer objects/maps over
arrays. Removed mention of tier, using policies as the outer map and
total for the policy-wide total capacity.
2020-10-21 11:57:11 +02:00
Henning Andersen d8dd6e38a7
Autoscaling decision return absolute capacity (#61575)
The autoscaling decision API now returns an absolute capacity,
and leaves the actual decision of whether a scale up or down
is needed to the orchestration system.

The decision API now returns both a tier and node level required
and current capacity as wells as a decider level breakdown of the
same though with in particular current memory still not populated.
2020-09-18 20:44:20 +02:00
Henning Andersen 92d70534ef
Autoscaling decider and decision service (#59005)
Split the autoscaling decider into a service and configuration
in order to enable having additional context information available
in the service. Added AutoscalingDeciderContext holding generic
information all deciders are expected to need. Implemented GET
_autoscaling/decision
2020-08-10 12:02:25 +02:00
Jason Tedor b82618d4a6
Rename the policy in put autoscaling policy docs
The put autoscaling policy docs use a "hot" policy as an
example. Instead, this commit changes the name of this policy to
"my_autoscaling_policy".
2020-04-01 16:30:26 -04:00
Jason Tedor 6e35354f8e
Introduce autoscaling policies (#54473)
This commit is the first in a series of commits that introduces
autoscaling policies, and APIs for working with them. For now, we
introduce the basic infrastructure, and a single API for putting an
autoscaling policy. We will follow in rapid succession with APIs for
getting, and deleting autoscaling policies.
2020-04-01 07:35:45 -04:00