Skip to content
This repository has been archived by the owner on Oct 29, 2021. It is now read-only.

Add test nsm suites to reduce cluster count on CI #2070

Open
denis-tingaikin opened this issue Jan 22, 2020 · 2 comments
Open

Add test nsm suites to reduce cluster count on CI #2070

denis-tingaikin opened this issue Jan 22, 2020 · 2 comments
Assignees
Labels
pinned Pin for stale-pod

Comments

@denis-tingaikin
Copy link
Member

denis-tingaikin commented Jan 22, 2020

Overview

Add suites for integration tests to reduce test time and reduce cluster instances on CI.
Each test in suite should reuse nsm / forwarder.

For example:

We have a suite of tests for cluster:

  1. TestNSCDiesSingleNode
  2. TestSimpleMemifConnection
  3. TestNSCDiesMultiNode
  4. TestNSEDiesMultiNode

How it will work:

  1. TestNSCDiesSingleNode started on CI. It checks namespace NSM_NAMESPACE and doesn't find NSM PODs*. The test will deploy NSM PODs.
  2. TestSimpleMemifConnection started on CI. It checks namespace NSM_NAMESPACE and finds NSM PODs. The test will reuse NSM PODs.
  3. TestNSCDiesMultiNode started on CI. It checks namespace NSM_NAMESPACE and finds NSM PODs. The test will reuse NSM PODs.
  4. TestNSEDiesMultiNode started on CI. It checks namespace NSM_NAMESPACE and finds NSM PODs. The test will reuse NSM PODs.
  5. Suite finished on CI and cloudiest will cleanup resources in NSM_NAMESPACE for the cluster.

Total : suite reduces (max(deploy nsmgr time, deploy forwarder time) + max(cleanup forwarder time, cleanup nsmgr time))
x 3

NSM PODs are forwarder and nsmgr.

Bugs which has been found by testing suites on CI

#2007
#1898
#1895
#1914
...

PRs

First implementation:

  1. NSM Test suites #1861

After splitting at parts:

  1. Cloudtest improvements cloudtest#3 -- MERGED
  2. Test NSM Suites: Update cloudtest tool, split executions #1 #2057 -- MERGED
  3. Test NSM Suites: Improve artifacts storing on CI #2 #2042 -- MERGED
  4. Test NSM Suites: Add suites on CI #3 #2061 -- Fixing bugs
@stale
Copy link

stale bot commented Mar 5, 2020

This issue has been automatically marked as stale because it has not had activity in 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Mar 5, 2020
@stale
Copy link

stale bot commented Mar 12, 2020

This issue has been automatically closed because it has been inactive for 37 days. Feel free to reopen it if you feel it has been closed in error.

@stale stale bot closed this as completed Mar 12, 2020
Issue/PR tracking automation moved this from Icebox to Done Mar 12, 2020
Issue/PR tracking automation moved this from Done to In progress Mar 12, 2020
@stale stale bot removed the wontfix This will not be worked on label Mar 12, 2020
@denis-tingaikin denis-tingaikin added the pinned Pin for stale-pod label Mar 12, 2020
@denis-tingaikin denis-tingaikin moved this from In progress to Icebox in Issue/PR tracking Mar 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pinned Pin for stale-pod
Projects
Development

No branches or pull requests

1 participant