Confirmed users
66
edits
m (Minor edits for clarity) |
|||
| Line 54: | Line 54: | ||
* Little use of standards based technologies | * Little use of standards based technologies | ||
* Practically no usage of pre-developed open source puppet modules | * Practically no usage of pre-developed open source puppet modules | ||
* Shared infrastructure | * Shared infrastructure which leads to issues such as: | ||
** Security: The more applications on the infra the larger the attack surface | |||
** Upgrades: Upgrading a library for one application may mean upgrading for all apps | |||
** Scalability: If one application needs to scale, all other applications on the shared infra will scale too | |||
** Uptime: If one application brings down the infrastructure, all applications come down | |||
* Lack of standardization leading to deployment difficulties | |||
* Lack of standardization | * No service catalog for developers to plan against | ||
* No service | * No easily deployable development environments which mimic production | ||
* No easily deployable | * Lack of best practices around multi tenant applications | ||
* Lack of best practices around multi tenant | |||
* Puppet modules do not work in a distributed environment | * Puppet modules do not work in a distributed environment | ||
** No development environment | ** No development environment for module testing | ||
** No per module permissions model | ** No per module permissions model | ||
** Workflow leads to unusable revision history | ** Workflow leads to unusable revision history | ||
| Line 82: | Line 81: | ||
* No log aggregation system / developers have poor access to logs | * No log aggregation system / developers have poor access to logs | ||
* Backups are not automatic and are often missing altogether | * Backups are not automatic and are often missing altogether | ||
* Lack of or out of date documentation | |||
== How will we solve the problems? == | == How will we solve the problems? == | ||