)]}'
{"security-guide/section_networking-services-security-best-practices.xml":[{"author":{"_account_id":12325,"name":"Nathaniel Dillon","email":"nathaniel.dillon@alumni.depaul.edu","username":"sicarie"},"change_message_id":"f668b0ba34d76637c51f46a84fb417dc06cd4427","unresolved":false,"context_lines":[{"line_number":68,"context_line":"          service.\u003c/para\u003e"},{"line_number":69,"context_line":"        \u003c/listitem\u003e"},{"line_number":70,"context_line":"      \u003c/itemizedlist\u003e"},{"line_number":71,"context_line":"      \u003cpara\u003eA security group is a container for security group rules. Security groups and their rules allow administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a virtual interface port. When a virtual interface port is created in OpenStack Networking it is associated with a security group. For further details on port security groups default behavior, reference the \u003clink xlink:href\u003d\"https://wiki.openstack.org/wiki/Neutron/SecurityGroups#Behavior\"\u003eNeutron Security Group Behavior\u003c/link\u003e documentation.\u003c/para\u003e"},{"line_number":72,"context_line":"      \u003cpara\u003eWhen using the OpenStack Compute API to modify security groups, the updated security group applies to all virtual interface ports on an instance. This is due to the OpenStack Compute security group APIs being instance-based rather than port-based, as found in OpenStack Networking.\u003c/para\u003e"},{"line_number":73,"context_line":"    \u003c/section\u003e"},{"line_number":74,"context_line":"    \u003csection xml:id\u003d\"networking-services-security-best-practices-quotas\"\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"9a41bdd9_c647221c","line":71,"updated":"2015-07-16 22:00:45.000000000","message":"1) I think security group should be without the s as we are referencing the generalized default security group.  \n\n2) Please update \u0027Neutron\u0027 in the link title to \u0027Networking\u0027 per doc convention.\n\n3) Personally (but I won\u0027t -1 based on this alone), I like the reminder at the end that the default security group can be modified on a per-deployment basis.","commit_id":"17d3e30dbf619a1d4eb0b58af573ce700b573ee7"},{"author":{"_account_id":9945,"name":"william snow","email":"wasnow@cisco.com","username":"wasnow"},"change_message_id":"a37a37fa998434fb1f17188aaf173a72cba53d0d","unresolved":false,"context_lines":[{"line_number":68,"context_line":"          service.\u003c/para\u003e"},{"line_number":69,"context_line":"        \u003c/listitem\u003e"},{"line_number":70,"context_line":"      \u003c/itemizedlist\u003e"},{"line_number":71,"context_line":"      \u003cpara\u003eA security group is a container for security group rules. Security groups and their rules allow administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a virtual interface port. When a virtual interface port is created in OpenStack Networking it is associated with a security group. For further details on port security groups default behavior, reference the \u003clink xlink:href\u003d\"https://wiki.openstack.org/wiki/Neutron/SecurityGroups#Behavior\"\u003eNeutron Security Group Behavior\u003c/link\u003e documentation.\u003c/para\u003e"},{"line_number":72,"context_line":"      \u003cpara\u003eWhen using the OpenStack Compute API to modify security groups, the updated security group applies to all virtual interface ports on an instance. This is due to the OpenStack Compute security group APIs being instance-based rather than port-based, as found in OpenStack Networking.\u003c/para\u003e"},{"line_number":73,"context_line":"    \u003c/section\u003e"},{"line_number":74,"context_line":"    \u003csection xml:id\u003d\"networking-services-security-best-practices-quotas\"\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"3a50d1a3_bb4883b4","line":71,"in_reply_to":"9a41bdd9_c647221c","updated":"2015-07-27 20:43:09.000000000","message":"Corrected based on your feedback","commit_id":"17d3e30dbf619a1d4eb0b58af573ce700b573ee7"}],"security-guide/source/networking/services-security-best-practices.rst":[{"author":{"_account_id":10670,"name":"Michael McCune","email":"elmiko@redhat.com","username":"mimccune"},"change_message_id":"a739d6327a19f1d85f4dcb0f4506e57cc43528c4","unresolved":false,"context_lines":[{"line_number":70,"context_line":"specify the type of traffic and direction (ingress/egress) that is"},{"line_number":71,"context_line":"allowed to pass through a virtual interface port. When a virtual"},{"line_number":72,"context_line":"interface port is created in OpenStack Networking it is associated with"},{"line_number":73,"context_line":"a security group. For further details on port security group default"},{"line_number":74,"context_line":"behavior, reference the `Networking Security Group Behavior"},{"line_number":75,"context_line":"\u003chttps://wiki.openstack.org/wiki/Neutron/SecurityGroups#Behavior\u003e`__"},{"line_number":76,"context_line":"documentation. Rules can be added to the default security group in order"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_61b4af34","line":73,"updated":"2015-08-24 22:23:13.000000000","message":"i think this reads a little odd, maybe it would be clearer as: \"For further details on the default behavior of security group ports, reference the...\"","commit_id":"fb6d455ba95edb099cf0c2b32a4040e56eb98a75"}]}