Chapter 12. Messaging security in OpenStack Security Guide  -> Message queue process isolation and policy - current - more details need for namespaces and zeromq

Bug #1342421 reported by Lucas Fisher
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Expired
Wishlist
Unassigned

Bug Description

More details are needed describing or illustrating the process isolation described in this section. There are suggestions of using network namespaces for process isolation but no real details on how to do so. Especially with zeromq. This looks complicated enough that at least a diagram illustrating setup of zeromq using network and ipc namespaces would be helpful.
-----------------------------------
Built: 2014-07-15T19:04:56 00:00
git SHA: f7711cc343e504283676dfe43afae6faa9046fd7
URL: http://docs.openstack.org/security-guide/content/messaging-security.html
source File: file:/home/jenkins/workspace/security-doc-tox-doc-publishdocs/security-guide/ch_messaging-security.xml
xml:id: messaging-security

Tags: sec-guide
Bryan D. Payne (bdpayne)
Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Bryan D. Payne (bdpayne) wrote :

Idea here should be to provide a high level diagram, but not get too deep into the discussion of network namespaces, which is probably best left to other guides. We do think that a diagram would be useful here.

summary: - Chapter 30. Messaging security in OpenStack Security Guide  -> Message
+ Chapter 12. Messaging security in OpenStack Security Guide  -> Message
queue process isolation and policy - current - more details need for
namespaces and zeromq
Revision history for this message
Tom Fifield (fifieldt) wrote :

With the recent stance on zeromq changing, is this bug still valid?

Changed in openstack-manuals:
status: Confirmed → Incomplete
Revision history for this message
N Dillon (sicarie) wrote :

I don't believe so, we have the section on message hardening so I think we're covered

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-manuals because there has been no activity for 60 days.]

Changed in openstack-manuals:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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