Entities

[rafi]

• Inventory
  • Host
• Job
  • Type (Run/Check?)
  • Playbook
  • Task
  • Project
• Team
  • User

[rafi]

Case-study example Project: Acme Inventory: Acme Servers Hosts: Prod01, Prod02, Stage01 Team: Acme IT Users: Roadrunner, Wolf Playbooks:

• Provision server, type: Check
• Provision server, type: Run
• Build, type: Run
• Deploy, type: Run

[rafi]

Different flag usages of ansible-playbook:

--check --diff --tags=postgresql --limit=dbservers

[adamli]

Chart editable source: https://docs.google.com/a/sortex.co.il/drawings/d/1TawttuWJfm51jRm5fRpZ06C7bi3ZwwZtRutZm8hIF_Y/edit?usp=drive_web

[ronenli]

Lets discuss about where will we save the data for each one of the entities. Database / Config files

[adamli]

Structure suggestion

Team

• name
• Actions:
  • Manage teams

User

• name
• email
• password
• is_owner
  • The 1st user.
  • He is the only one that is authorized to manage Teams, Users & Projects and their relations
• Actions:
  • Manage users

Team Users

• user_id
• team_id
• Actions:
  • Manage teams-users relation

---

Project

• name
• Actions:
  • Manage projects

Project Teams

• project_name
• team_id
• Actions:
  • Manage groups-teams relation

---

Inventory - hosts file

• One per project, mandatory
• Groups
• Hosts (name + IP in etc/hosts OR IP only)
• Actions:
  • Import using file upload OR git repository+path in repo OR textarea

---

Playbook - folder for each playbook

• Includes Variables + Roles + Tasks
• Will be stored in files, under each project folder
• Actions:
  • Import using zip file upload OR git repository+path in repo

---

Job (playbook execution)

• user
• playbook
• group
• hosts
• params
• version
• created
• finished
• output
• status (in progress, stop, success, failed)

---

Notes

• There might be parts that can be developed later like teams
• There are entities which we might be able to fetch from yml like hosts, groups, inventory and maybe even playbooks

[rafi]

A few questions I thought of:

• Does a Job have only one record in the jobs table?
• If a Job has a single output field - it can't accommodate a history of each time it was executed in the past. It will only store the last entry.

[adamli]

We planned 'playbook' as the execution plan, while 'job' is a single execution of the playbook. i believe you previously referred it as build/execute