Deployment
| Table of Contents |
|---|
Diagram - Single Environment
...
| web | db | geo | total |
|---|---|---|---|---|
DEV | 3 | 4 | 5 | 12 |
QA | 4 | 6 8 | 8 | 18 20 |
PROD | 4 | 6 8 | 8 | 18 20 |
TOTAL | 48 |
DISK (GB)
| web | db | geo | total |
|---|---|---|---|---|
DEV | 10 GB | 20GB 32GB | 200GB | 230GB 242GB |
QA | 10 GB | 20GB 32GB | 200GB | 230GB 242GB |
PROD | 10 GB | 20GB 32GB | 200GB | 230GB 242GB |
failover
Application failover must be achieved within 2-4 hours and proceeds several ways depending on the nature of the failure. Here we discuss fail-over only in the context of lost connectivity to the data center with an uncertain time to restore operations at that datacenter. When there is a configuration change, either at the VM level or at the application level, we clone the entire application and store it offsite (at the city?). Should the datacenter fail badly (fire, etc), we provide carinet with the application, and carinet brings up the application at another location.
...
Allow access only as specified in the deployment diagram.
...
TCP Wrapper Configuration
...
Can we restrict port level access?
- web
- Allow request from all host on port 80
- Allow ssh request from all
- Deny requests on all other ports
- geo
- Allow request from web server on port 8080
- Allow ssh request from all
- Deny request from all other host on port 8080
- db
...