This project goal is to ease and speed up the use of Fortinet VMs on any stack/cloud etc..
To achieve this we propose here a tested public openstack with CityCloud or a personnal openstack in a box (Ubuntu)
Then using the mini-poc concept of 2 VMs, 2 network 1 fortigate we build examples in script, heat, Cloudify or OSM/Rift.io formats.
The scripts are supposed to run on an Ubuntu with root access. See the README Dockerclient for running on external Openstack on any client.
Fortistacks1.2 on Public openstack : https://youtu.be/Zp6CCEbJiUU
If you want to install your own openstack and use the same (on 1 machine) refer to Fortistacks1.1 https://youtu.be/0y38B61FTSk the video applies to version 1.2.
For stable versions of this project refer to :
https://github.com/fortinet-solutions-cse/fortistacks/releases to find the release you like. The master branch can contain work in progress.
In the different directories you will find the following parts, read the README in each folder for details:
-
fortistacks Script to turn a vanilla Ubuntu with empty partition into a system ready for fortistack. Can be ignored if using public or your own openstack.
-
ubuntu-openstack set of scripts to install a fully fonctionnal openstack on 1 machine and use it later as the default VIM. Rely on you running the fortistacks script first.
-
public-openstack This section will configure you CityCloud openstack to work with this project.
-
mini-poc Is the name of a simple scenario (2 networks) 2 generic VMs 1 fortigate in between. All with floating ips so that one can connect to them and generate traffic, see it/block it. This same simple scenario is then declined with the the different approach. It contains the important points to pay attention to while deploying a fortigate/fortios.
-
fortigate/fortios Those are very similar only the fortigate/fortios are highlighted. Target is at least 5.6.3 or 5.4.5 which makes config_drive optionnal. There is script in bash(read it to see the cli) and heat templates
-
cloudify In this folder you will deploy a Cloudify-manager (on lxc locally or vm if public) autoconfigure for using opentack then have the blueprint to use it.
-
osm In this folder you will deploy an OpenSource MANO instance (on lxc locally or vm if public) autoconfigure for using opentack then have the descriptors to use it.
-
An Openstack:
- Public ($) use Citycloud: create and account and go to public-openstack folder
- Private create you own and go to ubuntu-openstack folder
-
Fortigate/fortios images check fortigate and fortios folder for scripted and heat examples.
-
MANO:
- Cloudify folder depending on you openstack choice deploy manager then use the blueprints.
- OSM/Rift.io same as above
This project is opensource and based under Apachev2 license. Every contribution is supposed to respect that. Don't put your company IP in here .. it is bad.
Mini-poc is used to refer to deploying 2 Ubuntu VMs with iperf, Apache, etc.. to be able to generate traffic. 2 networks left and right. 1 fortigate or fortios All have floating ips on a predefined mgmt network As described here:
===========================================================
| | Management/floating ips |
| | |
.----v-----. | |
| trafleft | | |
| Ubuntu | | |
'----------' | |
| | |
v | |
.-,( ),-. .-----v-----. .-,( ),-. |
.-( )-. | Fortigate | .-( )-. |
( left )----->| vm |--->( right ) |
'-( ).-' '-----------' '-( ).-' |
'-.( ).-' '-.( ).-' |
<-------. |
| v
.-----------.
| trafright |
| Ubuntu |
'-----------'
The goal is to offer an easy access to all parts and being able to experiment with Fortinet products on Openstack.