Re: [Starlingx-discuss] [ Test ] meeting notes for 09/10
Agenda for 09/10 Attendees: Elio, Cristopher, Fernando, JC, Jose, Maria P, JP, Richo, Yang, Ada 1. Sanity status - Cristopher Still green. After the change in the repos we found a small issue, but is fixed now. Issues: app port unreachable from external - https://bugs.launchpad.net/starlingx/+bug/1841802 - still not fixed. After host-swact completed, unexpected swact occurred due to ceph error - https://bugs.launchpad.net/starlingx/+bug/1840176 - intermittent issue, fixed now. 2. Unified sanity - JC Slides: https://drive.google.com/file/d/1hBfWCb4Rn_SmteeqjWSpgluzDH192sHv/view?usp=s... What we have today: 4 configs (SX, DX, Standard local storage, standard external storage) Bare metal and virtual, no proxy, proxy and local registry deployments. Sanity for platform (containers) and OpenStack Proposal: WR and Intel running two configs each. Are we considering ping and ssh tests? those are included in the pytest suite We will use only pytest for running sanity testing. Three tests from robot are not in the pytest suite. Resize are in the regression repo. Rebuild to be added Reboot could be added into the nova_actions test. Still having problems with the natbox setup - please send the question to the mailing list. Please also add this info to the documentation. Not a date defined yet due to the problems with the infrastructure, but next week will have more visibility. For reporting: Wind River will send their results to Intel and the report will be consolidated and sent out (in the mean time we do automatic reporting). 3. stx.3.0 - release and feature testing plans - Ada Schedule updated - https://docs.google.com/spreadsheets/d/16JxIbfX7hQBjyPkaxYYuPij3XwTWDHMsB-GR... Actions: Containerized Openstack clients - Yang to ask Frank if implicit testing (sanity) is enough - update to suite is required. Fault Containerization - Jose to ask if implicit testing is enough - maybe a small regression for covering this (Horizon should be manually verified) Upversion Openstack to Train - JC to get in contact to Bruce and ask for the plan. Redfish Support - Ada to check on this one Performance Testing/Measurement Framework - Elio to check the deliverable expected. For regression - test plan is to run automated testing and select a subset of the new tests created for features for 2.0 as the manual test plan. Ada to work on the list and make it public. 4. Opens - All Yang is taking Numan's position into StarlingX. Thanks Yang!
Upversion Openstack to Train - JC to get in contact to Bruce and ask for the plan.
Hi JC. I don't know enough to have a plan for this. What testing do you think is needed? What did we do for 2.0? Distro.openstack folks - what do we think needs to be done here? brucej -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales@intel.com] Sent: Thursday, September 12, 2019 10:01 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] meeting notes for 09/10 Agenda for 09/10 Attendees: Elio, Cristopher, Fernando, JC, Jose, Maria P, JP, Richo, Yang, Ada 1. Sanity status - Cristopher Still green. After the change in the repos we found a small issue, but is fixed now. Issues: app port unreachable from external - https://bugs.launchpad.net/starlingx/+bug/1841802 - still not fixed. After host-swact completed, unexpected swact occurred due to ceph error - https://bugs.launchpad.net/starlingx/+bug/1840176 - intermittent issue, fixed now. 2. Unified sanity - JC Slides: https://drive.google.com/file/d/1hBfWCb4Rn_SmteeqjWSpgluzDH192sHv/view?usp=s... What we have today: 4 configs (SX, DX, Standard local storage, standard external storage) Bare metal and virtual, no proxy, proxy and local registry deployments. Sanity for platform (containers) and OpenStack Proposal: WR and Intel running two configs each. Are we considering ping and ssh tests? those are included in the pytest suite We will use only pytest for running sanity testing. Three tests from robot are not in the pytest suite. Resize are in the regression repo. Rebuild to be added Reboot could be added into the nova_actions test. Still having problems with the natbox setup - please send the question to the mailing list. Please also add this info to the documentation. Not a date defined yet due to the problems with the infrastructure, but next week will have more visibility. For reporting: Wind River will send their results to Intel and the report will be consolidated and sent out (in the mean time we do automatic reporting). 3. stx.3.0 - release and feature testing plans - Ada Schedule updated - https://docs.google.com/spreadsheets/d/16JxIbfX7hQBjyPkaxYYuPij3XwTWDHMsB-GR... Actions: Containerized Openstack clients - Yang to ask Frank if implicit testing (sanity) is enough - update to suite is required. Fault Containerization - Jose to ask if implicit testing is enough - maybe a small regression for covering this (Horizon should be manually verified) Upversion Openstack to Train - JC to get in contact to Bruce and ask for the plan. Redfish Support - Ada to check on this one Performance Testing/Measurement Framework - Elio to check the deliverable expected. For regression - test plan is to run automated testing and select a subset of the new tests created for features for 2.0 as the manual test plan. Ada to work on the list and make it public. 4. Opens - All Yang is taking Numan's position into StarlingX. Thanks Yang! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Thu, Sep 12, 2019 at 12:51 PM Jones, Bruce E <bruce.e.jones@intel.com> wrote:
Upversion Openstack to Train - JC to get in contact to Bruce and ask for the plan. Hi JC. I don't know enough to have a plan for this. What testing do you think is needed? What did we do for 2.0?
Distro.openstack folks - what do we think needs to be done here?
What we discussed earlier in the week: * build a manifest file pointing to master OpenStack repos * perform as much of the build process required to get all of the OpenStack bits (this may no longer be a full build?) * run sanity * run other tests TBD I would think that last point requires someone who knows what tests are likely to be impacted by OpenStack changes, specifically things that are new since Stein. The high-level summaries of tha are being written now, but with OpenStack's general policy of writing release notes with code there already are detailed release notes in every repo to scan for changes. dt -- Dean Troyer dtroyer@gmail.com
It's the test plan (the "run other tests TBD") where I need help. I don't know how to scan the OpenStack release notes and how to tell which changes might impact us. I'll write up the story/tasks for the overall plan today. Then I'll be looking for volunteers to do the work. brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Thursday, September 12, 2019 11:05 AM To: Jones, Bruce E <bruce.e.jones@intel.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] meeting notes for 09/10 On Thu, Sep 12, 2019 at 12:51 PM Jones, Bruce E <bruce.e.jones@intel.com> wrote:
Upversion Openstack to Train - JC to get in contact to Bruce and ask for the plan. Hi JC. I don't know enough to have a plan for this. What testing do you think is needed? What did we do for 2.0?
Distro.openstack folks - what do we think needs to be done here?
What we discussed earlier in the week: * build a manifest file pointing to master OpenStack repos * perform as much of the build process required to get all of the OpenStack bits (this may no longer be a full build?) * run sanity * run other tests TBD I would think that last point requires someone who knows what tests are likely to be impacted by OpenStack changes, specifically things that are new since Stein. The high-level summaries of tha are being written now, but with OpenStack's general policy of writing release notes with code there already are detailed release notes in every repo to scan for changes. dt -- Dean Troyer dtroyer@gmail.com
Hello Bruce, I reviewed the last test plan for OpenStack patch elimination for STX 2.0: https://docs.google.com/spreadsheets/d/15us6HWgcb0dmHHZe2SyOR_UI5BvVpoU8TCST... The features I tested were: - Nova: SR-IOV Functionality - Nova: PT Functionality - Nova: vSwitch Affinity - Nova: DB Purge - Nova: PCI Interrupt Affinity - Neutron: Network Segmentation Range Management - Glance: Cache raw Extension - Horizon: Custom Confirmation Messages I don't know if same features will be tested for STX 3.0, will them? Do you have a general overview, or datasheet link of the features to be testes for patch elimination in SXT 3.0? Is there any meeting where I can ask for it? Regards. Juan Carlos Alonso -----Original Message----- From: Jones, Bruce E <bruce.e.jones@intel.com> Sent: Thursday, September 12, 2019 12:51 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] meeting notes for 09/10
Upversion Openstack to Train - JC to get in contact to Bruce and ask for the plan.
Hi JC. I don't know enough to have a plan for this. What testing do you think is needed? What did we do for 2.0? Distro.openstack folks - what do we think needs to be done here? brucej -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales@intel.com] Sent: Thursday, September 12, 2019 10:01 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] meeting notes for 09/10 Agenda for 09/10 Attendees: Elio, Cristopher, Fernando, JC, Jose, Maria P, JP, Richo, Yang, Ada 1. Sanity status - Cristopher Still green. After the change in the repos we found a small issue, but is fixed now. Issues: app port unreachable from external - https://bugs.launchpad.net/starlingx/+bug/1841802 - still not fixed. After host-swact completed, unexpected swact occurred due to ceph error - https://bugs.launchpad.net/starlingx/+bug/1840176 - intermittent issue, fixed now. 2. Unified sanity - JC Slides: https://drive.google.com/file/d/1hBfWCb4Rn_SmteeqjWSpgluzDH192sHv/view?usp=s... What we have today: 4 configs (SX, DX, Standard local storage, standard external storage) Bare metal and virtual, no proxy, proxy and local registry deployments. Sanity for platform (containers) and OpenStack Proposal: WR and Intel running two configs each. Are we considering ping and ssh tests? those are included in the pytest suite We will use only pytest for running sanity testing. Three tests from robot are not in the pytest suite. Resize are in the regression repo. Rebuild to be added Reboot could be added into the nova_actions test. Still having problems with the natbox setup - please send the question to the mailing list. Please also add this info to the documentation. Not a date defined yet due to the problems with the infrastructure, but next week will have more visibility. For reporting: Wind River will send their results to Intel and the report will be consolidated and sent out (in the mean time we do automatic reporting). 3. stx.3.0 - release and feature testing plans - Ada Schedule updated - https://docs.google.com/spreadsheets/d/16JxIbfX7hQBjyPkaxYYuPij3XwTWDHMsB-GR... Actions: Containerized Openstack clients - Yang to ask Frank if implicit testing (sanity) is enough - update to suite is required. Fault Containerization - Jose to ask if implicit testing is enough - maybe a small regression for covering this (Horizon should be manually verified) Upversion Openstack to Train - JC to get in contact to Bruce and ask for the plan. Redfish Support - Ada to check on this one Performance Testing/Measurement Framework - Elio to check the deliverable expected. For regression - test plan is to run automated testing and select a subset of the new tests created for features for 2.0 as the manual test plan. Ada to work on the list and make it public. 4. Opens - All Yang is taking Numan's position into StarlingX. Thanks Yang! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi JC. Please join the distro.openstack call tomorrow where this topic is the first thing on the agenda. -----Original Message----- From: Alonso, Juan Carlos Sent: Monday, September 23, 2019 11:35 AM To: Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [ Test ] meeting notes for 09/10 Hello Bruce, I reviewed the last test plan for OpenStack patch elimination for STX 2.0: https://docs.google.com/spreadsheets/d/15us6HWgcb0dmHHZe2SyOR_UI5BvVpoU8TCST... The features I tested were: - Nova: SR-IOV Functionality - Nova: PT Functionality - Nova: vSwitch Affinity - Nova: DB Purge - Nova: PCI Interrupt Affinity - Neutron: Network Segmentation Range Management - Glance: Cache raw Extension - Horizon: Custom Confirmation Messages I don't know if same features will be tested for STX 3.0, will them? Do you have a general overview, or datasheet link of the features to be testes for patch elimination in SXT 3.0? Is there any meeting where I can ask for it? Regards. Juan Carlos Alonso -----Original Message----- From: Jones, Bruce E <bruce.e.jones@intel.com> Sent: Thursday, September 12, 2019 12:51 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] meeting notes for 09/10
Upversion Openstack to Train - JC to get in contact to Bruce and ask for the plan.
Hi JC. I don't know enough to have a plan for this. What testing do you think is needed? What did we do for 2.0? Distro.openstack folks - what do we think needs to be done here? brucej -----Original Message----- From: Cabrales, Ada [mailto:ada.cabrales@intel.com] Sent: Thursday, September 12, 2019 10:01 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [ Test ] meeting notes for 09/10 Agenda for 09/10 Attendees: Elio, Cristopher, Fernando, JC, Jose, Maria P, JP, Richo, Yang, Ada 1. Sanity status - Cristopher Still green. After the change in the repos we found a small issue, but is fixed now. Issues: app port unreachable from external - https://bugs.launchpad.net/starlingx/+bug/1841802 - still not fixed. After host-swact completed, unexpected swact occurred due to ceph error - https://bugs.launchpad.net/starlingx/+bug/1840176 - intermittent issue, fixed now. 2. Unified sanity - JC Slides: https://drive.google.com/file/d/1hBfWCb4Rn_SmteeqjWSpgluzDH192sHv/view?usp=s... What we have today: 4 configs (SX, DX, Standard local storage, standard external storage) Bare metal and virtual, no proxy, proxy and local registry deployments. Sanity for platform (containers) and OpenStack Proposal: WR and Intel running two configs each. Are we considering ping and ssh tests? those are included in the pytest suite We will use only pytest for running sanity testing. Three tests from robot are not in the pytest suite. Resize are in the regression repo. Rebuild to be added Reboot could be added into the nova_actions test. Still having problems with the natbox setup - please send the question to the mailing list. Please also add this info to the documentation. Not a date defined yet due to the problems with the infrastructure, but next week will have more visibility. For reporting: Wind River will send their results to Intel and the report will be consolidated and sent out (in the mean time we do automatic reporting). 3. stx.3.0 - release and feature testing plans - Ada Schedule updated - https://docs.google.com/spreadsheets/d/16JxIbfX7hQBjyPkaxYYuPij3XwTWDHMsB-GR... Actions: Containerized Openstack clients - Yang to ask Frank if implicit testing (sanity) is enough - update to suite is required. Fault Containerization - Jose to ask if implicit testing is enough - maybe a small regression for covering this (Horizon should be manually verified) Upversion Openstack to Train - JC to get in contact to Bruce and ask for the plan. Redfish Support - Ada to check on this one Performance Testing/Measurement Framework - Elio to check the deliverable expected. For regression - test plan is to run automated testing and select a subset of the new tests created for features for 2.0 as the manual test plan. Ada to work on the list and make it public. 4. Opens - All Yang is taking Numan's position into StarlingX. Thanks Yang! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (4)
-
Alonso, Juan Carlos
-
Cabrales, Ada
-
Dean Troyer
-
Jones, Bruce E