Open Stack

1.) Your name: Rohit Agarwalla
2.) Your email: roagarwa at cisco.com
3.) Reporting on behalf of Company/Organization: Cisco
4.) Name and version (if applicable) of the product you tested: Cisco Metapod 4.0 (https://www.openstack.org/marketplace/distros/distribution/cisco/cisco-metapod-)
5.) Version of OpenStack the product uses: Liberty
6.) Link to RefStack results for this product:
Cisco Metapod 4.0 - https://refstack.openstack.org/#/results/0f4c390f-d256-4549-8393-f42709dbce14
(Guideline Version: 2016.01, Target Program: OpenStack Powered Compute) – OpenStack Compute Compliant with 2016.01.

7.) Workload 1: LAMP Stack with Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/lampstack)
  A.) Did the workload run successfully? Yes

  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.

  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.

  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?

The workload code did not support provider networks and self-signed certificates. The feedback was provided and this was fixed in this review - https://review.openstack.org/#/c/379116/


8.) Workload 2: Docker Swarm with Terraform and Ansible (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos, http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/dockerswarm)
  A.) Did the workload run successfully? Yes

  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.

  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.
  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?

The workload code referenced an unsupported parameter. The feedback was provided and this was fixed in this review - https://review.openstack.org/#/c/356586/
Thanks
Rohit
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20161008/83785d69/attachment-0001.html>