You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
now in the script, we use a customized template to make chroot environment. line 31-38 in file roles/compute_build_vnfs/tasks/main.yml which will install a bunch of software defined in templates roles/compute_build_vnfs/templates/extend_compute_packages.j2 and roles/compute_build_vnfs/templates/base_packages.j2.
After wwmkchroot, this customized environment will have footprint of 1.3G which is around 900M bigger than default centos-7 environment, 451M.
I am not sure what in the customized list of packages is needed but after all the required packages are installed, the chroot environment will become 2.7G which will cause compute node privisioning failed due to lack of memory.
So should we move back to default environment or just increase memory size of compute node?
The text was updated successfully, but these errors were encountered:
diedpigs
pushed a commit
to diedpigs/CRI_XCBC
that referenced
this issue
Feb 13, 2019
now in the script, we use a customized template to make chroot environment. line 31-38 in file
roles/compute_build_vnfs/tasks/main.yml
which will install a bunch of software defined in templatesroles/compute_build_vnfs/templates/extend_compute_packages.j2
androles/compute_build_vnfs/templates/base_packages.j2
.After wwmkchroot, this customized environment will have footprint of 1.3G which is around 900M bigger than default centos-7 environment, 451M.
I am not sure what in the customized list of packages is needed but after all the required packages are installed, the chroot environment will become 2.7G which will cause compute node privisioning failed due to lack of memory.
So should we move back to default environment or just increase memory size of compute node?
The text was updated successfully, but these errors were encountered: