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.

Sign up for GitHub

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

Jump to bottom

gitlab-ci: enable script for VBOX VMs orchestrate #5056

Closed
avtikhon opened this issue Jun 7, 2020 · 1 comment
Closed

gitlab-ci: enable script for VBOX VMs orchestrate #5056

avtikhon opened this issue Jun 7, 2020 · 1 comment
Assignees
@avtikhon
Labels
feature A new functionality qa Issues related to tests or testing subsystem
Projects
Quality Assurance

Comments

@avtikhon
Copy link
Contributor

avtikhon commented Jun 7, 2020

Tarantool version:
All

OS version:
Freebsd *
all VM VBOX based OS

Bug description:

Steps to reproduce:

Optional (but very desirable):

  • coredump
  • backtrace
  • netstat
@avtikhon avtikhon added feature A new functionality qa Issues related to tests or testing subsystem labels Jun 7, 2020
@avtikhon avtikhon self-assigned this Jun 7, 2020
avtikhon added a commit that referenced this issue Jun 7, 2020
@avtikhon
gitlab-ci: add script for VBOX VMs orchestrate
85d5ce0 
Added 'tools/run_vm.sh' script for VBOX VMs orchestrate.
It starts the VM on the local host at the previously
prepared configurations. It uses the template in options:
  freebsd_12_*|<OS_DIST>_*
to be able to choose free VM from the list:
  freebsd_12_[1-X]|<OS_DIST>_[1-X]

Gitlab-ci orchestrator chooses the host, where it's job can
be run, so to make it always workable without delays in
waiting the free VMs by the new local orchestrator script,
the limit of the overall started jobs must be not bigger
than requested template can find the appropriate VMs on the
host. Each of the template can use up to X pre-configured
VMs, so the gitlab-runner configuration file:
  /etc/gitlab-runner/config.toml
has common configuration option:
  concurrent = X
and each gitlab runner has limit option:
  limit = X
X value should be manually found by testing at each used host.

Closes #5056
@avtikhon avtikhon added this to ON REVIEW in Quality Assurance Jun 7, 2020
avtikhon added a commit that referenced this issue Jun 11, 2020
@avtikhon
gitlab-ci: add script for VBOX VMs orchestrate
6df4b10 
Added 'tools/run_vm.sh' script for VBOX VMs orchestrate.
It starts the VM on the local host at the previously
prepared configurations. It uses the template in options:
  freebsd_12_*|<OS_DIST>_*
to be able to choose free VM from the list:
  freebsd_12_[1-X]|<OS_DIST>_[1-X]

Gitlab-ci orchestrator chooses the host, where it's job can
be run, so to make it always workable without delays in
waiting the free VMs by the new local orchestrator script,
the limit of the overall started jobs must be not bigger
than requested template can find the appropriate VMs on the
host. Each of the template can use up to X pre-configured
VMs, so the gitlab-runner configuration file:
  /etc/gitlab-runner/config.toml
has common configuration option:
  concurrent = X
and each gitlab runner has limit option:
  limit = X
X value should be manually found by testing at each used host.

Closes #5056
@ylobankov
Copy link
Member

Not relevant anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@avtikhon avtikhon

Labels
feature A new functionality qa Issues related to tests or testing subsystem
Projects
No open projects
Quality Assurance
ON REVIEW
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ylobankov @avtikhon