The clients in the portal are test clients called "raspberry clients", because when we first developed Network Next, we ran hundreds of test clients around the world on raspberry pi's in people's homes.
As we move forward, we don't want these fake clients running anymore. We only want real clients in the portal.
To do this, open the file terraform/dev/terraform.tfvars and set "disable_raspberry" to true:
Commit your changes to the git repository:
git commit -am "disable raspberry"
git push originThen push a tag to trigger a deploy to dev:
git tag dev-003
git push origin dev-003This process is how you deploy any code or configuration change to the dev backend.
- Commit the change and push to origin
- Tag dev-[n+1]
- Push the tag to origin
The code at the tag is then automatically built and deployed to the dev environment with terraform.
While the deploy is running you can go to "Instance Groups" in google cloud, and watch the deploy.
Notice that each instance template name with "002" is being replaced with "003".
When the deploy completes, you'll see the various "raspberry_*" instance groups now have 0 VM instances each.
The raspberry test server, clients and backend are now disabled.
Go to your portal and you see that the raspberry clients are no longer running.
Up next: Connect a client to the test server.