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

Create a pre-Salted tutorial VM #14876

Closed
whiteinge opened this issue Aug 9, 2014 · 19 comments
Closed

Create a pre-Salted tutorial VM #14876

whiteinge opened this issue Aug 9, 2014 · 19 comments
Labels
Documentation Relates to Salt documentation Feature new functionality including changes to functionality and code refactors, etc.
Milestone

Comments

@whiteinge
Copy link
Contributor

It would be helpful for new users to be able to start a VM with Salt pre-installed as part of a tutorial. Ala Puppet.

Hat-tip to pivwan on Twitter.

@whiteinge whiteinge added this to the Approved milestone Aug 9, 2014
@ingwa
Copy link

ingwa commented Aug 10, 2014

+want :)

@JasonSwindle
Copy link
Contributor

Would a Vagrant setup work as well?

@whiteinge
Copy link
Contributor Author

Yeah, definitely.

@JasonSwindle
Copy link
Contributor

I will try my hand at this. I am going to go for:

Salt Master (Ubuntu)

1] Salt Minion (Ubuntu)

  1. Salt Minion (CentOS)

All in a Vagrantfile, so they don't have to download large files. This setup should allow the user to play with Salt on different host OSes, and learn how to target different distros, What do you think?

-Jason

@whiteinge
Copy link
Contributor Author

Love it. :)

Having multiple distros will be a nice touch.

@cro
Copy link
Contributor

cro commented Aug 12, 2014

Consider using lxc to reduce the resource footprint?

@JasonSwindle
Copy link
Contributor

LXC as in use Docker / Dockerfiles? Or use the Docker provider in
Vagrant? I am open to whatever you guys may think is best. :)

On Tue, Aug 12, 2014 at 11:26 AM, C. R. Oldham notifications@github.com
wrote:

Consider using lxc to reduce the resource footprint?


Reply to this email directly or view it on GitHub
#14876 (comment).

@cro
Copy link
Contributor

cro commented Aug 12, 2014

Well, we don't really need all of Docker, and Ubuntu 14.04's LXC support is
quite good. I just figured the Vagrant box could start up, host the
salt-master, and run the minions in two autostarted full-stack containers.

The only challenge might be finding a good CentOS LXC template. I don't
know if 14.04 has one in the distro.

--cro
C. R. Oldham, Engineer, SaltStack
cr@saltstack.com / 801-564-4673

On Aug 12, 2014, at 11:06, Jason Swindle notifications@github.com wrote:

LXC as in use Docker / Dockerfiles? Or use the Docker provider in
Vagrant? I am open to whatever you guys may think is best. :)

On Tue, Aug 12, 2014 at 11:26 AM, C. R. Oldham notifications@github.com
wrote:

Consider using lxc to reduce the resource footprint?


Reply to this email directly or view it on GitHub
#14876 (comment).


Reply to this email directly or view it on GitHub
#14876 (comment).

@whiteinge
Copy link
Contributor Author

The only concern I have is the end result must be simple since the primary audience for this will be users who have never touched Salt before.

@JasonSwindle
Copy link
Contributor

I agree 100%. Let me mock up some idea and get back shortly. :)

On Tue, Aug 12, 2014 at 1:30 PM, Seth House notifications@github.com
wrote:

The only concern I have is the end result must be simple since the primary
audience for this will be users who have never touched Salt before.


Reply to this email directly or view it on GitHub
#14876 (comment).

@UtahDave
Copy link
Contributor

Yeah, let's have the first version be Jason's original proposal
On Aug 12, 2014 1:14 PM, "Jason Swindle" notifications@github.com wrote:

I agree 100%. Let me mock up some idea and get back shortly. :)

On Tue, Aug 12, 2014 at 1:30 PM, Seth House notifications@github.com
wrote:

The only concern I have is the end result must be simple since the
primary
audience for this will be users who have never touched Salt before.


Reply to this email directly or view it on GitHub
#14876 (comment).


Reply to this email directly or view it on GitHub
#14876 (comment).

@jeunito
Copy link

jeunito commented Oct 13, 2014

I have been trying out salt. To share it easily with my colleagues, I did some Vagrant scripting for the setup mentioned above i.e Ubuntu - master with CentOS and Ubuntu minions in this branch. Thought I'd share this Vagrant config I wrote.

@jacobhammons
Copy link
Contributor

@whiteinge @UtahDave has some great Salt demo environments at https://github.com/UtahDave/salt-vagrant-demo and https://github.com/UtahDave/salt-vagrant-lxc (I refer users to the vagrant-demo in the Get Started guide).

My thought is to add links to these projects on the doc index page, do you think that will cover this request?

@whiteinge
Copy link
Contributor Author

whiteinge commented Jun 16, 2015 via email

jacobhammons added a commit to jacobhammons/salt that referenced this issue Oct 5, 2015
@jacobhammons
Copy link
Contributor

Added links to UtahDave's demo environments to the doc index page, https://docs.saltstack.com/en/2015.5/#demo-environments

@gravyboat
Copy link
Contributor

@jacobhammons I also have two environments set up here: https://github.com/gravyboat/demo-app-1 and https://github.com/gravyboat/demo-app-1. It might be good to actually just put a whole Vagrantfile into the docs in addition to the external links.

@jacobhammons
Copy link
Contributor

@gravyboat very nice, I'm going to give these a try and link them from the demo environments section.

@gravyboat
Copy link
Contributor

Sounds good, let me know if you run into problems.

@DanyC97
Copy link

DanyC97 commented Oct 8, 2015

This are all great ideas.. however does anyone knows/ provide a tip on how to test salt-cloud using vagrant?

I get that vbox driver for salt-cloud is not available but even so how you guys are testing it today ?

Dani

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Relates to Salt documentation Feature new functionality including changes to functionality and code refactors, etc.
Projects
None yet
Development

No branches or pull requests

9 participants