)]}'
{"doc/networking-guide/source/intro_network_namespaces.rst":[{"author":{"_account_id":4656,"name":"Sean M. Collins","email":"sean@coreitpro.com","username":"scollins"},"change_message_id":"7029ea64373b842afcd94509ee87b4e7f9219a88","unresolved":false,"context_lines":[{"line_number":5,"context_line":"A namespace, in general, is a way of scoping a particular set of identifiers,"},{"line_number":6,"context_line":"and thereby making it possible to use the same identifier multiple times - in"},{"line_number":7,"context_line":"different namespaces - or to restrict the set of such identifiers that are"},{"line_number":8,"context_line":"visible to a particular process."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_6f1afcc7","line":8,"updated":"2015-08-26 13:49:02.000000000","message":"I like Joseph\u0027s suggestion.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":10897,"name":"Joseph Robinson","email":"josephremail@gmail.com","username":"RobiJoe"},"change_message_id":"898c0fecde86834c441d035b697269c63a2518c1","unresolved":false,"context_lines":[{"line_number":5,"context_line":"A namespace, in general, is a way of scoping a particular set of identifiers,"},{"line_number":6,"context_line":"and thereby making it possible to use the same identifier multiple times - in"},{"line_number":7,"context_line":"different namespaces - or to restrict the set of such identifiers that are"},{"line_number":8,"context_line":"visible to a particular process."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_5b5cb318","line":8,"updated":"2015-08-26 06:23:15.000000000","message":"Line 5 - 8: (Optional) Consider removing the dash aside from this paragraph to reduce the sentence length and increase clarity:\n\n\"A namespace is a way of scoping a particular set of identifiers. Using a namespace, you can use the same identifier multiple times in different namespaces. You can also restrict an identifier set visible to particular processes.\"","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":5,"context_line":"A namespace, in general, is a way of scoping a particular set of identifiers,"},{"line_number":6,"context_line":"and thereby making it possible to use the same identifier multiple times - in"},{"line_number":7,"context_line":"different namespaces - or to restrict the set of such identifiers that are"},{"line_number":8,"context_line":"visible to a particular process."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_b2bb98c3","line":8,"in_reply_to":"fa1b9901_6f1afcc7","updated":"2015-08-26 15:07:14.000000000","message":"Agreed, will do.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"},{"line_number":12,"context_line":"see and communicate with other processes in the same namespace.  So, if a shell"},{"line_number":13,"context_line":"in a particular process namespace ran `ps waux`, it would only show the other"},{"line_number":14,"context_line":"processes in the same namespace."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_97b8d412","line":12,"updated":"2015-08-26 10:54:33.000000000","message":"Please remove extra whitespace before \u0027So\u0027.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"f24ea2d5f6a088bf04d37d407c95e1aef3650845","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"},{"line_number":12,"context_line":"see and communicate with other processes in the same namespace.  So, if a shell"},{"line_number":13,"context_line":"in a particular process namespace ran `ps waux`, it would only show the other"},{"line_number":14,"context_line":"processes in the same namespace."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_b096e092","line":12,"in_reply_to":"da20952f_7fa02791","updated":"2015-08-26 22:44:31.000000000","message":"I\u0027ve found this convention now in the IBM style guide, so will follow it in next upload.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"},{"line_number":12,"context_line":"see and communicate with other processes in the same namespace.  So, if a shell"},{"line_number":13,"context_line":"in a particular process namespace ran `ps waux`, it would only show the other"},{"line_number":14,"context_line":"processes in the same namespace."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_b21dd874","line":12,"in_reply_to":"fa1b9901_97b8d412","updated":"2015-08-26 15:07:14.000000000","message":"Can you point to a specific RST or OpenStack convention for this?  In general I find text more readable with two spaces after the end of each sentence, and I\u0027ve heard many other people say that too.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"99cdf3bcfbd723a993f149ec2a4b90401b897ccd","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"},{"line_number":12,"context_line":"see and communicate with other processes in the same namespace.  So, if a shell"},{"line_number":13,"context_line":"in a particular process namespace ran `ps waux`, it would only show the other"},{"line_number":14,"context_line":"processes in the same namespace."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_7fa02791","line":12,"in_reply_to":"fa1b9901_b21dd874","updated":"2015-08-26 16:34:55.000000000","message":"I don\u0027t thinks we have such a convention, but it\u0027s a common practice in all the OpenStack manuals. Moreover, it saves time and space. \u003d)","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"},{"line_number":12,"context_line":"see and communicate with other processes in the same namespace.  So, if a shell"},{"line_number":13,"context_line":"in a particular process namespace ran `ps waux`, it would only show the other"},{"line_number":14,"context_line":"processes in the same namespace."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Linux network namespaces"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_b773987f","line":13,"updated":"2015-08-26 10:54:33.000000000","message":"I would wrap `ps waux` into 2 backticks -\u003e ``ps waux``","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"},{"line_number":12,"context_line":"see and communicate with other processes in the same namespace.  So, if a shell"},{"line_number":13,"context_line":"in a particular process namespace ran `ps waux`, it would only show the other"},{"line_number":14,"context_line":"processes in the same namespace."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Linux network namespaces"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_b52b8281","line":13,"in_reply_to":"fa1b9901_b773987f","updated":"2015-08-26 15:07:14.000000000","message":"Thanks, will do.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":17,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as `eth0`, exists in a particular namespace.  Linux"},{"line_number":21,"context_line":"starts up with a default network namespace, so if your OS doesn\u0027t do anything"},{"line_number":22,"context_line":"special, that\u0027s where all the network devices will be.  But it\u0027s also possible"},{"line_number":23,"context_line":"to create further non-default namespaces, and create new devices in those"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_77c5005a","line":20,"updated":"2015-08-26 10:54:33.000000000","message":"Another extra whitespace after a full stop.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":17,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as `eth0`, exists in a particular namespace.  Linux"},{"line_number":21,"context_line":"starts up with a default network namespace, so if your OS doesn\u0027t do anything"},{"line_number":22,"context_line":"special, that\u0027s where all the network devices will be.  But it\u0027s also possible"},{"line_number":23,"context_line":"to create further non-default namespaces, and create new devices in those"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_55a30600","line":20,"in_reply_to":"fa1b9901_77c5005a","updated":"2015-08-26 15:07:14.000000000","message":"As above.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as `eth0`, exists in a particular namespace.  Linux"},{"line_number":21,"context_line":"starts up with a default network namespace, so if your OS doesn\u0027t do anything"},{"line_number":22,"context_line":"special, that\u0027s where all the network devices will be.  But it\u0027s also possible"},{"line_number":23,"context_line":"to create further non-default namespaces, and create new devices in those"},{"line_number":24,"context_line":"namespaces, or move an existing device from one namespace to another."}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_77c1802e","line":21,"updated":"2015-08-26 10:54:33.000000000","message":"1) OS - it\u0027s better not to use abbreviation in the docs, not to mix up OpenStack with operating system.\n\n2) doesn\u0027t -\u003e does not (it\u0027s better to avoid contractions, as auto-translator may do mistakes in such words).","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"f24ea2d5f6a088bf04d37d407c95e1aef3650845","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as `eth0`, exists in a particular namespace.  Linux"},{"line_number":21,"context_line":"starts up with a default network namespace, so if your OS doesn\u0027t do anything"},{"line_number":22,"context_line":"special, that\u0027s where all the network devices will be.  But it\u0027s also possible"},{"line_number":23,"context_line":"to create further non-default namespaces, and create new devices in those"},{"line_number":24,"context_line":"namespaces, or move an existing device from one namespace to another."}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_10f8ece4","line":21,"in_reply_to":"da20952f_9f6c1b0a","updated":"2015-08-26 22:44:31.000000000","message":"OK, I\u0027ll follow this in next upload.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as `eth0`, exists in a particular namespace.  Linux"},{"line_number":21,"context_line":"starts up with a default network namespace, so if your OS doesn\u0027t do anything"},{"line_number":22,"context_line":"special, that\u0027s where all the network devices will be.  But it\u0027s also possible"},{"line_number":23,"context_line":"to create further non-default namespaces, and create new devices in those"},{"line_number":24,"context_line":"namespaces, or move an existing device from one namespace to another."}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_95d2fe5a","line":21,"in_reply_to":"fa1b9901_77c1802e","updated":"2015-08-26 15:07:14.000000000","message":"1) OK, will do.\n\n2) Your suggestion sounds less natural to me.  Is there specific OpenStack doc guidance about this?","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"99cdf3bcfbd723a993f149ec2a4b90401b897ccd","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as `eth0`, exists in a particular namespace.  Linux"},{"line_number":21,"context_line":"starts up with a default network namespace, so if your OS doesn\u0027t do anything"},{"line_number":22,"context_line":"special, that\u0027s where all the network devices will be.  But it\u0027s also possible"},{"line_number":23,"context_line":"to create further non-default namespaces, and create new devices in those"},{"line_number":24,"context_line":"namespaces, or move an existing device from one namespace to another."}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_9f6c1b0a","line":21,"in_reply_to":"fa1b9901_95d2fe5a","updated":"2015-08-26 16:34:55.000000000","message":"We follow IBM Style guide conventions in OpenStack manuals where this rule mentioned (contractions can cause difficulties for translation and for users whose primary language is not English. For ex., it\u0027s can be interpreted as it is or it has etc).","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as `eth0`, exists in a particular namespace.  Linux"},{"line_number":21,"context_line":"starts up with a default network namespace, so if your OS doesn\u0027t do anything"},{"line_number":22,"context_line":"special, that\u0027s where all the network devices will be.  But it\u0027s also possible"},{"line_number":23,"context_line":"to create further non-default namespaces, and create new devices in those"},{"line_number":24,"context_line":"namespaces, or move an existing device from one namespace to another."},{"line_number":25,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_fafa5776","line":22,"updated":"2015-08-26 10:54:33.000000000","message":"1) that\u0027s -\u003e that is\n\n2) Could we replace \u0027devices will be\u0027 with devices are located\u0027?\n\n3) it\u0027s -\u003e it is","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as `eth0`, exists in a particular namespace.  Linux"},{"line_number":21,"context_line":"starts up with a default network namespace, so if your OS doesn\u0027t do anything"},{"line_number":22,"context_line":"special, that\u0027s where all the network devices will be.  But it\u0027s also possible"},{"line_number":23,"context_line":"to create further non-default namespaces, and create new devices in those"},{"line_number":24,"context_line":"namespaces, or move an existing device from one namespace to another."},{"line_number":25,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_75596afc","line":22,"in_reply_to":"fa1b9901_fafa5776","updated":"2015-08-26 15:07:14.000000000","message":"1) OK, will do.\n\n2) Good idea, thanks.\n\n3) As for \u0027doesn\u0027t\u0027 above.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":24,"context_line":"namespaces, or move an existing device from one namespace to another."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Each network namespace also has its own routing table, and in fact this is the"},{"line_number":27,"context_line":"main reason for namespaces to exist.  A routing table is keyed by destination"},{"line_number":28,"context_line":"IP address, so network namespaces are what you need if you want the same"},{"line_number":29,"context_line":"destination IP address to mean different things at different times -"},{"line_number":30,"context_line":"e.g. exactly what Neutron provides with overlapping IP addresses in different"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_1a6f0bfd","line":27,"updated":"2015-08-26 10:54:33.000000000","message":"another extra whitespace after a full stop.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":24,"context_line":"namespaces, or move an existing device from one namespace to another."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Each network namespace also has its own routing table, and in fact this is the"},{"line_number":27,"context_line":"main reason for namespaces to exist.  A routing table is keyed by destination"},{"line_number":28,"context_line":"IP address, so network namespaces are what you need if you want the same"},{"line_number":29,"context_line":"destination IP address to mean different things at different times -"},{"line_number":30,"context_line":"e.g. exactly what Neutron provides with overlapping IP addresses in different"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_d5187620","line":27,"in_reply_to":"fa1b9901_1a6f0bfd","updated":"2015-08-26 15:07:14.000000000","message":"As above.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":27,"context_line":"main reason for namespaces to exist.  A routing table is keyed by destination"},{"line_number":28,"context_line":"IP address, so network namespaces are what you need if you want the same"},{"line_number":29,"context_line":"destination IP address to mean different things at different times -"},{"line_number":30,"context_line":"e.g. exactly what Neutron provides with overlapping IP addresses in different"},{"line_number":31,"context_line":"Neutron networks."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_dd3f4db2","line":30,"updated":"2015-08-26 10:54:33.000000000","message":"e.g. -\u003e that is","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"99cdf3bcfbd723a993f149ec2a4b90401b897ccd","unresolved":false,"context_lines":[{"line_number":27,"context_line":"main reason for namespaces to exist.  A routing table is keyed by destination"},{"line_number":28,"context_line":"IP address, so network namespaces are what you need if you want the same"},{"line_number":29,"context_line":"destination IP address to mean different things at different times -"},{"line_number":30,"context_line":"e.g. exactly what Neutron provides with overlapping IP addresses in different"},{"line_number":31,"context_line":"Neutron networks."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_bf3f9fd5","line":30,"in_reply_to":"fa1b9901_357a1225","updated":"2015-08-26 16:34:55.000000000","message":"+1","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":27,"context_line":"main reason for namespaces to exist.  A routing table is keyed by destination"},{"line_number":28,"context_line":"IP address, so network namespaces are what you need if you want the same"},{"line_number":29,"context_line":"destination IP address to mean different things at different times -"},{"line_number":30,"context_line":"e.g. exactly what Neutron provides with overlapping IP addresses in different"},{"line_number":31,"context_line":"Neutron networks."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_357a1225","line":30,"in_reply_to":"fa1b9901_dd3f4db2","updated":"2015-08-26 15:07:14.000000000","message":"Thanks, I agree that \u0027e.g.\u0027 was clunky here.  I\u0027ll change to \u0027which is\u0027, though - let me know what you think.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14396,"name":"Alexander Adamov","email":"aadamov@mirantis.com","username":"Alexander"},"change_message_id":"4d566d5481f45e7ea9d9a9ebe8545cdafc646d0a","unresolved":false,"context_lines":[{"line_number":31,"context_line":"Neutron networks."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"},{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_c003070f","line":34,"updated":"2015-08-25 17:35:15.000000000","message":"So,","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":31,"context_line":"Neutron networks."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"},{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_3dbbe9e6","line":34,"updated":"2015-08-26 10:54:33.000000000","message":"extra whitespace","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":31,"context_line":"Neutron networks."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"},{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_55e546d9","line":34,"in_reply_to":"fa1b9901_3dbbe9e6","updated":"2015-08-26 15:07:14.000000000","message":"As above.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":31,"context_line":"Neutron networks."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"},{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_952d1e00","line":34,"in_reply_to":"fa1b9901_c003070f","updated":"2015-08-26 15:07:14.000000000","message":"Thanks, will do.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":7244,"name":"Victor Howard","email":"victor.r.howard@gmail.com","username":"vichoward"},"change_message_id":"808ab28ad1240e0018f1cc9eff2c5bc03aa3fa2d","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"},{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_3ab69d3e","line":35,"updated":"2015-08-26 04:33:14.000000000","message":"I would just take So out completely","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":10897,"name":"Joseph Robinson","email":"josephremail@gmail.com","username":"RobiJoe"},"change_message_id":"898c0fecde86834c441d035b697269c63a2518c1","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"},{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_fb9587e3","line":35,"updated":"2015-08-26 06:23:15.000000000","message":"Line 34: Switch to active voice here:\n\n\"You can apply different security to flows with the same IP addressing in different namespaces, similar to different routing security.\"","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"},{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_35521268","line":35,"in_reply_to":"fa1b9901_3ab69d3e","updated":"2015-08-26 15:07:14.000000000","message":"I\u0027d rather keep it.  Please take another look, with all the other changes in the next upload.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"},{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_15702e0a","line":35,"in_reply_to":"fa1b9901_fb9587e3","updated":"2015-08-26 15:07:14.000000000","message":"Thanks, good idea.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14396,"name":"Alexander Adamov","email":"aadamov@mirantis.com","username":"Alexander"},"change_message_id":"4d566d5481f45e7ea9d9a9ebe8545cdafc646d0a","unresolved":false,"context_lines":[{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_9b2ca49a","line":37,"updated":"2015-08-25 17:35:15.000000000","message":"By default,","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_5dbc9dba","line":37,"updated":"2015-08-26 10:54:33.000000000","message":"extra whitespace","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_3500d233","line":37,"in_reply_to":"fa1b9901_5dbc9dba","updated":"2015-08-26 15:07:14.000000000","message":"As above.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":34,"context_line":"IPv6).  So different security can be applied to flows with the same IP"},{"line_number":35,"context_line":"addressing in different namespaces, just as different routing can be."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_55e6a6b0","line":37,"in_reply_to":"fa1b9901_9b2ca49a","updated":"2015-08-26 15:07:14.000000000","message":"In this case, I think the sentence flows better without the comma.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14396,"name":"Alexander Adamov","email":"aadamov@mirantis.com","username":"Alexander"},"change_message_id":"4d566d5481f45e7ea9d9a9ebe8545cdafc646d0a","unresolved":false,"context_lines":[{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_20af632b","line":40,"updated":"2015-08-25 17:35:15.000000000","message":"using the :command:`ip netns exec NETNS COMMAND...`","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"1a641b7c18c155ec500f1fdd23201b1846d9d67c","unresolved":false,"context_lines":[{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_24f60090","line":40,"in_reply_to":"da20952f_10e22c04","updated":"2015-08-27 08:05:49.000000000","message":"The rst.ninjs.org doesn\u0027t have the same rules as we do (a lot of other markups don\u0027t work on this website either). The best way to ensure whether some markup works in openstack manuals is check your build locally. I can confirm that the :command:`..` works fine here. The only thing I am not sure whether the name of the command itself is accurate.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"59805af8c2bc66d089f79eb440c197754d692e4a","unresolved":false,"context_lines":[{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_e13f9523","line":40,"in_reply_to":"da20952f_24f60090","updated":"2015-08-27 09:32:20.000000000","message":"Thanks Olena.  Local build is working for me now.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"f24ea2d5f6a088bf04d37d407c95e1aef3650845","unresolved":false,"context_lines":[{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_10e22c04","line":40,"in_reply_to":"da20952f_42eea8ed","updated":"2015-08-26 22:44:31.000000000","message":"I tried entering that at rst.ninjs.org, and it reports a syntax error:\n\nSystem Message: ERROR/3 (\u003cstring\u003e, line 1); backlink\nUnknown interpreted text role \"command\".\n\nI also tried it with rst2html, and it didn\u0027t produce any noticeable markup.\n\nSo, I still don\u0027t think I\u0027m correctly understanding what Alex was suggesting here.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_7545ea6c","line":40,"in_reply_to":"fa1b9901_20af632b","updated":"2015-08-26 15:07:14.000000000","message":"Do you mean just \u0027command\u0027 instead of \u0027invocation\u0027, or is there also a nice RST syntax idea here?  I\u0027m afraid that the latter might have got lost, as a consequence of Gerrit interpreting RST as well.\n\nI\u0027ll leave this text as is for now, but please do clarify what you meant.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"99cdf3bcfbd723a993f149ec2a4b90401b897ccd","unresolved":false,"context_lines":[{"line_number":37,"context_line":"Any given Linux process runs in a particular network namespace.  By default"},{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_42eea8ed","line":40,"in_reply_to":"fa1b9901_7545ea6c","updated":"2015-08-26 16:34:55.000000000","message":"I guess Alex meant a special markup here, i.e., :command:`ip netns exec NETNS COMMAND...` invocation","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14396,"name":"Alexander Adamov","email":"aadamov@mirantis.com","username":"Alexander"},"change_message_id":"4d566d5481f45e7ea9d9a9ebe8545cdafc646d0a","unresolved":false,"context_lines":[{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"},{"line_number":44,"context_line":"determine the network device that the message is transmitted through."}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_c055471e","line":41,"updated":"2015-08-25 17:35:15.000000000","message":"Suppose,","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":14962,"name":"ologvinova","email":"ologvinova@mirantis.com","username":"ologvinova"},"change_message_id":"4eff7adec4758e3f288dd02309342dde161066d8","unresolved":false,"context_lines":[{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"},{"line_number":44,"context_line":"determine the network device that the message is transmitted through."}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_3d7a09f2","line":41,"updated":"2015-08-26 10:54:33.000000000","message":"extra whitespace","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"},{"line_number":44,"context_line":"determine the network device that the message is transmitted through."}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_984f956a","line":41,"in_reply_to":"fa1b9901_3d7a09f2","updated":"2015-08-26 15:07:14.000000000","message":"As above.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"fb32d6295805fe976729e38cefc6f8077895d39f","unresolved":false,"context_lines":[{"line_number":38,"context_line":"this is inherited from its parent process, but a process with the right"},{"line_number":39,"context_line":"capabilities can switch itself into a different namespace; in practice this is"},{"line_number":40,"context_line":"mostly done using the `ip netns exec NETNS COMMAND...` invocation, which starts"},{"line_number":41,"context_line":"`COMMAND` running in the namespace named `NETNS`.  Suppose such a process sends"},{"line_number":42,"context_line":"out a message to IP address A.B.C.D, the effect of the namespace is that"},{"line_number":43,"context_line":"A.B.C.D will be looked up in that namespace\u0027s routing table, and that will"},{"line_number":44,"context_line":"determine the network device that the message is transmitted through."}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa1b9901_9828f587","line":41,"in_reply_to":"fa1b9901_c055471e","updated":"2015-08-26 15:07:14.000000000","message":"That would sound very wrong to me.  The sentence should not pause at that point.","commit_id":"e8d2f4d356bc0e63dfcc1cdaa632d65f23dc8e1e"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"3a12bf67d8995e4844dac67f1ad12dc39012050c","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"},{"line_number":12,"context_line":"see and communicate with other processes in the same namespace.  So, if a shell"},{"line_number":13,"context_line":"in a particular process namespace ran ``ps waux``, it would only show the other"},{"line_number":14,"context_line":"processes in the same namespace."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_c298736d","line":12,"updated":"2015-08-26 18:17:57.000000000","message":"Documentation team uses single spaces everywhere - but we\u0027re not enforcing it. Next time please follow our style - or when you update.","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"766acd7a6617bfe6dee37bb1852c6e46b2f8c673","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"},{"line_number":12,"context_line":"see and communicate with other processes in the same namespace.  So, if a shell"},{"line_number":13,"context_line":"in a particular process namespace ran ``ps waux``, it would only show the other"},{"line_number":14,"context_line":"processes in the same namespace."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_cda09b93","line":12,"in_reply_to":"da20952f_c298736d","updated":"2015-08-26 22:25:49.000000000","message":"I\u0027m happy to follow established conventions where they exist and are documented, but I don\u0027t see this at https://wiki.openstack.org/wiki/Documentation/Conventions.  Am I looking at the right place?","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"a6bd7b26b3814006cd8a517e7a508f079fac6dbd","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"For example, Linux provides namespaces for networking and processes, among"},{"line_number":11,"context_line":"other things.  If a process is running within a process namespace, it can only"},{"line_number":12,"context_line":"see and communicate with other processes in the same namespace.  So, if a shell"},{"line_number":13,"context_line":"in a particular process namespace ran ``ps waux``, it would only show the other"},{"line_number":14,"context_line":"processes in the same namespace."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_d06594e1","line":12,"in_reply_to":"da20952f_cda09b93","updated":"2015-08-26 22:37:37.000000000","message":"I\u0027ve found this convention now in the IBM style guide, so will follow it in next upload.","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"3a12bf67d8995e4844dac67f1ad12dc39012050c","unresolved":false,"context_lines":[{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as ``eth0``, exists in a particular namespace."},{"line_number":21,"context_line":"Linux starts up with a default network namespace, so if your operating system"},{"line_number":22,"context_line":"doesn\u0027t do anything special, that is where all the network devices will be"},{"line_number":23,"context_line":"located.  But it\u0027s also possible to create further non-default namespaces, and"},{"line_number":24,"context_line":"create new devices in those namespaces, or to move an existing device from one"},{"line_number":25,"context_line":"namespace to another."}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_c2af137c","line":22,"updated":"2015-08-26 18:17:57.000000000","message":"doesn\u0027t -\u003e does not as per style guides","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"a6bd7b26b3814006cd8a517e7a508f079fac6dbd","unresolved":false,"context_lines":[{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as ``eth0``, exists in a particular namespace."},{"line_number":21,"context_line":"Linux starts up with a default network namespace, so if your operating system"},{"line_number":22,"context_line":"doesn\u0027t do anything special, that is where all the network devices will be"},{"line_number":23,"context_line":"located.  But it\u0027s also possible to create further non-default namespaces, and"},{"line_number":24,"context_line":"create new devices in those namespaces, or to move an existing device from one"},{"line_number":25,"context_line":"namespace to another."}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_50a0a4f4","line":22,"in_reply_to":"da20952f_6dc4ef3f","updated":"2015-08-26 22:37:37.000000000","message":"I\u0027ve found this convention now in the IBM style guide, so will follow it in next upload.","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"766acd7a6617bfe6dee37bb1852c6e46b2f8c673","unresolved":false,"context_lines":[{"line_number":19,"context_line":"In a network namespace, the scoped \u0027identifiers\u0027 are network devices; so a"},{"line_number":20,"context_line":"given network device, such as ``eth0``, exists in a particular namespace."},{"line_number":21,"context_line":"Linux starts up with a default network namespace, so if your operating system"},{"line_number":22,"context_line":"doesn\u0027t do anything special, that is where all the network devices will be"},{"line_number":23,"context_line":"located.  But it\u0027s also possible to create further non-default namespaces, and"},{"line_number":24,"context_line":"create new devices in those namespaces, or to move an existing device from one"},{"line_number":25,"context_line":"namespace to another."}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_6dc4ef3f","line":22,"in_reply_to":"da20952f_c2af137c","updated":"2015-08-26 22:25:49.000000000","message":"Same again.  Happy to follow this if it\u0027s documented somewhere; but I don\u0027t see it.","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"b271c1baa1f4684a6d7a017df3c8a5d5d324a97d","unresolved":false,"context_lines":[{"line_number":20,"context_line":"given network device, such as ``eth0``, exists in a particular namespace."},{"line_number":21,"context_line":"Linux starts up with a default network namespace, so if your operating system"},{"line_number":22,"context_line":"doesn\u0027t do anything special, that is where all the network devices will be"},{"line_number":23,"context_line":"located.  But it\u0027s also possible to create further non-default namespaces, and"},{"line_number":24,"context_line":"create new devices in those namespaces, or to move an existing device from one"},{"line_number":25,"context_line":"namespace to another."},{"line_number":26,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_33b5f5cc","line":23,"updated":"2015-08-27 01:43:13.000000000","message":"it is* as well :)","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"f2c722562452c79d7fe6903091a45d336e7b99b8","unresolved":false,"context_lines":[{"line_number":20,"context_line":"given network device, such as ``eth0``, exists in a particular namespace."},{"line_number":21,"context_line":"Linux starts up with a default network namespace, so if your operating system"},{"line_number":22,"context_line":"doesn\u0027t do anything special, that is where all the network devices will be"},{"line_number":23,"context_line":"located.  But it\u0027s also possible to create further non-default namespaces, and"},{"line_number":24,"context_line":"create new devices in those namespaces, or to move an existing device from one"},{"line_number":25,"context_line":"namespace to another."},{"line_number":26,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_812b3982","line":23,"in_reply_to":"da20952f_33b5f5cc","updated":"2015-08-27 09:19:21.000000000","message":"Sure, will do, thanks.","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"3a12bf67d8995e4844dac67f1ad12dc39012050c","unresolved":false,"context_lines":[{"line_number":28,"context_line":"main reason for namespaces to exist.  A routing table is keyed by destination"},{"line_number":29,"context_line":"IP address, so network namespaces are what you need if you want the same"},{"line_number":30,"context_line":"destination IP address to mean different things at different times - which is"},{"line_number":31,"context_line":"exactly what Neutron requires for its feature of providing overlapping IP"},{"line_number":32,"context_line":"addresses in different Neutron networks."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_823fdb24","line":31,"updated":"2015-08-26 18:17:57.000000000","message":"neutron lower case as per conventions https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names if you use it.\n\nBut this should be Networking, also below.","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":10705,"name":"Darren Chan","email":"dazzachan@yahoo.com.au","username":"daz"},"change_message_id":"e3eca262656c6b2aea44b68cd676b3efafa882f1","unresolved":false,"context_lines":[{"line_number":28,"context_line":"main reason for namespaces to exist.  A routing table is keyed by destination"},{"line_number":29,"context_line":"IP address, so network namespaces are what you need if you want the same"},{"line_number":30,"context_line":"destination IP address to mean different things at different times - which is"},{"line_number":31,"context_line":"exactly what Neutron requires for its feature of providing overlapping IP"},{"line_number":32,"context_line":"addresses in different Neutron networks."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_164d4472","line":31,"in_reply_to":"da20952f_6df2af9c","updated":"2015-08-26 23:37:02.000000000","message":"yes, that\u0027s fine.","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"766acd7a6617bfe6dee37bb1852c6e46b2f8c673","unresolved":false,"context_lines":[{"line_number":28,"context_line":"main reason for namespaces to exist.  A routing table is keyed by destination"},{"line_number":29,"context_line":"IP address, so network namespaces are what you need if you want the same"},{"line_number":30,"context_line":"destination IP address to mean different things at different times - which is"},{"line_number":31,"context_line":"exactly what Neutron requires for its feature of providing overlapping IP"},{"line_number":32,"context_line":"addresses in different Neutron networks."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Each network namespace also has its own set of iptables (for both IPv4 and"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_6df2af9c","line":31,"in_reply_to":"da20952f_823fdb24","updated":"2015-08-26 22:25:49.000000000","message":"Thanks.\n\nI\u0027m thinking \"OpenStack Networking\".  Would that be OK?","commit_id":"ecf464f34b0a26571df5899a79efd8ed0be47353"}]}