Aperture-py

Latest version: v2.26.0

Safety actively analyzes 688674 Python packages for vulnerabilities to keep your Python projects secure.

Page 39 of 53

0.21.0rc.1

Changelog

List of aperture PRs merged since 0.20.0 release. For the full list of changes, see [list of changes][changes]

Make SDK validator reject Check requests from feature control points (1208)

SDK validator updates expected `http.target` label to be present and so
only worked for traffic control points.
This change makes it work for feature control points with no labels set.

Also make CI run sdk validation if the sdk validator itself is changed.

Nested Circuit (1177)

Description of change
* Closes: 1129

![Screenshot from 2023-01-30
00-53-49](https://user-images.githubusercontent.com/18579817/215431032-0cc7edf4-7bd8-4e15-b4fe-ecf915d8c6ed.png)

---------

Co-authored-by: Harjot Gill <harjot.gillfluxninja.com>

blueprint: revert integrator from latency gradient policy (1205)

Description of change

There is a possible issue with the way we are using the integrator in
the latency gradient policy. Specifically, we need to figure out whether
the min value has to be applied or not. I am reverting to earlier
circuit for now and we can re-add integrator next week.

SDK validator updates for auto-instrumentation testing (1199)

OTEL code cleanup (1193)

* Fix naming in OTEL packages to make it consistent and more readable
* Move OTEL config structs to separate package and split one big file to
few smaller ones with separate responsibilities
* Move OTEL consts to separate package to avoid circular dependencies

Update OTEL to v0.69 (1194)

Add otel contrib receivers and processors to agent (1174)

As part of supporting auto scale feature, aperture agent's otel collector should have all the receivers and processors enabled.
Users can then configure which receivers and processors to be configured and then added into the pipeline.

[re-org docs] add new pages and fix descriptions. (1183)

Description of change
Add new content and re-organize docs.

Added field for agent installation mode in heartbeats (1181)

Description of change

Added field `installationMode` in the heartbeat report to identify that
the agent is running in which mode.

docs: restructure some sections (1184)

Add Holder component (1180)

Holder component holds the last valid signal value for the specified
duration then waits for next valid value to hold.

Provide dynamically configurable constant values in policy (1122)

Renames Constant to Variable, allows it to be dynamically configured.
ConstantSignal can accept either valid float or special math values "NaN", "+Inf", "-Inf".

restructure docs (1167)

Co-authored-by: Hardik Shingala <hardik.shingalafluxninja.com>
Co-authored-by: Sachin Maurya <sachin.mauryafluxninja.com>

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v0.20.0...releases/aperture-controller/v0.21.0-rc.1

0.20.0

Changelog

List of aperture PRs merged since 0.19.0 release. For the full list of changes, see [list of changes][changes]

Add Pulse Generator Component (1163)

Adds pulse generator component which produces 1 and 0 in turns with specified window durations.

Added API for fetching stats from the olric cluster (1158)

Description of change

Added API in agent for fetching stats from Olric cluster.

Add logical combinator components (1159)

Make `build.sh` work with `sh` (1157)

In some places we use the build.sh script with sh not bash. This change updates the if condition to work in both environments.

Enable race detection for agent and controller using `--race` flag in tilt dev environment (922)

Description of change
Fix https://github.com/fluxninja/aperture/issues/758

Add `--race` flag which build the agent and controller binary passing
`go build --race ....` flag.
Usage:

tilt up -- --race

Change error on removing metrics to warn (1117)

When `DeletePartialMatch` returns 0 it does not have to mean there was an error. We could have empty metrics.

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v0.19.0...releases/aperture-controller/v0.20.0

0.20.0rc.2

0.20.0rc.1

0.19.0

Changelog

List of aperture PRs merged since 0.18.0 release. For the full list of changes, see [list of changes][changes]

Fix Control Point Cache provide (1136)

* Move ProvideControlPointCache from Invoke to Provide.
* Make ControlPointCache dependency optional in FN plugin, as Controller won't use it.

flowcontrol: preview http requests (1130)

Description of change

Added preview API for HTTP requests (classifier).

Horizontal Pod Scaler (1112)

Description of change
* Kubernetes Control Point discovery
* Agent Group Leader is responsible for running a continuous Kubernetes
Control Point discovery against Kubernetes API Server to populate a
Kubernetes Control Point Cache
* The idea is to discover Resources which can be scaled
* At startup, it finds all Subresource of kind `Scale`. The parents of
these resources are scalable resources
* A watch is added for all scalable resources. The scale status is
fetched on Add/Update watch changes. A `notifiers.Trackers` is provided
for any other subsystem to subscribe to Kubernetes Control Point Changes
* FluxNinja Plugin sends a snapshot of Kubernetes Control Point Cache
every heartbeat
* Kubernetes Control Point Message

message KubernetesControlPoint {
string api_version = 1;
string kind = 2;
string namespace = 3;
string name = 4;
}

* Pod Scaler
* `horizontal_pod_scaler` spec
* `kubernetes_object_selector` to uniquely identify a scalable
Kubernetes Object (Control Point) at an Agent Group
* `scale_reporter` which emits `actual_replicas` and
`configured_replicas`
* `scale_actuator` which takes `desired_replicas`
* Agent
* The Agent Group Leader is responsible for running the Autoscaler
component
* It subscribes to the Control Point configured in the component from
the Kubernetes Control Point Cache
* The latest Scale Status for the Control Point is synced to etcd under
a new status subtree parallel to config and decisions I.E.
`/status/pod_autoscaler/<componentID>`
* It watches `/decisions/pod_autoscaler/<componentID>` for scale changes
from Controller. Scale is updated in Kubernetes if there's a change.
* Controller
* There is a `desired_replicas` port for setting replica count via a
Signal. This is synced by Controller to a decisions path in etcd path as
referred in Agent
* It signals for completing the feedback loop via ports
`actual_replicas` and `configured_replicas`
* This component takes dynamic config to set dry run mode which disabled
actuation (auto-scale) but still completed the feedback loop for testing
in "dry-run" mode.
* Implements 864

Renamed cloud to ARC and added plugin config example (1116)

Description of change

Renamed all the occurrences of FluxNinja Cloud with FluxNinja ARC and
added config example for fluxninja plugin for connecting Aperture with
FluxNinja ARC

Add Differentiator component (1058)

Adds differentiator component that calculates rate of change per tick.

Remove ControlPointCache dependency in Controller (1104)

Only agent uses control point cache, remove dependency for controller in heartbeats.

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v0.18.0...releases/aperture-controller/v0.19.0

Aperture-py

Page 39 of 53

0.21.0rc.1

0.20.0

0.20.0rc.2

0.20.0rc.1

0.19.0

0.19.0rc.2

Page 39 of 53

Links

Releases