[openstack-dev] [qa] API schema location
m.koderer at telekom.de
Tue Mar 18 11:34:57 UTC 2014
On Tue, 18 Marc 2014 12:00:00 +0100
Christopher Yeoh [mailto:cbkyeoh at gmail.com] wrote:
> On Tue, 18 Mar 2014 10:39:19 +0100
> "Koderer, Marc" <m.koderer at telekom.de> wrote:
> > I just recognized that we have very similar interface definitions in
> > tempest/api_schema and etc/schema:
> > https://github.com/openstack/tempest/tree/master/etc/schemas
> > https://github.com/openstack/tempest/tree/master/tempest/api_schema
> > Any objections if I move them to a single location? I'd prefer to use
> > json as file format instead of .py. As final goal we should find a way
> > how to merge them competently but I feel like this is something for
> > the design summit ;)
> Heh we just moved them but I'm open to other suggestions - they are are
> specific to API testing though aren't they? Long term the idea is that
> they should be generated by Nova rather than tempest. I think to prevent
> unintentional changes we'd probably cache a copy in tempest though rather
> than dynamically query them.
Sry that I didn't recognized this review.
Both definitions are coupled to API testing, yes.
> My feeling at the moment is that they should .py files.
> Because I think there's cases where we will want to have some schema
> definitions based on others or share common parts and use bits of python
> code to achieve this. For example availability zone list and detailed
> listing have a lot in common (detailed listing just has a more
> parameters). I think there'll be similar cases for v2 and v3 versions as
> well. While we're still manually generating them and keeping them up to
> date I think it's worth sharing as much as we can.
Ok understood. We just converted the negative testing
definitions to json files due to review findings..
It's just very confusing for new people if they see
two separate folders with schema definitions.
But unfortunately there isn't an easy way.
> I agree there's a lot of commonality and we should long term just have one
> schema definition. There's quite a bit to discuss (eg level of strictness
> is currently different) in this area and a summit session about it would
> be very useful.
> > Regards,
> > Marc
> > DEUTSCHE TELEKOM AG
> > Digital Business Unit, Cloud Services (P&I) Marc Koderer Cloud
> > Technology Software Developer T-Online-Allee 1, 64211 Darmstadt
> > E-Mail: m.koderer at telekom.de
> > www.telekom.com
> > LIFE IS FOR SHARING.
> > DEUTSCHE TELEKOM AG
> > Supervisory Board: Prof. Dr. Ulrich Lehner (Chairman) Board of
> > Management: René Obermann (Chairman), Reinhard Clemens, Niek Jan van
> > Damme, Timotheus Höttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr.
> > Marion Schick Commercial register: Amtsgericht Bonn HRB 6794
> > Registered office: Bonn
> > BIG CHANGES START SMALL – CONSERVE RESOURCES BY NOT PRINTING EVERY
> > E-MAIL.
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev