[openstack-dev] [heat] Split tempest plugin from heat

Rabi Mishra ramishra at redhat.com
Sun Nov 19 08:08:51 UTC 2017

Hi All,

As part of community goal[1] for Queens, we've completed the repo split and
created the new project[2].

The next objective to is to use the new plugin in our jobs. As we've merged
some changes after the split, I've synced them and fixed some minor issues
before using it in the gate jobs.

These are very small changes and I would suggest we review/land them on
priority (we don't have to keep syncing them again and again for broken
jobs). We should probably *not approve* any changes to integration tests in
heat before these go in.

- Changes in heat-tempest-plugin (sync  missing patches and fixes)


- Use heat-tempest-plugin for integration jobs

- Use heat-tempest-plugin for grenade job

- Add heat integration jobs to heat-tempest-plugin check/gate queue
  I guess this would result in some issues, where we can't add any changes
to heat that breaks the existing tests, as the changes for both projects
would have a circular dependency (not sure how it works atm with other

- Remove plugin an integration tests from heat (This has -1 atm as
releasenote job is broken, waiting for infra to fix it)

I've also created an etherpad[3] to track these.

Also, the plugin project is expected to be branchless (we may not backport
these job changes to stable branches soon though), we've to find  a  way to
run additional tests for any new feature only on > <release/branch>. AFAIK,
other projects check api microversions supported and without microversions
in heat, may be we've find an alternate way.
Rabi Mishra

[2] https://git.openstack.org/cgit/openstack/heat-tempest-plugin
[3] https://etherpad.openstack.org/p/heat-tempest-plugin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171119/ab93ad41/attachment.html>

More information about the OpenStack-dev mailing list