settingsLogin | Registersettings

[OpenStack-DefCore] [interop-challenge] Workload Results by Fujitsu Private Cloud

0 votes

1.) Your name: Daisuke Butsuda

2.) Your email: butsuda.daisuke@jp.fujitsu.combutsuda.daisuke@jp.fujitsu.com

3.) Reporting on behalf of Company/Organization: Fujitsu Limited.,

4.) Name and version (if applicable) of the product you tested: Fujitsu Private Cloud Service (TBD)

5.) Version of OpenStack the product uses: Kilo

6.) Link to RefStack results for this product:

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.

I already reached the cause of the problem; failed to download wordpress-importer.

Our test environment is settled inside of our company network with proxy server.

And I found Wordpress has problems to add-on the plugin via SSL behind a proxy.



[Direct cause]

TASK [wordpress : Import wordpress posts] **************************************

task path: /root/git/osops-tools-contrib/ansible/lampstack/roles/wordpress/tasks/main.yml:34

fatal: [10.124.166.134]: FAILED! => {"changed": true, "cmd": "sudo -u www-data wp --path=/var/www/html import /tmp/posts/.xml --authors=create --quiet", "delta": "0:00:00.359765", "end": "2016-09-27 04:39:28.488125", "failed": true, "invocation": {"moduleargs": {"raw_params": "sudo -u www-data wp --path=/var/www/html import /tmp/posts/.xml --authors=create --quiet", "usesshell": true, "chdir": null, "creates": null, "executable": null, "removes": null, "warn": true}, "modulename": "command"}, "rc": 1, "start": "2016-09-27 04:39:28.128360", "stderr": "Error: WordPress Importer needs to be installed. Try 'wp plugin install wordpress-importer --activate'.", "stdout": "", "stdoutlines": [], "warnings": ["Consider using 'become', 'becomemethod', and 'becomeuser' rather than running sudo"]}

[Problem trigger]

TASK [wordpress : Install wordpress importor plugin] ***************************

task path: /root/git/osops-tools-contrib/ansible/lampstack/roles/wordpress/tasks/main.yml:16

changed: [10.124.166.134] => {"changed": true, "cmd": "sudo -u www-data wp --path=/var/www/html plugin install wordpress-importer --activate", "delta": "0:00:00.465134", "end": "2016-09-27 04:39:26.824963", "invocation": {"moduleargs": {"rawparams": "sudo -u www-data wp --path=/var/www/html plugin install wordpress-importer --activate", "usesshell": true, "chdir": null, "creates": null, "executable": null, "removes": null, "warn": false}, "modulename": "command"}, "rc": 0, "start": "2016-09-27 04:39:26.359829", "stderr": "Warning: wordpress-importer: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the ">support forums.\nWarning: The 'wordpress-importer' plugin could not be found.", "stdout": "Activating 'wordpress-importer'...", "stdout_lines": ["Activating 'wordpress-importer'..."], "warnings": []}

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.

Importation of wordpress-importer has failed in the environment which has settled behind a proxy server.

This can be fixed by Wordpress (wp command) and no necessity for ansible scripts / definition.

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 described)

8.) Workload 2: Docker Swarm with Terraform (http://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/terraform/dockerswarm-coreos)

A.) Did the workload run successfully? N/A

N/A

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.

N/A

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?

9.) Workload 3: NFV (URL TBD) N/A

A.) Did the workload run successfully?

N/A

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.

N/A

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

=====
With best regards / mit freundlichen Grüßen / よろしくお願いします。
Daisuke Butsuda / 佛田 大輔
Tel. +81(45)474-1923 Ext. 72-61-644526


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
asked Oct 7, 2016 in defcore-committee by Butsuda,_Daisuke (140 points)  
...