)]}'
{"doc/arch-design/ch_multi_site.xml":[{"author":{"_account_id":14947,"name":"Maria Zlatkova","email":"mzlatkova@mirantis.com","username":"mzlatkova"},"change_message_id":"c181ba7bb1d708bb2a8de48ef09e2a346547bdae","unresolved":false,"context_lines":[{"line_number":6,"context_line":"  xml:id\u003d\"multi_site\"\u003e"},{"line_number":7,"context_line":"    \u003ctitle\u003eMulti-site\u003c/title\u003e"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"    \u003cpara\u003eA multi-site OpenStack environment is one in which, services"},{"line_number":10,"context_line":"        located in more than one data center, are used to provide the"},{"line_number":11,"context_line":"        overall solution. Usage requirements of different multi-site"},{"line_number":12,"context_line":"        clouds may vary widely, but they share some common needs."}],"source_content_type":"application/xml","patch_set":2,"id":"1a6ced46_ea788d2d","line":9,"updated":"2015-03-23 10:40:31.000000000","message":"The original variant sounds better to me, please leave it as it was.","commit_id":"4ece86e7f2b9fb0a7343966f05c8ac3c60699ec6"}],"doc/arch-design/multi_site/section_operational_considerations_multi_site.xml":[{"author":{"_account_id":14947,"name":"Maria Zlatkova","email":"mzlatkova@mirantis.com","username":"mzlatkova"},"change_message_id":"c181ba7bb1d708bb2a8de48ef09e2a346547bdae","unresolved":false,"context_lines":[{"line_number":180,"context_line":"        it is left to the end user to decide in which region to"},{"line_number":181,"context_line":"        schedule the new instance. The dashboard presents the user with"},{"line_number":182,"context_line":"        the first region in your configuration. The API and CLI tools"},{"line_number":183,"context_line":"        will not execute commands unless a valid region is specified."},{"line_number":184,"context_line":"        It is therefore important to provide documentation to your"},{"line_number":185,"context_line":"        users describing the region layout as well as calling out that"},{"line_number":186,"context_line":"        quotas are region-specific. If a user reaches his or her quota"}],"source_content_type":"application/xml","patch_set":2,"id":"1a6ced46_4add2114","line":183,"updated":"2015-03-23 10:40:31.000000000","message":"will not -\u003e do not","commit_id":"4ece86e7f2b9fb0a7343966f05c8ac3c60699ec6"}],"doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml":[{"author":{"_account_id":14947,"name":"Maria Zlatkova","email":"mzlatkova@mirantis.com","username":"mzlatkova"},"change_message_id":"c181ba7bb1d708bb2a8de48ef09e2a346547bdae","unresolved":false,"context_lines":[{"line_number":35,"context_line":"        the four chosen regions. The implications of this design are"},{"line_number":36,"context_line":"        based around the method of placing copies of resources in each"},{"line_number":37,"context_line":"        of the remote regions. Swift objects, Glance images, and block"},{"line_number":38,"context_line":"        storage will need to be manually replicated into each region."},{"line_number":39,"context_line":"        This may be beneficial for some systems, such as the case of"},{"line_number":40,"context_line":"        content service, where only some of the content needs to exist"},{"line_number":41,"context_line":"        in some but not all regions. A centralized Keystone is"}],"source_content_type":"application/xml","patch_set":2,"id":"1a6ced46_aa3a1534","line":38,"updated":"2015-03-23 10:40:31.000000000","message":"please remove \"will\"","commit_id":"4ece86e7f2b9fb0a7343966f05c8ac3c60699ec6"},{"author":{"_account_id":14947,"name":"Maria Zlatkova","email":"mzlatkova@mirantis.com","username":"mzlatkova"},"change_message_id":"c181ba7bb1d708bb2a8de48ef09e2a346547bdae","unresolved":false,"context_lines":[{"line_number":161,"context_line":"    \u003cpara\u003eThe reason that three regions were selected here was because of"},{"line_number":162,"context_line":"        the fear of having abnormal load on a single region in the"},{"line_number":163,"context_line":"        event of a failure. Two data center would have been sufficient"},{"line_number":164,"context_line":"        had the requirements been met.\u003c/para\u003e"},{"line_number":165,"context_line":"    \u003cpara\u003eOrchestration is used because of the built-in functionality of"},{"line_number":166,"context_line":"        autoscaling and auto healing in the event of increased load."},{"line_number":167,"context_line":"        Additional configuration management tools, such as Puppet or"}],"source_content_type":"application/xml","patch_set":2,"id":"1a6ced46_aa49358d","line":164,"updated":"2015-03-23 10:40:31.000000000","message":"This sentence should also be rewritten.","commit_id":"4ece86e7f2b9fb0a7343966f05c8ac3c60699ec6"},{"author":{"_account_id":14947,"name":"Maria Zlatkova","email":"mzlatkova@mirantis.com","username":"mzlatkova"},"change_message_id":"c181ba7bb1d708bb2a8de48ef09e2a346547bdae","unresolved":false,"context_lines":[{"line_number":196,"context_line":"        optimal user experience, in addition to reducing the cost of"},{"line_number":197,"context_line":"        bandwidth and transit, since the content resides on sites"},{"line_number":198,"context_line":"        closer to the customer, instead of a centralized content store"},{"line_number":199,"context_line":"        that would require utilizing higher cost cross country"},{"line_number":200,"context_line":"        links.\u003c/para\u003e"},{"line_number":201,"context_line":"    \u003cpara\u003eThis architecture usually includes a geo-location component"},{"line_number":202,"context_line":"        that places user requests at the closest possible node. In"}],"source_content_type":"application/xml","patch_set":2,"id":"1a6ced46_7e9b7ec9","line":199,"updated":"2015-03-23 10:40:31.000000000","message":"would require -\u003e requires    \n\ncross country -\u003e cross-country","commit_id":"4ece86e7f2b9fb0a7343966f05c8ac3c60699ec6"}],"doc/arch-design/multi_site/section_tech_considerations_multi_site.xml":[{"author":{"_account_id":14947,"name":"Maria Zlatkova","email":"mzlatkova@mirantis.com","username":"mzlatkova"},"change_message_id":"c181ba7bb1d708bb2a8de48ef09e2a346547bdae","unresolved":false,"context_lines":[{"line_number":22,"context_line":"        includes parameters such as bandwidth, latency, whether or not"},{"line_number":23,"context_line":"        a link is dedicated, and any business policies applied to the"},{"line_number":24,"context_line":"        connection. The capability and number of the links between"},{"line_number":25,"context_line":"        sites determine what kind of options are be available for"},{"line_number":26,"context_line":"        deployment. For example, if two sites have a pair of"},{"line_number":27,"context_line":"        high-bandwidth links available between them, it may be wise to"},{"line_number":28,"context_line":"        configure a separate storage replication network between the"}],"source_content_type":"application/xml","patch_set":2,"id":"1a6ced46_caae71e7","line":25,"updated":"2015-03-23 10:40:31.000000000","message":"Please remove \"be\"","commit_id":"4ece86e7f2b9fb0a7343966f05c8ac3c60699ec6"},{"author":{"_account_id":14947,"name":"Maria Zlatkova","email":"mzlatkova@mirantis.com","username":"mzlatkova"},"change_message_id":"c181ba7bb1d708bb2a8de48ef09e2a346547bdae","unresolved":false,"context_lines":[{"line_number":93,"context_line":"        actions to an API endpoint or in the dashboard.\u003c/para\u003e"},{"line_number":94,"context_line":"    \u003cpara\u003eLoad balancing is another common issue with multi-site"},{"line_number":95,"context_line":"        installations. While it is still possible to run HAproxy"},{"line_number":96,"context_line":"        instances with Load-Balancer-as-a-Service, these will be local"},{"line_number":97,"context_line":"        to a specific region. Some applications may be able to cope"},{"line_number":98,"context_line":"        with this via internal mechanisms. Others, however, may"},{"line_number":99,"context_line":"        require the implementation of an external system including"}],"source_content_type":"application/xml","patch_set":2,"id":"1a6ced46_2a4b85b1","line":96,"updated":"2015-03-23 10:40:31.000000000","message":"will be -\u003e are","commit_id":"4ece86e7f2b9fb0a7343966f05c8ac3c60699ec6"}],"doc/arch-design/multi_site/section_user_requirements_multi_site.xml":[{"author":{"_account_id":14947,"name":"Maria Zlatkova","email":"mzlatkova@mirantis.com","username":"mzlatkova"},"change_message_id":"c181ba7bb1d708bb2a8de48ef09e2a346547bdae","unresolved":false,"context_lines":[{"line_number":76,"context_line":"        into the infrastructure. If the OpenStack Object Storage is used as"},{"line_number":77,"context_line":"        a back end for the Image Service, it is possible to create repositories of"},{"line_number":78,"context_line":"        consistent images across multiple sites. Having central"},{"line_number":79,"context_line":"        endpoints with multiple storage nodes allows for"},{"line_number":80,"context_line":"        consistent centralized storage for each and every site.\u003c/para\u003e"},{"line_number":81,"context_line":"    \u003cpara\u003eNot using a centralized object store increases operational"},{"line_number":82,"context_line":"        overhead so that a consistent image library can be maintained. This"}],"source_content_type":"application/xml","patch_set":2,"id":"1a6ced46_6abf3dd1","line":79,"updated":"2015-03-23 10:40:31.000000000","message":"I believe \"for\" should be removed here.","commit_id":"4ece86e7f2b9fb0a7343966f05c8ac3c60699ec6"}]}