- 1 Interop Challenge
Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)
The interop challenge was started in July 2016 to create a set of common workloads/tests to be executed across multiple OpenStack distributions and/or cloud deployment models. The participants in this challenge will work together to prove once and for all that OpenStack-Powered clouds are interoperable.
Original presentation used during team creation: Interoperability Challenge Kick-Off
The team will complete the Interop Challenge prior to the next summit working together with partners in the OpenStack Foundation.
Schedule: Wednesdays at 1400 UTC IRC Channel (on freenode):
#openstack-defcoreLogs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/
Agenda * Review action items from previous meeting * Test candidates review ** Open reviews: https://review.openstack.org/#/q/status:open+project:openstack/osops-tools-contrib * Discuss how/where to share results (results repository) * Open Discussion
Previous Etherpads: 2016-08-03
- Members will meet regularly using the OpenStack DefCore channel on IRC
- The team will communicate on the OpenStack DefCore mailing list and add the [interop] tag to the subject of messages related to the interop challenge.
- The team may also have discussions in Gerrit on specific tools/workloads
|1||Create interop challenge and team||Completed|
|2||Identify tools/scripts that will be used to validate interoperability||In-Progress|
|3||Execute tests, resolve/document any issues, and share results||Pending|
|4||Create read-out for Interop Challenge||Pending|
|5||Share findings at the OpenStack Summit in Barcelona||Pending|
How to Join
If you are interested in joining the interop, please join the the OpenStack DefCore mailing list and send a message with the tag "[interop]" in the subject line. Please identify one business and technical leader from your organization in the introductory email. Welcome aboard!
Scripts/Tools used for Interop Challenge
The interop challenge requires that we use common testing scripts and validation methods across multiple clouds. The team has agreed to post all scripts to the osops-tools-contrib repository since the templates/scripts used for the Interop Challenge are also useful outside of this context and could serve as examples on how to use various tools to deploy applications on OpenStack-Powered Clouds.
The current list of proposed tooling includes:
- OpenStack Heat
The current list of workloads includes:
- LAMP (Linux, Apache, MySQL, PHP) Stack
How to Propose/Submit new tools/workloads
Any participating member of the Interop Challenge can submit additional scripts/workloads for review by the team. The script to leverage the new tool and/or deploy the new workload should be posted to the osops-tools-contrib repository. Information on how to contribute to OpenStack repositories can be found in the OpenStack Developer's Guide.
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: "[interop] New tool/workload proposal:
brief description" and provide a link to the code review page for the change along with an overview of the tool or where people can find more information. The proposal will be reviewed by the team and, if necessary, added to the agenda for an upcoming meeting.
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib
Directory structure is proposed below: /heat - use heat template to create workload lampstack dockerswarm-coreo ... /terraform - use terraform to create workload lampstack dockerswarme-coreos ... /xxx - use xxx to create workload
Test Candidate Process
(Proposed; subject to change after 08-10-2016 meeting)
- Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)
- Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)
- We may need to talk about the content of each work load, use lamp stack as an example.
- How substantial should the application be, if doing wordpress, do we also creates some posts, pages?
- Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?
- LAMP stack workload (created by Tong Li/IBM)
- Currently developed using terraform to deploy workload, looking into Ansible
- HEAT template (submitted by Craig Sterrett & Leong/Intel)
This section will be completed after August 10th, 2016.