lappis-unb / chef-lappis Goto Github PK

Create bot to help while managing LAPPIS's infrainstructure. And sends pug bombs, of course!!

Create emails' list for infra team.

Create documentation to explain:

• Initialization scripts;
• Routing scripts;
• LetsEncrypt scripts;
• Etc;

Create documentation to explain utilization and management of Rocker Chat.

nginx fires error with socket handshake.

these ate specific conf necessary to rocketchat

proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;

we have to figure out a way to define specific configurations to each application provided under https.

A big behavior problem of letsencrypt's recipe occurs when one o more services are down. It causes a bad generation of a new certificate and all services become inaccessible.

How to start working with devops at LAPPIS.

Create documentation to explain utilization of LetsEncrypt.

Create documentation to explain about services utilization:

• SSH utilization;
• user lappis;
• Scripts localization;
• Users management / permissions;

Create users at Rocket Chat for infra team.

Develop automatic system for monitoring infrastructure's services.

Update network topology, at https://github.com/lappis-tools/chef-lappis/wiki/Network--topology, in order to add new services' descriptions.

One problem we've been facing is that our letsencrypt recipe always requires us to manually create a new DNS zone for all new services provided under our domain. That is a problem when we descentralize our services maintenance, but centralize our DNS management.
We can try to use a DNS service that provides an API to dynamically create new zones, like cloudflare.

Create documentation to describe, utilization and configuration, of services available on Hadouken infrastructure, at LAPPIS.

For some security and reliability reasons, these subdomains reverse-proxies must be isolated in different virtual machines. The certificate_domains.yaml must be separated too, like certificate_domains-lappis.rocks.yaml and certificate_domains-fga.unb.br.yaml or, the recipe should apply a regex to check which domain will be used in different converges.

• The script should be properly reviewed and some updates are necessary
• The backup should be redundant.

Should be create script that receive an signal from Nobreak and shutdown the servers.

Create a package based on unb-gama/noosfero/unstable-1.8 branch and remove the 1.8 package from the repos machine. Upload the new package and run the recipe / or sudo apt-get install to update the package.

We should improve chef cookbook to read a config file with the VM's IPs and it's authorized users' public keys to automatize the process of deploying accessibility to new users at LAPPIS.

Simple recipe that contains only the external route configurations.

Now it's being saved under /arquives/lappis.rocks, overriding some older inside this folder. We should execute the recipe again, then should check the data of last modifying so we'll be able to update the letsencrypt cookbook to handle certificates generation again.

This page must contains a error message and links to LAPPIS' available services.

First of all, duplicate Chef/Chake documentation from old repository: https://github.com/lappis-tools/chef-lappis/wiki/Network--topology.
Once you did that, update the documentation with news about Chef/Chake's utilization.