I am going to share something that might be off the topic a bit.

Yesterday, I was pulled to the #openstack-infra channel to participant a 
discussion, which is related to the atomic image download in Magnum. It looks 
the infra team is not satisfied with the large image size. In particular, they 
need to double the timeout to accommodate the job [1] [2], which made them 
unhappy. Is there a way to reduce the image size? Or even better, is it 
possible to build the image locally instead of downloading it?

[1] https://review.openstack.org/#/c/242742/
[2] https://review.openstack.org/#/c/244847/

Best regards,
Hongbin

From: Kai Qiang Wu [mailto:wk...@cn.ibm.com]
Sent: November-13-15 12:33 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate.


Right now, we seems can not reduce devstack runtime. ANd @Ton, yes, download 
image time seems OK in jenkins job, it found about 4~5 mins

But bay-creation time is interesting topic, it seems something related with 
heat or VM setup time consumption. But needs some investigation.



Thanks

Best Wishes,
--------------------------------------------------------------------------------
Kai Qiang Wu (吴开强 Kennan)
IBM China System and Technology Lab, Beijing

E-mail: wk...@cn.ibm.com<mailto:wk...@cn.ibm.com>
Tel: 86-10-82451647
Address: Building 28(Ring Building), ZhongGuanCun Software Park,
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193
--------------------------------------------------------------------------------
Follow your heart. You are miracle!

[Inactive hide details for "Ton Ngo" ---13/11/2015 01:13:47 pm---Thanks Eli for 
the analysis.  I notice that the time to downloa]"Ton Ngo" ---13/11/2015 
01:13:47 pm---Thanks Eli for the analysis. I notice that the time to download 
the image is only around 1:15 mins

From: "Ton Ngo" <t...@us.ibm.com<mailto:t...@us.ibm.com>>
To: "OpenStack Development Mailing List \(not for usage questions\)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: 13/11/2015 01:13 pm
Subject: Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing on 
gate.

________________________________



Thanks Eli for the analysis. I notice that the time to download the image is 
only around 1:15 mins out of some 21 mins to set up devstack. So it seems 
trying to reduce the size of the image won't make a significant improvement in 
the devstack time. I wonder how the image size affects the VM creation time for 
the cluster. If we can look at the Heat event stream, we might get an idea.
Ton,


[Inactive hide details for Egor Guz ---11/12/2015 05:25:15 PM---Eli, First of 
all I would like to say thank you for your effort]Egor Guz ---11/12/2015 
05:25:15 PM---Eli, First of all I would like to say thank you for your effort 
(I never seen so many path sets ;)),

From: Egor Guz <e...@walmartlabs.com<mailto:e...@walmartlabs.com>>
To: 
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: 11/12/2015 05:25 PM
Subject: Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing on 
gate.
________________________________



Eli,

First of all I would like to say thank you for your effort (I never seen so 
many path sets ;)), but I don’t think we should remove “tls_disabled=True” 
tests from gates now (maybe in L).
It’s still vey commonly used feature and backup plan if TLS doesn’t work for 
some reasons.

I think it’s good idea to group tests per pipeline we should definitely follow 
it.

―
Egor

From: "Qiao,Liyong" <liyong.q...@intel.com<mailto:liyong.q...@intel.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, November 11, 2015 at 23:02
To: 
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.

hello all:

I will update some Magnum functional testing status, functional/integration 
testing
is important to us, since we change/modify the Heat template rapidly, we need to
verify the modification is correct, so we need to cover all templates Magnum 
has.
and currently we only has k8s testing(only test with atomic image), we need to
add more, like swarm(WIP), mesos(under plan), also , we may need to support COS 
image.
lots of work need to be done.

for the functional testing time costing, we discussed during the Tokyo summit,
Adrian expected that we can reduce the timing cost to 20min.

I did some analyses on the functional/integrated testing on gate pipeline.
the stages will be follows:
take k8s functional testing for example, we did follow testing case:

1) baymodel creation
2) bay(tls_disabled=True) creation/deletion
3) bay(tls_disabled=False) creation to testing k8s api and delete it after 
testing.

for each stage, the time costing is follows:

*   devstack prepare: 5-6 mins
*   Running devstack: 15 mins(include downloading atomic image)
*   1) and 2) 15 mins
*   3) 15 +3 mins

totally about 60 mins currently a example is 1h 05m 57s
see 
http://logs.openstack.org/10/243910/1/check/gate-functional-dsvm-magnum-k8s/5e61039/console.html
for all time stamps.

I don't think it is possible to reduce time to 20 mins, since devstack setup 
will take 20 mins already.

To reduce time, I suggest to only create 1 bay each pipeline and do vary kinds 
of testing
on this bay, if want to test some specify bay (for example, network_driver 
etc), create
a new pipeline .

So, I think we can delete 2), since 3) will do similar things(create/delete), 
the different is
3) use tls_disabled=False. what do you think ?
see https://review.openstack.org/244378 for the time costing, will reduce to 45 
min (48m 50s in the example.)

=================================
For other related functional testing works:
I 'v done the split of functional testing per COE, we have pipeline as:

*   gate-functional-dsvm-magnum-api 30 mins
*   gate-functional-dsvm-magnum-k8s 60 mins

And for swam pipeline, patches is done, under reviewing now(works fine on gate)
https://review.openstack.org/244391
https://review.openstack.org/226125

========================

--
BR, Eli(Li Yong)Qiao
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to