On Tue, Apr 5, 2016 at 11:53 AM, Minying Lu <m...@bu.edu> wrote: > Thank you for your awesome feedbacks! > > >> Another option is to add those tests to keystone itself (if you are not >>> including tests that triggers other components APIs). See >>> https://blueprints.launchpad.net/keystone/+spec/keystone-tempest-plugin-tests >>> >>> >> >> > knikolla and I are looking into the keystone-tempest-plugin too thanks > Rodrigo! > > >> Again though, the problem is not where the tests live but where we run >> them. To practically run these tests we need to either add K2K testing >> support to devstack (not sure this is appropriate) or come up with a new >> test environment that deploys 2 keystones and federation support that we >> can CI against in the gate. This is doable but i think something we need >> support with from infra before worrying about tempest. >> >> > We have engineers in the team that are communicating with the infra team > on how to set up a environment that runs the federation test. We're > thinking about creating a 2 devstack setup with the keystones configured as > Identity provider and service provider with federation support. Meanwhile I > can just work on writing the test in a pre-configured environment that's > the same as the 2 devstack setup. >
Awesome, please share your work so I can help on that front too! > > >> >> >>> >>>> The fly in the ointment for this case will be CI though. For tests to >>>> live in >>>> tempest they need to be verified by a CI system before they can land. >>>> So to >>>> land the additional testing in tempest you'll have to also ensure there >>>> is a >>>> CI job setup in infra to configure the necessary environment. While I >>>> think >>>> this is a good thing to have in the long run, it's not necessarily a >>>> small >>>> undertaking. >>>> >>> >>>> -Matt Treinish >>>> >>>> >>>> __________________________________________________________________________ >>>> OpenStack Development Mailing List (not for usage questions) >>>> Unsubscribe: >>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>> >>>> >>> >>> >>> -- >>> Rodrigo Duarte Sousa >>> Senior Quality Engineer @ Red Hat >>> MSc in Computer Science >>> http://rodrigods.com >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Rodrigo Duarte Sousa Senior Quality Engineer @ Red Hat MSc in Computer Science http://rodrigods.com
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
