On Feb 7, 2014, at 10:16 AM, Matthew Treinish <mtrein...@kortar.org<mailto:mtrein...@kortar.org>> wrote:
So the flag to make tenant isolation was always a temporary thing just for neutron so we could work out stabilizing things. It's been on by default for all the other jobs for as long as I can remember. If you think that we've reached the point were we can greenlight it everywhere, I'll push out the infra changes to do that. +1000 to enabling isolation everywhere - do not executed anymore non-isolated jobs for neutron. I think this was always the plan anyway. Yeah, that makes sense, but I still think we should keep 4 tempest jobs running for the neutron queue. Do you have any ideas for other configs or should we just duplicate the existing 2? (postgres and mysql) For now we could run the existing 2 with and without config drive enabled. Once the upstream kernel bug is addressed, we should have one config that enables key injection with Neutron. mark
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev