From c7068e6828d401f393a04440f7aab2c669aec41e Mon Sep 17 00:00:00 2001 From: lapentafd Date: Tue, 13 Jun 2023 15:07:08 +0100 Subject: [PATCH 1/5] Doc for windows demo --- install-guide/demo-vagrant-windows.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 install-guide/demo-vagrant-windows.md diff --git a/install-guide/demo-vagrant-windows.md b/install-guide/demo-vagrant-windows.md new file mode 100644 index 00000000..04302ced --- /dev/null +++ b/install-guide/demo-vagrant-windows.md @@ -0,0 +1,25 @@ +Steps: +- install git +- install virtualbox +- install vagrant +- open git bash +- `git config --global core.autocrlf false` This is to start the vagrant machine directly from its file. [See what it does here.](https://stackoverflow.com/questions/68264886/what-is-the-correct-core-autocrlf-setting-i-should-use/68265163#68265163) +- `git clone https://github.com/nephio-project/test-infra.git && cd test-infra/e2e/provision` +- `vagrant up` +- `vagrant ssh -- -L 7007:localhost:7007 -L 3000:172.18.0.200:3000` + +Also in order to access the nephio web-ui and gitea web-ui, the vagrant networking will not work on windows for [Hyper-V limitation](https://developer.hashicorp.com/vagrant/docs/providers/hyperv/limitations#limited-networking). +Meanwhile for [Virtualbox](https://developer.hashicorp.com/vagrant/docs/providers/virtualbox/networking#virtualbox-nic-type) (used here) we can create an internal network adding this line to Vagrant.configure: + +`config.vm.network "private_network", ip: "192.168.50.4", virtualbox__intnet: true` + +But the easiest way is to force the port-forwarding in the common way (as shown before): +`vagrant ssh -- -L 7007:localhost:7007 -L 3000:172.18.0.200:3000` + +Tests were done on: +Laptop 1: Windows 11 i7-10750H (16 T) 32GB ram (8VCPU 32GB) +Laptop 2: Windows 10 i5-7200U (4T) 24GB ram (4VCPU 16RAM) + +Note: for low end machines(less then 8T32GB) you need to alter the Vagrant file. This is not recommended! +In the Vagrant file there are _CPUS_ _RAM_ parameters in `config.vm.provider`. +In the ansible "./playbooks/roles/bootstrap/tasks/prechecks.yml" there are the checks for _CPUS_ _RAM_ \ No newline at end of file From d25f66de4a04b3859aaac449e653454c739024cd Mon Sep 17 00:00:00 2001 From: Lapenta Francesco Davide <37077655+lapentad@users.noreply.github.com> Date: Tue, 13 Jun 2023 15:17:57 +0100 Subject: [PATCH 2/5] Update demo-vagrant-windows.md Formatting --- install-guide/demo-vagrant-windows.md | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/install-guide/demo-vagrant-windows.md b/install-guide/demo-vagrant-windows.md index 04302ced..f4e0f246 100644 --- a/install-guide/demo-vagrant-windows.md +++ b/install-guide/demo-vagrant-windows.md @@ -1,4 +1,6 @@ -Steps: +# Nephio demo on Windows + +## Steps: - install git - install virtualbox - install vagrant @@ -14,12 +16,19 @@ Meanwhile for [Virtualbox](https://developer.hashicorp.com/vagrant/docs/provider `config.vm.network "private_network", ip: "192.168.50.4", virtualbox__intnet: true` But the easiest way is to force the port-forwarding in the common way (as shown before): + `vagrant ssh -- -L 7007:localhost:7007 -L 3000:172.18.0.200:3000` -Tests were done on: +## Tests were done on: + Laptop 1: Windows 11 i7-10750H (16 T) 32GB ram (8VCPU 32GB) + Laptop 2: Windows 10 i5-7200U (4T) 24GB ram (4VCPU 16RAM) -Note: for low end machines(less then 8T32GB) you need to alter the Vagrant file. This is not recommended! -In the Vagrant file there are _CPUS_ _RAM_ parameters in `config.vm.provider`. -In the ansible "./playbooks/roles/bootstrap/tasks/prechecks.yml" there are the checks for _CPUS_ _RAM_ \ No newline at end of file +## Notes + +**Warning**: for low end machines(less then 8T32GB) you need to alter the Vagrant file. This is not recommended! + +- In the Vagrant file "./Vagrantfile" there are *CPUS & RAM* parameters in `config.vm.provider`. + +- In the ansible "./playbooks/roles/bootstrap/tasks/prechecks.yml" there are the checks for *CPUS & RAM* From bb556f90d28950b015e8a5e0dd48fd1964f0b341 Mon Sep 17 00:00:00 2001 From: Lapenta Francesco Davide <37077655+lapentad@users.noreply.github.com> Date: Tue, 13 Jun 2023 15:19:57 +0100 Subject: [PATCH 3/5] Update demo-vagrant-windows.md add Networking tag --- install-guide/demo-vagrant-windows.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/install-guide/demo-vagrant-windows.md b/install-guide/demo-vagrant-windows.md index f4e0f246..a7a0d550 100644 --- a/install-guide/demo-vagrant-windows.md +++ b/install-guide/demo-vagrant-windows.md @@ -10,6 +10,8 @@ - `vagrant up` - `vagrant ssh -- -L 7007:localhost:7007 -L 3000:172.18.0.200:3000` +## Networking + Also in order to access the nephio web-ui and gitea web-ui, the vagrant networking will not work on windows for [Hyper-V limitation](https://developer.hashicorp.com/vagrant/docs/providers/hyperv/limitations#limited-networking). Meanwhile for [Virtualbox](https://developer.hashicorp.com/vagrant/docs/providers/virtualbox/networking#virtualbox-nic-type) (used here) we can create an internal network adding this line to Vagrant.configure: @@ -21,9 +23,9 @@ But the easiest way is to force the port-forwarding in the common way (as shown ## Tests were done on: -Laptop 1: Windows 11 i7-10750H (16 T) 32GB ram (8VCPU 32GB) +1. Laptop : Windows 11 i7-10750H (16 T) 32GB ram (8VCPU 32GB) -Laptop 2: Windows 10 i5-7200U (4T) 24GB ram (4VCPU 16RAM) +2. Laptop : Windows 10 i5-7200U (4T) 24GB ram (4VCPU 16RAM) ## Notes From 77b5dafe1c028c9c002cc15d6772964f13a59dd2 Mon Sep 17 00:00:00 2001 From: Lapenta Francesco Davide <37077655+lapentad@users.noreply.github.com> Date: Fri, 16 Jun 2023 07:21:41 +0100 Subject: [PATCH 4/5] Update install-guide/demo-vagrant-windows.md Co-authored-by: Victor Morales --- install-guide/demo-vagrant-windows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/install-guide/demo-vagrant-windows.md b/install-guide/demo-vagrant-windows.md index a7a0d550..1b241ba9 100644 --- a/install-guide/demo-vagrant-windows.md +++ b/install-guide/demo-vagrant-windows.md @@ -3,7 +3,7 @@ ## Steps: - install git - install virtualbox -- install vagrant +- install [vagrant](https://developer.hashicorp.com/vagrant/docs/installation) - open git bash - `git config --global core.autocrlf false` This is to start the vagrant machine directly from its file. [See what it does here.](https://stackoverflow.com/questions/68264886/what-is-the-correct-core-autocrlf-setting-i-should-use/68265163#68265163) - `git clone https://github.com/nephio-project/test-infra.git && cd test-infra/e2e/provision` From f8949ab1ad1fe8c6db00856771843edbd00f1d62 Mon Sep 17 00:00:00 2001 From: lapentafd Date: Fri, 16 Jun 2023 08:16:21 +0100 Subject: [PATCH 5/5] Removal of autocrlf step Signed-off-by: lapentafd --- install-guide/demo-vagrant-windows.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/install-guide/demo-vagrant-windows.md b/install-guide/demo-vagrant-windows.md index 1b241ba9..b7659ece 100644 --- a/install-guide/demo-vagrant-windows.md +++ b/install-guide/demo-vagrant-windows.md @@ -5,7 +5,6 @@ - install virtualbox - install [vagrant](https://developer.hashicorp.com/vagrant/docs/installation) - open git bash -- `git config --global core.autocrlf false` This is to start the vagrant machine directly from its file. [See what it does here.](https://stackoverflow.com/questions/68264886/what-is-the-correct-core-autocrlf-setting-i-should-use/68265163#68265163) - `git clone https://github.com/nephio-project/test-infra.git && cd test-infra/e2e/provision` - `vagrant up` - `vagrant ssh -- -L 7007:localhost:7007 -L 3000:172.18.0.200:3000` @@ -31,6 +30,8 @@ But the easiest way is to force the port-forwarding in the common way (as shown **Warning**: for low end machines(less then 8T32GB) you need to alter the Vagrant file. This is not recommended! -- In the Vagrant file "./Vagrantfile" there are *CPUS & RAM* parameters in `config.vm.provider`. +- In the Vagrant file "./Vagrantfile" there are *CPUS & RAM* parameters in `config.vm.provider`, it's possible to override them at runtime: + + -On Linux, or the Git Bash on Windows we can use one-liner command `CPUS=16 MEMORY=32768 vagrant up` - In the ansible "./playbooks/roles/bootstrap/tasks/prechecks.yml" there are the checks for *CPUS & RAM*