I'm in a Windows IIS shop that is trying to convert from using a using a VM
master image that is continually updated to a bare OS install starting
point. There is a lot of manual playbooking and simple scripting
currently. We are implementing a more robust system for configuration
I see there being three very different user groups for this:
- *nix admins who for whatever reason have some services in their herd
that are tied to Windows
- Windows Server/IIS admins
- Corporate desktop admins
I think the first group would be pleased with little more than the basic
file
I wonder if the automation group is going to stay as spinning up VMs from
manually configured starting points?
I'm coming from the development side; I've traditionally been in the .net
stack but as there is so much bleed-over between the different disciplines
now, I feel like we're finally
And the point that I try to make is I would rather be able to take a clean
VM with the absolute bare minimums and use that as a starting point, rather
than configuring a base VM image and then just pushing updates to it.
I may not have a lot of people on the Windows side that agree with that
I've recently updated the windows intro docs to reference Trond's helpful
setup script, see here:
https://github.com/ansible/ansible/blob/devel/examples/scripts/ConfigureRemotingForAnsible.ps1
On Thu, Jul 31, 2014 at 3:42 PM, Damon Overboe damon.over...@gmail.com
wrote:
And the point that I
Totally agree with you in regards to there being three groups - My
background is a *nix admin and in the middle of trying to convince two
separate teams that fall into the second category, that they need to start
using Ansible to manage their Windows infrastructure going forward.
Thankfully Tower
Porting the file module would be huge, especially:
- create / remove directories (including forcefully)
- transfer (from Controller) / fetch (from web) / create / remove files
I suppose I could use the map network drive on the clients to have the
.msi's available in one place
Loving the Windows support! Sure beats all of my attempted efforts with
Chef to date - I'm going to be needing a fair few of the features listed in
the immediate future.
I've started on a Registry module, please let me know if this clashes with
work done by anyone else thus far.
On Friday, 4
I would find this interesting (even though I only have a few boxes for real
Windows) but due to how different things are between Windows and basically
everything else, I think it pretty much requires a new project. The other
issue is reliability handling errors and pre-provisioning (which maybe
On Wed, Jul 9, 2014 at 5:08 AM, Andrew Udvare audv...@gmail.com wrote:
I would find this interesting (even though I only have a few boxes for
real Windows) but due to how different things are between Windows and
basically everything else, I think it pretty much requires a new project.
If
What I'm primarily interested in is being able to use Ansible as a Vagrant
provisioner on Win7 hosts. At the moment I'm kind of resigned to running
it locally on the VM, though, as I'd have to do with Packer anyway.
On Thursday, July 3, 2014 3:10:18 PM UTC-7, Michael DeHaan wrote:
A
We're not really looking to implement running Ansible from Windows, this is
about managing Windows remotes.
On Mon, Jul 7, 2014 at 11:08 AM, David Carmean dlcarm...@gmail.com wrote:
What I'm primarily interested in is being able to use Ansible as a Vagrant
provisioner on Win7 hosts. At
12 matches
Mail list logo
