settingsLogin | Registersettings

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

0 votes

1.) Your name: Daniela Ebert
2.) Your email: d.ebert@t-systems.comd.ebert@t-systems.com
3.) Reporting on behalf of Company/Organization: T-Systems International GmbH
4.) Name and version (if applicable) of the product you tested: Open Telekom Cloud based on Huawei FusionSphere OpenStack
5.) Version of OpenStack the product uses: Juno
6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/206476ee-a365-4222-9e9d-3bc8275bc6c0 (2016-01 COMPUTE)
7.) Workload 1: LAMP Stack with Ansible (https://github.com/openstack/osops-tools-contrib)
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.
(1) Database VM trying to install scsitools (without a prior apt-get update) fails
(2) Flavor Name from Config File not referenced in roles/apply/tasks/main.yml
(3) SSH to VMs failed (ssh connection reset)
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.
(1) we just injected "packageupgrade: true" into roles/apply/templates/userdata.j2
(2) Changed "roles/apply/tasks/main.yml":
OLD: flavor: "{{ openstack
flavors[0].id }}"
NEW: flavor: "{{ appenv.flavorname }}"
(3) Subnet should be created by neutron (or postprocessed with neutron to inject a gateway_ip, if created by API)

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? Didn't 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.
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? 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


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
asked Oct 14, 2016 in defcore-committee by D.Ebert_at_t-systems (120 points)  

2 Responses

0 votes
    (1) Database VM trying to install scsitools (without a prior apt-get update) fails

Ah, so the apt-cache wasn’t initialized here because it was a newly booted VM I imagine—good catch. This would be easy to deal with in the ansible code itself I’d think:

https://review.openstack.org/#/c/386678/

At Your Service,

Mark T. Voelker

On Oct 14, 2016, at 6:53 AM, D.Ebert@t-systems.com wrote:


1.) Your name: Daniela Ebert
2.) Your email: d.ebert@t-systems.com
3.) Reporting on behalf of Company/Organization: T-Systems International GmbH
4.) Name and version (if applicable) of the product you tested: Open Telekom Cloud based on Huawei FusionSphere OpenStack
5.) Version of OpenStack the product uses: Juno
6.) Link to RefStack results for this product: https://refstack.openstack.org/#/results/206476ee-a365-4222-9e9d-3bc8275bc6c0 (2016-01 COMPUTE)
7.) Workload 1: LAMP Stack with Ansible (https://github.com/openstack/osops-tools-contrib)
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.
(1) Database VM trying to install scsitools (without a prior apt-get update) fails
(2) Flavor Name from Config File not referenced in roles/apply/tasks/main.yml
(3) SSH to VMs failed (ssh connection reset)
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.
(1) we just injected “packageupgrade: true” into roles/apply/templates/userdata.j2
(2) Changed “roles/apply/tasks/main.yml”:
OLD: flavor: "{{ openstack
flavors[0].id }}"
NEW: flavor: "{{ appenv.flavorname }}"
(3) Subnet should be created by neutron (or postprocessed with neutron to inject a gateway_ip, if created by API)

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? Didn’t 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.
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? 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



Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


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

1.) Your name: Elise Eiden

2.) Your email: ee550x@att.com

3.) Reporting on behalf of Company/Organization: AT&T

4.) Name and version (if applicable) of the product you tested: AT&T Integrated Cloud (AIC) 3.0.1

5.) Version of OpenStack the product uses: Kilo

6.) Link to RefStack results for this product: in-progress

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

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? In-progress

Elise Eiden
Sr Specialist Applications Developer
AT&T Integrated Cloud | Call<tel:+12062897389> | Q<qto://talk/ee550x> | Skype<sip:ee550x@att.com> | ee550x@att.com | St. Louis, MO

AT&T Proprietary (Internal Use Only) -- Not for use or disclosure outside the AT&T companies except under written agreement


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Oct 14, 2016 by EIDEN,_ELISE_A (140 points)  
...