s a rough draft of a spec. Feel free to throw some darts.
https://review.openstack.org/#/c/222619/
--
Major Hayden
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
into documentation as things deployers
should do locally?
[1] https://benchmarks.cisecurity.org/
[2] https://bugs.launchpad.net/openstack-ansible/+bug/1491915
[3] https://bugs.launchpad.net/openstack-ansible/+bug/1493981
[4] https://en.wikipedia.org/wiki/Information_security#Key_concepts
--
Major Hayden
ist" of CIS benchmarks and
try to tag them with one of the following:
* Do this in OSAD
* Tell deployers how to do this (in docs)
* Tell deployers not to do this (in docs)
That could be lumped in with a spec/blueprint of some sort. Would that be
beneficial?
- --
Major Hayden
-BEG
h. One should be able to have code
> do the "turn it on" "turn it off" mechanics.
I'm completely in agreement on this one. ;)
- --
Major Hayden
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCAAGBQJV8fQcAAoJEHNwUeDBAR+x1BIP/jkq0Gd2SuPcWbMU53xADj1W
ml8VtfkJwT/gs1v8Kfd/
101 - 104 of 104 matches
Mail list logo