Black list of routes

Introduction

Use Case

Administrators would want to block a list of routes so that they are not assigned to any of the private Gateways.

Architecture and Design description

Each zone will get a new attribute - list of blacklisted Routes. By default this parameter will be empty, which means no routes will be blacklisted.

While creating routes on private Gateways within this zone, if the route is part of the blacklist, route creation will not be allowed. The verification will be done using NetUtils.isNetworksOverlap() method

API changes

create/updateZone will get a new parameter - blackListRoutes (corresponding responses will be added as well). It's going to accept list of routes separated by comma in format of x.x.x.x/x. Example: "10.10.10.0/24,172.16.1.0/24"

DB changes

Added field blacklist_routes to the data_center table (null by default). During the db upgrade insert this field with NULL value.

QA

Verify that you can't add static route if its exists as blacklisted route for the zone. It will apply only to the newly created static routes; if the static route was created before the blacklist route was updated for the zone with the same IP - it's ok.

Verify that blacklisted route accepts only valid IP addresses.