)]}'
{"specs/newton/multi-arch-support.rst":[{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"7733a8e8ec61c5c981b04354f8b26eefacff4bba","unresolved":false,"context_lines":[{"line_number":10,"context_line":"  * https://blueprints.launchpad.net/openstack-ansible/+spec/example"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"The purpose of this spec is to add support for multiple CPU architectures to"},{"line_number":13,"context_line":"OpenStack Ansible. With the introduction of OpenStack services running on other"},{"line_number":14,"context_line":"architectures such as PPC64LE, OpenStack-Ansible needs to be extended to support"},{"line_number":15,"context_line":"environments where a mixed environment of CPU architectures exists."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_0b8ace1a","line":13,"updated":"2016-06-14 20:12:23.000000000","message":"Add a dash here: \"OpenStack-Ansible\"","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":10,"context_line":"  * https://blueprints.launchpad.net/openstack-ansible/+spec/example"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"The purpose of this spec is to add support for multiple CPU architectures to"},{"line_number":13,"context_line":"OpenStack Ansible. With the introduction of OpenStack services running on other"},{"line_number":14,"context_line":"architectures such as PPC64LE, OpenStack-Ansible needs to be extended to support"},{"line_number":15,"context_line":"environments where a mixed environment of CPU architectures exists."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_dbce6eb6","line":13,"in_reply_to":"7aa08908_0b8ace1a","updated":"2016-06-16 17:39:31.000000000","message":"Done","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"7733a8e8ec61c5c981b04354f8b26eefacff4bba","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Problem description"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"OpenStack-Ansible was initially built to support deployments to a single"},{"line_number":22,"context_line":"architecture, primarily x86. With the extension of OpenStack and"},{"line_number":23,"context_line":"OpenStack-Ansible support to other platforms such as POWER, support for"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_eb8ca236","line":20,"updated":"2016-06-14 20:12:23.000000000","message":"Very nice explanation here!","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"28b19b14552c53a6dd8e54cab38314e3be6e94a6","unresolved":false,"context_lines":[{"line_number":41,"context_line":"Update OpenStack-Ansible and necessary roles to support building and deploying"},{"line_number":42,"context_line":"with multiple CPU architectures. This includes changes to:"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"* Detect and store the CPU architectures used across all hosts"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Support a \u0027repo master\u0027 for each CPU architecture in the deployment"},{"line_number":47,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_b81ad67a","line":44,"range":{"start_line":44,"start_character":0,"end_line":44,"end_character":62},"updated":"2016-06-15 10:35:11.000000000","message":"Ansible fact gathering already does this. The following vars are present with the value \u0027x86_64\u0027 on a test system I have:\n\n - ansible_architecture\n - ansible_machine\n - ansible_userspace_architecture","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":41,"context_line":"Update OpenStack-Ansible and necessary roles to support building and deploying"},{"line_number":42,"context_line":"with multiple CPU architectures. This includes changes to:"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"* Detect and store the CPU architectures used across all hosts"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Support a \u0027repo master\u0027 for each CPU architecture in the deployment"},{"line_number":47,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_4a010239","line":44,"range":{"start_line":44,"start_character":0,"end_line":44,"end_character":62},"in_reply_to":"7aa08908_b81ad67a","updated":"2016-06-16 17:39:31.000000000","message":"Noted, no need for additional detection, only tasks for looking at the facts to assign an appropriate build \u0027master\u0027 for each architecture and storing that.","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"28b19b14552c53a6dd8e54cab38314e3be6e94a6","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":"* Detect and store the CPU architectures used across all hosts"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Support a \u0027repo master\u0027 for each CPU architecture in the deployment"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"* Support building copies of all artifacts on each repo master, then copying"},{"line_number":49,"context_line":"  to all other masters for synchronization out to slaves."}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_ab9d5ebd","line":46,"range":{"start_line":46,"start_character":0,"end_line":46,"end_character":69},"updated":"2016-06-15 10:35:11.000000000","message":"Do you mean that each architecture will have a set of repo servers and exclusively use repo servers that match their architecture? I don\u0027t think this is necessary. The only problem space here is that the package *build* must happen on the correct architecture. The packages can be *served* from any host.","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":43,"context_line":""},{"line_number":44,"context_line":"* Detect and store the CPU architectures used across all hosts"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Support a \u0027repo master\u0027 for each CPU architecture in the deployment"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"* Support building copies of all artifacts on each repo master, then copying"},{"line_number":49,"context_line":"  to all other masters for synchronization out to slaves."}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_aa05067a","line":46,"range":{"start_line":46,"start_character":0,"end_line":46,"end_character":69},"in_reply_to":"7aa08908_ab9d5ebd","updated":"2016-06-16 17:39:31.000000000","message":"No, sorry for the poor wording here. It was basically saying we would designate a repo build \u0027master\u0027 server for each architecture, then synchronize everywhere as needed. I\u0027ve made that more clear in the revision.","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"28b19b14552c53a6dd8e54cab38314e3be6e94a6","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Support a \u0027repo master\u0027 for each CPU architecture in the deployment"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"* Support building copies of all artifacts on each repo master, then copying"},{"line_number":49,"context_line":"  to all other masters for synchronization out to slaves."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Support tagging built artifacts with their CPU architecture where needed"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_8bb7c239","line":49,"range":{"start_line":48,"start_character":0,"end_line":49,"end_character":57},"updated":"2016-06-15 10:35:11.000000000","message":"To my mind the building of artifacts should happen on the designated master for each architecture, then the artifacts should be synchronised to all slaves (regardless of architecture).","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Support a \u0027repo master\u0027 for each CPU architecture in the deployment"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"* Support building copies of all artifacts on each repo master, then copying"},{"line_number":49,"context_line":"  to all other masters for synchronization out to slaves."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Support tagging built artifacts with their CPU architecture where needed"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_ca021272","line":49,"range":{"start_line":48,"start_character":0,"end_line":49,"end_character":57},"in_reply_to":"7aa08908_8bb7c239","updated":"2016-06-16 17:39:31.000000000","message":"Yeah, as above this was poorly worded. I\u0027ve reworded in the next patchset.","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"7733a8e8ec61c5c981b04354f8b26eefacff4bba","unresolved":false,"context_lines":[{"line_number":48,"context_line":"* Support building copies of all artifacts on each repo master, then copying"},{"line_number":49,"context_line":"  to all other masters for synchronization out to slaves."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Support tagging built artifacts with their CPU architecture where needed"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* Maintain backwards compatibility with existing single-architecture"},{"line_number":54,"context_line":"  deployments by linking a non-tagged version of artifacts to the primary"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_4b8056f7","line":51,"updated":"2016-06-14 20:12:23.000000000","message":"This may read better with \"build\" instead of \"built\", but I see where you were going with this.","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":48,"context_line":"* Support building copies of all artifacts on each repo master, then copying"},{"line_number":49,"context_line":"  to all other masters for synchronization out to slaves."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Support tagging built artifacts with their CPU architecture where needed"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* Maintain backwards compatibility with existing single-architecture"},{"line_number":54,"context_line":"  deployments by linking a non-tagged version of artifacts to the primary"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_9e4a1454","line":51,"in_reply_to":"7aa08908_4b8056f7","updated":"2016-06-16 17:39:31.000000000","message":"Done","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"28b19b14552c53a6dd8e54cab38314e3be6e94a6","unresolved":false,"context_lines":[{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Support tagging built artifacts with their CPU architecture where needed"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* Maintain backwards compatibility with existing single-architecture"},{"line_number":54,"context_line":"  deployments by linking a non-tagged version of artifacts to the primary"},{"line_number":55,"context_line":"  tagged architecture versions"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Ensure pre-built binaries used during installation (apt packages, etc) exist"},{"line_number":58,"context_line":"  or are made available for the supported CPU architectures (x86, ppc64el"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_2bbfaefd","line":55,"range":{"start_line":53,"start_character":0,"end_line":55,"end_character":30},"updated":"2016-06-15 10:35:11.000000000","message":"As this change will be introduced in a major version, this is not a concern at all. Why bother?","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Support tagging built artifacts with their CPU architecture where needed"},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"* Maintain backwards compatibility with existing single-architecture"},{"line_number":54,"context_line":"  deployments by linking a non-tagged version of artifacts to the primary"},{"line_number":55,"context_line":"  tagged architecture versions"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Ensure pre-built binaries used during installation (apt packages, etc) exist"},{"line_number":58,"context_line":"  or are made available for the supported CPU architectures (x86, ppc64el"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_1b11165e","line":55,"range":{"start_line":53,"start_character":0,"end_line":55,"end_character":30},"in_reply_to":"7aa08908_2bbfaefd","updated":"2016-06-16 17:39:31.000000000","message":"My thought here was that it might be needed for people upgrading, but I suppose any conversion to using tagged artifacts needed could be handled as part of the upgrade scripts?","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"7733a8e8ec61c5c981b04354f8b26eefacff4bba","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  tagged architecture versions"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Ensure pre-built binaries used during installation (apt packages, etc) exist"},{"line_number":58,"context_line":"  or are made available for the supported CPU architectures (x86, ppc64el"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Alternatives"},{"line_number":61,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_2b834a04","line":58,"updated":"2016-06-14 20:12:23.000000000","message":"Missing a closing ) on the end here","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  tagged architecture versions"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Ensure pre-built binaries used during installation (apt packages, etc) exist"},{"line_number":58,"context_line":"  or are made available for the supported CPU architectures (x86, ppc64el"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Alternatives"},{"line_number":61,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_be4ef06b","line":58,"in_reply_to":"7aa08908_2b834a04","updated":"2016-06-16 17:39:31.000000000","message":"Done","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"7733a8e8ec61c5c981b04354f8b26eefacff4bba","unresolved":false,"context_lines":[{"line_number":60,"context_line":"Alternatives"},{"line_number":61,"context_line":"------------"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Potential Alternative - Cross compiling artifacts (under investigation)"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Support only single-architecture OpenStack-Ansible deployments. This is"},{"line_number":66,"context_line":"  harmful to deployers by limiting the potential integration of servers"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_8b7ebe16","line":63,"updated":"2016-06-14 20:12:23.000000000","message":"This could make things easier but I worry about small differences or issues that may crop up from cross-compiling. Then again, I don\u0027t have much experience in this area.","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":60,"context_line":"Alternatives"},{"line_number":61,"context_line":"------------"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"* Potential Alternative - Cross compiling artifacts (under investigation)"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Support only single-architecture OpenStack-Ansible deployments. This is"},{"line_number":66,"context_line":"  harmful to deployers by limiting the potential integration of servers"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_bbde020e","line":63,"in_reply_to":"7aa08908_8b7ebe16","updated":"2016-06-16 17:39:31.000000000","message":"I\u0027ve updated this in the next patchset. I tried experimenting with cross-compiling but was unsuccessful in finding a reliable way to do it for wheels/venvs.","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"28b19b14552c53a6dd8e54cab38314e3be6e94a6","unresolved":false,"context_lines":[{"line_number":77,"context_line":"Upgrade impact"},{"line_number":78,"context_line":"--------------"},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"This change should be made transparent to existing environments by linking a"},{"line_number":81,"context_line":"copy of non-tagged build artifacts where needed."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Security impact"},{"line_number":84,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_2bf4cecd","line":81,"range":{"start_line":80,"start_character":0,"end_line":81,"end_character":48},"updated":"2016-06-15 10:35:11.000000000","message":"This should not matter. All artifacts are built and tagged for each tag version so there\u0027s no need to do some sort of backward compatibility thing, unless I\u0027m missing something?","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":77,"context_line":"Upgrade impact"},{"line_number":78,"context_line":"--------------"},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"This change should be made transparent to existing environments by linking a"},{"line_number":81,"context_line":"copy of non-tagged build artifacts where needed."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Security impact"},{"line_number":84,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_0d4b912c","line":81,"range":{"start_line":80,"start_character":0,"end_line":81,"end_character":48},"in_reply_to":"7aa08908_2bf4cecd","updated":"2016-06-16 17:39:31.000000000","message":"Done","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"28b19b14552c53a6dd8e54cab38314e3be6e94a6","unresolved":false,"context_lines":[{"line_number":91,"context_line":"Both repo build and synchronization operations will take longer to complete"},{"line_number":92,"context_line":"proportionate to the number of CPU architectures being deployed."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"* Repo builds can occur in parallel across each CPU architecture, minimizing"},{"line_number":95,"context_line":"  the build-time performance impact"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"* Synchronizations will take longer and require more bandwidth to transfer"},{"line_number":98,"context_line":"  when there are multiple architectures due to the increased number of"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_abbc3edc","line":95,"range":{"start_line":94,"start_character":0,"end_line":95,"end_character":35},"updated":"2016-06-15 10:35:11.000000000","message":"If you\u0027re implementing a repo cluster per architecture, then I guess so - but ultimately this is wasteful and expensive. I don\u0027t think there needs to be a repo cluster per architecture and I think that it would be a more complex implementation than the suggestions I\u0027ve made above.\n\nWith my suggestion above the repo builds for each architecture will have to be done in serial though to prevent artifact synchronisation collisions for non-arch specific packages.","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":91,"context_line":"Both repo build and synchronization operations will take longer to complete"},{"line_number":92,"context_line":"proportionate to the number of CPU architectures being deployed."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":"* Repo builds can occur in parallel across each CPU architecture, minimizing"},{"line_number":95,"context_line":"  the build-time performance impact"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"* Synchronizations will take longer and require more bandwidth to transfer"},{"line_number":98,"context_line":"  when there are multiple architectures due to the increased number of"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_fb836a01","line":95,"range":{"start_line":94,"start_character":0,"end_line":95,"end_character":35},"in_reply_to":"7aa08908_abbc3edc","updated":"2016-06-16 17:39:31.000000000","message":"Yeah, that makes sense based on what you laid out above. I\u0027ll update this accordingly.","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"7733a8e8ec61c5c981b04354f8b26eefacff4bba","unresolved":false,"context_lines":[{"line_number":144,"context_line":""},{"line_number":145,"context_line":"Work items"},{"line_number":146,"context_line":"----------"},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"* Add a repo discovery tasks to detect and store facts on the CPU architectures"},{"line_number":149,"context_line":"  used across all hosts, and assign a master for each architecture"},{"line_number":150,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_6b79d22e","line":147,"updated":"2016-06-14 20:12:23.000000000","message":"These first four bullet points don\u0027t end with periods, but the last two do. Could you end them all with periods?","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":13883,"name":"Adam Reznechek","email":"adreznec@us.ibm.com","username":"adrez"},"change_message_id":"bc6e77c278b8c009e0f162a4ac4e76c60fc73e2c","unresolved":false,"context_lines":[{"line_number":144,"context_line":""},{"line_number":145,"context_line":"Work items"},{"line_number":146,"context_line":"----------"},{"line_number":147,"context_line":""},{"line_number":148,"context_line":"* Add a repo discovery tasks to detect and store facts on the CPU architectures"},{"line_number":149,"context_line":"  used across all hosts, and assign a master for each architecture"},{"line_number":150,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"7aa08908_bb2d6247","line":147,"in_reply_to":"7aa08908_6b79d22e","updated":"2016-06-16 17:39:31.000000000","message":"Done","commit_id":"237841454f7d30f259eed28d59186a6d2b30564c"},{"author":{"_account_id":538,"name":"Major Hayden","email":"major@mhtx.net","username":"rackerhacker"},"change_message_id":"36e6b4c80d39785c3f4dbf4bf4de772c58c3bf13","unresolved":false,"context_lines":[{"line_number":6,"context_line":"The purpose of this spec is to enable OpenStack-Ansible to deploy OpenStack"},{"line_number":7,"context_line":"in clouds with multiple CPU architectures across the nodes to be deployed."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Include the URL of your launchpad blueprint:"},{"line_number":10,"context_line":"  * https://blueprints.launchpad.net/openstack-ansible/+spec/example"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"The purpose of this spec is to add support for multiple CPU architectures to"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3aaa91ec_09de106d","line":9,"updated":"2016-06-22 12:34:51.000000000","message":"Don\u0027t forget to put the link to the blueprint in LaunchPad here. :)","commit_id":"0cac092495e9a46fc473c96949320f2f16fb57db"},{"author":{"_account_id":18784,"name":"Michael Carden","email":"mike.carden@gmail.com","username":"mcarden"},"change_message_id":"fedc6d99c4736e6dddaed0252d9889cd2dd7de5d","unresolved":false,"context_lines":[{"line_number":22,"context_line":"OpenStack-Ansible support to other platforms such as POWER, support for"},{"line_number":23,"context_line":"deployments running a combination of different CPU architectures is needed."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"For each deployment, OpenStack-Ansible creates and builds an \u0027repo\u0027 containing"},{"line_number":26,"context_line":"necessary artifacts for the OpenStack deployment. This repo holds components"},{"line_number":27,"context_line":"such as pip wheels, virtualenvs, and source trees for the different services"},{"line_number":28,"context_line":"to be deployed. For each deployment a single \u0027master\u0027 repo is designated where"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3aaa91ec_aa9adc11","line":25,"updated":"2016-06-30 04:12:28.000000000","message":"a \u0027repo\u0027","commit_id":"3b9aaae78e493029272c954d3517e46d5b952f6b"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"8c757bcb81dc8d1d3a46dedf316d3a4c49e42082","unresolved":false,"context_lines":[{"line_number":94,"context_line":"proportionate to the number of CPU architectures being deployed."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"* Repo builds will take longer as artifacts for each repo must be built"},{"line_number":97,"context_line":"  serially to avoid collisions during synchronization between non-architecture"},{"line_number":98,"context_line":"  specific packages."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"* Synchronizations will take longer and require more bandwidth to transfer"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3aaa91ec_6cb12501","line":97,"range":{"start_line":97,"start_character":54,"end_line":97,"end_character":61},"updated":"2016-06-30 10:15:51.000000000","message":"s/between/of/","commit_id":"3b9aaae78e493029272c954d3517e46d5b952f6b"},{"author":{"_account_id":18784,"name":"Michael Carden","email":"mike.carden@gmail.com","username":"mcarden"},"change_message_id":"fedc6d99c4736e6dddaed0252d9889cd2dd7de5d","unresolved":false,"context_lines":[{"line_number":109,"context_line":"Deployer impact"},{"line_number":110,"context_line":"---------------"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Deployers will now be able to create deployments with servers with servers of"},{"line_number":113,"context_line":"multiple CPU architectures included."},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"No other deployer impact is expected as the detection of multiple"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3aaa91ec_eaa06444","line":112,"updated":"2016-06-30 04:12:28.000000000","message":"only need to say \u0027with servers\u0027 once","commit_id":"3b9aaae78e493029272c954d3517e46d5b952f6b"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"8c757bcb81dc8d1d3a46dedf316d3a4c49e42082","unresolved":false,"context_lines":[{"line_number":186,"context_line":"References"},{"line_number":187,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"* https://github.com/openstack/openstack-ansible-specs/blob/master/specs/newton/powervm-virt-driver.rst"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3aaa91ec_ec73554c","line":189,"updated":"2016-06-30 10:15:51.000000000","message":"Ideally this should refer to the published doc, not the source: http://specs.openstack.org/openstack/openstack-ansible-specs/specs/newton/powervm-virt-driver.html","commit_id":"3b9aaae78e493029272c954d3517e46d5b952f6b"}]}
