Hi Martin, I think that either ways (Vagrant or Chef) you are approaching the problem from the wrong angle. If the problem you are trying to solve is to have an easy setup I would probably recommend the use of images that can be easily restored on the laptop whenever the employee join. This will likely bound you for some time to buy the same machine for all the people for some time unless you go for apple products. The reason I'm saying this is because I tried in past the setup you are trying to build as a user and it's very unproductive, it's slow and frustrating by time. As a developer you want to be fast, productive and independent and the most important thing, be free to use the tool you feel more comfortable with. But that's just my opinion as developer and I know it could be hard to convince your boss.
Good luck. Debo On 25 May 2014 14:46, David Severski <[email protected]> wrote: > A CM system like chef or puppet is definitely the way to go here. You can > use Vagrant to build/test your configuration recipes/scripts/etc. and then > deploy to your bare metal instances as appropraite. > > David > > > On Sunday, May 25, 2014 5:16:18 AM UTC-7, Terrance Shepherd wrote: > >> My suggestion would be to use a configuration management tool like puppet >> or chef on whatever environment you want. >> On May 25, 2014 3:22 AM, "Martin Schmid" <[email protected]> wrote: >> >>> Hello Sebastian, >>> >>> >>> the "problem" we want to solve is quickly setting up a new pc for a >>> future employee. My boss (who btw, knows not too much about Vagrant) >>> imagined Vagrant to be a tool where we could just use Vagrant to automate >>> the process of setting up the work environment (whether local or remote >>> doesn't matter too much I guess). >>> >>> To reiterate again: >>> >>> - new employee arrives >>> - we use tool x to set up a standardized environment for developing (aka >>> a preconfigured eclipse and maybe some other plugins - I got only vague >>> information about this myself) >>> - we can use vagrant to administer the image file and make changes to it. >>> >>> To me it very much sounds like vagrant is not the tool for our task. >>> >>> Thanks in advance. >>> >>> Am Sonntag, 25. Mai 2014 09:04:58 UTC+2 schrieb Sebastian Schulze: >>>> >>>> Hey Martin. >>>> >>>> I guess – it depends.® >>>> The question is: which problem are you trying to solve? Vagrant started >>>> out as a tool to simplify the process of setting up virtual machines >>>> for >>>> local development. The benefit: coherent development environments. >>>> >>>> The setup you're describing sounds a lot more like having 'thin >>>> clients' >>>> for your developers – probably so they don't have to set up Eclipse on >>>> their own. If Eclipse is the problem, you might want to look for ways >>>> to >>>> automate the setup & deployment of the IDE (and the plugin) on your >>>> employees workstations. I could imagine that not everybody will be >>>> happy >>>> working with a Java GUI, running inside a virtual machine on a remote >>>> host. :) >>>> >>>> Bascht >>>> >>>> >>>> On Sat, May 24, 2014 at 12:00:21PM -0700, Martin Schmid wrote: >>>> > Hello folks, >>>> > >>>> > >>>> > the situation: >>>> > >>>> > My boss wants me to automate the process of configuring systems for >>>> new >>>> > employees. His "vision" is that we would install a naked system and >>>> have >>>> > the users connect to a virtual machine on a server. This virtual >>>> machine >>>> > should run everything the users need to develop their applications - >>>> most >>>> > namely Eclipse with a fairly specific plugin. >>>> > >>>> > So, I started doing research on Vagrant. While it seems to be a >>>> fantastic >>>> > tool I'm simply not sure it is what I need. Most people using vagrant >>>> seem >>>> > to develop on their local machine and use the vagrant-managed VM to >>>> > simulate development environments along the lines of an apache >>>> webserver. >>>> > >>>> > So my question is: >>>> > >>>> > Is it viable to use Vagrant to create machines provisioned with a >>>> Linux GUI >>>> > (Xfce would be preferred), Eclipse and a few other smaller programs? >>>> > Updating the image should be a fairly simple process. The Clients are >>>> then >>>> > supposed to connect to the server via PuTTy, ssh into their vagrant >>>> box and >>>> > find themselves inside a fully operational linux that is >>>> preconfigured with >>>> > eclipse. >>>> > >>>> > I realize this is a fairly broad question, but so far my research has >>>> not >>>> > yielded a sufficient answer. >>>> > >>>> > Best Regards >>>> > >>>> > MS. >>>> > >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> Groups "Vagrant" group. >>>> > To unsubscribe from this group and stop receiving emails from it, >>>> send an email to [email protected]. >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> Sebastian Schulze | jabber: [email protected] | http: >>>> http://bascht.com | gpg: 0xBC21CEC5 >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Vagrant" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
