<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.openstack.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Topol</id>
		<title>OpenStack - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.openstack.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Topol"/>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/wiki/Special:Contributions/Topol"/>
		<updated>2026-07-10T17:11:39Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.28.2</generator>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=144763</id>
		<title>Interop Challenge</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=144763"/>
				<updated>2016-12-09T14:00:09Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Scope */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Interop Challenge ==&lt;br /&gt;
&amp;quot;Status: Making decisions on workloads second round Interop Challenge (as of Dec 7, 2016)''&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
[[File:InteropKeynote.JPG|200px|thumb|left|Interop Challenge Keynote OpenStack Barcelona]]&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off] &lt;br /&gt;
&lt;br /&gt;
OpenStack Barcelona Summit Interoperability Challenge: [https://www.openstack.org/videos/video/openstack-interoperability-challenge-running-unmodified-apps-in-any-openstack-cloud OpenStack Keynote Video] &lt;br /&gt;
&lt;br /&gt;
Project repository: &amp;lt;br /&amp;gt;&lt;br /&gt;
https://github.com/openstack/interop-workloads&amp;lt;br /&amp;gt;&lt;br /&gt;
https://git.openstack.org/cgit/openstack/interop-workloads&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Duration ===&lt;br /&gt;
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Information ===&lt;br /&gt;
 Schedule: Wednesdays at 1500 UTC&lt;br /&gt;
 IRC Channel (on freenode): &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting-cp&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
 Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/&lt;br /&gt;
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&amp;amp;iso=20161214T15&amp;amp;p1=%3A Wednesday, December 14th, 2016 at 1500 UTC]'''&lt;br /&gt;
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-12-14 2016-12-14]'''&lt;br /&gt;
 '''Agenda'''&lt;br /&gt;
 * see the etherpad &lt;br /&gt;
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-12-07 2016-12-07]&lt;br /&gt;
&lt;br /&gt;
==== Communication methods====&lt;br /&gt;
* Members will meet regularly using the OpenStack DefCore channel on IRC&lt;br /&gt;
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.&lt;br /&gt;
* The team may also have discussions in Gerrit on specific tools/workloads&lt;br /&gt;
&lt;br /&gt;
=== Milestones ===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Milestone !! Goal !! References !! Status&lt;br /&gt;
|-&lt;br /&gt;
| 1 || ''Create interop challenge and team''  ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Execute tests, resolve/document any issues, and share results ||  || ''In-Progress''&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Create read-out for Interop Challenge || || Pending&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== How to Join ===&lt;br /&gt;
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag &amp;quot;[interop]&amp;quot; in the subject line.  Please identify one business and technical leader from your organization in the introductory email.  Welcome aboard!&lt;br /&gt;
&lt;br /&gt;
Current Participants Alphabetical Order&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner&lt;br /&gt;
|-&lt;br /&gt;
| AT&amp;amp;T || Kilo || LAMPstack tested with Ansible || Success || || Elise Eiden &lt;br /&gt;
|-&lt;br /&gt;
| Canonical || Mitaka and Newton  || LAMP and Dockerswarm ||Sucess || || Mark Baker&lt;br /&gt;
|-&lt;br /&gt;
| Cisco || Liberty ||  || Success || Rohit Agarwalla || Rohit Agarwalla&lt;br /&gt;
|-&lt;br /&gt;
| Fujitsu || Icehouse and Kilo  || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler &lt;br /&gt;
|-&lt;br /&gt;
| HPE || Mitaka  || RefStack Pass. Tested with Ansible || Success || Ghe Rivero || Simon  McCartney&lt;br /&gt;
|-&lt;br /&gt;
| Huawei || Juno || DockerSwarm tested with Terraform, LAMPStack tested with Ansible || Success || Jichun Liu(Huawei) || Zhenyu Zheng||&lt;br /&gt;
|-&lt;br /&gt;
| DT OTC (public cloud) || Juno || LAMPStack tested with Ansible || Success ||  ||Daniela Ebert ||&lt;br /&gt;
|-&lt;br /&gt;
| IBM || Liberty and Mitaka ||  || Success || Tong Li (IBM) || Tong Li (IBM)&lt;br /&gt;
|-&lt;br /&gt;
| Linaro || Newton on AArch64 ||  || Success  || Gema Gomez (Linaro) || Gema Gomez ||&lt;br /&gt;
|-&lt;br /&gt;
| Mirantis || Mitaka  ||  || Success || Craig Peters (Mirantis) ||Craig Peters cpeters@mirantis.com&lt;br /&gt;
|-&lt;br /&gt;
| Intel Corporation, OSIC || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares&lt;br /&gt;
|-&lt;br /&gt;
| OVH || Juno/Kilo ||  || Success || Tong Li (IBM) || Damien Rannou (OVH)&lt;br /&gt;
|-&lt;br /&gt;
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler&lt;br /&gt;
|-&lt;br /&gt;
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado&lt;br /&gt;
|-&lt;br /&gt;
| SUSE || Liberty and Mitaka || Tested with Ansible || Success || contact Roman Arcea (SUSE) || Pete Chadwick - placeholder&lt;br /&gt;
|-&lt;br /&gt;
| VMware || Mitaka || || Success || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||&lt;br /&gt;
|-&lt;br /&gt;
| DreamHost || Mitaka  ||  LAMPstack Ansible || Success || || Stefano Maffuli&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Scripts/Tools used for Interop Challenge ===&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib 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.&lt;br /&gt;
&lt;br /&gt;
The current list of proposed tooling includes:&lt;br /&gt;
* Ansible&lt;br /&gt;
* Terraform&lt;br /&gt;
* OpenStack Heat&lt;br /&gt;
&lt;br /&gt;
The current list of workloads includes:&lt;br /&gt;
* LAMP (Linux, Apache, MySQL, PHP) Stack&lt;br /&gt;
* Dockerswarm-coreos&lt;br /&gt;
* NFV&lt;br /&gt;
&lt;br /&gt;
==== How to Propose/Submit new tools/workloads ====&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository.  Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].&lt;br /&gt;
&lt;br /&gt;
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: &amp;quot;[interop] New tool/workload proposal: &amp;lt;code&amp;gt;brief description&amp;lt;/code&amp;gt;&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
==== Directory Structure ====&lt;br /&gt;
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib&lt;br /&gt;
    Directory structure is proposed below:&lt;br /&gt;
    /heat  - use heat template to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarm-coreo&lt;br /&gt;
        ...&lt;br /&gt;
    /terraform - use terraform to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarme-coreos&lt;br /&gt;
        ...&lt;br /&gt;
    /xxx - use xxx to create workload&lt;br /&gt;
&lt;br /&gt;
=== Test Candidate Process ===&lt;br /&gt;
(Proposed; subject to change after 08-10-2016 meeting)&lt;br /&gt;
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)&lt;br /&gt;
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)&lt;br /&gt;
** We may need to talk about the content of each work load, use lamp stack as an example.&lt;br /&gt;
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?&lt;br /&gt;
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?&lt;br /&gt;
* LAMP stack workload (created by Tong Li/IBM)&lt;br /&gt;
** https://review.openstack.org/#/c/351879/ &lt;br /&gt;
** Currently developed using terraform to deploy workload, looking into Ansible&lt;br /&gt;
* HEAT template (submitted by Craig Sterrett &amp;amp; Leong/Intel) &lt;br /&gt;
**  https://review.openstack.org/#/c/351799/&lt;br /&gt;
&lt;br /&gt;
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )&lt;br /&gt;
&lt;br /&gt;
=== RefStack Testing and Results Upload ===&lt;br /&gt;
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst&lt;br /&gt;
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once tests are run,  test results can be uploaded to the official  [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.&lt;br /&gt;
*RefStack team highly recommends to upload test results with signatures and not anonymously.  By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Interop Challenge, DefCore team recommends to run complete API tests  (not just the must-pass tests).  Following is the command to run the tests:&lt;br /&gt;
 ./refstack-client test -c &amp;lt;Path of the tempest configuration file to use&amp;gt; -v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For questions, please contact us at IRC channels  #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]&lt;br /&gt;
&lt;br /&gt;
=== Where/How to Share Test Results ===&lt;br /&gt;
Rather than collecting binary &amp;quot;pass/fail&amp;quot; results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not.  Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with &amp;quot;[interop-challenge] Workload Results&amp;quot; in the subject line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 1.) Your name:  &lt;br /&gt;
 2.) Your email: &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization:   &lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested:&lt;br /&gt;
 5.) Version of OpenStack the product uses: &lt;br /&gt;
 6.) Link to RefStack results for this product: &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
&lt;br /&gt;
Here's a fictional example of what the email template might look like when filled out:&lt;br /&gt;
&lt;br /&gt;
 1.) Your name: Jane Doe  &lt;br /&gt;
 2.) Your email: jdoe@supercoolsoftware.com &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization: XYZ, Inc.&lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5&lt;br /&gt;
 5.) Version of OpenStack the product uses: Liberty&lt;br /&gt;
 6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? No&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
     &amp;quot;Error in fetching the floating IP's: no floating IP addresses available&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
 &lt;br /&gt;
     SuperCoolCloud doesn't use floating IP addresses.  Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
     Not very.  Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says &amp;quot;if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead&amp;quot;).&lt;br /&gt;
 &lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
  &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=File:InteropKeynote.JPG&amp;diff=144762</id>
		<title>File:InteropKeynote.JPG</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=File:InteropKeynote.JPG&amp;diff=144762"/>
				<updated>2016-12-09T13:45:31Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=135427</id>
		<title>Interop Challenge</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=135427"/>
				<updated>2016-10-21T20:56:12Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* How to Join */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Interop Challenge ==&lt;br /&gt;
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]&lt;br /&gt;
&lt;br /&gt;
=== Duration ===&lt;br /&gt;
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Information ===&lt;br /&gt;
 Schedule: Wednesdays at 1400 UTC&lt;br /&gt;
 IRC Channel (on freenode): &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting-cp&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
 Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/&lt;br /&gt;
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&amp;amp;iso=20161012T14&amp;amp;p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''&lt;br /&gt;
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''&lt;br /&gt;
 '''Agenda'''&lt;br /&gt;
 * see the etherpad &lt;br /&gt;
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]&lt;br /&gt;
&lt;br /&gt;
==== Communication methods====&lt;br /&gt;
* Members will meet regularly using the OpenStack DefCore channel on IRC&lt;br /&gt;
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.&lt;br /&gt;
* The team may also have discussions in Gerrit on specific tools/workloads&lt;br /&gt;
&lt;br /&gt;
=== Milestones ===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Milestone !! Goal !! References !! Status&lt;br /&gt;
|-&lt;br /&gt;
| 1 || ''Create interop challenge and team''  ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Execute tests, resolve/document any issues, and share results ||  || ''In-Progress''&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Create read-out for Interop Challenge || || Pending&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== How to Join ===&lt;br /&gt;
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag &amp;quot;[interop]&amp;quot; in the subject line.  Please identify one business and technical leader from your organization in the introductory email.  Welcome aboard!&lt;br /&gt;
&lt;br /&gt;
Current Participants Alphabetical Order&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner&lt;br /&gt;
|-&lt;br /&gt;
| AT&amp;amp;T || Kilo || LAMPstack tested with Ansible || Success || || Elise Eiden &lt;br /&gt;
|-&lt;br /&gt;
| Canonical || Mitaka and Newton  ||  || || || Mark Baker&lt;br /&gt;
|-&lt;br /&gt;
| Cisco || Liberty ||  || Success || Rohit Agarwalla || Rohit Agarwalla&lt;br /&gt;
|-&lt;br /&gt;
| Fujitsu || Icehouse and Kilo  || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler &lt;br /&gt;
|-&lt;br /&gt;
| HPE || Mitaka  || RefStack Pass. Tested with Ansible || Success || Ghe Rivero || Simon  McCartney&lt;br /&gt;
|-&lt;br /&gt;
| Huawei || Juno || DockerSwarm tested with Terraform, LAMPStack tested with Ansible || Success || Jichun Liu(Huawei) || Zhenyu Zheng||&lt;br /&gt;
|-&lt;br /&gt;
| DT OTC (public cloud) || Juno || LAMPStack tested with Ansible || Success ||  ||Daniela Ebert ||&lt;br /&gt;
|-&lt;br /&gt;
| IBM || Liberty and Mitaka ||  || Success || Tong Li (IBM) || Tong Li (IBM)&lt;br /&gt;
|-&lt;br /&gt;
| Linaro || Newton on AArch64 ||  || Success  || Gema Gomez (Linaro) || Gema Gomez ||&lt;br /&gt;
|-&lt;br /&gt;
| Mirantis || Mitaka  ||  || Success || Craig Peters (Mirantis) ||Craig Peters cpeters@mirantis.com&lt;br /&gt;
|-&lt;br /&gt;
| Intel Corporation, OSIC || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares&lt;br /&gt;
|-&lt;br /&gt;
| OVH || Juno/Kilo ||  || Success || Tong Li (IBM) || Damien Rannou (OVH)&lt;br /&gt;
|-&lt;br /&gt;
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler&lt;br /&gt;
|-&lt;br /&gt;
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado&lt;br /&gt;
|-&lt;br /&gt;
| SUSE || Liberty and Mitaka || Tested with Ansible || Success || contact Roman Arcea (SUSE) || Pete Chadwick - placeholder&lt;br /&gt;
|-&lt;br /&gt;
| VMware || Mitaka || || Success || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||&lt;br /&gt;
|-&lt;br /&gt;
| DreamHost || Mitaka  ||  LAMPstack Ansible || Success || || Stefano Maffuli&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Scripts/Tools used for Interop Challenge ===&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib 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.&lt;br /&gt;
&lt;br /&gt;
The current list of proposed tooling includes:&lt;br /&gt;
* Ansible&lt;br /&gt;
* Terraform&lt;br /&gt;
* OpenStack Heat&lt;br /&gt;
&lt;br /&gt;
The current list of workloads includes:&lt;br /&gt;
* LAMP (Linux, Apache, MySQL, PHP) Stack&lt;br /&gt;
* Dockerswarm-coreos&lt;br /&gt;
* NFV&lt;br /&gt;
&lt;br /&gt;
==== How to Propose/Submit new tools/workloads ====&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository.  Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].&lt;br /&gt;
&lt;br /&gt;
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: &amp;quot;[interop] New tool/workload proposal: &amp;lt;code&amp;gt;brief description&amp;lt;/code&amp;gt;&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
==== Directory Structure ====&lt;br /&gt;
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib&lt;br /&gt;
    Directory structure is proposed below:&lt;br /&gt;
    /heat  - use heat template to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarm-coreo&lt;br /&gt;
        ...&lt;br /&gt;
    /terraform - use terraform to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarme-coreos&lt;br /&gt;
        ...&lt;br /&gt;
    /xxx - use xxx to create workload&lt;br /&gt;
&lt;br /&gt;
=== Test Candidate Process ===&lt;br /&gt;
(Proposed; subject to change after 08-10-2016 meeting)&lt;br /&gt;
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)&lt;br /&gt;
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)&lt;br /&gt;
** We may need to talk about the content of each work load, use lamp stack as an example.&lt;br /&gt;
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?&lt;br /&gt;
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?&lt;br /&gt;
* LAMP stack workload (created by Tong Li/IBM)&lt;br /&gt;
** https://review.openstack.org/#/c/351879/ &lt;br /&gt;
** Currently developed using terraform to deploy workload, looking into Ansible&lt;br /&gt;
* HEAT template (submitted by Craig Sterrett &amp;amp; Leong/Intel) &lt;br /&gt;
**  https://review.openstack.org/#/c/351799/&lt;br /&gt;
&lt;br /&gt;
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )&lt;br /&gt;
&lt;br /&gt;
=== RefStack Testing and Results Upload ===&lt;br /&gt;
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst&lt;br /&gt;
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once tests are run,  test results can be uploaded to the official  [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.&lt;br /&gt;
*RefStack team highly recommends to upload test results with signatures and not anonymously.  By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Interop Challenge, DefCore team recommends to run complete API tests  (not just the must-pass tests).  Following is the command to run the tests:&lt;br /&gt;
 ./refstack-client test -c &amp;lt;Path of the tempest configuration file to use&amp;gt; -v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For questions, please contact us at IRC channels  #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]&lt;br /&gt;
&lt;br /&gt;
=== Where/How to Share Test Results ===&lt;br /&gt;
Rather than collecting binary &amp;quot;pass/fail&amp;quot; results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not.  Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with &amp;quot;[interop-challenge] Workload Results&amp;quot; in the subject line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 1.) Your name:  &lt;br /&gt;
 2.) Your email: &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization:   &lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested:&lt;br /&gt;
 5.) Version of OpenStack the product uses: &lt;br /&gt;
 6.) Link to RefStack results for this product: &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
&lt;br /&gt;
Here's a fictional example of what the email template might look like when filled out:&lt;br /&gt;
&lt;br /&gt;
 1.) Your name: Jane Doe  &lt;br /&gt;
 2.) Your email: jdoe@supercoolsoftware.com &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization: XYZ, Inc.&lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5&lt;br /&gt;
 5.) Version of OpenStack the product uses: Liberty&lt;br /&gt;
 6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? No&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
     &amp;quot;Error in fetching the floating IP's: no floating IP addresses available&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
 &lt;br /&gt;
     SuperCoolCloud doesn't use floating IP addresses.  Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
     Not very.  Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says &amp;quot;if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead&amp;quot;).&lt;br /&gt;
 &lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
  &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134472</id>
		<title>Interop Challenge</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134472"/>
				<updated>2016-10-07T20:34:06Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* How to Join */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Interop Challenge ==&lt;br /&gt;
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]&lt;br /&gt;
&lt;br /&gt;
=== Duration ===&lt;br /&gt;
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Information ===&lt;br /&gt;
 Schedule: Wednesdays at 1400 UTC&lt;br /&gt;
 IRC Channel (on freenode): &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting-cp&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
 Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/&lt;br /&gt;
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&amp;amp;iso=20161012T14&amp;amp;p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''&lt;br /&gt;
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''&lt;br /&gt;
 '''Agenda'''&lt;br /&gt;
 * see the etherpad &lt;br /&gt;
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]&lt;br /&gt;
&lt;br /&gt;
==== Communication methods====&lt;br /&gt;
* Members will meet regularly using the OpenStack DefCore channel on IRC&lt;br /&gt;
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.&lt;br /&gt;
* The team may also have discussions in Gerrit on specific tools/workloads&lt;br /&gt;
&lt;br /&gt;
=== Milestones ===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Milestone !! Goal !! References !! Status&lt;br /&gt;
|-&lt;br /&gt;
| 1 || ''Create interop challenge and team''  ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Execute tests, resolve/document any issues, and share results ||  || ''In-Progress''&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Create read-out for Interop Challenge || || Pending&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== How to Join ===&lt;br /&gt;
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag &amp;quot;[interop]&amp;quot; in the subject line.  Please identify one business and technical leader from your organization in the introductory email.  Welcome aboard!&lt;br /&gt;
&lt;br /&gt;
Current Participants Alphabetical Order&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner&lt;br /&gt;
|-&lt;br /&gt;
| AT&amp;amp;T ||  ||  ||  || || Elise Eiden &lt;br /&gt;
|-&lt;br /&gt;
| Canonical || Mitaka and Newton  ||  || || || Mark Baker&lt;br /&gt;
|-&lt;br /&gt;
| Cisco || Liberty ||  || Success || Rohit Agarwalla || Rohit Agarwalla&lt;br /&gt;
|-&lt;br /&gt;
| Fujitsu || Kilo  || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler &lt;br /&gt;
|-&lt;br /&gt;
| Hitachi ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| HPE ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Huawei ||  ||  ||  || || zheng zhen yu||&lt;br /&gt;
|-&lt;br /&gt;
| DT OTC (public cloud) ||  ||  || ||  ||Daniela Ebert ||&lt;br /&gt;
|-&lt;br /&gt;
| IBM || Liberty and Mitaka ||  || Success || Tong Li (IBM) || Tong Li (IBM)&lt;br /&gt;
|-&lt;br /&gt;
| Linaro || Newton on AArch64 ||  ||  || || Gema Gomez ||&lt;br /&gt;
|-&lt;br /&gt;
| Mirantis || Mitaka  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| NetApp ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Osic (Intel+Rackspace) || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares&lt;br /&gt;
|-&lt;br /&gt;
| OVH || Juno/Kilo ||  || Success || Tong Li (IBM) || pilgrimstack&lt;br /&gt;
|-&lt;br /&gt;
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler&lt;br /&gt;
|-&lt;br /&gt;
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado&lt;br /&gt;
|-&lt;br /&gt;
| SUSE || Liberty and Mitaka || Tested with Terraform || Success || contact Roman Arcea (SUSE) || Pete Chadwick - placeholder&lt;br /&gt;
|-&lt;br /&gt;
| VMware || Mitaka || || Success** (**one issue w/rescanning SCSI bus, investigating best fix) || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||&lt;br /&gt;
|-&lt;br /&gt;
| DreamHost ||  ||  ||  || || Stefano Maffuli&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Scripts/Tools used for Interop Challenge ===&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib 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.&lt;br /&gt;
&lt;br /&gt;
The current list of proposed tooling includes:&lt;br /&gt;
* Ansible&lt;br /&gt;
* Terraform&lt;br /&gt;
* OpenStack Heat&lt;br /&gt;
&lt;br /&gt;
The current list of workloads includes:&lt;br /&gt;
* LAMP (Linux, Apache, MySQL, PHP) Stack&lt;br /&gt;
* Dockerswarm-coreos&lt;br /&gt;
* NFV&lt;br /&gt;
&lt;br /&gt;
==== How to Propose/Submit new tools/workloads ====&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository.  Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].&lt;br /&gt;
&lt;br /&gt;
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: &amp;quot;[interop] New tool/workload proposal: &amp;lt;code&amp;gt;brief description&amp;lt;/code&amp;gt;&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
==== Directory Structure ====&lt;br /&gt;
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib&lt;br /&gt;
    Directory structure is proposed below:&lt;br /&gt;
    /heat  - use heat template to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarm-coreo&lt;br /&gt;
        ...&lt;br /&gt;
    /terraform - use terraform to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarme-coreos&lt;br /&gt;
        ...&lt;br /&gt;
    /xxx - use xxx to create workload&lt;br /&gt;
&lt;br /&gt;
=== Test Candidate Process ===&lt;br /&gt;
(Proposed; subject to change after 08-10-2016 meeting)&lt;br /&gt;
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)&lt;br /&gt;
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)&lt;br /&gt;
** We may need to talk about the content of each work load, use lamp stack as an example.&lt;br /&gt;
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?&lt;br /&gt;
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?&lt;br /&gt;
* LAMP stack workload (created by Tong Li/IBM)&lt;br /&gt;
** https://review.openstack.org/#/c/351879/ &lt;br /&gt;
** Currently developed using terraform to deploy workload, looking into Ansible&lt;br /&gt;
* HEAT template (submitted by Craig Sterrett &amp;amp; Leong/Intel) &lt;br /&gt;
**  https://review.openstack.org/#/c/351799/&lt;br /&gt;
&lt;br /&gt;
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )&lt;br /&gt;
&lt;br /&gt;
=== RefStack Testing and Results Upload ===&lt;br /&gt;
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst&lt;br /&gt;
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once tests are run,  test results can be uploaded to the official  [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.&lt;br /&gt;
*RefStack team highly recommends to upload test results with signatures and not anonymously.  By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Interop Challenge, DefCore team recommends to run complete API tests  (not just the must-pass tests).  Following is the command to run the tests:&lt;br /&gt;
 ./refstack-client test -c &amp;lt;Path of the tempest configuration file to use&amp;gt; -v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For questions, please contact us at IRC channels  #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]&lt;br /&gt;
&lt;br /&gt;
=== Where/How to Share Test Results ===&lt;br /&gt;
Rather than collecting binary &amp;quot;pass/fail&amp;quot; results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not.  Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with &amp;quot;[interop-challenge] Workload Results&amp;quot; in the subject line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 1.) Your name:  &lt;br /&gt;
 2.) Your email: &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization:   &lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested:&lt;br /&gt;
 5.) Version of OpenStack the product uses: &lt;br /&gt;
 6.) Link to RefStack results for this product: &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
&lt;br /&gt;
Here's a fictional example of what the email template might look like when filled out:&lt;br /&gt;
&lt;br /&gt;
 1.) Your name: Jane Doe  &lt;br /&gt;
 2.) Your email: jdoe@supercoolsoftware.com &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization: XYZ, Inc.&lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5&lt;br /&gt;
 5.) Version of OpenStack the product uses: Liberty&lt;br /&gt;
 6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? No&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
     &amp;quot;Error in fetching the floating IP's: no floating IP addresses available&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
 &lt;br /&gt;
     SuperCoolCloud doesn't use floating IP addresses.  Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
     Not very.  Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says &amp;quot;if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead&amp;quot;).&lt;br /&gt;
 &lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
  &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134471</id>
		<title>Interop Challenge</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134471"/>
				<updated>2016-10-07T20:31:33Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* How to Join */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Interop Challenge ==&lt;br /&gt;
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]&lt;br /&gt;
&lt;br /&gt;
=== Duration ===&lt;br /&gt;
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Information ===&lt;br /&gt;
 Schedule: Wednesdays at 1400 UTC&lt;br /&gt;
 IRC Channel (on freenode): &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting-cp&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
 Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/&lt;br /&gt;
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&amp;amp;iso=20161012T14&amp;amp;p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''&lt;br /&gt;
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''&lt;br /&gt;
 '''Agenda'''&lt;br /&gt;
 * see the etherpad &lt;br /&gt;
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]&lt;br /&gt;
&lt;br /&gt;
==== Communication methods====&lt;br /&gt;
* Members will meet regularly using the OpenStack DefCore channel on IRC&lt;br /&gt;
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.&lt;br /&gt;
* The team may also have discussions in Gerrit on specific tools/workloads&lt;br /&gt;
&lt;br /&gt;
=== Milestones ===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Milestone !! Goal !! References !! Status&lt;br /&gt;
|-&lt;br /&gt;
| 1 || ''Create interop challenge and team''  ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Execute tests, resolve/document any issues, and share results ||  || ''In-Progress''&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Create read-out for Interop Challenge || || Pending&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== How to Join ===&lt;br /&gt;
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag &amp;quot;[interop]&amp;quot; in the subject line.  Please identify one business and technical leader from your organization in the introductory email.  Welcome aboard!&lt;br /&gt;
&lt;br /&gt;
Current Participants Alphabetical Order&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner&lt;br /&gt;
|-&lt;br /&gt;
| AT&amp;amp;T ||  ||  ||  || || Elise Eiden |&lt;br /&gt;
|-&lt;br /&gt;
| Canonical || Mitaka and Newton  ||  || || || Mark Baker&lt;br /&gt;
|-&lt;br /&gt;
| Cisco || Liberty ||  || Success || Rohit Agarwalla || Rohit Agarwalla&lt;br /&gt;
|-&lt;br /&gt;
| Fujitsu || Kilo  || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler &lt;br /&gt;
|-&lt;br /&gt;
| Hitachi ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| HPE ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Huawei ||  ||  ||  || || zheng zhen yu||&lt;br /&gt;
|-&lt;br /&gt;
| DT OTC (public cloud) ||  ||  || ||  ||Daniela Ebert ||&lt;br /&gt;
|-&lt;br /&gt;
| IBM || Liberty and Mitaka ||  || Success || Tong Li (IBM) || Tong Li (IBM)&lt;br /&gt;
|-&lt;br /&gt;
| Linaro || Newton on AArch64 ||  ||  || || Gema Gomez ||&lt;br /&gt;
|-&lt;br /&gt;
| Mirantis || Mitaka  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| NetApp ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Osic (Intel+Rackspace) || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares&lt;br /&gt;
|-&lt;br /&gt;
| OVH || Juno/Kilo ||  || Success || Tong Li (IBM) || pilgrimstack&lt;br /&gt;
|-&lt;br /&gt;
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler&lt;br /&gt;
|-&lt;br /&gt;
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado&lt;br /&gt;
|-&lt;br /&gt;
| SUSE || Liberty and Mitaka || Tested with Terraform || Success || contact Roman Arcea (SUSE) || Pete Chadwick - placeholder&lt;br /&gt;
|-&lt;br /&gt;
| VMware || Mitaka || || Success** (**one issue w/rescanning SCSI bus, investigating best fix) || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||&lt;br /&gt;
|-&lt;br /&gt;
| DreamHost ||  ||  ||  || || Stefano Maffuli&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Scripts/Tools used for Interop Challenge ===&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib 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.&lt;br /&gt;
&lt;br /&gt;
The current list of proposed tooling includes:&lt;br /&gt;
* Ansible&lt;br /&gt;
* Terraform&lt;br /&gt;
* OpenStack Heat&lt;br /&gt;
&lt;br /&gt;
The current list of workloads includes:&lt;br /&gt;
* LAMP (Linux, Apache, MySQL, PHP) Stack&lt;br /&gt;
* Dockerswarm-coreos&lt;br /&gt;
* NFV&lt;br /&gt;
&lt;br /&gt;
==== How to Propose/Submit new tools/workloads ====&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository.  Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].&lt;br /&gt;
&lt;br /&gt;
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: &amp;quot;[interop] New tool/workload proposal: &amp;lt;code&amp;gt;brief description&amp;lt;/code&amp;gt;&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
==== Directory Structure ====&lt;br /&gt;
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib&lt;br /&gt;
    Directory structure is proposed below:&lt;br /&gt;
    /heat  - use heat template to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarm-coreo&lt;br /&gt;
        ...&lt;br /&gt;
    /terraform - use terraform to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarme-coreos&lt;br /&gt;
        ...&lt;br /&gt;
    /xxx - use xxx to create workload&lt;br /&gt;
&lt;br /&gt;
=== Test Candidate Process ===&lt;br /&gt;
(Proposed; subject to change after 08-10-2016 meeting)&lt;br /&gt;
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)&lt;br /&gt;
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)&lt;br /&gt;
** We may need to talk about the content of each work load, use lamp stack as an example.&lt;br /&gt;
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?&lt;br /&gt;
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?&lt;br /&gt;
* LAMP stack workload (created by Tong Li/IBM)&lt;br /&gt;
** https://review.openstack.org/#/c/351879/ &lt;br /&gt;
** Currently developed using terraform to deploy workload, looking into Ansible&lt;br /&gt;
* HEAT template (submitted by Craig Sterrett &amp;amp; Leong/Intel) &lt;br /&gt;
**  https://review.openstack.org/#/c/351799/&lt;br /&gt;
&lt;br /&gt;
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )&lt;br /&gt;
&lt;br /&gt;
=== RefStack Testing and Results Upload ===&lt;br /&gt;
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst&lt;br /&gt;
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once tests are run,  test results can be uploaded to the official  [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.&lt;br /&gt;
*RefStack team highly recommends to upload test results with signatures and not anonymously.  By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Interop Challenge, DefCore team recommends to run complete API tests  (not just the must-pass tests).  Following is the command to run the tests:&lt;br /&gt;
 ./refstack-client test -c &amp;lt;Path of the tempest configuration file to use&amp;gt; -v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For questions, please contact us at IRC channels  #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]&lt;br /&gt;
&lt;br /&gt;
=== Where/How to Share Test Results ===&lt;br /&gt;
Rather than collecting binary &amp;quot;pass/fail&amp;quot; results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not.  Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with &amp;quot;[interop-challenge] Workload Results&amp;quot; in the subject line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 1.) Your name:  &lt;br /&gt;
 2.) Your email: &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization:   &lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested:&lt;br /&gt;
 5.) Version of OpenStack the product uses: &lt;br /&gt;
 6.) Link to RefStack results for this product: &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
&lt;br /&gt;
Here's a fictional example of what the email template might look like when filled out:&lt;br /&gt;
&lt;br /&gt;
 1.) Your name: Jane Doe  &lt;br /&gt;
 2.) Your email: jdoe@supercoolsoftware.com &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization: XYZ, Inc.&lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5&lt;br /&gt;
 5.) Version of OpenStack the product uses: Liberty&lt;br /&gt;
 6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? No&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
     &amp;quot;Error in fetching the floating IP's: no floating IP addresses available&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
 &lt;br /&gt;
     SuperCoolCloud doesn't use floating IP addresses.  Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
     Not very.  Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says &amp;quot;if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead&amp;quot;).&lt;br /&gt;
 &lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
  &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134470</id>
		<title>Interop Challenge</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134470"/>
				<updated>2016-10-07T20:30:24Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* How to Join */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Interop Challenge ==&lt;br /&gt;
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]&lt;br /&gt;
&lt;br /&gt;
=== Duration ===&lt;br /&gt;
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Information ===&lt;br /&gt;
 Schedule: Wednesdays at 1400 UTC&lt;br /&gt;
 IRC Channel (on freenode): &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting-cp&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
 Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/&lt;br /&gt;
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&amp;amp;iso=20161012T14&amp;amp;p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''&lt;br /&gt;
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''&lt;br /&gt;
 '''Agenda'''&lt;br /&gt;
 * see the etherpad &lt;br /&gt;
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]&lt;br /&gt;
&lt;br /&gt;
==== Communication methods====&lt;br /&gt;
* Members will meet regularly using the OpenStack DefCore channel on IRC&lt;br /&gt;
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.&lt;br /&gt;
* The team may also have discussions in Gerrit on specific tools/workloads&lt;br /&gt;
&lt;br /&gt;
=== Milestones ===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Milestone !! Goal !! References !! Status&lt;br /&gt;
|-&lt;br /&gt;
| 1 || ''Create interop challenge and team''  ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Execute tests, resolve/document any issues, and share results ||  || ''In-Progress''&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Create read-out for Interop Challenge || || Pending&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== How to Join ===&lt;br /&gt;
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag &amp;quot;[interop]&amp;quot; in the subject line.  Please identify one business and technical leader from your organization in the introductory email.  Welcome aboard!&lt;br /&gt;
&lt;br /&gt;
Current Participants Alphabetical Order&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner&lt;br /&gt;
|-&lt;br /&gt;
| AT&amp;amp;T ||  ||  ||  || Elise Eiden ||&lt;br /&gt;
|-&lt;br /&gt;
| Canonical || Mitaka and Newton  ||  || || || Mark Baker&lt;br /&gt;
|-&lt;br /&gt;
| Cisco || Liberty ||  || Success || Rohit Agarwalla || Rohit Agarwalla&lt;br /&gt;
|-&lt;br /&gt;
| Fujitsu || Kilo  || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler &lt;br /&gt;
|-&lt;br /&gt;
| Hitachi ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| HPE ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Huawei ||  ||  ||  || || zheng zhen yu||&lt;br /&gt;
|-&lt;br /&gt;
| DT OTC (public cloud) ||  ||  || ||  ||Daniela Ebert ||&lt;br /&gt;
|-&lt;br /&gt;
| IBM || Liberty and Mitaka ||  || Success || Tong Li (IBM) || Tong Li (IBM)&lt;br /&gt;
|-&lt;br /&gt;
| Linaro || Newton on AArch64 ||  ||  || || Gema Gomez ||&lt;br /&gt;
|-&lt;br /&gt;
| Mirantis || Mitaka  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| NetApp ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Osic (Intel+Rackspace) || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares&lt;br /&gt;
|-&lt;br /&gt;
| OVH || Juno/Kilo ||  || Success || Tong Li (IBM) || pilgrimstack&lt;br /&gt;
|-&lt;br /&gt;
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler&lt;br /&gt;
|-&lt;br /&gt;
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado&lt;br /&gt;
|-&lt;br /&gt;
| SUSE || Liberty and Mitaka || Tested with Terraform || Success || contact Roman Arcea (SUSE) || Pete Chadwick - placeholder&lt;br /&gt;
|-&lt;br /&gt;
| VMware || Mitaka || || Success** (**one issue w/rescanning SCSI bus, investigating best fix) || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||&lt;br /&gt;
|-&lt;br /&gt;
| DreamHost ||  ||  ||  || || Stefano Maffuli&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Scripts/Tools used for Interop Challenge ===&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib 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.&lt;br /&gt;
&lt;br /&gt;
The current list of proposed tooling includes:&lt;br /&gt;
* Ansible&lt;br /&gt;
* Terraform&lt;br /&gt;
* OpenStack Heat&lt;br /&gt;
&lt;br /&gt;
The current list of workloads includes:&lt;br /&gt;
* LAMP (Linux, Apache, MySQL, PHP) Stack&lt;br /&gt;
* Dockerswarm-coreos&lt;br /&gt;
* NFV&lt;br /&gt;
&lt;br /&gt;
==== How to Propose/Submit new tools/workloads ====&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository.  Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].&lt;br /&gt;
&lt;br /&gt;
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: &amp;quot;[interop] New tool/workload proposal: &amp;lt;code&amp;gt;brief description&amp;lt;/code&amp;gt;&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
==== Directory Structure ====&lt;br /&gt;
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib&lt;br /&gt;
    Directory structure is proposed below:&lt;br /&gt;
    /heat  - use heat template to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarm-coreo&lt;br /&gt;
        ...&lt;br /&gt;
    /terraform - use terraform to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarme-coreos&lt;br /&gt;
        ...&lt;br /&gt;
    /xxx - use xxx to create workload&lt;br /&gt;
&lt;br /&gt;
=== Test Candidate Process ===&lt;br /&gt;
(Proposed; subject to change after 08-10-2016 meeting)&lt;br /&gt;
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)&lt;br /&gt;
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)&lt;br /&gt;
** We may need to talk about the content of each work load, use lamp stack as an example.&lt;br /&gt;
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?&lt;br /&gt;
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?&lt;br /&gt;
* LAMP stack workload (created by Tong Li/IBM)&lt;br /&gt;
** https://review.openstack.org/#/c/351879/ &lt;br /&gt;
** Currently developed using terraform to deploy workload, looking into Ansible&lt;br /&gt;
* HEAT template (submitted by Craig Sterrett &amp;amp; Leong/Intel) &lt;br /&gt;
**  https://review.openstack.org/#/c/351799/&lt;br /&gt;
&lt;br /&gt;
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )&lt;br /&gt;
&lt;br /&gt;
=== RefStack Testing and Results Upload ===&lt;br /&gt;
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst&lt;br /&gt;
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once tests are run,  test results can be uploaded to the official  [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.&lt;br /&gt;
*RefStack team highly recommends to upload test results with signatures and not anonymously.  By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Interop Challenge, DefCore team recommends to run complete API tests  (not just the must-pass tests).  Following is the command to run the tests:&lt;br /&gt;
 ./refstack-client test -c &amp;lt;Path of the tempest configuration file to use&amp;gt; -v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For questions, please contact us at IRC channels  #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]&lt;br /&gt;
&lt;br /&gt;
=== Where/How to Share Test Results ===&lt;br /&gt;
Rather than collecting binary &amp;quot;pass/fail&amp;quot; results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not.  Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with &amp;quot;[interop-challenge] Workload Results&amp;quot; in the subject line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 1.) Your name:  &lt;br /&gt;
 2.) Your email: &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization:   &lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested:&lt;br /&gt;
 5.) Version of OpenStack the product uses: &lt;br /&gt;
 6.) Link to RefStack results for this product: &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
&lt;br /&gt;
Here's a fictional example of what the email template might look like when filled out:&lt;br /&gt;
&lt;br /&gt;
 1.) Your name: Jane Doe  &lt;br /&gt;
 2.) Your email: jdoe@supercoolsoftware.com &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization: XYZ, Inc.&lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5&lt;br /&gt;
 5.) Version of OpenStack the product uses: Liberty&lt;br /&gt;
 6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? No&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
     &amp;quot;Error in fetching the floating IP's: no floating IP addresses available&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
 &lt;br /&gt;
     SuperCoolCloud doesn't use floating IP addresses.  Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
     Not very.  Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says &amp;quot;if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead&amp;quot;).&lt;br /&gt;
 &lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
  &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134469</id>
		<title>Interop Challenge</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134469"/>
				<updated>2016-10-07T18:23:06Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* How to Join */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Interop Challenge ==&lt;br /&gt;
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]&lt;br /&gt;
&lt;br /&gt;
=== Duration ===&lt;br /&gt;
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Information ===&lt;br /&gt;
 Schedule: Wednesdays at 1400 UTC&lt;br /&gt;
 IRC Channel (on freenode): &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting-cp&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
 Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/&lt;br /&gt;
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&amp;amp;iso=20161012T14&amp;amp;p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''&lt;br /&gt;
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''&lt;br /&gt;
 '''Agenda'''&lt;br /&gt;
 * see the etherpad &lt;br /&gt;
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]&lt;br /&gt;
&lt;br /&gt;
==== Communication methods====&lt;br /&gt;
* Members will meet regularly using the OpenStack DefCore channel on IRC&lt;br /&gt;
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.&lt;br /&gt;
* The team may also have discussions in Gerrit on specific tools/workloads&lt;br /&gt;
&lt;br /&gt;
=== Milestones ===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Milestone !! Goal !! References !! Status&lt;br /&gt;
|-&lt;br /&gt;
| 1 || ''Create interop challenge and team''  ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Execute tests, resolve/document any issues, and share results ||  || ''In-Progress''&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Create read-out for Interop Challenge || || Pending&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== How to Join ===&lt;br /&gt;
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag &amp;quot;[interop]&amp;quot; in the subject line.  Please identify one business and technical leader from your organization in the introductory email.  Welcome aboard!&lt;br /&gt;
&lt;br /&gt;
Current Participants Alphabetical Order&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner&lt;br /&gt;
|-&lt;br /&gt;
| AT&amp;amp;T ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Canonical || Mitaka and Newton  ||  || || ||&lt;br /&gt;
|-&lt;br /&gt;
| Cisco || Liberty ||  || Success || Rohit Agarwalla || Rohit Agarwalla&lt;br /&gt;
|-&lt;br /&gt;
| Fujitsu || Kilo  || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler &lt;br /&gt;
|-&lt;br /&gt;
| Hitachi ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| HPE ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Huawei ||  ||  ||  || || zheng zhen yu||&lt;br /&gt;
|-&lt;br /&gt;
| DT OTC (public cloud) ||  ||  || ||  ||Daniela Ebert ||&lt;br /&gt;
|-&lt;br /&gt;
| IBM || Liberty and Mitaka ||  || Success || Tong Li (IBM) || Tong Li (IBM)&lt;br /&gt;
|-&lt;br /&gt;
| Linaro || Newton on AArch64 ||  ||  || || Gema Gomez ||&lt;br /&gt;
|-&lt;br /&gt;
| Mirantis || Mitaka  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| NetApp ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Osic (Intel+Rackspace) || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares&lt;br /&gt;
|-&lt;br /&gt;
| OVH || Juno/Kilo ||  || Success || Tong Li (IBM) ||&lt;br /&gt;
|-&lt;br /&gt;
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler&lt;br /&gt;
|-&lt;br /&gt;
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado&lt;br /&gt;
|-&lt;br /&gt;
| SUSE || Liberty and Mitaka || Tested with Terraform || Success || contact Roman Arcea (SUSE) ||&lt;br /&gt;
|-&lt;br /&gt;
| VMware || Mitaka || || Success** (**one issue w/rescanning SCSI bus, investigating best fix) || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||&lt;br /&gt;
|-&lt;br /&gt;
| DreamHost ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Scripts/Tools used for Interop Challenge ===&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib 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.&lt;br /&gt;
&lt;br /&gt;
The current list of proposed tooling includes:&lt;br /&gt;
* Ansible&lt;br /&gt;
* Terraform&lt;br /&gt;
* OpenStack Heat&lt;br /&gt;
&lt;br /&gt;
The current list of workloads includes:&lt;br /&gt;
* LAMP (Linux, Apache, MySQL, PHP) Stack&lt;br /&gt;
* Dockerswarm-coreos&lt;br /&gt;
* NFV&lt;br /&gt;
&lt;br /&gt;
==== How to Propose/Submit new tools/workloads ====&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository.  Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].&lt;br /&gt;
&lt;br /&gt;
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: &amp;quot;[interop] New tool/workload proposal: &amp;lt;code&amp;gt;brief description&amp;lt;/code&amp;gt;&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
==== Directory Structure ====&lt;br /&gt;
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib&lt;br /&gt;
    Directory structure is proposed below:&lt;br /&gt;
    /heat  - use heat template to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarm-coreo&lt;br /&gt;
        ...&lt;br /&gt;
    /terraform - use terraform to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarme-coreos&lt;br /&gt;
        ...&lt;br /&gt;
    /xxx - use xxx to create workload&lt;br /&gt;
&lt;br /&gt;
=== Test Candidate Process ===&lt;br /&gt;
(Proposed; subject to change after 08-10-2016 meeting)&lt;br /&gt;
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)&lt;br /&gt;
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)&lt;br /&gt;
** We may need to talk about the content of each work load, use lamp stack as an example.&lt;br /&gt;
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?&lt;br /&gt;
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?&lt;br /&gt;
* LAMP stack workload (created by Tong Li/IBM)&lt;br /&gt;
** https://review.openstack.org/#/c/351879/ &lt;br /&gt;
** Currently developed using terraform to deploy workload, looking into Ansible&lt;br /&gt;
* HEAT template (submitted by Craig Sterrett &amp;amp; Leong/Intel) &lt;br /&gt;
**  https://review.openstack.org/#/c/351799/&lt;br /&gt;
&lt;br /&gt;
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )&lt;br /&gt;
&lt;br /&gt;
=== RefStack Testing and Results Upload ===&lt;br /&gt;
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst&lt;br /&gt;
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once tests are run,  test results can be uploaded to the official  [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.&lt;br /&gt;
*RefStack team highly recommends to upload test results with signatures and not anonymously.  By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Interop Challenge, DefCore team recommends to run complete API tests  (not just the must-pass tests).  Following is the command to run the tests:&lt;br /&gt;
 ./refstack-client test -c &amp;lt;Path of the tempest configuration file to use&amp;gt; -v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For questions, please contact us at IRC channels  #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]&lt;br /&gt;
&lt;br /&gt;
=== Where/How to Share Test Results ===&lt;br /&gt;
Rather than collecting binary &amp;quot;pass/fail&amp;quot; results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not.  Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with &amp;quot;[interop-challenge] Workload Results&amp;quot; in the subject line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 1.) Your name:  &lt;br /&gt;
 2.) Your email: &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization:   &lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested:&lt;br /&gt;
 5.) Version of OpenStack the product uses: &lt;br /&gt;
 6.) Link to RefStack results for this product: &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
&lt;br /&gt;
Here's a fictional example of what the email template might look like when filled out:&lt;br /&gt;
&lt;br /&gt;
 1.) Your name: Jane Doe  &lt;br /&gt;
 2.) Your email: jdoe@supercoolsoftware.com &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization: XYZ, Inc.&lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5&lt;br /&gt;
 5.) Version of OpenStack the product uses: Liberty&lt;br /&gt;
 6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? No&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
     &amp;quot;Error in fetching the floating IP's: no floating IP addresses available&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
 &lt;br /&gt;
     SuperCoolCloud doesn't use floating IP addresses.  Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
     Not very.  Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says &amp;quot;if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead&amp;quot;).&lt;br /&gt;
 &lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
  &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134468</id>
		<title>Interop Challenge</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134468"/>
				<updated>2016-10-07T18:14:57Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* How to Join */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Interop Challenge ==&lt;br /&gt;
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]&lt;br /&gt;
&lt;br /&gt;
=== Duration ===&lt;br /&gt;
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Information ===&lt;br /&gt;
 Schedule: Wednesdays at 1400 UTC&lt;br /&gt;
 IRC Channel (on freenode): &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting-cp&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
 Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/&lt;br /&gt;
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&amp;amp;iso=20161012T14&amp;amp;p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''&lt;br /&gt;
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''&lt;br /&gt;
 '''Agenda'''&lt;br /&gt;
 * see the etherpad &lt;br /&gt;
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]&lt;br /&gt;
&lt;br /&gt;
==== Communication methods====&lt;br /&gt;
* Members will meet regularly using the OpenStack DefCore channel on IRC&lt;br /&gt;
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.&lt;br /&gt;
* The team may also have discussions in Gerrit on specific tools/workloads&lt;br /&gt;
&lt;br /&gt;
=== Milestones ===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Milestone !! Goal !! References !! Status&lt;br /&gt;
|-&lt;br /&gt;
| 1 || ''Create interop challenge and team''  ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Execute tests, resolve/document any issues, and share results ||  || ''In-Progress''&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Create read-out for Interop Challenge || || Pending&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== How to Join ===&lt;br /&gt;
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag &amp;quot;[interop]&amp;quot; in the subject line.  Please identify one business and technical leader from your organization in the introductory email.  Welcome aboard!&lt;br /&gt;
&lt;br /&gt;
Current Participants Alphabetical Order&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner&lt;br /&gt;
|-&lt;br /&gt;
| AT&amp;amp;T ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Canonical || Mitaka and Newton  ||  || || ||&lt;br /&gt;
|-&lt;br /&gt;
| Cisco || Liberty ||  || Success || Rohit Agarwalla || Rohit Agarwalla&lt;br /&gt;
|-&lt;br /&gt;
| Fujitsu || Kilo  || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler &lt;br /&gt;
|-&lt;br /&gt;
| Hitachi ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| HPE ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Huawei ||  ||  ||  || || zheng zhen yu||&lt;br /&gt;
|-&lt;br /&gt;
| DT OTC (public cloud) ||  ||  || ||  ||Daniela Ebert ||&lt;br /&gt;
|-&lt;br /&gt;
| IBM || Liberty and Mitaka ||  || Success || Tong Li (IBM) || Tong Li (IBM)&lt;br /&gt;
|-&lt;br /&gt;
| Linaro || Newton on AArch64 ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Mirantis || Mitaka  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| NetApp ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Osic (Intel+Rackspace) || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares&lt;br /&gt;
|-&lt;br /&gt;
| OVH || Juno/Kilo ||  || Success || Tong Li (IBM) ||&lt;br /&gt;
|-&lt;br /&gt;
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler&lt;br /&gt;
|-&lt;br /&gt;
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado&lt;br /&gt;
|-&lt;br /&gt;
| SUSE || Liberty and Mitaka || Tested with Terraform || Success || contact Roman Arcea (SUSE) ||&lt;br /&gt;
|-&lt;br /&gt;
| VMware || Mitaka || || Success** (**one issue w/rescanning SCSI bus, investigating best fix) || Xiangfei Zhu/Mark Voelker ||Mark Voelker ||&lt;br /&gt;
|-&lt;br /&gt;
| DreamHost ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Scripts/Tools used for Interop Challenge ===&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib 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.&lt;br /&gt;
&lt;br /&gt;
The current list of proposed tooling includes:&lt;br /&gt;
* Ansible&lt;br /&gt;
* Terraform&lt;br /&gt;
* OpenStack Heat&lt;br /&gt;
&lt;br /&gt;
The current list of workloads includes:&lt;br /&gt;
* LAMP (Linux, Apache, MySQL, PHP) Stack&lt;br /&gt;
* Dockerswarm-coreos&lt;br /&gt;
* NFV&lt;br /&gt;
&lt;br /&gt;
==== How to Propose/Submit new tools/workloads ====&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository.  Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].&lt;br /&gt;
&lt;br /&gt;
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: &amp;quot;[interop] New tool/workload proposal: &amp;lt;code&amp;gt;brief description&amp;lt;/code&amp;gt;&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
==== Directory Structure ====&lt;br /&gt;
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib&lt;br /&gt;
    Directory structure is proposed below:&lt;br /&gt;
    /heat  - use heat template to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarm-coreo&lt;br /&gt;
        ...&lt;br /&gt;
    /terraform - use terraform to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarme-coreos&lt;br /&gt;
        ...&lt;br /&gt;
    /xxx - use xxx to create workload&lt;br /&gt;
&lt;br /&gt;
=== Test Candidate Process ===&lt;br /&gt;
(Proposed; subject to change after 08-10-2016 meeting)&lt;br /&gt;
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)&lt;br /&gt;
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)&lt;br /&gt;
** We may need to talk about the content of each work load, use lamp stack as an example.&lt;br /&gt;
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?&lt;br /&gt;
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?&lt;br /&gt;
* LAMP stack workload (created by Tong Li/IBM)&lt;br /&gt;
** https://review.openstack.org/#/c/351879/ &lt;br /&gt;
** Currently developed using terraform to deploy workload, looking into Ansible&lt;br /&gt;
* HEAT template (submitted by Craig Sterrett &amp;amp; Leong/Intel) &lt;br /&gt;
**  https://review.openstack.org/#/c/351799/&lt;br /&gt;
&lt;br /&gt;
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )&lt;br /&gt;
&lt;br /&gt;
=== RefStack Testing and Results Upload ===&lt;br /&gt;
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst&lt;br /&gt;
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once tests are run,  test results can be uploaded to the official  [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.&lt;br /&gt;
*RefStack team highly recommends to upload test results with signatures and not anonymously.  By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Interop Challenge, DefCore team recommends to run complete API tests  (not just the must-pass tests).  Following is the command to run the tests:&lt;br /&gt;
 ./refstack-client test -c &amp;lt;Path of the tempest configuration file to use&amp;gt; -v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For questions, please contact us at IRC channels  #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]&lt;br /&gt;
&lt;br /&gt;
=== Where/How to Share Test Results ===&lt;br /&gt;
Rather than collecting binary &amp;quot;pass/fail&amp;quot; results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not.  Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with &amp;quot;[interop-challenge] Workload Results&amp;quot; in the subject line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 1.) Your name:  &lt;br /&gt;
 2.) Your email: &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization:   &lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested:&lt;br /&gt;
 5.) Version of OpenStack the product uses: &lt;br /&gt;
 6.) Link to RefStack results for this product: &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
&lt;br /&gt;
Here's a fictional example of what the email template might look like when filled out:&lt;br /&gt;
&lt;br /&gt;
 1.) Your name: Jane Doe  &lt;br /&gt;
 2.) Your email: jdoe@supercoolsoftware.com &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization: XYZ, Inc.&lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5&lt;br /&gt;
 5.) Version of OpenStack the product uses: Liberty&lt;br /&gt;
 6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? No&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
     &amp;quot;Error in fetching the floating IP's: no floating IP addresses available&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
 &lt;br /&gt;
     SuperCoolCloud doesn't use floating IP addresses.  Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
     Not very.  Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says &amp;quot;if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead&amp;quot;).&lt;br /&gt;
 &lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
  &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134465</id>
		<title>Interop Challenge</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134465"/>
				<updated>2016-10-07T17:24:45Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* How to Join */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Interop Challenge ==&lt;br /&gt;
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]&lt;br /&gt;
&lt;br /&gt;
=== Duration ===&lt;br /&gt;
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Information ===&lt;br /&gt;
 Schedule: Wednesdays at 1400 UTC&lt;br /&gt;
 IRC Channel (on freenode): &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting-cp&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
 Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/&lt;br /&gt;
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&amp;amp;iso=20161012T14&amp;amp;p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''&lt;br /&gt;
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''&lt;br /&gt;
 '''Agenda'''&lt;br /&gt;
 * see the etherpad &lt;br /&gt;
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]&lt;br /&gt;
&lt;br /&gt;
==== Communication methods====&lt;br /&gt;
* Members will meet regularly using the OpenStack DefCore channel on IRC&lt;br /&gt;
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.&lt;br /&gt;
* The team may also have discussions in Gerrit on specific tools/workloads&lt;br /&gt;
&lt;br /&gt;
=== Milestones ===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Milestone !! Goal !! References !! Status&lt;br /&gt;
|-&lt;br /&gt;
| 1 || ''Create interop challenge and team''  ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Execute tests, resolve/document any issues, and share results ||  || ''In-Progress''&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Create read-out for Interop Challenge || || Pending&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== How to Join ===&lt;br /&gt;
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag &amp;quot;[interop]&amp;quot; in the subject line.  Please identify one business and technical leader from your organization in the introductory email.  Welcome aboard!&lt;br /&gt;
&lt;br /&gt;
Current Participants Alphabetical Order&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner&lt;br /&gt;
|-&lt;br /&gt;
| AT&amp;amp;T ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Canonical || Mitaka and Newton  ||  || || ||&lt;br /&gt;
|-&lt;br /&gt;
| Cisco || Liberty ||  || Success || Rohit Agarwalla || &lt;br /&gt;
|-&lt;br /&gt;
| Fujitsu || Kilo  || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler &lt;br /&gt;
|-&lt;br /&gt;
| Hitachi ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| HPE ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Huawei ||  ||  ||  || || zheng zhen yu||&lt;br /&gt;
|-&lt;br /&gt;
| DT OTC (public cloud) ||  ||  || ||  ||Daniela Ebert ||&lt;br /&gt;
|-&lt;br /&gt;
| IBM || Liberty and Mitaka ||  || Success || Tong Li (IBM) ||&lt;br /&gt;
|-&lt;br /&gt;
| Linaro || Newton on AArch64 ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Mirantis || Mitaka  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| NetApp ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Osic (Intel+Rackspace) || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares&lt;br /&gt;
|-&lt;br /&gt;
| OVH || Juno/Kilo ||  || Success || Tong Li (IBM) ||&lt;br /&gt;
|-&lt;br /&gt;
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler&lt;br /&gt;
|-&lt;br /&gt;
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado&lt;br /&gt;
|-&lt;br /&gt;
| SUSE || Liberty and Mitaka || Tested with Terraform || Success || contact Roman Arcea (SUSE) ||&lt;br /&gt;
|-&lt;br /&gt;
| VMware || Mitaka || || Success** (**one issue w/rescanning SCSI bus, investigating best fix) || Xiangfei Zhu/Mark Voelker ||&lt;br /&gt;
|-&lt;br /&gt;
| DreamHost ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Scripts/Tools used for Interop Challenge ===&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib 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.&lt;br /&gt;
&lt;br /&gt;
The current list of proposed tooling includes:&lt;br /&gt;
* Ansible&lt;br /&gt;
* Terraform&lt;br /&gt;
* OpenStack Heat&lt;br /&gt;
&lt;br /&gt;
The current list of workloads includes:&lt;br /&gt;
* LAMP (Linux, Apache, MySQL, PHP) Stack&lt;br /&gt;
* Dockerswarm-coreos&lt;br /&gt;
* NFV&lt;br /&gt;
&lt;br /&gt;
==== How to Propose/Submit new tools/workloads ====&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository.  Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].&lt;br /&gt;
&lt;br /&gt;
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: &amp;quot;[interop] New tool/workload proposal: &amp;lt;code&amp;gt;brief description&amp;lt;/code&amp;gt;&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
==== Directory Structure ====&lt;br /&gt;
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib&lt;br /&gt;
    Directory structure is proposed below:&lt;br /&gt;
    /heat  - use heat template to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarm-coreo&lt;br /&gt;
        ...&lt;br /&gt;
    /terraform - use terraform to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarme-coreos&lt;br /&gt;
        ...&lt;br /&gt;
    /xxx - use xxx to create workload&lt;br /&gt;
&lt;br /&gt;
=== Test Candidate Process ===&lt;br /&gt;
(Proposed; subject to change after 08-10-2016 meeting)&lt;br /&gt;
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)&lt;br /&gt;
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)&lt;br /&gt;
** We may need to talk about the content of each work load, use lamp stack as an example.&lt;br /&gt;
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?&lt;br /&gt;
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?&lt;br /&gt;
* LAMP stack workload (created by Tong Li/IBM)&lt;br /&gt;
** https://review.openstack.org/#/c/351879/ &lt;br /&gt;
** Currently developed using terraform to deploy workload, looking into Ansible&lt;br /&gt;
* HEAT template (submitted by Craig Sterrett &amp;amp; Leong/Intel) &lt;br /&gt;
**  https://review.openstack.org/#/c/351799/&lt;br /&gt;
&lt;br /&gt;
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )&lt;br /&gt;
&lt;br /&gt;
=== RefStack Testing and Results Upload ===&lt;br /&gt;
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst&lt;br /&gt;
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once tests are run,  test results can be uploaded to the official  [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.&lt;br /&gt;
*RefStack team highly recommends to upload test results with signatures and not anonymously.  By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Interop Challenge, DefCore team recommends to run complete API tests  (not just the must-pass tests).  Following is the command to run the tests:&lt;br /&gt;
 ./refstack-client test -c &amp;lt;Path of the tempest configuration file to use&amp;gt; -v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For questions, please contact us at IRC channels  #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]&lt;br /&gt;
&lt;br /&gt;
=== Where/How to Share Test Results ===&lt;br /&gt;
Rather than collecting binary &amp;quot;pass/fail&amp;quot; results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not.  Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with &amp;quot;[interop-challenge] Workload Results&amp;quot; in the subject line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 1.) Your name:  &lt;br /&gt;
 2.) Your email: &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization:   &lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested:&lt;br /&gt;
 5.) Version of OpenStack the product uses: &lt;br /&gt;
 6.) Link to RefStack results for this product: &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
&lt;br /&gt;
Here's a fictional example of what the email template might look like when filled out:&lt;br /&gt;
&lt;br /&gt;
 1.) Your name: Jane Doe  &lt;br /&gt;
 2.) Your email: jdoe@supercoolsoftware.com &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization: XYZ, Inc.&lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5&lt;br /&gt;
 5.) Version of OpenStack the product uses: Liberty&lt;br /&gt;
 6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? No&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
     &amp;quot;Error in fetching the floating IP's: no floating IP addresses available&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
 &lt;br /&gt;
     SuperCoolCloud doesn't use floating IP addresses.  Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
     Not very.  Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says &amp;quot;if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead&amp;quot;).&lt;br /&gt;
 &lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
  &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134464</id>
		<title>Interop Challenge</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Interop_Challenge&amp;diff=134464"/>
				<updated>2016-10-07T17:23:12Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* How to Join */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Interop Challenge ==&lt;br /&gt;
''Status: Collecting workload scripts, milestone-1 (as of Aug 8, 2016)''&lt;br /&gt;
&lt;br /&gt;
=== Scope ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Original presentation used during team creation: [https://drive.google.com/open?id=0B_yCSDGnhIbzZmtOUXlmZGhPR0U Interoperability Challenge Kick-Off]&lt;br /&gt;
&lt;br /&gt;
=== Duration ===&lt;br /&gt;
The team will complete the Interop Challenge prior to the [https://www.openstack.org/summit/barcelona-2016/ next summit] working together with partners in the OpenStack Foundation.&lt;br /&gt;
&lt;br /&gt;
=== Meeting Information ===&lt;br /&gt;
 Schedule: Wednesdays at 1400 UTC&lt;br /&gt;
 IRC Channel (on freenode): &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting-cp&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
 Logs from past meeting: http://eavesdrop.openstack.org/meetings/interop_challenge/&lt;br /&gt;
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Interop+Challenge+Team+Meeting&amp;amp;iso=20161012T14&amp;amp;p1=%3A Wednesday, October 12th, 2016 at 1400 UTC]'''&lt;br /&gt;
'''Etherpad For Next Meeting: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-10-12 2016-10-12]'''&lt;br /&gt;
 '''Agenda'''&lt;br /&gt;
 * see the etherpad &lt;br /&gt;
Previous Etherpads: [https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-28 2016-10-05]&lt;br /&gt;
&lt;br /&gt;
==== Communication methods====&lt;br /&gt;
* Members will meet regularly using the OpenStack DefCore channel on IRC&lt;br /&gt;
* The team will communicate on the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and add the [interop] tag to the subject of messages related to the interop challenge.&lt;br /&gt;
* The team may also have discussions in Gerrit on specific tools/workloads&lt;br /&gt;
&lt;br /&gt;
=== Milestones ===&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Milestone !! Goal !! References !! Status&lt;br /&gt;
|-&lt;br /&gt;
| 1 || ''Create interop challenge and team''  ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 2 || ''Identify tools/scripts that will be used to validate interoperability'' ||  || ''Completed''&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Execute tests, resolve/document any issues, and share results ||  || ''In-Progress''&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Create read-out for Interop Challenge || || Pending&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Share findings at the OpenStack Summit in Barcelona || || Pending&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== How to Join ===&lt;br /&gt;
If you are interested in joining the interop, please join the the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list] and send a message with the tag &amp;quot;[interop]&amp;quot; in the subject line.  Please identify one business and technical leader from your organization in the introductory email.  Welcome aboard!&lt;br /&gt;
&lt;br /&gt;
Current Participants Alphabetical Order&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Participant !! OpenStack version !! References !! Status || Tested by || Keynote 2 Demo Owner&lt;br /&gt;
|-&lt;br /&gt;
| AT&amp;amp;T ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Canonical || Mitaka and Newton  ||  || || ||&lt;br /&gt;
|-&lt;br /&gt;
| Cisco || Liberty ||  || Success || Rohit Agarwalla || &lt;br /&gt;
|-&lt;br /&gt;
| Fujitsu || Kilo  || Tested with Ansible || Success || Dror Gensler, Daisuke Butsuda || Dror Gensler &lt;br /&gt;
|-&lt;br /&gt;
| Hitachi ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| HPE ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Huawei ||  ||  || || zheng zhen yu||&lt;br /&gt;
|-&lt;br /&gt;
| DT OTC (public cloud) ||  ||  || ||Daniela Ebert ||&lt;br /&gt;
|-&lt;br /&gt;
| IBM || Liberty and Mitaka ||  || Success || Tong Li (IBM) ||&lt;br /&gt;
|-&lt;br /&gt;
| Linaro || Newton on AArch64 ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Mirantis || Mitaka  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| NetApp ||   ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
| Osic (Intel+Rackspace) || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Luz Cazares&lt;br /&gt;
|-&lt;br /&gt;
| OVH || Juno/Kilo ||  || Success || Tong Li (IBM) ||&lt;br /&gt;
|-&lt;br /&gt;
| Rackspace || Liberty || RefStack Pass. Tested with Ansible || Success || Tong LI (IBM), Luz Cazares (Intel) || Egle Sigler&lt;br /&gt;
|-&lt;br /&gt;
| Red Hat || Mitaka || RefStack Pass - Tested with Ansible || Success || Victoria Martinez de la Cruz (Red Hat), Daniel Mellado (Red Hat) || Daniel Mellado&lt;br /&gt;
|-&lt;br /&gt;
| SUSE || Liberty and Mitaka || Tested with Terraform || Success || contact Roman Arcea (SUSE) ||&lt;br /&gt;
|-&lt;br /&gt;
| VMware || Mitaka || || Success** (**one issue w/rescanning SCSI bus, investigating best fix) || Xiangfei Zhu/Mark Voelker ||&lt;br /&gt;
|-&lt;br /&gt;
| DreamHost ||  ||  ||  || ||&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Scripts/Tools used for Interop Challenge ===&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib 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.&lt;br /&gt;
&lt;br /&gt;
The current list of proposed tooling includes:&lt;br /&gt;
* Ansible&lt;br /&gt;
* Terraform&lt;br /&gt;
* OpenStack Heat&lt;br /&gt;
&lt;br /&gt;
The current list of workloads includes:&lt;br /&gt;
* LAMP (Linux, Apache, MySQL, PHP) Stack&lt;br /&gt;
* Dockerswarm-coreos&lt;br /&gt;
* NFV&lt;br /&gt;
&lt;br /&gt;
==== How to Propose/Submit new tools/workloads ====&lt;br /&gt;
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 [https://github.com/openstack/osops-tools-contrib osops-tools-contrib] repository.  Information on how to contribute to OpenStack repositories can be found in the OpenStack [http://docs.openstack.org/infra/manual/developers.html Developer's Guide].&lt;br /&gt;
&lt;br /&gt;
Once you have posted the code for review, please send an email to the OpenStack DefCore mailing list with the following subject: &amp;quot;[interop] New tool/workload proposal: &amp;lt;code&amp;gt;brief description&amp;lt;/code&amp;gt;&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
==== Directory Structure ====&lt;br /&gt;
Repo used by the Interop-challenge: https://github.com/openstack/osops-tools-contrib&lt;br /&gt;
    Directory structure is proposed below:&lt;br /&gt;
    /heat  - use heat template to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarm-coreo&lt;br /&gt;
        ...&lt;br /&gt;
    /terraform - use terraform to create workload&lt;br /&gt;
        lampstack&lt;br /&gt;
        dockerswarme-coreos&lt;br /&gt;
        ...&lt;br /&gt;
    /xxx - use xxx to create workload&lt;br /&gt;
&lt;br /&gt;
=== Test Candidate Process ===&lt;br /&gt;
(Proposed; subject to change after 08-10-2016 meeting)&lt;br /&gt;
* Run complete RefStack API tests and submit results to https://refstack.openstack.org/#/ (SME: Catherine Diep/IBM)&lt;br /&gt;
* Terraform/docker swarm https://github.com/openstack/osops-tools-contrib/tree/master/terraform/dockerswarm-coreos (SME: Jason Kennedy/IBM)&lt;br /&gt;
** We may need to talk about the content of each work load, use lamp stack as an example.&lt;br /&gt;
** How substantial should the application be, if doing wordpress, do we also creates some posts, pages?&lt;br /&gt;
** Do we need the lamp stack being deployed by terraform, heat template, ansible or we just need one say ansible?&lt;br /&gt;
* LAMP stack workload (created by Tong Li/IBM)&lt;br /&gt;
** https://review.openstack.org/#/c/351879/ &lt;br /&gt;
** Currently developed using terraform to deploy workload, looking into Ansible&lt;br /&gt;
* HEAT template (submitted by Craig Sterrett &amp;amp; Leong/Intel) &lt;br /&gt;
**  https://review.openstack.org/#/c/351799/&lt;br /&gt;
&lt;br /&gt;
For test assistance or if you would like Tong Li to run the tests on your clouds, please contact Tong Li (IRC: tongli, email: litong01@us.ibm.com )&lt;br /&gt;
&lt;br /&gt;
=== RefStack Testing and Results Upload ===&lt;br /&gt;
Information on how to run RefStack tests can be found at:https://github.com/openstack/refstack-client/blob/master/README.rst&lt;br /&gt;
*Slide 15, 16, 17 in this RefStack Austin Summit [https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.p presentation] provides some information about customizing a tempest.conf file for RefStack testing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Once tests are run,  test results can be uploaded to the official  [https://refstack.openstack.org/#/ RefStack server] by following the instruction described in https://github.com/openstack/refstack/blob/master/doc/source/uploading_private_results.rst.&lt;br /&gt;
*RefStack team highly recommends to upload test results with signatures and not anonymously.  By default, the privately uploaded data isn't shared, but authorized users can decide to share the results with the community anonymously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For Interop Challenge, DefCore team recommends to run complete API tests  (not just the must-pass tests).  Following is the command to run the tests:&lt;br /&gt;
 ./refstack-client test -c &amp;lt;Path of the tempest configuration file to use&amp;gt; -v&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For questions, please contact us at IRC channels  #refstack or #openstack-defcore, or send email to the OpenStack [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee DefCore mailing list]&lt;br /&gt;
&lt;br /&gt;
=== Where/How to Share Test Results ===&lt;br /&gt;
Rather than collecting binary &amp;quot;pass/fail&amp;quot; results, one of our goals for the challenge is to start gathering some information about what makes a workload portable or not.  Once you've run each of the workloads above, we ask that you copy/paste the following template into an email and send it to defcore-committee@lists.openstack.org with &amp;quot;[interop-challenge] Workload Results&amp;quot; in the subject line.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 1.) Your name:  &lt;br /&gt;
 2.) Your email: &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization:   &lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested:&lt;br /&gt;
 5.) Version of OpenStack the product uses: &lt;br /&gt;
 6.) Link to RefStack results for this product: &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully? &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  &lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
&lt;br /&gt;
Here's a fictional example of what the email template might look like when filled out:&lt;br /&gt;
&lt;br /&gt;
 1.) Your name: Jane Doe  &lt;br /&gt;
 2.) Your email: jdoe@supercoolsoftware.com &lt;br /&gt;
 3.) Reporting on behalf of Company/Organization: XYZ, Inc.&lt;br /&gt;
 4.) Name and version (if applicable) of the product you tested: SuperCool Private Cloud 4.5&lt;br /&gt;
 5.) Version of OpenStack the product uses: Liberty&lt;br /&gt;
 6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/fc80592b-4503-481c-8aa6-49d414961f2d &lt;br /&gt;
 7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)&lt;br /&gt;
   A.) Did the workload run successfully? No&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
     &amp;quot;Error in fetching the floating IP's: no floating IP addresses available&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
 &lt;br /&gt;
     SuperCoolCloud doesn't use floating IP addresses.  Instead, we recommend that cloud admins create a shared provider network with external routing connectivity.&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
     Not very.  Basically we just need to add a config variable that allows the user to specify whether the cloud uses floating IP's (and a small if loop in a few places that says &amp;quot;if we're configured to not use floating IP's, assume it's ok to use the instance's fixed IP instead&amp;quot;).&lt;br /&gt;
 &lt;br /&gt;
 8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc. &lt;br /&gt;
  &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
 9.) Workload 3: NFV (URL TBD)&lt;br /&gt;
   A.) Did the workload run successfully?  Yes&lt;br /&gt;
   B.) If not, did you encounter any end-user visible error messages?  Please copy/paste them here and provide any context you think would help us understand what happened. &lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   C.) Were you able to determine why the workload failed on this product?  If so, please describe.  Examples: the product is missing a feature that the workload assumes is available, the product limits an action by policy that the workload requires, the workload assumes a particular image type or processor architecture, etc.&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;br /&gt;
 &lt;br /&gt;
   D.) (optional) In your estimation, how hard would it be to modify this workload to get it running on this product?  Can you describe what would need to be done?&lt;br /&gt;
 &lt;br /&gt;
   N/A&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99373</id>
		<title>Sprints/KeystoneMitakaSprint</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99373"/>
				<updated>2015-12-10T16:36:52Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Registration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Keystone Mitaka Midcycle Meetup ==&lt;br /&gt;
This page tracks information for the Keystone Liberty Code Sprint.&lt;br /&gt;
&lt;br /&gt;
=== Time and Location ===&lt;br /&gt;
When: January 27-29 (Wed-Fri) 9:00 AM to 5:pm&lt;br /&gt;
&lt;br /&gt;
Where: IBM Austin - Building 904, Executive Briefing Centre&lt;br /&gt;
11501 Burnet Rd, Austin, TX 78758, USA&lt;br /&gt;
&lt;br /&gt;
=== Other Information ===&lt;br /&gt;
Current Attendance Cap: 25&lt;br /&gt;
&lt;br /&gt;
[https://etherpad.openstack.org/p/keystone-mitaka-midcycle-meetup Etherpad] for Keystone MidCycle Meetup/Sprint Topics and Information&lt;br /&gt;
&lt;br /&gt;
=== Registration ===&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Twitter handle is optional, but often we use twitter to let people know where we are, especially for evening food and/or drinks. Feel free to provide your twitter or just keep an eye out on those of us who have provided ours for where everyone is at the Meetup/when we're headed out for dinner, etc.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Lunches are likely to be provided, please mention any special dietary restrictions in the comments section of the table.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! # !! Name !! IRC Nick !! Twitter (optional) !! Comment !! Email&lt;br /&gt;
|-&lt;br /&gt;
| 1 || Steve Martinelli || stevemar || [https://twitter.com/stevebot @stevebot] || || stevemar AT ca DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 2 || Lance Bragstad || lbragstad || [https://twitter.com/LanceBragstad @LanceBragstad] ||  || lbragstad AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Joe Savak || jsavak || [https://twitter.com/joesavak @JoeSavak] ||  || jsavak AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Fernando Diaz || diazjf || ||  || diazjf AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Dolph Mathews || dolphm || [https://twitter.com/dolphm @dolphm] || No comment. || dolph DOT mathews AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 6 || David Stanek || dstanek || [https://twitter.com/dstanek @dstanek] || I like trees || dstanek AT dstanek DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 7 || Samuel de Medeiros Queiroz || samueldmq || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || samueldmq AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 8 || Brad Topol || topol || [https://twitter.com/bradtopol @bradtopol]|| Hoping to get fantastic BBQ, recommendations?|| btopol AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 9 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 10 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 11 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 13 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 15 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 17 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 18 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 19 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 20 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 21 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 22 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 23 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 24 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 25 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| || No || more || spaces || available! || (sorry!)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hotel List ===&lt;br /&gt;
&lt;br /&gt;
====  Home2 Suites by Hilton Austin North/Near The Domain ====&lt;br /&gt;
* 2800 Esperanza Crossing, Austin, TX 78758, United States&lt;br /&gt;
* 1-512-339-2400&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 0.3 mi to IBM, very walkable&lt;br /&gt;
&lt;br /&gt;
==== Hyatt Place Austin/Arboretum ====&lt;br /&gt;
* 3612 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* +1 512-231-8491&lt;br /&gt;
* ~$140/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Residence Inn Austin Northwest/Arboretum ====&lt;br /&gt;
* 3713 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8200&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Courtyard Austin Northwest/Arboretum ====&lt;br /&gt;
* 9409 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8100&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
====  Embassy Suites by Hilton Austin Arboretum ====&lt;br /&gt;
* 9505 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-372-8771&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99372</id>
		<title>Sprints/KeystoneMitakaSprint</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99372"/>
				<updated>2015-12-10T16:36:09Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Registration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Keystone Mitaka Midcycle Meetup ==&lt;br /&gt;
This page tracks information for the Keystone Liberty Code Sprint.&lt;br /&gt;
&lt;br /&gt;
=== Time and Location ===&lt;br /&gt;
When: January 27-29 (Wed-Fri) 9:00 AM to 5:pm&lt;br /&gt;
&lt;br /&gt;
Where: IBM Austin - Building 904, Executive Briefing Centre&lt;br /&gt;
11501 Burnet Rd, Austin, TX 78758, USA&lt;br /&gt;
&lt;br /&gt;
=== Other Information ===&lt;br /&gt;
Current Attendance Cap: 25&lt;br /&gt;
&lt;br /&gt;
[https://etherpad.openstack.org/p/keystone-mitaka-midcycle-meetup Etherpad] for Keystone MidCycle Meetup/Sprint Topics and Information&lt;br /&gt;
&lt;br /&gt;
=== Registration ===&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Twitter handle is optional, but often we use twitter to let people know where we are, especially for evening food and/or drinks. Feel free to provide your twitter or just keep an eye out on those of us who have provided ours for where everyone is at the Meetup/when we're headed out for dinner, etc.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Lunches are likely to be provided, please mention any special dietary restrictions in the comments section of the table.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! # !! Name !! IRC Nick !! Twitter (optional) !! Comment !! Email&lt;br /&gt;
|-&lt;br /&gt;
| 1 || Steve Martinelli || stevemar || [https://twitter.com/stevebot @stevebot] || || stevemar AT ca DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 2 || Lance Bragstad || lbragstad || [https://twitter.com/LanceBragstad @LanceBragstad] ||  || lbragstad AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Joe Savak || jsavak || [https://twitter.com/joesavak @JoeSavak] ||  || jsavak AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Fernando Diaz || diazjf || ||  || diazjf AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Dolph Mathews || dolphm || [https://twitter.com/dolphm @dolphm] || No comment. || dolph DOT mathews AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 6 || David Stanek || dstanek || [https://twitter.com/dstanek @dstanek] || I like trees || dstanek AT dstanek DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 7 || Samuel de Medeiros Queiroz || samueldmq || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || samueldmq AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 8 || Brad Topol || topol || https://twitter.com/bradtopol @bradtopol|| Hoping to get fantastic BBQ, recommendations?|| btopol AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 9 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 10 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 11 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 13 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 15 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 17 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 18 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 19 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 20 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 21 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 22 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 23 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 24 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 25 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| || No || more || spaces || available! || (sorry!)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hotel List ===&lt;br /&gt;
&lt;br /&gt;
====  Home2 Suites by Hilton Austin North/Near The Domain ====&lt;br /&gt;
* 2800 Esperanza Crossing, Austin, TX 78758, United States&lt;br /&gt;
* 1-512-339-2400&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 0.3 mi to IBM, very walkable&lt;br /&gt;
&lt;br /&gt;
==== Hyatt Place Austin/Arboretum ====&lt;br /&gt;
* 3612 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* +1 512-231-8491&lt;br /&gt;
* ~$140/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Residence Inn Austin Northwest/Arboretum ====&lt;br /&gt;
* 3713 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8200&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Courtyard Austin Northwest/Arboretum ====&lt;br /&gt;
* 9409 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8100&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
====  Embassy Suites by Hilton Austin Arboretum ====&lt;br /&gt;
* 9505 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-372-8771&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99371</id>
		<title>Sprints/KeystoneMitakaSprint</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99371"/>
				<updated>2015-12-10T16:35:43Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Registration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Keystone Mitaka Midcycle Meetup ==&lt;br /&gt;
This page tracks information for the Keystone Liberty Code Sprint.&lt;br /&gt;
&lt;br /&gt;
=== Time and Location ===&lt;br /&gt;
When: January 27-29 (Wed-Fri) 9:00 AM to 5:pm&lt;br /&gt;
&lt;br /&gt;
Where: IBM Austin - Building 904, Executive Briefing Centre&lt;br /&gt;
11501 Burnet Rd, Austin, TX 78758, USA&lt;br /&gt;
&lt;br /&gt;
=== Other Information ===&lt;br /&gt;
Current Attendance Cap: 25&lt;br /&gt;
&lt;br /&gt;
[https://etherpad.openstack.org/p/keystone-mitaka-midcycle-meetup Etherpad] for Keystone MidCycle Meetup/Sprint Topics and Information&lt;br /&gt;
&lt;br /&gt;
=== Registration ===&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Twitter handle is optional, but often we use twitter to let people know where we are, especially for evening food and/or drinks. Feel free to provide your twitter or just keep an eye out on those of us who have provided ours for where everyone is at the Meetup/when we're headed out for dinner, etc.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Lunches are likely to be provided, please mention any special dietary restrictions in the comments section of the table.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! # !! Name !! IRC Nick !! Twitter (optional) !! Comment !! Email&lt;br /&gt;
|-&lt;br /&gt;
| 1 || Steve Martinelli || stevemar || [https://twitter.com/stevebot @stevebot] || || stevemar AT ca DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 2 || Lance Bragstad || lbragstad || [https://twitter.com/LanceBragstad @LanceBragstad] ||  || lbragstad AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Joe Savak || jsavak || [https://twitter.com/joesavak @JoeSavak] ||  || jsavak AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Fernando Diaz || diazjf || ||  || diazjf AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Dolph Mathews || dolphm || [https://twitter.com/dolphm @dolphm] || No comment. || dolph DOT mathews AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 6 || David Stanek || dstanek || [https://twitter.com/dstanek @dstanek] || I like trees || dstanek AT dstanek DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 7 || Samuel de Medeiros Queiroz || samueldmq || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || samueldmq AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 8 || Brad Topol || topol || &amp;lt;https://twitter.com/bradtopol @bradtopol&amp;gt;|| Hoping to get fantastic BBQ, recommendations?|| btopol AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 9 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 10 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 11 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 13 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 15 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 17 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 18 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 19 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 20 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 21 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 22 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 23 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 24 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 25 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| || No || more || spaces || available! || (sorry!)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hotel List ===&lt;br /&gt;
&lt;br /&gt;
====  Home2 Suites by Hilton Austin North/Near The Domain ====&lt;br /&gt;
* 2800 Esperanza Crossing, Austin, TX 78758, United States&lt;br /&gt;
* 1-512-339-2400&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 0.3 mi to IBM, very walkable&lt;br /&gt;
&lt;br /&gt;
==== Hyatt Place Austin/Arboretum ====&lt;br /&gt;
* 3612 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* +1 512-231-8491&lt;br /&gt;
* ~$140/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Residence Inn Austin Northwest/Arboretum ====&lt;br /&gt;
* 3713 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8200&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Courtyard Austin Northwest/Arboretum ====&lt;br /&gt;
* 9409 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8100&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
====  Embassy Suites by Hilton Austin Arboretum ====&lt;br /&gt;
* 9505 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-372-8771&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99370</id>
		<title>Sprints/KeystoneMitakaSprint</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99370"/>
				<updated>2015-12-10T16:35:12Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Registration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Keystone Mitaka Midcycle Meetup ==&lt;br /&gt;
This page tracks information for the Keystone Liberty Code Sprint.&lt;br /&gt;
&lt;br /&gt;
=== Time and Location ===&lt;br /&gt;
When: January 27-29 (Wed-Fri) 9:00 AM to 5:pm&lt;br /&gt;
&lt;br /&gt;
Where: IBM Austin - Building 904, Executive Briefing Centre&lt;br /&gt;
11501 Burnet Rd, Austin, TX 78758, USA&lt;br /&gt;
&lt;br /&gt;
=== Other Information ===&lt;br /&gt;
Current Attendance Cap: 25&lt;br /&gt;
&lt;br /&gt;
[https://etherpad.openstack.org/p/keystone-mitaka-midcycle-meetup Etherpad] for Keystone MidCycle Meetup/Sprint Topics and Information&lt;br /&gt;
&lt;br /&gt;
=== Registration ===&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Twitter handle is optional, but often we use twitter to let people know where we are, especially for evening food and/or drinks. Feel free to provide your twitter or just keep an eye out on those of us who have provided ours for where everyone is at the Meetup/when we're headed out for dinner, etc.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Lunches are likely to be provided, please mention any special dietary restrictions in the comments section of the table.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! # !! Name !! IRC Nick !! Twitter (optional) !! Comment !! Email&lt;br /&gt;
|-&lt;br /&gt;
| 1 || Steve Martinelli || stevemar || [https://twitter.com/stevebot @stevebot] || || stevemar AT ca DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 2 || Lance Bragstad || lbragstad || [https://twitter.com/LanceBragstad @LanceBragstad] ||  || lbragstad AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Joe Savak || jsavak || [https://twitter.com/joesavak @JoeSavak] ||  || jsavak AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Fernando Diaz || diazjf || ||  || diazjf AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Dolph Mathews || dolphm || [https://twitter.com/dolphm @dolphm] || No comment. || dolph DOT mathews AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 6 || David Stanek || dstanek || [https://twitter.com/dstanek @dstanek] || I like trees || dstanek AT dstanek DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 7 || Samuel de Medeiros Queiroz || samueldmq || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || samueldmq AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 8 || Brad Topol || &amp;lt;topol&amp;gt; || &amp;lt;https://twitter.com/bradtopol @bradtopol&amp;gt;|| Hoping to get fantastic BBQ, recommendations?|| btopol AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 9 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 10 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 11 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 13 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 15 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 17 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 18 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 19 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 20 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 21 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 22 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 23 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 24 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 25 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| || No || more || spaces || available! || (sorry!)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hotel List ===&lt;br /&gt;
&lt;br /&gt;
====  Home2 Suites by Hilton Austin North/Near The Domain ====&lt;br /&gt;
* 2800 Esperanza Crossing, Austin, TX 78758, United States&lt;br /&gt;
* 1-512-339-2400&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 0.3 mi to IBM, very walkable&lt;br /&gt;
&lt;br /&gt;
==== Hyatt Place Austin/Arboretum ====&lt;br /&gt;
* 3612 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* +1 512-231-8491&lt;br /&gt;
* ~$140/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Residence Inn Austin Northwest/Arboretum ====&lt;br /&gt;
* 3713 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8200&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Courtyard Austin Northwest/Arboretum ====&lt;br /&gt;
* 9409 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8100&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
====  Embassy Suites by Hilton Austin Arboretum ====&lt;br /&gt;
* 9505 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-372-8771&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99369</id>
		<title>Sprints/KeystoneMitakaSprint</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneMitakaSprint&amp;diff=99369"/>
				<updated>2015-12-10T16:34:35Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Registration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Keystone Mitaka Midcycle Meetup ==&lt;br /&gt;
This page tracks information for the Keystone Liberty Code Sprint.&lt;br /&gt;
&lt;br /&gt;
=== Time and Location ===&lt;br /&gt;
When: January 27-29 (Wed-Fri) 9:00 AM to 5:pm&lt;br /&gt;
&lt;br /&gt;
Where: IBM Austin - Building 904, Executive Briefing Centre&lt;br /&gt;
11501 Burnet Rd, Austin, TX 78758, USA&lt;br /&gt;
&lt;br /&gt;
=== Other Information ===&lt;br /&gt;
Current Attendance Cap: 25&lt;br /&gt;
&lt;br /&gt;
[https://etherpad.openstack.org/p/keystone-mitaka-midcycle-meetup Etherpad] for Keystone MidCycle Meetup/Sprint Topics and Information&lt;br /&gt;
&lt;br /&gt;
=== Registration ===&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Twitter handle is optional, but often we use twitter to let people know where we are, especially for evening food and/or drinks. Feel free to provide your twitter or just keep an eye out on those of us who have provided ours for where everyone is at the Meetup/when we're headed out for dinner, etc.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Lunches are likely to be provided, please mention any special dietary restrictions in the comments section of the table.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! # !! Name !! IRC Nick !! Twitter (optional) !! Comment !! Email&lt;br /&gt;
|-&lt;br /&gt;
| 1 || Steve Martinelli || stevemar || [https://twitter.com/stevebot @stevebot] || || stevemar AT ca DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 2 || Lance Bragstad || lbragstad || [https://twitter.com/LanceBragstad @LanceBragstad] ||  || lbragstad AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Joe Savak || jsavak || [https://twitter.com/joesavak @JoeSavak] ||  || jsavak AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Fernando Diaz || diazjf || ||  || diazjf AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Dolph Mathews || dolphm || [https://twitter.com/dolphm @dolphm] || No comment. || dolph DOT mathews AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 6 || David Stanek || dstanek || [https://twitter.com/dstanek @dstanek] || I like trees || dstanek AT dstanek DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 7 || Samuel de Medeiros Queiroz || samueldmq || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || samueldmq AT gmail DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 8 || Brad Topol || &amp;lt;topol&amp;gt; || &amp;lt;https://twitter.com/bradtopol @bradtopol&amp;gt;|| &amp;lt;!-- Hoping to get fantastic BBQ, recommendations?--&amp;gt; || btopol AT us DOT ibm DOT com&lt;br /&gt;
|-&lt;br /&gt;
| 9 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 10 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 11 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 13 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 15 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 17 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 18 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 19 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 20 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 21 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 22 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 23 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 24 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 25 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| || No || more || spaces || available! || (sorry!)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hotel List ===&lt;br /&gt;
&lt;br /&gt;
====  Home2 Suites by Hilton Austin North/Near The Domain ====&lt;br /&gt;
* 2800 Esperanza Crossing, Austin, TX 78758, United States&lt;br /&gt;
* 1-512-339-2400&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 0.3 mi to IBM, very walkable&lt;br /&gt;
&lt;br /&gt;
==== Hyatt Place Austin/Arboretum ====&lt;br /&gt;
* 3612 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* +1 512-231-8491&lt;br /&gt;
* ~$140/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Residence Inn Austin Northwest/Arboretum ====&lt;br /&gt;
* 3713 Tudor Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8200&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
==== Courtyard Austin Northwest/Arboretum ====&lt;br /&gt;
* 9409 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-502-8100&lt;br /&gt;
* ~$180/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;br /&gt;
&lt;br /&gt;
====  Embassy Suites by Hilton Austin Arboretum ====&lt;br /&gt;
* 9505 Stonelake Blvd, Austin, TX 78759, United States&lt;br /&gt;
* 1-512-372-8771&lt;br /&gt;
* ~$200/night&lt;br /&gt;
* 3.0 mi to IBM, 5 minute drive&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneLibertySprint&amp;diff=80731</id>
		<title>Sprints/KeystoneLibertySprint</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneLibertySprint&amp;diff=80731"/>
				<updated>2015-05-08T13:20:54Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Registration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Keystone Liberty Midcycle Meetup ==&lt;br /&gt;
This page tracks information for the Keystone Liberty Code Sprint.&lt;br /&gt;
&lt;br /&gt;
=== Time and Location ===&lt;br /&gt;
When: July 15-17 (Wed-Fri) &lt;br /&gt;
&lt;br /&gt;
Where: Boston University, Boston, MA, USA&lt;br /&gt;
&lt;br /&gt;
Recommended Hotels: TBD&lt;br /&gt;
&lt;br /&gt;
=== Other Information ===&lt;br /&gt;
Current Attendance Cap: 30&lt;br /&gt;
&lt;br /&gt;
[https://etherpad.openstack.org/p/keystone-liberty-midcycle-meetup Etherpad] for Keystone MidCycle Meetup/Sprint Topics and Information&lt;br /&gt;
&lt;br /&gt;
=== Registration ===&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Twitter handle is optional, but often we use twitter to let people know where we are, especially for evening food and/or drinks. Feel free to provide your twitter or just keep an eye out on those of us who have provided ours for where everyone is at the Meetup/when we're headed out for dinner, etc.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! # !! Name !! IRC Nick !! Twitter (optional) !! Comment !! Email&lt;br /&gt;
|-&lt;br /&gt;
| 1 || Morgan Fainberg || morganfainberg || [https://twitter.com/MdrnStm @mdrnstm] || || morgan.fainberg AT gmail.com&lt;br /&gt;
|-&lt;br /&gt;
| 2 || Henry Nash || henrynash || [https://twitter.com/henrynash @henrynash] || || henry.nash AT uk.ibm.com&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Adam Young || ayoung  || admiyoung || || ayoung@redhat.com&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Geoff Arnold || geoffarnold  || geoffarnold || || geoff AT geoffarnold.com&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Brad Topol ||  topol || [https://twitter.com/bradtopol @bradtopol] || Will be there all day Wednesday &amp;amp; Thursday || btopol AT us.ibm.com&lt;br /&gt;
|-&lt;br /&gt;
| 6 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 7 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 8 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 9 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 10 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 11 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 13 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 15 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 17 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 18 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 19 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 20 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 21 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 22 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 23 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 24 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 25 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 26 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 27 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 28 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 29 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 30 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| || No || more || spaces || available! || (sorry!)&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneLibertySprint&amp;diff=80730</id>
		<title>Sprints/KeystoneLibertySprint</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Sprints/KeystoneLibertySprint&amp;diff=80730"/>
				<updated>2015-05-08T13:19:54Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Registration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Keystone Liberty Midcycle Meetup ==&lt;br /&gt;
This page tracks information for the Keystone Liberty Code Sprint.&lt;br /&gt;
&lt;br /&gt;
=== Time and Location ===&lt;br /&gt;
When: July 15-17 (Wed-Fri) &lt;br /&gt;
&lt;br /&gt;
Where: Boston University, Boston, MA, USA&lt;br /&gt;
&lt;br /&gt;
Recommended Hotels: TBD&lt;br /&gt;
&lt;br /&gt;
=== Other Information ===&lt;br /&gt;
Current Attendance Cap: 30&lt;br /&gt;
&lt;br /&gt;
[https://etherpad.openstack.org/p/keystone-liberty-midcycle-meetup Etherpad] for Keystone MidCycle Meetup/Sprint Topics and Information&lt;br /&gt;
&lt;br /&gt;
=== Registration ===&lt;br /&gt;
&lt;br /&gt;
'''Note:''' Twitter handle is optional, but often we use twitter to let people know where we are, especially for evening food and/or drinks. Feel free to provide your twitter or just keep an eye out on those of us who have provided ours for where everyone is at the Meetup/when we're headed out for dinner, etc.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! # !! Name !! IRC Nick !! Twitter (optional) !! Comment !! Email&lt;br /&gt;
|-&lt;br /&gt;
| 1 || Morgan Fainberg || morganfainberg || [https://twitter.com/MdrnStm @mdrnstm] || || morgan.fainberg AT gmail.com&lt;br /&gt;
|-&lt;br /&gt;
| 2 || Henry Nash || henrynash || [https://twitter.com/henrynash @henrynash] || || henry.nash AT uk.ibm.com&lt;br /&gt;
|-&lt;br /&gt;
| 3 || Adam Young || ayoung  || admiyoung || || ayoung@redhat.com&lt;br /&gt;
|-&lt;br /&gt;
| 4 || Geoff Arnold || geoffarnold  || geoffarnold || || geoff AT geoffarnold.com&lt;br /&gt;
|-&lt;br /&gt;
| 5 || Brad Topol || &amp;lt; topol || https://twitter.com/bradtopol @bradtopol|| Will be there all day Wednesday &amp;amp; Thursday || btopol AT us.ibm.com&lt;br /&gt;
|-&lt;br /&gt;
| 6 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 7 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 8 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 9 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 10 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 11 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 12 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 13 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 14 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 15 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 16 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 17 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 18 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 19 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 20 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 21 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 22 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 23 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 24 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 25 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 26 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 27 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 28 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 29 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| 30 || &amp;lt;!-- name --&amp;gt; || &amp;lt;!-- irc --&amp;gt; || &amp;lt;!-- twitter --&amp;gt;|| &amp;lt;!-- comment --&amp;gt; || &amp;lt;!-- email --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| || No || more || spaces || available! || (sorry!)&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Keystone&amp;diff=56643</id>
		<title>Keystone</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Keystone&amp;diff=56643"/>
				<updated>2014-06-24T19:51:01Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= OpenStack Identity (&amp;quot;Keystone&amp;quot;) =&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
|  Source code   &lt;br /&gt;
|-&lt;br /&gt;
|  Bug tracker   &lt;br /&gt;
|-&lt;br /&gt;
|  Blueprints    &lt;br /&gt;
|-&lt;br /&gt;
|  Developer doc &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Related projects ==&lt;br /&gt;
* Python Keystone client&lt;br /&gt;
* Identity API documentation&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
* [https://github.com/openstack/identity-api/blob/master/v3/src/markdown/identity-api-v3.md Identity API (v3) specification]&lt;br /&gt;
* [http://docs.openstack.org/api/openstack-identity-service/2.0/content/ Identity API (v2) specification]&lt;br /&gt;
&lt;br /&gt;
== What is Keystone? ==&lt;br /&gt;
&lt;br /&gt;
Keystone is the identity service used by [[OpenStack]] for authentication (authN) and high-level authorization (authZ). It currently supports token-based authN and user-service authorization. It has recently been rearchitected to allow for expansion to support proxying external services and AuthN/AuthZ mechanisms such as oAuth, SAML and openID in future versions.&lt;br /&gt;
&lt;br /&gt;
'''Meetings'''&lt;br /&gt;
&lt;br /&gt;
* http://wiki.openstack.org/Meetings/KeystoneMeeting&lt;br /&gt;
&lt;br /&gt;
'''Doc'''&lt;br /&gt;
&lt;br /&gt;
* http://keystone.openstack.org&lt;br /&gt;
&lt;br /&gt;
'''Code'''&lt;br /&gt;
&lt;br /&gt;
* Source&lt;br /&gt;
** https://github.com/openstack/keystone&lt;br /&gt;
* Pending Code Reviews:&lt;br /&gt;
** Keystone Service: https://review.openstack.org/#q,status:open+keystone,n,z&lt;br /&gt;
** Keystone Client: https://review.openstack.org/#/q/status:open+python-keystoneclient,n,z&lt;br /&gt;
** Keystone Middleware: https://review.openstack.org/#q,status:open+keystonemiddleware,n,z&lt;br /&gt;
&lt;br /&gt;
* Keystone Spec Repository:&lt;br /&gt;
** https://review.openstack.org/#q,status:open+keystone-specs,n,z&lt;br /&gt;
&lt;br /&gt;
'''Bugs and Blueprints'''&lt;br /&gt;
* [https://bugs.launchpad.net/keystone/+bugs?orderby=-importance&amp;amp;field.status%3Alist=NEW&amp;amp;field.status%3Alist=CONFIRMED&amp;amp;field.status%3Alist=TRIAGED&amp;amp;field.status%3Alist=INPROGRESS&amp;amp;field.status%3Alist=INCOMPLETE_WITH_RESPONSE&amp;amp;field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&amp;amp;assignee_option=any&amp;amp;field.tag=-python-keystoneclient&amp;amp;field.tags_combinator=ANY&amp;amp;field.omit_dupes=on&amp;amp;field.has_branches=on&amp;amp;field.has_no_branches=on&amp;amp;field.has_blueprints=on&amp;amp;field.has_no_blueprints=on   keystone bugs]&lt;br /&gt;
* [https://bugs.launchpad.net/python-keystoneclient/+bugs?orderby=-importance&amp;amp;field.status%3Alist=NEW&amp;amp;field.status%3Alist=CONFIRMED&amp;amp;field.status%3Alist=TRIAGED&amp;amp;field.status%3Alist=INPROGRESS&amp;amp;field.status%3Alist=INCOMPLETE_WITH_RESPONSE&amp;amp;field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&amp;amp;assignee_option=any&amp;amp;field.tag=-python-keystoneclient&amp;amp;field.tags_combinator=ANY&amp;amp;field.omit_dupes=on&amp;amp;field.has_branches=on&amp;amp;field.has_no_branches=on&amp;amp;field.has_blueprints=on&amp;amp;field.has_no_blueprints=on   keystone client bugs]&lt;br /&gt;
* [https://blueprints.launchpad.net/keystone   keystone blueprints]&lt;br /&gt;
* [https://blueprints.launchpad.net/python-keystoneclient   keystone client blueprints]&lt;br /&gt;
* ''bugs tags''&lt;br /&gt;
** blueprint (implies bug indicates a needed feature or function, can be migrated to a blueprint)&lt;br /&gt;
** python-keystoneclient (related to the client end of keystone)&lt;br /&gt;
** legacy (existing prior to the feb14, 2012 rebaseline of the code)&lt;br /&gt;
** gsoc (appropriate for a google summer of code project effort)&lt;br /&gt;
** low-hanging-fruit (easy piece for someone to get started with, minimal design needed to solve)&lt;br /&gt;
* ''importance meanings''&lt;br /&gt;
** critical (bug renders the system non-functional)&lt;br /&gt;
** high (bug we want resolved before the next release)&lt;br /&gt;
** medium/low (general issue bug or annoyance, perhaps requiring significant design change to implement or new features needed to resolve)&lt;br /&gt;
** wishlist (nice to have)&lt;br /&gt;
&lt;br /&gt;
'''Use Cases'''&lt;br /&gt;
&lt;br /&gt;
* [[KeystoneUseCases]]&lt;br /&gt;
&lt;br /&gt;
'''Performance'''&lt;br /&gt;
&lt;br /&gt;
* [[KeystonePerformance]]&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Meetings/KeystoneMeeting&amp;diff=19210</id>
		<title>Meetings/KeystoneMeeting</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Meetings/KeystoneMeeting&amp;diff=19210"/>
				<updated>2013-03-19T17:56:17Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Agenda for next meeting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Weekly Keystone team meeting =&lt;br /&gt;
&lt;br /&gt;
If you're interested in identity for OpenStack, we hold public meetings weekly in &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, on Tuesdays at 18:00 UTC. Please feel free to add items to the agenda below and we'll cover them.&lt;br /&gt;
&lt;br /&gt;
== Agenda for next meeting ==&lt;br /&gt;
&lt;br /&gt;
Scheduled for [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130305T18 Tuesday, Mar 19th, 2013, 1800 UTC]&lt;br /&gt;
*  RC Bugs &lt;br /&gt;
* https://launchpad.net/keystone/+milestone/grizzly-rc1&lt;br /&gt;
* https://launchpad.net/keystone/+milestone/grizzly-rc2&lt;br /&gt;
* High priority bugs or immediate issues?&lt;br /&gt;
* Open discussion&lt;br /&gt;
I explicitly added the cosine and inetorgperson schema files in a patch to fix devstack install ldap on fedora. And then noticed they have a license in them&lt;br /&gt;
Does that keep me from being able to bundle them up? Please see https://review.openstack.org/#/c/24764/&lt;br /&gt;
Otherwise I need to know if these files are consistently placed in a certain location when openldap is installed on Fedora&lt;br /&gt;
=== Known issues for Havana Summit ===&lt;br /&gt;
&lt;br /&gt;
* Scoping to endpoints&lt;br /&gt;
* redefining what is meant by is_admin&lt;br /&gt;
* Documenting Workflow bestpractices&lt;br /&gt;
* X509&lt;br /&gt;
* Mapping and Delegation&lt;br /&gt;
* Apache, Kerberos, Active Directory and LDAP&lt;br /&gt;
* HATEOAS&lt;br /&gt;
* HTTPS not available as an option, tokens vulnerable to packet sniffiing&lt;br /&gt;
* Embracing open standards for authentication and authorization (e.g. Oauth, SAML) to support external services for authentication and authorization&lt;br /&gt;
* Endpoint Filtering&lt;br /&gt;
* Service Metadata&lt;br /&gt;
&lt;br /&gt;
== Previous meetings ==&lt;br /&gt;
&lt;br /&gt;
Mar 12th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-03-12-18.01.html&lt;br /&gt;
&lt;br /&gt;
Mar 5th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-03-05-18.01.html&lt;br /&gt;
&lt;br /&gt;
Feb 26th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-26-18.03.html&lt;br /&gt;
&lt;br /&gt;
Feb 19th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-19-18.01.html&lt;br /&gt;
&lt;br /&gt;
Feb 12th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-12-18.02.html&lt;br /&gt;
&lt;br /&gt;
Feb 5th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-05-18.00.html&lt;br /&gt;
&lt;br /&gt;
Jan 29th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-29-17.59.html&lt;br /&gt;
&lt;br /&gt;
Jan 22nd: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-22-18.00.html&lt;br /&gt;
&lt;br /&gt;
Jan 15th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-15-18.02.html&lt;br /&gt;
&lt;br /&gt;
Jan 8th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-08-18.00.html&lt;br /&gt;
&lt;br /&gt;
Dec 18th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-18-18.00.html&lt;br /&gt;
&lt;br /&gt;
Dec 12th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-11-18.00.html&lt;br /&gt;
&lt;br /&gt;
Dec 4th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-04-18.00.html&lt;br /&gt;
&lt;br /&gt;
Nov 27th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-27-18.10.html&lt;br /&gt;
&lt;br /&gt;
Nov 20th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-20-18.01.html&lt;br /&gt;
&lt;br /&gt;
Nov 6th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-06-18.00.html&lt;br /&gt;
&lt;br /&gt;
Oct 30th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-10-30-18.00.html&lt;br /&gt;
&lt;br /&gt;
Oct 23rd: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-10-23-18.04.html&lt;br /&gt;
&lt;br /&gt;
Oct 2nd: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-10-02-18.01.html&lt;br /&gt;
&lt;br /&gt;
Sept 25th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-25-18.00.html&lt;br /&gt;
&lt;br /&gt;
Sept 18th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-18-18.00.html&lt;br /&gt;
&lt;br /&gt;
Sept 11th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-11-18.01.html&lt;br /&gt;
&lt;br /&gt;
Sept 4th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-04-17.58.html&lt;br /&gt;
&lt;br /&gt;
Aug 28th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-08-28-18.07.html&lt;br /&gt;
&lt;br /&gt;
Aug 21st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-18.02.html&lt;br /&gt;
&lt;br /&gt;
Aug 14th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-18.00.html&lt;br /&gt;
&lt;br /&gt;
Aug 7th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-18.00.html&lt;br /&gt;
&lt;br /&gt;
July 31st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-18.00.html&lt;br /&gt;
&lt;br /&gt;
July 24th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-24-18.01.html&lt;br /&gt;
&lt;br /&gt;
July 10th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-10-18.01.html&lt;br /&gt;
&lt;br /&gt;
July 3rd: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-18.01.html&lt;br /&gt;
&lt;br /&gt;
June 26th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-26-18.01.html&lt;br /&gt;
&lt;br /&gt;
June 19th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-19-18.00.html&lt;br /&gt;
&lt;br /&gt;
June 12th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-12-18.02.html&lt;br /&gt;
&lt;br /&gt;
June 5th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-05-18.06.html&lt;br /&gt;
&lt;br /&gt;
May 29th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-18.02.html&lt;br /&gt;
&lt;br /&gt;
May 22nd: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-22-18.02.html&lt;br /&gt;
&lt;br /&gt;
May 15th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-15-18.02.html&lt;br /&gt;
&lt;br /&gt;
May 8th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-08-18.01.html&lt;br /&gt;
&lt;br /&gt;
May 1st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-18.01.log.txt&lt;br /&gt;
&lt;br /&gt;
Apr 24th:  http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-24-18.05.html&lt;br /&gt;
&lt;br /&gt;
Apr 10th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-10-18.02.html&lt;br /&gt;
&lt;br /&gt;
Mar 27th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-27-18.01.html&lt;br /&gt;
&lt;br /&gt;
Mar 20th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-20-18.02.html&lt;br /&gt;
&lt;br /&gt;
Mar 13th: (two meetings, because I couldn't get my time shifts straight)&lt;br /&gt;
&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-13-16.12.html&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-13-18.00.html&lt;br /&gt;
&lt;br /&gt;
Mar 6th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-06-18.01.html&lt;br /&gt;
&lt;br /&gt;
Feb 28th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-28-18.02.html&lt;br /&gt;
&lt;br /&gt;
Feb 21st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-21-18.03.html&lt;br /&gt;
&lt;br /&gt;
Feb 14th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-18.00.html&lt;br /&gt;
&lt;br /&gt;
Jan 31st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-31-18.02.html&lt;br /&gt;
&lt;br /&gt;
Jan 17th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-18.00.txt&lt;br /&gt;
&lt;br /&gt;
Jan 10th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-10-18.13.txt&lt;br /&gt;
&lt;br /&gt;
Dec 20th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-20-17.58.txt&lt;br /&gt;
&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-20-17.58.log.html&lt;br /&gt;
&lt;br /&gt;
Dec 13th: No attendees&lt;br /&gt;
&lt;br /&gt;
Dec 6th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-18.00.txt&lt;br /&gt;
&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-18.00.log.html&lt;br /&gt;
&lt;br /&gt;
Nov 29: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-18.00.txt&lt;br /&gt;
&lt;br /&gt;
Previous meetings, with their notes and logs, can be found in under [[Keystone/MeetingLogs]]&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Meetings/KeystoneMeeting&amp;diff=18682</id>
		<title>Meetings/KeystoneMeeting</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Meetings/KeystoneMeeting&amp;diff=18682"/>
				<updated>2013-03-05T16:44:13Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Agenda for next meeting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Weekly Keystone team meeting =&lt;br /&gt;
If you're interested in identity for OpenStack, we hold public meetings weekly in &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, on Tuesdays at 18:00 UTC. Please feel free to add items to the agenda below and we'll cover them.&lt;br /&gt;
&lt;br /&gt;
== Agenda for next meeting ==&lt;br /&gt;
Scheduled for [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130305T18 Tuesday, Mar 5th, 2013, 1800 UTC]&lt;br /&gt;
&lt;br /&gt;
* High priority bugs or immediate issues?&lt;br /&gt;
* Trusts:&lt;br /&gt;
      dependency chain:  Sync timeutils with oslo  &amp;lt;- fix inconsistent format for expires_at and issued_at &amp;lt;- Trusts&lt;br /&gt;
           &amp;lt;- Expand v3 trust test coverage&lt;br /&gt;
&lt;br /&gt;
* Folsom Stable:&lt;br /&gt;
** Backport potential for https://review.openstack.org/#/c/15116/&lt;br /&gt;
** Hashing PKI tokens in auth-token middleware https://review.openstack.org/#/c/15116/&lt;br /&gt;
** Backport for in memory caching https://review.openstack.org/#/c/23309/3&lt;br /&gt;
&lt;br /&gt;
	 	&lt;br /&gt;
&lt;br /&gt;
* Known issues For Havana Summit:&lt;br /&gt;
** Scoping to endpoints&lt;br /&gt;
** Documenting Workflow bestpractices&lt;br /&gt;
** X509&lt;br /&gt;
** Mapping and Delegation&lt;br /&gt;
** Apache, Kerberos, Active Directory and LDAP&lt;br /&gt;
** HATEOAS&lt;br /&gt;
**HTTPS not available as an option, tokens vulnerable to packet sniffiing&lt;br /&gt;
**Embracing open standards for authentication and authorization (e.g. Oauth, SAML) to support external services for authentication and authorization&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Open discussion&lt;br /&gt;
&lt;br /&gt;
== Previous meetings ==&lt;br /&gt;
&lt;br /&gt;
Feb 26th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-26-18.03.html&lt;br /&gt;
&lt;br /&gt;
Feb 19th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-19-18.01.html&lt;br /&gt;
&lt;br /&gt;
Feb 12th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-12-18.02.html&lt;br /&gt;
&lt;br /&gt;
Feb 5th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-05-18.00.html&lt;br /&gt;
&lt;br /&gt;
Jan 29th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-29-17.59.html&lt;br /&gt;
&lt;br /&gt;
Jan 22nd: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-22-18.00.html&lt;br /&gt;
&lt;br /&gt;
Jan 15th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-15-18.02.html&lt;br /&gt;
&lt;br /&gt;
Jan 8th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-08-18.00.html&lt;br /&gt;
&lt;br /&gt;
Dec 18th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-18-18.00.html&lt;br /&gt;
&lt;br /&gt;
Dec 12th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-11-18.00.html&lt;br /&gt;
&lt;br /&gt;
Dec 4th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-04-18.00.html&lt;br /&gt;
&lt;br /&gt;
Nov 27th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-27-18.10.html&lt;br /&gt;
&lt;br /&gt;
Nov 20th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-20-18.01.html&lt;br /&gt;
&lt;br /&gt;
Nov 6th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-06-18.00.html&lt;br /&gt;
&lt;br /&gt;
Oct 30th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-10-30-18.00.html&lt;br /&gt;
&lt;br /&gt;
Oct 23rd: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-10-23-18.04.html&lt;br /&gt;
&lt;br /&gt;
Oct 2nd: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-10-02-18.01.html&lt;br /&gt;
&lt;br /&gt;
Sept 25th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-25-18.00.html&lt;br /&gt;
&lt;br /&gt;
Sept 18th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-18-18.00.html&lt;br /&gt;
&lt;br /&gt;
Sept 11th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-11-18.01.html&lt;br /&gt;
&lt;br /&gt;
Sept 4th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-04-17.58.html&lt;br /&gt;
&lt;br /&gt;
Aug 28th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-08-28-18.07.html&lt;br /&gt;
&lt;br /&gt;
Aug 21st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-18.02.html&lt;br /&gt;
&lt;br /&gt;
Aug 14th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-18.00.html&lt;br /&gt;
&lt;br /&gt;
Aug 7th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-18.00.html&lt;br /&gt;
&lt;br /&gt;
July 31st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-18.00.html&lt;br /&gt;
&lt;br /&gt;
July 24th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-24-18.01.html&lt;br /&gt;
&lt;br /&gt;
July 10th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-10-18.01.html&lt;br /&gt;
&lt;br /&gt;
July 3rd: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-18.01.html&lt;br /&gt;
&lt;br /&gt;
June 26th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-26-18.01.html&lt;br /&gt;
&lt;br /&gt;
June 19th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-19-18.00.html&lt;br /&gt;
&lt;br /&gt;
June 12th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-12-18.02.html&lt;br /&gt;
&lt;br /&gt;
June 5th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-05-18.06.html&lt;br /&gt;
&lt;br /&gt;
May 29th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-18.02.html&lt;br /&gt;
&lt;br /&gt;
May 22nd: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-22-18.02.html&lt;br /&gt;
&lt;br /&gt;
May 15th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-15-18.02.html&lt;br /&gt;
&lt;br /&gt;
May 8th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-08-18.01.html&lt;br /&gt;
&lt;br /&gt;
May 1st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-18.01.log.txt&lt;br /&gt;
&lt;br /&gt;
Apr 24th:  http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-24-18.05.html&lt;br /&gt;
&lt;br /&gt;
Apr 10th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-10-18.02.html&lt;br /&gt;
&lt;br /&gt;
Mar 27th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-27-18.01.html&lt;br /&gt;
&lt;br /&gt;
Mar 20th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-20-18.02.html&lt;br /&gt;
&lt;br /&gt;
Mar 13th: (two meetings, because I couldn't get my time shifts straight)&lt;br /&gt;
&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-13-16.12.html&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-13-18.00.html&lt;br /&gt;
&lt;br /&gt;
Mar 6th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-06-18.01.html&lt;br /&gt;
&lt;br /&gt;
Feb 28th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-28-18.02.html&lt;br /&gt;
&lt;br /&gt;
Feb 21st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-21-18.03.html&lt;br /&gt;
&lt;br /&gt;
Feb 14th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-18.00.html&lt;br /&gt;
&lt;br /&gt;
Jan 31st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-31-18.02.html&lt;br /&gt;
&lt;br /&gt;
Jan 17th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-18.00.txt&lt;br /&gt;
&lt;br /&gt;
Jan 10th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-10-18.13.txt&lt;br /&gt;
&lt;br /&gt;
Dec 20th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-20-17.58.txt&lt;br /&gt;
&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-20-17.58.log.html&lt;br /&gt;
&lt;br /&gt;
Dec 13th: No attendees&lt;br /&gt;
&lt;br /&gt;
Dec 6th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-18.00.txt&lt;br /&gt;
&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-18.00.log.html&lt;br /&gt;
&lt;br /&gt;
Nov 29: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-18.00.txt&lt;br /&gt;
&lt;br /&gt;
Previous meetings, with their notes and logs, can be found in under [[Keystone/MeetingLogs]]&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	<entry>
		<id>https://wiki.openstack.org/w/index.php?title=Meetings/KeystoneMeeting&amp;diff=18076</id>
		<title>Meetings/KeystoneMeeting</title>
		<link rel="alternate" type="text/html" href="https://wiki.openstack.org/w/index.php?title=Meetings/KeystoneMeeting&amp;diff=18076"/>
				<updated>2013-02-19T03:00:25Z</updated>
		
		<summary type="html">&lt;p&gt;Topol: /* Agenda for next meeting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= Weekly Keystone team meeting =&lt;br /&gt;
If you're interested in identity for OpenStack, we hold public meetings weekly in &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;#openstack-meeting&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;, on Tuesdays at 18:00 UTC. Please feel free to add items to the agenda below and we'll cover them.&lt;br /&gt;
&lt;br /&gt;
== Agenda for next meeting ==&lt;br /&gt;
Scheduled for [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130219T18 Tuesday, Feb 19th, 2013, 1800 UTC]&lt;br /&gt;
&lt;br /&gt;
* High priority bugs or immediate issues?&lt;br /&gt;
* Grizzly feature freeze&lt;br /&gt;
*Understand the implications of https://review.openstack.org/#/c/21327/13, what would the ldap structure now look like?  Will this affect things like ProjectAPI.attribute_mapping = {'name': 'ou', 'description': 'desc', 'tenantId': 'cn',  'enabled': 'enabled'}&lt;br /&gt;
* Open discussion&lt;br /&gt;
&lt;br /&gt;
== Previous meetings ==&lt;br /&gt;
&lt;br /&gt;
Feb 12th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-12-18.02.html&lt;br /&gt;
&lt;br /&gt;
Feb 5th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-05-18.00.html&lt;br /&gt;
&lt;br /&gt;
Jan 29th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-29-17.59.html&lt;br /&gt;
&lt;br /&gt;
Jan 22nd: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-22-18.00.html&lt;br /&gt;
&lt;br /&gt;
Jan 15th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-15-18.02.html&lt;br /&gt;
&lt;br /&gt;
Jan 8th: http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-08-18.00.html&lt;br /&gt;
&lt;br /&gt;
Dec 18th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-18-18.00.html&lt;br /&gt;
&lt;br /&gt;
Dec 12th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-11-18.00.html&lt;br /&gt;
&lt;br /&gt;
Dec 4th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-12-04-18.00.html&lt;br /&gt;
&lt;br /&gt;
Nov 27th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-27-18.10.html&lt;br /&gt;
&lt;br /&gt;
Nov 20th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-20-18.01.html&lt;br /&gt;
&lt;br /&gt;
Nov 6th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-06-18.00.html&lt;br /&gt;
&lt;br /&gt;
Oct 30th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-10-30-18.00.html&lt;br /&gt;
&lt;br /&gt;
Oct 23rd: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-10-23-18.04.html&lt;br /&gt;
&lt;br /&gt;
Oct 2nd: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-10-02-18.01.html&lt;br /&gt;
&lt;br /&gt;
Sept 25th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-25-18.00.html&lt;br /&gt;
&lt;br /&gt;
Sept 18th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-18-18.00.html&lt;br /&gt;
&lt;br /&gt;
Sept 11th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-11-18.01.html&lt;br /&gt;
&lt;br /&gt;
Sept 4th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-09-04-17.58.html&lt;br /&gt;
&lt;br /&gt;
Aug 28th: http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-08-28-18.07.html&lt;br /&gt;
&lt;br /&gt;
Aug 21st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-21-18.02.html&lt;br /&gt;
&lt;br /&gt;
Aug 14th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-18.00.html&lt;br /&gt;
&lt;br /&gt;
Aug 7th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-07-18.00.html&lt;br /&gt;
&lt;br /&gt;
July 31st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-18.00.html&lt;br /&gt;
&lt;br /&gt;
July 24th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-24-18.01.html&lt;br /&gt;
&lt;br /&gt;
July 10th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-10-18.01.html&lt;br /&gt;
&lt;br /&gt;
July 3rd: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-03-18.01.html&lt;br /&gt;
&lt;br /&gt;
June 26th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-26-18.01.html&lt;br /&gt;
&lt;br /&gt;
June 19th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-19-18.00.html&lt;br /&gt;
&lt;br /&gt;
June 12th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-12-18.02.html&lt;br /&gt;
&lt;br /&gt;
June 5th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-05-18.06.html&lt;br /&gt;
&lt;br /&gt;
May 29th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-29-18.02.html&lt;br /&gt;
&lt;br /&gt;
May 22nd: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-22-18.02.html&lt;br /&gt;
&lt;br /&gt;
May 15th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-15-18.02.html&lt;br /&gt;
&lt;br /&gt;
May 8th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-08-18.01.html&lt;br /&gt;
&lt;br /&gt;
May 1st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-01-18.01.log.txt&lt;br /&gt;
&lt;br /&gt;
Apr 24th:  http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-24-18.05.html&lt;br /&gt;
&lt;br /&gt;
Apr 10th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-04-10-18.02.html&lt;br /&gt;
&lt;br /&gt;
Mar 27th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-27-18.01.html&lt;br /&gt;
&lt;br /&gt;
Mar 20th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-20-18.02.html&lt;br /&gt;
&lt;br /&gt;
Mar 13th: (two meetings, because I couldn't get my time shifts straight)&lt;br /&gt;
&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-13-16.12.html&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-13-18.00.html&lt;br /&gt;
&lt;br /&gt;
Mar 6th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-03-06-18.01.html&lt;br /&gt;
&lt;br /&gt;
Feb 28th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-28-18.02.html&lt;br /&gt;
&lt;br /&gt;
Feb 21st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-21-18.03.html&lt;br /&gt;
&lt;br /&gt;
Feb 14th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-02-14-18.00.html&lt;br /&gt;
&lt;br /&gt;
Jan 31st: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-31-18.02.html&lt;br /&gt;
&lt;br /&gt;
Jan 17th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-17-18.00.txt&lt;br /&gt;
&lt;br /&gt;
Jan 10th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-01-10-18.13.txt&lt;br /&gt;
&lt;br /&gt;
Dec 20th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-20-17.58.txt&lt;br /&gt;
&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-20-17.58.log.html&lt;br /&gt;
&lt;br /&gt;
Dec 13th: No attendees&lt;br /&gt;
&lt;br /&gt;
Dec 6th: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-18.00.txt&lt;br /&gt;
&lt;br /&gt;
* http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-18.00.log.html&lt;br /&gt;
&lt;br /&gt;
Nov 29: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-18.00.txt&lt;br /&gt;
&lt;br /&gt;
Previous meetings, with their notes and logs, can be found in under [[Keystone/MeetingLogs]]&lt;/div&gt;</summary>
		<author><name>Topol</name></author>	</entry>

	</feed>