openstack/puppet-openstack-integration
Code Issues Proposed changes

Fix outdated number of scenarios mentioned

Browse Source 
Currently we have 5 scenarios instead of 4.

Change-Id: I045d758e09b7639cdca628ea7d230997cd45007b
(cherry picked from commit 02aca06f64)
(cherry picked from commit 0e4898eb4f)
(cherry picked from commit 777ac3e841)
This commit is contained in:
Takashi Kajinami 2024-09-15 00:54:23 +09:00
parent 16d1be6e5a
commit 700ef35536
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -29,7 +29,7 @@ Infrastructure environment.
Description
-----------
OpenStack Infrastructure is deploying four jobs per supported Operating System
OpenStack Infrastructure is deploying 5 jobs per supported Operating System
(Ubuntu and CentOS): scenario001, scenario002, scenario003, scenario004, and
scenario005.
@ -37,7 +37,7 @@ The manifest files under the fixtures directory is used to compose the required
services for each senario. The manifest files under the manifests directory
is used to set up basic set of a single component (like nova, cinder and so on).
OpenStack services are balanced between four scenarios because OpenStack
OpenStack services are balanced between 5 scenarios because OpenStack
Infastructure Jenkins slaves can not afford the load of running everything on
the same node.
One manifest (scenario-aio) is used for people who want to [run a simple All-In-One