Ansible Lockdown Meeting Agenda

juliedavila commented 6 years ago

Request Agenda Meetings Here

juliedavila commented 6 years ago

actually @gundalow is it acceptable for folks to open up individual issues for desired agenda topics? It seems most meetings have a single open issue with all agenda items for every meeting...

gundalow commented 6 years ago

Single issue with people adding topics to this, see https://github.com/ansible/community/issues/375

juliedavila commented 6 years ago

Nov 1. After odyssey4me joins the IRC meeting we will discuss the remaining topics around the merger efforts.

Lockown Topics

Generic

[x] policy for new STIGs
[x] Ansible version policy (only promise latest stable support?)
[x] how to best address manual/not-remediated tasks?
[x] Any requests to be considered active member?

Style Guidelines

pulled from https://github.com/MindPointGroup/RHEL7-STIG/issues/81

[x] move from 'yes/no' to real boolean values?
[x] line length limit (or none)
[x] remove severity tags from tasks in favor of having them at the include level
[x] name blocks
[x] no more registered_var | failed move to foo is failed
[x] remove audit playbooks
[x] remove audit and patch tags
[x] must pass DISA check content?

Galaxy

[x] ansible galaxy: should we make tagging/pushing to galaxy a part of the build process?
[x] ansible galaxy: should we make pulp builds during the build process to help air-gapped users?

Development

[x] devexp: would it be useful to have a docker/oscap based runner to tinker against a single rule at a time?
[x] Should we reintegrate oscap eval as part of the CI process to pass/fail testing based on results?

Merger

[x] How do we get roles in lockdown on boarded to the OpenStack/Zuul testing environment?
[x] What permissions/blessings do we need to add Rackspace cobranding to lockdown stuff?
[ ] Any word on @mnaser being ok with having Ubuntu hardening be delegated to an Ubuntu STIG role?
[ ] Status on sphinx books research?
[ ] Open topic for merger-specific things

juliedavila commented 6 years ago

Minutes from Nov1 meeting: https://meetbot.fedoraproject.org/ansible-lockdown/2018-11-01/lockdown_working_group.2018-11-01-16.01.html

shepdelacreme commented 6 years ago

Topics for the agenda today (Nov 15).

Documentation

[x] Remove or keep/update "domains" that ansible-hardening has their tasks split into.
- Decided to remove
[x] Remove the "contrib" stuff from docs. Ansible Hardening has non-STIG items in the role like disabling IPv6. We most likely won't support that in the role so remove this entire section from docs.
- keep but split into "extras" area.
[x] Use V-##### or RHEL-07-##### as the primary identifier in the DOCS? Ansible Hardening used V- and we use RHEL-
- Use RHEL- as primary id but include both in docs