Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VNFS image oversize #10

Open
diedpigs opened this issue Oct 8, 2018 · 0 comments
Open

VNFS image oversize #10

diedpigs opened this issue Oct 8, 2018 · 0 comments

Comments

@diedpigs
Copy link
Collaborator

diedpigs commented Oct 8, 2018

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?

diedpigs pushed a commit to diedpigs/CRI_XCBC that referenced this issue Feb 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant