# "Getting Ansible" with Ansible **URL:** \ **Category:** Ansible Project\ **Tags:** ubuntu\ **Created:** [February 21, 2013, 4:32am UTC](https://forum.ansible.com/t/getting-ansible-with-ansible/12395 "2013-02-21T04:32:17Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Brice\_Burgess](https://avatars.discourse-cdn.com/v4/letter/b/d2c977/32.png) [@Brice\_Burgess](https://forum.ansible.com/u/Brice_Burgess)\ **Post date:** [February 21, 2013, 4:32am UTC](https://forum.ansible.com/t/getting-ansible-with-ansible/12395/1 "2013-02-21T04:32:17Z")
I’d love to hear how other people are pushing Ansible out to their servers using ansible. I think once there’s a solid method for this, it would be great to add to the documentation under; [http://ansible.cc/docs/gettingstarted.html#getting-ansible](http://ansible.cc/docs/gettingstarted.html#getting-ansible) My scripts are below && they’re for Ubuntu. It’d be fun to see what you all use for this – please submit yours if you have a chance. I also really like things like `curl [http://install.meteor.com](http://t.co/W6YGo4we)| sh` if they can be checksummed as a one-liner. == push-ansible.yml playbook == ---
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [February 21, 2013, 4:35am UTC](https://forum.ansible.com/t/getting-ansible-with-ansible/12395/2 "2013-02-21T04:35:53Z")
Curious to understand the use case before we talk tech first. So are you doing distributed datacenter setups with sub-ansibles? --Michael ---
**Author:** ![jpmens1](https://avatars.discourse-cdn.com/v4/letter/j/e9c0ed/32.png) [@jpmens1](https://forum.ansible.com/u/jpmens1)\ **Post date:** [February 21, 2013, 6:14am UTC](https://forum.ansible.com/t/getting-ansible-with-ansible/12395/3 "2013-02-21T06:14:00Z")
> I'd love to hear how other people are pushing Ansible out to their servers > using ansible. Why are you pushing Ansible to your servers?         -JP ---
**Author:** ![Brice\_Burgess](https://avatars.discourse-cdn.com/v4/letter/b/d2c977/32.png) [@Brice\_Burgess](https://forum.ansible.com/u/Brice_Burgess)\ **Post date:** [February 21, 2013, 6:15am UTC](https://forum.ansible.com/t/getting-ansible-with-ansible/12395/4 "2013-02-21T06:15:03Z")
Michael, I wouldn’t call it distributed datacenter setups – more like plain-jane basic provisioning. I’ve written a collection of ansible playbooks and shell scripts to “provision” a server as a particular role (e.g. app-server, db-server, or in this case a sysop-server where ansible is used by CI [jenkins] to deploy software to app-servers). Typically this process is done via VM images (e.g. AMIs / qcow / whatever virtualbox do)… although I tend to use dedicated servers that are provisioned with a base OS install by the hosting provider. Make any sense? 🙂 Anyway – I thought it would be cool to have a “Via Ansible” section to go along with “Via PIP” and “Via RPM” in the Getting Started section of the docs; however I now realize it’s not a common use-case. ~ Brice ---
**Author:** ![Brice\_Burgess](https://avatars.discourse-cdn.com/v4/letter/b/d2c977/32.png) [@Brice\_Burgess](https://forum.ansible.com/u/Brice_Burgess)\ **Post date:** [February 21, 2013, 6:39am UTC](https://forum.ansible.com/t/getting-ansible-with-ansible/12395/5 "2013-02-21T06:39:35Z")
I’ve written a collection of ansible playbooks and shell scripts to “provision” a server as a particular role (e.g. app-server, db-server, or in this case a build-server where ansible is used by CI [jenkins] to deploy software to app-servers). Typically this process is done via VM images (e.g. AMIs / qcow / whatever virtualbox do)… although I tend to use dedicated servers that are provisioned with a base OS install by the hosting provider – and use ansible to make their environment consistent (e.g. jenkins ++ ansible for deployment!). Make any sense? 🙂 ---
**Author:** ![Yves\_Dorfsman](https://avatars.discourse-cdn.com/v4/letter/y/9de0a6/32.png) [@Yves\_Dorfsman](https://forum.ansible.com/u/Yves_Dorfsman)\ **Post date:** [February 21, 2013, 6:56am UTC](https://forum.ansible.com/t/getting-ansible-with-ansible/12395/6 "2013-02-21T06:56:57Z")
At one site, I use an ansible shell task with an rsync (pushing to all laptops at install time, to enable them to run ansible-pull). At another site, I only use ansible on one host per environment, and use it as a jumphost to install software on a bunch of servers in that environment. Those "jumphosts" all need the playbooks, tasks and even some tar ball of software. It is a very restricted environment (apps team can't get access to root, there is no central NFS server (actually no NFS server at all) etc... so I just stuck everything in subversion, including ansible. It does have the advantage that if a playbook use a new module, it will have the right version of ansible in the same svn checkout. ---
**Author:** ![Romeo\_Theriault](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@Romeo\_Theriault](https://forum.ansible.com/u/Romeo_Theriault)\ **Post date:** [February 24, 2013, 7:09pm UTC](https://forum.ansible.com/t/getting-ansible-with-ansible/12395/7 "2013-02-24T19:09:58Z")
Hi Brice, We’re a RHEL shop but I usually build an rpm, `make rpm`, and put it in our yum repo. Then the install looks like: yum: name=ansible Looks like there is support for `make debian` in the makefile too. Romeo