Template: OSCI impact moved under Infra impact

OSCI is now part of Fuel project infrastructure, so relevant questions
in the spec template were moved under Infrastructure impact, and a
separate section for OSCI impact was removed.

Following 8.0 specs updated for the new structure:
* build-fuel-rpm-packages-for-centos7

Change-Id: Ibd99c9de0ca1a4c8f8e6a2e4eb1bb5d91ba105a4

specs/8.0/build-fuel-rpm-packages-for-centos7.rst

@@ -198,9 +198,9 @@ There is no impact on developing process, since packages for both CentOS 6
 and CentOS 7 will be built and appear on mirrors on the same gerrit events
 
 
---------------------------------
-Infrastructure/operations impact
---------------------------------
+---------------------
+Infrastructure impact
+---------------------
 
 * Expected jobs workload (building/publishing) will be double increased,
   because of triggering two sets of jobs (for CentOS 6 and 7) in parallel
@@ -262,17 +262,6 @@ Infrastructure/operations impact
                             Picture 1 - Zuul schema
 
 
---------------------
-Documentation impact
---------------------
-
-All infrastructure changes should be documented
-
-
---------------------
-Expected OSCI impact
---------------------
-
 Related mirrors should be created/rsynced to all location with the `base`
 path defined below:
 
@@ -285,7 +274,14 @@ path defined below:
 +----------+---------------------------------------+
 
 Fuel packages naming schema must correspond to those that is described in spec
-`separate-mos-from-centos`_
+`separate-mos-from-centos`_.
+
+
+--------------------
+Documentation impact
+--------------------
+
+All infrastructure changes should be documented
 
 
 --------------

specs/template.rst

@@ -346,9 +346,9 @@ such as:
   drivers would implement the feature is required.
 
 
---------------------------------
-Infrastructure/operations impact
---------------------------------
+---------------------
+Infrastructure impact
+---------------------
 
 Explain what changes in project infrastructure will be required to support the
 proposed change. Consider the following:
@@ -357,8 +357,8 @@ proposed change. Consider the following:
   consume more CPU, network, or storage capacity? Will it increase the number
   of scheduled jobs?
 
-* Will it require new work-flows or changes in existing work-flows implemented
-  in CI, packaging, source code management, code review, or software artifact
+* Will it require new workflows or changes in existing workflows implemented in
+  CI, packaging, source code management, code review, or software artifact
   publishing tools?
 
   * Will it require new or upgraded tools or services to be deployed on project
@@ -370,6 +370,11 @@ proposed change. Consider the following:
 
   * Will it introduce new release artifacts?
 
+  * Will it require changes to package dependencies: new packages, updated
+    package versions?
+
+  * Will it require changes to the structure of any package repositories?
+
 * Will it require changes in build environments of any existing CI jobs? Would
   such changes be backwards compatible with previous Fuel releases currently
   supported by project infrastructure?
@@ -384,20 +389,6 @@ donating resources to the docs team to have the documentation updated. Don't
 repeat details discussed above, but please reference them here.
 
 
---------------------
-Expected OSCI impact
---------------------
-
-Expected and known impact to OSCI should be described here. Please mention
-whether:
-
-* There are new packages that should be added to the mirror
-
-* Version for some packages should be changed
-
-* Some changes to the mirror itself are required
-
-
 --------------
 Implementation
 --------------

tests/test_titles.py

@@ -34,10 +34,9 @@ class TestTitles(base.BaseDocTest):
         'Performance impact': None,
         'Deployment impact': None,
         'Developer impact': None,
-        'Infrastructure/operations impact': None,
+        'Infrastructure impact': None,
         'Notifications impact': None,
         'Documentation impact': None,
-        'Expected OSCI impact': None,
         'Implementation': {
             'Assignee(s)': None,
             'Dependencies': None,