Commits on Sep 5, 2018

1. Shift IP Ranges …

   If we increment the IP ranges from `.7`, `.8`, `.9` to `.16`, `.17`, `.18`, it will play nicer with other canonical bosh-deployment cf-deployment repositories.
   
   This is because the cf-deployment sets up a cloud-config range of `10.244.0.0/20`.  That only has a usable range to `.15`:
   
   ```
   $ sipcalc 10.244.0.0/20
   -[ipv4 : 10.244.0.0/20] - 0
   
   [CIDR]
   Host address		- 10.244.0.0
   Host address (decimal)	- 183762944
   Host address (hex)	- AF40000
   Network address		- 10.244.0.0
   Network mask		- 255.255.240.0
   Network mask (bits)	- 20
   Network mask (hex)	- FFFFF000
   Broadcast address	- 10.244.15.255
   Cisco wildcard		- 0.0.15.255
   Addresses in network	- 4096
   Network range		- 10.244.0.0 - 10.244.15.255
   Usable range		- 10.244.0.1 - 10.244.15.254
   ```
   
   And the [convention in bosh-lite](https://bosh.io/docs/bosh-lite/) has been to add a route for internal containers to be on a `10.244.0.0/16` range.  So we can get to more networks than just the cf-deployment's `/20`.
   
   I've test the `.16`, `.17`, `.18`, and all three deployments (bosh-deployment, cf-deployment, cf-mysql-deployment) work better "out of the box" with these changes.

   

   7hunderbird authored Sep 5, 2018
   Configuration menu

   • View commit details
   • Copy full SHA for 1ce1f11
   • Browse repository at this point

   Copy the full SHA

   1ce1f11 View commit details

   Browse the repository at this point in the history