Outdated information in OpenStack security guide case studies

Bug #1680488 reported by Rahul U Nair
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Security Guide Documentation
Confirmed
Medium
Rahul U Nair

Bug Description

Some of the case studies in OpenStack Security Guide needs review and outdated information needs to be updated.

case-studies/compliance-case-studies.rst
Line 39:
As we have openstack sensible security project now, it needs to be mentioned here https://docs.openstack.org/developer/openstack-ansible-security/ . And may be we can rewrite the sentence from `as there is no STIG` to `STIG guidelines can be deployed enforced using ansible-security`

case-studies/dashboard-case-studies.rst
Line 63:
nit: `;` at the end of server name
case-studies/instance-management-case-studies.rst

Line 19:
Intel Ivy Bridge and newer
Line 63:
May be we can write something like : "He plans to implement encrypted migrations by configuring the ``ACCESS_TYPE`` of ``live_migration_uri`` in /etc/libvirt/libvirtd.conf. " Please see this url for more details: /etc/libvirt/libvirtd.conf

Changed in ossp-security-documentation:
importance: Undecided → Medium
assignee: nobody → Rahul U Nair (rahulunair)
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.