Project

General

Profile

Actions
Copy link

User story #2351

closed

Create a Vagrant configuration for Rudder

Added by Matthieu CERDA about 12 years ago. Updated about 9 years ago.

Status:
Released
Priority:
5
Assignee:
Matthieu CERDA
Category:
Vagrant
Target version:
-
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Create a Vagrant configuration for Rudder, enabling the user to quickly deploy a Rudder environment to play or develop with

Actions
Copy link
 #1

Updated by Matthieu CERDA about 12 years ago

  • Status changed from New to Pending technical review
  • % Done changed from 0 to 100

Applied in changeset commit:e4433b4c8e0e69722fe2793438bb61c55a038b0e.

Actions
Copy link
 #2

Updated by Jonathan CLARKE about 12 years ago

  • Status changed from Pending technical review to Discussion
  • Target version changed from 2.4.0~alpha6 to 2.4.0~alpha7
I just had a look at this, and it looks great! I have a few comments and questions:
  • To DRY-ify the script and make it a bit less resource intensive, you should call "lsb_release -cs" only once, and store the result in a variable, instead of calling it many times.
  • Why is "aptitude ${APTITUDE_ARGS} install debian-archive-keyring" necessary? We don't use these keys on our repos...
  • Why allow all connections to LDAP and PSQL? This is not necessary for normal behaviour. If there is a reason, please explain in a comment in the Vagrantfile, so that people reading this don't think it's required. If it's not, please remove it so that we don't have unrequired complexity.
  • Why do you add the CFEngine cron check in /etc/crontab? It is done automatically by CFEngine when it starts, so this is duplicated effort. If there is a reason, please explain in a comment in the Vagrantfile, so that people reading this don't think it's required.
  • Could you group together all commands you use to setup a functional DNS/hosts config, and add a comment before explaining your assumptions? (ie, what IPs you used, what hostnames are set, where, etc)
Actions
Copy link
 #3

Updated by Matthieu CERDA about 12 years ago

  • Status changed from Discussion to In progress
  • % Done changed from 100 to 80
  • OK ! I'll do it right away
  • I install debian-archive-keyring because some boxes seems to come without it... I thought maybe "just in case" I would add it.
  • Indeed, authorizing all connexions is not necessary. I will remove it.
  • I add the crontab entry because right after the installation the rudder-agent is not launched (to grant the user the time to prepare the policy_server.dat), and thus I thought it was an elegant way to start the rudder node without it having the edit the cron.
    But it can be replaced with the init.d script.
  • OK !

I'm working on it.

Actions
Copy link
 #4

Updated by Jonathan CLARKE about 12 years ago

Matthieu CERDA wrote:

  • OK ! I'll do it right away
  • I install debian-archive-keyring because some boxes seems to come without it... I thought maybe "just in case" I would add it.

All that matters is that the vagrant box that we use has it :) If it does, please remove it, no point in running things for no reason.

  • Indeed, authorizing all connexions is not necessary. I will remove it.
  • I add the crontab entry because right after the installation the rudder-agent is not launched (to grant the user the time to prepare the policy_server.dat), and thus I thought it was an elegant way to start the rudder node without it having the edit the cron.
    But it can be replaced with the init.d script.

Well, that brings up a good point. Why don't you fill out the policy_server.dat file? We know the IP address of the server, you may as well just do it. Then run /etc/init.d/rudder-agent start, thus sticking closely to the docs.

Actions
Copy link
 #5

Updated by Matthieu CERDA about 12 years ago

I verified, and the Debian keyring is already bundled in. I removed the useless package installation.

About the cron entry, you did not understand: I am already adding the policy_server.dat, i was just experimenting another way of starting CFEngine. But you are totally right about sticking to what the doc says, so I replaced the cron edition by a simple /etc/init.d/rudder-agent start as in the doc.

Actions
Copy link
 #6

Updated by Nicolas PERRON about 12 years ago

Could you add:

server_config.vm.customize ["modifyvm", :id, "--memory", "1024"]

In order to ensure that server has enough memory for Rudder, please ?

Actions
Copy link
 #7

Updated by Matthieu CERDA about 12 years ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 80 to 100

Applied in changeset commit:dfc25c98d2f86446a1e9749071ad0a8396214576.

Actions
Copy link
 #8

Updated by Matthieu CERDA about 12 years ago

All done !

Actions
Copy link
 #9

Updated by Nicolas PERRON about 12 years ago

It's better like this and it's good for me. Thanks

Actions
Copy link
 #10

Updated by Jonathan CLARKE almost 12 years ago

  • Status changed from Pending technical review to 10

I just looked through this again, and it all looks good for me.

Just one thing: now that we have Ubuntu packages, it would be simpler to use an Ubuntu box rather than a Debian one... See #2522.

Actions
Copy link
 #11

Updated by Jonathan CLARKE almost 12 years ago

  • Project changed from Rudder to 35
  • Category deleted (11)
Actions
Copy link
 #12

Updated by Jonathan CLARKE almost 12 years ago

  • Status changed from 10 to Released
Actions
Copy link
 #13

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 35 to Rudder tools
  • Category set to Vagrant
Actions
Copy link
 #14

Updated by Benoît PECCATTE about 9 years ago

  • Target version deleted (2.4.0~alpha7)
Actions
Copy link

Also available in: Atom PDF