settingsLogin | Registersettings

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

0 votes

1.) Your name: Craig Peters
2.) Your email: cpeters@mirantis.com
3.) Reporting on behalf of Company/Organization: Mirantis, Inc
4.) Name and version (if applicable) of the product you tested: Mirantis
OpenStack 9.0
5.) Version of OpenStack the product uses: Mitaka
6.) Link to RefStack results for this product:
https://www.openstack.org/marketplace/distros/distribution/mirantis/mirantis-openstack
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 (only with Ubuntu 14.04 given
the way the ansible scripts are structured)
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.
For Ubuntu 15.04 and 16.04: The scripts assume that python is installed,
so I got an error during the task installing database
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?
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? No, did not try
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?
9.) Workload 3: NFV (URL TBD)
A.) Did the workload run successfully? No, did not try
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?
--
Craig Peters | Director of Product Management | www.mirantis.com
d: +1 650 490 4324 | m: +1 925 639 0804
e: cpeters@mirantis.com | skype: craig.l.peters


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 Craig_Peters (240 points)   2

5 Responses

0 votes

1.) Your name: Mark T. Voelker and Xiangfei Zhu
2.) Your email: mvoelker@vmware.com and xiangfeiz@vmware.com
3.) Reporting on behalf of Company/Organization: VMware, Inc
4.) Name and version (if applicable) of the product you tested: VMware Integrated OpenStack 3.0
5.) Version of OpenStack the product uses: Mitaka
6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/681eca53-cc28-4d04-8a43-2d6059b694da
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 (with the trivial patch submitted here: https://review.openstack.org/#/c/383923/ )

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 [database : command] ******************************************************
fatal: [192.168.112.201]: FAILED! => {"changed": true, "cmd": "parted -s \"/dev/sdb\" mklabel msdos", "delta": "0:00:00.025755", "end": "2016-10-07 20:40:29.295529", "failed": true, "rc": 1, "start": "2016-10-07 20:40:29.269774", "stderr": "", "stdout": "Error: Could not stat device /dev/sdb - No such file or directory.", "stdout_lines": ["Error: Could not stat device /dev/sdb - No such file or directory."], "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.

The Ubuntu 14.04 image I was using was configured with an lsiLogic SCSI adapter by default. When a volume is attached to an instance booted from the image and later a Cinder volume is attached, the lsiLogic adapter needs to be rescanned before the newly-attached Cinder volume is recognized (this may not be needed for all paravirt adapter types). Rescanning the bus is quite simple to do: you simply run the rescan-scsi-bus script included in the scsitools package. Rescanning the bus should also be harmless on all other adapter types I’ve encountered, so I submitted a four-line patch to the Ansible playbooks to ensure scsitools is installed and run the rescan-scsi-bus tool.

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?

Trivial…I’ve already posted a ~4 line patch to make it work better across adapter/OS/hypervisor types at: https://review.openstack.org/#/c/383923

At Your Service,

Mark T. Voelker


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Oct 7, 2016 by Mark_Voelker (4,000 points)   2 3
0 votes

1.) Your name: Rohit Agarwalla
2.) Your email: roagarwa@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


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Oct 8, 2016 by Rohit_Agarwalla_(roa (340 points)   1
0 votes

1.) Your name: Fred Li
2.) Your email: liyongle@huawei.com
3.) Reporting on behalf of Company/Organization: Huawei Technologies Co., Ltd.
4.) Name and version (if applicable) of the product you tested: FusionSphere OpenStack
5.) Version of OpenStack the product uses: Juno
6.) Link to RefStack results for this product: https://www.openstack.org/marketplace/distros/distribution/huawei/fusionsphere-openstack
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.
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
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? 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.
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
9.) Workload 3: NFV (URL TBD)
A.) Did the workload run successfully? No. I didn't try it.
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

Fred (李永乐)

本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中
的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Oct 8, 2016 by Liyongle_(Fred) (320 points)   1
0 votes

1.) Your name: Gema Gomez

2.) Your email: gema.gomez-solano@linaro.org

3.) Reporting on behalf of Company/Organization: Linaro

4.) Name and version (if applicable) of the product you tested:
Linaro Developer Cloud (ARM64)

5.) Version of OpenStack the product uses: Newton on Debian (ARM64)

6.) Link to RefStack results for this product: TBD

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?

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? 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.
It deployed the cluster properly but the containers failed.

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.

The containers are x86 based, we would need to use aarch64 containers
for them to work (like the coreos image used).

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?

Containers for aarch64 would need to be created / used, instead of the
x86 ones.

9.) Workload 3: NFV (URL TBD)
A.) Did the workload run successfully? Haven't tried yet.
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?

Cheers,
Gema

--
Gema Gomez-Solano
Tech Lead, SDI
Linaro Ltd
IRC: gema@#linaro on irc.freenode.net


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Oct 9, 2016 by gema.gomez-solano_at (400 points)  
0 votes

Updating RefStack results.

On 09/10/16 17:20, Gema Gomez wrote:
1.) Your name: Gema Gomez

2.) Your email: gema.gomez-solano@linaro.org

3.) Reporting on behalf of Company/Organization: Linaro

4.) Name and version (if applicable) of the product you tested:
Linaro Developer Cloud (ARM64)

5.) Version of OpenStack the product uses: Newton on Debian (ARM64)

6.) Link to RefStack results for this product:
https://refstack.openstack.org/#/results/dfd3f68e-7d5a-4b60-b18c-b571d9ae41d3

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?

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? 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.
It deployed the cluster properly but the containers failed.

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.

The containers are x86 based, we would need to use aarch64 containers
for them to work (like the coreos image used).

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?

Containers for aarch64 would need to be created / used, instead of the
x86 ones.

9.) Workload 3: NFV (URL TBD)
A.) Did the workload run successfully? Haven't tried yet.
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?

Cheers,
Gema

--
Gema Gomez-Solano
Tech Lead, SDI
Linaro Ltd
IRC: gema@#linaro on irc.freenode.net


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Oct 19, 2016 by gema.gomez-solano_at (400 points)  
...