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

Improve output of development VM startup #17343

Merged
merged 3 commits into from Sep 16, 2021

Conversation

pchaigno
Copy link
Member

@pchaigno pchaigno commented Sep 8, 2021

Minor clean ups, rewording, and improvements to the development VM startup. See commits for details.

@pchaigno pchaigno added release-note/misc This PR makes changes that have no direct user impact. sig/contributing Impacts contribution workflow, guidelines, and tools. labels Sep 8, 2021
@pchaigno pchaigno requested a review from a team as a code owner September 8, 2021 13:35
Copy link
Member

@aditighag aditighag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Vagrantfile Show resolved Hide resolved
Vagrantfile Outdated Show resolved Hide resolved
It's probably best to avoid suggesting to run:

    export NWORKERS=n
    ./contrib/vagrant/start.sh

First, users tend to forget they export environment variables, so at
least for new contributors, it's probably best to pass the environment
variables in the start.sh command. Second, the above configuration
doesn't make much sense: starting *several* Runtime (i.e., no Kubernetes)
VMs is almost never useful. The user should refer to the development
guide for the appropriate options instead.

Signed-off-by: Paul Chaignon <paul@cilium.io>
In start.sh, we have some code to detect if there are already running
VMs and propose to the user that they stop or delete such VMs. This
commit cleans up the output of that code, by removing unnecessary
newlines and suggestions.

Signed-off-by: Paul Chaignon <paul@cilium.io>
In start.sh, we have some code to detect existing VMs and propose to the
user to delete or stop them. After executing those actions, we can
directly proceed with start.sh and the provisioning of new development
VMs. There's no need for the user to run the command a second time.

Signed-off-by: Paul Chaignon <paul@cilium.io>
@aditighag aditighag added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Sep 16, 2021
@christarazi christarazi changed the title Improve ouput of development VM startup Improve output of development VM startup Sep 16, 2021
@christarazi christarazi merged commit 861228f into cilium:master Sep 16, 2021
@pchaigno pchaigno deleted the improve-vagrant-vm-output branch September 16, 2021 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact. sig/contributing Impacts contribution workflow, guidelines, and tools.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants