[Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!

Miller, Frank Frank.Miller at windriver.com
Thu May 28 17:06:30 UTC 2020


Thanks Zhipeng.

Good to see progress on IPv6.
Waiting for 10 minutes for pods to recover isn't a good result.  Is there a LP open on this issue?  Which pods are not ready? What can you tell us about this 10 minute outage?

Frank

-----Original Message-----
From: Liu, ZhipengS <zhipengs.liu at intel.com> 
Sent: Thursday, May 28, 2020 5:06 AM
To: Miller, Frank <Frank.Miller at windriver.com>; starlingx-discuss at lists.starlingx.io; Jascanu, Nicolae <nicolae.jascanu at intel.com>
Subject: RE: [Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!

Hi Frank,

Nicolae already added test case description. Thanks Nicolae!

I also did below test on AIO-DX virtual setup, exactly according to your mentioned steps.
No issue found, but just need to wait for around 10 min before all pods are ready again after reboot.

For ipv6 issue, I have submitted new patch for it since dynamic override for database config did not work.
 https://review.opendev.org/#/c/731461/
 https://review.opendev.org/#/c/731470/

Thanks!
Zhipeng

-----Original Message-----
From: Miller, Frank <Frank.Miller at windriver.com>
Sent: 2020年5月27日 22:43
To: Liu, ZhipengS <zhipengs.liu at intel.com>; starlingx-discuss at lists.starlingx.io; Jascanu, Nicolae <nicolae.jascanu at intel.com>
Subject: RE: [Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!

Zhipeng:

Thanks for the info.  You have provided the # of testcases but not what those testcase do.  Where can I find a description of what the OpenStack testcases do?

For the controller reset testcases I'd like to see the test result for the following:
Is openstack usable during the following scenarios on AIO-DX and on Standard configurations:
- Lock/unlock of standby controller
- reset (ie: reboot -f) of the standby controller
- reset (ie: reboot -f) of the active controller
- reapply of stx-openstack after the above scenarios

Frank

-----Original Message-----
From: Liu, ZhipengS <zhipengs.liu at intel.com>
Sent: Wednesday, May 27, 2020 9:15 AM
To: Miller, Frank <Frank.Miller at windriver.com>; starlingx-discuss at lists.starlingx.io; Jascanu, Nicolae <nicolae.jascanu at intel.com>
Subject: RE: [Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!

Hi Frank,

We have done below tests.
1) Sanity tests by Nicolae.
AIO - Simplex
Setup                                    04 TCs [PASS]
Provisioning                       01 TCs [PASS]
Sanity OpenStack             49 TCs [PASS]
Sanity Platform                 07 TCs [PASS]

TOTAL: [ 61 TCs ]

AIO - Duplex 
Setup                                    04 TCs [PASS]
Provisioning                       01 TCs [PASS]
Sanity OpenStack             52 TCs [PASS]
Sanity Platform                 07 TCs [PASS]

TOTAL: [ 64 TCs ]

Standard - Local Storage (2+2)
Setup                                    04 TCs [PASS]
Provisioning                       01 TCs [PASS]
Sanity OpenStack             52 TCs [PASS]
Sanity Platform                 08 TCs [PASS]

TOTAL: [ 65 TCs ]

Standard External - Dedicated Storage (2+2+2)
Setup                                    04 TCs [PASS]
Provisioning                       01 TCs [PASS]
Sanity OpenStack             52 TCs [PASS]
Sanity Platform                 09 TCs [PASS]

TOTAL: [ 66 TCs ]

2) NFV scenario test by me
    on duplex/multi standard virtual setup
          duplex bare metal setup
===== Setup =================================================================================================================================
2020-05-14 02:30:05.524  Create flavor small  ........................................ [OKAY]
2020-05-14 02:30:05.524  Create flavor small_ephemeral  .............................. [OKAY]
2020-05-14 02:30:05.524  Create flavor small_swap  ................................... [OKAY]
2020-05-14 02:30:05.524  Create flavor small_ephemeral_swap  ......................... [OKAY]
2020-05-14 02:30:05.524  Create flavor medium  ....................................... [OKAY]
2020-05-14 02:30:05.524  Create flavor medium_ephemeral  ............................. [OKAY]
2020-05-14 02:30:05.524  Create flavor medium_swap  .................................. [OKAY]
2020-05-14 02:30:05.524  Create flavor medium_ephemeral_swap  ........................ [OKAY]
2020-05-14 02:30:05.653  Create image cirros  ........................................ [OKAY]
2020-05-14 02:30:05.695  Create volume cirros  ....................................... [OKAY]
2020-05-14 02:30:05.695  Create volume cirros-ephemeral  ............................. [OKAY]
2020-05-14 02:30:05.695  Create volume cirros-swap  .................................. [OKAY]
2020-05-14 02:30:05.695  Create volume cirros-ephemeral-swap  ........................ [OKAY]
2020-05-14 02:30:05.695  Create volume empty_volume  ................................. [OKAY]
2020-05-14 02:30:05.786  Create network internal  .................................... [OKAY]
2020-05-14 02:30:06.158  Create network external  .................................... [OKAY]
2020-05-14 02:30:06.772  Create subnet internal  ..................................... [OKAY]
2020-05-14 02:30:07.661  Create subnet external  ..................................... [OKAY]
2020-05-14 02:30:08.553  Create instance cirros-1  ................................... [OKAY]
2020-05-14 02:30:29.918  Create instance cirros-ephemeral-1  ......................... [OKAY]
2020-05-14 02:30:43.160  Create instance cirros-swap-1  .............................. [OKAY]
2020-05-14 02:30:56.101  Create instance cirros-ephemeral-swap-1  .................... [OKAY]
2020-05-14 02:31:09.077  Create instance cirros-image-1  ............................. [OKAY]
2020-05-14 02:31:21.241  Create instance cirros-image-with-volumes-1  ................ [OKAY] =============================================================================================================================================
===== Test Iteration 0 (single-execution) ===================================================================================================
2020-05-14 02:33:04.172  Test Instance-Pause  ........................................ [OKAY]  (2020-05-14 02:33:18.078 Δ=0:00:12.870)
2020-05-14 02:33:35.073  Test Instance-Unpause  ...................................... [OKAY]  (2020-05-14 02:33:41.608 Δ=0:00:05.866)
2020-05-14 02:33:53.049  Test Instance-Suspend  ...................................... [OKAY]  (2020-05-14 02:33:59.546 Δ=0:00:05.792)
2020-05-14 02:34:11.103  Test Instance-Resume  ....................................... [OKAY]  (2020-05-14 02:34:17.756 Δ=0:00:05.937)
2020-05-14 02:34:29.269  Test Instance-Reboot (soft)  ................................ [OKAY]  (2020-05-14 02:36:45.923 Δ=0:02:15.748)
2020-05-14 02:37:02.160  Test Instance-Reboot (hard)  ................................ [OKAY]  (2020-05-14 02:37:14.504 Δ=0:00:11.704)
2020-05-14 02:37:30.673  Test Instance-Stop  ......................................... [OKAY]  (2020-05-14 02:38:44.543 Δ=0:01:13.220)
2020-05-14 02:39:00.481  Test Instance-Start  ........................................ [OKAY]  (2020-05-14 02:39:07.198 Δ=0:00:06.068)
2020-05-14 02:39:18.578  Test Instance-Live-Migrate  ................................. [OKAY]  (2020-05-14 02:39:41.692 Δ=0:00:22.306)
2020-05-14 02:39:57.927  Test Instance-Cold-Migrate  ................................. [OKAY]  (2020-05-14 02:41:22.720 Δ=0:01:24.179)
2020-05-14 02:41:38.995  Test Instance-Cold-Migrate-Confirm  ......................... [OKAY]  (2020-05-14 02:41:45.441 Δ=0:00:05.884)
2020-05-14 02:41:57.108  Test Instance-Cold-Migrate-Revert  .......................... [OKAY]  (2020-05-14 02:43:36.381 Δ=0:00:21.637)
2020-05-14 02:43:52.320  Test Instance-Resize  ....................................... [OKAY]  (2020-05-14 02:45:16.409 Δ=0:01:22.812)
2020-05-14 02:45:32.723  Test Instance-Resize-Confirm  ............................... [OKAY]  (2020-05-14 02:45:39.119 Δ=0:00:05.777)
2020-05-14 02:45:50.437  Test Instance-Resize-Revert  ................................ [OKAY]  (2020-05-14 02:47:30.175 Δ=0:00:21.748)
2020-05-14 02:47:46.230  Test Instance-Rebuild  ...................................... [OKAY]  (2020-05-14 02:48:59.762 Δ=0:01:12.980)
Total-Tests: 16     Execution-Time: 0:16:11.676

3) Another 2 test
    a) Using IPv6
         It can pass with workaround now.  I need one more fix for it.
         In my previous patch https://review.opendev.org/#/c/716524 (merged), I dynamically override below 
            config_override: |
                [mysqld]
                bind_address=::
         However, it did not work now. From log,  it shows error "OpenStack-Helm Mariadb - INFO - b'error: Found option without preceding group in config file: /etc/mysql/conf.d/20-override.cnf at line: 1'"
         I tried many methods, but could not remove the first line in 20-override.cnf
                mysql at mariadb-server-0:/etc/mysql/conf.d$ cat 20-override.cnf
                |-     
                [mysqld]
                bind_address=::
        I can only add it in manifest.yaml as a static override like below.
               values:
                  conf:
                      database:
                          config_override: |
                              [mysqld]
                              bind_address=::
            
    b) Reset of controllers and check status of OpenStack while a controller is rebooting.
         I have tested it and pass on simplex.
         For duplex, I have a setup issue in my side.
         @Jascanu, Nicolae  Could you help me on it for duplex test, if you have time today. Thanks!

Zhipeng



-----Original Message-----
From: Miller, Frank <Frank.Miller at windriver.com>
Sent: 2020年5月26日 21:13
To: Liu, ZhipengS <zhipengs.liu at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: RE: [Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!

Zhipeng:

Can you publish the list of tests that have been run for openstack?

Also has openstack been tested for the following scenarios:
1) Using IPv6
2) Reset of controllers and check status of openstack while a controller is rebooting?  

Frank

-----Original Message-----
From: Liu, ZhipengS <zhipengs.liu at intel.com>
Sent: Monday, May 25, 2020 3:14 AM
To: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!

Hi all,

We have passed all sanity test on all setup. Thanks Nicolae!!
We also built out OpenStack service images from layered build environment.

Please help to review and push below patches to be merged, thanks!
https://review.opendev.org/#/q/topic:for_ussuri+(status:open+OR+status)

BRs
Zhipeng 

-----Original Message-----
From: Liu, ZhipengS
Sent: 2020年5月14日 16:49
To: 'Saul Wold' <sgw at linux.intel.com>; 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>
Subject: RE: [Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!

Hi all, 

Call for patch review again!
https://review.opendev.org/#/q/topic:for_ussuri+(status:open+OR+status)

Thanks!
Zhipeng

-----Original Message-----
From: Liu, ZhipengS
Sent: 2020年5月9日 8:38
To: Saul Wold <sgw at linux.intel.com>; starlingx-discuss at lists.starlingx.io
Subject: RE: [Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!

Agree!

-----Original Message-----
From: Saul Wold <sgw at linux.intel.com>
Sent: 2020年5月9日 0:29
To: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call for patch review!!

I would strengthen that to no changes until we get Green Sanity other than what's required to make them Green.

Full Stop!

Sau!


On 5/8/20 9:05 AM, Miller, Frank wrote:
> Until we can get sanity passing for several days in a row I strongly 
> suggest we do not allow any further changes into the load related to 
> OpenStack.  Folks can continue with reviews but let’s hold off 
> allowing merges related to a new OpenStack version.
> 
> Frank
> 
> *From:*Liu, ZhipengS <zhipengs.liu at intel.com>
> *Sent:* Friday, May 08, 2020 11:59 AM
> *To:* starlingx-discuss <starlingx-discuss at lists.starlingx.io>
> *Cc:* YU CHENGDE <yu.chengde at 99cloud.net>; Penney, Don 
> <Don.Penney at windriver.com>
> *Subject:* [Starlingx-discuss] [OpenStack Ussuri Upgrade Task] Call 
> for patch review!!
> 
> Hi all,
> 
> Please help to review OpenStack Ussuri upgrade patches.
> 
> Our target is to get all below patches merged by end of next week.
> 
> https://review.opendev.org/#/q/topic:for_ussuri+(status:open+OR+status
> :merged)
> 
> During OpenStack upgrade for StarlingX, we have to move python2.7 to
> python3.6 for OpenStack services as ussuri release only support python3.
> 
> We also rebased openstack-helm/helm-infra to latest version.
> 
> Engineering build test status.
> 
>  1. nfv_scenario_tests PASS on simplex/duplex/multi virtual setup.
>  2. nfv_scenario_tests PASS on simplex bare metal setup.
>  3. Sanity test is ongoing.   Duplex/standard virtual setup test PASS.
> 
> Thanks!
> 
> Zhipeng
> 
> 
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> 

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


More information about the Starlingx-discuss mailing list