Skip to content
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.

Ansible Lockdown Meeting Agenda #388

Closed
juliedavila opened this issue Oct 26, 2018 · 12 comments
Closed

Ansible Lockdown Meeting Agenda #388

juliedavila opened this issue Oct 26, 2018 · 12 comments
Labels

Comments

@juliedavila
Copy link
Contributor

Request Agenda Meetings Here

@juliedavila
Copy link
Contributor Author

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
Copy link
Contributor

Single issue with people adding topics to this, see #375

@juliedavila
Copy link
Contributor Author

juliedavila commented Nov 1, 2018

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

Lockown Topics

Generic

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

Style Guidelines

pulled from ansible-lockdown/RHEL7-STIG#81

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

Galaxy

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

Development

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

Merger

  • How do we get roles in lockdown on boarded to the OpenStack/Zuul testing environment?
  • 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
Copy link
Contributor Author

@shepdelacreme
Copy link

shepdelacreme commented Nov 15, 2018

Topics for the agenda today (Nov 15).

Documentation

  • Remove or keep/update "domains" that ansible-hardening has their tasks split into.
    • Decided to remove
  • 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.
  • 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

@jamescassell
Copy link

@jamescassell
Copy link

jamescassell commented Dec 13, 2019

@Andersson007
Copy link
Contributor

closed as no activity, thanks everyone!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants