This release is a pre-release and may not be stable for production use.
validation-app-engine
Overview
Why Required ?
Distributed Workload Resource Validation and Metrics Collection is a key aspect of scale testing today. resources can be Network Resource, Memory Resource etc.
Currently, available resource validators don’t scale economically and are limited when it comes to customization. Metrics and Analytics tools are also extremely expensive and do not always work with some products. That may not be generating metrics that are compatible with the platform. Reliability and Serviceability testing is not fully automated today as teams struggle to simulate user workloads and analyze the data from the same. Products need metrics to measure performance and reliability.
What is Validation App Engine ?
validation-app-engine an agent based distributed workload resource validation and monitoring engine that lets various quality and reliability engineering teams to validate their products at large scale. The remote agents can be programmed to generate resource patterns OR monitor resources and send back information to a central analytics layer for further analysis teams can make several inferences by analyzing the data generated.
Target Audiance
Quality Teams
Performance Engineering Teams
Chaos/Reliability Engineering Teams
Development Teams
Key Highlights
Framework agnostic.
Platform agnostic (Windows / Linux).
It also support validation against Linux network namespaces.
Cloud agnostic (vSphere, AWS, Azure).
Self-contained Repo / Binaries.
Support for client / servers running on any port.
Integration with any DB (natively works on SQLite DB and RiakDB).
Utility for validating Traffic, Resource and Realization patterns.
Build utilities on top of it to manage or monitor remote endpoints.
Architecture
As per current architecture, it can support number of resources. Currently it supports only network resources, where it generates, validates and monitor network traffic. In future, other resources support can be added based on interfaces provided in the code. Under network resource it supports -
Distributed traffic generation
Validating traffic patterns
Traffic rule realization
Local and central store of traffic stats.
Installation
Please refer Installation Guide for detailed installation.
Network Resource Realization and Validation
Supported Protocols/Modes
- Protocols -
TCP
UDP
- Modes -
Client
Server
Topology and workflow
Please refer Workflow Guide for detailed description on basic topologies and workflow.
How to validate traffic
Please refer Example Traffic Validation Guide for detailed example on how to generate, realize traffic rules and validate traffic.
Metadata
Release files for validation-app-engine 0.3.5.dev43
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| validation-app-engine-0.3.5.dev43.tar.gz | 487.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| validation_app_engine-0.3.5.dev43-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 575.2 kB
Release files / validation-app-engine-0.3.5.dev43.tar.gz
| Download URL | validation-app-engine-0.3.5.dev43.tar.gz |
|---|---|
| Size | 487.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff82307b1840a6c6544dca6bea26f81080eaca619c983e69de059b68d21cd73c
|
|
BLAKE2b-256 checksum How to use checksums |
ae178ab68a7fcd3bc9e2cf039767ef784f1c31819077a0ff357fe2bb0204839e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.9
|
Release files / validation_app_engine-0.3.5.dev43-py3-none-any.whl
| Download URL | validation_app_engine-0.3.5.dev43-py3-none-any.whl |
|---|---|
| Size | 87.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
319dfa65392d4c275422b42e53d7309d83d7f062ed09fad5717cb620fae967b7
|
|
BLAKE2b-256 checksum How to use checksums |
032ff3a388698600c0582bf74a2e1dfd396ae387ab9d09b936f60e4ec8684765
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.9
|
Security for validation-app-engine 0.3.5.dev43
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.