openstack
/
tripleo-incubator
Code Issues Proposed changes

Documents workarounds for tmpfs space errors 

tmpfs space errors result from creating a new seed image on
a system with less than 9GB of RAM. This patch documents
how to prevent the tmpfs space errors by avoiding the use of
tmpfs or specifying a minimum tmpfs size required.
Closes-Bug: 1215298

Change-Id: I89e63bb9a12988c0a4fa9fc781719070c98a0dfa
This commit is contained in:
Ronelle Landy 2014-01-30 05:11:23 -05:00
parent 53b1d0c76f
commit 4884df9c60
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/source/deploying.rst
View File

@ -178,6 +178,21 @@ If you require VLANs you should create a diskimage-builder element to
add the vlan package and vlan configuration to /etc/network/interfaces
as a first-boot rule.
New seed image creation returns tmpfs space errors (systems with < 9GB of RAM)
------------------------------------------------------------------------------
Creating a new seed image takes up to 4.5GB of space inside a /tmp/imageXXXXX
directory. tmpfs can take up to 50% of RAM and systems with less than 9GB of
RAM will fail in this step. When using 'diskimage-builder' directly, you can
prevent the space errors by:
- avoiding tmpfs with --no-tmpfs or
- specifying a minimum tmpfs size required with --min-tmpfs (which can be used
in conjunction with setting the environment variable TMP_DIR to override the
default temporary directory)
If you are using 'boot-seed-vm', set the environment variable DIB_NO_TMPFS=1.
Example deployments (possible today)
====================================