openstack
/
nova-specs
Code Issues Proposed changes

Correct some spell errors 

Change-Id: I41d7f8247724394dbf67ae309965ebeede8cbb45
This commit is contained in:
songwenping 2020-09-02 15:30:06 +08:00
parent afab5cf623
commit 74a6836b17
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
specs/kilo/approved/online-schema-changes.rst
View File

@ -159,7 +159,7 @@ This limits the schema changes that can be safely executed online to
that of the lowest common denominator of databases supported by Nova.
This would also require changes to sqlalchemy-migrate to be able to
manage seperate streams of migrations.
manage separate streams of migrations.
Another option would be remove the use of sqlalchemy-migrate for schema
changes altogether. The 'db sync' command to nova-manage would be

2
specs/train/implemented/virtual-persistent-memory.rst
View File

@ -231,7 +231,7 @@ resource even though they are of the same quantity.
Persistent memory is by nature NUMA sensitive. However for the initial
iteration, the resource inventories are put directly under ROOT resource
provider of the compute host. Persistent memory NUMA affinity will be
adddressed by a seperate follow-on spec.
addressed by a separate follow-on spec.
A change in the configuration will stop the nova compute agent from
(re)starting if that change removes any namespaces in use by guests