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

Parameterize the Che Vagrantfile #1531

Closed
creckord opened this issue Jun 20, 2016 · 1 comment
Closed

Parameterize the Che Vagrantfile #1531

creckord opened this issue Jun 20, 2016 · 1 comment
Labels
kind/enhancement A feature request - must adhere to the feature request template.

Comments

@creckord
Copy link
Contributor

We would like to automate setting up Che with the required VirtualBox and Vagrant stack using the Yatta Launcher.

In order to do that, we'd like to make a few changes to the Vagrantfile to better support external configuration. This would include

  • Setting the already available parameters like HTTP_PROXY etc via environment variables
  • Configuration of the network ip address and port
  • More detailed progress output

The goal is to keep the out-of-the-box behavior of the Vagrantfile during a plain vagrant up unchanged as long as the introduced environment variables are unset.

I'll have a pull request with the proposed changes ready in a moment.

creckord added a commit to YattaSolutions/che that referenced this issue Jun 20, 2016
- Introduce environment variables for all settings in the Vagrantfile
- Make the synced user folder configurable via CHE_DATA environment 
variable
- Expose the final Che URL in <user folder>/.che_url

Signed-off-by: Carsten Reckord <reckord@yatta.de>
creckord added a commit to YattaSolutions/che that referenced this issue Jun 20, 2016
- Introduce separate parameters for the container's port and the
binding port on the host
- Allow disabling host port binding by setting the host port to -1

Signed-off-by: Carsten Reckord <reckord@yatta.de>
creckord added a commit to YattaSolutions/che that referenced this issue Jun 20, 2016
- Setting CHE_IP to "dhcp" configures the machine with a dynamic IP
managed by VirtualBox
- The chosen IP is resolved in the provisioning script and handed off
to docker

Signed-off-by: Carsten Reckord <reckord@yatta.de>
creckord added a commit to YattaSolutions/che that referenced this issue Jun 20, 2016
- Setting PROVISION_PROGRESS to "extended" outputs full progress from
docker and yum to better track overall provisioning progress
- Extended progress will additionally install the 'expect' package to 
fool yum and docker into detecting a TTY for extended progress output;
a small overhead (~2MB) for much better progress during the bulk of the
provisioning process
- Default 'vagrant up' progress stays unchanged (using '#' every 10 seconds)

Signed-off-by: Carsten Reckord <reckord@yatta.de>
@ghost ghost added the kind/enhancement A feature request - must adhere to the feature request template. label Jun 21, 2016
TylerJewell pushed a commit that referenced this issue Jun 21, 2016
* (#1531) Parameterize Vagrantfile

- Introduce environment variables for all settings in the Vagrantfile
- Make the synced user folder configurable via CHE_DATA environment 
variable
- Expose the final Che URL in <user folder>/.che_url

Signed-off-by: Carsten Reckord <reckord@yatta.de>

* (#1531) Vagrantfile: Configurable host and container port

- Introduce separate parameters for the container's port and the
binding port on the host
- Allow disabling host port binding by setting the host port to -1

Signed-off-by: Carsten Reckord <reckord@yatta.de>

* (#1531) Vagrantfile: Support DHCP instead of fixed IP

- Setting CHE_IP to "dhcp" configures the machine with a dynamic IP
managed by VirtualBox
- The chosen IP is resolved in the provisioning script and handed off
to docker

Signed-off-by: Carsten Reckord <reckord@yatta.de>

* (#1531) Vagrantfile: Verbose progress

- Setting PROVISION_PROGRESS to "extended" outputs full progress from
docker and yum to better track overall provisioning progress
- Extended progress will additionally install the 'expect' package to 
fool yum and docker into detecting a TTY for extended progress output;
a small overhead (~2MB) for much better progress during the bulk of the
provisioning process
- Default 'vagrant up' progress stays unchanged (using '#' every 10 seconds)

Signed-off-by: Carsten Reckord <reckord@yatta.de>
@creckord
Copy link
Contributor Author

PR #1532 and corresponding artik-ide PR https://github.com/codenvy/artik-ide/pull/69 have been merged. Thanks for the fast review.

tolusha pushed a commit that referenced this issue Jul 5, 2016
* (#1531) Parameterize Vagrantfile

- Introduce environment variables for all settings in the Vagrantfile
- Make the synced user folder configurable via CHE_DATA environment 
variable
- Expose the final Che URL in <user folder>/.che_url

Signed-off-by: Carsten Reckord <reckord@yatta.de>

* (#1531) Vagrantfile: Configurable host and container port

- Introduce separate parameters for the container's port and the
binding port on the host
- Allow disabling host port binding by setting the host port to -1

Signed-off-by: Carsten Reckord <reckord@yatta.de>

* (#1531) Vagrantfile: Support DHCP instead of fixed IP

- Setting CHE_IP to "dhcp" configures the machine with a dynamic IP
managed by VirtualBox
- The chosen IP is resolved in the provisioning script and handed off
to docker

Signed-off-by: Carsten Reckord <reckord@yatta.de>

* (#1531) Vagrantfile: Verbose progress

- Setting PROVISION_PROGRESS to "extended" outputs full progress from
docker and yum to better track overall provisioning progress
- Extended progress will additionally install the 'expect' package to 
fool yum and docker into detecting a TTY for extended progress output;
a small overhead (~2MB) for much better progress during the bulk of the
provisioning process
- Default 'vagrant up' progress stays unchanged (using '#' every 10 seconds)

Signed-off-by: Carsten Reckord <reckord@yatta.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

1 participant