Alejandro Gonzalez Roman - Load Generation Environment

Load Generation Environment

Client: Enterprise cloud security system.

What: Prodruc arquitecture, prototyping, workflow and, design.

Results: 160% Productivity

Summary

The Client’s lab, development and, QA environments (Loadgen) has grown over the many years. This environment has expanded to support everything from basic testing to 100G+ load generation by tacking on features, hardware, and tools.

The Problem

The actual solution has cause many disruptions, delays in QA testing, and incidents beyond simple misconfigurations and overlaping of work and enviroments. In addition to these issues, there is a need to simulate the production Internet, which requires the used of space for load generation sources. This need, when deployed in a merged testing and development environment, limits what any environment within the QA suite can access on the Internet. This leads to new requirements and a ground up rebuild of the load generation and testing infrastructure.

Discovery & Research

We meet with stakeholders, manages and programers, to gather requirements and information about their goal and needs.

• All of the load generation tools and traffic need to be placed and manage in a single platform.

• Users have to login to the platform

• Users will have the ability to view of multiple types of loadgen and

• Users will select loadgen and environment, indicate the timeframe for the reservation. Application is expected to validate that there are no other conflicting tests scheduled for the environment/loadgen combination selected.

• Display loadgen calendar

• Provide capability of rescheduling prior tests.

• List reservations by resource and time.

• List reservation for the day.

User-flow / Brainstorming session