5.00 score from hupso.pl for:
nicholaskuechler.com



HTML Content


Titlenicholas kuechler

Length: 17, Words: 2
Description nicholas, or nick, kuechler

Length: 27, Words: 4
Keywords nicholas, kuechler, nick, nicholaskuechler, nkuechler
Robots
Charset UTF-8
Og Meta - Title pusty
Og Meta - Description pusty
Og Meta - Site name pusty
Tytuł powinien zawierać pomiędzy 10 a 70 znaków (ze spacjami), a mniej niż 12 słów w długości.
Meta opis powinien zawierać pomiędzy 50 a 160 znaków (łącznie ze spacjami), a mniej niż 24 słów w długości.
Kodowanie znaków powinny być określone , UTF-8 jest chyba najlepszy zestaw znaków, aby przejść z powodu UTF-8 jest bardziej międzynarodowy kodowaniem.
Otwarte obiekty wykresu powinny być obecne w stronie internetowej (więcej informacji na temat protokołu OpenGraph: http://ogp.me/)

SEO Content

Words/Characters 5816
Text/HTML 52.81 %
Headings H1 1
H2 23
H3 18
H4 10
H5 0
H6 0
H1
nicholas kuechler
H2
recent posts
what i’m reading
pages
my sites
tags
ever2text: migrating off of evernote to dropbox with plain text files
ever2text: migrating off of evernote to dropbox with plain text files
build rackspace cloud servers with ansible in a virtualenv
ansible, rackspace cloud servers, and virtualenv
set up your virtualenv with pyrax and ansible
configuration files for pyrax and ansible
ansible playbook to create rackspace cloud servers
kicking it up a notch: create a server, add dns records, and install some packages
use ansible to install base packages on a rackspace cloud server
final version of playbook to create a rackspace cloud server and install packages
beef stew recipe for 3 quart slow cooker
 3 quart slow cooker beef stew recipe
favorite quotes: thomas edison on work, success and inventing
thomas edison quotes on work
thomas edison quotes on success
thomas edison quotes on inventing
favorite quotes: chinese proverb on happiness
posts navigation
H3
tl;dr
why migrate off of evernote?
migrating to dropbox
exporting evernote notes and notebooks to plain text files with ever2text
create a new python virtualenv for use with rackspace cloud
install the pyrax python package for working with rackspace cloud
install ansible in to the virtualenv
configuration file for pyrax
configuration file for ansible
use a dynamic ansible inventory in virtualenv with rackspace cloud
a basic playbook to create a new rackspace cloud server
run the ansible playbook to create new rackspace cloud server
use ansible to create rackspace cloud dns entries for a cloud server
add a new ansible task to install a list of packages
create a new ansible role to install a list of base packages
source for ansible-rackspace-servers-example on github
ingredients
directions
H4 ansible task to add dynamic instance to dynamic group inventory
ansible task to create a rackspace cloud dns a record
ansible task to create a new domain in rackspace cloud dns
ansible task to create a new rackspace cloud ptr record
ansible playbook to create new rackspace cloud server and add dns entries
let’s give our updated playbook a test run and see what happens!
make ansible role directories
create package installation task in the new base role
using the newly created base role in our build cloud server playbook
run the playbook with the new base role to install packages
H5
H6
strong
all
~/.rackspace_cloud_credentials
~/.ansible.cfg
notes:
-i virtualenv-inventory.yml
-vvvv
success!
but wait!
success!
success!
the good
the bad
b
i
em
Bolds strong 12
b 0
i 0
em 0
Zawartość strony internetowej powinno zawierać więcej niż 250 słów, z stopa tekst / kod jest wyższy niż 20%.
Pozycji używać znaczników (h1, h2, h3, ...), aby określić temat sekcji lub ustępów na stronie, ale zwykle, użyj mniej niż 6 dla każdego tagu pozycje zachować swoją stronę zwięzły.
Styl używać silnych i kursywy znaczniki podkreślić swoje słowa kluczowe swojej stronie, ale nie nadużywać (mniej niż 16 silnych tagi i 16 znaczników kursywy)

Statystyki strony

twitter:title pusty
twitter:description pusty
google+ itemprop=name pusty
Pliki zewnętrzne 16
Pliki CSS 5
Pliki javascript 11
Plik należy zmniejszyć całkowite odwołanie plików (CSS + JavaScript) do 7-8 maksymalnie.

Linki wewnętrzne i zewnętrzne

Linki 142
Linki wewnętrzne 1
Linki zewnętrzne 141
Linki bez atrybutu Title 91
Linki z atrybutem NOFOLLOW 0
Linki - Użyj atrybutu tytuł dla każdego łącza. Nofollow link jest link, który nie pozwala wyszukiwarkom boty zrealizują są odnośniki no follow. Należy zwracać uwagę na ich użytkowania

Linki wewnętrzne

skip to content #content

Linki zewnętrzne

nicholas kuechler http://nicholaskuechler.com/
ever2text: migrating off of evernote to dropbox with plain text files http://nicholaskuechler.com/2016/07/31/ever2text-migrating-off-of-evernote-to-dropbox-with-plain-text-files/
build rackspace cloud servers with ansible in a virtualenv http://nicholaskuechler.com/2015/01/09/build-rackspace-cloud-servers-ansible-virtualenv/
beef stew recipe for 3 quart slow cooker http://nicholaskuechler.com/2014/12/31/beef-stew-recipe-3-quart-slow-cooker/
favorite quotes: thomas edison on work, success and inventing http://nicholaskuechler.com/2014/12/21/favorite-quotes-thomas-edison-on-work-success-and-inventing/
favorite quotes: chinese proverb on happiness http://nicholaskuechler.com/2014/10/14/favorite-quotes-chinese-proverb-on-happiness/
trading tools – stock price decline checker http://nicholaskuechler.com/2013/11/04/trading-tools-stock-price-decline-checker/
pelican, a static site generator written in python http://nicholaskuechler.com/2013/09/15/pelican-a-static-site-generator-written-in-python/
- http://www.amazon.com/gp/product/0140275363/ref=as_li_tl?ie=utf8&camp=1789&creative=9325&creativeasin=0140275363&linkcode=as2&tag=nicholask-20&linkid=3jvkoknk3mpm5tr5
about http://nicholaskuechler.com/about/
contact http://nicholaskuechler.com/contact/
portfolio http://nicholaskuechler.com/portfolio/
projects http://nicholaskuechler.com/projects/
past projects http://nicholaskuechler.com/projects/past-projects/
resume http://nicholaskuechler.com/resume/
things i use http://nicholaskuechler.com/things-i-use/
things i use – kitchen and cooking http://nicholaskuechler.com/things-i-use-kitchen-and-cooking/
athena strategy trading http://www.athenastrategytrading.com/
geo ip location tool http://www.geoipinfo.com/
investing winner http://www.investingwinner.com/
learn trading http://www.learn-trading.com/
left hand firearms http://www.lefthandfirearms.com/
trading winner http://www.tradingwinner.com/
apt http://nicholaskuechler.com/tag/apt/
apt-file http://nicholaskuechler.com/tag/apt-file/
aptitude http://nicholaskuechler.com/tag/aptitude/
automated http://nicholaskuechler.com/tag/automated/
automatic http://nicholaskuechler.com/tag/automatic/
caching http://nicholaskuechler.com/tag/caching/
celery http://nicholaskuechler.com/tag/celery/
centos http://nicholaskuechler.com/tag/centos/
charles darwin http://nicholaskuechler.com/tag/charles-darwin/
cloud http://nicholaskuechler.com/tag/cloud/
cloud files http://nicholaskuechler.com/tag/cloud-files/
code http://nicholaskuechler.com/tag/code/
debian http://nicholaskuechler.com/tag/debian/
dpkg http://nicholaskuechler.com/tag/dpkg/
expires http://nicholaskuechler.com/tag/expires/
fabric http://nicholaskuechler.com/tag/fabric/
favorite quotes http://nicholaskuechler.com/tag/favorite-quotes/
fedora http://nicholaskuechler.com/tag/fedora/
git http://nicholaskuechler.com/tag/git/
github http://nicholaskuechler.com/tag/github/
health http://nicholaskuechler.com/tag/health-2/
how to http://nicholaskuechler.com/tag/how-to/
http headers http://nicholaskuechler.com/tag/http-headers/
instmodsh http://nicholaskuechler.com/tag/instmodsh/
investing http://nicholaskuechler.com/tag/investing-2/
jekyll http://nicholaskuechler.com/tag/jekyll/
list http://nicholaskuechler.com/tag/list/
modules http://nicholaskuechler.com/tag/modules/
nginx http://nicholaskuechler.com/tag/nginx/
opportunity http://nicholaskuechler.com/tag/opportunity/
optimism http://nicholaskuechler.com/tag/optimism/
optimization http://nicholaskuechler.com/tag/optimization/
pelican http://nicholaskuechler.com/tag/pelican/
perl http://nicholaskuechler.com/tag/perl/
proverbs http://nicholaskuechler.com/tag/proverbs/
python http://nicholaskuechler.com/tag/python/
rackspace http://nicholaskuechler.com/tag/rackspace/
scale http://nicholaskuechler.com/tag/scale/
system http://nicholaskuechler.com/tag/system/
trading http://nicholaskuechler.com/tag/trading/
tutorial http://nicholaskuechler.com/tag/tutorial/
ubuntu http://nicholaskuechler.com/tag/ubuntu/
water http://nicholaskuechler.com/tag/water/
winston churchill http://nicholaskuechler.com/tag/winston-churchill/
yum http://nicholaskuechler.com/tag/yum/
ever2text: migrating off of evernote to dropbox with plain text files http://nicholaskuechler.com/2016/07/31/ever2text-migrating-off-of-evernote-to-dropbox-with-plain-text-files/
evernote https://evernote.com/
read their announcement here https://blog.evernote.com/blog/2016/06/28/changes-to-evernotes-pricing-plans/
dropbox https://www.dropbox.com/
ever2simple https://github.com/claytron/ever2simple
ever2text https://github.com/nicholaskuechler/ever2text
my github https://github.com/nicholaskuechler
https://github.com/nicholaskuechler/ever2text https://github.com/nicholaskuechler/ever2text
http://nicholaskuechler.com/2016/07/31/ever2text-migrating-off-of-evernote-to-dropbox-with-plain-text-files/
nicholas kuechler http://nicholaskuechler.com/author/nkuechler/
projects http://nicholaskuechler.com/category/projects/
python http://nicholaskuechler.com/category/python-2/
technology http://nicholaskuechler.com/category/technology/
dropbox http://nicholaskuechler.com/tag/dropbox/
ever2text http://nicholaskuechler.com/tag/ever2text/
evernote http://nicholaskuechler.com/tag/evernote/
migrate off evernote http://nicholaskuechler.com/tag/migrate-off-evernote/
notes http://nicholaskuechler.com/tag/notes/
1 comment on ever2text: migrating off of evernote to dropbox with plain text files http://nicholaskuechler.com/2016/07/31/ever2text-migrating-off-of-evernote-to-dropbox-with-plain-text-files/#comments
build rackspace cloud servers with ansible in a virtualenv http://nicholaskuechler.com/2015/01/09/build-rackspace-cloud-servers-ansible-virtualenv/
my github https://github.com/nicholaskuechler
ansible-rackspace-servers-example https://github.com/nicholaskuechler/ansible-rackspace-servers-example
https://gist.github.com/nicholaskuechler/603ee13bd74944866650 https://gist.github.com/nicholaskuechler/603ee13bd74944866650
https://gist.github.com/nicholaskuechler/8f4812226c6a908dbc9a https://gist.github.com/nicholaskuechler/8f4812226c6a908dbc9a
https://gist.github.com/nicholaskuechler/85aa9e21998bea87a3c5 https://gist.github.com/nicholaskuechler/85aa9e21998bea87a3c5
https://gist.github.com/nicholaskuechler/f6a01223252b89dea959 https://gist.github.com/nicholaskuechler/f6a01223252b89dea959
https://gist.github.com/nicholaskuechler/d2562ef1c780cdeffe14 https://gist.github.com/nicholaskuechler/d2562ef1c780cdeffe14
https://gist.github.com/nicholaskuechler/72ae99ef1acc85a712fe https://gist.github.com/nicholaskuechler/72ae99ef1acc85a712fe
my github https://github.com/nicholaskuechler
ansible-rackspace-servers-example https://github.com/nicholaskuechler/ansible-rackspace-servers-example
http://nicholaskuechler.com/2015/01/09/build-rackspace-cloud-servers-ansible-virtualenv/
nicholas kuechler http://nicholaskuechler.com/author/nkuechler/
devops engineering http://nicholaskuechler.com/category/devops-engineering/
ansible http://nicholaskuechler.com/tag/ansible/
automation http://nicholaskuechler.com/tag/automation/
devops http://nicholaskuechler.com/tag/devops/
dns http://nicholaskuechler.com/tag/dns/
pyrax http://nicholaskuechler.com/tag/pyrax/
python http://nicholaskuechler.com/tag/python/
rackspace http://nicholaskuechler.com/tag/rackspace/
4 comments on build rackspace cloud servers with ansible in a virtualenv http://nicholaskuechler.com/2015/01/09/build-rackspace-cloud-servers-ansible-virtualenv/#comments
beef stew recipe for 3 quart slow cooker http://nicholaskuechler.com/2014/12/31/beef-stew-recipe-3-quart-slow-cooker/
crock-pot 3-quart manual slow cooker, stainless steel http://www.amazon.com/gp/product/b003ucg8ii/ref=as_li_tl?ie=utf8&camp=1789&creative=390957&creativeasin=b003ucg8ii&linkcode=as2&tag=nicholaskuechler-20&linkid=z56w7zl4fzfkiyxr
http://nicholaskuechler.com/2014/12/31/beef-stew-recipe-3-quart-slow-cooker/
nicholas kuechler http://nicholaskuechler.com/author/nkuechler/
recipes http://nicholaskuechler.com/category/recipes/
beef stew http://nicholaskuechler.com/tag/beef-stew/
recipes http://nicholaskuechler.com/tag/recipes/
slow cooker http://nicholaskuechler.com/tag/slow-cooker/
leave a comment on beef stew recipe for 3 quart slow cooker http://nicholaskuechler.com/2014/12/31/beef-stew-recipe-3-quart-slow-cooker/#respond
favorite quotes: thomas edison on work, success and inventing http://nicholaskuechler.com/2014/12/21/favorite-quotes-thomas-edison-on-work-success-and-inventing/
- http://nicholaskuechler.com/wp-content/uploads/2014/12/thomas-edison-with-lightbulb.jpg
http://nicholaskuechler.com/2014/12/21/favorite-quotes-thomas-edison-on-work-success-and-inventing/
nicholas kuechler http://nicholaskuechler.com/author/nkuechler/
favorite quotes http://nicholaskuechler.com/category/favorite-quotes/
favorite quotes http://nicholaskuechler.com/tag/favorite-quotes/
inventing http://nicholaskuechler.com/tag/inventing/
success http://nicholaskuechler.com/tag/success/
thomas edison http://nicholaskuechler.com/tag/thomas-edison/
work http://nicholaskuechler.com/tag/work/
leave a comment on favorite quotes: thomas edison on work, success and inventing http://nicholaskuechler.com/2014/12/21/favorite-quotes-thomas-edison-on-work-success-and-inventing/#respond
favorite quotes: chinese proverb on happiness http://nicholaskuechler.com/2014/10/14/favorite-quotes-chinese-proverb-on-happiness/
http://nicholaskuechler.com/2014/10/14/favorite-quotes-chinese-proverb-on-happiness/
nicholas kuechler http://nicholaskuechler.com/author/nkuechler/
favorite quotes http://nicholaskuechler.com/category/favorite-quotes/
chinese proverb http://nicholaskuechler.com/tag/chinese-proverb/
favorite quotes http://nicholaskuechler.com/tag/favorite-quotes/
happiness http://nicholaskuechler.com/tag/happiness/
proverbs http://nicholaskuechler.com/tag/proverbs/
page 2 http://nicholaskuechler.com/page/2/
page 7 http://nicholaskuechler.com/page/7/
next page http://nicholaskuechler.com/page/2/
nicholas kuechler http://www.nicholaskuechler.com/

Zdjęcia

Zdjęcia 4
Zdjęcia bez atrybutu ALT 3
Zdjęcia bez atrybutu TITLE 4
Korzystanie Obraz ALT i TITLE atrybutu dla każdego obrazu.

Zdjęcia bez atrybutu TITLE

http://ws-na.amazon-adsystem.com/widgets/q?_encoding=utf8&asin=0140275363&format=_sl250_&id=asinimage&marketplace=us&serviceversion=20070822&ws=1&tag=nicholask-20
http://ir-na.amazon-adsystem.com/e/ir?t=nicholask-20&l=as2&o=1&a=0140275363
http://ir-na.amazon-adsystem.com/e/ir?t=nicholaskuechler-20&l=as2&o=1&a=b003ucg8ii
http://nicholaskuechler.com/wp-content/uploads/2014/12/thomas-edison-with-lightbulb.jpg

Zdjęcia bez atrybutu ALT

http://ws-na.amazon-adsystem.com/widgets/q?_encoding=utf8&asin=0140275363&format=_sl250_&id=asinimage&marketplace=us&serviceversion=20070822&ws=1&tag=nicholask-20
http://ir-na.amazon-adsystem.com/e/ir?t=nicholask-20&l=as2&o=1&a=0140275363
http://ir-na.amazon-adsystem.com/e/ir?t=nicholaskuechler-20&l=as2&o=1&a=b003ucg8ii

Ranking:


Alexa Traffic
Daily Global Rank Trend
Daily Reach (Percent)









Majestic SEO











Text on page:

skip to content nicholas kuechler nick kuechler menu and widgets search for: recent posts ever2text: migrating off of evernote to dropbox with plain text files build rackspace cloud servers with ansible in a virtualenv beef stew recipe for 3 quart slow cooker favorite quotes: thomas edison on work, success and inventing favorite quotes: chinese proverb on happiness trading tools – stock price decline checker pelican, a static site generator written in python what i’m reading pages about contact portfolio projects past projects resume things i use things i use – kitchen and cooking my sites athena strategy trading geo ip location tool investing winner learn trading left hand firearms trading winner tagsapt apt-file aptitude automated automatic caching celery centos charles darwin cloud cloud files code debian dpkg expires fabric favorite quotes fedora git github health how to http headers instmodsh investing jekyll list modules nginx opportunity optimism optimization pelican perl proverbs python rackspace scale system trading tutorial ubuntu water winston churchill yum ever2text: migrating off of evernote to dropbox with plain text files ever2text: migrating off of evernote to dropbox with plain text files tl;dr ever2text converts evernote exports of notebooks and files to pure text files, stored in dropbox. why migrate off of evernote? evernote recently announced they were limiting the free tier of accounts to only 2 devices, and also substantially increasing the pricing of all of their plans. you can read their announcement here. i used evernote on 5 devices, but i only used evernote to take text notes. i didn’t use evernote for images, pdfs, email support, or any of the other features included in the — now costlier — paid plans. i just use plain text notes. i started working on a plan to move to a different platform for my notes. my goal was to get plain text files that i could use with any text editor, and on any device. migrating to dropbox i heavily use dropbox, so dropbox seemed like the best place to store all of my text notes. with dropbox, i could access my notes on all of my devices and store them permanently in plain text files. the dropbox app for phones and tablets (both android and ios) also lets you create, search, and edit plain text files. this means i have no need for any additional apps on my phone and tablet devices for taking notes. the problem with evernote became: how do i export my all of my evernote notes and notebooks to plain text files? exporting evernote notes and notebooks to plain text files with ever2text after some googling, i came across ever2simple which was created to export evernote enex export files to simplenote format. it could also export to a directory, but it left me desiring more functionality, such as preserving the note’s title in the generated filename, and an option to export to pure text rather than a markdown formatted text file. i decided to create a pure evernote to text file converter: ever2text. ever2text converts evernote enex exports to files while preserving the note title in the file name and the ability to choose either raw text or markdown for the formatting. i did come across an issue with exporting evernote notebooks. it appears you are unable to export all notebooks in to a single export file. i had a lot of notebooks i had created over the years, so i ended up having to export each evernote notebook individually in to separate enex export files. you can export an evernote notebook by right-clicking on the notebook then clicking on “export notes”. make sure to select the option to export as a file in enex format. you can find ever2text in my github: https://github.com/nicholaskuechler/ever2text posted on july 31, 2016author nicholas kuechlercategories projects, python, technologytags dropbox, ever2text, evernote, migrate off evernote, notes1 comment on ever2text: migrating off of evernote to dropbox with plain text files build rackspace cloud servers with ansible in a virtualenv ansible, rackspace cloud servers, and virtualenv ansible is a powerful tool for managing and configuring servers. it can also be used to create new cloud servers and then configure them automatically for us. for a system administrator, engineer, and developer, ansible can save us a lot of time and hassle by automating a lot of our routine tasks. here’s a tutorial guide for using ansible to build and configure new rackspace cloud servers. i will walk through setting up a new python virtual environment, installing pyrax and ansible inside of of the virtualenv, and then write an ansible playbook and role for building a rackspace cloud server, setting up dns entries for the new server, and installing our favorite packages on the new server. you can find the complete source for this ansible rackspace cloud servers example on my github: ansible-rackspace-servers-example set up your virtualenv with pyrax and ansible first, let’s create a new python virtualenv for use with rackspace cloud. the new virtualenv contains everything needed to build new rackspace cloud servers using the cloud servers api. create a new python virtualenv for use with rackspace cloud virtualenv rackspace the output from the virtualenv command should look something like this: nick@mbp: ~/virtualenvs$ virtualenv rackspace_cloud new python executable in rackspace_cloud/bin/python installing setuptools, pip...done. once the virtualenv has been created, let’s activate it so we can work with it: source rackspace_cloud/bin/activate this is what it will look like once activated on my machine. notice how the prompt has changed to include the virtualenv name “rackspace_cloud” i have just activated. nick@mbp: ~/virtualenvs$ source rackspace_cloud/bin/activate (rackspace_cloud)nick@mbp: ~/virtualenvs$ install the pyrax python package for working with rackspace cloud next we’ll need to install the pyrax package which is needed to work with the rackspace cloud api in python. installing pyrax will also install all of the other prerequisite packages needed by pyrax, such as python-novaclient, python-keystoneclient, rackspace-novaclient, and rackspace-auth-openstack. pip install pyrax here’s what the output looks like on my workstation: https://gist.github.com/nicholaskuechler/603ee13bd74944866650 install ansible in to the virtualenv now that we have pyrax installed, let’s go ahead and install ansible in to our new virtualenv. pip install ansible here’s the output from my workstation: https://gist.github.com/nicholaskuechler/8f4812226c6a908dbc9a configuration files for pyrax and ansible now that we have our python virtualenv set up and the pyrax and ansible packages installed, we need to create a couple configuration files for use with pyrax and ansible. configuration file for pyrax we will place our rackspace cloud username and api key in the pyrax configuration, which pyrax will use when making api calls to rackspace cloud products. create a new file: ~/.rackspace_cloud_credentials here’s what my .rackspace_cloud_credentials pyrax config looks like: [rackspace_cloud] username = mycloudusername api_key = 0123456789abcde configuration file for ansible an ansible configuration file is not necessary as the defaults will work without any issues. there’s one setting in particular, though, which i find helpful when creating a lot of new rackspace cloud servers via ansible. this setting is the ssh setting stricthostkeychecking=no, which means i don’t have to manually confirm a host key when trying to ssh to it. this is a real advantage during automation and playbook runs, since we may not want to have a human confirm the ssh connection. the default ansible configuration file lives at: ~/.ansible.cfg here’s my .ansible.cfg with the option to disable ssh’s strict host key checking: [ssh_connection] ssh_args = -o stricthostkeychecking=no ansible playbook to create rackspace cloud servers now that we’ve installed and configured virtualenv, pyrax, and ansible, we’re ready to write an ansible playbook for building new rackspace cloud servers. first let’s make a new directory for our ansible playbook where the inventory file, play books, and ansible roles will live: mkdir ansible-rackspace-servers use a dynamic ansible inventory in virtualenv with rackspace cloud many people use static ansible inventory files when working with their servers. since we’re using a cloud provider, let’s use a dynamic inventory. but there’s a catch due to installing ansible in a virtualenv: we need to specify the path to the virtualenv python, because ansible will default to the system python rather than the python installed in the virtualenv. in the ansible-rackspace-servers directory we’ve just created, make a new file for the ansible virtualenv inventory file. i named my virtualenv inventory file: virtualenv-inventory.yml here are the contents of my ansible virtualenv inventory file: virtualenv-inventory.yml [localhost] localhost ansible_connection=local ansible_python_interpreter=/users/nick/virtualenvs/rackspace_cloud/bin/python the important configuration piece here is ansible_python_interpreter where we specify the full path to our “rackspace_cloud” virtualenv’s python binary. without the ansible_python_interpreter setting, ansible will try to use the default system python which is probably /usr/bin/python, and as such it will not find our virtualenv packages like pyrax and ansible that we installed in our virtualenv named rackspace_cloud. a basic playbook to create a new rackspace cloud server reading an ansible playbook is fairly straightforward, but writing them can be a little trickier. i’ve created a simple playbook you can use to build new cloud servers in the rackspace cloud. let’s create a new file for our playbook. i’ve called mine build-cloud-server.yml. here’s my playbook to create a new rackspace cloud instance: build-cloud-server.yml --- - name: create a rackspace cloud server hosts: localhost user: root connection: local gather_facts: false vars: # this is the name we will see in the rackspace cloud control panel, and # this will also be the hostname of our new server - name: admin.enhancedtest.net # the flavor specifies the server side of our instance - flavor: performance1-1 # the image specifies the linux distro we will use for our server # note: this image uuid is for ubuntu 14.10 pvhvm - image: 0766e5df-d60a-4100-ae8c-07f27ec0148f # the region is the rackspace cloud region we want to build our server in - region: dfw # credentials specifies the location of our pyrax configuration file we created earlier - credentials: /users/nick/.rackspace_cloud_credentials # i like to drop in my ssh pub key automatically when i create the server # so that i can ssh in without a password # note: instead of dropping in a file, you can use a stored rackspace key # when you build the server by editing key_name below to your key's name. - files: /root/.ssh/authorized_keys: /users/nick/.ssh/id_rsa.pub tasks: - name: rackspace cloud server build request local_action: module: rax credentials: "{{ credentials }}" name: "{{ name }}" flavor: "{{ flavor }}" image: "{{ image }}" region: "{{ region }}" # key_name - specifies the rackspace cloud key to add to the server upon creation #key_name: my_rackspace_key files: "{{ files }}" # wait - specifies that we should wait until the server is fully created before proceeding wait: yes # state - present means we want our server to exist state: present # specify that we want both a public network (public ipv4) and # a private network (10. aka service net) networks: - private - public # group - specifies metadata to add to the new server with a server group #group: deploy # register is an ansible term to save the output in to a variable named rax register: rax the ansible task to create a new rackspace cloud server is pretty straightforward. it uses the rax module included by default with ansible. there are many different options we can work with when creating a new server, but i’ve included the important ones in this playbook. run the ansible playbook to create new rackspace cloud server let’s run our new playbook and see what happens! to run the playbook, we need to call ansible-playbook along with our dynamic inventory file virtualenv-inventory.yml and our playbook yaml build-cloud-server.yml. note: make sure you’re still in the virtualenv you’ve created for this project! ansible-playbook -i virtualenv-inventory.yml build-cloud-server.yml -vvvv notes: -i virtualenv-inventory.yml specifies the inventory file to use. the “-i” denotes the inventory option.  -vvvv specifies that we want really verbose ansible-playbook output, so that we can debug and troubleshoot if something goes wrong. here’s the output when running the build-cloud-server.yml playbook. note i have obfuscated some of the output as it contains personal information: https://gist.github.com/nicholaskuechler/85aa9e21998bea87a3c5 success! we’ve just created a new rackspace cloud server using an ansible playbook inside of a virtualenv. kicking it up a notch: create a server, add dns records, and install some packages when creating a new server, there are other tasks i have to complete, such as adding new forward and reverse dns entries and installing a set of base packages i like to use on my new servers. we can do all of these tasks in ansible! use ansible to create rackspace cloud dns entries for a cloud server now that we have a play for building a new server, let’s add a couple tasks for creating dns a and ptr records for the newly created server automatically. another benefit is that if we have an existing dns record, the ansible rax_dns module can update the records to the new ip address of a newly created cloud server. ansible task to add dynamic instance to dynamic group inventory first we need to have ansible add the new cloud server to an ansible group that we will be using for future tasks in our playbook: - name: add new cloud server to host group local_action: module: add_host hostname: "{{ item.name }}" ansible_ssh_host: "{{ item.rax_accessipv4 }}" ansible_ssh_user: root groupname: deploy with_items: rax.instances what this tasks is doing is looking at the variable we registered with ansible “rax” and adding it to ansible’s internal list of groups and hosts within the group through ansible’s add_host module. the group we’re adding this newly created cloud server to is named “deploy”. we want to specify the hostname, ip address, and the username of the new server when adding the host to the ansible group. ansible task to create a rackspace cloud dns a record next, we’ll create a task to add a forward dns a record in rackspace cloud dns for our new server: - name: dns - create a record local_action: module: rax_dns_record credentials: "{{ credentials }}" domain: "{{ domain }}" name: "{{ name }}" data: "{{ item.rax_accessipv4 }}" type: a with_items: rax.instances register: a_record again we’re using the registered “rax” variable which contains our newly created instance. we’ve also added a new variable “{{ domain }}” that we’ll specify in the “vars” section of our playbook. the domain variable specifies the domain name we want to ensure exists, or create it, in rackspace cloud dns. add domain to the list of vars at the top of the playbook: - domain: enhancedtest.net but wait! what if the domain does not yet exist in rackspace cloud dns? the dns a record addition will fail! ansible task to create a new domain in rackspace cloud dns let’s make a new task to create a new domain if it does not yet exist in rackspace cloud dns. this tasks will come before the task to add any dns records. - name: dns - domain create request local_action: module: rax_dns credentials: "{{ credentials }}" name: "{{ domain }}" email: "{{ dns_email }}" register: rax_dns rackspace cloud dns requires an email address to use as the admin contact for a domain’s dns. let’s add a new variable “dns_email” in our “vars” list at the top of our playbook. note: the email address doesn’t actually have to exist or work, we just need to specify one to create the new domain. add dns_email to the list of vars at the top of the playbook: - dns_email: admin@enhancedtest.net ansible task to create a new rackspace cloud ptr record now that we have created the new dns domain and a record for our server, let’s create a dns ptr record aka reverse dns for the new server. - name: dns - create ptr record local_action: module: rax_dns_record credentials: "{{ credentials }}" server: "{{ item.id }}" name: "{{ name }}" region: "{{ region }}" data: "{{ item.rax_accessipv4 }}" type: ptr with_items: rax.instances register: ptr_record ansible playbook to create new rackspace cloud server and add dns entries here’s what the playbook looks like now with our rackspace cloud dns additions to create a new domain, add an a record for the new server, and add a ptr record. --- - name: create a rackspace cloud server hosts: localhost user: root connection: local gather_facts: false vars: # rackspace cloud dns settings: # domain - the domain we will be using for the new server - domain: enhancedtest.net # dns_email - admin email address for the new domain name - dns_email: admin@enhancedtest.net # this is the name we will see in the rackspace cloud control panel, and # this will also be the hostname of our new server - name: admin.enhancedtest.net # the flavor specifies the server side of our instance - flavor: performance1-1 # the image specifies the linux distro we will use for our server # note: this image uuid is for ubuntu 14.10 pvhvm - image: 0766e5df-d60a-4100-ae8c-07f27ec0148f # the region is the rackspace cloud region we want to build our server in - region: dfw # credentials specifies the location of our pyrax configuration file we created earlier - credentials: /users/nick/.rackspace_cloud_credentials # i like to drop in my ssh pub key automatically when i create the server # so that i can ssh in without a password # note: instead of dropping in a file, you can use a stored rackspace key # when you build the server by editing key_name below to your key's name. - files: /root/.ssh/authorized_keys: /users/nick/.ssh/id_rsa.pub tasks: - name: rackspace cloud server build request local_action: module: rax credentials: "{{ credentials }}" name: "{{ name }}" flavor: "{{ flavor }}" image: "{{ image }}" region: "{{ region }}" # key_name - specifies the rackspace cloud key to add to the server upon creation #key_name: my_rackspace_key files: "{{ files }}" # wait - specifies that we should wait until the server is fully created before proceeding wait: yes # state - present means we want our server to exist state: present # specify that we want both a public network (public ipv4) and # a private network (10. aka service net) networks: - private - public # group - specifies metadata to add to the new server with a server group #group: deploy # register is an ansible term to save the output in to a variable named rax register: rax - name: add new cloud server to host group local_action: module: add_host hostname: "{{ item.name }}" ansible_ssh_host: "{{ item.rax_accessipv4 }}" ansible_ssh_user: root groupname: deploy with_items: rax.instances - name: add new instance to host group local_action: module: add_host hostname: "{{ item.name }}" ansible_ssh_host: "{{ item.rax_accessipv4 }}" ansible_ssh_user: root groupname: deploy with_items: rax.instances - name: dns - domain create request local_action: module: rax_dns credentials: "{{ credentials }}" name: "{{ domain }}" email: "{{ dns_email }}" register: rax_dns - name: dns - create a record local_action: module: rax_dns_record credentials: "{{ credentials }}" domain: "{{ domain }}" name: "{{ name }}" data: "{{ item.rax_accessipv4 }}" type: a with_items: rax.instances register: a_record - name: dns - create ptr record local_action: module: rax_dns_record credentials: "{{ credentials }}" server: "{{ item.id }}" name: "{{ name }}" region: "{{ region }}" data: "{{ item.rax_accessipv4 }}" type: ptr with_items: rax.instances register: ptr_record let’s give our updated playbook a test run and see what happens! run the playbook the same way as before. note: i’m not including -vvvv this time as the output can be extremely verbose, but i always run it when testing, debugging and troubleshooting. ansible-playbook -i virtualenv-inventory.yml build-cloud-server.yml output from the playbook: https://gist.github.com/nicholaskuechler/f6a01223252b89dea959 success! some interesting things to note: the server already existed with the name we specified in the playbook, so a new cloud server was not created the new dns domain was added successfully the new a record was added successfully the new ptr record was added successfully what happens if we run the playbook again? will it create more dns records again? let’s give it a try. here’s the output from my workstation: https://gist.github.com/nicholaskuechler/d2562ef1c780cdeffe14 since the domain, the a record, and ptr record already existed in dns, the tasks were marked as ok and no changes were made. if changes were made, the tasks would be denoted with “changed:” rather than “ok:” in the task output. you can also see the overall playbook tasks ok / changed / failed status in the play recap summary. use ansible to install base packages on a rackspace cloud server now that we have successfully created a new cloud server and performed routine system administrator tasks like setting up dns entries, let’s go ahead and install our favorite packages on our new server. on every server i use, i want vim, git and screen to be available, so let’s make sure those packages are definitely installed. there are two different ways we can accomplish the package installations: 1.) add a new task to install a list of packages 2.) add a new ansible role that installs base packages that we can reuse in other playbooks i prefer option #2 which allows me to re-use my code in other playbooks. i install the same set of base packages on each new server i create, so this will definitely come in handy for me in the future. but let’s cover both options! add a new ansible task to install a list of packages here’s how we can add a new task to our existing ansible playbook to run apt update and install a bunch of our favorite packages on our new rackspace cloud server. the task basically loops through a list of packages specified by with_items and uses apt to install the individual item, which is the package. - name: install packages hosts: deploy user: root gather_facts: true tasks: - name: run apt update apt: update_cache=yes - name: install packages action: apt state=installed pkg={{ item }} with_items: - vim - git - screen tags: - packages important note: since we’re using ubuntu as our linux distro, we need to use the apt ansible module to install packages. if we were using centos or fedora we would change this to yum. note: the ansible hosts group we’re using is “deploy” which we specified previously when adding the newly created cloud server to an internal, dynamic ansible host group. the important piece here is to make sure both group names match if you decide to use a different name! create a new ansible role to install a list of base packages using ansible roles to install our favorite packages is a slightly more complicated method than adding the install packages task to the existing playbook, but it is much more reusable and using roles is generally the preferred ansible way. make ansible role directories first, we need to create a directory structure for our ansible roles. all ansible roles will live in a subdirectory of the directory your playbook lives in called “roles”. let’s call our new role “base” in our example, our playbook build-cloud-server.yml lives in the directory ansible-rackspace-servers, so in the ansible-rackspace-servers directory let’s make a new directory named “roles” mkdir roles then make the roles directory for our “base” role, and a couple standard directories roles in ansible use: cd roles mkdir -p base/{files,handlers,meta,templates,tasks,vars} note: we’re not going to be using all of these standard role directories like meta and vars at this time, but we’ll go ahead and create them now in case we expand our role in the future. create package installation task in the new base role with our directory structure set up for our new “base” role, we need to create a task in this role to install our favorite packages. create a new file in roles/base/tasks/ directory named main.yml. by default, all ansible roles will have a main.yml in the role’s tasks subdirectory. inside of main.yml, let’s write a simple task to install our packages. it’s going to look very similar to the method of adding the package install tasks directly in the playbook, but we won’t need to specify hosts, users, etc. --- - name: run apt update apt: update_cache=yes - name: install apt packages apt: pkg={{ item }} state=installed with_items: - vim - git - screen tags: - packages that’s it! we’ve just created a new role named “base” to install our favorite packages. the best part about this is that we can expand our base role to perform other tasks that need to run on all of our servers, such as adding an admin user or setting up ntp. using the newly created base role in our build cloud server playbook with our base role created, we now need to modify our playbook to use the role to install our base configuration and packages. in our playbook, we need to add: - name: install base packages to new cloud server hosts: deploy user: root gather_facts: true roles: - base the “roles” section specifies which roles to run on the hosts specified in the dynamic “deploy” group. for example, if we had an nginx ansible role we wanted to use, we could easily add it to the list of roles to use, like this: roles: - base - nginx we can also easily use the new “base” role we just created in other ansible playbooks. run the playbook with the new base role to install packages let’s run our playbook now using the new base role to install packages on our new cloud server. here’s the ansible-playbook output from my test run: https://gist.github.com/nicholaskuechler/72ae99ef1acc85a712fe success! the “changed” status under “install apt packages” denotes our 3 favorite packages were installed, and the recap tells us there were no failures. final version of playbook to create a rackspace cloud server and install packages here’s the final version of our playbook: --- - name: create a rackspace cloud server hosts: localhost user: root connection: local gather_facts: false vars: # rackspace cloud dns settings: # domain - the domain we will be using for the new server - domain: enhancedtest.net # dns_email - admin email address for the new domain name - dns_email: admin@enhancedtest.net # this is the name we will see in the rackspace cloud control panel, and # this will also be the hostname of our new server - name: admin.enhancedtest.net # the flavor specifies the server side of our instance - flavor: performance1-1 # the image specifies the linux distro we will use for our server - image: 0766e5df-d60a-4100-ae8c-07f27ec0148f # the region is the rackspace cloud region we want to build our server in - region: dfw # credentials specifies the location of our pyrax configuration file we created earlier - credentials: /users/nick/.rackspace_cloud_credentials # i like to drop in my ssh pub key automatically when i create the server # so that i can ssh in without a password # note: instead of dropping in a file, you can use a stored rackspace key # when you build the server by editing key_name below to your key's name. - files: /root/.ssh/authorized_keys: /users/nick/.ssh/id_rsa.pub tasks: - name: rackspace cloud server build request local_action: module: rax credentials: "{{ credentials }}" name: "{{ name }}" flavor: "{{ flavor }}" image: "{{ image }}" region: "{{ region }}" # key_name - specifies the rackspace cloud key to add to the server upon creation #key_name: my_rackspace_key files: "{{ files }}" # wait - specifies that we should wait until the server is fully created before proceeding wait: yes # state - present means we want our server to exist state: present # specify that we want both a public network (public ipv4) and # a private network (10. aka service net) networks: - private - public # group - specifies metadata to add to the new server with a server group #group: deploy # register is an ansible term to save the output in to a variable named rax register: rax - name: add new cloud server to host group local_action: module: add_host hostname: "{{ item.name }}" ansible_ssh_host: "{{ item.rax_accessipv4 }}" ansible_ssh_user: root groupname: deploy with_items: rax.instances - name: add new instance to host group local_action: module: add_host hostname: "{{ item.name }}" ansible_ssh_host: "{{ item.rax_accessipv4 }}" ansible_ssh_user: root groupname: deploy with_items: rax.instances - name: dns - domain create request local_action: module: rax_dns credentials: "{{ credentials }}" name: "{{ domain }}" email: "{{ dns_email }}" register: rax_dns - name: dns - create a record local_action: module: rax_dns_record credentials: "{{ credentials }}" domain: "{{ domain }}" name: "{{ name }}" data: "{{ item.rax_accessipv4 }}" type: a with_items: rax.instances register: a_record - name: dns - create ptr record local_action: module: rax_dns_record credentials: "{{ credentials }}" server: "{{ item.id }}" name: "{{ name }}" region: "{{ region }}" data: "{{ item.rax_accessipv4 }}" type: ptr with_items: rax.instances register: ptr_record - name: install base packages to new cloud server hosts: deploy user: root gather_facts: true roles: - base source for ansible-rackspace-servers-example on github you can find the complete source for this ansible rackspace cloud servers example on my github: ansible-rackspace-servers-example posted on january 9, 2015author nicholas kuechlercategories devops engineeringtags ansible, automation, devops, dns, pyrax, python, rackspace4 comments on build rackspace cloud servers with ansible in a virtualenv beef stew recipe for 3 quart slow cooker  3 quart slow cooker beef stew recipe i enjoy a nice, hot bowl of stew when it’s cold outside. making your own beef stew is easy, cheap, and most importantly delicious. unfortunately for me, i only have a 3 quart slow cooker (crock-pot 3-quart manual slow cooker, stainless steel). the good: the slow cooker was free. the bad: most slow cooker recipes are for 6 quart slow cookers. after some experimentation, i’ve come up with a beef stew recipe i really enjoy for my 3 quart slow cooker. note: if you have a 6 quart slow cooker, you can double all the ingredients. the recipe makes about 3-4 servings. i like to serve it with some warm, crusty bread, like a warmed baguette. ingredients 1 lb beef stew meat, cut in to 1 inch cubes (my grocery store sells 1 pound packs of beef stew meat already cut in to 1 inch cubes.) 1 large potato, diced 1/2 pound of baby carrots, cut in half crosswise 1 stalk celery, chopped (i buy the pre-washed, pre-cut celery sticks and chop them up. i use about 5-6 celery sticks.) 1/2 onion (large), or 1 small onion, chopped 1/8 cup all-purpose (plain) flour 1/4 teaspoon salt 1/4 teaspoon ground black pepper 1/4 teaspoon seasoned salt 1 bay leaf 1 cup beef broth 1 clove garlic, minced 1/2 teaspoon paprika 1/2 teaspoon worcestershire sauce directions prep the meat place raw meat in slow cooker. in a small bowl, mix together the flour, salt, pepper, and seasoned salt. pour the mixture over the meat, and stir to coat meat with flour mixture. i use my hands to coat the meat with the flour mixture. prep the vegetables chop and dice the vegetables per the ingredients. put all of the vegetables in a large bowl, and mix them together. add bay leaf to vegetable mixture. prep the broth in a small bowl, mix the beef broth, worcestershire sauce, paprika, and minced garlic together. combine all the ingredients in the slow cooker first i add the broth mixture to slow cooker next i slowly add vegetables to slow cooker, and mix with the meat and broth once everything has been added to the slow cooker, i give everything another stir to mix together. start cooking cover the stew. cook on low setting for 10 to 12 hours, or on high setting for 4 to 6 hours. most times i cook on high for 5-6 hours. enjoy your beef stew! posted on december 31, 2014author nicholas kuechlercategories recipestags beef stew, recipes, slow cookerleave a comment on beef stew recipe for 3 quart slow cooker favorite quotes: thomas edison on work, success and inventing thomas edison quotes on work thomas edison, inventor of the lightbulb opportunity is missed by most people because it is dressed in overalls and looks like work. – thomas edison there is no substitute for hard work. – thomas edison i never did anything by accident, nor did any of my inventions come by accident; they came by work. – thomas edison thomas edison quotes on success i have not failed. i’ve just found 10,000 ways that won’t work. – thomas edison one might think that the money value of an invention constitutes its reward to the man who loves his work. but… i continue to find my greatest pleasure, and so my reward, in the work that precedes what the world calls success. – thomas edison many of life’s failures are people who did not realize how close they were to success when they gave up. – thomas edison the three great essentials to achieve anything worth while are: hard work, stick-to-itiveness, and common sense. – thomas edison thomas edison quotes on inventing genius is one percent inspiration and ninety-nine percent perspiration. – thomas edison to invent, you need a good imagination and a pile of junk. – thomas edison just because something doesn’t do what you planned it to do doesn’t mean it’s useless. – thomas edison if we did all the things we are capable of, we would literally astound ourselves. – thomas edison posted on december 21, 2014author nicholas kuechlercategories favorite quotestags favorite quotes, inventing, success, thomas edison, workleave a comment on favorite quotes: thomas edison on work, success and inventing favorite quotes: chinese proverb on happiness if you want happiness for an hour, take a nap. if you want happiness for a day, go fishing. if you want happiness for a month, get married. if you want happiness for a year, inherit a fortune. if you want happiness for a lifetime, help somebody else. posted on october 14, 2014author nicholas kuechlercategories favorite quotestags chinese proverb, favorite quotes, happiness, proverbs posts navigation page 1 page 2 … page 7 next page copyright © 2005-2015 nicholas kuechler


Here you find all texts from your page as Google (googlebot) and others search engines seen it.

Words density analysis:

Numbers of all words: 5596

One word

Two words phrases

Three words phrases

the - 5.31% (297)
serve - 2.07% (116)
server - 2.06% (115)
name - 1.91% (107)
ansible - 1.84% (103)
and - 1.79% (100)
cloud - 1.77% (99)
all - 1.66% (93)
new - 1.63% (91)
our - 1.63% (91)
for - 1.59% (89)
rackspace - 1.59% (89)
not - 1.34% (75)
create - 1.32% (74)
use - 1.27% (71)
rax - 1.22% (68)
"{{ - 1.14% (64)
}}" - 1.14% (64)
note - 1.09% (61)
dns - 1.09% (61)
with - 1.07% (60)
add - 1.07% (60)
file - 0.98% (55)
name: - 0.98% (55)
play - 0.95% (53)
install - 0.91% (51)
playbook - 0.89% (50)
host - 0.82% (46)
virtual - 0.73% (41)
package - 0.73% (41)
role - 0.71% (40)
virtualenv - 0.71% (40)
task - 0.66% (37)
record - 0.64% (36)
item - 0.64% (36)
packages - 0.63% (35)
credentials - 0.63% (35)
domain - 0.61% (34)
key - 0.61% (34)
you - 0.61% (34)
work - 0.57% (32)
can - 0.54% (30)
that - 0.54% (30)
group - 0.52% (29)
text - 0.52% (29)
ssh - 0.5% (28)
his - 0.5% (28)
files - 0.5% (28)
will - 0.5% (28)
this - 0.48% (27)
build - 0.46% (26)
local - 0.46% (26)
here - 0.45% (25)
servers - 0.45% (25)
created - 0.45% (25)
base - 0.43% (24)
user - 0.43% (24)
python - 0.43% (24)
low - 0.41% (23)
module - 0.39% (22)
specifies - 0.39% (22)
region - 0.38% (21)
evernote - 0.38% (21)
pyrax - 0.38% (21)
cook - 0.38% (21)
tasks - 0.36% (20)
want - 0.36% (20)
let’s - 0.36% (20)
roles - 0.34% (19)
instance - 0.34% (19)
thomas - 0.34% (19)
edison - 0.34% (19)
when - 0.32% (18)
email - 0.32% (18)
set - 0.32% (18)
need - 0.32% (18)
inventor - 0.32% (18)
have - 0.32% (18)
slow - 0.32% (18)
action: - 0.32% (18)
local_action: - 0.3% (17)
config - 0.3% (17)
drop - 0.3% (17)
module: - 0.3% (17)
favorite - 0.3% (17)
run - 0.3% (17)
like - 0.3% (17)
cooker - 0.3% (17)
inventory - 0.3% (17)
register - 0.3% (17)
git - 0.29% (16)
per - 0.29% (16)
using - 0.29% (16)
export - 0.29% (16)
ptr - 0.27% (15)
test - 0.27% (15)
kuechler - 0.27% (15)
image - 0.27% (15)
pub - 0.27% (15)
credentials: - 0.27% (15)
put - 0.27% (15)
rackspace_cloud - 0.27% (15)
app - 0.25% (14)
here’s - 0.25% (14)
success - 0.25% (14)
root - 0.25% (14)
output - 0.25% (14)
with_items - 0.25% (14)
apt - 0.25% (14)
deploy - 0.25% (14)
nicholas - 0.25% (14)
notes - 0.23% (13)
server. - 0.23% (13)
with_items: - 0.23% (13)
quotes - 0.23% (13)
directory - 0.23% (13)
man - 0.23% (13)
note: - 0.23% (13)
– - 0.23% (13)
rax_dns - 0.23% (13)
register: - 0.21% (12)
exist - 0.21% (12)
configuration - 0.21% (12)
stew - 0.21% (12)
access - 0.21% (12)
any - 0.21% (12)
github - 0.21% (12)
admin - 0.21% (12)
one - 0.21% (12)
setting - 0.21% (12)
but - 0.21% (12)
beef - 0.21% (12)
what - 0.21% (12)
get - 0.21% (12)
call - 0.21% (12)
flavor - 0.21% (12)
now - 0.2% (11)
nick - 0.2% (11)
over - 0.2% (11)
which - 0.2% (11)
plain - 0.2% (11)
rax.instances - 0.2% (11)
ever2text - 0.2% (11)
item.rax_accessipv4 - 0.2% (11)
dropbox - 0.2% (11)
user: - 0.2% (11)
also - 0.2% (11)
make - 0.2% (11)
two - 0.18% (10)
wait - 0.18% (10)
mix - 0.18% (10)
dns_email - 0.18% (10)
are - 0.18% (10)
hosts - 0.18% (10)
list - 0.18% (10)
some - 0.18% (10)
installed - 0.16% (9)
notebook - 0.16% (9)
region: - 0.16% (9)
specify - 0.16% (9)
quart - 0.16% (9)
key_name - 0.16% (9)
recipe - 0.16% (9)
hostname - 0.16% (9)
named - 0.16% (9)
network - 0.16% (9)
vars - 0.16% (9)
public - 0.16% (9)
other - 0.16% (9)
just - 0.16% (9)
enhancedtest.net - 0.16% (9)
were - 0.14% (8)
meat - 0.14% (8)
read - 0.14% (8)
adding - 0.14% (8)
was - 0.14% (8)
full - 0.14% (8)
variable - 0.14% (8)
happiness - 0.14% (8)
server, - 0.14% (8)
http - 0.14% (8)
state - 0.14% (8)
look - 0.14% (8)
see - 0.13% (7)
example - 0.13% (7)
fully - 0.13% (7)
update - 0.13% (7)
change - 0.13% (7)
inventory. - 0.13% (7)
your - 0.13% (7)
option - 0.13% (7)
ansible-rackspace-servers - 0.13% (7)
build-cloud-server.yml - 0.13% (7)
there - 0.13% (7)
dynamic - 0.13% (7)
side - 0.13% (7)
store - 0.13% (7)
we’re - 0.13% (7)
data: - 0.11% (6)
notebooks - 0.11% (6)
off - 0.11% (6)
domain: - 0.11% (6)
rax_dns_record - 0.11% (6)
type: - 0.11% (6)
default - 0.11% (6)
did - 0.11% (6)
email: - 0.11% (6)
automatic - 0.11% (6)
virtualenv-inventory.yml - 0.11% (6)
request - 0.11% (6)
installing - 0.11% (6)
add_host - 0.11% (6)
files: - 0.11% (6)
present - 0.11% (6)
sure - 0.11% (6)
find - 0.11% (6)
both - 0.11% (6)
private - 0.11% (6)
image: - 0.11% (6)
flavor: - 0.11% (6)
them - 0.11% (6)
mean - 0.11% (6)
newly - 0.11% (6)
gather_facts: - 0.11% (6)
address - 0.11% (6)
hosts: - 0.11% (6)
does - 0.09% (5)
without - 0.09% (5)
live - 0.09% (5)
first - 0.09% (5)
“base” - 0.09% (5)
we’ve - 0.09% (5)
inventing - 0.09% (5)
meta - 0.09% (5)
.rackspace_cloud_credentials - 0.09% (5)
packages. - 0.09% (5)
very - 0.09% (5)
way - 0.09% (5)
ansible_ssh_host: - 0.09% (5)
added - 0.09% (5)
playbook: - 0.09% (5)
page - 0.09% (5)
before - 0.09% (5)
yes - 0.09% (5)
migrating - 0.09% (5)
playbook, - 0.09% (5)
ansible-playbook - 0.09% (5)
me, - 0.09% (5)
records - 0.09% (5)
hostname: - 0.09% (5)
perform - 0.09% (5)
item.name - 0.09% (5)
cut - 0.09% (5)
ansible_ssh_user: - 0.09% (5)
playbook. - 0.09% (5)
i’ve - 0.09% (5)
groupname: - 0.09% (5)
important - 0.09% (5)
localhost - 0.09% (5)
ansible. - 0.09% (5)
up. - 0.09% (5)
source - 0.09% (5)
time - 0.09% (5)
kuechlercategories - 0.09% (5)
posted - 0.09% (5)
activate - 0.09% (5)
notes. - 0.09% (5)
then - 0.09% (5)
servers. - 0.09% (5)
automatically - 0.09% (5)
system - 0.09% (5)
vegetable - 0.09% (5)
work. - 0.09% (5)
teaspoon - 0.09% (5)
from - 0.09% (5)
come - 0.09% (5)
how - 0.09% (5)
entries - 0.09% (5)
work, - 0.09% (5)
proverb - 0.09% (5)
trading - 0.09% (5)
such - 0.09% (5)
edit - 0.09% (5)
mixture - 0.09% (5)
quotes: - 0.09% (5)
api - 0.09% (5)
means - 0.09% (5)
broth - 0.09% (5)
ubuntu - 0.07% (4)
celery - 0.07% (4)
save - 0.07% (4)
stored - 0.07% (4)
--- - 0.07% (4)
they - 0.07% (4)
simple - 0.07% (4)
comment - 0.07% (4)
linux - 0.07% (4)
aka - 0.07% (4)
distro - 0.07% (4)
devices - 0.07% (4)
enex - 0.07% (4)
more - 0.07% (4)
together - 0.07% (4)
than - 0.07% (4)
vegetables - 0.07% (4)
cooker, - 0.07% (4)
ever2text: - 0.07% (4)
tasks: - 0.07% (4)
ingredients - 0.07% (4)
could - 0.07% (4)
most - 0.07% (4)
lot - 0.07% (4)
bowl - 0.07% (4)
different - 0.07% (4)
plan - 0.07% (4)
hand - 0.07% (4)
python, - 0.07% (4)
forward - 0.07% (4)
server: - 0.07% (4)
tool - 0.07% (4)
next - 0.07% (4)
successfully - 0.07% (4)
specified - 0.07% (4)
creating - 0.07% (4)
has - 0.07% (4)
salt - 0.07% (4)
changed - 0.07% (4)
things - 0.07% (4)
we’ll - 0.07% (4)
chop - 0.07% (4)
should - 0.07% (4)
real - 0.07% (4)
file, - 0.07% (4)
looks - 0.07% (4)
about - 0.07% (4)
location - 0.07% (4)
include - 0.07% (4)
1/2 - 0.07% (4)
every - 0.07% (4)
username - 0.07% (4)
flour - 0.07% (4)
ready - 0.07% (4)
since - 0.07% (4)
it: - 0.07% (4)
playbooks - 0.05% (3)
-vvvv - 0.05% (3)
ways - 0.05% (3)
place - 0.05% (3)
dropbox, - 0.05% (3)
screen - 0.05% (3)
files. - 0.05% (3)
recipes - 0.05% (3)
true - 0.05% (3)
service - 0.05% (3)
chinese - 0.05% (3)
net) - 0.05% (3)
networks: - 0.05% (3)
“deploy” - 0.05% (3)
apt: - 0.05% (3)
came - 0.05% (3)
together. - 0.05% (3)
metadata - 0.05% (3)
#group: - 0.05% (3)
mixture. - 0.05% (3)
site - 0.05% (3)
directories - 0.05% (3)
term - 0.05% (3)
own - 0.05% (3)
working - 0.05% (3)
use, - 0.05% (3)
item.id - 0.05% (3)
it’s - 0.05% (3)
group. - 0.05% (3)
ptr_record - 0.05% (3)
(10. - 0.05% (3)
work. – - 0.05% (3)
nginx - 0.05% (3)
a_record - 0.05% (3)
give - 0.05% (3)
again - 0.05% (3)
admin@enhancedtest.net - 0.05% (3)
dns. - 0.05% (3)
dns_email: - 0.05% (3)
doesn’t - 0.05% (3)
top - 0.05% (3)
main.yml - 0.05% (3)
roles: - 0.05% (3)
enjoy - 0.05% (3)
“roles” - 0.05% (3)
success! - 0.05% (3)
addition - 0.05% (3)
included - 0.05% (3)
existing - 0.05% (3)
used - 0.05% (3)
their - 0.05% (3)
future - 0.05% (3)
2014author - 0.05% (3)
would - 0.05% (3)
happens - 0.05% (3)
only - 0.05% (3)
already - 0.05% (3)
projects - 0.05% (3)
pure - 0.05% (3)
virtualenv. - 0.05% (3)
state: - 0.05% (3)
lives - 0.05% (3)
through - 0.05% (3)
cloud. - 0.05% (3)
ansible_python_interpreter - 0.05% (3)
try - 0.05% (3)
ansible-rackspace-servers-example - 0.05% (3)
complete - 0.05% (3)
building - 0.05% (3)
write - 0.05% (3)
inside - 0.05% (3)
ipv4) - 0.05% (3)
everything - 0.05% (3)
false - 0.05% (3)
vars: - 0.05% (3)
control - 0.05% (3)
panel, - 0.05% (3)
admin.enhancedtest.net - 0.05% (3)
configure - 0.05% (3)
servers, - 0.05% (3)
ansible, - 0.05% (3)
contains - 0.05% (3)
needed - 0.05% (3)
0766e5df-d60a-4100-ae8c-07f27ec0148f - 0.05% (3)
strict - 0.05% (3)
ahead - 0.05% (3)
installed, - 0.05% (3)
workstation: - 0.05% (3)
vim - 0.05% (3)
file: - 0.05% (3)
pip - 0.05% (3)
pyrax, - 0.05% (3)
small - 0.05% (3)
large - 0.05% (3)
because - 0.05% (3)
created, - 0.05% (3)
1/4 - 0.05% (3)
once - 0.05% (3)
~/virtualenvs$ - 0.05% (3)
mkdir - 0.05% (3)
nick@mbp: - 0.05% (3)
many - 0.05% (3)
people - 0.05% (3)
something - 0.05% (3)
performance1-1 - 0.05% (3)
connection: - 0.05% (3)
/root/.ssh/authorized_keys: - 0.05% (3)
creation - 0.05% (3)
my_rackspace_key - 0.05% (3)
password - 0.05% (3)
#key_name: - 0.05% (3)
instead - 0.05% (3)
dropping - 0.05% (3)
editing - 0.05% (3)
below - 0.05% (3)
until - 0.05% (3)
key's - 0.05% (3)
name. - 0.05% (3)
had - 0.05% (3)
/users/nick/.ssh/id_rsa.pub - 0.05% (3)
upon - 0.05% (3)
bowl, - 0.05% (3)
/users/nick/.rackspace_cloud_credentials - 0.05% (3)
prep - 0.05% (3)
github: - 0.05% (3)
wait: - 0.05% (3)
(public - 0.05% (3)
couple - 0.05% (3)
file. - 0.05% (3)
dfw - 0.05% (3)
earlier - 0.05% (3)
proceeding - 0.05% (3)
rather - 0.05% (3)
expand - 0.04% (2)
stir - 0.04% (2)
cooker. - 0.04% (2)
onion - 0.04% (2)
time, - 0.04% (2)
great - 0.04% (2)
going - 0.04% (2)
sticks - 0.04% (2)
decide - 0.04% (2)
standard - 0.04% (2)
good - 0.04% (2)
quotestags - 0.04% (2)
role, - 0.04% (2)
example, - 0.04% (2)
dice - 0.04% (2)
method - 0.04% (2)
help - 0.04% (2)
chopped - 0.04% (2)
subdirectory - 0.04% (2)
structure - 0.04% (2)
percent - 0.04% (2)
cup - 0.04% (2)
minced - 0.04% (2)
quotes, - 0.04% (2)
edison, - 0.04% (2)
hard - 0.04% (2)
paprika - 0.04% (2)
version - 0.04% (2)
part - 0.04% (2)
garlic - 0.04% (2)
leaf - 0.04% (2)
december - 0.04% (2)
devops - 0.04% (2)
final - 0.04% (2)
5-6 - 0.04% (2)
hours. - 0.04% (2)
easily - 0.04% (2)
high - 0.04% (2)
start - 0.04% (2)
bay - 0.04% (2)
worcestershire - 0.04% (2)
installation - 0.04% (2)
pepper - 0.04% (2)
manual - 0.04% (2)
pound - 0.04% (2)
sauce - 0.04% (2)
ingredients. - 0.04% (2)
cubes - 0.04% (2)
failures - 0.04% (2)
inch - 0.04% (2)
anything - 0.04% (2)
who - 0.04% (2)
meat, - 0.04% (2)
won’t - 0.04% (2)
it! - 0.04% (2)
reward - 0.04% (2)
seasoned - 0.04% (2)
invention - 0.04% (2)
coat - 0.04% (2)
content - 0.04% (2)
tags: - 0.04% (2)
while - 0.04% (2)
lets - 0.04% (2)
create, - 0.04% (2)
phone - 0.04% (2)
tablet - 0.04% (2)
exporting - 0.04% (2)
after - 0.04% (2)
across - 0.04% (2)
format. - 0.04% (2)
preserving - 0.04% (2)
title - 0.04% (2)
markdown - 0.04% (2)
raw - 0.04% (2)
— - 0.04% (2)
issue - 0.04% (2)
each - 0.04% (2)
clicking - 0.04% (2)
31, - 0.04% (2)
evernote, - 0.04% (2)
us. - 0.04% (2)
routine - 0.04% (2)
virtualenv, - 0.04% (2)
first, - 0.04% (2)
this: - 0.04% (2)
rackspace_cloud/bin/python - 0.04% (2)
been - 0.04% (2)
best - 0.04% (2)
take - 0.04% (2)
activated - 0.04% (2)
centos - 0.04% (2)
search - 0.04% (2)
recent - 0.04% (2)
posts - 0.04% (2)
tools - 0.04% (2)
static - 0.04% (2)
i’m - 0.04% (2)
reading - 0.04% (2)
contact - 0.04% (2)
cooking - 0.04% (2)
investing - 0.04% (2)
winner - 0.04% (2)
left - 0.04% (2)
code - 0.04% (2)
plans. - 0.04% (2)
fedora - 0.04% (2)
opportunity - 0.04% (2)
pelican - 0.04% (2)
proverbs - 0.04% (2)
tutorial - 0.04% (2)
yum - 0.04% (2)
converts - 0.04% (2)
exports - 0.04% (2)
files, - 0.04% (2)
migrate - 0.04% (2)
free - 0.04% (2)
devices, - 0.04% (2)
rackspace_cloud/bin/activate - 0.04% (2)
“rackspace_cloud” - 0.04% (2)
pkg={{ - 0.04% (2)
changes - 0.04% (2)
ansible’s - 0.04% (2)
internal - 0.04% (2)
“vars” - 0.04% (2)
section - 0.04% (2)
yet - 0.04% (2)
domain, - 0.04% (2)
settings: - 0.04% (2)
same - 0.04% (2)
existed - 0.04% (2)
again? - 0.04% (2)
dns, - 0.04% (2)
overall - 0.04% (2)
registered - 0.04% (2)
failed - 0.04% (2)
status - 0.04% (2)
recap - 0.04% (2)
administrator - 0.04% (2)
definitely - 0.04% (2)
prefer - 0.04% (2)
playbooks. - 0.04% (2)
future. - 0.04% (2)
cover - 0.04% (2)
individual - 0.04% (2)
update_cache=yes - 0.04% (2)
state=installed - 0.04% (2)
“rax” - 0.04% (2)
record, - 0.04% (2)
making - 0.04% (2)
uuid - 0.04% (2)
calls - 0.04% (2)
there’s - 0.04% (2)
confirm - 0.04% (2)
automation - 0.04% (2)
.ansible.cfg - 0.04% (2)
stricthostkeychecking=no - 0.04% (2)
where - 0.04% (2)
path - 0.04% (2)
piece - 0.04% (2)
basic - 0.04% (2)
called - 0.04% (2)
build-cloud-server.yml. - 0.04% (2)
14.10 - 0.04% (2)
another - 0.04% (2)
pvhvm - 0.04% (2)
uses - 0.04% (2)
options - 0.04% (2)
ones - 0.04% (2)
happens! - 0.04% (2)
denotes - 0.04% (2)
really - 0.04% (2)
verbose - 0.04% (2)
debug - 0.04% (2)
troubleshoot - 0.04% (2)
reverse - 0.04% (2)
these - 0.04% (2)
… - 0.04% (2)
rackspace cloud - 1% (56)
cloud server - 0.77% (43)
- name: - 0.54% (30)
create a - 0.5% (28)
the new - 0.48% (27)
in the - 0.46% (26)
new server - 0.36% (20)
that we - 0.34% (19)
thomas edison - 0.34% (19)
to create - 0.34% (19)
to the - 0.32% (18)
local_action: module: - 0.3% (17)
slow cooker - 0.3% (17)
name: "{{ - 0.3% (17)
the server - 0.29% (16)
to install - 0.27% (15)
of our - 0.27% (15)
cloud servers - 0.25% (14)
name }}" - 0.25% (14)
specifies the - 0.25% (14)
of the - 0.23% (13)
we want - 0.23% (13)
need to - 0.23% (13)
task to - 0.23% (13)
module: rax - 0.21% (12)
"{{ credentials - 0.21% (12)
our new - 0.21% (12)
}}" name: - 0.21% (12)
credentials: "{{ - 0.21% (12)
new rackspace - 0.21% (12)
credentials }}" - 0.21% (12)
new cloud - 0.2% (11)
with_items: rax.instances - 0.2% (11)
user: root - 0.2% (11)
the rackspace - 0.2% (11)
our server - 0.2% (11)
cloud dns - 0.2% (11)
the play - 0.2% (11)
you can - 0.2% (11)
item.rax_accessipv4 }}" - 0.2% (11)
"{{ item.rax_accessipv4 - 0.2% (11)
a record - 0.18% (10)
plain text - 0.18% (10)
the output - 0.18% (10)
install a - 0.18% (10)
beef stew - 0.18% (10)
to add - 0.18% (10)
the ansible - 0.18% (10)
with a - 0.18% (10)
ansible playbook - 0.18% (10)
text files - 0.18% (10)
for the - 0.18% (10)
the playbook - 0.18% (10)
for our - 0.18% (10)
we will - 0.18% (10)
to use - 0.16% (9)
ptr record - 0.16% (9)
we can - 0.16% (9)
module: rax_dns - 0.16% (9)
name: dns - 0.16% (9)
"{{ name - 0.16% (9)
at the - 0.16% (9)
ansible in - 0.16% (9)
server to - 0.16% (9)
server i - 0.16% (9)
- specifies - 0.16% (9)
configuration file - 0.16% (9)
an ansible - 0.16% (9)
ansible role - 0.16% (9)
and an - 0.16% (9)
all of - 0.16% (9)
is the - 0.14% (8)
playbook to - 0.14% (8)
the virtualenv - 0.14% (8)
list of - 0.14% (8)
and ansible - 0.14% (8)
quart slow - 0.14% (8)
to drop - 0.14% (8)
we need - 0.14% (8)
a rackspace - 0.13% (7)
inventory file - 0.13% (7)
enhancedtest.net # - 0.13% (7)
with the - 0.13% (7)
favorite packages - 0.13% (7)
nicholas kuechler - 0.13% (7)
if you - 0.13% (7)
have a - 0.13% (7)
install packages - 0.13% (7)
base packages - 0.13% (7)
and install - 0.13% (7)
server - - 0.11% (6)
we have - 0.11% (6)
the domain - 0.11% (6)
# this - 0.11% (6)
newly created - 0.11% (6)
now that - 0.11% (6)
in our - 0.11% (6)
the host - 0.11% (6)
module: rax_dns_record - 0.11% (6)
}}" region: - 0.11% (6)
record local_action: - 0.11% (6)
"{{ region - 0.11% (6)
add to - 0.11% (6)
this is - 0.11% (6)
in rackspace - 0.11% (6)
ansible task - 0.11% (6)
domain }}" - 0.11% (6)
want to - 0.11% (6)
host group - 0.11% (6)
data: "{{ - 0.11% (6)
- domain - 0.11% (6)
"{{ domain - 0.11% (6)
that i - 0.11% (6)
on the - 0.11% (6)
install our - 0.11% (6)
role to - 0.11% (6)
base role - 0.11% (6)
all ansible - 0.11% (6)
new domain - 0.11% (6)
register: rax - 0.11% (6)
to build - 0.11% (6)
- create - 0.11% (6)
rax_dns_record credentials: - 0.11% (6)
}}" data: - 0.11% (6)
}}" type: - 0.11% (6)
rax.instances register: - 0.11% (6)
3 quart - 0.11% (6)
evernote to - 0.11% (6)
request local_action: - 0.11% (6)
side of - 0.11% (6)
pyrax and - 0.11% (6)
region: "{{ - 0.11% (6)
our favorite - 0.11% (6)
packages on - 0.11% (6)
region }}" - 0.11% (6)
name: add - 0.09% (5)
ansible roles - 0.09% (5)
like to - 0.09% (5)
module: add_host - 0.09% (5)
here’s the - 0.09% (5)
new server, - 0.09% (5)
add new - 0.09% (5)
output from - 0.09% (5)
to dropbox - 0.09% (5)
of evernote - 0.09% (5)
group local_action: - 0.09% (5)
add_host hostname: - 0.09% (5)
nicholas kuechlercategories - 0.09% (5)
stew recipe - 0.09% (5)
favorite quotes: - 0.09% (5)
server # - 0.09% (5)
create the - 0.09% (5)
name we - 0.09% (5)
i like - 0.09% (5)
a virtualenv - 0.09% (5)
# note: - 0.09% (5)
you want - 0.09% (5)
happiness for - 0.09% (5)
want happiness - 0.09% (5)
make a - 0.09% (5)
the task - 0.09% (5)
using a - 0.09% (5)
"{{ item.name - 0.09% (5)
ansible_ssh_user: root - 0.09% (5)
off of - 0.09% (5)
name: install - 0.09% (5)
server hosts: - 0.09% (5)
deploy with_items: - 0.09% (5)
to export - 0.09% (5)
playbook a - 0.09% (5)
to host - 0.09% (5)
groupname: deploy - 0.09% (5)
run the - 0.09% (5)
root groupname: - 0.09% (5)
}}" ansible_ssh_user: - 0.09% (5)
dns entries - 0.09% (5)
}}" ansible_ssh_host: - 0.09% (5)
name - - 0.09% (5)
hostname: "{{ - 0.09% (5)
i have - 0.09% (5)
posted on - 0.09% (5)
item.name }}" - 0.09% (5)
with ansible - 0.09% (5)
ansible_ssh_host: "{{ - 0.09% (5)
rax.instances - - 0.07% (4)
when i - 0.07% (4)
so that - 0.07% (4)
linux distro - 0.07% (4)
the meat - 0.07% (4)
without a - 0.07% (4)
pyrax configuration - 0.07% (4)
slow cooker, - 0.07% (4)
edison on - 0.07% (4)
tasks: - - 0.07% (4)
we’re using - 0.07% (4)
created a - 0.07% (4)
to run - 0.07% (4)
playbook: - - 0.07% (4)
the hostname - 0.07% (4)
packages i - 0.07% (4)
tasks i - 0.07% (4)
just created - 0.07% (4)
adding the - 0.07% (4)
i create - 0.07% (4)
with our - 0.07% (4)
a server - 0.07% (4)
email address - 0.07% (4)
both a - 0.07% (4)
specifies that - 0.07% (4)
to exist - 0.07% (4)
looks like - 0.07% (4)
fully created - 0.07% (4)
server is - 0.07% (4)
be using - 0.07% (4)
this will - 0.07% (4)
a list - 0.07% (4)
also be - 0.07% (4)
ever2text: migrating - 0.07% (4)
the name - 0.07% (4)
with rackspace - 0.07% (4)
to specify - 0.07% (4)
here are - 0.07% (4)
setting up - 0.07% (4)
will use - 0.07% (4)
use the - 0.07% (4)
with plain - 0.07% (4)
migrating off - 0.07% (4)
such as - 0.07% (4)
make sure - 0.07% (4)
the pyrax - 0.07% (4)
work with - 0.07% (4)
file for - 0.07% (4)
let’s make - 0.07% (4)
python virtual - 0.07% (4)
using the - 0.07% (4)
dropbox with - 0.07% (4)
lot of - 0.07% (4)
can use - 0.07% (4)
new python - 0.07% (4)
new file - 0.07% (4)
will also - 0.07% (4)
use with - 0.07% (4)
the important - 0.05% (3)
option to - 0.05% (3)
root gather_facts: - 0.05% (3)
of packages - 0.05% (3)
new ansible - 0.05% (3)
enex export - 0.05% (3)
file. i - 0.05% (3)
rather than - 0.05% (3)
roles to - 0.05% (3)
deploy user: - 0.05% (3)
the note - 0.05% (3)
roles will - 0.05% (3)
run apt - 0.05% (3)
flavor specifies - 0.05% (3)
inside of - 0.05% (3)
will see - 0.05% (3)
the linux - 0.05% (3)
image specifies - 0.05% (3)
flavor: performance1-1 - 0.05% (3)
instance - - 0.05% (3)
server side - 0.05% (3)
the flavor - 0.05% (3)
admin.enhancedtest.net # - 0.05% (3)
control panel, - 0.05% (3)
domain: enhancedtest.net - 0.05% (3)
write a - 0.05% (3)
new base - 0.05% (3)
in other - 0.05% (3)
- base - 0.05% (3)
roles: - - 0.05% (3)
gather_facts: true - 0.05% (3)
hosts: deploy - 0.05% (3)
our base - 0.05% (3)
apt update - 0.05% (3)
package install - 0.05% (3)
on our - 0.05% (3)
was added - 0.05% (3)
ahead and - 0.05% (3)
dns_email: admin@enhancedtest.net - 0.05% (3)
register: ptr_record - 0.05% (3)
type: ptr - 0.05% (3)
can find - 0.05% (3)
item.id }}" - 0.05% (3)
server: "{{ - 0.05% (3)
create ptr - 0.05% (3)
new server. - 0.05% (3)
source for - 0.05% (3)
the top - 0.05% (3)
here’s what - 0.05% (3)
vars at - 0.05% (3)
note: the - 0.05% (3)
as the - 0.05% (3)
}}" register: - 0.05% (3)
"{{ dns_email - 0.05% (3)
}}" email: - 0.05% (3)
rax_dns credentials: - 0.05% (3)
create request - 0.05% (3)
and add - 0.05% (3)
for building - 0.05% (3)
server and - 0.05% (3)
dns_email }}" - 0.05% (3)
and no - 0.05% (3)
dns records - 0.05% (3)
what happens - 0.05% (3)
image: 0766e5df-d60a-4100-ae8c-07f27ec0148f - 0.05% (3)
our instance - 0.05% (3)
over the - 0.05% (3)
evernote notebook - 0.05% (3)
register: rax_dns - 0.05% (3)
email: "{{ - 0.05% (3)
localhost user: - 0.05% (3)
domain create - 0.05% (3)
build rackspace - 0.05% (3)
can also - 0.05% (3)
- dns_email: - 0.05% (3)
domain name - 0.05% (3)
false vars: - 0.05% (3)
local gather_facts: - 0.05% (3)
root connection: - 0.05% (3)
distro we - 0.05% (3)
we created - 0.05% (3)
region is - 0.05% (3)
group - - 0.05% (3)
named rax - 0.05% (3)
a variable - 0.05% (3)
to save - 0.05% (3)
ansible term - 0.05% (3)
# register - 0.05% (3)
#group: deploy - 0.05% (3)
server group - 0.05% (3)
specifies metadata - 0.05% (3)
public # - 0.05% (3)
a with_items: - 0.05% (3)
private - - 0.05% (3)
networks: - - 0.05% (3)
service net) - 0.05% (3)
(10. aka - 0.05% (3)
private network - 0.05% (3)
ipv4) and - 0.05% (3)
network (public - 0.05% (3)
a public - 0.05% (3)
want both - 0.05% (3)
}}" domain: - 0.05% (3)
}}" server: - 0.05% (3)
state: present - 0.05% (3)
the slow - 0.05% (3)
servers with - 0.05% (3)
comment on - 0.05% (3)
edison quotes - 0.05% (3)
work. – thomas - 0.05% (3)
quotes on - 0.05% (3)
and inventing - 0.05% (3)
work, success - 0.05% (3)
recipe for - 0.05% (3)
quotes: thomas - 0.05% (3)
the ingredients - 0.05% (3)
"{{ item.id - 0.05% (3)
the vegetables - 0.05% (3)
on work, - 0.05% (3)
1/4 teaspoon - 0.05% (3)
cut in - 0.05% (3)
success and - 0.05% (3)
my github: - 0.05% (3)
example on - 0.05% (3)
for this - 0.05% (3)
ptr with_items: - 0.05% (3)
# specify - 0.05% (3)
present means - 0.05% (3)
cloud region - 0.05% (3)
any of - 0.05% (3)
build the - 0.05% (3)
when you - 0.05% (3)
stored rackspace - 0.05% (3)
a file, - 0.05% (3)
dropping in - 0.05% (3)
instead of - 0.05% (3)
a password - 0.05% (3)
in without - 0.05% (3)
can ssh - 0.05% (3)
automatically when - 0.05% (3)
editing key_name - 0.05% (3)
pub key - 0.05% (3)
my ssh - 0.05% (3)
drop in - 0.05% (3)
credentials: /users/nick/.rackspace_cloud_credentials - 0.05% (3)
earlier - - 0.05% (3)
our pyrax - 0.05% (3)
location of - 0.05% (3)
# credentials - 0.05% (3)
region: dfw - 0.05% (3)
server by - 0.05% (3)
below to - 0.05% (3)
state - - 0.05% (3)
server upon - 0.05% (3)
proceeding wait: - 0.05% (3)
created before - 0.05% (3)
is fully - 0.05% (3)
wait until - 0.05% (3)
we should - 0.05% (3)
wait - - 0.05% (3)
"{{ files - 0.05% (3)
my_rackspace_key files: - 0.05% (3)
creation #key_name: - 0.05% (3)
cloud key - 0.05% (3)
your key's - 0.05% (3)
# key_name - 0.05% (3)
image }}" - 0.05% (3)
image: "{{ - 0.05% (3)
flavor }}" - 0.05% (3)
flavor: "{{ - 0.05% (3)
server build - 0.05% (3)
/users/nick/.ssh/id_rsa.pub tasks: - 0.05% (3)
files: /root/.ssh/authorized_keys: - 0.05% (3)
name. - - 0.05% (3)
set up - 0.05% (3)
added successfully - 0.05% (3)
register is - 0.05% (3)
key to - 0.05% (3)
see in - 0.05% (3)
/users/nick/.rackspace_cloud_credentials # - 0.05% (3)
- credentials: - 0.05% (3)
deploy # - 0.05% (3)
created earlier - 0.05% (3)
the newly - 0.05% (3)
created cloud - 0.05% (3)
specify the - 0.05% (3)
file we - 0.05% (3)
cloud control - 0.05% (3)
panel, and - 0.05% (3)
instance to - 0.05% (3)
key_name - - 0.05% (3)
the location - 0.05% (3)
}}" image: - 0.05% (3)
credentials specifies - 0.05% (3)
- region: - 0.05% (3)
upon creation - 0.05% (3)
#key_name: my_rackspace_key - 0.05% (3)
will be - 0.05% (3)
using for - 0.05% (3)
files: "{{ - 0.05% (3)
the inventory - 0.05% (3)
files }}" - 0.05% (3)
# wait - 0.05% (3)
server in - 0.05% (3)
build our - 0.05% (3)
and our - 0.05% (3)
our virtualenv - 0.05% (3)
"{{ image - 0.05% (3)
use ansible - 0.05% (3)
since we - 0.05% (3)
file, you - 0.05% (3)
build request - 0.05% (3)
name: rackspace - 0.05% (3)
/root/.ssh/authorized_keys: /users/nick/.ssh/id_rsa.pub - 0.05% (3)
-i virtualenv-inventory.yml - 0.05% (3)
- files: - 0.05% (3)
key's name. - 0.05% (3)
to your - 0.05% (3)
key_name below - 0.05% (3)
by editing - 0.05% (3)
you build - 0.05% (3)
# when - 0.05% (3)
rackspace key - 0.05% (3)
a stored - 0.05% (3)
of dropping - 0.05% (3)
"{{ flavor - 0.05% (3)
note: instead - 0.05% (3)
when creating - 0.05% (3)
password # - 0.05% (3)
have to - 0.05% (3)
name: create - 0.05% (3)
}}" flavor: - 0.05% (3)
ssh in - 0.05% (3)
hosts: localhost - 0.05% (3)
connection: local - 0.05% (3)
gather_facts: false - 0.05% (3)
vars: # - 0.05% (3)
of base - 0.05% (3)
key automatically - 0.05% (3)
ssh pub - 0.05% (3)
region we - 0.05% (3)
should wait - 0.05% (3)
until the - 0.05% (3)
for use - 0.05% (3)
what the - 0.05% (3)
# group - 0.05% (3)
metadata to - 0.05% (3)
domain: "{{ - 0.05% (3)
be the - 0.05% (3)
use for - 0.05% (3)
hostname of - 0.05% (3)
nick@mbp: ~/virtualenvs$ - 0.05% (3)
server with - 0.05% (3)
type: a - 0.05% (3)
there are - 0.05% (3)
we’ve just - 0.05% (3)
group #group: - 0.05% (3)
register: a_record - 0.05% (3)
our playbook. - 0.05% (3)
create new - 0.05% (3)
python virtualenv - 0.05% (3)
the list - 0.05% (3)
name: admin.enhancedtest.net - 0.05% (3)
rax register: - 0.05% (3)
variable named - 0.05% (3)
output in - 0.05% (3)
top of - 0.05% (3)
the playbook: - 0.05% (3)
- domain: - 0.05% (3)
save the - 0.05% (3)
the image - 0.05% (3)
performance1-1 # - 0.05% (3)
term to - 0.05% (3)
- flavor: - 0.05% (3)
- public - 0.05% (3)
- private - 0.05% (3)
net) networks: - 0.05% (3)
specify that - 0.05% (3)
the region - 0.05% (3)
creating a - 0.05% (3)
before proceeding - 0.05% (3)
the playbook, - 0.05% (3)
wait: yes - 0.05% (3)
# state - 0.05% (3)
- present - 0.05% (3)
means we - 0.05% (3)
want our - 0.05% (3)
0766e5df-d60a-4100-ae8c-07f27ec0148f # - 0.05% (3)
a couple - 0.05% (3)
exist state: - 0.05% (3)
present # - 0.05% (3)
rax credentials: - 0.05% (3)
- image: - 0.05% (3)
to our - 0.05% (3)
aka service - 0.05% (3)
public network - 0.05% (3)
my workstation: - 0.05% (3)
new task - 0.05% (3)
(public ipv4) - 0.05% (3)
go ahead - 0.05% (3)
a private - 0.05% (3)
virtualenv inventory - 0.05% (3)
network (10. - 0.05% (3)
from my - 0.05% (3)
inventory file: - 0.04% (2)
text notes. - 0.04% (2)
i only - 0.04% (2)
ansible will - 0.04% (2)
file: virtualenv-inventory.yml - 0.04% (2)
the other - 0.04% (2)
ansible virtualenv - 0.04% (2)
piece here - 0.04% (2)
virtualenv for - 0.04% (2)
a simple - 0.04% (2)
a comment - 0.04% (2)
the broth - 0.04% (2)
mix the - 0.04% (2)
add the - 0.04% (2)
to slow - 0.04% (2)
has been - 0.04% (2)
14.10 pvhvm - 0.04% (2)
cook on - 0.04% (2)
on high - 0.04% (2)
setting for - 0.04% (2)
6 hours. - 0.04% (2)
on december - 0.04% (2)
cooker favorite - 0.04% (2)
mixture. prep - 0.04% (2)
for ubuntu - 0.04% (2)
uuid is - 0.04% (2)
this image - 0.04% (2)
edison i - 0.04% (2)
did any - 0.04% (2)
edison the - 0.04% (2)
edison thomas - 0.04% (2)
we would - 0.04% (2)
favorite quotestags - 0.04% (2)
favorite quotes, - 0.04% (2)
thomas edison, - 0.04% (2)
files build - 0.04% (2)
bay leaf - 0.04% (2)
the flour - 0.04% (2)
used evernote - 0.04% (2)
6 quart - 0.04% (2)
they were - 0.04% (2)
pure text - 0.04% (2)
files to - 0.04% (2)
rax_dns - - 0.04% (2)
converts evernote - 0.04% (2)
in python - 0.04% (2)
a_record - - 0.04% (2)
find the - 0.04% (2)
complete source - 0.04% (2)
ansible rackspace - 0.04% (2)
proverb on - 0.04% (2)
recipe i - 0.04% (2)
after some - 0.04% (2)
meat with - 0.04% (2)
quotes: chinese - 0.04% (2)
inventing favorite - 0.04% (2)
the ingredients. - 0.04% (2)
inch cubes - 0.04% (2)
celery sticks - 0.04% (2)
seasoned salt - 0.04% (2)
1/2 teaspoon - 0.04% (2)
slow cooker. - 0.04% (2)
small bowl, - 0.04% (2)
mix together - 0.04% (2)
stir to - 0.04% (2)
use my - 0.04% (2)
things i - 0.04% (2)
# domain - 0.04% (2)
ansible-rackspace-servers directory - 0.04% (2)
let’s give - 0.04% (2)
our ansible - 0.04% (2)
we specified - 0.04% (2)
can be - 0.04% (2)
directory for - 0.04% (2)
test run - 0.04% (2)
create rackspace - 0.04% (2)
the ssh - 0.04% (2)
record was - 0.04% (2)
host key - 0.04% (2)
clicking on - 0.04% (2)
means i - 0.04% (2)
the option - 0.04% (2)
file in - 0.04% (2)
this tasks - 0.04% (2)
virtualenv ansible - 0.04% (2)
successfully the - 0.04% (2)
already existed - 0.04% (2)
using ansible - 0.04% (2)
dynamic ansible - 0.04% (2)
other playbooks - 0.04% (2)
packages that - 0.04% (2)
server, let’s - 0.04% (2)
and ptr - 0.04% (2)
title in - 0.04% (2)
name and - 0.04% (2)
let’s go - 0.04% (2)
the tasks - 0.04% (2)
system administrator - 0.04% (2)
markdown for - 0.04% (2)
server now - 0.04% (2)
to have - 0.04% (2)
notebooks i - 0.04% (2)
changes were - 0.04% (2)
ansible group - 0.04% (2)
for ansible - 0.04% (2)
and configure - 0.04% (2)
set of - 0.04% (2)
let’s add - 0.04% (2)
the complete - 0.04% (2)
it will - 0.04% (2)
like this: - 0.04% (2)
reverse dns - 0.04% (2)
new dns - 0.04% (2)
created the - 0.04% (2)
of vars - 0.04% (2)
pyrax will - 0.04% (2)
this ansible - 0.04% (2)
servers example - 0.04% (2)
github: ansible-rackspace-servers-example - 0.04% (2)
not yet - 0.04% (2)
exist in - 0.04% (2)
rackspace cloud. - 0.04% (2)
with pyrax - 0.04% (2)
virtualenv name - 0.04% (2)
pip install - 0.04% (2)
cloud servers. - 0.04% (2)
when adding - 0.04% (2)
new instance - 0.04% (2)
admin@enhancedtest.net # - 0.04% (2)
for pyrax - 0.04% (2)
configuration files - 0.04% (2)
address for - 0.04% (2)
admin email - 0.04% (2)
dns_email - - 0.04% (2)
and then - 0.04% (2)
and installing - 0.04% (2)
domain - - 0.04% (2)
settings: # - 0.04% (2)
# rackspace - 0.04% (2)
write an - 0.04% (2)
add an - 0.04% (2)
our rackspace - 0.04% (2)
like on - 0.04% (2)
the same - 0.04% (2)
the future. - 0.04% (2)
by default - 0.04% (2)
playbook, we - 0.04% (2)
role we - 0.04% (2)
specified in - 0.04% (2)
run on - 0.04% (2)
system python - 0.04% (2)
dynamic inventory - 0.04% (2)
to new - 0.04% (2)
playbook with - 0.04% (2)
what happens! - 0.04% (2)
role in - 0.04% (2)
on all - 0.04% (2)
other tasks - 0.04% (2)
expand our - 0.04% (2)
is that - 0.04% (2)
new role - 0.04% (2)
- packages - 0.04% (2)
installed in - 0.04% (2)
and see - 0.04% (2)
with_items: - - 0.04% (2)
- admin - 0.04% (2)
for my - 0.04% (2)
i could - 0.04% (2)
can work - 0.04% (2)
in this - 0.04% (2)
text files. - 0.04% (2)
evernote notes - 0.04% (2)
# dns_email - 0.04% (2)
and notebooks - 0.04% (2)
run our - 0.04% (2)
domain we - 0.04% (2)
dns settings: - 0.04% (2)
our playbook: - 0.04% (2)
version of - 0.04% (2)
packages here’s - 0.04% (2)
final version - 0.04% (2)
screen tags: - 0.04% (2)
install apt - 0.04% (2)
can do - 0.04% (2)
as adding - 0.04% (2)
a directory - 0.04% (2)
notebooks to - 0.04% (2)
but it - 0.04% (2)
since we’re - 0.04% (2)
working with - 0.04% (2)
preserving the - 0.04% (2)
tags: - - 0.04% (2)
the directory - 0.04% (2)
- screen - 0.04% (2)
pkg={{ item - 0.04% (2)
update_cache=yes - - 0.04% (2)
update apt: - 0.04% (2)
ansible inventory - 0.04% (2)
export to - 0.04% (2)
virtualenv with - 0.04% (2)
will live - 0.04% (2)
lives in - 0.04% (2)
apt: update_cache=yes - 0.04% (2)
exporting evernote - 0.04% (2)
ansible-playbook -i - 0.04% (2)
name: run - 0.04% (2)
playbook, but - 0.04% (2)
virtualenv-inventory.yml build-cloud-server.yml - 0.04% (2)
to plain - 0.04% (2)
and troubleshoot - 0.04% (2)
a dynamic - 0.04% (2)
new “base” - 0.04% (2)
directory named - 0.04% (2)
directory structure - 0.04% (2)
notes and - 0.04% (2)
task in - 0.04% (2)
package installation - 0.04% (2)
of these - 0.04% (2)
in ansible - 0.04% (2)
“base” role, - 0.04% (2)
the group - 0.04% (2)
rackspace cloud server - 0.46% (26)
to create a - 0.23% (13)
create a new - 0.23% (13)
new rackspace cloud - 0.21% (12)
}}" name: "{{ - 0.21% (12)
"{{ credentials }}" - 0.21% (12)
local_action: module: rax - 0.21% (12)
credentials: "{{ credentials - 0.21% (12)
rackspace cloud servers - 0.2% (11)
new cloud server - 0.2% (11)
the rackspace cloud - 0.2% (11)
rackspace cloud dns - 0.2% (11)
"{{ item.rax_accessipv4 }}" - 0.2% (11)
– thomas edison - 0.2% (11)
the new server - 0.18% (10)
name: dns - - 0.16% (9)
- name: dns - 0.16% (9)
plain text files - 0.16% (9)
"{{ name }}" - 0.16% (9)
name: "{{ name - 0.16% (9)
for the new - 0.14% (8)
quart slow cooker - 0.14% (8)
we need to - 0.14% (8)
a rackspace cloud - 0.13% (7)
cloud server to - 0.11% (6)
ansible task to - 0.11% (6)
local_action: module: rax_dns_record - 0.11% (6)
pyrax and ansible - 0.11% (6)
module: rax_dns_record credentials: - 0.11% (6)
playbook to create - 0.11% (6)
add to the - 0.11% (6)
our favorite packages - 0.11% (6)
region: "{{ region - 0.11% (6)
data: "{{ item.rax_accessipv4 - 0.11% (6)
credentials }}" name: - 0.11% (6)
dns - create - 0.11% (6)
now that we - 0.11% (6)
to add to - 0.11% (6)
with_items: rax.instances register: - 0.11% (6)
"{{ region }}" - 0.11% (6)
"{{ domain }}" - 0.11% (6)
}}" region: "{{ - 0.11% (6)
}}" data: "{{ - 0.11% (6)
rax_dns_record credentials: "{{ - 0.11% (6)
request local_action: module: - 0.11% (6)
item.rax_accessipv4 }}" type: - 0.11% (6)
record local_action: module: - 0.11% (6)
}}" ansible_ssh_user: root - 0.09% (5)
ansible_ssh_user: root groupname: - 0.09% (5)
to install our - 0.09% (5)
deploy with_items: rax.instances - 0.09% (5)
role to install - 0.09% (5)
our new server - 0.09% (5)
host group local_action: - 0.09% (5)
groupname: deploy with_items: - 0.09% (5)
module: add_host hostname: - 0.09% (5)
"{{ item.name }}" - 0.09% (5)
ansible_ssh_host: "{{ item.rax_accessipv4 - 0.09% (5)
- name: install - 0.09% (5)
cloud server hosts: - 0.09% (5)
item.rax_accessipv4 }}" ansible_ssh_user: - 0.09% (5)
item.name }}" ansible_ssh_host: - 0.09% (5)
new server - - 0.09% (5)
want happiness for - 0.09% (5)
all of the - 0.09% (5)
beef stew recipe - 0.09% (5)
a new rackspace - 0.09% (5)
you want happiness - 0.09% (5)
add a new - 0.09% (5)
off of evernote - 0.09% (5)
add_host hostname: "{{ - 0.09% (5)
name: add new - 0.09% (5)
in rackspace cloud - 0.09% (5)
task to create - 0.09% (5)
we want to - 0.09% (5)
root groupname: deploy - 0.09% (5)
i like to - 0.09% (5)
}}" ansible_ssh_host: "{{ - 0.09% (5)
hostname: "{{ item.name - 0.09% (5)
local_action: module: add_host - 0.09% (5)
to host group - 0.09% (5)
- name: add - 0.09% (5)
group local_action: module: - 0.09% (5)
if you want - 0.09% (5)
tasks: - name: - 0.07% (4)
install our favorite - 0.07% (4)
evernote to dropbox - 0.07% (4)
to the new - 0.07% (4)
the name we - 0.07% (4)
specifies that we - 0.07% (4)
run the playbook - 0.07% (4)
rax.instances - name: - 0.07% (4)
that we want - 0.07% (4)
migrating off of - 0.07% (4)
a list of - 0.07% (4)
dropbox with plain - 0.07% (4)
make a new - 0.07% (4)
an ansible playbook - 0.07% (4)
with_items: rax.instances - - 0.07% (4)
ansible in a - 0.07% (4)
in the rackspace - 0.07% (4)
you can use - 0.07% (4)
with plain text - 0.07% (4)
in a virtualenv - 0.07% (4)
to dropbox with - 0.07% (4)
of evernote to - 0.07% (4)
ever2text: migrating off - 0.07% (4)
private network (10. - 0.05% (3)
present means we - 0.05% (3)
group - specifies - 0.05% (3)
- public # - 0.05% (3)
networks: - private - 0.05% (3)
aka service net) - 0.05% (3)
want our server - 0.05% (3)
to exist state: - 0.05% (3)
network (public ipv4) - 0.05% (3)
both a public - 0.05% (3)
create ptr record - 0.05% (3)
credentials }}" domain: - 0.05% (3)
a with_items: rax.instances - 0.05% (3)
present # specify - 0.05% (3)
metadata to add - 0.05% (3)
deploy # register - 0.05% (3)
server with a - 0.05% (3)
to a variable - 0.05% (3)
- private - - 0.05% (3)
public # group - 0.05% (3)
- specifies metadata - 0.05% (3)
with a server - 0.05% (3)
group #group: deploy - 0.05% (3)
# register is - 0.05% (3)
named rax register: - 0.05% (3)
an ansible term - 0.05% (3)
to save the - 0.05% (3)
server group #group: - 0.05% (3)
output in to - 0.05% (3)
the output in - 0.05% (3)
a variable named - 0.05% (3)
rax register: rax - 0.05% (3)
term to save - 0.05% (3)
is an ansible - 0.05% (3)
- create a - 0.05% (3)
item.id }}" name: - 0.05% (3)
}}" server: "{{ - 0.05% (3)
key # when - 0.05% (3)
# state - - 0.05% (3)
a password # - 0.05% (3)
editing key_name below - 0.05% (3)
the server by - 0.05% (3)
when you build - 0.05% (3)
rackspace key # - 0.05% (3)
use a stored - 0.05% (3)
file, you can - 0.05% (3)
dropping in a - 0.05% (3)
note: instead of - 0.05% (3)
ssh in without - 0.05% (3)
2014author nicholas kuechlercategories - 0.05% (3)
that i can - 0.05% (3)
server # so - 0.05% (3)
i create the - 0.05% (3)
key automatically when - 0.05% (3)
my ssh pub - 0.05% (3)
to drop in - 0.05% (3)
- credentials: /users/nick/.rackspace_cloud_credentials - 0.05% (3)
we created earlier - 0.05% (3)
pyrax configuration file - 0.05% (3)
to your key's - 0.05% (3)
name. - files: - 0.05% (3)
ptr with_items: rax.instances - 0.05% (3)
#key_name: my_rackspace_key files: - 0.05% (3)
network (10. aka - 0.05% (3)
proceeding wait: yes - 0.05% (3)
fully created before - 0.05% (3)
the server is - 0.05% (3)
for 3 quart - 0.05% (3)
should wait until - 0.05% (3)
thomas edison quotes - 0.05% (3)
work. – thomas edison - 0.05% (3)
"{{ files }}" - 0.05% (3)
server upon creation - 0.05% (3)
/root/.ssh/authorized_keys: /users/nick/.ssh/id_rsa.pub tasks: - 0.05% (3)
cloud key to - 0.05% (3)
specifies the rackspace - 0.05% (3)
# key_name - - 0.05% (3)
image }}" region: - 0.05% (3)
}}" image: "{{ - 0.05% (3)
flavor: "{{ flavor - 0.05% (3)
rax credentials: "{{ - 0.05% (3)
cloud server build - 0.05% (3)
- name: rackspace - 0.05% (3)
service net) networks: - 0.05% (3)
(public ipv4) and - 0.05% (3)
# a private - 0.05% (3)
- files: /root/.ssh/authorized_keys: - 0.05% (3)
the new base - 0.05% (3)
to install packages - 0.05% (3)
deploy user: root - 0.05% (3)
server by editing - 0.05% (3)
key_name below to - 0.05% (3)
new base role - 0.05% (3)
go ahead and - 0.05% (3)
your key's name. - 0.05% (3)
/users/nick/.ssh/id_rsa.pub tasks: - - 0.05% (3)
output from my - 0.05% (3)
name: rackspace cloud - 0.05% (3)
server build request - 0.05% (3)
name }}" flavor: - 0.05% (3)
the newly created - 0.05% (3)
user: root gather_facts: - 0.05% (3)
"{{ flavor }}" - 0.05% (3)
image: "{{ image - 0.05% (3)
list of packages - 0.05% (3)
install a list - 0.05% (3)
packages on our - 0.05% (3)
0766e5df-d60a-4100-ae8c-07f27ec0148f # the - 0.05% (3)
region }}" # - 0.05% (3)
drop in my - 0.05% (3)
in a file, - 0.05% (3)
instead of dropping - 0.05% (3)
password # note: - 0.05% (3)
in without a - 0.05% (3)
i can ssh - 0.05% (3)
# so that - 0.05% (3)
create the server - 0.05% (3)
automatically when i - 0.05% (3)
ssh pub key - 0.05% (3)
you build the - 0.05% (3)
region is the - 0.05% (3)
credentials: /users/nick/.rackspace_cloud_credentials # - 0.05% (3)
created earlier - - 0.05% (3)
configuration file we - 0.05% (3)
of our pyrax - 0.05% (3)
specifies the location - 0.05% (3)
dfw # credentials - 0.05% (3)
in - region: - 0.05% (3)
build our server - 0.05% (3)
rackspace cloud region - 0.05% (3)
a new ansible - 0.05% (3)
credentials specifies the - 0.05% (3)
a stored rackspace - 0.05% (3)
created before proceeding - 0.05% (3)
create request local_action: - 0.05% (3)
dns - domain - 0.05% (3)
my_rackspace_key files: "{{ - 0.05% (3)
files }}" # - 0.05% (3)
wait - specifies - 0.05% (3)
that we should - 0.05% (3)
wait until the - 0.05% (3)
server is fully - 0.05% (3)
wait: yes # - 0.05% (3)
name: "{{ domain - 0.05% (3)
state - present - 0.05% (3)
means we want - 0.05% (3)
our server to - 0.05% (3)
exist state: present - 0.05% (3)
# specify that - 0.05% (3)
we want both - 0.05% (3)
server to host - 0.05% (3)
a public network - 0.05% (3)
add new cloud - 0.05% (3)
module: rax_dns credentials: - 0.05% (3)
upon creation #key_name: - 0.05% (3)
task to install - 0.05% (3)
key to add - 0.05% (3)
on our new - 0.05% (3)
cloud server and - 0.05% (3)
created a new - 0.05% (3)
in the play - 0.05% (3)
was added successfully - 0.05% (3)
key_name - specifies - 0.05% (3)
rax.instances register: ptr_record - 0.05% (3)
type: ptr with_items: - 0.05% (3)
region }}" data: - 0.05% (3)
"{{ item.id }}" - 0.05% (3)
}}" email: "{{ - 0.05% (3)
credentials }}" server: - 0.05% (3)
to the server - 0.05% (3)
- create ptr - 0.05% (3)
rax.instances register: a_record - 0.05% (3)
type: a with_items: - 0.05% (3)
name }}" data: - 0.05% (3)
domain: "{{ domain - 0.05% (3)
a record local_action: - 0.05% (3)
dns_email }}" register: - 0.05% (3)
location of our - 0.05% (3)
# the image - 0.05% (3)
region: dfw # - 0.05% (3)
a file, you - 0.05% (3)
files: /root/.ssh/authorized_keys: /users/nick/.ssh/id_rsa.pub - 0.05% (3)
key's name. - - 0.05% (3)
below to your - 0.05% (3)
by editing key_name - 0.05% (3)
build the server - 0.05% (3)
# when you - 0.05% (3)
stored rackspace key - 0.05% (3)
can use a - 0.05% (3)
of dropping in - 0.05% (3)
module: rax credentials: - 0.05% (3)
# note: instead - 0.05% (3)
without a password - 0.05% (3)
can ssh in - 0.05% (3)
so that i - 0.05% (3)
the server # - 0.05% (3)
when i create - 0.05% (3)
pub key automatically - 0.05% (3)
in my ssh - 0.05% (3)
like to drop - 0.05% (3)
build request local_action: - 0.05% (3)
server in - - 0.05% (3)
earlier - credentials: - 0.05% (3)
until the server - 0.05% (3)
specify that we - 0.05% (3)
state: present # - 0.05% (3)
server to exist - 0.05% (3)
we want our - 0.05% (3)
- present means - 0.05% (3)
yes # state - 0.05% (3)
before proceeding wait: - 0.05% (3)
is fully created - 0.05% (3)
we should wait - 0.05% (3)
flavor }}" image: - 0.05% (3)
- specifies that - 0.05% (3)
}}" # wait - 0.05% (3)
files: "{{ files - 0.05% (3)
creation #key_name: my_rackspace_key - 0.05% (3)
the server upon - 0.05% (3)
rackspace cloud key - 0.05% (3)
- specifies the - 0.05% (3)
}}" # key_name - 0.05% (3)
"{{ image }}" - 0.05% (3)
/users/nick/.rackspace_cloud_credentials # i - 0.05% (3)
file we created - 0.05% (3)
public network (public - 0.05% (3)
for use with - 0.05% (3)
is the name - 0.05% (3)
local gather_facts: false - 0.05% (3)
user: root connection: - 0.05% (3)
server hosts: localhost - 0.05% (3)
- name: create - 0.05% (3)
let’s make a - 0.05% (3)
need to create - 0.05% (3)
here’s the output - 0.05% (3)
let’s create a - 0.05% (3)
cloud control panel, - 0.05% (3)
to create new - 0.05% (3)
servers with ansible - 0.05% (3)
build rackspace cloud - 0.05% (3)
all of my - 0.05% (3)
success and inventing - 0.05% (3)
edison on work, - 0.05% (3)
favorite quotes: thomas - 0.05% (3)
recipe for 3 - 0.05% (3)
cloud servers with - 0.05% (3)
we will see - 0.05% (3)
and # this - 0.05% (3)
our pyrax configuration - 0.05% (3)
- image: 0766e5df-d60a-4100-ae8c-07f27ec0148f - 0.05% (3)
the location of - 0.05% (3)
# credentials specifies - 0.05% (3)
- region: dfw - 0.05% (3)
our server in - 0.05% (3)
want to build - 0.05% (3)
cloud region we - 0.05% (3)
is the rackspace - 0.05% (3)
# the region - 0.05% (3)
will use for - 0.05% (3)
will also be - 0.05% (3)
linux distro we - 0.05% (3)
image specifies the - 0.05% (3)
performance1-1 # the - 0.05% (3)
instance - flavor: - 0.05% (3)
side of our - 0.05% (3)
specifies the server - 0.05% (3)
# the flavor - 0.05% (3)
- name: admin.enhancedtest.net - 0.05% (3)
the hostname of - 0.05% (3)
want both a - 0.05% (3)
}}" flavor: "{{ - 0.05% (3)
ipv4) and # - 0.05% (3)
task to add - 0.05% (3)
server: "{{ item.id - 0.05% (3)
ptr record local_action: - 0.05% (3)
at the top - 0.05% (3)
}}" register: rax_dns - 0.05% (3)
email: "{{ dns_email - 0.05% (3)
rax_dns credentials: "{{ - 0.05% (3)
- domain create - 0.05% (3)
a new task - 0.05% (3)
a private network - 0.05% (3)
a new domain - 0.05% (3)
the top of - 0.05% (3)
to the list - 0.05% (3)
}}" type: a - 0.05% (3)
domain }}" name: - 0.05% (3)
}}" domain: "{{ - 0.05% (3)
create a record - 0.05% (3)
name }}" region: - 0.05% (3)
- dns_email: admin@enhancedtest.net - 0.05% (3)
will be using - 0.05% (3)
- flavor: performance1-1 - 0.05% (3)
to build our - 0.05% (3)
region we want - 0.05% (3)
the region is - 0.05% (3)
image: 0766e5df-d60a-4100-ae8c-07f27ec0148f # - 0.05% (3)
use for our - 0.05% (3)
distro we will - 0.05% (3)
specifies the linux - 0.05% (3)
of our instance - 0.05% (3)
# this is - 0.05% (3)
the server side - 0.05% (3)
the flavor specifies - 0.05% (3)
name: admin.enhancedtest.net # - 0.05% (3)
hostname of our - 0.05% (3)
also be the - 0.05% (3)
# this will - 0.05% (3)
control panel, and - 0.05% (3)
will see in - 0.05% (3)
dns a record - 0.05% (3)
}}" type: ptr - 0.05% (3)
a server group - 0.05% (3)
save the output - 0.05% (3)
when creating a - 0.05% (3)
#group: deploy # - 0.05% (3)
variable named rax - 0.05% (3)
new server with - 0.05% (3)
# group - - 0.05% (3)
a new server, - 0.05% (3)
private - public - 0.05% (3)
net) networks: - - 0.05% (3)
ansible term to - 0.05% (3)
specifies metadata to - 0.05% (3)
(10. aka service - 0.05% (3)
register is an - 0.05% (3)
new python virtualenv - 0.04% (2)
ahead and install - 0.04% (2)
install the pyrax - 0.04% (2)
of the other - 0.04% (2)
here’s what the - 0.04% (2)
in to the - 0.04% (2)
all ansible roles - 0.04% (2)
with pyrax and - 0.04% (2)
ansible in to - 0.04% (2)
from my workstation: - 0.04% (2)
see what happens! - 0.04% (2)
servers example on - 0.04% (2)
configuration file for - 0.04% (2)
use a dynamic - 0.04% (2)
to the virtualenv - 0.04% (2)
the ansible-rackspace-servers directory - 0.04% (2)
ansible virtualenv inventory - 0.04% (2)
virtualenv inventory file: - 0.04% (2)
to build new - 0.04% (2)
new file for - 0.04% (2)
my github: ansible-rackspace-servers-example - 0.04% (2)
find the complete - 0.04% (2)
ansible rackspace cloud - 0.04% (2)
stew recipe i - 0.04% (2)
files build rackspace - 0.04% (2)
virtualenv beef stew - 0.04% (2)
a comment on - 0.04% (2)
edison thomas edison - 0.04% (2)
rax_dns - name: - 0.04% (2)
14.10 pvhvm - - 0.04% (2)
posted on december - 0.04% (2)
all the ingredients - 0.04% (2)
favorite quotes: chinese - 0.04% (2)
in a small - 0.04% (2)
beef stew meat - 0.04% (2)
to 1 inch - 0.04% (2)
6 quart slow - 0.04% (2)
source for this - 0.04% (2)
proverb on happiness - 0.04% (2)
i have no - 0.04% (2)
is for ubuntu - 0.04% (2)
evernote notes and - 0.04% (2)
notebooks to plain - 0.04% (2)
title in the - 0.04% (2)
register: a_record - - 0.04% (2)
the option to - 0.04% (2)
this image uuid - 0.04% (2)
server # note: - 0.04% (2)
up dns entries - 0.04% (2)
instance to host - 0.04% (2)
a new cloud - 0.04% (2)
output from the - 0.04% (2)
record was added - 0.04% (2)
created the new - 0.04% (2)
gather_facts: true roles: - 0.04% (2)
not yet exist - 0.04% (2)
the playbook: - - 0.04% (2)
of vars at - 0.04% (2)
name: run apt - 0.04% (2)
of our playbook. - 0.04% (2)
final version of - 0.04% (2)
update apt: update_cache=yes - 0.04% (2)
vim - git - 0.04% (2)
- screen tags: - 0.04% (2)
let’s run our - 0.04% (2)
to create rackspace - 0.04% (2)
new “base” role - 0.04% (2)
server now that - 0.04% (2)
to install the - 0.04% (2)
when adding the - 0.04% (2)
packages to new - 0.04% (2)
name: install base - 0.04% (2)
playbook, we need - 0.04% (2)
to run on - 0.04% (2)
our base role - 0.04% (2)
rax - name: - 0.04% (2)
pkg={{ item }} - 0.04% (2)
for our new - 0.04% (2)
we have a - 0.04% (2)
in the future. - 0.04% (2)
let’s add a - 0.04% (2)
just created a - 0.04% (2)
yet exist in - 0.04% (2)
added successfully the - 0.04% (2)
our server # - 0.04% (2)
all of these - 0.04% (2)
base packages on - 0.04% (2)
new domain name - 0.04% (2)
address for the - 0.04% (2)
- admin email - 0.04% (2)
enhancedtest.net # dns_email - 0.04% (2)
server - domain: - 0.04% (2)
the domain we - 0.04% (2)
# domain - - 0.04% (2)
cloud dns settings: - 0.04% (2)
vars: # rackspace - 0.04% (2)
the new server, - 0.04% (2)
note: this image - 0.04% (2)
rackspace cloud dns. - 0.04% (2)
uuid is for - 0.04% (2)
ubuntu 14.10 pvhvm - 0.04% (2)
a record for - 0.04% (2)
our rackspace cloud - 0.04% (2)
setting up dns - 0.04% (2)
we can work - 0.04% (2)
new dns domain - 0.04% (2)
and see what - 0.04% (2)
in the virtualenv - 0.04% (2)
in other playbooks - 0.04% (2)
set of base - 0.04% (2)
new instance to - 0.04% (2)
-i virtualenv-inventory.yml build-cloud-server.yml - 0.04% (2)
kuechlercategories favorite quotestags - 0.04% (2)

Here you can find chart of all your popular one, two and three word phrases. Google and others search engines means your page is about words you use frequently.

Copyright © 2015-2016 hupso.pl. All rights reserved. FB | +G | Twitter

Hupso.pl jest serwisem internetowym, w którym jednym kliknieciem możesz szybko i łatwo sprawdź stronę www pod kątem SEO. Oferujemy darmowe pozycjonowanie stron internetowych oraz wycena domen i stron internetowych. Prowadzimy ranking polskich stron internetowych oraz ranking stron alexa.