settingsLogin | Registersettings

[OpenStack-DefCore] [interop-challenge] Workload Results

0 votes

1.) Your name: Ghe Rivero
2.) Your email: ghe.rivero@hpe.com
3.) Reporting on behalf of Company/Organization: HPE
4.) Name and version (if applicable) of the product you tested: HPE Helion
OpenStack 4.0
5.) Version of OpenStack the product uses: Mitaka
6.) Link to RefStack results for this product:
https://refstack.openstack.org/#/results/68ae5223-9cea-4c8f-ba53-6efb21179e39
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/No

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.

TASK [apply : Create database node]


fatal: [cloud]: FAILED! => {"changed": false, "extradata": null, "failed":
true, "msg": "unable to get available floating IPs: unable to create
floating IP for net 972840f9-3c51-4d94-9c49-42e6d8c0cd26: Bad floatingip
request: Network 972840f9-3c51-4d94-9c49-42e6d8c0cd26 is not a valid
external network\nNeutron server returns request
ids:
['req-1248569d-1e66-4f1c-a87a-92ec74b4d439']"}

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.
Private cloud running inside vpn with restricted access to the internet
via proxies.
Multiple external networks without floating ip support that raised a bug
in the shade library used by ansible

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?
https://review.openstack.org/#/c/384044/ - shade [WIP] Exclude
physical_provider from external networks
https://review.openstack.org/#/c/384733/ - osops-tools-contrib Add
.tox and site.retry to gitignore list
https://review.openstack.org/#/c/384738/ - osops-tools-contrib Add
proxy support

Ghe Rivero
--
Pinky: "Gee, Brain, what do you want to do tonight?"
The Brain: "The same thing we do every night, Pinky—try to take over the
world!"

.''. Pienso, Luego Incordio : :' :. '- www.debian.org www.openstack.com

GPG Key: 26F020F7
GPG fingerprint: 4986 39DA D152 050B 4699 9A71 66DB 5A36 26F0 20F7


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
asked Oct 11, 2016 in defcore-committee by Ghe_Rivero (1,400 points)   2

1 Response

0 votes

1.) Your name: Daniel Mellado

2.) Your email: dmellado@redhat.com

3.) Reporting on behalf of Company/Organization: Red Hat

4.) Name and version (if applicable) of the product you tested:
Red Hat OpenStack Platform 9

5.) Version of OpenStack the product uses: Mitaka

6.) Link to RefStack results for this product:
https://refstack.openstack.org/#/results/475433fd-4b12-4de4-b930-36a42a139446

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.
I had a few issues with host cert, which wasn't disabled in Ansible, so
when the workload tried to connect to the ssh volumes, it asked for
confirmation. I've submitted a patch for this and it's already merged,
so it should be good now.

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.

Yes, I submitted a patch for it:
https://review.openstack.org/#/c/382216/

I've also submitted another patch in order to leverage possible issues
with versions of shade that allows to use tox to run the lampstack test.
https://review.openstack.org/#/c/383076/

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?

N/A (already done)

8.) Workload 2: Docker Swarm with Terraform and/ or Ansible
(http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/ansible/dockerswarm)

A.) Did the workload run successfully?

Yes, with Ansible – Same issue with host key cert, fixed in the same way

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.

Same issue with host key cert, fixed in the same way

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.

N/A

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?

N/A


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Oct 11, 2016 by dmellado_at_redhat.c (400 points)  
...