)]}'
{"doc/source/admin/drivers.rst":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":2,"context_line":"Drivers, Hardware Types and Hardware Interfaces"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Ironic-Python-Agent (agent)"},{"line_number":6,"context_line":"---------------------------"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Ironic-Python-Agent is an agent that handles *ironic* bare metal"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_8db3a598","line":5,"updated":"2017-11-15 17:24:26.000000000","message":"is this a \u0027driver\u0027, \u0027hardware type\u0027 or \u0027hardware interface\u0027 :-(\n\nIf we keep it here, maybe we ought to clarify what it\u0027s role is -- \u0027direct\u0027 deploy hardware interface ?","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":2,"context_line":"Drivers, Hardware Types and Hardware Interfaces"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Ironic-Python-Agent (agent)"},{"line_number":6,"context_line":"---------------------------"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Ironic-Python-Agent is an agent that handles *ironic* bare metal"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_ab4a2b52","line":5,"in_reply_to":"1f485f77_8db3a598","updated":"2017-11-22 13:57:05.000000000","message":"Well... it\u0027s neither. Maybe we should move this to the top admin page? Oh, we actually have it there. Removing from here.","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  interfaces/boot"},{"line_number":24,"context_line":"  interfaces/deploy"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Drivers and Hardware Types"},{"line_number":27,"context_line":"--------------------------"},{"line_number":28,"context_line":""},{"line_number":29,"context_line":".. toctree::"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_683a97cc","line":26,"updated":"2017-11-15 17:24:26.000000000","message":"I think the problem is that we\u0027re using different terminology. We use \u0027classic driver\u0027 and hardware type.\n\nBy \u0027drivers\u0027 here, we are providing links to the vendors\u0027 \"drivers\", which to me, map to what we are calling hardware types. Can we get rid of \u0027drivers\u0027 or will it be confusing if we do that? We have these hardware types (from setup.cfg):\ncisco-ucs-managed \ncisco-ucs-standalone \nfake-hardware \nidrac \nilo \nipmi \nirmc \nmanual-management \noneview \nredfish \nsnmp","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":23,"context_line":"  interfaces/boot"},{"line_number":24,"context_line":"  interfaces/deploy"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Drivers and Hardware Types"},{"line_number":27,"context_line":"--------------------------"},{"line_number":28,"context_line":""},{"line_number":29,"context_line":".. toctree::"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_6b9bc3c8","line":26,"in_reply_to":"1f485f77_683a97cc","updated":"2017-11-22 13:57:05.000000000","message":"Done","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":40,"context_line":"  drivers/ucs"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Unsupported drivers"},{"line_number":44,"context_line":"-------------------"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The following drivers were declared as unsupported in ironic Newton release"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_a872cfab","line":43,"updated":"2017-11-15 17:24:26.000000000","message":"Unsupported classic drivers? Or we can leave it I guess...","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":40,"context_line":"  drivers/ucs"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Unsupported drivers"},{"line_number":44,"context_line":"-------------------"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The following drivers were declared as unsupported in ironic Newton release"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_8b872762","line":43,"in_reply_to":"1f485f77_a872cfab","updated":"2017-11-22 13:57:05.000000000","message":"Yes, let\u0027s maybe just leave it..","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":44,"context_line":"-------------------"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The following drivers were declared as unsupported in ironic Newton release"},{"line_number":47,"context_line":"and as of Ocata release they are removed form ironic:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"- AMT driver - available as part of ironic-staging-drivers_"},{"line_number":50,"context_line":"- iBoot driver - available as part of ironic-staging-drivers_"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_686857b8","line":47,"updated":"2017-11-15 17:24:26.000000000","message":"ouch s/form/from/ :D","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":44,"context_line":"-------------------"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The following drivers were declared as unsupported in ironic Newton release"},{"line_number":47,"context_line":"and as of Ocata release they are removed form ironic:"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"- AMT driver - available as part of ironic-staging-drivers_"},{"line_number":50,"context_line":"- iBoot driver - available as part of ironic-staging-drivers_"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_4b811f4a","line":47,"in_reply_to":"1f485f77_686857b8","updated":"2017-11-22 13:57:05.000000000","message":"Done","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":51,"context_line":"- Wake-On-Lan driver - available as part of ironic-staging-drivers_"},{"line_number":52,"context_line":"- Virtualbox drivers"},{"line_number":53,"context_line":"- SeaMicro drivers"},{"line_number":54,"context_line":"- MSFT OCS drivers"},{"line_number":55,"context_line":""},{"line_number":56,"context_line":".. _ironic-staging-drivers: http://ironic-staging-drivers.readthedocs.io"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_c8f06b00","line":54,"updated":"2017-11-15 17:24:26.000000000","message":"As an aside, do we want to keep this list up to date? We also removed ssh-based ones in PIke.","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":51,"context_line":"- Wake-On-Lan driver - available as part of ironic-staging-drivers_"},{"line_number":52,"context_line":"- Virtualbox drivers"},{"line_number":53,"context_line":"- SeaMicro drivers"},{"line_number":54,"context_line":"- MSFT OCS drivers"},{"line_number":55,"context_line":""},{"line_number":56,"context_line":".. _ironic-staging-drivers: http://ironic-staging-drivers.readthedocs.io"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_cb8c4f81","line":54,"in_reply_to":"1f485f77_c8f06b00","updated":"2017-11-22 13:57:05.000000000","message":"Dunno, lemme add them","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"}],"doc/source/admin/drivers/ipa.rst":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":21,"context_line":"IPA for deployment. There are two types of them, which can be distinguished"},{"line_number":22,"context_line":"by prefix:"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"* For nodes using the :ref:`iscsi-deploy` IPA exposes the root hard"},{"line_number":25,"context_line":"  drive as an iSCSI share and calls back to the ironic conductor. The"},{"line_number":26,"context_line":"  conductor mounts the share and copies an image there. It then signals back"},{"line_number":27,"context_line":"  to IPA for post-installation actions like setting up a bootloader for local"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_fc0be8d2","line":24,"updated":"2017-11-15 17:24:26.000000000","message":"maybe s/IPA/interface, IPA/","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":21,"context_line":"IPA for deployment. There are two types of them, which can be distinguished"},{"line_number":22,"context_line":"by prefix:"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"* For nodes using the :ref:`iscsi-deploy` IPA exposes the root hard"},{"line_number":25,"context_line":"  drive as an iSCSI share and calls back to the ironic conductor. The"},{"line_number":26,"context_line":"  conductor mounts the share and copies an image there. It then signals back"},{"line_number":27,"context_line":"  to IPA for post-installation actions like setting up a bootloader for local"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_0b46b722","line":24,"in_reply_to":"1f485f77_fc0be8d2","updated":"2017-11-22 13:57:05.000000000","message":"Done","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"}],"doc/source/admin/index.rst":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":9,"context_line":"  :maxdepth: 1"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"   Enabling Drivers \u003cdrivers\u003e"},{"line_number":12,"context_line":"   Deploy Interfaces \u003cinterfaces/deploy\u003e"},{"line_number":13,"context_line":"   Ironic Python Agent \u003cdrivers/ipa\u003e"},{"line_number":14,"context_line":"   Node Hardware Inspection \u003cinspection\u003e"},{"line_number":15,"context_line":"   Node Cleaning \u003ccleaning\u003e"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_1567694f","line":12,"updated":"2017-11-06 16:21:10.000000000","message":"Hmm. I\u0027m worried that we\u0027re getting into a big mess. One of the problems is the above \u0027Enabling Drivers\u0027 is not about how to enable drivers, but is a description of the drivers themselves. If that had been called eg. Drivers and Hardware Types, maybe it would make more sense for this one to be Hardware Interfaces. Where Hardware Interfaces could have subsections for the diff interfaces, and/or link from there to a Deploy Interface or any other interface that we feel may require it\u0027s own page? I\u0027m concerned about putting Deploy Interfaces at this level; if we decided to add separate pages for other interfaces, this level will get very cluttered. What do you think?","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":9,"context_line":"  :maxdepth: 1"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"   Enabling Drivers \u003cdrivers\u003e"},{"line_number":12,"context_line":"   Deploy Interfaces \u003cinterfaces/deploy\u003e"},{"line_number":13,"context_line":"   Ironic Python Agent \u003cdrivers/ipa\u003e"},{"line_number":14,"context_line":"   Node Hardware Inspection \u003cinspection\u003e"},{"line_number":15,"context_line":"   Node Cleaning \u003ccleaning\u003e"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_041210b2","line":12,"in_reply_to":"3f4b6375_1567694f","updated":"2017-11-14 19:23:43.000000000","message":"Sigh, yes. I guess it\u0027s the time to rework the drivers page.","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6637,"name":"Sam Betts","email":"sam@code-smash.net","username":"sambetts"},"change_message_id":"922209f32eeed882bbcc1cf2e672ab243efbfb83","unresolved":false,"context_lines":[{"line_number":8,"context_line":".. toctree::"},{"line_number":9,"context_line":"  :maxdepth: 1"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"   Drivers, Hardware Types and Hardware Interfaces \u003cdrivers\u003e"},{"line_number":12,"context_line":"   Ironic Python Agent \u003cdrivers/ipa\u003e"},{"line_number":13,"context_line":"   Node Hardware Inspection \u003cinspection\u003e"},{"line_number":14,"context_line":"   Node Cleaning \u003ccleaning\u003e"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ff82abbf_2479f692","line":11,"range":{"start_line":11,"start_character":3,"end_line":11,"end_character":50},"updated":"2017-11-28 13:44:19.000000000","message":"There is really no need to write the title out again, because just specifying \"drivers\" it\u0027ll pull the title from the drivers page.","commit_id":"f02ef8ad7a8d993bbd62780a8da6e66a6a0a1cf6"}],"doc/source/admin/interfaces/boot.rst":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":24,"context_line":"The ``pxe`` boot interface works by preparing a PXE/iPXE environment for a"},{"line_number":25,"context_line":"node on the file system, then instructing the DHCP provider (for example,"},{"line_number":26,"context_line":"the Networking service) to boot the node from it. See"},{"line_number":27,"context_line":":ref:`iscsi-deploy-example` and :ref:`direct-deploy-example` for better"},{"line_number":28,"context_line":"understanding of the whole deployment process."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":".. note::"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_3cbaa009","line":27,"updated":"2017-11-15 17:24:26.000000000","message":"nit s/for better/for a better/","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":24,"context_line":"The ``pxe`` boot interface works by preparing a PXE/iPXE environment for a"},{"line_number":25,"context_line":"node on the file system, then instructing the DHCP provider (for example,"},{"line_number":26,"context_line":"the Networking service) to boot the node from it. See"},{"line_number":27,"context_line":":ref:`iscsi-deploy-example` and :ref:`direct-deploy-example` for better"},{"line_number":28,"context_line":"understanding of the whole deployment process."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":".. note::"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_ab546bcb","line":27,"in_reply_to":"1f485f77_3cbaa009","updated":"2017-11-22 13:57:05.000000000","message":"Done","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":11076,"name":"Shivanand Tendulker","email":"stendulker@gmail.com","username":"stendulker"},"change_message_id":"7bbf0fee3f4395a9ef2f00a3838e7a3fd9b62b77","unresolved":false,"context_lines":[{"line_number":9,"context_line":"booting from network. Alternatively, several vendors provide *virtual media*"},{"line_number":10,"context_line":"implementations of the boot interface. They work by pushing an ISO image to"},{"line_number":11,"context_line":"the node\u0027s `management controller`_, and do not require either PXE or iPXE."},{"line_number":12,"context_line":"Check your driver documentation at :doc:`../drivers` for details."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":".. _pxe-boot:"},{"line_number":15,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"ff82abbf_c88f1fcb","line":12,"range":{"start_line":12,"start_character":35,"end_line":12,"end_character":52},"updated":"2017-11-27 13:38:15.000000000","message":"nit: Would it be better to give this link to \u0027Hardware Types\u0027 instead of just to main page?","commit_id":"f02ef8ad7a8d993bbd62780a8da6e66a6a0a1cf6"}],"doc/source/admin/interfaces/deploy.rst":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":2,"context_line":"Deploy Interfaces"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"A *deploy* interface plays critical role in the provisioning process. It"},{"line_number":6,"context_line":"orchestrates the whole deployment and defines how the image gets transferred"},{"line_number":7,"context_line":"to the target disk."},{"line_number":8,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_95523966","line":5,"updated":"2017-11-06 16:21:10.000000000","message":"nit s/plays/plays a/","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":2,"context_line":"Deploy Interfaces"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"A *deploy* interface plays critical role in the provisioning process. It"},{"line_number":6,"context_line":"orchestrates the whole deployment and defines how the image gets transferred"},{"line_number":7,"context_line":"to the target disk."},{"line_number":8,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_64f1c46b","line":5,"in_reply_to":"3f4b6375_95523966","updated":"2017-11-14 19:23:43.000000000","message":"Done","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":".. _iscsi-deploy:"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"iSCSI deploy"},{"line_number":12,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"With ``iscsi`` deploy interface (and also ``oneview-iscsi``, specific to the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_38393ca3","line":11,"updated":"2017-11-06 16:21:10.000000000","message":"I know this is the default, but do we \u0027prefer\u0027 one over the other? Wondering about whether we want iscii first, or direct first.","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":".. _iscsi-deploy:"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"iSCSI deploy"},{"line_number":12,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"With ``iscsi`` deploy interface (and also ``oneview-iscsi``, specific to the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_c4ff5832","line":11,"in_reply_to":"3f4b6375_38393ca3","updated":"2017-11-14 19:23:43.000000000","message":"I\u0027m putting it first because it\u0027s the default, yes. We explain our preference in the refarch guide","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":12,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"With ``iscsi`` deploy interface (and also ``oneview-iscsi``, specific to the"},{"line_number":15,"context_line":"``oneview`` hardware type) the deploy ramdisk publishes node\u0027s hard drive"},{"line_number":16,"context_line":"as an iSCSI_ share. The ironic-conductor then copies the image to this share."},{"line_number":17,"context_line":"See :ref:`iSCSI deploy diagram \u003ciscsi-deploy-example\u003e` for a detailed"},{"line_number":18,"context_line":"explanation of how this deploy interface works."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_f59ccd0e","line":15,"updated":"2017-11-06 16:21:10.000000000","message":"nit s/publishes/publishes the/","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":12,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"With ``iscsi`` deploy interface (and also ``oneview-iscsi``, specific to the"},{"line_number":15,"context_line":"``oneview`` hardware type) the deploy ramdisk publishes node\u0027s hard drive"},{"line_number":16,"context_line":"as an iSCSI_ share. The ironic-conductor then copies the image to this share."},{"line_number":17,"context_line":"See :ref:`iSCSI deploy diagram \u003ciscsi-deploy-example\u003e` for a detailed"},{"line_number":18,"context_line":"explanation of how this deploy interface works."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_a4fe9c34","line":15,"in_reply_to":"3f4b6375_f59ccd0e","updated":"2017-11-14 19:23:43.000000000","message":"Done","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":17,"context_line":"See :ref:`iSCSI deploy diagram \u003ciscsi-deploy-example\u003e` for a detailed"},{"line_number":18,"context_line":"explanation of how this deploy interface works."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"This interface is used by default, if enabled. You can specify it explicitly"},{"line_number":21,"context_line":"when creating or updating a node::"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"    openstack baremetal node create --driver ipmi --deploy-interface iscsi"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_75fb3d46","line":20,"updated":"2017-11-06 16:21:10.000000000","message":"I wonder if we should add a link for \u0027if enabled\u0027.","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":17,"context_line":"See :ref:`iSCSI deploy diagram \u003ciscsi-deploy-example\u003e` for a detailed"},{"line_number":18,"context_line":"explanation of how this deploy interface works."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"This interface is used by default, if enabled. You can specify it explicitly"},{"line_number":21,"context_line":"when creating or updating a node::"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"    openstack baremetal node create --driver ipmi --deploy-interface iscsi"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_24a06c43","line":20,"in_reply_to":"3f4b6375_75fb3d46","updated":"2017-11-14 19:23:43.000000000","message":"Done","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    openstack baremetal node create --driver ipmi --deploy-interface iscsi"},{"line_number":24,"context_line":"    openstack baremetal node set \u003cNODE\u003e --deploy-interface iscsi"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"The ``iscsi`` deploy interface is also used in the most of *classic drivers*"},{"line_number":27,"context_line":"with names starting with ``pxe_`` (except for ``pxe_agent_cimc``)"},{"line_number":28,"context_line":"and ``iscsi_``."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_7590dded","line":26,"updated":"2017-11-06 16:21:10.000000000","message":"s/in the most of/in all of the/\n\nbecause you mention the only exception at L27","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":23,"context_line":"    openstack baremetal node create --driver ipmi --deploy-interface iscsi"},{"line_number":24,"context_line":"    openstack baremetal node set \u003cNODE\u003e --deploy-interface iscsi"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"The ``iscsi`` deploy interface is also used in the most of *classic drivers*"},{"line_number":27,"context_line":"with names starting with ``pxe_`` (except for ``pxe_agent_cimc``)"},{"line_number":28,"context_line":"and ``iscsi_``."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_64bf8461","line":26,"in_reply_to":"3f4b6375_7590dded","updated":"2017-11-14 19:23:43.000000000","message":"Done","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    openstack baremetal node create --driver ipmi --deploy-interface direct"},{"line_number":47,"context_line":"    openstack baremetal node set \u003cNODE\u003e --deploy-interface direct"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"The ``direct`` deploy interface is also used in the most of *classic drivers*"},{"line_number":50,"context_line":"with names starting with ``agent_`` and with ``pxe_agent_cimc``."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":".. note::"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_35338516","line":49,"updated":"2017-11-06 16:21:10.000000000","message":"s/in the most of/in most of the/\n\nI looked at the upgrade table. How about\n\nThe ``direct`` deploy interface is used with all the *classic drivers* whose names start with ``agent_`` and``pxe_agent_cimc``.\n\nOr we could just say that it is \u0027used with all classic drivers whose names include \u0027agent\u0027.","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    openstack baremetal node create --driver ipmi --deploy-interface direct"},{"line_number":47,"context_line":"    openstack baremetal node set \u003cNODE\u003e --deploy-interface direct"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"The ``direct`` deploy interface is also used in the most of *classic drivers*"},{"line_number":50,"context_line":"with names starting with ``agent_`` and with ``pxe_agent_cimc``."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":".. note::"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_84a72050","line":49,"in_reply_to":"3f4b6375_35338516","updated":"2017-11-14 19:23:43.000000000","message":"Done","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":53,"context_line":"    For historical reasons the ``direct`` deploy interface is sometimes called"},{"line_number":54,"context_line":"    ``agent``, and some *classic drivers* using it are called ``agent_*``."},{"line_number":55,"context_line":"    This is because long time ago **ironic-python-agent** only supported this"},{"line_number":56,"context_line":"    deploy interface."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_7848d45a","line":56,"updated":"2017-11-06 16:21:10.000000000","message":"I\u0027m wondering if we want this note. It looks like all classic drivers that use this have \u0027agent\u0027 it their name. We don\u0027t have anything else besides ipa that supports the direct deploy interface, do we?","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":53,"context_line":"    For historical reasons the ``direct`` deploy interface is sometimes called"},{"line_number":54,"context_line":"    ``agent``, and some *classic drivers* using it are called ``agent_*``."},{"line_number":55,"context_line":"    This is because long time ago **ironic-python-agent** only supported this"},{"line_number":56,"context_line":"    deploy interface."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_a481fc91","line":56,"in_reply_to":"3f4b6375_7848d45a","updated":"2017-11-14 19:23:43.000000000","message":"This is a very common source of confusion, so I\u0027d like to elaborate on it.","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":16,"context_line":"as an iSCSI_ share. The ironic-conductor then copies the image to this share."},{"line_number":17,"context_line":"See :ref:`iSCSI deploy diagram \u003ciscsi-deploy-example\u003e` for a detailed"},{"line_number":18,"context_line":"explanation of how this deploy interface works."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"This interface is used by default, if enabled (see"},{"line_number":21,"context_line":":ref:`enable-hardware-interfaces`). You can specify it explicitly"},{"line_number":22,"context_line":"when creating or updating a node::"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_7c6818b8","line":19,"updated":"2017-11-15 17:24:26.000000000","message":"Do we want to mention \u0027Most of the deployment operations happen on the ironic-conductor.\u0027","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":16,"context_line":"as an iSCSI_ share. The ironic-conductor then copies the image to this share."},{"line_number":17,"context_line":"See :ref:`iSCSI deploy diagram \u003ciscsi-deploy-example\u003e` for a detailed"},{"line_number":18,"context_line":"explanation of how this deploy interface works."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"This interface is used by default, if enabled (see"},{"line_number":21,"context_line":":ref:`enable-hardware-interfaces`). You can specify it explicitly"},{"line_number":22,"context_line":"when creating or updating a node::"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_8b63a7b1","line":19,"in_reply_to":"1f485f77_7c6818b8","updated":"2017-11-22 13:57:05.000000000","message":"I think it will be a bit vague.. also even in the direct case the conductor does the most of the job.","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":".. _direct-deploy:"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Direct deploy"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"With ``direct`` deploy interface (and also ``oneview-direct``, specific to the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_fcd9a856","line":35,"updated":"2017-11-15 17:24:26.000000000","message":"we might want to s/Direct/direct/\n\nsince \u0027direct\u0027 is the name of this deploy. Unless you mean to use it as the word \u0027direct\u0027, not the name.","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":".. _direct-deploy:"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Direct deploy"},{"line_number":36,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"With ``direct`` deploy interface (and also ``oneview-direct``, specific to the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_0b6f9792","line":35,"in_reply_to":"1f485f77_fcd9a856","updated":"2017-11-22 13:57:05.000000000","message":"I meant to use it as a word, but I can change. then we need s/iSCSI/iscsi/ in the previous heading too, which may be a bit ugly though.","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"With ``direct`` deploy interface (and also ``oneview-direct``, specific to the"},{"line_number":39,"context_line":"``oneview`` hardware type), the deploy ramdisk fetches the image from an"},{"line_number":40,"context_line":"HTTP location. It can be an object storage temporary URL or a user-provided"},{"line_number":41,"context_line":"HTTP URL. The deploy ramdisk then copies the image to the target disk."},{"line_number":42,"context_line":"See :ref:`direct deploy diagram \u003cdirect-deploy-example\u003e` for a detailed"},{"line_number":43,"context_line":"explanation of how this deploy interface works."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_7cadb8e7","line":40,"updated":"2017-11-15 17:24:26.000000000","message":"do we want to mention s/URL/URL (swift or RadosGW)/ ?","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"With ``direct`` deploy interface (and also ``oneview-direct``, specific to the"},{"line_number":39,"context_line":"``oneview`` hardware type), the deploy ramdisk fetches the image from an"},{"line_number":40,"context_line":"HTTP location. It can be an object storage temporary URL or a user-provided"},{"line_number":41,"context_line":"HTTP URL. The deploy ramdisk then copies the image to the target disk."},{"line_number":42,"context_line":"See :ref:`direct deploy diagram \u003cdirect-deploy-example\u003e` for a detailed"},{"line_number":43,"context_line":"explanation of how this deploy interface works."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_8b0887d9","line":40,"in_reply_to":"1f485f77_7cadb8e7","updated":"2017-11-22 13:57:05.000000000","message":"Done","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":41,"context_line":"HTTP URL. The deploy ramdisk then copies the image to the target disk."},{"line_number":42,"context_line":"See :ref:`direct deploy diagram \u003cdirect-deploy-example\u003e` for a detailed"},{"line_number":43,"context_line":"explanation of how this deploy interface works."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"You can specify this deploy interface when creating or updating a node::"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"    openstack baremetal node create --driver ipmi --deploy-interface direct"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_3c8ce07d","line":44,"updated":"2017-11-15 17:24:26.000000000","message":"Do we want to mention here, (from refarch/common.rst), \u0027If the Object Storage service (swift) or RadosGW is present in the environment, it is recommended to use this interface for better scalability and reliability\u0027 ?","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":41,"context_line":"HTTP URL. The deploy ramdisk then copies the image to the target disk."},{"line_number":42,"context_line":"See :ref:`direct deploy diagram \u003cdirect-deploy-example\u003e` for a detailed"},{"line_number":43,"context_line":"explanation of how this deploy interface works."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"You can specify this deploy interface when creating or updating a node::"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"    openstack baremetal node create --driver ipmi --deploy-interface direct"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_8b3167a5","line":44,"in_reply_to":"1f485f77_3c8ce07d","updated":"2017-11-22 13:57:05.000000000","message":"I think any recommendations should stay there. I was planning to only put raw facts here.","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":53,"context_line":".. note::"},{"line_number":54,"context_line":"    For historical reasons the ``direct`` deploy interface is sometimes called"},{"line_number":55,"context_line":"    ``agent``, and some *classic drivers* using it are called ``agent_*``."},{"line_number":56,"context_line":"    This is because long time ago **ironic-python-agent** only supported this"},{"line_number":57,"context_line":"    deploy interface."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_9c3d14c6","line":56,"updated":"2017-11-15 17:24:26.000000000","message":"maybe s/long time ago//\n\ns/only supported/used to only support/\n\nBonus points if anyone remembers which release it changed!\n\nFound it, the docs mention that it changed in kilo :)","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":53,"context_line":".. note::"},{"line_number":54,"context_line":"    For historical reasons the ``direct`` deploy interface is sometimes called"},{"line_number":55,"context_line":"    ``agent``, and some *classic drivers* using it are called ``agent_*``."},{"line_number":56,"context_line":"    This is because long time ago **ironic-python-agent** only supported this"},{"line_number":57,"context_line":"    deploy interface."}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_0b1d570e","line":56,"in_reply_to":"1f485f77_9c3d14c6","updated":"2017-11-22 13:57:05.000000000","message":"Done","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"}],"doc/source/install/enabling-drivers.rst":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":72,"context_line":"    See :doc:`/admin/console` for details."},{"line_number":73,"context_line":"deploy"},{"line_number":74,"context_line":"    defines how the image gets transferred to the target disk. See"},{"line_number":75,"context_line":"    :doc:`../admin/interfaces/deploy` for explanation of the difference"},{"line_number":76,"context_line":"    between supported deploy interfaces."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"    The deploy interfaces can be enabled as follows:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_788fb474","line":75,"updated":"2017-11-06 16:21:10.000000000","message":"nit s/for explanation/for an explanation/","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":72,"context_line":"    See :doc:`/admin/console` for details."},{"line_number":73,"context_line":"deploy"},{"line_number":74,"context_line":"    defines how the image gets transferred to the target disk. See"},{"line_number":75,"context_line":"    :doc:`../admin/interfaces/deploy` for explanation of the difference"},{"line_number":76,"context_line":"    between supported deploy interfaces."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"    The deploy interfaces can be enabled as follows:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_44500833","line":75,"in_reply_to":"3f4b6375_788fb474","updated":"2017-11-14 19:23:43.000000000","message":"Done","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":73,"context_line":"deploy"},{"line_number":74,"context_line":"    defines how the image gets transferred to the target disk. See"},{"line_number":75,"context_line":"    :doc:`../admin/interfaces/deploy` for explanation of the difference"},{"line_number":76,"context_line":"    between supported deploy interfaces."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"    The deploy interfaces can be enabled as follows:"},{"line_number":79,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_f8c964ab","line":76,"updated":"2017-11-06 16:21:10.000000000","message":"Or you could say\n\nSee ... for a description of the supported deploy interfaces ``direct`` and ``iscsi``.\n\n(Since you mention those two interfaces below.)","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":73,"context_line":"deploy"},{"line_number":74,"context_line":"    defines how the image gets transferred to the target disk. See"},{"line_number":75,"context_line":"    :doc:`../admin/interfaces/deploy` for explanation of the difference"},{"line_number":76,"context_line":"    between supported deploy interfaces."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"    The deploy interfaces can be enabled as follows:"},{"line_number":79,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_0418d07e","line":76,"in_reply_to":"3f4b6375_f8c964ab","updated":"2017-11-14 19:23:43.000000000","message":"Done","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":88,"context_line":"    * the ``iscsi`` deploy interface requires :doc:`configure-iscsi`"},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"    * the ``direct`` deploy interface requires the Object Storage service"},{"line_number":91,"context_line":"      or an HTTP service"},{"line_number":92,"context_line":"inspect"},{"line_number":93,"context_line":"    implements fetching hardware information from nodes. Can be implemented"},{"line_number":94,"context_line":"    out-of-band (via contacting the node\u0027s BMC) or in-band (via booting"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_58fbd8bc","line":91,"updated":"2017-11-06 16:21:10.000000000","message":"Wondering. If we consider the new deploy interface page as \u0027the\u0027 page that describes everything you want to know about deploy interfaces, maybe we should mention this stuff there too. Or have a link from the deploy interface page, to here, wrt what is needed when installing ?","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":88,"context_line":"    * the ``iscsi`` deploy interface requires :doc:`configure-iscsi`"},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"    * the ``direct`` deploy interface requires the Object Storage service"},{"line_number":91,"context_line":"      or an HTTP service"},{"line_number":92,"context_line":"inspect"},{"line_number":93,"context_line":"    implements fetching hardware information from nodes. Can be implemented"},{"line_number":94,"context_line":"    out-of-band (via contacting the node\u0027s BMC) or in-band (via booting"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_842a808d","line":91,"in_reply_to":"3f4b6375_58fbd8bc","updated":"2017-11-14 19:23:43.000000000","message":"That page is in the admin guide, so it should not IMO include installation bits.","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":55,"context_line":""},{"line_number":56,"context_line":"boot"},{"line_number":57,"context_line":"    manages booting of both the deploy ramdisk and the user instances on the"},{"line_number":58,"context_line":"    bare metal node. See :doc:`/admin/interfaces/deploy` for details."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"    Boot interface implementations are often vendor specific,"},{"line_number":61,"context_line":"    and can be enabled via the ``enabled_boot_interfaces`` option:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_c8ce2b2c","line":58,"updated":"2017-11-15 17:24:26.000000000","message":"did you want s/deploy/boot/ ?","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":55,"context_line":""},{"line_number":56,"context_line":"boot"},{"line_number":57,"context_line":"    manages booting of both the deploy ramdisk and the user instances on the"},{"line_number":58,"context_line":"    bare metal node. See :doc:`/admin/interfaces/deploy` for details."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"    Boot interface implementations are often vendor specific,"},{"line_number":61,"context_line":"    and can be enabled via the ``enabled_boot_interfaces`` option:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_cb168ff2","line":58,"in_reply_to":"1f485f77_c8ce2b2c","updated":"2017-11-22 13:57:05.000000000","message":"OOps","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"}],"doc/source/install/refarch/common.rst":[{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"6eb6df20539e404e1629d7f393778db52862a116","unresolved":false,"context_lines":[{"line_number":116,"context_line":"With the ``iscsi`` deploy method, most of the deployment operations happen on"},{"line_number":117,"context_line":"the conductor. If the Object Storage service (swift) or RadosGW is present in"},{"line_number":118,"context_line":"the environment, it is recommended to use the ``direct`` deploy method for"},{"line_number":119,"context_line":"better scalability and reliability."},{"line_number":120,"context_line":""},{"line_number":121,"context_line":".. TODO(dtantsur): say something about the ansible deploy, when it\u0027s in"},{"line_number":122,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f4b6375_98e39005","line":119,"updated":"2017-11-06 16:21:10.000000000","message":"ditto, i hate copy/paste, but might be worth adding this info to the new deploy interfaces page too?","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"bf05a9fd5a97274a5cd7e319c6210ef831bc305b","unresolved":false,"context_lines":[{"line_number":116,"context_line":"With the ``iscsi`` deploy method, most of the deployment operations happen on"},{"line_number":117,"context_line":"the conductor. If the Object Storage service (swift) or RadosGW is present in"},{"line_number":118,"context_line":"the environment, it is recommended to use the ``direct`` deploy method for"},{"line_number":119,"context_line":"better scalability and reliability."},{"line_number":120,"context_line":""},{"line_number":121,"context_line":".. TODO(dtantsur): say something about the ansible deploy, when it\u0027s in"},{"line_number":122,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1f485f77_5818e873","line":119,"in_reply_to":"3f4b6375_98e39005","updated":"2017-11-14 19:23:43.000000000","message":"The goal was to leave only opinionated bits (\"it is recommended\") here and only raw facts (\"this works the following way\") in the interface page. Please let me know if it makes sense to you.","commit_id":"d5196d3d5226b3d32606c9df7525d0aa25e124df"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":89,"context_line":"the user instances on the bare metal node. The deploy interface orchestrates"},{"line_number":90,"context_line":"the deployment and defines how the image gets transferred to the target disk."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"The main alternatives are to use PXE/iPXE or to use virtual media - see"},{"line_number":93,"context_line":":doc:`/admin/interfaces/boot` for a detailed explanation. If a virtual media"},{"line_number":94,"context_line":"implementation is available for the hardware, it is recommended using it"},{"line_number":95,"context_line":"for better scalability and security. Otherwise, it is recommended to use iPXE,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_c8b3cb09","line":92,"updated":"2017-11-15 17:24:26.000000000","message":"nit, probably no need to mention s/to use//","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":89,"context_line":"the user instances on the bare metal node. The deploy interface orchestrates"},{"line_number":90,"context_line":"the deployment and defines how the image gets transferred to the target disk."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"The main alternatives are to use PXE/iPXE or to use virtual media - see"},{"line_number":93,"context_line":":doc:`/admin/interfaces/boot` for a detailed explanation. If a virtual media"},{"line_number":94,"context_line":"implementation is available for the hardware, it is recommended using it"},{"line_number":95,"context_line":"for better scalability and security. Otherwise, it is recommended to use iPXE,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_6bd3c339","line":92,"in_reply_to":"1f485f77_c8b3cb09","updated":"2017-11-22 13:57:05.000000000","message":"Done","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":93,"context_line":":doc:`/admin/interfaces/boot` for a detailed explanation. If a virtual media"},{"line_number":94,"context_line":"implementation is available for the hardware, it is recommended using it"},{"line_number":95,"context_line":"for better scalability and security. Otherwise, it is recommended to use iPXE,"},{"line_number":96,"context_line":"when it is supported by target hardware."},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"Deploy interface"},{"line_number":99,"context_line":"~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_68cf3756","line":96,"updated":"2017-11-15 17:24:26.000000000","message":"Did I ask this before? Would it make sense to also put the recommendations in the admin/interfaces/boot.html page too?\n\nHow about\n\nWe recommend using virtual media (if it is available with your hardware) for better scalability and security. Otherwise, we recommend iPXE (if it is supported by your hardware).","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":93,"context_line":":doc:`/admin/interfaces/boot` for a detailed explanation. If a virtual media"},{"line_number":94,"context_line":"implementation is available for the hardware, it is recommended using it"},{"line_number":95,"context_line":"for better scalability and security. Otherwise, it is recommended to use iPXE,"},{"line_number":96,"context_line":"when it is supported by target hardware."},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"Deploy interface"},{"line_number":99,"context_line":"~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_2bddbb41","line":96,"in_reply_to":"1f485f77_68cf3756","updated":"2017-11-22 13:57:05.000000000","message":"You did, I answered that I\u0027d like only the refarch guide to be opinionated, while the other guides only provide facts. Otherwise we really should scatter such recommendations all over the documentation.","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":6618,"name":"Ruby Loo","email":"opensrloo@gmail.com","username":"rloo"},"change_message_id":"0fb9be2c03b877e5d411d760b6db797567c7abfa","unresolved":false,"context_lines":[{"line_number":98,"context_line":"Deploy interface"},{"line_number":99,"context_line":"~~~~~~~~~~~~~~~~"},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"There are two deploy interfaces in-tree, ``iscsi`` and ``direct``. See"},{"line_number":102,"context_line":":doc:`../../admin/interfaces/deploy` for explanation of the difference."},{"line_number":103,"context_line":"With the ``iscsi`` deploy method, most of the deployment operations happen on"},{"line_number":104,"context_line":"the conductor. If the Object Storage service (swift) or RadosGW is present in"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1f485f77_e80c47a6","line":101,"updated":"2017-11-15 17:24:26.000000000","message":"nit, I don\u0027t see why we need to mention \u0027in-tree\u0027, we didn\u0027t for boot interface above.\n\nWhy do we emphasize iscsi and direct here, but we don\u0027t above for boot interfaces PXE/iPXE and virtual media?","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"},{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"70e8496cd7d5e4c774997d039d344a763ab7f608","unresolved":false,"context_lines":[{"line_number":98,"context_line":"Deploy interface"},{"line_number":99,"context_line":"~~~~~~~~~~~~~~~~"},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"There are two deploy interfaces in-tree, ``iscsi`` and ``direct``. See"},{"line_number":102,"context_line":":doc:`../../admin/interfaces/deploy` for explanation of the difference."},{"line_number":103,"context_line":"With the ``iscsi`` deploy method, most of the deployment operations happen on"},{"line_number":104,"context_line":"the conductor. If the Object Storage service (swift) or RadosGW is present in"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff82abbf_6bbc23dc","line":101,"in_reply_to":"1f485f77_e80c47a6","updated":"2017-11-22 13:57:05.000000000","message":"Because the list of deploy interfaces changes rarely, while we already have 5 (?) boot interfaces, and we may have more..\n\n\"In-tree\" - mostly because of the out-of-tree ansible deploy interface. I can remove it, if you feel like, but then this phrase will be not exactly correct :)","commit_id":"510ad4907d8d829ca9e7c94c2c945b5e0e713c1b"}]}