Documentation/SecurityGuide

The SecurityGuide is a product of the Security Project. We meet on Mondays at 10.00 (usually) in #openstack-security (may change soon).

You can find the Table of Contents for the Security Guide here.

Security Guide Update

What

Maintenance and creation of best practice of the OpenStack Security Guide.

Next Meeting

Monday, July 19 at 10:00 am in the #openstack-security channel

Agenda

• RST migration status
• Individual sections: https://etherpad.openstack.org/p/sec-guide-rst

Past Meetings

Monday, July 19 at 10:00 am in the #openstack-security channel

Agenda

• RST migration status (pdesai)
• Drafting of Case Studies while waiting for RST migration to land: Data Processing (elmiko), Data Tenant Privacy (shelleea007), Storage (Daviey?), Compute (Nathaniel) (not discussed as RST migration was ready)
• Current bugs (https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=sec-guide) (not discussed, will carry over to next meeting)
• Planning for mid-cycle - how do we break down current bug set into 'sprint' activities? (not discussed)
• Status of Security Guide meeting submission into meetings repository

Monday, July 12

• RST migration
• Current bugs
• Planning for mid-cycle
• Formalization of the Security Guide meeting including this wiki, and the proposed meeting in #openstack-meeting-alt

Monday, July 5

Useful links:

• security specs repo
• Review for formalizing the move to #openstack-meeting-alt

Action items

1. pdesai to submit the blueprint to migrate from DocBook to RST format

Where

Join the group in #openstack-security room to chat about this effort. Regular meetings are for 30 minutes on each Monday at 10am US Pacific.

---

Bug Bash

1. Whenː Weekly at 10.00 PST
2. Whereː The #openstack-security room

Logistics

Open Bugsː Link

1. Tag to useː sec-guide
2. Version of Book to file bugs againstː HTML Version

Suggested Priority

1. Pri0ː Stale/ Incorrect info (for instance wrong config, incorrect settings etc)
2. Pri1ː Missing Info (like new chapters to add, topics to cover etc)
3. Pri2ː Cosmetic Errors/ Sentence formation etc

Things to Note

1. Use the little 'bug' icon to auto-magically create a bug entry with relevant info such as chapter name, page, url. You can add more details like tag, description as required.
2. Include as many details as possible, chapter #, location etc in the book.
3. Include OpenStack Versions if applicable