)]}'
{"rally/verification/tempest/config.ini":[{"author":{"_account_id":7428,"name":"Yaroslav Lobankov","email":"lobankovyv@gmail.com","username":"ylobankov"},"change_message_id":"e3431be5fa4ccc22013f38235421cf4b8af5e7e5","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"instance_type \u003d m1.nano"}],"source_content_type":"text/x-properties","patch_set":1,"id":"9a1a9d01_ca074a16","line":8,"updated":"2015-09-30 21:40:14.000000000","message":"Why do you set the create_isolated_networks option to False? Could you please explain it?","commit_id":"0ab9de6902a2f4fb862e2f2c34953217d5179d7c"},{"author":{"_account_id":9152,"name":"Castulo J. Martinez","email":"castulo.martinez@intel.com","username":"cas"},"change_message_id":"c05e192c2be25b7e78100abef8c3df26e43d0f82","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"instance_type \u003d m1.nano"}],"source_content_type":"text/x-properties","patch_set":1,"id":"9a1a9d01_c2992121","line":8,"in_reply_to":"9a1a9d01_011de50e","updated":"2015-10-08 19:34:53.000000000","message":"I see you are adding this option as part of this blueprint: https://blueprints.launchpad.net/rally/+spec/tempest-in-rally so I am not including it here then to not duplicate efforts.","commit_id":"0ab9de6902a2f4fb862e2f2c34953217d5179d7c"},{"author":{"_account_id":7428,"name":"Yaroslav Lobankov","email":"lobankovyv@gmail.com","username":"ylobankov"},"change_message_id":"a9b5306d22a4c5f10127d56a095ad3fd88bd6faf","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"instance_type \u003d m1.nano"}],"source_content_type":"text/x-properties","patch_set":1,"id":"9a1a9d01_011de50e","line":8,"in_reply_to":"9a1a9d01_0d08fcd8","updated":"2015-10-02 10:22:58.000000000","message":"Ok, but in this case you should specify the fixed_network_name option in the compute section because there may be a few private networks that are visible in all tenants. And Tempest tests will fail with error \"Multiple possible networks found\".","commit_id":"0ab9de6902a2f4fb862e2f2c34953217d5179d7c"},{"author":{"_account_id":9152,"name":"Castulo J. Martinez","email":"castulo.martinez@intel.com","username":"cas"},"change_message_id":"99afa5842fc66a2e1e4b7b6791c77d661dcf963d","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"instance_type \u003d m1.nano"}],"source_content_type":"text/x-properties","patch_set":1,"id":"9a1a9d01_0d08fcd8","line":8,"in_reply_to":"9a1a9d01_ca074a16","updated":"2015-09-30 22:15:47.000000000","message":"The reason is that based on information from the tempest.conf.sample file, it mentions that for some neutron configurations, using isolated_networks doesn\u0027t work, so I wanted to aim to a configuration that would work in most deployments. My understanding was that not using isolated networks should work in all (or most) deployments.\n\n\"If allow_tenant_isolation is set to True and Neutron is enabled, Tempest will try to create a usable network, subnet, and router when needed for each tenant it creates. However in some neutron configurations, like with VLAN provider networks, this doesn\u0027t work. So if set to False the isolated networks will not be created\"","commit_id":"0ab9de6902a2f4fb862e2f2c34953217d5179d7c"},{"author":{"_account_id":7428,"name":"Yaroslav Lobankov","email":"lobankovyv@gmail.com","username":"ylobankov"},"change_message_id":"9a5231ae05f843219c741b72c83b809a04cf4239","unresolved":false,"context_lines":[{"line_number":4,"context_line":"use_stderr \u003d False"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"}],"source_content_type":"text/x-properties","patch_set":3,"id":"7a2fa921_e4185bd5","line":7,"updated":"2015-10-09 10:14:44.000000000","message":"Actually, the default value of this option in Tempest is True. So we don\u0027t need to configure this option. Though it doesn\u0027t make any harm.","commit_id":"0e6209c883178cf34e6aa28db9df8ad1253dadae"},{"author":{"_account_id":7428,"name":"Yaroslav Lobankov","email":"lobankovyv@gmail.com","username":"ylobankov"},"change_message_id":"9a5231ae05f843219c741b72c83b809a04cf4239","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"http_socket_timeout \u003d 30"}],"source_content_type":"text/x-properties","patch_set":3,"id":"7a2fa921_e4693bfa","line":8,"updated":"2015-10-09 10:14:44.000000000","message":"If an OpenStack cload has a few shared internal networks, Tempest tests will fail even though this option is set to False. There is a patch that is intended to solve this issue https://review.openstack.org/#/c/232134/ by configuring the fixed_network_name option. So it makes sense to configure this option once https://review.openstack.org/#/c/232134/ is merged.","commit_id":"0e6209c883178cf34e6aa28db9df8ad1253dadae"},{"author":{"_account_id":7428,"name":"Yaroslav Lobankov","email":"lobankovyv@gmail.com","username":"ylobankov"},"change_message_id":"856cb7bb65d763acb0cfee3268c175c0944d81e9","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"http_socket_timeout \u003d 30"}],"source_content_type":"text/x-properties","patch_set":3,"id":"3a29b11f_cb8364cb","line":8,"in_reply_to":"3a29b11f_08ede524","updated":"2015-10-20 09:15:52.000000000","message":"Yair, you are absolutely right. If a cloud **doesn\u0027t** have any shared network, then no networks will be available for the tests and the tests will fail. But there is a patch (https://review.openstack.org/#/c/232134/) that resolves this issue (at least, in the case of Neutron) by configuring the fixed_network_name option. If this option is configured, Tempest will use only this network for all instances. The patch adds creation of network resources to Tempest context. It will not matter whether the cloud has networks or not, Tempest context will create needed network resources and tests will work. The idea is to configure Tempest config so that we will be able to run Tempest against any clouds without failures.","commit_id":"0e6209c883178cf34e6aa28db9df8ad1253dadae"},{"author":{"_account_id":7428,"name":"Yaroslav Lobankov","email":"lobankovyv@gmail.com","username":"ylobankov"},"change_message_id":"e7d9ef66e034ce6af5eea8053a48a0546a2c6c2b","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"http_socket_timeout \u003d 30"}],"source_content_type":"text/x-properties","patch_set":3,"id":"3a29b11f_dda734bb","line":8,"in_reply_to":"3a29b11f_8cb2f4e3","updated":"2015-10-22 11:34:46.000000000","message":"To avoid failures when a cloud has a few networks that are visible in all tenants.","commit_id":"0e6209c883178cf34e6aa28db9df8ad1253dadae"},{"author":{"_account_id":8576,"name":"Yair Fried","email":"yfried@redhat.com","username":"yfried"},"change_message_id":"ae293dab67be1e08d5808d6a627718e6e722b0fe","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"http_socket_timeout \u003d 30"}],"source_content_type":"text/x-properties","patch_set":3,"id":"3a29b11f_8cb2f4e3","line":8,"in_reply_to":"3a29b11f_cb8364cb","updated":"2015-10-22 10:34:48.000000000","message":"I\u0027m not sure I understand that patch. DO you wish to create a fixed network for any tempest run? If so, why?","commit_id":"0e6209c883178cf34e6aa28db9df8ad1253dadae"},{"author":{"_account_id":8576,"name":"Yair Fried","email":"yfried@redhat.com","username":"yfried"},"change_message_id":"1b3055a0b3411d48447357e3e11aa17de1fbccf1","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"http_socket_timeout \u003d 30"}],"source_content_type":"text/x-properties","patch_set":3,"id":"3a29b11f_08ede524","line":8,"in_reply_to":"7a2fa921_0c8ea027","updated":"2015-10-20 07:32:12.000000000","message":"If a cloud **doesn\u0027t** have any shared network, then no networks will be available for the tests and the test would fail as well.\nWhy do you assume any cloud would have a shared network present prior to testing?","commit_id":"0e6209c883178cf34e6aa28db9df8ad1253dadae"},{"author":{"_account_id":7428,"name":"Yaroslav Lobankov","email":"lobankovyv@gmail.com","username":"ylobankov"},"change_message_id":"859a5e451904197e1049d9797ef031b4aa66b798","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"http_socket_timeout \u003d 30"}],"source_content_type":"text/x-properties","patch_set":3,"id":"7a2fa921_0c8ea027","line":8,"in_reply_to":"7a2fa921_9142d966","updated":"2015-10-12 10:18:50.000000000","message":"Because if a cloud has some networks visible in all tenants, we will get Tempest failures such as \"Multiple possible networks found\". To fix the issue it is enough to specify  the fixed_network_name option. We may not set the create_isolated_networks option to False if we configured \"fixed_network_name\", but it looks like it doesn\u0027t make any harm.","commit_id":"0e6209c883178cf34e6aa28db9df8ad1253dadae"},{"author":{"_account_id":8576,"name":"Yair Fried","email":"yfried@redhat.com","username":"yfried"},"change_message_id":"a348ac75ef415c5c7d2259842b591c2ab0f48848","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"http_socket_timeout \u003d 30"}],"source_content_type":"text/x-properties","patch_set":3,"id":"7a2fa921_9142d966","line":8,"in_reply_to":"7a2fa921_e4693bfa","updated":"2015-10-11 10:30:33.000000000","message":"Why not allow tempest to create the isolated networks?","commit_id":"0e6209c883178cf34e6aa28db9df8ad1253dadae"},{"author":{"_account_id":9152,"name":"Castulo J. Martinez","email":"castulo.martinez@intel.com","username":"cas"},"change_message_id":"7dc15e423218ff588d212826b1f1242cf26cb8d3","unresolved":false,"context_lines":[{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[auth]"},{"line_number":7,"context_line":"allow_tenant_isolation \u003d True"},{"line_number":8,"context_line":"create_isolated_networks \u003d False"},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"[boto]"},{"line_number":11,"context_line":"http_socket_timeout \u003d 30"}],"source_content_type":"text/x-properties","patch_set":3,"id":"7a2fa921_f9fb1a77","line":8,"in_reply_to":"7a2fa921_e4693bfa","updated":"2015-10-09 14:28:46.000000000","message":"Yes, I saw your patch, that is why I didn\u0027t include the creation of a  test network with this fix","commit_id":"0e6209c883178cf34e6aa28db9df8ad1253dadae"}],"rally/verification/tempest/config.py":[{"author":{"_account_id":7428,"name":"Yaroslav Lobankov","email":"lobankovyv@gmail.com","username":"ylobankov"},"change_message_id":"e3431be5fa4ccc22013f38235421cf4b8af5e7e5","unresolved":false,"context_lines":[{"line_number":113,"context_line":"            if services_type2name_map.get(service[\"type\"]) \u003d\u003d servicename:"},{"line_number":114,"context_line":"                return service[\"endpoints\"][0][\"publicURL\"]"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"    def _set_auth_role(self, section_name\u003d\"auth\"):"},{"line_number":117,"context_line":"        keystoneclient \u003d self.clients.keystone()"},{"line_number":118,"context_line":"        roles_list \u003d [role for role in keystoneclient.roles.list()"},{"line_number":119,"context_line":"                      if role.name \u003d\u003d \"_member_\" or"}],"source_content_type":"text/x-python","patch_set":1,"id":"9a1a9d01_4a61fad1","line":116,"updated":"2015-09-30 21:40:14.000000000","message":"Why do you create these roles at all? :) It should work fine without them.","commit_id":"0ab9de6902a2f4fb862e2f2c34953217d5179d7c"},{"author":{"_account_id":9152,"name":"Castulo J. Martinez","email":"castulo.martinez@intel.com","username":"cas"},"change_message_id":"99afa5842fc66a2e1e4b7b6791c77d661dcf963d","unresolved":false,"context_lines":[{"line_number":113,"context_line":"            if services_type2name_map.get(service[\"type\"]) \u003d\u003d servicename:"},{"line_number":114,"context_line":"                return service[\"endpoints\"][0][\"publicURL\"]"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"    def _set_auth_role(self, section_name\u003d\"auth\"):"},{"line_number":117,"context_line":"        keystoneclient \u003d self.clients.keystone()"},{"line_number":118,"context_line":"        roles_list \u003d [role for role in keystoneclient.roles.list()"},{"line_number":119,"context_line":"                      if role.name \u003d\u003d \"_member_\" or"}],"source_content_type":"text/x-python","patch_set":1,"id":"9a1a9d01_cd0a0479","line":116,"in_reply_to":"9a1a9d01_4a61fad1","updated":"2015-09-30 22:15:47.000000000","message":"You are right, it would probably work fine without them, but based on tempest documentation it says that in some cases you might need to assign roles. Again, I was aiming to set the tempest configuration with values that would work best in most deployments, and based on info from the tempest configuration guide (http://docs.openstack.org/developer/tempest/configuration.html#tenant-isolation) I saw that not using them in an environment that do use them may cause the tests to fail, so I think it is better setting it and not needing it than needing it and not having it.\n\n\"It is worth pointing out that depending on your cloud configuration you might need to assign a role to each of the users created Tempest’s tenant isolation. This can be set using the tempest_roles option. It takes in a list of role names each of which will be assigned to each of the users created by tenant isolation. This option will not have any effect when set and tempest is not configured to use tenant isolation.\"","commit_id":"0ab9de6902a2f4fb862e2f2c34953217d5179d7c"},{"author":{"_account_id":9152,"name":"Castulo J. Martinez","email":"castulo.martinez@intel.com","username":"cas"},"change_message_id":"c05e192c2be25b7e78100abef8c3df26e43d0f82","unresolved":false,"context_lines":[{"line_number":113,"context_line":"            if services_type2name_map.get(service[\"type\"]) \u003d\u003d servicename:"},{"line_number":114,"context_line":"                return service[\"endpoints\"][0][\"publicURL\"]"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"    def _set_auth_role(self, section_name\u003d\"auth\"):"},{"line_number":117,"context_line":"        keystoneclient \u003d self.clients.keystone()"},{"line_number":118,"context_line":"        roles_list \u003d [role for role in keystoneclient.roles.list()"},{"line_number":119,"context_line":"                      if role.name \u003d\u003d \"_member_\" or"}],"source_content_type":"text/x-python","patch_set":1,"id":"9a1a9d01_42ff5134","line":116,"in_reply_to":"9a1a9d01_66307708","updated":"2015-10-08 19:34:53.000000000","message":"I see... it makes sense. I will remove this from the fix then.","commit_id":"0ab9de6902a2f4fb862e2f2c34953217d5179d7c"},{"author":{"_account_id":7428,"name":"Yaroslav Lobankov","email":"lobankovyv@gmail.com","username":"ylobankov"},"change_message_id":"a9b5306d22a4c5f10127d56a095ad3fd88bd6faf","unresolved":false,"context_lines":[{"line_number":113,"context_line":"            if services_type2name_map.get(service[\"type\"]) \u003d\u003d servicename:"},{"line_number":114,"context_line":"                return service[\"endpoints\"][0][\"publicURL\"]"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"    def _set_auth_role(self, section_name\u003d\"auth\"):"},{"line_number":117,"context_line":"        keystoneclient \u003d self.clients.keystone()"},{"line_number":118,"context_line":"        roles_list \u003d [role for role in keystoneclient.roles.list()"},{"line_number":119,"context_line":"                      if role.name \u003d\u003d \"_member_\" or"}],"source_content_type":"text/x-python","patch_set":1,"id":"9a1a9d01_66307708","line":116,"in_reply_to":"9a1a9d01_cd0a0479","updated":"2015-10-02 10:22:58.000000000","message":"Tempest\u0027s isolated credentials mechanism assigns the proper default roles itself to indicate a users membership. IMHO, we don\u0027t need to configure this option. Please, read the second comment from Matthew Treinish for what this option is actually intended. https://bugs.launchpad.net/tempest/+bug/1474193 .","commit_id":"0ab9de6902a2f4fb862e2f2c34953217d5179d7c"}]}
