Skip to content

advornic/packer-veos

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

62 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

#Automatically Create vEOS nodes using Packer

##Introduction The guides below will help you quickly turn up vEOS nodes running on VMware (FusionPro/Workstation) or VirtualBox. The Packer configuration files (.json) define 4 VM nodes and assign specific virtual networks to switch interfaces to simulate isolated connections. You can setup a quick demo by using packer-veos and packer-ztpserver. Both of these installations use the ztpserver-demo files to create a simple test environment.

##Memory Requirements Each vEOS node requires at least 2G of RAM and so does the ZTPServer VM. While the memory for the ZTPServer could be reduced without impacting the performance much (500M RAM should also work just fine), the memory requirements for vEOS are not as flexible (1.5G per VM might work with some older vEOS instances, but it is NOT recommended to go lower than that). Hence, in order to run this demo it is recommended to use a machine which has at least 16G or RAM. If that is not possible, the demo can still be used, but the VMs should not all be started at the same time (the maximum number of VMs which could run in parallel will depend on memory size of the system, given the constraints from above).

###VMware Virtual Network Setup vEOS Networks

###VirtualBox Virtual Network Setup vEOS Networks

##Getting Started

About

Packer.io automation of the vEOS nodes

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 100.0%