NFD

I believe I should wait till the official vagrant box for this version gets released?

No. We no longer use official boxes (specifically, Ubuntu ones), as they are not really designed to be used (honestly, I have no clue why they exist, as they are not usable). Eric created custom boxes, I think he left instructions on how to do it or just email him.

Eric created custom boxes, I think he left instructions on how to do it or just email him.

Eric uses boxcutter. His scripts are at https://github.com/eric135/ndn-jenkins-ubuntu. Boxcutter no longer offers built images so Eric has to build his own.

I would suggest bento instead. They publish built images. Bento is the base of yoursunny's NFD devbox and it works well.

Hi everyone. I figured I'd offer my input on this:

There were multiple reasons why I created custom boxes. For one, I couldn't find any good 17.10 boxes at the time, given the recency of that release. Second, when running the integration testing suite on Vagrant, a good chunk of time was spent installing Ubuntu dependency packages. Therefore, I created boxes with the dependency packages pre-installed to speed up the integration testing environment, as well as the deployment of new Jenkins agents.

I based my boxes on boxcutter because we had had good luck with their boxes in the past. Additionally, they provided straightforward instructions on how to build their boxes, as well as user-friendly ways to modify the box configuration scripts. I've never really taken a look at bento, but they may provide the same.

Does bento provide any benefit over boxcutter when creating custom boxes? Particularly enough to justify the effort needed to switch the custom boxes away from boxcutter.

Does bento provide any benefit over boxcutter when creating custom boxes?

bento publishes pre-built boxes. There's no need to build a custom box.

I created boxes with the dependency packages pre-installed to speed up the integration testing environment

This can cause integ to run with older dependencies, which is undesirable. This is also inapplicable to Jenkins, where boxes are persistent.

Junxiao Shi wrote:

This can cause integ to run with older dependencies, which is undesirable.

Disagree. That's really not an issue. Ubuntu doesn't release any major upgrade of any packages (that we care about) during the life cycle of one distro version, they only publish bug and security fixes, which make virtually zero difference for us. Speeding up integration test runs is more important that running the absolute latest version.

On the other hand, I agree that the argument of reusing the same custom box for jenkins and the integration tests doesn't apply in this case, because it seems that we've usually run integ on LTS releases, and 18.10 is not an LTS release.

Junxiao Shi wrote:

I created boxes with the dependency packages pre-installed to speed up the integration testing environment

This can cause integ to run with older dependencies, which is undesirable. This is also inapplicable to Jenkins, where boxes are persistent.

The integ tests script updates all the packages to avoid this. However, if the box is kept up-to-date, the package upgrade delays will be greatly reduced.

Update: the previous box is having issues with DNS resolver. So switched to this: https://app.vagrantup.com/lasp/boxes/ubuntu18.10.

[ Old ] I took the box from https://app.vagrantup.com/generic/boxes/ubuntu1810. It's up and running on maestro. I'll add it to Jenkins by today.

Added for NFD and ndn-cxx. Running on test job for ndn-tools. Should this be added to all jobs that currently have 18.04 support?

Md Ashiqur Rahman wrote:

Should this be added to all jobs that currently have 18.04 support?

Yes, unless there are build failures.

So far, for ndn-cxx and NFD, the builds have passed 18.10

Added to all projects. I've also deployed 2nd agent at UA. 2 more at the FIU site should provide a good redundancy.