Browse Source

Merge "Test plan v0.1"

Jenkins 2 years ago
parent
commit
00f57db10d

+ 2
- 0
doc/requirements.txt View File

@@ -0,0 +1,2 @@
1
+docutils==0.9.1
2
+sphinx>=1.1.2,!=1.2.0,<1.3

+ 177
- 0
doc/test/Makefile View File

@@ -0,0 +1,177 @@
1
+# Makefile for Sphinx documentation
2
+#
3
+
4
+# You can set these variables from the command line.
5
+SPHINXOPTS    =
6
+SPHINXBUILD   = sphinx-build
7
+PAPER         =
8
+BUILDDIR      = _build
9
+
10
+# User-friendly check for sphinx-build
11
+ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
12
+$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/)
13
+endif
14
+
15
+# Internal variables.
16
+PAPEROPT_a4     = -D latex_paper_size=a4
17
+PAPEROPT_letter = -D latex_paper_size=letter
18
+ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
19
+# the i18n builder cannot share the environment and doctrees with the others
20
+I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
21
+
22
+.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest gettext
23
+
24
+help:
25
+	@echo "Please use \`make <target>' where <target> is one of"
26
+	@echo "  html       to make standalone HTML files"
27
+	@echo "  dirhtml    to make HTML files named index.html in directories"
28
+	@echo "  singlehtml to make a single large HTML file"
29
+	@echo "  pickle     to make pickle files"
30
+	@echo "  json       to make JSON files"
31
+	@echo "  htmlhelp   to make HTML files and a HTML help project"
32
+	@echo "  qthelp     to make HTML files and a qthelp project"
33
+	@echo "  devhelp    to make HTML files and a Devhelp project"
34
+	@echo "  epub       to make an epub"
35
+	@echo "  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
36
+	@echo "  latexpdf   to make LaTeX files and run them through pdflatex"
37
+	@echo "  latexpdfja to make LaTeX files and run them through platex/dvipdfmx"
38
+	@echo "  text       to make text files"
39
+	@echo "  man        to make manual pages"
40
+	@echo "  texinfo    to make Texinfo files"
41
+	@echo "  info       to make Texinfo files and run them through makeinfo"
42
+	@echo "  gettext    to make PO message catalogs"
43
+	@echo "  changes    to make an overview of all changed/added/deprecated items"
44
+	@echo "  xml        to make Docutils-native XML files"
45
+	@echo "  pseudoxml  to make pseudoxml-XML files for display purposes"
46
+	@echo "  linkcheck  to check all external links for integrity"
47
+	@echo "  doctest    to run all doctests embedded in the documentation (if enabled)"
48
+
49
+clean:
50
+	rm -rf $(BUILDDIR)/*
51
+
52
+html:
53
+	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
54
+	@echo
55
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
56
+
57
+dirhtml:
58
+	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
59
+	@echo
60
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
61
+
62
+singlehtml:
63
+	$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
64
+	@echo
65
+	@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
66
+
67
+pickle:
68
+	$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
69
+	@echo
70
+	@echo "Build finished; now you can process the pickle files."
71
+
72
+json:
73
+	$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
74
+	@echo
75
+	@echo "Build finished; now you can process the JSON files."
76
+
77
+htmlhelp:
78
+	$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
79
+	@echo
80
+	@echo "Build finished; now you can run HTML Help Workshop with the" \
81
+	      ".hhp project file in $(BUILDDIR)/htmlhelp."
82
+
83
+qthelp:
84
+	$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
85
+	@echo
86
+	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
87
+	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
88
+	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/FuelNSXplugin.qhcp"
89
+	@echo "To view the help file:"
90
+	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/FuelNSXplugin.qhc"
91
+
92
+devhelp:
93
+	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
94
+	@echo
95
+	@echo "Build finished."
96
+	@echo "To view the help file:"
97
+	@echo "# mkdir -p $$HOME/.local/share/devhelp/FuelNSXplugin"
98
+	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/FuelNSXplugin"
99
+	@echo "# devhelp"
100
+
101
+epub:
102
+	$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
103
+	@echo
104
+	@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
105
+
106
+latex:
107
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
108
+	@echo
109
+	@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
110
+	@echo "Run \`make' in that directory to run these through (pdf)latex" \
111
+	      "(use \`make latexpdf' here to do that automatically)."
112
+
113
+latexpdf:
114
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
115
+	@echo "Running LaTeX files through pdflatex..."
116
+	$(MAKE) -C $(BUILDDIR)/latex all-pdf
117
+	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
118
+
119
+latexpdfja:
120
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
121
+	@echo "Running LaTeX files through platex and dvipdfmx..."
122
+	$(MAKE) -C $(BUILDDIR)/latex all-pdf-ja
123
+	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
124
+
125
+text:
126
+	$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
127
+	@echo
128
+	@echo "Build finished. The text files are in $(BUILDDIR)/text."
129
+
130
+man:
131
+	$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
132
+	@echo
133
+	@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
134
+
135
+texinfo:
136
+	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
137
+	@echo
138
+	@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
139
+	@echo "Run \`make' in that directory to run these through makeinfo" \
140
+	      "(use \`make info' here to do that automatically)."
141
+
142
+info:
143
+	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
144
+	@echo "Running Texinfo files through makeinfo..."
145
+	make -C $(BUILDDIR)/texinfo info
146
+	@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
147
+
148
+gettext:
149
+	$(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
150
+	@echo
151
+	@echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
152
+
153
+changes:
154
+	$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
155
+	@echo
156
+	@echo "The overview file is in $(BUILDDIR)/changes."
157
+
158
+linkcheck:
159
+	$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
160
+	@echo
161
+	@echo "Link check complete; look for any errors in the above output " \
162
+	      "or in $(BUILDDIR)/linkcheck/output.txt."
163
+
164
+doctest:
165
+	$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
166
+	@echo "Testing of doctests in the sources finished, look at the " \
167
+	      "results in $(BUILDDIR)/doctest/output.txt."
168
+
169
+xml:
170
+	$(SPHINXBUILD) -b xml $(ALLSPHINXOPTS) $(BUILDDIR)/xml
171
+	@echo
172
+	@echo "Build finished. The XML files are in $(BUILDDIR)/xml."
173
+
174
+pseudoxml:
175
+	$(SPHINXBUILD) -b pseudoxml $(ALLSPHINXOPTS) $(BUILDDIR)/pseudoxml
176
+	@echo
177
+	@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."

+ 254
- 0
doc/test/conf.py View File

@@ -0,0 +1,254 @@
1
+"""Copyright 2016 Mirantis, Inc.
2
+
3
+Licensed under the Apache License, Version 2.0 (the "License"); you may
4
+not use this file except in compliance with the License. You may obtain
5
+copy of the License at
6
+
7
+http://www.apache.org/licenses/LICENSE-2.0
8
+
9
+Unless required by applicable law or agreed to in writing, software
10
+distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
11
+WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
12
+License for the specific language governing permissions and limitations
13
+under the License.
14
+"""
15
+
16
+
17
+# If extensions (or modules to document with autodoc) are in another directory,
18
+# add these directories to sys.path here. If the directory is relative to the
19
+# documentation root, use os.path.abspath to make it absolute, like shown here.
20
+#sys.path.insert(0, os.path.abspath('.'))
21
+
22
+# -- General configuration ------------------------------------------------
23
+
24
+# If your documentation needs a minimal Sphinx version, state it here.
25
+#needs_sphinx = '1.0'
26
+
27
+# Add any Sphinx extension module names here, as strings. They can be
28
+# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
29
+# ones.
30
+extensions = [ ]
31
+
32
+# Add any paths that contain templates here, relative to this directory.
33
+templates_path = ['_templates']
34
+
35
+# The suffix of source filenames.
36
+source_suffix = '.rst'
37
+
38
+# The encoding of source files.
39
+#source_encoding = 'utf-8-sig'
40
+
41
+# The master toctree document.
42
+master_doc = 'index'
43
+
44
+# General information about the project.
45
+project = u'Fuel NSX-T plugin'
46
+copyright = u'2016, Mirantis Inc.'
47
+
48
+# The version info for the project you're documenting, acts as replacement for
49
+# |version| and |release|, also used in various other places throughout the
50
+# built documents.
51
+#
52
+# The short X.Y version.
53
+version = '1.0.0'
54
+# The full version, including alpha/beta/rc tags.
55
+release = '1.0-1.0.0-1'
56
+
57
+# The language for content autogenerated by Sphinx. Refer to documentation
58
+# for a list of supported languages.
59
+#language = None
60
+
61
+# There are two options for replacing |today|: either, you set today to some
62
+# non-false value, then it is used:
63
+#today = ''
64
+# Else, today_fmt is used as the format for a strftime call.
65
+#today_fmt = '%B %d, %Y'
66
+
67
+# List of patterns, relative to source directory, that match files and
68
+# directories to ignore when looking for source files.
69
+#exclude_patterns = []
70
+
71
+# The reST default role (used for this markup: `text`) to use for all
72
+# documents.
73
+#default_role = None
74
+
75
+# If true, '()' will be appended to :func: etc. cross-reference text.
76
+#add_function_parentheses = True
77
+
78
+# If true, the current module name will be prepended to all description
79
+# unit titles (such as .. function::).
80
+#add_module_names = True
81
+
82
+# If true, sectionauthor and moduleauthor directives will be shown in the
83
+# output. They are ignored by default.
84
+#show_authors = False
85
+
86
+# The name of the Pygments (syntax highlighting) style to use.
87
+pygments_style = 'sphinx'
88
+
89
+# A list of ignored prefixes for module index sorting.
90
+#modindex_common_prefix = []
91
+
92
+# If true, keep warnings as "system message" paragraphs in the built documents.
93
+#keep_warnings = False
94
+
95
+
96
+# -- Options for HTML output ----------------------------------------------
97
+
98
+# The theme to use for HTML and HTML Help pages.  See the documentation for
99
+# a list of builtin themes.
100
+html_theme = 'default'
101
+
102
+# Theme options are theme-specific and customize the look and feel of a theme
103
+# further.  For a list of options available for each theme, see the
104
+# documentation.
105
+#html_theme_options = {}
106
+
107
+# Add any paths that contain custom themes here, relative to this directory.
108
+#html_theme_path = []
109
+
110
+# The name for this set of Sphinx documents.  If None, it defaults to
111
+# "<project> v<release> documentation".
112
+#html_title = None
113
+
114
+# A shorter title for the navigation bar.  Default is the same as html_title.
115
+#html_short_title = None
116
+
117
+# The name of an image file (relative to this directory) to place at the top
118
+# of the sidebar.
119
+#html_logo = None
120
+
121
+# The name of an image file (within the static path) to use as favicon of the
122
+# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
123
+# pixels large.
124
+#html_favicon = None
125
+
126
+# Add any paths that contain custom static files (such as style sheets) here,
127
+# relative to this directory. They are copied after the builtin static files,
128
+# so a file named "default.css" will overwrite the builtin "default.css".
129
+#html_static_path = ['_static']
130
+
131
+# Add any extra paths that contain custom files (such as robots.txt or
132
+# .htaccess) here, relative to this directory. These files are copied
133
+# directly to the root of the documentation.
134
+#html_extra_path = []
135
+
136
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
137
+# using the given strftime format.
138
+#html_last_updated_fmt = '%b %d, %Y'
139
+
140
+# If true, SmartyPants will be used to convert quotes and dashes to
141
+# typographically correct entities.
142
+#html_use_smartypants = True
143
+
144
+# Custom sidebar templates, maps document names to template names.
145
+#html_sidebars = {}
146
+
147
+# Additional templates that should be rendered to pages, maps page names to
148
+# template names.
149
+#html_additional_pages = {}
150
+
151
+# If false, no module index is generated.
152
+#html_domain_indices = True
153
+
154
+# If false, no index is generated.
155
+#html_use_index = True
156
+
157
+# If true, the index is split into individual pages for each letter.
158
+#html_split_index = False
159
+
160
+# If true, links to the reST sources are added to the pages.
161
+#html_show_sourcelink = True
162
+
163
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
164
+#html_show_sphinx = True
165
+
166
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
167
+#html_show_copyright = True
168
+
169
+# If true, an OpenSearch description file will be output, and all pages will
170
+# contain a <link> tag referring to it.  The value of this option must be the
171
+# base URL from which the finished HTML is served.
172
+#html_use_opensearch = ''
173
+
174
+# This is the file name suffix for HTML files (e.g. ".xhtml").
175
+#html_file_suffix = None
176
+
177
+# Output file base name for HTML help builder.
178
+htmlhelp_basename = 'FuelNSXplugindoc'
179
+
180
+
181
+# -- Options for LaTeX output ---------------------------------------------
182
+
183
+latex_elements = { 'classoptions': ',openany,oneside',
184
+                   'babel': '\\usepackage[english]{babel}',
185
+                   'preamble': '\setcounter{tocdepth}{3} '
186
+                               '\setcounter{secnumdepth}{0}'}
187
+
188
+# Grouping the document tree into LaTeX files. List of tuples
189
+# (source start file, target name, title,
190
+#  author, documentclass [howto, manual, or own class]).
191
+latex_documents = [
192
+  ('index', 'nsx-test-plan-' + version + '.tex', u'Fuel NSX-T plugin testing documentation',
193
+   u'Mirantis Inc.', 'manual'),
194
+]
195
+
196
+# The name of an image file (relative to this directory) to place at the top of
197
+# the title page.
198
+#latex_logo = None
199
+
200
+# For "manual" documents, if this is true, then toplevel headings are parts,
201
+# not chapters.
202
+#latex_use_parts = False
203
+
204
+# If true, show page references after internal links.
205
+#latex_show_pagerefs = False
206
+
207
+# If true, show URL addresses after external links.
208
+#latex_show_urls = False
209
+
210
+# Documents to append as an appendix to all manuals.
211
+#latex_appendices = []
212
+
213
+# If false, no module index is generated.
214
+#latex_domain_indices = True
215
+
216
+
217
+# -- Options for manual page output ---------------------------------------
218
+
219
+# One entry per manual page. List of tuples
220
+# (source start file, name, description, authors, manual section).
221
+man_pages = [
222
+    ('index', 'fuelnsxplugin', u'Fuel NSX-T plugin testing documentation',
223
+     [u'Mirantis Inc.'], 1)
224
+]
225
+
226
+# If true, show URL addresses after external links.
227
+#man_show_urls = False
228
+
229
+
230
+# -- Options for Texinfo output -------------------------------------------
231
+
232
+# Grouping the document tree into Texinfo files. List of tuples
233
+# (source start file, target name, title, author,
234
+#  dir menu entry, description, category)
235
+texinfo_documents = [
236
+  ('index', 'FuelNSXplugin', u'Fuel NSX-T plugin testing documentation',
237
+   u'Mirantis Inc.', 'FuelNSXplugin', 'One line description of project.',
238
+   'Miscellaneous'),
239
+]
240
+
241
+# Documents to append as an appendix to all manuals.
242
+#texinfo_appendices = []
243
+
244
+# If false, no module index is generated.
245
+#texinfo_domain_indices = True
246
+
247
+# How to display URL addresses: 'footnote', 'no', or 'inline'.
248
+#texinfo_show_urls = 'footnote'
249
+
250
+# If true, do not generate a @detailmenu in the "Top" node's menu.
251
+#texinfo_no_detailmenu = False
252
+
253
+# Insert footnotes where they are defined instead of at the end.
254
+pdf_inline_footnotes = True

+ 11
- 0
doc/test/index.rst View File

@@ -0,0 +1,11 @@
1
+Fuel NSX-T plugin's testing documentation
2
+========================================
3
+
4
+Testing documents
5
+-----------------
6
+
7
+.. toctree::
8
+   :glob:
9
+   :maxdepth: 3
10
+
11
+   source/nsx-t_test_plan

+ 256
- 0
doc/test/source/nsx-t_test_plan.rst View File

@@ -0,0 +1,256 @@
1
+=================================
2
+Test Plan for NSX-T plugin v1.0.0
3
+=================================
4
+
5
+************
6
+Introduction
7
+************
8
+
9
+Purpose
10
+=======
11
+
12
+Main purpose of this document is intended to describe Quality Assurance
13
+activities, required to insure that Fuel plugin for VMware NSX driver is
14
+ready for production. The project will be able to offer VMware NSX
15
+integration functionality with MOS. The scope of this plan defines the
16
+following objectives:
17
+
18
+* Identify testing activities;
19
+* Outline testing approach, test types, test cycle that will be used;
20
+* List of metrics and deliverable elements;
21
+* List of items for testing and out of testing scope;
22
+* Detect exit criteria in testing purposes;
23
+* Describe test environment.
24
+
25
+Scope
26
+=====
27
+
28
+Fuel NSX-T plugin includes NSX-T plugin for Neutron which is developed by
29
+third party. This test plan covers a full functionality of Fuel NSX-T plugin,
30
+include basic scenarios related with NSX Neutron plugin.
31
+
32
+Following test types should be provided:
33
+
34
+* Smoke/BVT tests
35
+* Integration tests
36
+* System tests
37
+* Destructive tests
38
+* GUI tests
39
+
40
+Performance testing will be executed on the scale lab and a custom set of
41
+rally scenarios must be run with NSX environment. Configuration, environment
42
+and scenarios for performance/scale testing should be determine separately.
43
+
44
+Intended Audience
45
+=================
46
+
47
+This document is intended for project team staff (QA and Dev engineers and
48
+managers) and all other persons who are interested in testing results.
49
+
50
+Limitation
51
+==========
52
+
53
+Plugin (or its components) has the following limitations:
54
+
55
+* VMware NSX-T plugin can be enabled only with Neutron tunnel segmentation.
56
+* NSX Transformers Manager 1.0.0 and 1.0.1 are supported.
57
+
58
+Product compatibility matrix
59
+============================
60
+
61
+.. list-table:: product compatibility matrix
62
+   :widths: 15 10 30
63
+   :header-rows: 1
64
+
65
+   * - Requirement
66
+     - Version
67
+     - Comment
68
+   * - MOS
69
+     - 9.0
70
+     -
71
+   * - OpenStack release
72
+     - Mitaka with Ubuntu 14.04
73
+     -
74
+   * - vSphere
75
+     - 6.0
76
+     -
77
+   * - VMware NSX Transformers
78
+     - 1.0.0, 1.0.1
79
+     -
80
+
81
+**************************************
82
+Evaluation Mission and Test Motivation
83
+**************************************
84
+
85
+Project main goal is to build a MOS plugin that integrates a Neutron VMware
86
+NSX-T plugin. This plugin gives opportunity to utilize KVM and VMware compute
87
+cluster. The plugin must be compatible with the version 9.0 of Mirantis
88
+OpenStack and should be tested with software/hardware described in
89
+`product compatibility matrix`_.
90
+
91
+See the VMware NSX-T plugin specification for more details.
92
+
93
+Evaluation mission
94
+==================
95
+
96
+* Find important problems with integration of Neutron VMware NSX-T plugin.
97
+* Verify a specification.
98
+* Provide tests for maintenance update.
99
+* Lab environment deployment.
100
+* Deploy MOS with developed plugin installed.
101
+* Create and run specific tests for plugin/deployment.
102
+* Documentation.
103
+
104
+*****************
105
+Target Test Items
106
+*****************
107
+
108
+* Install/uninstall Fuel NSX-T plugin
109
+* Deploy Cluster with Fuel NSX-T plugin by Fuel
110
+    * Roles of nodes
111
+        * controller
112
+        * mongo
113
+        * compute
114
+        * compute-vmware
115
+        * cinder-vmware
116
+    * Hypervisors:
117
+        * Qemu+Vcenter
118
+        * KVM
119
+    * Storage:
120
+        * Ceph
121
+        * Cinder
122
+        * VMWare vCenter/ESXi datastore for images
123
+    * Network
124
+        * Neutron with NSX-T plugin
125
+    * Additional components
126
+        * Ceilometer
127
+        * Health Check
128
+    * Upgrade master node
129
+* MOS and VMware-NSX-T plugin
130
+    * Computes(Nova)
131
+        * Launch and manage instances
132
+        * Launch instances in batch
133
+    * Networks (Neutron)
134
+        * Create and manage public and private networks.
135
+        * Create and manage routers.
136
+        * Port binding / disabling
137
+        * Security groups
138
+        * Assign vNIC to a VM
139
+        * Connection between instances
140
+    * Horizon
141
+        * Create and manage projects
142
+    * Glance
143
+        * Create and manage images
144
+* GUI
145
+    * Fuel UI
146
+* CLI
147
+    * Fuel CLI
148
+
149
+*************
150
+Test approach
151
+*************
152
+
153
+The project test approach consists of Smoke, Integration, System, Regression
154
+Failover and Acceptance test levels.
155
+
156
+**Smoke testing**
157
+
158
+The goal of smoke testing is to ensure that the most critical features of Fuel
159
+VMware NSX-T plugin work after new build delivery. Smoke tests will be used by
160
+QA to accept software builds from Development team.
161
+
162
+**Integration and System testing**
163
+
164
+The goal of integration and system testing is to ensure that new or modified
165
+components of Fuel and MOS work effectively with Fuel VMware NSX-T plugin
166
+without gaps in data flow.
167
+
168
+**Regression testing**
169
+
170
+The goal of regression testing is to verify that key features of Fuel VMware
171
+NSX-T plugin are not affected by any changes performed during preparation to
172
+release (includes defects fixing, new features introduction and possible
173
+updates).
174
+
175
+**Failover testing**
176
+
177
+Failover and recovery testing ensures that the target-of-test can successfully
178
+failover and recover from a variety of hardware, software, or network
179
+malfunctions with undue loss of data or data integrity.
180
+
181
+**Acceptance testing**
182
+
183
+The goal of acceptance testing is to ensure that Fuel VMware NSX-T plugin has
184
+reached a level of stability that meets requirements and acceptance criteria.
185
+
186
+
187
+***********************
188
+Entry and exit criteria
189
+***********************
190
+
191
+Criteria for test process starting
192
+==================================
193
+
194
+Before test process can be started it is needed to make some preparation
195
+actions - to execute important preconditions. The following steps must be
196
+executed successfully for starting test phase:
197
+
198
+* all project requirements are reviewed and confirmed;
199
+* implementation of testing features has finished (a new build is ready for testing);
200
+* implementation code is stored in GIT;
201
+* test environment is prepared with correct configuration, installed all needed software, hardware;
202
+* test environment contains the last delivered build for testing;
203
+* test plan is ready and confirmed internally;
204
+* implementation of manual tests and autotests (if any) has finished.
205
+
206
+Feature exit criteria
207
+=====================
208
+
209
+Testing of a feature can be finished when:
210
+
211
+* All planned tests (prepared before) for the feature are executed; no defects are found during this run;
212
+* All planned tests for the feature are executed; defects found during this run are verified or confirmed to be acceptable (known issues);
213
+* The time for testing of that feature according to the project plan has run out and Project Manager confirms that no changes to the schedule are possible.
214
+
215
+Suspension and resumption criteria
216
+==================================
217
+
218
+Testing of a particular feature is suspended if there is a blocking issue
219
+which prevents tests execution. Blocking issue can be one of the following:
220
+
221
+* Testing environment for the feature is not ready
222
+* Testing environment is unavailable due to failure
223
+* Feature has a blocking defect, which prevents further usage of this feature and there is no workaround available
224
+* CI tests fail
225
+
226
+************
227
+Deliverables
228
+************
229
+
230
+List of deliverables
231
+====================
232
+
233
+Project testing activities are to be resulted in the following reporting documents:
234
+
235
+* Test plan
236
+* Test report
237
+* Automated test cases
238
+
239
+Acceptance criteria
240
+===================
241
+
242
+* All acceptance criteria for user stories are met.
243
+* All test cases are executed. BVT tests are passed
244
+* Critical and high issues are fixed
245
+* All required documents are delivered
246
+* Release notes including a report on the known errors of that release
247
+
248
+**********
249
+Test cases
250
+**********
251
+
252
+.. include:: test_suite_smoke.rst
253
+.. include:: test_suite_integration.rst
254
+.. include:: test_suite_scale.rst
255
+.. include:: test_suite_system.rst
256
+.. include:: test_suite_failover.rst

+ 129
- 0
doc/test/source/test_suite_failover.rst View File

@@ -0,0 +1,129 @@
1
+Failover
2
+========
3
+
4
+
5
+Verify deleting of Fuel NSX-T plugin is impossible if it's used by created cluster.
6
+-----------------------------------------------------------------------------------
7
+
8
+
9
+ID
10
+##
11
+
12
+nsxt_uninstall_negative
13
+
14
+
15
+Description
16
+###########
17
+
18
+It is impossible to remove plugin while at least one environment exists.
19
+
20
+
21
+Complexity
22
+##########
23
+
24
+smoke
25
+
26
+
27
+Steps
28
+#####
29
+
30
+    1. Install NSX-T plugin on master node.
31
+    2. Create a new environment with enabled NSX-T plugin.
32
+    3. Try to delete plugin via cli from master node::
33
+
34
+          fuel plugins --remove nsxt==1.0.0
35
+
36
+
37
+Expected result
38
+###############
39
+
40
+Alert: "400 Client Error: Bad Request (Can't delete plugin which is enabled for some environment.)" should be displayed.
41
+
42
+
43
+Check plugin functionality after shutdown primary controller.
44
+-------------------------------------------------------------
45
+
46
+
47
+ID
48
+##
49
+
50
+nsxt_shutdown_controller
51
+
52
+
53
+Description
54
+###########
55
+
56
+Check plugin functionality after shutdown primary controller.
57
+
58
+
59
+Complexity
60
+##########
61
+
62
+core
63
+
64
+
65
+Steps
66
+#####
67
+
68
+    1. Log in to the Fuel with preinstalled plugin and deployed enviroment with 3 controllers.
69
+    2. Log in to Horizon.
70
+    3. Create vcenter VM and check connectivity to outside world from VM.
71
+    4. Shutdown primary controller.
72
+    5. Ensure that VIPs are moved to other controller.
73
+    6. Ensure taht there is a connectivity to outside world from created VM.
74
+    7. Create a new network and attach it to default router.
75
+    8. Create a vcenter VM with new network and check network connectivity via ICMP.
76
+
77
+
78
+Expected result
79
+###############
80
+
81
+Networking works correct after failure of primary controller.
82
+
83
+
84
+Check cluster functionality after reboot vcenter.
85
+-------------------------------------------------
86
+
87
+
88
+ID
89
+##
90
+
91
+nsxt_reboot_vcenter
92
+
93
+
94
+Description
95
+###########
96
+
97
+Test verifies that system functionality is ok when vcenter has been rebooted.
98
+
99
+
100
+Complexity
101
+##########
102
+
103
+core
104
+
105
+
106
+Steps
107
+#####
108
+
109
+    1. Log in to the Fuel with preinstalled plugin and deployed enviroment.
110
+    2. Log in to Horizon.
111
+    3. Launch vcenter instance VM_1 with image TestVM-VMDK and flavor m1.tiny.
112
+    4. Launch vcenter instance VM_2 with image TestVM-VMDK and flavor m1.tiny.
113
+    5. Check connection between VMs, send ping from VM_1 to VM_2 and vice verse.
114
+    6. Reboot vcenter::
115
+
116
+          vmrun -T ws-shared -h https://localhost:443/sdk -u vmware -p pass
117
+          reset "[standard] vcenter/vcenter.vmx"
118
+
119
+    7. Check that controller lost connection with vCenter.
120
+    8. Wait for vCenter is online.
121
+    9. Ensure that all instances from vCenter are displayed in dashboard.
122
+    10. Ensure there is connectivity between vcenter1's and vcenter2's VMs.
123
+    11. Run OSTF.
124
+
125
+
126
+Expected result
127
+###############
128
+
129
+Cluster should be deployed and all OSTF test cases should be passed. Ping should get response.

+ 54
- 0
doc/test/source/test_suite_integration.rst View File

@@ -0,0 +1,54 @@
1
+Integration
2
+===========
3
+
4
+
5
+Deploy cluster with NSX-T plugin and ceilometer.
6
+------------------------------------------------
7
+
8
+
9
+ID
10
+##
11
+
12
+nsxt_ceilometer
13
+
14
+
15
+Description
16
+###########
17
+
18
+Check deployment of environment with Fuel NSX-T plugin and Ceilometer.
19
+
20
+
21
+Complexity
22
+##########
23
+
24
+core
25
+
26
+
27
+Steps
28
+#####
29
+
30
+    1. Log in to the Fuel UI with preinstalled NSX-T plugin.
31
+    2. Create a new environment with following parameters:
32
+        * Compute: KVM/QEMU with vCenter
33
+        * Networking: Neutron with NSX-T plugin
34
+        * Storage: default
35
+        * Additional services: Ceilometer
36
+    3. Add nodes with following roles:
37
+        * Controller + Mongo
38
+        * Controller + Mongo
39
+        * Controller + Mongo
40
+        * Compute-vmware
41
+        * Compute
42
+    4. Configure interfaces on nodes.
43
+    5. Configure network settings.
44
+    6. Enable and configure NSX-T plugin.
45
+    7. Configure VMware vCenter Settings. Add 2 vSphere clusters and configure Nova Compute instances on conrollers and compute-vmware.
46
+    8. Verify networks.
47
+    9. Deploy cluster.
48
+    10. Run OSTF.
49
+
50
+
51
+Expected result
52
+###############
53
+
54
+Cluster should be deployed and all OSTF tests cases should be passed.

+ 180
- 0
doc/test/source/test_suite_scale.rst View File

@@ -0,0 +1,180 @@
1
+Scale
2
+=====
3
+
4
+
5
+Check scale actions for controller nodes.
6
+-----------------------------------------
7
+
8
+
9
+ID
10
+##
11
+
12
+nsxt_add_delete_controller
13
+
14
+
15
+Description
16
+###########
17
+
18
+Verifies that system functionality is ok when controller has been removed.
19
+
20
+
21
+Complexity
22
+##########
23
+
24
+core
25
+
26
+
27
+Steps
28
+#####
29
+
30
+    1. Log in to the Fuel with preinstalled NSX-T plugin.
31
+    2. Create a new environment with following parameters:
32
+        * Compute: KVM/QEMU with vCenter
33
+        * Networking: Neutron with NSX-T plugin
34
+        * Storage: default
35
+    3. Add nodes with following roles:
36
+        * Controller
37
+        * Controller
38
+        * Controller
39
+        * Controller
40
+        * Cinder-vmware
41
+        * Compute-vmware
42
+    4. Configure interfaces on nodes.
43
+    5. Configure network settings.
44
+    6. Enable and configure NSX-T plugin.
45
+    7. Configure VMware vCenter Settings. Add 2 vSphere clusters and configure Nova Compute instances on conrollers and compute-vmware.
46
+    8. Deploy cluster.
47
+    9. Run OSTF.
48
+    10. Launch 1 KVM and 1 vcenter VMs.
49
+    11. Remove node with controller role.
50
+    12. Redeploy cluster.
51
+    13. Check that all instances are in place.
52
+    14. Run OSTF.
53
+    15. Add controller.
54
+    16. Redeploy cluster.
55
+    17. Check that all instances are in place.
56
+    18. Run OSTF.
57
+
58
+
59
+Expected result
60
+###############
61
+
62
+Cluster should be deployed and all OSTF test cases should be passed.
63
+
64
+
65
+Check scale actions for compute nodes.
66
+--------------------------------------
67
+
68
+
69
+ID
70
+##
71
+
72
+nsxt_add_delete_compute_node
73
+
74
+
75
+Description
76
+###########
77
+
78
+Verify that system functionality is ok after redeploy.
79
+
80
+
81
+Complexity
82
+##########
83
+
84
+core
85
+
86
+
87
+Steps
88
+#####
89
+
90
+    1. Connect to the Fuel web UI with preinstalled NSX-T plugin.
91
+    2. Create a new environment with following parameters:
92
+        * Compute: KVM/QEMU
93
+        * Networking: Neutron with NSX-T plugin
94
+        * Storage: default
95
+        * Additional services: default
96
+    3. Add nodes with following roles:
97
+        * Controller
98
+        * Controller
99
+        * Controller
100
+        * Compute
101
+    4. Configure interfaces on nodes.
102
+    5. Configure network settings.
103
+    6. Enable and configure NSX-T plugin.
104
+    7. Deploy cluster.
105
+    8. Run OSTF.
106
+    9. Launch KVM vm.
107
+    10. Add node with compute role.
108
+    11. Redeploy cluster.
109
+    12. Check that all instances are in place.
110
+    13. Run OSTF.
111
+    14. Remove node with compute role from base installation.
112
+    15. Redeploy cluster.
113
+    16. Check that all instances are in place.
114
+    17. Run OSTF.
115
+
116
+
117
+Expected result
118
+###############
119
+
120
+Changing of cluster configuration was successful. Cluster should be deployed and all OSTF test cases should be passed.
121
+
122
+
123
+Check scale actions for compute-vmware nodes.
124
+---------------------------------------------
125
+
126
+
127
+ID
128
+##
129
+
130
+nsxt_add_delete_compute_vmware_node
131
+
132
+
133
+Description
134
+###########
135
+
136
+Verify that system functionality is ok after redeploy.
137
+
138
+
139
+Complexity
140
+##########
141
+
142
+core
143
+
144
+
145
+Steps
146
+#####
147
+
148
+    1. Connect to the Fuel web UI with preinstalled NSX-T plugin.
149
+    2. Create a new environment with following parameters:
150
+        * Compute: KVM/QEMU with vCenter
151
+        * Networking: Neutron with NSX-T plugin
152
+        * Storage: default
153
+        * Additional services: default
154
+    3. Add nodes with following roles:
155
+        * Controller
156
+        * Controller
157
+        * Controller
158
+        * Compute-vmware
159
+    4. Configure interfaces on nodes.
160
+    5. Configure network settings.
161
+    6. Enable and configure NSX-T plugin.
162
+    7. Configure VMware vCenter Settings. Add 1 vSphere cluster and configure Nova Compute instance on compute-vmware.
163
+    8. Deploy cluster.
164
+    9. Run OSTF.
165
+    10. Launch vcenter vm.
166
+    11. Remove node with compute-vmware role.
167
+    12. Reconfigure vcenter compute clusters.
168
+    13. Redeploy cluster.
169
+    14. Check vm instance has been removed.
170
+    15. Run OSTF.
171
+    16. Add node with compute-vmware role.
172
+    17. Reconfigure vcenter compute clusters.
173
+    18. Redeploy cluster.
174
+    19. Run OSTF.
175
+
176
+
177
+Expected result
178
+###############
179
+
180
+Changing of cluster configuration was successful. Cluster should be deployed and all OSTF test cases should be passed.

+ 363
- 0
doc/test/source/test_suite_smoke.rst View File

@@ -0,0 +1,363 @@
1
+Smoke
2
+=====
3
+
4
+
5
+Install Fuel VMware NSX-T plugin.
6
+---------------------------------
7
+
8
+
9
+ID
10
+##
11
+
12
+nsxt_install
13
+
14
+
15
+Description
16
+###########
17
+
18
+Check that plugin can be installed.
19
+
20
+
21
+Complexity
22
+##########
23
+
24
+smoke
25
+
26
+
27
+Steps
28
+#####
29
+
30
+    1. Connect to the Fuel master node via ssh.
31
+    2. Upload NSX-T plugin.
32
+    3. Install NSX-T plugin.
33
+    4. Run command 'fuel plugins'.
34
+    5. Check name, version and package version of plugin.
35
+
36
+
37
+Expected result
38
+###############
39
+Output::
40
+
41
+ [root@nailgun ~]# fuel plugins --install nsx-t-1.0-1.0.0-1.noarch.rpm
42
+ Loaded plugins: fastestmirror, priorities
43
+ Examining nsx-t-1.0-1.0.0-1.noarch.rpm: nsx-t-1.0-1.0.0-1.noarch
44
+ Marking nsx-t-1.0-1.0.0-1.noarch.rpm to be installed
45
+ Resolving Dependencies
46
+ --> Running transaction check
47
+ ---> Package nsx-t-1.0.noarch 0:1.0.0-1 will be installed
48
+ --> Finished Dependency Resolution
49
+
50
+ Dependencies Resolved
51
+
52
+
53
+  Package Arch Version Repository Size
54
+ Installing:
55
+  nsx-t-1.0 noarch 1.0.0-1 /nsx-t-1.0-1.0.0-1.noarch 20 M
56
+
57
+ Transaction Summary
58
+ Install  1 Package
59
+
60
+ Total size: 20 M
61
+ Installed size: 20 M
62
+ Downloading packages:
63
+ Running transaction check
64
+ Running transaction test
65
+ Transaction test succeeded
66
+ Running transaction
67
+   Installing : nsx-t-1.0-1.0.0-1.noarch 1/1
68
+   Verifying  : nsx-t-1.0-1.0.0-1.noarch 1/1
69
+
70
+ Installed:
71
+   nsx-t-1.0.noarch 0:1.0.0-1
72
+
73
+ Complete!
74
+ Plugin nsx-t-1.0-1.0.0-1.noarch.rpm was successfully installed.
75
+
76
+Plugin was installed successfully using cli.
77
+
78
+
79
+Uninstall Fuel VMware NSX-T plugin.
80
+-----------------------------------
81
+
82
+
83
+ID
84
+##
85
+
86
+nsxt_uninstall
87
+
88
+
89
+Description
90
+###########
91
+
92
+Check that plugin can be removed.
93
+
94
+
95
+Complexity
96
+##########
97
+
98
+smoke
99
+
100
+
101
+Steps
102
+#####
103
+
104
+    1. Connect to fuel node with preinstalled NSX-T plugin via ssh.
105
+    2. Remove NSX-T plugin.
106
+    3. Run command 'fuel plugins' to ensure the NSX-T plugin has been removed.
107
+
108
+
109
+Expected result
110
+###############
111
+Output::
112
+
113
+ [root@nailgun ~]# fuel plugins --remove nsx-t==1.0.0
114
+ Loaded plugins: fastestmirror, priorities
115
+ Resolving Dependencies
116
+ --> Running transaction check
117
+ ---> Package nsx-t-1.0.noarch 0:1.0.0-1 will be erased
118
+ --> Finished Dependency Resolution
119
+
120
+ Dependencies Resolved
121
+
122
+  Package  Arch  Version Repository Size
123
+ Removing:
124
+  nsx-t-1.0 noarch 1.0.0-1 @/nsx-t-1.0-1.0.0-1.noarch 20 M
125
+
126
+ Transaction Summary
127
+ Remove  1 Package
128
+
129
+ Installed size: 20 M
130
+ Downloading packages:
131
+ Running transaction check
132
+ Running transaction test
133
+ Transaction test succeeded
134
+ Running transaction
135
+   Erasing    : nsx-t-1.0-1.0.0-1.noarch 1/1
136
+   Verifying  : nsx-t-1.0-1.0.0-1.noarch 1/1
137
+
138
+ Removed:
139
+   nsx-t-1.0.noarch 0:1.0.0-1
140
+
141
+ Complete!
142
+ Plugin nsx-t==1.0.0 was successfully removed.
143
+
144
+Plugin was removed.
145
+
146
+
147
+Verify that all UI elements of NSX-T plugin section meets the requirements.
148
+---------------------------------------------------------------------------
149
+
150
+
151
+ID
152
+##
153
+
154
+nsxt_gui
155
+
156
+
157
+Description
158
+###########
159
+
160
+Verify that all UI elements of NSX-T plugin section meets the requirements.
161
+
162
+
163
+Complexity
164
+##########
165
+
166
+smoke
167
+
168
+
169
+Steps
170
+#####
171
+
172
+    1. Login to the Fuel web UI.
173
+    2. Click on the Networks tab.
174
+    3. Verify that section of NSX-T plugin is present under the Other menu option.
175
+    4. Verify that check box 'NSX-T plugin' is enabled by default.
176
+    5. Verify that all labels of 'NSX-T plugin' section have the same font style and colour.
177
+    6. Verify that all elements of NSX-T plugin section are vertical aligned.
178
+
179
+
180
+Expected result
181
+###############
182
+
183
+All elements of NSX-T plugin section are regimented.
184
+
185
+
186
+Deployment with plugin, controller and vmware datastore backend.
187
+----------------------------------------------------------------
188
+
189
+
190
+ID
191
+##
192
+
193
+nsxt_smoke
194
+
195
+
196
+Description
197
+###########
198
+
199
+Check deployment of environment with NSX-T plugin and one controller.
200
+
201
+
202
+Complexity
203
+##########
204
+
205
+smoke
206
+
207
+
208
+Steps
209
+#####
210
+
211
+    1. Log in to the Fuel with preinstalled NSX-T plugin.
212
+    2. Create a new environment with following parameters:
213
+        * Compute: KVM, QEMU with vCenter
214
+        * Networking: Neutron with NSX-T plugin
215
+        * Storage: default
216
+        * Additional services: default
217
+    3. Add nodes with following roles:
218
+        * Controller
219
+    4. Configure interfaces on nodes.
220
+    5. Configure network settings.
221
+    6. Enable and configure NSX-T plugin.
222
+    7. Configure VMware vCenter Settings. Add 1 vSphere cluster and configure Nova Compute instances on controllers.
223
+    8. Deploy cluster.
224
+    9. Run OSTF.
225
+
226
+
227
+Expected result
228
+###############
229
+
230
+Cluster should be deployed successfully and all OSTF tests should be passed.
231
+
232
+
233
+Deploy HA cluster with NSX-T plugin.
234
+------------------------------------
235
+
236
+
237
+ID
238
+##
239
+
240
+nsxt_bvt
241
+
242
+
243
+Description
244
+###########
245
+
246
+Check deployment of environment with NSX-T plugin, 3 Controllers, 1 Compute, 3 CephOSD, cinder-vware + compute-vmware roles.
247
+
248
+
249
+Complexity
250
+##########
251
+
252
+smoke
253
+
254
+
255
+Steps
256
+#####
257
+
258
+    1. Connect to the Fuel web UI with preinstalled NSX-T plugin.
259
+    2. Create a new environment with following parameters:
260
+        * Compute: KVM, QEMU with vCenter
261
+        * Networking: Neutron with NSX-T plugin
262
+        * Storage: Ceph RBD for images (Glance)
263
+        * Additional services: default
264
+    3. Add nodes with following roles:
265
+        * Controller
266
+        * Controller
267
+        * Controller
268
+        * CephOSD
269
+        * CephOSD
270
+        * CephOSD
271
+        * Compute-vmware, cinder-vmware
272
+        * Compute
273
+    4. Configure interfaces on nodes.
274
+    5. Configure network settings.
275
+    6. Enable and configure NSX-T plugin.
276
+    7. Configure VMware vCenter Settings. Add 2 vSphere clusters and configure Nova Compute instances on controllers and compute-vmware.
277
+    8. Verify networks.
278
+    9. Deploy cluster.
279
+    10. Run OSTF.
280
+
281
+
282
+Expected result
283
+###############
284
+
285
+Cluster should be deployed and all OSTF tests should be passed.
286
+
287
+
288
+Check option 'Bypass NSX Manager certificate verification' works correct
289
+------------------------------------------------------------------------
290
+
291
+
292
+ID
293
+##
294
+
295
+nsxt_insecure_false
296
+
297
+
298
+Description
299
+###########
300
+
301
+Check that insecure checkbox functions properly.
302
+
303
+
304
+Complexity
305
+##########
306
+
307
+core
308
+
309
+
310
+Steps
311
+#####
312
+
313
+    1. Provide CA certificate via web UI or through system storage.
314
+    2. Install NSX-T plugin.
315
+    3. Enable plugin on tab Networks -> NSX-T plugin.
316
+    4. Fill the form with corresponding values.
317
+    5. Uncheck checkbox 'Bypass NSX Manager certificate verification'.
318
+    6. Deploy cluster with one controller.
319
+    7. Run OSTF.
320
+
321
+
322
+Expected result
323
+###############
324
+
325
+Cluster should be deployed and all OSTF tests should be passed.
326
+
327
+
328
+Verify that nsxt driver configured properly after enabling NSX-T plugin
329
+-----------------------------------------------------------------------
330
+
331
+
332
+ID
333
+##
334
+
335
+nsxt_config_ok
336
+
337
+
338
+Description
339
+###########
340
+
341
+Check that all parameters of nsxt driver config files have been filled up with values were entered from GUI. Applicable values that are typically used are described in plugin docs. Root & intermediate certificate are signed, in attachment.
342
+
343
+
344
+Complexity
345
+##########
346
+
347
+advanced
348
+
349
+
350
+Steps
351
+#####
352
+
353
+    1. Install NSX-T plugin.
354
+    2. Enable plugin on tab Networks -> NSX-T plugin.
355
+    3. Fill the form with corresponding values.
356
+    4. Do all things that are necessary to provide interoperability of NSX-T plugin and NSX Manager with certificate.
357
+    5. Check Additional settings. Fill the form with corresponding values. Save settings by pressing the button.
358
+
359
+
360
+Expected result
361
+###############
362
+
363
+Check that nsx.ini on controller nodes is properly configured.

+ 780
- 0
doc/test/source/test_suite_system.rst View File

@@ -0,0 +1,780 @@
1
+System
2
+======
3
+
4
+
5
+Setup for system tests
6
+----------------------
7
+
8
+
9
+ID
10
+##
11
+
12
+nsxt_ha_mode
13
+
14
+
15
+Description
16
+###########
17
+
18
+Deploy environment with 3 controlers and 1 Compute node. Nova Compute instances are running on controllers nodes. It is a config for all system tests.
19
+
20
+
21
+Complexity
22
+##########
23
+
24
+core
25
+
26
+
27
+Steps
28
+#####
29
+
30
+    1. Log in to the Fuel web UI with preinstalled NSX-T plugin.
31
+    2. Create a new environment with following parameters:
32
+        * Compute: KVM, QEMU with vCenter
33
+        * Networking: Neutron with NSX-T plugin
34
+        * Storage: default
35
+        * Additional services: default
36
+    3. Add nodes with following roles:
37
+        * Controller
38
+        * Controller
39
+        * Controller
40
+        * Compute
41
+    4. Configure interfaces on nodes.
42
+    5. Configure network settings.
43
+    6. Enable and configure NSX-T plugin.
44
+    7. Configure VMware vCenter Settings. Add 1 vSphere cluster and configure Nova Compute instance on conrollers.
45
+    8. Verify networks.
46
+    9. Deploy cluster.
47
+    10. Run OSTF.
48
+
49
+
50
+Expected result
51
+###############
52
+
53
+Cluster should be deployed and all OSTF test cases should be passed.
54
+
55
+
56
+Check abilities to create and terminate networks on NSX.
57
+--------------------------------------------------------
58
+
59
+
60
+ID
61
+##
62
+
63
+nsxt_create_terminate_networks
64
+
65
+
66
+Description
67
+###########
68
+
69
+Verifies that creation of network is translated to vcenter.
70
+
71
+
72
+Complexity
73
+##########
74
+
75
+core
76
+
77
+
78
+Steps
79
+#####
80
+
81
+    1. Setup for system tests.
82
+    2. Log in to Horizon Dashboard.
83
+    3. Add private networks net_01 and net_02.
84
+    4. Check taht networks are present in the vcenter.
85
+    5. Remove private network net_01.
86
+    6. Check that network net_01 has been removed from the vcenter.
87
+    7. Add private network net_01.
88
+
89
+
90
+Expected result
91
+###############
92
+
93
+No errors.
94
+
95
+
96
+Check abilities to bind port on NSX to VM, disable and enable this port.
97
+------------------------------------------------------------------------
98
+
99
+
100
+ID
101
+##
102
+
103
+nsxt_ability_to_bind_port
104
+
105
+
106
+Description
107
+###########
108
+
109
+Verifies that system can not manipulate with port(plugin limitation).
110
+
111
+
112
+Complexity
113
+##########
114
+
115
+core
116
+
117
+
118
+Steps
119
+#####
120
+
121
+    1. Log in to Horizon Dashboard.
122
+    2. Navigate to Project -> Compute -> Instances
123
+    3. Launch instance VM_1 with image TestVM-VMDK and flavor m1.tiny in vcenter az.
124
+    4. Launch instance VM_2 with image TestVM and flavor m1.tiny in nova az.
125
+    5. Verify that VMs should communicate between each other. Send icmp ping from VM_1 to VM_2 and vice versa.
126
+    6. Disable NSX_port of VM_1.
127
+    7. Verify that VMs should communicate between each other. Send icmp ping from VM_2 to VM_1 and vice versa.
128
+    8. Enable NSX_port of VM_1.
129
+    9. Verify that VMs should communicate between each other. Send icmp ping from VM_1 to VM_2 and vice versa.
130
+
131
+
132
+Expected result
133
+###############
134
+
135
+Pings should get a response.
136
+
137
+
138
+Check abilities to assign multiple vNIC to a single VM.
139
+-------------------------------------------------------
140
+
141
+
142
+ID
143
+##
144
+
145
+nsxt_multi_vnic
146
+
147
+
148
+Description
149
+###########
150
+
151
+Check abilities to assign multiple vNICs to a single VM.
152
+
153
+
154
+Complexity
155
+##########
156
+
157
+core
158
+
159
+
160
+Steps
161
+#####
162
+
163
+    1. Setup for system tests.
164
+    2. Log in to Horizon Dashboard.
165
+    3. Add two private networks (net01 and net02).
166
+    4. Add one subnet (net01_subnet01: 192.168.101.0/24, net02_subnet01, 192.168.101.0/24) to each network.
167
+       NOTE: We have a constraint about network interfaces. One of subnets should have gateway and another should not. So disable gateway on that subnet.
168
+    5. Launch instance VM_1 with image TestVM-VMDK and flavor m1.tiny in vcenter az.
169
+    6. Launch instance VM_2 with image TestVM and flavor m1.tiny in nova az.
170
+    7. Check abilities to assign multiple vNIC net01 and net02 to VM_1.
171
+    8. Check abilities to assign multiple vNIC net01 and net02 to VM_2.
172
+    9. Send icmp ping from VM_1 to VM_2 and vice versa.
173
+
174
+
175
+Expected result
176
+###############
177
+
178
+VM_1 and VM_2 should be attached to multiple vNIC net01 and net02. Pings should get a response.
179
+
180
+
181
+Check connectivity between VMs attached to different networks with a router between them.
182
+-----------------------------------------------------------------------------------------
183
+
184
+
185
+ID
186
+##
187
+
188
+nsxt_connectivity_diff_networks
189
+
190
+
191
+Description
192
+###########
193
+
194
+Test verifies that there is a connection between networks connected through the router.
195
+
196
+
197
+Complexity
198
+##########
199
+
200
+core
201
+
202
+
203
+Steps
204
+#####
205
+
206
+    1. Setup for system tests.
207
+    2. Log in to Horizon Dashboard.
208
+    3. Add two private networks (net01 and net02).
209
+    4. Add one subnet (net01_subnet01: 192.168.101.0/24, net02_subnet01, 192.168.101.0/24) to each network. Disable gateway for all subnets.
210
+    5. Navigate to Project -> Compute -> Instances
211
+    6. Launch instances VM_1 and VM_2 in the network 192.168.101.0/24 with image TestVM-VMDK and flavor m1.tiny in vcenter az. Attach default private net as a NIC 1.
212
+    7. Launch instances VM_3 and VM_4 in the network 192.168.101.0/24 with image TestVM and flavor m1.tiny in nova az. Attach default private net as a NIC 1.
213
+    8. Verify that VMs of same networks should communicate
214
+       between each other. Send icmp ping from VM_1 to VM_2, VM_3 to VM_4 and vice versa.
215
+    9. Verify that VMs of different networks should not communicate
216
+       between each other. Send icmp ping from VM_1 to VM_3, VM_4 to VM_2 and vice versa.
217
+    10. Create Router_01, set gateway and add interface to external network.
218
+    11. Enable gateway on subnets. Attach private networks to router.
219
+    12. Verify that VMs of different networks should communicate between each other. Send icmp ping from VM_1 to VM_3, VM_4 to VM_2 and vice versa.
220
+    13. Add new Router_02, set gateway and add interface to external network.
221
+    14. Detach net_02 from Router_01 and attach to Router_02
222
+    15. Assign floating IPs for all created VMs.
223
+    16. Verify that VMs of different networks should communicate between each other by FIPs. Send icmp ping from VM_1 to VM_3, VM_4 to VM_2 and vice versa.
224
+
225
+
226
+Expected result
227
+###############
228
+
229
+Pings should get a response.
230
+
231
+
232
+Check isolation between VMs in different tenants.
233
+-------------------------------------------------
234
+
235
+
236
+ID
237
+##
238
+
239
+nsxt_different_tenants
240
+
241
+
242
+Description
243
+###########
244
+
245
+Verifies isolation in different tenants.
246
+
247
+
248
+Complexity
249
+##########
250
+
251
+core
252
+
253
+
254
+Steps
255
+#####
256
+
257
+    1. Setup for system tests.
258
+    2. Log in to Horizon Dashboard.
259
+    3. Create non-admin tenant test_tenant.
260
+    4. Navigate to Identity -> Projects.
261
+    5. Click on Create Project.
262
+    6. Type name test_tenant.
263
+    7. On tab Project Members add admin with admin and member.
264
+       Activate test_tenant project by selecting at the top panel.
265
+    8. Navigate to Project -> Network -> Networks
266
+    9. Create network with 2 subnet.
267
+       Create Router, set gateway and add interface.
268
+    10. Navigate to Project -> Compute -> Instances
269
+    11. Launch instance VM_1
270
+    12. Activate default tenant.
271
+    13. Navigate to Project -> Network -> Networks
272
+    14. Create network with subnet.
273
+        Create Router, set gateway and add interface.
274
+    15. Navigate to Project -> Compute -> Instances
275
+    16. Launch instance VM_2.
276
+    17. Verify that VMs on different tenants should not communicate between each other. Send icmp ping from VM_1 of admin tenant to VM_2 of test_tenant and vice versa.
277
+
278
+
279
+Expected result
280
+###############
281
+
282
+Pings should not get a response.
283
+
284
+
285
+Check connectivity between VMs with same ip in different tenants.
286
+-----------------------------------------------------------------
287
+
288
+
289
+ID
290
+##
291
+
292
+nsxt_same_ip_different_tenants
293
+
294
+
295
+Description
296
+###########
297
+
298
+Verifies connectivity with same IP in different tenants.
299
+
300
+
301
+Complexity
302
+##########
303
+
304
+advanced
305
+
306
+
307
+Steps
308
+#####
309
+
310
+    1. Setup for system tests.
311
+    2. Log in to Horizon Dashboard.
312
+    3. Create 2 non-admin tenants 'test_1' and 'test_2'.
313
+    4. Navigate to Identity -> Projects.
314
+    5. Click on Create Project.
315
+    6. Type name 'test_1' of tenant.
316
+    7. Click on Create Project.
317
+    8. Type name 'test_2' of tenant.
318
+    9. On tab Project Members add admin with admin and member.
319
+    10. In tenant 'test_1' create net1 and subnet1 with CIDR 10.0.0.0/24
320
+    11. In tenant 'test_1' create security group 'SG_1' and add rule that allows ingress icmp traffic
321
+    12. In tenant 'test_2' create net2 and subnet2 with CIDR 10.0.0.0/24
322
+    13. In tenant 'test_2' create security group 'SG_2'
323
+    14. In tenant 'test_1' add VM_1 of vcenter in net1 with ip 10.0.0.4 and 'SG_1' as security group.
324
+    15. In tenant 'test_1' add VM_2 of nova in net1 with ip 10.0.0.5 and 'SG_1' as security group.
325
+    16. In tenant 'test_2' create net1 and subnet1 with CIDR 10.0.0.0/24
326
+    17. In tenant 'test_2' create security group 'SG_1' and add rule that allows ingress icmp traffic
327
+    18. In tenant 'test_2' add VM_3 of vcenter in net1 with ip 10.0.0.4 and 'SG_1' as security group.
328
+    19. In tenant 'test_2' add VM_4 of nova in net1 with ip 10.0.0.5 and 'SG_1' as security group.
329
+    20. Assign floating IPs for all created VMs.
330
+    21. Verify that VMs with same ip on different tenants should communicate between each other by FIPs. Send icmp ping from VM_1 to VM_3, VM_2 to Vm_4 and vice versa.
331
+
332
+
333
+Expected result
334
+###############
335
+
336
+Pings should get a response.
337
+
338
+
339
+Check connectivity Vms to public network.
340
+-----------------------------------------
341
+
342
+
343
+ID
344
+##
345
+
346
+nsxt_public_network_availability
347
+
348
+
349
+Description
350
+###########
351
+
352
+Verifies that public network is available.
353
+
354
+
355
+Complexity
356
+##########
357
+
358
+core
359
+
360
+
361
+Steps
362
+#####
363
+
364
+    1. Setup for system tests.
365
+    2. Log in to Horizon Dashboard.
366
+    3. Create net01: net01_subnet, 192.168.111.0/24 and attach it to the router04
367
+    4. Launch instance VM_1 of vcenter az with image TestVM-VMDK and flavor m1.tiny in the net_04.
368
+    5. Launch instance VM_1 of nova az with image TestVM and flavor m1.tiny in the net_01.
369
+    6. Send ping from instances VM_1 and VM_2 to 8.8.8.8.
370
+
371
+
372
+Expected result
373
+###############
374
+
375
+Pings should get a response.
376
+
377
+
378
+Check connectivity VMs to public network with floating ip.
379
+----------------------------------------------------------
380
+
381
+
382
+ID
383
+##
384
+
385
+nsxt_floating_ip_to_public
386
+
387
+
388
+Description
389
+###########
390
+
391
+Verifies that public network is available via floating ip.
392
+
393
+
394
+Complexity
395
+##########
396
+
397
+core
398
+
399
+
400
+Steps
401
+#####
402
+
403
+    1. Setup for system tests.
404
+    2. Log in to Horizon Dashboard
405
+    3. Create net01: net01_subnet, 192.168.111.0/24 and attach it to the router04
406
+    4. Launch instance VM_1 of vcenter az with image TestVM-VMDK and flavor m1.tiny in the net_04. Associate floating ip.
407
+    5. Launch instance VM_1 of nova az with image TestVM and flavor m1.tiny in the net_01. Associate floating ip.
408
+    6. Send ping from instances VM_1 and VM_2 to 8.8.8.8.
409
+
410
+
411
+Expected result
412
+###############
413
+
414
+Pings should get a response
415
+
416
+
417
+Check abilities to create and delete security group.
418
+----------------------------------------------------
419
+
420
+
421
+ID
422
+##
423
+
424
+nsxt_create_and_delete_secgroups
425
+
426
+
427
+Description
428
+###########
429
+
430
+Verifies that creation and removing security group works fine.
431
+
432
+
433
+Complexity
434
+##########
435
+
436
+advanced
437
+
438
+
439
+Steps
440
+#####
441
+
442
+    1. Setup for system tests.
443
+    2. Log in to Horizon Dashboard.
444
+    3. Launch instance VM_1 in the tenant network net_02 with image TestVM-VMDK and flavor m1.tiny in vcenter az.
445
+    4. Launch instance VM_2 in the tenant network net_02 with image TestVM and flavor m1.tiny in nova az.
446
+    5. Create security groups SG_1 to allow ICMP traffic.
447
+    6. Add Ingress rule for ICMP protocol to SG_1
448
+    7. Attach SG_1 to VMs
449
+    8. Check ping between VM_1 and VM_2 and vice verse
450
+    9. Create security groups SG_2 to allow TCP traffic 22 port.
451
+       Add Ingress rule for TCP protocol to SG_2
452
+    10. Attach SG_2 to VMs.
453
+    11. ssh from VM_1 to VM_2 and vice verse.
454
+    12. Delete custom rules from SG_1 and SG_2.
455
+    13. Check ping and ssh aren't available from VM_1 to VM_2 and vice verse.
456
+    14. Add Ingress rule for ICMP protocol to SG_1.
457
+    15. Add Ingress rule for SSH protocol to SG_2.
458
+    16. Check ping between VM_1 and VM_2 and vice verse.
459
+    17. Check ssh from VM_1 to VM_2 and vice verse.
460
+    18. Attach VMs to default security group.
461
+    19. Delete security groups.
462
+    20. Check ping between VM_1 and VM_2 and vice verse.
463
+    21. Check SSH from VM_1 to VM_2 and vice verse.
464
+
465
+
466
+Expected result
467
+###############
468
+
469
+We should be able to send ICMP and TCP traffic between VMs in different tenants.
470
+
471
+
472
+Verify that only the associated MAC and IP addresses can communicate on the logical port.
473
+-----------------------------------------------------------------------------------------
474
+
475
+
476
+ID
477
+##
478
+
479
+nsxt_associated_addresses_communication_on_port
480
+
481
+
482
+Description
483
+###########
484
+
485
+Verify that only the associated MAC and IP addresses can communicate on the logical port.
486
+
487
+
488
+Complexity
489
+##########
490
+
491
+core
492
+
493
+
494
+Steps
495
+#####
496
+
497
+    1. Setup for system tests.
498
+    2. Log in to Horizon Dashboard.
499
+    3. Launch 2 instances in each az.
500
+    4. Verify that traffic can be successfully sent from and received on the MAC and IP address associated with the logical port.
501
+    5. Configure a new IP address from the subnet not like original one on the instance associated with the logical port.
502
+        * ifconfig eth0 down
503
+        * ifconfig eth0 192.168.99.14 netmask 255.255.255.0
504
+        * ifconfig eth0 up
505
+    6. Confirm that the instance cannot communicate with that IP address.
506
+    7. Revert IP address. Configure a new MAC address on the instance associated with the logical port.
507
+        * ifconfig eth0 down
508
+        * ifconfig eth0 hw ether 00:80:48:BA:d1:30
509
+        * ifconfig eth0 up
510
+    8. Confirm that the instance cannot communicate with that MAC address and the original IP address.
511
+
512
+
513
+Expected result
514
+###############
515
+
516
+Instance should not communicate with new ip and mac addresses but it should communicate with old IP.
517
+
518
+
519
+Check creation instance in the one group simultaneously.
520
+--------------------------------------------------------
521
+
522
+
523
+ID
524
+##
525
+
526
+nsxt_create_and_delete_vms
527
+
528
+
529
+Description
530
+###########
531
+
532
+Verifies that system could create and delete several instances simultaneously.
533
+
534
+
535
+Complexity
536
+##########
537
+
538
+core
539
+
540
+
541
+Steps
542
+#####
543
+
544
+    1. Setup for system tests.
545
+    2. Navigate to Project -> Compute -> Instances
546
+    3. Launch 5 instance VM_1 simultaneously with image TestVM-VMDK and flavor m1.tiny in vcenter az in default net_04.
547
+    4. All instance should be created without any error.
548
+    5. Launch 5 instance VM_2 simultaneously with image TestVM and flavor m1.tiny in nova az in default net_04.
549
+    6. All instance should be created without any error.
550
+    7. Check connection between VMs (ping, ssh)
551
+    8. Delete all VMs from horizon simultaneously.
552
+
553
+
554
+Expected result
555
+###############
556
+
557
+All instance should be created and deleted without any error.
558
+
559
+
560
+Verify that instances could be launched on enabled compute host
561
+---------------------------------------------------------------
562
+
563
+
564
+ID
565
+##
566
+
567
+nsxt_disable_hosts
568
+
569
+
570
+Description
571
+###########
572
+
573
+Check instance creation on enabled cluster.
574
+
575
+
576
+Complexity
577
+##########
578
+
579
+core
580
+
581
+
582
+Steps
583
+#####
584
+
585
+    1. Setup cluster with 3 controllers, 2 Compute nodes and cinder-vmware +
586
+       compute-vmware role.
587
+    2. Assign instances in each az.
588
+    3. Disable one of compute host with vCenter cluster
589
+       (Admin -> Hypervisors).
590
+    4. Create several instances in vcenter az.
591
+    5. Check that instances were created on enabled compute host
592
+       (vcenter cluster).
593
+    6. Disable second compute host with vCenter cluster and enable
594
+       first one.
595
+    7. Create several instances in vcenter az.
596
+    8. Check that instances were created on enabled compute host
597
+       (vcenter cluster).
598
+    9. Create several instances in nova az.
599
+    10. Check that instances were created on enabled compute host
600
+        (nova cluster).
601
+
602
+
603
+Expected result
604
+###############
605
+
606
+All instances work fine.
607
+
608
+
609
+Check that settings about new cluster are placed in neutron config
610
+------------------------------------------------------------------
611
+
612
+
613
+ID
614
+##
615
+
616
+nsxt_smoke_add_compute
617
+
618
+
619
+Description
620
+###########
621
+
622
+Adding compute-vmware role and redeploy cluster with NSX-T plugin has effect in neutron configs.
623
+
624
+
625
+Complexity
626
+##########
627
+
628
+core
629
+
630
+
631
+Steps
632
+#####
633
+
634
+    1. Upload the NSX-T plugin to master node.
635
+    2. Create cluster and configure NSX-T for that cluster.
636
+    3. Provision three controller node.
637
+    4. Deploy cluster.
638
+    5. Get configured clusters morefid(Managed Object Reference) from neutron config.
639
+    6. Add node with compute-vmware role.
640
+    7. Redeploy cluster with new node.
641
+    8. Get new configured clusters morefid from neutron config.
642
+    9. Check new cluster added in neutron config.
643
+
644
+
645
+Expected result
646
+###############
647
+
648
+Clusters are reconfigured after compute-vmware has been added.
649
+
650
+
651
+Fuel create mirror and update core repos on cluster with NSX-T plugin
652
+---------------------------------------------------------------------
653
+
654
+
655
+ID
656
+##
657
+
658
+nsxt_update_core_repos
659
+
660
+
661
+Description
662
+###########
663
+
664
+Fuel create mirror and update core repos in cluster with NSX-T plugin
665
+
666
+
667
+Complexity
668
+##########
669
+
670
+core
671
+
672
+
673
+Steps
674
+#####
675
+
676
+    1. Setup for system tests
677
+    2. Log into controller node via Fuel CLI and get PIDs of services which were launched by plugin and store them:
678
+        `ps ax | grep neutron-server`
679
+    3. Launch the following command on the Fuel Master node:
680
+        `fuel-mirror create -P ubuntu -G mos ubuntu`
681
+    4. Run the command below on the Fuel Master node:
682
+        `fuel-mirror apply -P ubuntu -G mos ubuntu --env <env_id> --replace`
683
+    5. Run the command below on the Fuel Master node:
684
+        `fuel --env <env_id> node --node-id <node_ids_separeted_by_coma> --tasks setup_repositories`
685
+        And wait until task is done.
686
+    6. Log into controller node and check plugins services are alive and their PID are not changed.
687
+    7. Check all nodes remain in ready status.
688
+    8. Rerun OSTF.
689
+
690
+Expected result
691
+###############
692
+
693
+Cluster (nodes) should remain in ready state.
694
+OSTF tests should be passed on rerun.
695
+
696
+
697
+Configuration with multiple NSX managers
698
+----------------------------------------
699
+
700
+
701
+ID
702
+##
703
+
704
+nsxt_multiple_nsx_managers
705
+
706
+
707
+Description
708
+###########
709
+
710
+NSX-T plugin can configure several NSX managers at once.
711
+
712
+
713
+Complexity
714
+##########
715
+
716
+core
717
+
718
+
719
+Steps
720
+#####
721
+
722
+    1. Create cluster.
723
+       Prepare 2 NSX managers.
724
+    2. Configure plugin.
725
+    3. Set comma separtated list of NSX managers.
726
+       nsx_api_managers = 1.2.3.4,1.2.3.5
727
+    4. Deploy cluster.
728
+    5. Run OSTF.
729
+    6. Power off the first NSX manager.
730
+    7. Run OSTF.
731
+    8. Power off the second NSX manager.
732
+       Power on the first NSX manager.
733
+    9. Run OSTF.
734
+
735
+
736
+Expected result
737
+###############
738
+
739
+OSTF tests should be passed.
740
+
741
+
742
+Deploy HOT
743
+----------
744
+
745
+
746
+ID
747
+##
748
+
749
+nsxt_hot
750
+
751
+
752
+Description
753
+###########
754
+
755
+Template creates flavor, net, security group, instance.
756
+
757
+
758
+Complexity
759
+##########
760
+
761
+smoke
762
+
763
+
764
+Steps
765
+#####
766
+
767
+    1. Deploy cluster with NSX.
768
+    2. Copy nsxt_stack.yaml to controller on which heat will be run.
769
+    3. On controller node run command::
770
+
771
+         . ./openrc
772
+         heat stack-create -f nsxt_stack.yaml teststack
773
+
774
+       Wait for status COMPLETE.
775
+    4. Run OSTF.
776
+
777
+
778
+Expected result
779
+###############
780
+All OSTF are passed.

Loading…
Cancel
Save