chore(agw): Increase disk size for agw vm

[crasu]

Summary

Disk size for agw containers was increased to 75GB to accomdate build of dockerized agw containers. Vagrant cannot
handle file system resizing for the container - probably because it uses lvm.

Test Plan

Tested increased container size locally. You need to remove all your vms from virtualbox (including the base vm virtualboxes uses for quicker vm setup) to test this.

AGW integ run: https://github.com/crasu/magma/actions/workflows/lte-integ-test.yml

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

feg-workflow

    2 files  203 suites   40s ⏱️
374 tests 374 ✔️ 0 💤 0 ❌
388 runs  388 ✔️ 0 💤 0 ❌

Results for commit 66005e9.

♻️ This comment has been updated with latest results.

[Neudrino]

• Is the disk-size for the VMs dynamically allocated?
• Depending on the above, this might also be an anti-feature if you are developing on a system with limited hard disk space.
• If docker is the culprit, a regular docker clean might be the better option to mitigate the problem?

Out of interest:

• Would the docker build also work outside the AGW VM?

[crasu]

• Is the disk-size for the VMs dynamically allocated?
  yes

• Depending on the above, this might also be an anti-feature if you are developing on a system with limited hard disk space.
  The disk will only get large if you use the space inside the vm. So this should not be an issue on ci and similar.

• If docker is the culprit, a regular docker clean might be the better option to mitigate the problem?
  Currently you have to clean the entire docker cache after every build and even that is not enough. There is only 1-2 GB space left after building the agw.

Out of interest:

• Would the docker build also work outside the AGW VM?
  At the moment we have no way to quickly transfer the containers inside the VM. This would also require to setup parts of the dev tool chain locally which kind of defeats the purpose of the dev vm.

[github-actions]

agw-workflow

615 tests   611 ✔️  4m 26s ⏱️
    2 suites      4 💤
    2 files        0 ❌

Results for commit 66005e9.

♻️ This comment has been updated with latest results.

[github-actions]

dp-workflow

14 tests   14 ✔️  3m 9s ⏱️
  1 suites    0 💤
  1 files      0 ❌

Results for commit 66005e9.

♻️ This comment has been updated with latest results.

[ajahl]

Two times the same parameter ... vagrant-vbguest ... vagrant-vbguest ... ?

[crasu]

fixed

[crasu]

Currently the integ tests fails for this PR. Put it to WIP.

[github-actions]

✔️ The Semantic PR check ended with status success. See instructions on formatting your commit and pull request titles.

[crasu]

Currently the integ tests fails for this PR. Put it to WIP.

Failures seem to be unrelated to these changes

[voisey]

Docs changes look good