)]}'
{"doc/arch-design/specialized/section_multi_hypervisor_specialized.xml":[{"author":{"_account_id":10497,"name":"KATO Tomoyuki","email":"kato.tomoyuki@jp.fujitsu.com","username":"to222"},"change_message_id":"965e88a1db13c2bbb354b978fe3471c186d39846","unresolved":false,"context_lines":[{"line_number":34,"context_line":"    QEMU disk images to VMDK, VMFS Flat Disks. These disk images"},{"line_number":35,"context_line":"    can also be thin, thick, zeroed-thick, and eager-zeroed-thick."},{"line_number":36,"context_line":"    After exporting a VMFS thin disk from VMFS to the"},{"line_number":37,"context_line":"    OpenStack Image service (a non-VMFS location) it"},{"line_number":38,"context_line":"    becomes a preallocated flat disk. This impacts the transfer"},{"line_number":39,"context_line":"    time from the OpenStack Image service to the data store since transfers"},{"line_number":40,"context_line":"    require moving the full preallocated flat disk rather than the"}],"source_content_type":"application/xml","patch_set":1,"id":"1a4dcd0f_8f536ee2","line":37,"updated":"2015-08-14 04:20:28.000000000","message":"...), it","commit_id":"947de1ddf93c1089698b224d0a295862b97d355b"},{"author":{"_account_id":10497,"name":"KATO Tomoyuki","email":"kato.tomoyuki@jp.fujitsu.com","username":"to222"},"change_message_id":"965e88a1db13c2bbb354b978fe3471c186d39846","unresolved":false,"context_lines":[{"line_number":64,"context_line":"    with legacy networking does not support security groups. The new"},{"line_number":65,"context_line":"    architecture uses VMware NSX as a part of the design. When users launch an"},{"line_number":66,"context_line":"    instance within either of the host aggregates, VMware NSX ensures the"},{"line_number":67,"context_line":"    instance attachs to the appropriate network overlay-based logical"},{"line_number":68,"context_line":"    networks.\u003c/para\u003e"},{"line_number":69,"context_line":"  \u003cpara\u003eThe architecture planning teams also consider OpenStack Compute"},{"line_number":70,"context_line":"    integration. When running vSphere in an OpenStack environment, nova-compute"}],"source_content_type":"application/xml","patch_set":1,"id":"1a4dcd0f_efc9d27a","line":67,"updated":"2015-08-14 04:20:28.000000000","message":"attachs -\u003e attaches","commit_id":"947de1ddf93c1089698b224d0a295862b97d355b"},{"author":{"_account_id":10497,"name":"KATO Tomoyuki","email":"kato.tomoyuki@jp.fujitsu.com","username":"to222"},"change_message_id":"965e88a1db13c2bbb354b978fe3471c186d39846","unresolved":false,"context_lines":[{"line_number":71,"context_line":"    communications with vCenter appear as a single large hypervisor. This"},{"line_number":72,"context_line":"    hypervisor represents the entire ESXi cluster. Multiple nova-compute"},{"line_number":73,"context_line":"    instances can represent multiple ESXi clusters. They can connect to"},{"line_number":74,"context_line":"    multiple vCenter serves. If the process running nova-compute"},{"line_number":75,"context_line":"    crashes it cuts the connection to the vCenter server. Any"},{"line_number":76,"context_line":"    ESXi clusters will stop running, and you will not"},{"line_number":77,"context_line":"    be able to provision further instances on the vCenter, even if you enable high"}],"source_content_type":"application/xml","patch_set":1,"id":"1a4dcd0f_afbf4aa9","line":74,"updated":"2015-08-14 04:20:28.000000000","message":"serves -\u003e servers (this should mean \"vCenter server\")","commit_id":"947de1ddf93c1089698b224d0a295862b97d355b"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"6aeda4094cf604c9a5186c31c574a90757b7fbc5","unresolved":false,"context_lines":[{"line_number":43,"context_line":"    vCenter rather than spawning directly on a hypervisor."},{"line_number":44,"context_line":"    The vCenter then requests scheduling for the instance to run on"},{"line_number":45,"context_line":"    an ESXi hypervisor.\u003c/para\u003e"},{"line_number":46,"context_line":"  \u003cpara\u003eAs of the Icehouse release, this functionality requires"},{"line_number":47,"context_line":"    that VMware Distributed Resource"},{"line_number":48,"context_line":"    Scheduler (DRS) is enabled on a cluster and set to \u003cguilabel\u003eFully"},{"line_number":49,"context_line":"    Automated\u003c/guilabel\u003e. The vSphere requires shared storage because the DRS"}],"source_content_type":"application/xml","patch_set":2,"id":"1a4dcd0f_0a0aec79","line":46,"updated":"2015-08-14 05:00:56.000000000","message":"We can remove reference to the Icehouse release. Jump straight to \"This functionality requires ...\"","commit_id":"fa321e4ead1bafd8532f6683a56cf397eae31218"}]}