)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"877e1271c900f089973136fae22a39891a11e4e2","unresolved":false,"context_lines":[{"line_number":7,"context_line":"Floating ip on vertica master node"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Specification for associating floating ip to master node in the"},{"line_number":10,"context_line":"vertica cluster, to make managment console, running on the master"},{"line_number":11,"context_line":"node, accessible from outside of the OpenStack network."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Implements blueprint: floating-ip-on-vertica-master-node"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":7,"id":"da20952f_ae790f84","line":10,"updated":"2015-08-30 04:55:12.000000000","message":"s/managment/management/","commit_id":"8c7e445cc2bb7de7c7a3a0be6fedfcb7084dc7ac"}],"specs/liberty/vertica-floating-ip-on-master-node.rst":[{"author":{"_account_id":7806,"name":"Sushil Kumar","email":"skm.net@gmail.com","username":"sushilkm"},"change_message_id":"60c171b1a99517e8bd2f1e3e89611e8ca1fabab9","unresolved":false,"context_lines":[{"line_number":37,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Cluster Provisioning:"},{"line_number":40,"context_line":"* On successful cluster is provisioning Taskmanager will try to"},{"line_number":41,"context_line":"provision floating IP on the port from the customer provided network."},{"line_number":42,"context_line":"* If taskmanager fails to provision floating ip on the node, the cluster"},{"line_number":43,"context_line":"will still be created successfully (there might be multiple reasons"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a4dcd0f_8ea9f9df","line":40,"updated":"2015-08-15 16:18:24.000000000","message":"Once the cluster is successfully provisioned","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"7a96452b833c3cfdd4c3aedcd62e01ef0fdf4756","unresolved":false,"context_lines":[{"line_number":37,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Cluster Provisioning:"},{"line_number":40,"context_line":"* On successful cluster is provisioning Taskmanager will try to"},{"line_number":41,"context_line":"provision floating IP on the port from the customer provided network."},{"line_number":42,"context_line":"* If taskmanager fails to provision floating ip on the node, the cluster"},{"line_number":43,"context_line":"will still be created successfully (there might be multiple reasons"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa1b9901_d9513664","line":40,"in_reply_to":"1a4dcd0f_8ea9f9df","updated":"2015-08-18 05:27:39.000000000","message":"Done","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":7806,"name":"Sushil Kumar","email":"skm.net@gmail.com","username":"sushilkm"},"change_message_id":"60c171b1a99517e8bd2f1e3e89611e8ca1fabab9","unresolved":false,"context_lines":[{"line_number":53,"context_line":"* If user chooses not to provision cluster with floating IP, on the cluster"},{"line_number":54,"context_line":"create, they can provide a network which doesn\u0027t have router to the"},{"line_number":55,"context_line":"public/ext-network, in that case cluster will be provisioned without"},{"line_number":56,"context_line":"floating ip."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"Configuration"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a4dcd0f_ee80bd4b","line":56,"updated":"2015-08-15 16:18:24.000000000","message":"why should one be needed to provided a network even in that case, it should be simple if one does not provides a network then he/she does not needs a floating ip.\n\nto provide an un-useful network seems a bit awkward as far as a user-experience is concerned, \n\nI am still looking about if it is really necessary to provide a network, if one does not needs a floating-ip on master","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"7a96452b833c3cfdd4c3aedcd62e01ef0fdf4756","unresolved":false,"context_lines":[{"line_number":53,"context_line":"* If user chooses not to provision cluster with floating IP, on the cluster"},{"line_number":54,"context_line":"create, they can provide a network which doesn\u0027t have router to the"},{"line_number":55,"context_line":"public/ext-network, in that case cluster will be provisioned without"},{"line_number":56,"context_line":"floating ip."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"Configuration"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa1b9901_16e53808","line":56,"in_reply_to":"1a4dcd0f_ee80bd4b","updated":"2015-08-18 05:27:39.000000000","message":"As per my understanding of how trove works with neutron:\n\n1. Trove has default neutron network configured, every instance that trove creates, it will associate a port from this network on that instance (eth0). Ideally this is your management network using which trove guests will talk to your control plane (rabbitmq). End user doesn\u0027t see this network at all,  we even hide the IP from this network in the instance details, so this network doesn\u0027t have any use for the end user\n\n2. Trove allows user to specify a network in user\u0027s tenant on instance/cluster create call. If user provides a network/port , trove associates that to the instance as well (eth1). This network will allow user\u0027s application to be able to connect to the database. Applications either will be running on the same network or user has a router between this network and the applications network.\n\nSo if we say that user doesn\u0027t provide network information then those instances/clusters will be of no use, as they will not be accessible from anywhere.\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nWith this spec, we don\u0027t want to change that, we still want user to provide their network, so that their applications can connect to the database (because we will be putting floating ip only on master node, other nodes in the cluster will still be only accessible from only the user\u0027s network).\n\nThe user provided network can have a router to public network which means a port on such network can have a floating ip associated with it. And in such cases we will provision floating ip.\n\nIf the user provided network doesn\u0027t have router to the public network then we cannot put floating ip on the port so we will provision cluster without floating ip.","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":7806,"name":"Sushil Kumar","email":"skm.net@gmail.com","username":"sushilkm"},"change_message_id":"60c171b1a99517e8bd2f1e3e89611e8ca1fabab9","unresolved":false,"context_lines":[{"line_number":72,"context_line":"Cluster details response will return management_console URL"},{"line_number":73,"context_line":"with extended_properties."},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"Response::"},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"    {"},{"line_number":78,"context_line":"      \"cluster\": {"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a4dcd0f_aec875a9","line":75,"updated":"2015-08-15 16:18:24.000000000","message":"this is response in regard to what request.","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"7a96452b833c3cfdd4c3aedcd62e01ef0fdf4756","unresolved":false,"context_lines":[{"line_number":72,"context_line":"Cluster details response will return management_console URL"},{"line_number":73,"context_line":"with extended_properties."},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"Response::"},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"    {"},{"line_number":78,"context_line":"      \"cluster\": {"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa1b9901_79aa6a1b","line":75,"in_reply_to":"1a4dcd0f_aec875a9","updated":"2015-08-18 05:27:39.000000000","message":"Done","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":7806,"name":"Sushil Kumar","email":"skm.net@gmail.com","username":"sushilkm"},"change_message_id":"60c171b1a99517e8bd2f1e3e89611e8ca1fabab9","unresolved":false,"context_lines":[{"line_number":159,"context_line":"CLI (python-troveclient)"},{"line_number":160,"context_line":"------------------------"},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"None."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"Management API"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a4dcd0f_ae7ab575","line":162,"updated":"2015-08-15 16:18:24.000000000","message":"There should be some change in client to absorb and display the extended_properties","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"7a96452b833c3cfdd4c3aedcd62e01ef0fdf4756","unresolved":false,"context_lines":[{"line_number":159,"context_line":"CLI (python-troveclient)"},{"line_number":160,"context_line":"------------------------"},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"None."},{"line_number":163,"context_line":""},{"line_number":164,"context_line":""},{"line_number":165,"context_line":"Management API"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa1b9901_39bcf26b","line":162,"in_reply_to":"1a4dcd0f_ae7ab575","updated":"2015-08-18 05:27:39.000000000","message":"Since the management console url will be returned in the extended_properties, which is a property/attribute of the cluster, it will be displayed as another row in the output of the cluster-show command.\n\nSo thats why we don\u0027t need to change anything on the CLI for this.","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":7806,"name":"Sushil Kumar","email":"skm.net@gmail.com","username":"sushilkm"},"change_message_id":"60c171b1a99517e8bd2f1e3e89611e8ca1fabab9","unresolved":false,"context_lines":[{"line_number":180,"context_line":"Alternatives"},{"line_number":181,"context_line":"------------"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":"The current alternative is use expect user to use"},{"line_number":184,"context_line":"python neutron CLI to :"},{"line_number":185,"context_line":"* provision a port on the required network."},{"line_number":186,"context_line":"* associate floating ip to that port."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a4dcd0f_6e958d86","line":183,"updated":"2015-08-15 16:18:24.000000000","message":"\"alternative is expect user\"","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"7a96452b833c3cfdd4c3aedcd62e01ef0fdf4756","unresolved":false,"context_lines":[{"line_number":180,"context_line":"Alternatives"},{"line_number":181,"context_line":"------------"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":"The current alternative is use expect user to use"},{"line_number":184,"context_line":"python neutron CLI to :"},{"line_number":185,"context_line":"* provision a port on the required network."},{"line_number":186,"context_line":"* associate floating ip to that port."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa1b9901_d9adb632","line":183,"in_reply_to":"1a4dcd0f_6e958d86","updated":"2015-08-18 05:27:39.000000000","message":"Done","commit_id":"09e822e5b84ff637149edf9d6d8e33745c003035"},{"author":{"_account_id":4240,"name":"Craig Vyvial","email":"cp16net@gmail.com","username":"cp16net"},"change_message_id":"775816dee5bcf6191b885ea464017acd2d61a0cc","unresolved":false,"context_lines":[{"line_number":182,"context_line":"Alternatives"},{"line_number":183,"context_line":"------------"},{"line_number":184,"context_line":""},{"line_number":185,"context_line":"The current alternative is to expect user to"},{"line_number":186,"context_line":"* use python neutron CLI to :"},{"line_number":187,"context_line":"** provision a port on the required network."},{"line_number":188,"context_line":"** associate floating ip to that port."}],"source_content_type":"text/x-rst","patch_set":4,"id":"fa1b9901_ba699827","line":185,"updated":"2015-08-18 22:37:26.000000000","message":"why is this the alternative?","commit_id":"d5bc0254db96adf697cbcbcbdc920285f1d92c8e"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"e41225e0d7152c5a0963d4b9f927eb8a9de34d35","unresolved":false,"context_lines":[{"line_number":17,"context_line":"on the Vertica master node, from outside of the OpenStack network"},{"line_number":18,"context_line":"(e.g. from user\u0027s laptop)."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Problem Description"},{"line_number":21,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Vertica master node will be running Vertica management console application"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_0f30d59d","line":20,"updated":"2015-08-21 18:20:48.000000000","message":"As a general comment, your problem description appears to meander around a bit. Would you consider rearranging the paragraphs into background -\u003e observation -\u003e problem.","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"ee89945316c3a987a37f5b555bec95ac09adea2e","unresolved":false,"context_lines":[{"line_number":17,"context_line":"on the Vertica master node, from outside of the OpenStack network"},{"line_number":18,"context_line":"(e.g. from user\u0027s laptop)."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"Problem Description"},{"line_number":21,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Vertica master node will be running Vertica management console application"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_c4071f17","line":20,"in_reply_to":"fa1b9901_0f30d59d","updated":"2015-08-26 22:40:02.000000000","message":"Done","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"e41225e0d7152c5a0963d4b9f927eb8a9de34d35","unresolved":false,"context_lines":[{"line_number":33,"context_line":"the OpenStack network. In order to make it acceesible from outside, we have"},{"line_number":34,"context_line":"to associate a floating ip to the instance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"In the trove deployments where a pool account is used to create/manage nova"},{"line_number":37,"context_line":"resources, the user doesn\u0027t have direct access to the nova instances,"},{"line_number":38,"context_line":"so they have less control on the instance once its created. Due to this there"},{"line_number":39,"context_line":"is no easy way to associate floating ip with the"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_efcec1b6","line":36,"updated":"2015-08-21 18:20:48.000000000","message":"Trove (here and in other places).\n\ns/trove/Trove/g","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"ee89945316c3a987a37f5b555bec95ac09adea2e","unresolved":false,"context_lines":[{"line_number":33,"context_line":"the OpenStack network. In order to make it acceesible from outside, we have"},{"line_number":34,"context_line":"to associate a floating ip to the instance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"In the trove deployments where a pool account is used to create/manage nova"},{"line_number":37,"context_line":"resources, the user doesn\u0027t have direct access to the nova instances,"},{"line_number":38,"context_line":"so they have less control on the instance once its created. Due to this there"},{"line_number":39,"context_line":"is no easy way to associate floating ip with the"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_e40ca33d","line":36,"in_reply_to":"fa1b9901_efcec1b6","updated":"2015-08-26 22:40:02.000000000","message":"Done","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"e41225e0d7152c5a0963d4b9f927eb8a9de34d35","unresolved":false,"context_lines":[{"line_number":34,"context_line":"to associate a floating ip to the instance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"In the trove deployments where a pool account is used to create/manage nova"},{"line_number":37,"context_line":"resources, the user doesn\u0027t have direct access to the nova instances,"},{"line_number":38,"context_line":"so they have less control on the instance once its created. Due to this there"},{"line_number":39,"context_line":"is no easy way to associate floating ip with the"},{"line_number":40,"context_line":"trove instances after its created (standalone or instances in cluster)."}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_8f47051d","line":37,"updated":"2015-08-21 18:20:48.000000000","message":"Nova","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"ee89945316c3a987a37f5b555bec95ac09adea2e","unresolved":false,"context_lines":[{"line_number":34,"context_line":"to associate a floating ip to the instance."},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"In the trove deployments where a pool account is used to create/manage nova"},{"line_number":37,"context_line":"resources, the user doesn\u0027t have direct access to the nova instances,"},{"line_number":38,"context_line":"so they have less control on the instance once its created. Due to this there"},{"line_number":39,"context_line":"is no easy way to associate floating ip with the"},{"line_number":40,"context_line":"trove instances after its created (standalone or instances in cluster)."}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_84128757","line":37,"in_reply_to":"fa1b9901_8f47051d","updated":"2015-08-26 22:40:02.000000000","message":"Done","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"e41225e0d7152c5a0963d4b9f927eb8a9de34d35","unresolved":false,"context_lines":[{"line_number":39,"context_line":"is no easy way to associate floating ip with the"},{"line_number":40,"context_line":"trove instances after its created (standalone or instances in cluster)."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Also where trove is running with neutron, every instance is usually"},{"line_number":43,"context_line":"provisioned with two network interfaces."},{"line_number":44,"context_line":"- First interface is from default network configured in trove, this is kind"},{"line_number":45,"context_line":"of a management network that allow trove guest instances to talk to the"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_6f715177","line":42,"updated":"2015-08-21 18:20:48.000000000","message":"Is this really true?","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"ee89945316c3a987a37f5b555bec95ac09adea2e","unresolved":false,"context_lines":[{"line_number":39,"context_line":"is no easy way to associate floating ip with the"},{"line_number":40,"context_line":"trove instances after its created (standalone or instances in cluster)."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Also where trove is running with neutron, every instance is usually"},{"line_number":43,"context_line":"provisioned with two network interfaces."},{"line_number":44,"context_line":"- First interface is from default network configured in trove, this is kind"},{"line_number":45,"context_line":"of a management network that allow trove guest instances to talk to the"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_444a2f57","line":42,"in_reply_to":"fa1b9901_6f715177","updated":"2015-08-26 22:40:02.000000000","message":"Yes I think so.\n\nWhen trove works with neutron, the guest needs to have connectivity to two entities:\n1. Trove control plane (through rabbitmq), which it done through the default/mgmt network\n2. Customer\u0027s applications, which it done through the user provided network.\n\nCan\u0027t think of a scenario where this is not going to be true?","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"e41225e0d7152c5a0963d4b9f927eb8a9de34d35","unresolved":false,"context_lines":[{"line_number":47,"context_line":"- Second interface is from the customer provided network and it allows"},{"line_number":48,"context_line":"user\u0027s application to access the database instance."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"While provisioning floating IP, we should use the latter, user provided"},{"line_number":51,"context_line":"network, as putting floating IP on management network poses seucurity risk to"},{"line_number":52,"context_line":"the trove control plane and other trove guest instances (in cases where user"},{"line_number":53,"context_line":"opens up the security group rule on their instances in unsafe manner)."}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_0f2f75f7","line":50,"updated":"2015-08-21 18:20:48.000000000","message":"Should this be somewhere else (other than in problem description)?","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"e41225e0d7152c5a0963d4b9f927eb8a9de34d35","unresolved":false,"context_lines":[{"line_number":63,"context_line":"why this could fail)."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Cluster details:"},{"line_number":66,"context_line":"* If a cluster\u0027s master node has the floating IP associated with it then"},{"line_number":67,"context_line":"in the cluster response the URL for management console will be returned."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Security:"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_ef77a106","line":66,"updated":"2015-08-21 18:20:48.000000000","message":"The cluster create response comes from the API service, not the task manager (I think). So, if it is the task manager that will provision this interface, ...","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"ee89945316c3a987a37f5b555bec95ac09adea2e","unresolved":false,"context_lines":[{"line_number":63,"context_line":"why this could fail)."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Cluster details:"},{"line_number":66,"context_line":"* If a cluster\u0027s master node has the floating IP associated with it then"},{"line_number":67,"context_line":"in the cluster response the URL for management console will be returned."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Security:"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_35cba720","line":66,"in_reply_to":"fa1b9901_ef77a106","updated":"2015-08-26 22:40:02.000000000","message":"Can you elaborate more, what is the concern here?\nYou are correct, create response is returned by the API, but all the resource provisioning (nova,neutron etc) happens on the Taskmanager.\n\nThe floating IP will be created/associated by the task manager if the cluster provisioning is successful.\n\nFor processing GET response on the cluster, if the master node has floating ip, extended properties will be returned by the VerticaClusterView, which will run on the API.","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"e41225e0d7152c5a0963d4b9f927eb8a9de34d35","unresolved":false,"context_lines":[{"line_number":180,"context_line":"CLI (python-troveclient)"},{"line_number":181,"context_line":"------------------------"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":"None."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":""},{"line_number":186,"context_line":"Management API"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_6f53916d","line":183,"updated":"2015-08-21 18:20:48.000000000","message":"Oh?","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"ee89945316c3a987a37f5b555bec95ac09adea2e","unresolved":false,"context_lines":[{"line_number":180,"context_line":"CLI (python-troveclient)"},{"line_number":181,"context_line":"------------------------"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":"None."},{"line_number":184,"context_line":""},{"line_number":185,"context_line":""},{"line_number":186,"context_line":"Management API"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_75a6ff54","line":183,"in_reply_to":"fa1b9901_6f53916d","updated":"2015-08-26 22:40:02.000000000","message":"For this, there is no API change, so we don\u0027t expect user to supply any extra parameter to enable this.\n\nAnd in the response to GET on the cluster, since the management console url will be returned in the extended_properties, which is a property/attribute of the cluster, it will be displayed as another row in the output of the cluster-show command.\n\nSo thats why we don\u0027t need to change anything on the CLI for this.","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":9664,"name":"amrith","email":"amrith.kumar@gmail.com","username":"amrith"},"change_message_id":"e41225e0d7152c5a0963d4b9f927eb8a9de34d35","unresolved":false,"context_lines":[{"line_number":252,"context_line":"Documentation Impact"},{"line_number":253,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"None."},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"References"},{"line_number":258,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":6,"id":"fa1b9901_2fe4b9aa","line":255,"updated":"2015-08-21 18:20:48.000000000","message":"Would be nice to tell your friends about this ;)","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"ee89945316c3a987a37f5b555bec95ac09adea2e","unresolved":false,"context_lines":[{"line_number":252,"context_line":"Documentation Impact"},{"line_number":253,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":254,"context_line":""},{"line_number":255,"context_line":"None."},{"line_number":256,"context_line":""},{"line_number":257,"context_line":"References"},{"line_number":258,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":6,"id":"da20952f_90e4fc3b","line":255,"in_reply_to":"fa1b9901_2fe4b9aa","updated":"2015-08-26 22:40:02.000000000","message":"Again no API change not sure what else we document other than API.","commit_id":"29153eee679da783954673aa4b11534b9c3c0441"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"877e1271c900f089973136fae22a39891a11e4e2","unresolved":false,"context_lines":[{"line_number":37,"context_line":"and one needs credentials to be able to login into the console. Since"},{"line_number":38,"context_line":"this application will mostly be used by the users/administrators for"},{"line_number":39,"context_line":"managing the cluster one should be able to access it from outside"},{"line_number":40,"context_line":"the OpenStack network. In order to make it acceesible from outside, we have"},{"line_number":41,"context_line":"to associate a floating ip to the instance."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"da20952f_4e8b9368","line":40,"updated":"2015-08-30 04:55:12.000000000","message":"s/acceesible/accessible/","commit_id":"8c7e445cc2bb7de7c7a3a0be6fedfcb7084dc7ac"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"877e1271c900f089973136fae22a39891a11e4e2","unresolved":false,"context_lines":[{"line_number":60,"context_line":"* The management console has its own authentication, so without valid"},{"line_number":61,"context_line":"credentials nobody will be able to login into the console."},{"line_number":62,"context_line":"* Also the floating ip will be associated with customer provided network"},{"line_number":63,"context_line":"so defualt/management network will still be protected."},{"line_number":64,"context_line":"* If user chooses not to provision cluster with floating IP, on the cluster"},{"line_number":65,"context_line":"create, they can provide a network which doesn\u0027t have router to the"},{"line_number":66,"context_line":"public/ext-network, in that case cluster will be provisioned without"}],"source_content_type":"text/x-rst","patch_set":7,"id":"da20952f_eeeaa70e","line":63,"updated":"2015-08-30 04:55:12.000000000","message":"s/defualt/default/","commit_id":"8c7e445cc2bb7de7c7a3a0be6fedfcb7084dc7ac"},{"author":{"_account_id":15321,"name":"Matthew Van Dijk","email":"mvandijk@tesora.com","username":"mvandijk"},"change_message_id":"6c1455b79e4841f29320a46f06a2910c3b79e895","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"https://blueprints.launchpad.net/trove/+spec/floating-ip-on-Vertica-master-node"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"The proposal is to provision floating ip on the master node in"},{"line_number":16,"context_line":"the Vertica cluster to allow users to access management console, running"},{"line_number":17,"context_line":"on the Vertica master node, from outside of the OpenStack network"},{"line_number":18,"context_line":"(e.g. from user\u0027s laptop)."}],"source_content_type":"text/x-rst","patch_set":8,"id":"da20952f_ff6b091c","line":15,"updated":"2015-08-31 18:20:43.000000000","message":"provision a floating ip","commit_id":"aeb2caaa72eb419bd8b8af1ff06bc1986437fbe9"},{"author":{"_account_id":15321,"name":"Matthew Van Dijk","email":"mvandijk@tesora.com","username":"mvandijk"},"change_message_id":"6c1455b79e4841f29320a46f06a2910c3b79e895","unresolved":false,"context_lines":[{"line_number":13,"context_line":"https://blueprints.launchpad.net/trove/+spec/floating-ip-on-Vertica-master-node"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"The proposal is to provision floating ip on the master node in"},{"line_number":16,"context_line":"the Vertica cluster to allow users to access management console, running"},{"line_number":17,"context_line":"on the Vertica master node, from outside of the OpenStack network"},{"line_number":18,"context_line":"(e.g. from user\u0027s laptop)."},{"line_number":19,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"da20952f_1f591d8e","line":16,"updated":"2015-08-31 18:20:43.000000000","message":"access the management console","commit_id":"aeb2caaa72eb419bd8b8af1ff06bc1986437fbe9"},{"author":{"_account_id":15321,"name":"Matthew Van Dijk","email":"mvandijk@tesora.com","username":"mvandijk"},"change_message_id":"6c1455b79e4841f29320a46f06a2910c3b79e895","unresolved":false,"context_lines":[{"line_number":23,"context_line":"Background:"},{"line_number":24,"context_line":"In the Trove deployments where a pool account is used to create/manage Nova"},{"line_number":25,"context_line":"resources, the user doesn\u0027t have direct access to the Nova instances,"},{"line_number":26,"context_line":"so they have less control on the instance once its created. Due to this there"},{"line_number":27,"context_line":"is no easy way to associate floating ip with the"},{"line_number":28,"context_line":"Trove instances after its created (standalone or instances in cluster)."},{"line_number":29,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"da20952f_bf4831b4","line":26,"updated":"2015-08-31 18:20:43.000000000","message":"s/its/it is/","commit_id":"aeb2caaa72eb419bd8b8af1ff06bc1986437fbe9"},{"author":{"_account_id":15321,"name":"Matthew Van Dijk","email":"mvandijk@tesora.com","username":"mvandijk"},"change_message_id":"6c1455b79e4841f29320a46f06a2910c3b79e895","unresolved":false,"context_lines":[{"line_number":24,"context_line":"In the Trove deployments where a pool account is used to create/manage Nova"},{"line_number":25,"context_line":"resources, the user doesn\u0027t have direct access to the Nova instances,"},{"line_number":26,"context_line":"so they have less control on the instance once its created. Due to this there"},{"line_number":27,"context_line":"is no easy way to associate floating ip with the"},{"line_number":28,"context_line":"Trove instances after its created (standalone or instances in cluster)."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Vertica master node will be running Vertica management console application"}],"source_content_type":"text/x-rst","patch_set":8,"id":"da20952f_5fca351c","line":27,"updated":"2015-08-31 18:20:43.000000000","message":"associate a floating ip","commit_id":"aeb2caaa72eb419bd8b8af1ff06bc1986437fbe9"},{"author":{"_account_id":15321,"name":"Matthew Van Dijk","email":"mvandijk@tesora.com","username":"mvandijk"},"change_message_id":"6c1455b79e4841f29320a46f06a2910c3b79e895","unresolved":false,"context_lines":[{"line_number":25,"context_line":"resources, the user doesn\u0027t have direct access to the Nova instances,"},{"line_number":26,"context_line":"so they have less control on the instance once its created. Due to this there"},{"line_number":27,"context_line":"is no easy way to associate floating ip with the"},{"line_number":28,"context_line":"Trove instances after its created (standalone or instances in cluster)."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Vertica master node will be running Vertica management console application"},{"line_number":31,"context_line":"which allows Vertica user/administrator to manage the Vertica cluster."}],"source_content_type":"text/x-rst","patch_set":8,"id":"da20952f_3fd3c1d6","line":28,"updated":"2015-08-31 18:20:43.000000000","message":"s/its/it is/","commit_id":"aeb2caaa72eb419bd8b8af1ff06bc1986437fbe9"},{"author":{"_account_id":15321,"name":"Matthew Van Dijk","email":"mvandijk@tesora.com","username":"mvandijk"},"change_message_id":"6c1455b79e4841f29320a46f06a2910c3b79e895","unresolved":false,"context_lines":[{"line_number":39,"context_line":"managing the cluster one should be able to access it from outside"},{"line_number":40,"context_line":"the OpenStack network. In order to make it accessible from outside, we have"},{"line_number":41,"context_line":"to associate a floating ip to the instance."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":""},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":8,"id":"da20952f_e8cd8d66","line":42,"updated":"2015-08-31 18:20:43.000000000","message":"This can be expanded to other datastores as well. The implementation could be generic. Cluster create could accept a floating ip option and the datastore\u0027s strategy should handle it as needed. For example MongoDB could attach it to the query router instance, as that is all that the users need to see. The cluster\u0027s floating ip address (or addresses, if we add an api to attach floating ip addresses) should be slated as the access point for the cluster, hiding the addresses of instances that are not to be user-accessible. This management console should be a subset I believe. The real problem that this is uncovering is the poor cluster user-experience we have.","commit_id":"aeb2caaa72eb419bd8b8af1ff06bc1986437fbe9"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"e0fbdfacc8622ecb651940c5191742cd63efbff0","unresolved":false,"context_lines":[{"line_number":39,"context_line":"managing the cluster one should be able to access it from outside"},{"line_number":40,"context_line":"the OpenStack network. In order to make it accessible from outside, we have"},{"line_number":41,"context_line":"to associate a floating ip to the instance."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":""},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"Proposed Change"}],"source_content_type":"text/x-rst","patch_set":8,"id":"da20952f_8a1cc9c2","line":42,"in_reply_to":"da20952f_e8cd8d66","updated":"2015-09-01 19:06:07.000000000","message":"Agreed. But that doesn\u0027t exist today. \n\nThat is why I am trying to address this change for vertica datastore specifically here.","commit_id":"aeb2caaa72eb419bd8b8af1ff06bc1986437fbe9"},{"author":{"_account_id":15321,"name":"Matthew Van Dijk","email":"mvandijk@tesora.com","username":"mvandijk"},"change_message_id":"6c1455b79e4841f29320a46f06a2910c3b79e895","unresolved":false,"context_lines":[{"line_number":46,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":47,"context_line":"Cluster Provisioning:"},{"line_number":48,"context_line":"* Once the cluster is successfully provisioned, Taskmanager will try to"},{"line_number":49,"context_line":"provision floating IP on the port from the customer provided network."},{"line_number":50,"context_line":"* If taskmanager fails to provision floating ip on the node, the cluster"},{"line_number":51,"context_line":"will still be created successfully (there might be multiple reasons"},{"line_number":52,"context_line":"why this could fail)."}],"source_content_type":"text/x-rst","patch_set":8,"id":"da20952f_3f0e618c","line":49,"updated":"2015-08-31 18:20:43.000000000","message":"Why not provision the floating IP during the API call? You could check it during the quota checks and gracefully fail, as well as provide an error message back to the user. The taskmanager wouldn\u0027t notify the user - they would have to look through the logs.","commit_id":"aeb2caaa72eb419bd8b8af1ff06bc1986437fbe9"},{"author":{"_account_id":6160,"name":"Saurabh Surana","email":"saurabh.cloud@gmail.com","username":"saurabh-surana"},"change_message_id":"e0fbdfacc8622ecb651940c5191742cd63efbff0","unresolved":false,"context_lines":[{"line_number":46,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":47,"context_line":"Cluster Provisioning:"},{"line_number":48,"context_line":"* Once the cluster is successfully provisioned, Taskmanager will try to"},{"line_number":49,"context_line":"provision floating IP on the port from the customer provided network."},{"line_number":50,"context_line":"* If taskmanager fails to provision floating ip on the node, the cluster"},{"line_number":51,"context_line":"will still be created successfully (there might be multiple reasons"},{"line_number":52,"context_line":"why this could fail)."}],"source_content_type":"text/x-rst","patch_set":8,"id":"da20952f_2767f926","line":49,"in_reply_to":"da20952f_3f0e618c","updated":"2015-09-01 19:06:07.000000000","message":"Possible, but doing it in taskmanager, will that pose any issues?\n\nFloating IP provisioning is not a straight forward API with neutron, if we have to do this before instance provisioning then \n1. we need to get a port from user provided network, \n2. get a floating iP and \n3. associate floating ip with that port and then use that port to provision the instance.\n\nThis will introduce multiple neutron API unnecessarily for a simple use case which is again very datastore specific at the moment.\n\nWe don\u0027t want cluster provisioning to fail if the floating IP cannot be created. management console is a add on feature which will not be available directly in case of floating ip provisioning failure.","commit_id":"aeb2caaa72eb419bd8b8af1ff06bc1986437fbe9"}],"specs/mitaka/vertica-floating-ip-on-master-node.rst":[{"author":{"_account_id":4240,"name":"Craig Vyvial","email":"cp16net@gmail.com","username":"cp16net"},"change_message_id":"1810ab2979c9e2e6fae7f6b7feecd4860a42863b","unresolved":false,"context_lines":[{"line_number":61,"context_line":"credentials nobody will be able to login into the console."},{"line_number":62,"context_line":"* Also the floating ip will be associated with customer provided network"},{"line_number":63,"context_line":"so default/management network will still be protected."},{"line_number":64,"context_line":"* If user chooses not to provision cluster with floating IP, on the cluster"},{"line_number":65,"context_line":"create, they can provide a network which doesn\u0027t have router to the"},{"line_number":66,"context_line":"public/ext-network, in that case cluster will be provisioned without"},{"line_number":67,"context_line":"floating ip."}],"source_content_type":"text/x-rst","patch_set":10,"id":"9a8ffd7b_fa0a54d1","line":64,"range":{"start_line":64,"start_character":5,"end_line":64,"end_character":59},"updated":"2015-12-02 22:41:35.000000000","message":"how does a user choose this option or not? Seems like its either on or off.","commit_id":"ccc0e4105b0c1733054b41f979de1bd81b966259"}]}