Skip to content

Keysight/bpsve

BranchesTags

Repository files navigation

BreakingPoint VE Deployment Templates

Welcome to the official GitHub repository for Keysight BreakingPoint VE Deployment Templates.
This repository provides deployment configurations and templates for BreakingPoint VE, compatible with multiple cloud environments.

🖥️ Platforms

AWS Logo Amazon Web Services (AWS)

🔧 Configurations

This section includes .bpt configuration files tailored for specific AWS instance types:

  • c5.xlarge
  • c5n.xlarge

🚀 Deployment

Starting with version 11.00, BreakingPoint VE Virtual Controller and Virtual Blade are available on the AWS Marketplace:

The BreakingPoint VE product is split between the two above VMs. Please make sure that you subscript to both of them before moving forward.

🔧 Prerequisites

Before you begin, ensure you have the following:

  • AWS Account: An active AWS account with appropriate permissions.
  • BreakingPoint VE License: Ensure you have a valid license for BreakingPoint VE.

📦 CloudFormation Templates

Located in aws/Deployment/CloudFormation, these JSON templates are organized into:

  • BPS Folder: Includes both Virtual Controller and Blade(s)
    • Demo Use Case: Full deployment including networking, security groups, etc.
    • Standalone Use Case: Similar to Demo, but allows parameter customization (e.g., VPC CIDR)
    • Add-On Use Case: Designed to integrate with existing infrastructure
  • NP Folder: Templates for deploying additional Virtual Blades

🧪 Example #1: Deploying a Demo Use Case Template

To deploy a full BreakingPoint VE environment using a CloudFormation template:

aws cloudformation create-stack \
  --stack-name BPS-Demo-Deployment \
  --template-body file://Deployment/CloudFormation/BPS-VE-FullDeployment/AWS-1-Virtual-Blade-Demo-Use-Case.json

🧷 Example #2: Deploying an Add-On Use Case Template

This adds a Virtual Blade to an existing infrastructure (e.g., VPC, subnets).

aws cloudformation create-stack \
  --stack-name BPS-AddOn-Deployment \
  --template-body file://Deployment/CloudFormation/BPS-VE-FullDeployment/AWS-1-Virtual-Blade-Add-On-Use-Case.json

📋 Notes

  • Ensure the AWS CLI is configured with appropriate credentials and region.
  • Replace file paths and parameter files with your actual paths if different.

Terraform logo Terraform Templates

Welcome to the guide for deploying BreakingPoint VE using Terraform templates on AWS. This document provides step-by-step instructions, example commands, and best practices for a successful deployment.

🔧 Prerequisites

Before you begin, ensure you have the following (additionally on top of top prerequisites):

  • Terraform: Installed on your local machine. Install Terraform

🛠️ Setup

1. 🔧 Clone the Repository

Clone the BreakingPoint VE Terraform templates repository to your local machine:

git clone https://github.com/Keysight/bpsve.git
cd aws/Deployment/Terraform/

🔐 2. Configure AWS Credentials

aws configure

🌍 3. Initialize Terraform

Run the following command to initialize the working directory:

terraform init

🧱 4. Review the type of template you wish to use

Choose between:

  • Demo Templates
  • Add On Templates

🚀 5. Apply the Deployment

terraform apply -auto-approve

🧩 6. Optional Usage

terraform validate
terraform plan
terraform state list
terraform output

🧹 7. Cleanup

To destroy the deployment and remove all resources:

terraform destroy -auto-approve

📋 Notes

  • Ensure your IAM user has permissions to create EC2 instances, VPC resources, and IAM roles.
  • Use Terraform workspaces if managing multiple environments (e.g., dev, staging, prod).
  • Store your state file securely if using remote backends like S3 with DynamoDB for locking.

GCP Logo Google Cloud Platform (GCP)

🔧 Configurations

This folder contains several BPS-VE .bpt configurations that can be used on their respective instance sizes. We have 4 different folders:

  • C2-STANDARD-4
  • C2-STANDARD-8
  • C2-STANDARD-16

🚀 Deployment

Starting with version 11.00, BreakingPoint VE Virtual Controller and Virtual Blade are available on the GCP Marketplace

This product contains both the Virtual Controller and Virtual Blade as part of the product subscription.

🔧 Prerequisites

Before you begin, ensure you have the following:

  • GCP Account: An active GCP account with appropriate permissions.
  • GCP CLI: Installed and configured with your credentials. Install GCP CLI
  • BreakingPoint VE License: Ensure you have a valid license for BreakingPoint VE. between each other.

Deployment Manager

Located in google-cloud-platform/Deployment/DeploymentManager, these JSON templates are organized into:

  • Demo Use Case: Full deployment including networking, security groups, etc.
  • Add-On Use Case: Designed to integrate with existing infrastructure

Deployment of these templates can be done through the Google Cloud Platform Cloud Shell. Before starting the deployment please upload your .jinja and .jinja.schema files to your Cloud Shell machine.

The following command should be executed to run a deployment:

gcloud deployment-manager deployments create DEPLOYMENT-NAME --template -GCP-1-Virtual-Blade-Demo-Use-Case-DM-Template.jinja

The status of the deployment will be displayed when the deployment will finish.

Terraform logo Terraform Templates

Welcome to the guide for deploying BreakingPoint VE using Terraform templates on GCP. This document provides step-by-step instructions, example commands, and best practices for a successful deployment.

🔧 Prerequisites

Before you begin, ensure you have the following (additionally on top of top prerequisites):

🛠️ Setup

1. 🔧 Clone the Repository

Clone the BreakingPoint VE Terraform templates repository to your local machine:

git clone https://github.com/Keysight/bpsve.git
cd google-cloud-platform/Deployment/Terraform/

🔐 2. Install Google Cloud SDK

# For Ubuntu/Debian
curl https://sdk.cloud.google.com | bash
exec -l $SHELL

# For macOS (using Homebrew)
brew install --cask google-cloud-sdk

# For Windows, download from: https://cloud.google.com/sdk/docs/install

3. Authenticate with Google Cloud

# Login to your Google account
gcloud auth login

# Set up application default credentials for Terraform
gcloud auth application-default login

# Verify authentication
gcloud auth list

4. Create and Configure GCP Project

# Create a new project (optional)
gcloud projects create my-terraform-project-$(date +%s) --name="Terraform Demo Project"

# Set the project ID (replace with your project ID)
export PROJECT_ID="your-project-id"
gcloud config set project $PROJECT_ID

# Enable required APIs
gcloud services enable compute.googleapis.com
gcloud services enable sqladmin.googleapis.com
gcloud services enable servicenetworking.googleapis.com
gcloud services enable cloudresourcemanager.googleapis.com

🌍 5. Initialize Terraform

Run the following command to initialize the working directory:

terraform init

🧱 4. Review the type of template you wish to use

Choose between:

  • Demo Templates
  • Add On Templates

🚀 5. Apply the Deployment

terraform apply -auto-approve

🧩 6. Optional Usage

terraform validate
terraform plan
terraform state list
terraform output

🧹 7. Cleanup

To destroy the deployment and remove all resources:

terraform destroy -auto-approve

📋 Notes

  • Use Terraform workspaces if managing multiple environments (e.g., dev, staging, prod).

Cloud Shell

Contains two bash scripts that can help you create or delete network peering between two VPCs. You will need to provide the following parameters:

  • Region name
  • Login ID Tag
  • Project Tag
  • Verbose Output

Alibaba Logo Alibaba Cloud

This repository contains a collection of YAML templates for deploying infrastructure and applications on Alibaba Cloud using Resource Orchestration Service (ROS).

📦 Contents

  • alibaba/ – Templates for Alibaba Cloud ROS (e.g., ECS, VPC, RDS)

🛠️ Prerequisites

  • An active [Alibaba Cloud account](httpss to the [ROS Consoleor [ACK Console- Properly configured [Alibaba Cloud CLI](https://www.alibabaclInstructions
  • Virtual Controller and Virtual Blade QCOW2 images uploaded into the Alibaba Cloud account

Deploying ROS Templates

This template deploys one Virtual Controller with the following characteristics:

  • 8 GB RAM
  • 4 vCPUs
  • 30 GB Disk
  • One management interface
aliyun ros CreateStack \
  --StackName my-stack \
  --TemplateBody file://ansible/Ixia_BreakingPoint_Virtual_Controller_Alibaba_ROS_Template.yaml

This template deploys one Virtual Blade with the following characteristics:

  • 8 GB RAM
  • 4 vCPUs
  • 10 GB Disk
  • One management interface (for test interfaces please use UI to attach more interfaces )
aliyun ros CreateStack \
  --StackName my-stack \
  --TemplateBody file://ansible/Ixia_BreakingPoint_Virtual_Blade_Alibaba_ROS_Template.yaml

OpenStack Logo OpenStack

Introduction

For OpenStack private cloud we provide Heat templates that can be used to deploy one BreakingPoint VE Virtual Controller and one BreakingPoint VE Virtual Blade.

🔧 Prerequisites

Before getting started, make sure you have the following in place:

  • BreakingPoint VE License: A valid license for BreakingPoint VE is required.
  • Image Uploads: The BreakingPoint VE Virtual Controller and Virtual Blade .qcow2 images must be extracted and uploaded to the OpenStack Glance image service.
  • Flavor Configuration: Create the following flavors in OpenStack for the respective components:
    • Virtual Controller: 8 GB RAM, 4 vCPUs, 30 GB disk
    • Virtual Blade: 8 GB RAM, 4 vCPUs, 10 GB disk

Specialized knowledge

Before you deploy these templates, we recommend that you become familiar with the following notions:

About

BreakingPoint Virtual Edition

Resources

Readme

License

MIT license
Activity
Custom properties

Stars

2 stars

Watchers

2 watching

Forks

4 forks
Report repository

Releases 6

11.20 Latest
Dec 17, 2025
+ 5 releases

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages