equalitie / deflect Goto Github PK

• create appropriate role directory
• create README.md file and describe what this part of the role will do and the exact data it needs as input (exact Ansible variable names can be figured out later)

This is only about the initial installation on edges of ATS, Banjax and Swabber.

Write a stub Ansible inventory file and a stub playbook.

The inventory example should take into account the various nature of Deflect's core components: edge, controller, etc. as per the architecture documentation (see #6), even if the names may change later.

The playbook only needs to be a stub that includes roles that have already been implemented. It will be completed later as new roles are implemented.

Content must include:

• a global description of Deflect;
• who this project is aimed at;
• an overview of its components;
• an approximative description of the installation process (it will be made more precise as the implementation gets done);
• a short paragraph about eQualit.ie and contact information.

It must be 80 characters per line maximum.

• create the classical Ansible role structure (roles/ folder etc.)
• write a README.md file in the new role's folder that describes in details what the role will do:
  • how it must change the system
  • what input data it needs (exact names of variables can be figured out later)

As a minimum, the role should do SSH hardening (enforce public key authentication). More can be spec'd in later iterations.

The description must give the reader a clear overview of what a Deflect infrastructure is composed of and how the components interact together.

It must also include vocabularty definitions, such as "edge", "origin", "controller", etc.

Some content should be inserted into the repository's README in the Deflect infrastructure architecture section, but if it ends up being too big, dedicated files can be created.

• add the license to a COPYING or LICENSE file;
• add an explicit mention of it in the README file.