)]}'
{"doc/source/deploy/multitenancy.rst":[{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"bec0819c98772d21b135ea65633fddb0357e6cf1","unresolved":false,"context_lines":[{"line_number":25,"context_line":"  a single layer 2 network, separated from the cleaning network;"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"- ``neutron`` interface provides tenant-defined networking by integrating with"},{"line_number":28,"context_line":"  the Networking service, while also separating tenant networks from the"},{"line_number":29,"context_line":"  provisioning and cleaning provider networks."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Configuring the Bare Metal service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa6399be_f3f6f25b","line":28,"range":{"start_line":28,"start_character":2,"end_line":28,"end_character":24},"updated":"2016-10-20 07:53:57.000000000","message":"Openstack may use different networking services, but this driver provides integration with Neutron only. I think we should left Neutron mention here: s/Networking service/Neutron Networking service/","commit_id":"95c2a7bfef7fb3b0a0b036a30bcfa0045761f99a"},{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"c73291838b0d37535031bba9483a809ad429bfa8","unresolved":false,"context_lines":[{"line_number":25,"context_line":"  a single layer 2 network, separated from the cleaning network;"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"- ``neutron`` interface provides tenant-defined networking by integrating with"},{"line_number":28,"context_line":"  the Networking service, while also separating tenant networks from the"},{"line_number":29,"context_line":"  provisioning and cleaning provider networks."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Configuring the Bare Metal service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa6399be_1b3291f2","line":28,"range":{"start_line":28,"start_character":2,"end_line":28,"end_character":24},"in_reply_to":"fa6399be_18ab7776","updated":"2016-10-20 13:38:24.000000000","message":"thanks for explanation.","commit_id":"95c2a7bfef7fb3b0a0b036a30bcfa0045761f99a"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"e7c432f22948e42d20c37d02b93990ce42583b22","unresolved":false,"context_lines":[{"line_number":25,"context_line":"  a single layer 2 network, separated from the cleaning network;"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"- ``neutron`` interface provides tenant-defined networking by integrating with"},{"line_number":28,"context_line":"  the Networking service, while also separating tenant networks from the"},{"line_number":29,"context_line":"  provisioning and cleaning provider networks."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Configuring the Bare Metal service"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa6399be_18ab7776","line":28,"range":{"start_line":28,"start_character":2,"end_line":28,"end_character":24},"in_reply_to":"fa6399be_f3f6f25b","updated":"2016-10-20 13:29:18.000000000","message":"neutron\u0027s official name is \u0027Networking service\u0027 [1], the whole idea is not to use the project names in user-facing docs and this one is meant for the future admin guide.\n\n[1] https://github.com/openstack/governance/blob/51303e779f8206792ffda6600b8445eab310d9ce/reference/projects.yaml#L2814","commit_id":"95c2a7bfef7fb3b0a0b036a30bcfa0045761f99a"},{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"bec0819c98772d21b135ea65633fddb0357e6cf1","unresolved":false,"context_lines":[{"line_number":150,"context_line":"#. The node\u0027s ``network_interface`` field should be set to a valid network"},{"line_number":151,"context_line":"   interface that is listed in the ``[DEFAULT]/enabled_network_interfaces``"},{"line_number":152,"context_line":"   configuration option in the ironic-api configuration file. Set it to"},{"line_number":153,"context_line":"   ``neutron`` to use the Network service\u0027s ML2 driver:"},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"   - ``ironic`` command::"},{"line_number":156,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa6399be_b3871ab4","line":153,"updated":"2016-10-20 07:53:57.000000000","message":"ditto about Neutron.","commit_id":"95c2a7bfef7fb3b0a0b036a30bcfa0045761f99a"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"e7c432f22948e42d20c37d02b93990ce42583b22","unresolved":false,"context_lines":[{"line_number":150,"context_line":"#. The node\u0027s ``network_interface`` field should be set to a valid network"},{"line_number":151,"context_line":"   interface that is listed in the ``[DEFAULT]/enabled_network_interfaces``"},{"line_number":152,"context_line":"   configuration option in the ironic-api configuration file. Set it to"},{"line_number":153,"context_line":"   ``neutron`` to use the Network service\u0027s ML2 driver:"},{"line_number":154,"context_line":""},{"line_number":155,"context_line":"   - ``ironic`` command::"},{"line_number":156,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa6399be_98adc786","line":153,"in_reply_to":"fa6399be_b3871ab4","updated":"2016-10-20 13:29:18.000000000","message":"ditto","commit_id":"95c2a7bfef7fb3b0a0b036a30bcfa0045761f99a"},{"author":{"_account_id":12356,"name":"Vladyslav Drok","email":"vdrok@mirantis.com","username":"vdrok"},"change_message_id":"cb3dd3fdb68eb01ca4c831afdeb7e22eb5072ac0","unresolved":false,"context_lines":[{"line_number":82,"context_line":"   Please refer to `Configure the Bare Metal service for cleaning`_ for more"},{"line_number":83,"context_line":"   information about cleaning."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"   .. warning::"},{"line_number":86,"context_line":"      Please make sure ironic is exclusive to the provisioning and cleaning"},{"line_number":87,"context_line":"      network. Spawning instances by non-admin users in these networks and"},{"line_number":88,"context_line":"      getting access to ironic control plane is a security risk. For this"},{"line_number":89,"context_line":"      reason, the provisioning and cleaning network should be configured as"},{"line_number":90,"context_line":"      non-shared network in the admin tenant."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"   .. note::"},{"line_number":93,"context_line":"      Spawning a bare metal instance onto the provisioning network is"},{"line_number":94,"context_line":"      impossible, the deployment will fail. The node should be deployed onto a"},{"line_number":95,"context_line":"      different network than the provisioning network. When you boot a bare"},{"line_number":96,"context_line":"      metal instance from nova, you should choose a different network in"},{"line_number":97,"context_line":"      neutron for your instance."},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"   .. note::"},{"line_number":100,"context_line":"      The \"provisioning\" and \"cleaning\" networks may be the same neutron"},{"line_number":101,"context_line":"      provider network, or may be distinct networks. To ensure communication"},{"line_number":102,"context_line":"      between ironic and the deploy ramdisk works, it\u0027s important to ensure"},{"line_number":103,"context_line":"      that security groups are disabled for these networks, *or* the default"},{"line_number":104,"context_line":"      security groups allow:"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"      * DHCP"},{"line_number":107,"context_line":"      * TFTP"},{"line_number":108,"context_line":"      * egress port used for ironic (6385 by default)"},{"line_number":109,"context_line":"      * ingress port used for ironic-python-agent (9999 by default)"},{"line_number":110,"context_line":"      * if using the iSCSI deploy method (``pxe_*`` and ``iscsi_*`` drivers),"},{"line_number":111,"context_line":"        the ingress port used for iSCSI (3260 by default)"},{"line_number":112,"context_line":"      * if using the direct deploy method (``agent_*`` drivers), the egress"},{"line_number":113,"context_line":"        port used for swift (typically 80 or 443)"},{"line_number":114,"context_line":"      * if using iPXE, the egress port used for the HTTP server running"},{"line_number":115,"context_line":"        on the ironic-conductor nodes (typically 80)."},{"line_number":116,"context_line":""},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"#. This step is optional and applicable only if you want to use security"},{"line_number":119,"context_line":"   groups during provisioning and/or cleaning of the nodes. If not specified,"},{"line_number":120,"context_line":"   default security groups are used."},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"   First define security groups in neutron to be used for provisioning"},{"line_number":123,"context_line":"   and/or cleaning networks. Then add the list of these security group"},{"line_number":124,"context_line":"   UUIDs under the neutron section in ironic-conductor configuration file"},{"line_number":125,"context_line":"   as shown below::"},{"line_number":126,"context_line":""},{"line_number":127,"context_line":"    [neutron]"},{"line_number":128,"context_line":"    ..."}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_6a4ba3b1","line":125,"range":{"start_line":85,"start_character":0,"end_line":125,"end_character":19},"updated":"2016-12-21 16:07:41.000000000","message":"These bits need updating too :( there are ironic, neutron, nova, swift mentions here.","commit_id":"e60144fa51a4b42882f447569427695a401bca19"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"b5ba9352a28fbaeab7120cf15835acb6c3c4a6a8","unresolved":false,"context_lines":[{"line_number":82,"context_line":"   Please refer to `Configure the Bare Metal service for cleaning`_ for more"},{"line_number":83,"context_line":"   information about cleaning."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"   .. warning::"},{"line_number":86,"context_line":"      Please make sure ironic is exclusive to the provisioning and cleaning"},{"line_number":87,"context_line":"      network. Spawning instances by non-admin users in these networks and"},{"line_number":88,"context_line":"      getting access to ironic control plane is a security risk. For this"},{"line_number":89,"context_line":"      reason, the provisioning and cleaning network should be configured as"},{"line_number":90,"context_line":"      non-shared network in the admin tenant."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"   .. note::"},{"line_number":93,"context_line":"      Spawning a bare metal instance onto the provisioning network is"},{"line_number":94,"context_line":"      impossible, the deployment will fail. The node should be deployed onto a"},{"line_number":95,"context_line":"      different network than the provisioning network. When you boot a bare"},{"line_number":96,"context_line":"      metal instance from nova, you should choose a different network in"},{"line_number":97,"context_line":"      neutron for your instance."},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"   .. note::"},{"line_number":100,"context_line":"      The \"provisioning\" and \"cleaning\" networks may be the same neutron"},{"line_number":101,"context_line":"      provider network, or may be distinct networks. To ensure communication"},{"line_number":102,"context_line":"      between ironic and the deploy ramdisk works, it\u0027s important to ensure"},{"line_number":103,"context_line":"      that security groups are disabled for these networks, *or* the default"},{"line_number":104,"context_line":"      security groups allow:"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"      * DHCP"},{"line_number":107,"context_line":"      * TFTP"},{"line_number":108,"context_line":"      * egress port used for ironic (6385 by default)"},{"line_number":109,"context_line":"      * ingress port used for ironic-python-agent (9999 by default)"},{"line_number":110,"context_line":"      * if using the iSCSI deploy method (``pxe_*`` and ``iscsi_*`` drivers),"},{"line_number":111,"context_line":"        the ingress port used for iSCSI (3260 by default)"},{"line_number":112,"context_line":"      * if using the direct deploy method (``agent_*`` drivers), the egress"},{"line_number":113,"context_line":"        port used for swift (typically 80 or 443)"},{"line_number":114,"context_line":"      * if using iPXE, the egress port used for the HTTP server running"},{"line_number":115,"context_line":"        on the ironic-conductor nodes (typically 80)."},{"line_number":116,"context_line":""},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"#. This step is optional and applicable only if you want to use security"},{"line_number":119,"context_line":"   groups during provisioning and/or cleaning of the nodes. If not specified,"},{"line_number":120,"context_line":"   default security groups are used."},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"   First define security groups in neutron to be used for provisioning"},{"line_number":123,"context_line":"   and/or cleaning networks. Then add the list of these security group"},{"line_number":124,"context_line":"   UUIDs under the neutron section in ironic-conductor configuration file"},{"line_number":125,"context_line":"   as shown below::"},{"line_number":126,"context_line":""},{"line_number":127,"context_line":"    [neutron]"},{"line_number":128,"context_line":"    ..."}],"source_content_type":"text/x-rst","patch_set":3,"id":"da4df55a_912b5c33","line":125,"range":{"start_line":85,"start_character":0,"end_line":125,"end_character":19},"in_reply_to":"1a6eadb0_6a4ba3b1","updated":"2016-12-21 19:24:30.000000000","message":"I didn\u0027t want to read those because I don\u0027t like all those NOTEs etc. Sigh, I\u0027m trying hard not to look :)","commit_id":"e60144fa51a4b42882f447569427695a401bca19"},{"author":{"_account_id":14826,"name":"Mark Goddard","email":"markgoddard86@gmail.com","username":"mgoddard"},"change_message_id":"acb7ca8b7fcd9704edda39cff4655913947aefba","unresolved":false,"context_lines":[{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Below is an example flow of how to set up the Bare Metal service so that node"},{"line_number":35,"context_line":"provisioning will happen in a multi-tenant environment (which means using"},{"line_number":36,"context_line":"``neutron`` network interface as stated above):"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"#. Network interfaces can be enabled on ironic-conductor by adding them to the"},{"line_number":39,"context_line":"   ``enabled_network_interfaces`` configuration option under the ``default``"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a3905b3_ff0ab01e","line":36,"updated":"2017-01-24 17:48:58.000000000","message":"nit: the ``neutron``","commit_id":"7556dc6a76e011ae08b5a05f9bda29831cf4fac5"},{"author":{"_account_id":14826,"name":"Mark Goddard","email":"markgoddard86@gmail.com","username":"mgoddard"},"change_message_id":"acb7ca8b7fcd9704edda39cff4655913947aefba","unresolved":false,"context_lines":[{"line_number":69,"context_line":""},{"line_number":70,"context_line":"#. Define a provider network in the Networking service, which we shall refer to"},{"line_number":71,"context_line":"   as the \"provisioning\" network, and add it in the ``neutron`` section of"},{"line_number":72,"context_line":"   the ironic-conductor configuration file. Using ``neutron`` network interface"},{"line_number":73,"context_line":"   requires that ``provisioning_network`` and ``cleaning_network``"},{"line_number":74,"context_line":"   configuration options are set to valid Networking service\u0027s network"},{"line_number":75,"context_line":"   identifiers (UUID or name); otherwise cleaning or provisioning will fail to"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a3905b3_1fc77c96","line":72,"updated":"2017-01-24 17:48:58.000000000","message":"using the ``neutron``","commit_id":"7556dc6a76e011ae08b5a05f9bda29831cf4fac5"},{"author":{"_account_id":14826,"name":"Mark Goddard","email":"markgoddard86@gmail.com","username":"mgoddard"},"change_message_id":"acb7ca8b7fcd9704edda39cff4655913947aefba","unresolved":false,"context_lines":[{"line_number":72,"context_line":"   the ironic-conductor configuration file. Using ``neutron`` network interface"},{"line_number":73,"context_line":"   requires that ``provisioning_network`` and ``cleaning_network``"},{"line_number":74,"context_line":"   configuration options are set to valid Networking service\u0027s network"},{"line_number":75,"context_line":"   identifiers (UUID or name); otherwise cleaning or provisioning will fail to"},{"line_number":76,"context_line":"   start::"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"    [neutron]"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a3905b3_1f75bc62","line":75,"updated":"2017-01-24 17:48:58.000000000","message":"\"valid identifiers (UUID or name) of networks in the Networking service. If these options are not set correctly, cleaning or provisioning will fail to start::\"?","commit_id":"7556dc6a76e011ae08b5a05f9bda29831cf4fac5"},{"author":{"_account_id":14826,"name":"Mark Goddard","email":"markgoddard86@gmail.com","username":"mgoddard"},"change_message_id":"acb7ca8b7fcd9704edda39cff4655913947aefba","unresolved":false,"context_lines":[{"line_number":122,"context_line":"   default security groups are used."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"   First define security groups in the Networking service, to be used for"},{"line_number":125,"context_line":"   provisioning and/or cleaning networks. Then add the list of these security"},{"line_number":126,"context_line":"   group UUIDs under the ``neutron`` section of ironic-conductor\u0027s"},{"line_number":127,"context_line":"   configuration file as shown below::"},{"line_number":128,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a3905b3_fa9abe60","line":125,"updated":"2017-01-24 17:48:58.000000000","message":"Could we be explicit about the list syntax here?","commit_id":"7556dc6a76e011ae08b5a05f9bda29831cf4fac5"}]}