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 7372
Text/HTML 57.75 %
Headings H1 1
H2 28
H3 21
H4 11
H5 0
H6 0
H1
nicholas kuechler
H2
recent posts
what i’m reading
pages
my sites
tags
create a static website at amazon aws using python, s3, and route53
benefits of static web sites
static vs dynamic
setting up a static web site at amazon aws with python
add content to s3 bucket
change nameservers at your domain registrar to point to aws route53
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
posts navigation
H3
prerequisite: install aws python sdk
step 1: create s3 bucket for a static web site
step 2: create a route53 hosted zone for the domain
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 step 1.1: create s3 bucket for redirecting www.domain.com to root domain.com
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 151
Linki wewnętrzne 1
Linki zewnętrzne 150
Linki bez atrybutu Title 100
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/
create a static website at amazon aws using python, s3, and route53 http://nicholaskuechler.com/2016/12/04/create-a-static-website-at-amazon-aws-using-python-s3-and-route53/
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/
- 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/
create a static website at amazon aws using python, s3, and route53 http://nicholaskuechler.com/2016/12/04/create-a-static-website-at-amazon-aws-using-python-s3-and-route53/
critical vulnerability in drupal was announced https://www.drupal.org/psa-2014-003
getting started: static website hosting http://docs.aws.amazon.com/gettingstarted/latest/swh/website-hosting-intro.html
aws python sdk https://aws.amazon.com/sdk-for-python/
get your name servers for your new hosted zone http://docs.aws.amazon.com/route53/latest/developerguide/getinfoabouthostedzone.html
http://nicholaskuechler.com/2016/12/04/create-a-static-website-at-amazon-aws-using-python-s3-and-route53/
nicholas kuechler http://nicholaskuechler.com/author/nkuechler/
devops engineering http://nicholaskuechler.com/category/devops-engineering/
python http://nicholaskuechler.com/category/python-2/
web development http://nicholaskuechler.com/category/web-development/
amazon http://nicholaskuechler.com/tag/amazon/
aws http://nicholaskuechler.com/tag/aws/
python http://nicholaskuechler.com/tag/python/
route53 http://nicholaskuechler.com/tag/route53/
s3 http://nicholaskuechler.com/tag/s3/
wordpress http://nicholaskuechler.com/tag/wordpress/
leave a comment on create a static website at amazon aws using python, s3, and route53 http://nicholaskuechler.com/2016/12/04/create-a-static-website-at-amazon-aws-using-python-s3-and-route53/#respond
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
page 2 http://nicholaskuechler.com/page/2/
page 7 http://nicholaskuechler.com/page/7/
next page http://nicholaskuechler.com/page/2/
nicholas kuechler http://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 create a static website at amazon aws using python, s3, and route53 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 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 create a static website at amazon aws using python, s3, and route53 benefits of static web sites the most important benefits of static web sites are speed and security. fully static web sites can be delivered via content delivery networks (cdn), making them load much faster to the end user. cdn benefits include caching for your site objects and edge locations (servers) that are geographically closer to your end users. static web sites are also generally more secure than dynamic sites. this is because there are significantly fewer attack vectors for flat html pages than with using an application server. popular content management systems such as wordpress and drupal have had exploits affecting millions of web sites. and new exploits for popular application servers and cms software are routinely discovered. in one example, a critical vulnerability in drupal was announced impacting 12 million websites, and any web site not patched within 7 hours was considered compromised. a critical vulnerability in wordpress could be considered even more serious as wordpress powers an estimated 25% of all websites globally. static vs dynamic a static web site is a website made up of “flat” or “stationary” files, that are delivered to the end user exactly as stored. most commonly, static websites are a collection of plain .html files. dynamic web sites, on the other hand, are generated for the user on the fly by an application server. an example of a dynamic web site would be any wordpress site. setting up a static web site at amazon aws with python to set up a static web site at aws, we’ll use 2 of their services: s3 and route53. s3 is an object storage service and this is where we’ll store the files that comprise our site. cloudfront is the aws content delivery network (cdn) service, that has edge locations distributed throughout the world, to ensure your end users are able to load your site as fast as possible. route53 is the domain name system (dns) which lets you host your domain name with aws. i’ll be using python to demonstrate creating the static site using aws services. aws provides a getting started: static website hosting tutorial if you want to manually perform these steps. prerequisite: install aws python sdk the examples use the aws python sdk to build the static site, so you’ll want to install it. for most people, this will typically be: pip install boto3 awscli once installed, we will create an aws configuration file with credentials and default settings such as preferred region: aws configure step 1: create s3 bucket for a static web site our new static web site will be stored in aws s3 so we’ll need to create a new bucket for the website’s files. creating a s3 bucket with python is simple: # load aws boto3 module import boto3 # specify the region to create the aws resources in default_region = "us-east-1" # create s3 resource s3 = boto3.resource('s3') # set a bucket name which will be our domain name. bucket_name = "demo123456.com" # create a new s3 bucket, using a demo bucket name s3.create_bucket(bucket=bucket_name) # we need to set an s3 policy for our bucket to # allow anyone read access to our bucket and files. # if we do not set this policy, people will not be # able to view our s3 static web site. bucket_policy = s3.bucketpolicy(bucket_name) policy_payload = { "version": "2012-10-17", "statement": [{ "sid": "allow public access to all objects", "effect": "allow", "principal": "*", "action": "s3:getobject", "resource": "arn:aws:s3:::%s/*" % (domain) } ] } # add the policy to the bucket response = bucket_policy.put(policy=json.dumps(policy_payload)) # next we'll set a basic configuration for the static # website. website_payload = { 'errordocument': { 'key': 'error.html' }, 'indexdocument': { 'suffix': 'index.html' } } # make our new s3 bucket a static website bucket_website = s3.bucketwebsite(bucket_name) # and configure the static website with our desired index.html # and error.html configuration. bucket_website.put(websiteconfiguration=website_payload) step 1.1: create s3 bucket for redirecting www.domain.com to root domain.com i like to redirect “www” to the root domain, such that www.domain.com will redirect to domain.com for the user. for this to work in aws, we’ll need to create a second bucket for the www hostname, and set the bucket to redirect. # load aws boto3 module import boto3 # specify the region to create the aws resources in default_region = "us-east-1" # create s3 resource s3 = boto3.resource('s3') # create a new s3 bucket, using the www demo bucket name bucket_name = "demo123456.com" redirect_bucket_name = "www.demo123456.com" s3.create_bucket(bucket=redirect_bucket_name) # the s3 settings to redirect to the root domain, # in this case the bucket_name variable from above. redirect_payload = { 'redirectallrequeststo': { 'hostname': '%s' % (bucket_name), 'protocol': 'http' } } # make our redirect bucket a s3 website bucket_website_redirect = s3.bucketwebsite(redirect_bucket_name) # set the new bucket to redirect to our root domain # with the redirect payload above. bucket_website_redirect.put(websiteconfiguration=redirect_payload) step 2: create a route53 hosted zone for the domain now that we have created an s3 bucket and web site for our new domain, we need to add the new domain to amazon aws dns service, called route53. in route53, we will create a new hosted zone for our domain name and add dns records for the root domain.com and the redirect www.domain.com to point to our corresponding s3 buckets. # load the aws boto3 module import boto3 # we'll want to generate a unique uuid later import uuid # specify the region to create the aws resources in default_region = "us-east-1" # a mapping of hosted zone ids to aws regions. # apparently this data is not accessible via api # http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region # https://forums.aws.amazon.com/thread.jspa?threadid=116724 s3_hosted_zone_ids = { 'us-east-1': 'z3aqbstgfyjstf', 'us-west-1': 'z2f56uzl2m1acd', 'us-west-2': 'z3bj6k6riion7m', 'ap-south-1': 'z11rgjofqnvjup', 'ap-northeast-1': 'z2m4ehur26p7zw', 'ap-northeast-2': 'z3w03o7b5ymiyp', 'ap-southeast-1': 'z3o0j2dxbe1ftb', 'ap-southeast-2': 'z1wcigyicn2byd', 'eu-central-1': 'z21dnduvltqw6q', 'eu-west-1': 'z1bkctxd74ezpe', 'sa-east-1': 'z7kqh4qjs55so', 'us-gov-west-1': 'z31gft0ua1i2hv', } # load route53 module route53 = boto3.client('route53') # define the domain name we want to add in route53 domain = "demo123456.com" www_redirect = "www.demo123456.com" # we need to create a unique string to identify the request. # a uuid4 string is an easy to use unique identifier. caller_reference_uuid = "%s" % (uuid.uuid4()) # create the new hosted zone in route53 response = route53.create_hosted_zone( name=domain, callerreference=caller_reference_uuid, hostedzoneconfig={'comment': domain, 'privatezone': false}) # get the newly created hosted zone id, used for # adding our dns records pointing to our s3 buckets hosted_zone_id = response['hostedzone']['id'] # add dns records for domain.com and www.domain.com website_dns_name = "s3-website-%s.amazonaws.com" % (default_region) redirect_dns_name = "s3-website-%s.amazonaws.com" % (default_region) # here is the payload we will send to route53 # we are creating two dns records: # one for domain.com to point to our s3 bucket, # and a second for www.domain.com to point to our # s3 redirect bucket, to redirect to domain.com change_batch_payload = { 'changes': [ { 'action': 'upsert', 'resourcerecordset': { 'name': domain, 'type': 'a', 'aliastarget': { 'hostedzoneid': s3_hosted_zone_ids[default_region], 'dnsname': website_dns_name, 'evaluatetargethealth': false } } }, { 'action': 'upsert', 'resourcerecordset': { 'name': www_redirect, 'type': 'a', 'aliastarget': { 'hostedzoneid': s3_hosted_zone_ids[default_region], 'dnsname': redirect_dns_name, 'evaluatetargethealth': false } } } ] } # create the dns records payload in route53 response = route53.change_resource_record_sets( hostedzoneid=hosted_zone_id, changebatch=change_batch_payload) add content to s3 bucket after creating our s3 buckets and added our domain name to route53, we have a few remaining tasks in order to make our new static web site live. first, we need to add an html page to our s3 bucket for our visitors to see. we can do this with python or we can use a static site generator site as jekyll to build our static site. here’s an example using python: # load the aws boto3 module import boto3 # set our domain name and bucket name # i use the domain as the bucket name, # such that they are the same domain = "demo123456.com" s3 = boto3.resource('s3') # very simple, basic html code for our landing page payload = ("%s" "

%s

" % (domain, domain)) # create the index.html page in s3 s3.object(domain, 'index.html').put(body=payload, contenttype='text/html') change nameservers at your domain registrar to point to aws route53 if we are using route53 for our dns services, we will need to update our nameservers at our domain name registrar to use route53. this step will vary from registrar to registrar and will most likely be a manual process because most registrars do not offer api access. on the aws route53 side, you’ll need to get your name servers for your new hosted zone, then you’ll go to your registrar, such as namecheap, godaddy, etc. and update your name server records there. your registrar will have documentation on how to perform the necessary updates in their dashboards. posted on december 4, 2016author nicholas kuechlercategories devops engineering, python, web developmenttags amazon, aws, python, route53, s3, wordpressleave a comment on create a static website at amazon aws using python, s3, and route53 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 posts navigation page 1 page 2 … page 7 next page copyright © 2005-2016 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: 6999

One word

Two words phrases

Three words phrases

the - 5.22% (365)
name - 2.09% (146)
our - 2.03% (142)
and - 1.83% (128)
serve - 1.77% (124)
server - 1.76% (123)
all - 1.6% (112)
for - 1.59% (111)
new - 1.5% (105)
ansible - 1.47% (103)
cloud - 1.43% (100)
create - 1.43% (100)
rackspace - 1.27% (89)
use - 1.23% (86)
not - 1.14% (80)
dns - 1.07% (75)
domain - 1% (70)
add - 1% (70)
with - 0.99% (69)
rax - 0.97% (68)
host - 0.96% (67)
}}" - 0.91% (64)
"{{ - 0.91% (64)
file - 0.87% (61)
note - 0.87% (61)
site - 0.8% (56)
name: - 0.79% (55)
install - 0.79% (55)
play - 0.76% (53)
playbook - 0.71% (50)
bucket - 0.71% (50)
record - 0.64% (45)
you - 0.64% (45)
web - 0.63% (44)
package - 0.59% (41)
virtual - 0.59% (41)
will - 0.57% (40)
virtualenv - 0.57% (40)
role - 0.57% (40)
task - 0.54% (38)
that - 0.53% (37)
his - 0.53% (37)
item - 0.51% (36)
credentials - 0.51% (36)
this - 0.51% (36)
work - 0.5% (35)
python - 0.5% (35)
packages - 0.5% (35)
key - 0.5% (35)
region - 0.49% (34)
can - 0.47% (33)
aws - 0.47% (33)
files - 0.47% (33)
one - 0.47% (33)
set - 0.46% (32)
user - 0.43% (30)
here - 0.43% (30)
servers - 0.43% (30)
text - 0.43% (30)
group - 0.41% (29)
ssh - 0.4% (28)
build - 0.4% (28)
created - 0.39% (27)
module - 0.39% (27)
website - 0.39% (27)
using - 0.37% (26)
local - 0.37% (26)
need - 0.37% (26)
low - 0.37% (26)
config - 0.36% (25)
static - 0.36% (25)
base - 0.34% (24)
able - 0.34% (24)
are - 0.34% (24)
redirect - 0.33% (23)
route53 - 0.33% (23)
specifies - 0.31% (22)
have - 0.31% (22)
tasks - 0.3% (21)
cook - 0.3% (21)
evernote - 0.3% (21)
pyrax - 0.3% (21)
let’s - 0.29% (20)
load - 0.29% (20)
root - 0.27% (19)
roles - 0.27% (19)
instance - 0.27% (19)
get - 0.27% (19)
want - 0.27% (19)
thomas - 0.27% (19)
edison - 0.27% (19)
put - 0.27% (19)
like - 0.27% (19)
action: - 0.26% (18)
call - 0.26% (18)
email - 0.26% (18)
your - 0.26% (18)
per - 0.26% (18)
inventor - 0.26% (18)
zone - 0.26% (18)
when - 0.26% (18)
slow - 0.26% (18)
local_action: - 0.24% (17)
drop - 0.24% (17)
configuration - 0.24% (17)
run - 0.24% (17)
hosted - 0.24% (17)
inventory - 0.24% (17)
source - 0.24% (17)
module: - 0.24% (17)
register - 0.24% (17)
cooker - 0.24% (17)
man - 0.23% (16)
access - 0.23% (16)
export - 0.23% (16)
pub - 0.23% (16)
git - 0.23% (16)
rackspace_cloud - 0.21% (15)
server. - 0.21% (15)
setting - 0.21% (15)
any - 0.21% (15)
here’s - 0.21% (15)
test - 0.21% (15)
credentials: - 0.21% (15)
ptr - 0.21% (15)
kuechler - 0.21% (15)
image - 0.21% (15)
apt - 0.2% (14)
with_items - 0.2% (14)
make - 0.2% (14)
favorite - 0.2% (14)
deploy - 0.2% (14)
nicholas - 0.2% (14)
output - 0.2% (14)
success - 0.2% (14)
html - 0.2% (14)
default - 0.2% (14)
rax_dns - 0.19% (13)
which - 0.19% (13)
payload - 0.19% (13)
with_items: - 0.19% (13)
but - 0.19% (13)
- 0.19% (13)
notes - 0.19% (13)
records - 0.19% (13)
two - 0.19% (13)
note: - 0.19% (13)
directory - 0.19% (13)
boto3 - 0.19% (13)
change - 0.19% (13)
what - 0.17% (12)
domain. - 0.17% (12)
www - 0.17% (12)
specify - 0.17% (12)
resource - 0.17% (12)
admin - 0.17% (12)
app - 0.17% (12)
register: - 0.17% (12)
github - 0.17% (12)
exist - 0.17% (12)
stew - 0.17% (12)
now - 0.17% (12)
beef - 0.17% (12)
plain - 0.17% (12)
flavor - 0.17% (12)
also - 0.17% (12)
network - 0.16% (11)
ever2text - 0.16% (11)
dropbox - 0.16% (11)
import - 0.16% (11)
nick - 0.16% (11)
read - 0.16% (11)
domain.com - 0.16% (11)
example - 0.16% (11)
user: - 0.16% (11)
sites - 0.16% (11)
dynamic - 0.16% (11)
hostname - 0.16% (11)
rax.instances - 0.16% (11)
item.rax_accessipv4 - 0.16% (11)
http - 0.16% (11)
update - 0.14% (10)
wait - 0.14% (10)
public - 0.14% (10)
was - 0.14% (10)
dns_email - 0.14% (10)
installed - 0.14% (10)
region: - 0.14% (10)
side - 0.14% (10)
such - 0.14% (10)
list - 0.14% (10)
domain, - 0.14% (10)
store - 0.14% (10)
mix - 0.14% (10)
quotes - 0.14% (10)
live - 0.14% (10)
bucket_name - 0.14% (10)
data - 0.14% (10)
other - 0.14% (10)
hosts - 0.14% (10)
users - 0.14% (10)
amazon - 0.14% (10)
policy - 0.13% (9)
uuid - 0.13% (9)
demo - 0.13% (9)
adding - 0.13% (9)
variable - 0.13% (9)
named - 0.13% (9)
page - 0.13% (9)
over - 0.13% (9)
key_name - 0.13% (9)
full - 0.13% (9)
there - 0.13% (9)
vars - 0.13% (9)
enhancedtest.net - 0.13% (9)
state - 0.13% (9)
notebook - 0.13% (9)
most - 0.13% (9)
service - 0.13% (9)
some - 0.13% (9)
python, - 0.13% (9)
just - 0.13% (9)
recipe - 0.13% (9)
quart - 0.13% (9)
server, - 0.11% (8)
.html - 0.11% (8)
look - 0.11% (8)
we’ll - 0.11% (8)
meat - 0.11% (8)
very - 0.11% (8)
creating - 0.11% (8)
were - 0.11% (8)
see - 0.11% (8)
request - 0.11% (8)
fully - 0.11% (8)
me, - 0.11% (8)
from - 0.1% (7)
inventory. - 0.1% (7)
private - 0.1% (7)
build-cloud-server.yml - 0.1% (7)
ansible-rackspace-servers - 0.1% (7)
we’re - 0.1% (7)
api - 0.1% (7)
newly - 0.1% (7)
did - 0.1% (7)
option - 0.1% (7)
registrar - 0.1% (7)
content - 0.1% (7)
sure - 0.1% (7)
default_region - 0.1% (7)
perform - 0.1% (7)
off - 0.1% (7)
system - 0.1% (7)
them - 0.1% (7)
end - 0.09% (6)
more - 0.09% (6)
how - 0.09% (6)
both - 0.09% (6)
present - 0.09% (6)
comment - 0.09% (6)
files: - 0.09% (6)
image: - 0.09% (6)
flavor: - 0.09% (6)
stored - 0.09% (6)
gather_facts: - 0.09% (6)
than - 0.09% (6)
hosts: - 0.09% (6)
address - 0.09% (6)
simple - 0.09% (6)
virtualenv-inventory.yml - 0.09% (6)
first - 0.09% (6)
false - 0.09% (6)
added - 0.09% (6)
files. - 0.09% (6)
name, - 0.09% (6)
site. - 0.09% (6)
installing - 0.09% (6)
find - 0.09% (6)
then - 0.09% (6)
automatic - 0.09% (6)
important - 0.09% (6)
add_host - 0.09% (6)
location - 0.09% (6)
mean - 0.09% (6)
its - 0.09% (6)
email: - 0.09% (6)
type: - 0.09% (6)
data: - 0.09% (6)
domain: - 0.09% (6)
rax_dns_record - 0.09% (6)
notebooks - 0.09% (6)
groupname: - 0.07% (5)
work. - 0.07% (5)
ansible. - 0.07% (5)
activate - 0.07% (5)
could - 0.07% (5)
broth - 0.07% (5)
mixture - 0.07% (5)
entries - 0.07% (5)
migrating - 0.07% (5)
vegetable - 0.07% (5)
automatically - 0.07% (5)
servers. - 0.07% (5)
their - 0.07% (5)
teaspoon - 0.07% (5)
route53. - 0.07% (5)
object - 0.07% (5)
hand - 0.07% (5)
come - 0.07% (5)
has - 0.07% (5)
means - 0.07% (5)
edit - 0.07% (5)
aws. - 0.07% (5)
notes. - 0.07% (5)
hostname: - 0.07% (5)
.rackspace_cloud_credentials - 0.07% (5)
without - 0.07% (5)
ansible_ssh_user: - 0.07% (5)
trading - 0.07% (5)
yes - 0.07% (5)
before - 0.07% (5)
ansible_ssh_host: - 0.07% (5)
playbook, - 0.07% (5)
ansible-playbook - 0.07% (5)
does - 0.07% (5)
item.name - 0.07% (5)
include - 0.07% (5)
way - 0.07% (5)
packages. - 0.07% (5)
“base” - 0.07% (5)
up. - 0.07% (5)
meta - 0.07% (5)
playbook. - 0.07% (5)
inventing - 0.07% (5)
i’ve - 0.07% (5)
because - 0.07% (5)
localhost - 0.07% (5)
playbook: - 0.07% (5)
wordpress - 0.07% (5)
work, - 0.07% (5)
we’ve - 0.07% (5)
cut - 0.07% (5)
www.domain.com - 0.07% (5)
they - 0.07% (5)
people - 0.07% (5)
step - 0.07% (5)
configure - 0.07% (5)
point - 0.07% (5)
hosted_zone_id - 0.07% (5)
kuechlercategories - 0.07% (5)
next - 0.07% (5)
posted - 0.07% (5)
settings - 0.06% (4)
used - 0.06% (4)
quotes: - 0.06% (4)
together - 0.06% (4)
should - 0.06% (4)
aka - 0.06% (4)
installed, - 0.06% (4)
basic - 0.06% (4)
would - 0.06% (4)
celery - 0.06% (4)
through - 0.06% (4)
time - 0.06% (4)
save - 0.06% (4)
vegetables - 0.06% (4)
once - 0.06% (4)
forward - 0.06% (4)
benefit - 0.06% (4)
pip - 0.06% (4)
it: - 0.06% (4)
looks - 0.06% (4)
changed - 0.06% (4)
ready - 0.06% (4)
cooker, - 0.06% (4)
bowl - 0.06% (4)
ingredients - 0.06% (4)
linux - 0.06% (4)
distro - 0.06% (4)
1/2 - 0.06% (4)
file, - 0.06% (4)
had - 0.06% (4)
chop - 0.06% (4)
hours - 0.06% (4)
networks - 0.06% (4)
since - 0.06% (4)
real - 0.06% (4)
flour - 0.06% (4)
salt - 0.06% (4)
tasks: - 0.06% (4)
username - 0.06% (4)
ubuntu - 0.06% (4)
lot - 0.06% (4)
manual - 0.06% (4)
successfully - 0.06% (4)
name. - 0.06% (4)
every - 0.06% (4)
tool - 0.06% (4)
server: - 0.06% (4)
allow - 0.06% (4)
bucket_website - 0.06% (4)
ever2text: - 0.06% (4)
devices - 0.06% (4)
different - 0.06% (4)
title - 0.06% (4)
plan - 0.06% (4)
things - 0.06% (4)
only - 0.06% (4)
about - 0.06% (4)
response - 0.06% (4)
specified - 0.06% (4)
index.html - 0.06% (4)
enex - 0.06% (4)
--- - 0.06% (4)
ids - 0.06% (4)
"demo123456.com" - 0.06% (4)
s3, - 0.06% (4)
bucket, - 0.06% (4)
-vvvv - 0.04% (3)
instead - 0.04% (3)
earlier - 0.04% (3)
admin@enhancedtest.net - 0.04% (3)
/users/nick/.rackspace_cloud_credentials - 0.04% (3)
making - 0.04% (3)
dns_email: - 0.04% (3)
password - 0.04% (3)
projects - 0.04% (3)
doesn’t - 0.04% (3)
dropping - 0.04% (3)
existing - 0.04% (3)
editing - 0.04% (3)
addition - 0.04% (3)
below - 0.04% (3)
top - 0.04% (3)
key's - 0.04% (3)
/root/.ssh/authorized_keys: - 0.04% (3)
item.id - 0.04% (3)
0766e5df-d60a-4100-ae8c-07f27ec0148f - 0.04% (3)
dfw - 0.04% (3)
version - 0.04% (3)
connection: - 0.04% (3)
future - 0.04% (3)
already - 0.04% (3)
vars: - 0.04% (3)
enjoy - 0.04% (3)
boto3.resource('s3') - 0.04% (3)
control - 0.04% (3)
panel, - 0.04% (3)
admin.enhancedtest.net - 0.04% (3)
true - 0.04% (3)
cdn - 0.04% (3)
roles: - 0.04% (3)
performance1-1 - 0.04% (3)
s3_hosted_zone_ids - 0.04% (3)
give - 0.04% (3)
it’s - 0.04% (3)
main.yml - 0.04% (3)
changes - 0.04% (3)
ptr_record - 0.04% (3)
/users/nick/.ssh/id_rsa.pub - 0.04% (3)
dns. - 0.04% (3)
apt: - 0.04% (3)
group. - 0.04% (3)
(public - 0.04% (3)
nginx - 0.04% (3)
(10. - 0.04% (3)
route53, - 0.04% (3)
net) - 0.04% (3)
networks: - 0.04% (3)
metadata - 0.04% (3)
#group: - 0.04% (3)
own - 0.04% (3)
vim - 0.04% (3)
cover - 0.04% (3)
health - 0.04% (3)
term - 0.04% (3)
prefer - 0.04% (3)
code - 0.04% (3)
directories - 0.04% (3)
names - 0.04% (3)
“deploy” - 0.04% (3)
ways - 0.04% (3)
“roles” - 0.04% (3)
called - 0.04% (3)
playbooks - 0.04% (3)
again - 0.04% (3)
via - 0.04% (3)
buckets - 0.04% (3)
benefits - 0.04% (3)
use, - 0.04% (3)
unique - 0.04% (3)
upon - 0.04% (3)
creation - 0.04% (3)
screen - 0.04% (3)
success! - 0.04% (3)
my_rackspace_key - 0.04% (3)
state: - 0.04% (3)
tutorial - 0.04% (3)
generate - 0.04% (3)
until - 0.04% (3)
resources - 0.04% (3)
proceeding - 0.04% (3)
wait: - 0.04% (3)
a_record - 0.04% (3)
id, - 0.04% (3)
"us-east-1" - 0.04% (3)
#key_name: - 0.04% (3)
ipv4) - 0.04% (3)
write - 0.04% (3)
prep - 0.04% (3)
you’ll - 0.04% (3)
needed - 0.04% (3)
websites - 0.04% (3)
something - 0.04% (3)
nick@mbp: - 0.04% (3)
~/virtualenvs$ - 0.04% (3)
bowl, - 0.04% (3)
work. – - 0.04% (3)
contains - 0.04% (3)
created, - 0.04% (3)
first, - 0.04% (3)
nor - 0.04% (3)
together. - 0.04% (3)
pyrax, - 0.04% (3)
workstation: - 0.04% (3)
ahead - 0.04% (3)
virtualenv. - 0.04% (3)
everything - 0.04% (3)
cloud. - 0.04% (3)
couple - 0.04% (3)
file. - 0.04% (3)
start - 0.04% (3)
where - 0.04% (3)
ansible, - 0.04% (3)
servers, - 0.04% (3)
ability - 0.04% (3)
mixture. - 0.04% (3)
routine - 0.04% (3)
aws, - 0.04% (3)
made - 0.04% (3)
same - 0.04% (3)
inside - 0.04% (3)
rather - 0.04% (3)
building - 0.04% (3)
complete - 0.04% (3)
files, - 0.04% (3)
came - 0.04% (3)
ansible-rackspace-servers-example - 0.04% (3)
lets - 0.04% (3)
github: - 0.04% (3)
place - 0.04% (3)
pure - 0.04% (3)
ansible_python_interpreter - 0.04% (3)
included - 0.04% (3)
mkdir - 0.04% (3)
large - 0.04% (3)
application - 0.04% (3)
december - 0.04% (3)
example, - 0.04% (3)
these - 0.04% (3)
try - 0.04% (3)
redirect_bucket_name - 0.04% (3)
strict - 0.04% (3)
small - 0.04% (3)
lives - 0.04% (3)
happens - 0.04% (3)
devops - 0.04% (3)
1/4 - 0.04% (3)
recipes - 0.04% (3)
after - 0.04% (3)
working - 0.04% (3)
file: - 0.04% (3)
dropbox, - 0.04% (3)
many - 0.04% (3)
5-6 - 0.03% (2)
good - 0.03% (2)
percent - 0.03% (2)
common - 0.03% (2)
high - 0.03% (2)
pages - 0.03% (2)
hours. - 0.03% (2)
future. - 0.03% (2)
dns, - 0.03% (2)
garlic - 0.03% (2)
website_payload - 0.03% (2)
great - 0.03% (2)
world - 0.03% (2)
playbooks. - 0.03% (2)
hard - 0.03% (2)
reward - 0.03% (2)
administrator - 0.03% (2)
definitely - 0.03% (2)
anything - 0.03% (2)
recap - 0.03% (2)
status - 0.03% (2)
who - 0.03% (2)
failed - 0.03% (2)
2014author - 0.03% (2)
search - 0.03% (2)
overall - 0.03% (2)
recent - 0.03% (2)
failures - 0.03% (2)
'index.html' - 0.03% (2)
close - 0.03% (2)
posts - 0.03% (2)
edison, - 0.03% (2)
invention - 0.03% (2)
cheap, - 0.03% (2)
reading - 0.03% (2)
won’t - 0.03% (2)
bay - 0.03% (2)
seasoned - 0.03% (2)
pepper - 0.03% (2)
redirect. - 0.03% (2)
cup - 0.03% (2)
onion - 0.03% (2)
expand - 0.03% (2)
sticks - 0.03% (2)
chopped - 0.03% (2)
installation - 0.03% (2)
"www.demo123456.com" - 0.03% (2)
going - 0.03% (2)
it! - 0.03% (2)
part - 0.03% (2)
pound - 0.03% (2)
cubes - 0.03% (2)
easily - 0.03% (2)
final - 0.03% (2)
inch - 0.03% (2)
case - 0.03% (2)
meat, - 0.03% (2)
we'll - 0.03% (2)
cooker. - 0.03% (2)
leaf - 0.03% (2)
standard - 0.03% (2)
website. - 0.03% (2)
method - 0.03% (2)
individual - 0.03% (2)
second - 0.03% (2)
dice - 0.03% (2)
update_cache=yes - 0.03% (2)
i’m - 0.03% (2)
state=installed - 0.03% (2)
pkg={{ - 0.03% (2)
tools - 0.03% (2)
tags: - 0.03% (2)
bucket_website_redirect - 0.03% (2)
decide - 0.03% (2)
coat - 0.03% (2)
hostname, - 0.03% (2)
proverb - 0.03% (2)
structure - 0.03% (2)
stir - 0.03% (2)
redirect_payload - 0.03% (2)
subdirectory - 0.03% (2)
above. - 0.03% (2)
role, - 0.03% (2)
sauce - 0.03% (2)
worcestershire - 0.03% (2)
paprika - 0.03% (2)
minced - 0.03% (2)
ingredients. - 0.03% (2)
sdk - 0.03% (2)
again? - 0.03% (2)
million - 0.03% (2)
us. - 0.03% (2)
virtualenv, - 0.03% (2)
generated - 0.03% (2)
sites, - 0.03% (2)
preferred - 0.03% (2)
this: - 0.03% (2)
considered - 0.03% (2)
rackspace_cloud/bin/python - 0.03% (2)
been - 0.03% (2)
rackspace_cloud/bin/activate - 0.03% (2)
activated - 0.03% (2)
“rackspace_cloud” - 0.03% (2)
prerequisite - 0.03% (2)
within - 0.03% (2)
calls - 0.03% (2)
evernote, - 0.03% (2)
'evaluatetargethealth': - 0.03% (2)
popular - 0.03% (2)
s3_hosted_zone_ids[default_region], - 0.03% (2)
drupal - 0.03% (2)
exploits - 0.03% (2)
'dnsname': - 0.03% (2)
critical - 0.03% (2)
stricthostkeychecking=no - 0.03% (2)
few - 0.03% (2)
.ansible.cfg - 0.03% (2)
automation - 0.03% (2)
confirm - 0.03% (2)
vulnerability - 0.03% (2)
there’s - 0.03% (2)
announced - 0.03% (2)
(domain, - 0.03% (2)
31, - 0.03% (2)
flat - 0.03% (2)
tablet - 0.03% (2)
exports - 0.03% (2)
migrate - 0.03% (2)
free - 0.03% (2)
devices, - 0.03% (2)
plans. - 0.03% (2)
here. - 0.03% (2)
2016author - 0.03% (2)
manually - 0.03% (2)
- 0.03% (2)
started - 0.03% (2)
best - 0.03% (2)
create, - 0.03% (2)
necessary - 0.03% (2)
phone - 0.03% (2)
fast - 0.03% (2)
nameservers - 0.03% (2)
(cdn) - 0.03% (2)
clicking - 0.03% (2)
it. - 0.03% (2)
each - 0.03% (2)
issue - 0.03% (2)
etc. - 0.03% (2)
raw - 0.03% (2)
while - 0.03% (2)
ensure - 0.03% (2)
markdown - 0.03% (2)
service, - 0.03% (2)
preserving - 0.03% (2)
format. - 0.03% (2)
across - 0.03% (2)
exporting - 0.03% (2)
path - 0.03% (2)
'hostedzoneid': - 0.03% (2)
existed - 0.03% (2)
left - 0.03% (2)
centos - 0.03% (2)
happens! - 0.03% (2)
uuid4 - 0.03% (2)
string - 0.03% (2)
denotes - 0.03% (2)
really - 0.03% (2)
verbose - 0.03% (2)
debug - 0.03% (2)
troubleshoot - 0.03% (2)
reverse - 0.03% (2)
caching - 0.03% (2)
www_redirect - 0.03% (2)
another - 0.03% (2)
record, - 0.03% (2)
winner - 0.03% (2)
options - 0.03% (2)
geo - 0.03% (2)
settings: - 0.03% (2)
contact - 0.03% (2)
"allow - 0.03% (2)
yet - 0.03% (2)
policy_payload - 0.03% (2)
cooking - 0.03% (2)
section - 0.03% (2)
investing - 0.03% (2)
“vars” - 0.03% (2)
bucket_policy - 0.03% (2)
internal - 0.03% (2)
ansible’s - 0.03% (2)
“rax” - 0.03% (2)
registered - 0.03% (2)
ones - 0.03% (2)
uses - 0.03% (2)
'aliastarget': - 0.03% (2)
redirect_dns_name - 0.03% (2)
piece - 0.03% (2)
'a', - 0.03% (2)
'type': - 0.03% (2)
'name': - 0.03% (2)
'resourcerecordset': - 0.03% (2)
build-cloud-server.yml. - 0.03% (2)
sites. - 0.03% (2)
'upsert', - 0.03% (2)
'action': - 0.03% (2)
change_batch_payload - 0.03% (2)
generally - 0.03% (2)
locations - 0.03% (2)
edge - 0.03% (2)
objects - 0.03% (2)
user. - 0.03% (2)
fedora - 0.03% (2)
delivered - 0.03% (2)
easy - 0.03% (2)
jekyll - 0.03% (2)
converts - 0.03% (2)
caller_reference_uuid - 0.03% (2)
opportunity - 0.03% (2)
yum - 0.03% (2)
delivery - 0.03% (2)
(default_region) - 0.03% (2)
website_dns_name - 0.03% (2)
"s3-website-%s.amazonaws.com" - 0.03% (2)
pvhvm - 0.03% (2)
14.10 - 0.03% (2)
much - 0.03% (2)
error.html - 0.03% (2)
- 0.03% (2)
rackspace cloud - 0.8% (56)
cloud server - 0.61% (43)
create a - 0.56% (39)
the new - 0.44% (31)
- name: - 0.43% (30)
in the - 0.39% (27)
to create - 0.36% (25)
to the - 0.33% (23)
need to - 0.3% (21)
that we - 0.29% (20)
new server - 0.29% (20)
thomas edison - 0.27% (19)
static web - 0.26% (18)
slow cooker - 0.24% (17)
for the - 0.24% (17)
local_action: module: - 0.24% (17)
our new - 0.24% (17)
name: "{{ - 0.24% (17)
the server - 0.23% (16)
for our - 0.23% (16)
to install - 0.23% (16)
web site - 0.23% (16)
of our - 0.21% (15)
of the - 0.2% (14)
we want - 0.2% (14)
name }}" - 0.2% (14)
specifies the - 0.2% (14)
we will - 0.2% (14)
cloud servers - 0.2% (14)
s3 bucket - 0.19% (13)
to add - 0.19% (13)
task to - 0.19% (13)
module: rax - 0.17% (12)
"{{ credentials - 0.17% (12)
}}" name: - 0.17% (12)
we need - 0.17% (12)
credentials: "{{ - 0.17% (12)
new rackspace - 0.17% (12)
credentials }}" - 0.17% (12)
cloud dns - 0.16% (11)
user: root - 0.16% (11)
with a - 0.16% (11)
create the - 0.16% (11)
domain name - 0.16% (11)
the play - 0.16% (11)
install a - 0.16% (11)
new cloud - 0.16% (11)
is the - 0.16% (11)
the rackspace - 0.16% (11)
you can - 0.16% (11)
"{{ item.rax_accessipv4 - 0.16% (11)
our server - 0.16% (11)
with_items: rax.instances - 0.16% (11)
item.rax_accessipv4 }}" - 0.16% (11)
we can - 0.16% (11)
to use - 0.16% (11)
want to - 0.14% (10)
and an - 0.14% (10)
text files - 0.14% (10)
at the - 0.14% (10)
ansible playbook - 0.14% (10)
to our - 0.14% (10)
the domain - 0.14% (10)
the ansible - 0.14% (10)
the output - 0.14% (10)
configuration file - 0.14% (10)
a record - 0.14% (10)
beef stew - 0.14% (10)
the playbook - 0.14% (10)
plain text - 0.14% (10)
module: rax_dns - 0.13% (9)
on the - 0.13% (9)
a static - 0.13% (9)
all of - 0.13% (9)
name: dns - 0.13% (9)
"{{ name - 0.13% (9)
ansible in - 0.13% (9)
server i - 0.13% (9)
ptr record - 0.13% (9)
ansible role - 0.13% (9)
an ansible - 0.13% (9)
server to - 0.13% (9)
- specifies - 0.13% (9)
quart slow - 0.11% (8)
playbook to - 0.11% (8)
new domain - 0.11% (8)
to build - 0.11% (8)
have a - 0.11% (8)
dns records - 0.11% (8)
to drop - 0.11% (8)
this is - 0.11% (8)
using a - 0.11% (8)
list of - 0.11% (8)
the aws - 0.11% (8)
and ansible - 0.11% (8)
the virtualenv - 0.11% (8)
we have - 0.11% (8)
with the - 0.11% (8)
enhancedtest.net # - 0.1% (7)
such as - 0.1% (7)
newly created - 0.1% (7)
use the - 0.1% (7)
install packages - 0.1% (7)
and install - 0.1% (7)
static website - 0.1% (7)
now that - 0.1% (7)
# create - 0.1% (7)
base packages - 0.1% (7)
our domain - 0.1% (7)
a rackspace - 0.1% (7)
favorite packages - 0.1% (7)
inventory file - 0.1% (7)
all ansible - 0.09% (6)
in rackspace - 0.09% (6)
the host - 0.09% (6)
ansible task - 0.09% (6)
packages on - 0.09% (6)
our favorite - 0.09% (6)
that i - 0.09% (6)
name we - 0.09% (6)
install our - 0.09% (6)
request local_action: - 0.09% (6)
record local_action: - 0.09% (6)
module: rax_dns_record - 0.09% (6)
pyrax and - 0.09% (6)
"{{ domain - 0.09% (6)
evernote to - 0.09% (6)
domain }}" - 0.09% (6)
the region - 0.09% (6)
data: "{{ - 0.09% (6)
in our - 0.09% (6)
side of - 0.09% (6)
3 quart - 0.09% (6)
region: "{{ - 0.09% (6)
role to - 0.09% (6)
server - - 0.09% (6)
# this - 0.09% (6)
base role - 0.09% (6)
- domain - 0.09% (6)
region }}" - 0.09% (6)
register: rax - 0.09% (6)
}}" data: - 0.09% (6)
}}" type: - 0.09% (6)
"{{ region - 0.09% (6)
add to - 0.09% (6)
i like - 0.09% (6)
rax.instances register: - 0.09% (6)
}}" region: - 0.09% (6)
like to - 0.09% (6)
host group - 0.09% (6)
specify the - 0.09% (6)
# specify - 0.09% (6)
rax_dns_record credentials: - 0.09% (6)
hosted zone - 0.09% (6)
- create - 0.09% (6)
be using - 0.07% (5)
created a - 0.07% (5)
here are - 0.07% (5)
to dropbox - 0.07% (5)
using the - 0.07% (5)
of evernote - 0.07% (5)
output from - 0.07% (5)
nicholas kuechlercategories - 0.07% (5)
run the - 0.07% (5)
playbook a - 0.07% (5)
# note: - 0.07% (5)
tasks i - 0.07% (5)
name - - 0.07% (5)
this will - 0.07% (5)
with our - 0.07% (5)
to export - 0.07% (5)
a virtualenv - 0.07% (5)
posted on - 0.07% (5)
with ansible - 0.07% (5)
name: install - 0.07% (5)
the task - 0.07% (5)
make a - 0.07% (5)
new server, - 0.07% (5)
i have - 0.07% (5)
off of - 0.07% (5)
bucket name - 0.07% (5)
to redirect - 0.07% (5)
groupname: deploy - 0.07% (5)
dns entries - 0.07% (5)
# load - 0.07% (5)
deploy with_items: - 0.07% (5)
ansible_ssh_user: root - 0.07% (5)
}}" ansible_ssh_host: - 0.07% (5)
here’s the - 0.07% (5)
root domain - 0.07% (5)
and add - 0.07% (5)
to host - 0.07% (5)
ansible_ssh_host: "{{ - 0.07% (5)
server # - 0.07% (5)
will be - 0.07% (5)
add new - 0.07% (5)
group local_action: - 0.07% (5)
setting up - 0.07% (5)
stew recipe - 0.07% (5)
}}" ansible_ssh_user: - 0.07% (5)
server hosts: - 0.07% (5)
amazon aws - 0.07% (5)
ansible roles - 0.07% (5)
root groupname: - 0.07% (5)
add dns - 0.07% (5)
add_host hostname: - 0.07% (5)
"{{ item.name - 0.07% (5)
our s3 - 0.07% (5)
item.name }}" - 0.07% (5)
module: add_host - 0.07% (5)
hostname: "{{ - 0.07% (5)
name: add - 0.07% (5)
bucket a - 0.07% (5)
to your - 0.07% (5)
can use - 0.07% (5)
bucket for - 0.07% (5)
new python - 0.06% (4)
make sure - 0.06% (4)
a list - 0.06% (4)
dropbox with - 0.06% (4)
fully created - 0.06% (4)
module import - 0.06% (4)
the pyrax - 0.06% (4)
a server - 0.06% (4)
new file - 0.06% (4)
looks like - 0.06% (4)
we’re using - 0.06% (4)
aws boto3 - 0.06% (4)
work with - 0.06% (4)
just created - 0.06% (4)
let’s make - 0.06% (4)
server is - 0.06% (4)
to specify - 0.06% (4)
email address - 0.06% (4)
python virtual - 0.06% (4)
packages i - 0.06% (4)
boto3 # - 0.06% (4)
the static - 0.06% (4)
rax.instances - - 0.06% (4)
will use - 0.06% (4)
ever2text: migrating - 0.06% (4)
with rackspace - 0.06% (4)
at amazon - 0.06% (4)
creating a - 0.06% (4)
and route53 - 0.06% (4)
file for - 0.06% (4)
comment on - 0.06% (4)
build the - 0.06% (4)
there are - 0.06% (4)
to point - 0.06% (4)
both a - 0.06% (4)
also be - 0.06% (4)
pyrax configuration - 0.06% (4)
the hostname - 0.06% (4)
using an - 0.06% (4)
i create - 0.06% (4)
= "demo123456.com" - 0.06% (4)
the meat - 0.06% (4)
the bucket - 0.06% (4)
build our - 0.06% (4)
linux distro - 0.06% (4)
as the - 0.06% (4)
tasks: - - 0.06% (4)
favorite quotes: - 0.06% (4)
edison on - 0.06% (4)
with plain - 0.06% (4)
playbook: - - 0.06% (4)
here is - 0.06% (4)
when i - 0.06% (4)
migrating off - 0.06% (4)
for this - 0.06% (4)
specifies that - 0.06% (4)
point to - 0.06% (4)
lot of - 0.06% (4)
add the - 0.06% (4)
boto3 module - 0.06% (4)
import boto3 - 0.06% (4)
to exist - 0.06% (4)
name and - 0.06% (4)
adding the - 0.06% (4)
use with - 0.06% (4)
the name - 0.06% (4)
set up - 0.06% (4)
slow cooker, - 0.06% (4)
will also - 0.06% (4)
without a - 0.06% (4)
the newly - 0.06% (4)
to run - 0.06% (4)
so that - 0.06% (4)
variable named - 0.04% (3)
}}" email: - 0.04% (3)
rax register: - 0.04% (3)
item.id }}" - 0.04% (3)
domain: "{{ - 0.04% (3)
create new - 0.04% (3)
type: ptr - 0.04% (3)
register: ptr_record - 0.04% (3)
in this - 0.04% (3)
server: "{{ - 0.04% (3)
create ptr - 0.04% (3)
type: a - 0.04% (3)
of base - 0.04% (3)
register is - 0.04% (3)
use ansible - 0.04% (3)
"{{ dns_email - 0.04% (3)
created cloud - 0.04% (3)
deploy # - 0.04% (3)
create request - 0.04% (3)
}}" register: - 0.04% (3)
-i virtualenv-inventory.yml - 0.04% (3)
and our - 0.04% (3)
new task - 0.04% (3)
the playbook, - 0.04% (3)
- domain: - 0.04% (3)
term to - 0.04% (3)
note: the - 0.04% (3)
the playbook: - 0.04% (3)
group #group: - 0.04% (3)
dns_email: admin@enhancedtest.net - 0.04% (3)
output in - 0.04% (3)
save the - 0.04% (3)
register: a_record - 0.04% (3)
can do - 0.04% (3)
new server. - 0.04% (3)
our playbook. - 0.04% (3)
the list - 0.04% (3)
instance to - 0.04% (3)
top of - 0.04% (3)
using for - 0.04% (3)
the top - 0.04% (3)
vars at - 0.04% (3)
when creating - 0.04% (3)
have to - 0.04% (3)
rax_dns credentials: - 0.04% (3)
inside of - 0.04% (3)
here’s what - 0.04% (3)
creation #key_name: - 0.04% (3)
network (public - 0.04% (3)
a public - 0.04% (3)
want both - 0.04% (3)
state: present - 0.04% (3)
present means - 0.04% (3)
state - - 0.04% (3)
proceeding wait: - 0.04% (3)
created before - 0.04% (3)
is fully - 0.04% (3)
wait until - 0.04% (3)
we should - 0.04% (3)
wait - - 0.04% (3)
"{{ files - 0.04% (3)
my_rackspace_key files: - 0.04% (3)
server upon - 0.04% (3)
private network - 0.04% (3)
files: /root/.ssh/authorized_keys: - 0.04% (3)
when you - 0.04% (3)
server by - 0.04% (3)
editing key_name - 0.04% (3)
below to - 0.04% (3)
your key's - 0.04% (3)
name. - - 0.04% (3)
/users/nick/.ssh/id_rsa.pub tasks: - 0.04% (3)
cloud key - 0.04% (3)
server build - 0.04% (3)
flavor: "{{ - 0.04% (3)
flavor }}" - 0.04% (3)
image: "{{ - 0.04% (3)
image }}" - 0.04% (3)
# key_name - 0.04% (3)
ipv4) and - 0.04% (3)
(10. aka - 0.04% (3)
a file, - 0.04% (3)
ptr with_items: - 0.04% (3)
edison quotes - 0.04% (3)
work. – thomas - 0.04% (3)
quotes on - 0.04% (3)
and inventing - 0.04% (3)
work, success - 0.04% (3)
quotes: thomas - 0.04% (3)
a comment - 0.04% (3)
the slow - 0.04% (3)
the ingredients - 0.04% (3)
the vegetables - 0.04% (3)
1/4 teaspoon - 0.04% (3)
cut in - 0.04% (3)
my github: - 0.04% (3)
example on - 0.04% (3)
"{{ item.id - 0.04% (3)
service net) - 0.04% (3)
#group: deploy - 0.04% (3)
networks: - - 0.04% (3)
private - - 0.04% (3)
public # - 0.04% (3)
group - - 0.04% (3)
specifies metadata - 0.04% (3)
server group - 0.04% (3)
# register - 0.04% (3)
}}" server: - 0.04% (3)
ansible term - 0.04% (3)
to save - 0.04% (3)
a variable - 0.04% (3)
named rax - 0.04% (3)
}}" domain: - 0.04% (3)
a with_items: - 0.04% (3)
stored rackspace - 0.04% (3)
dropping in - 0.04% (3)
add an - 0.04% (3)
on our - 0.04% (3)
apt update - 0.04% (3)
package install - 0.04% (3)
write a - 0.04% (3)
metadata to - 0.04% (3)
roles will - 0.04% (3)
roles to - 0.04% (3)
if you - 0.04% (3)
the important - 0.04% (3)
root gather_facts: - 0.04% (3)
deploy user: - 0.04% (3)
run apt - 0.04% (3)
of packages - 0.04% (3)
the same - 0.04% (3)
new ansible - 0.04% (3)
ahead and - 0.04% (3)
hosts: deploy - 0.04% (3)
email: "{{ - 0.04% (3)
localhost user: - 0.04% (3)
root connection: - 0.04% (3)
local gather_facts: - 0.04% (3)
false vars: - 0.04% (3)
- dns_email: - 0.04% (3)
domain create - 0.04% (3)
dns_email }}" - 0.04% (3)
server and - 0.04% (3)
register: rax_dns - 0.04% (3)
can be - 0.04% (3)
added successfully - 0.04% (3)
was added - 0.04% (3)
what happens - 0.04% (3)
and no - 0.04% (3)
our base - 0.04% (3)
gather_facts: true - 0.04% (3)
instead of - 0.04% (3)
cloud region - 0.04% (3)
a password - 0.04% (3)
in without - 0.04% (3)
can ssh - 0.04% (3)
automatically when - 0.04% (3)
pub key - 0.04% (3)
my ssh - 0.04% (3)
drop in - 0.04% (3)
credentials: /users/nick/.rackspace_cloud_credentials - 0.04% (3)
earlier - - 0.04% (3)
we created - 0.04% (3)
our pyrax - 0.04% (3)
location of - 0.04% (3)
# credentials - 0.04% (3)
region: dfw - 0.04% (3)
region is - 0.04% (3)
roles: - - 0.04% (3)
admin.enhancedtest.net # - 0.04% (3)
- base - 0.04% (3)
in other - 0.04% (3)
new base - 0.04% (3)
domain: enhancedtest.net - 0.04% (3)
will see - 0.04% (3)
control panel, - 0.04% (3)
the flavor - 0.04% (3)
image: 0766e5df-d60a-4100-ae8c-07f27ec0148f - 0.04% (3)
server side - 0.04% (3)
instance - - 0.04% (3)
flavor: performance1-1 - 0.04% (3)
image specifies - 0.04% (3)
the linux - 0.04% (3)
distro we - 0.04% (3)
server with - 0.04% (3)
until the - 0.04% (3)
# group - 0.04% (3)
a couple - 0.04% (3)
our virtualenv - 0.04% (3)
virtualenv inventory - 0.04% (3)
we’ve just - 0.04% (3)
a dynamic - 0.04% (3)
the inventory - 0.04% (3)
since we - 0.04% (3)
from my - 0.04% (3)
name: create - 0.04% (3)
go ahead - 0.04% (3)
my workstation: - 0.04% (3)
what the - 0.04% (3)
pip install - 0.04% (3)
we’ll need - 0.04% (3)
able to - 0.04% (3)
sites are - 0.04% (3)
hosts: localhost - 0.04% (3)
for use - 0.04% (3)
flavor specifies - 0.04% (3)
- image: - 0.04% (3)
use for - 0.04% (3)
the image - 0.04% (3)
performance1-1 # - 0.04% (3)
- flavor: - 0.04% (3)
our instance - 0.04% (3)
name: admin.enhancedtest.net - 0.04% (3)
connection: local - 0.04% (3)
hostname of - 0.04% (3)
be the - 0.04% (3)
panel, and - 0.04% (3)
cloud control - 0.04% (3)
see in - 0.04% (3)
vars: # - 0.04% (3)
gather_facts: false - 0.04% (3)
nick@mbp: ~/virtualenvs$ - 0.04% (3)
python virtualenv - 0.04% (3)
region we - 0.04% (3)
option to - 0.04% (3)
- public - 0.04% (3)
s3 buckets - 0.04% (3)
the note - 0.04% (3)
file. i - 0.04% (3)
rather than - 0.04% (3)
we are - 0.04% (3)
s3 bucket, - 0.04% (3)
new hosted - 0.04% (3)
tasks in - 0.04% (3)
make our - 0.04% (3)
registrar to - 0.04% (3)
enex export - 0.04% (3)
on december - 0.04% (3)
any of - 0.04% (3)
records for - 0.04% (3)
over the - 0.04% (3)
with python - 0.04% (3)
bucket_name = - 0.04% (3)
region to - 0.04% (3)
aws resources - 0.04% (3)
in default_region - 0.04% (3)
= "us-east-1" - 0.04% (3)
source for - 0.04% (3)
boto3.resource('s3') # - 0.04% (3)
can find - 0.04% (3)
evernote notebook - 0.04% (3)
new s3 - 0.04% (3)
for building - 0.04% (3)
and configure - 0.04% (3)
can also - 0.04% (3)
build rackspace - 0.04% (3)
www.domain.com to - 0.04% (3)
the root - 0.04% (3)
0766e5df-d60a-4100-ae8c-07f27ec0148f # - 0.04% (3)
the other - 0.04% (3)
server in - 0.04% (3)
"{{ flavor - 0.04% (3)
files: "{{ - 0.04% (3)
#key_name: my_rackspace_key - 0.04% (3)
upon creation - 0.04% (3)
key to - 0.04% (3)
- region: - 0.04% (3)
"{{ image - 0.04% (3)
}}" image: - 0.04% (3)
servers with - 0.04% (3)
# wait - 0.04% (3)
recipe for - 0.04% (3)
}}" flavor: - 0.04% (3)
rax credentials: - 0.04% (3)
build request - 0.04% (3)
on work, - 0.04% (3)
success and - 0.04% (3)
name: rackspace - 0.04% (3)
/root/.ssh/authorized_keys: /users/nick/.ssh/id_rsa.pub - 0.04% (3)
files }}" - 0.04% (3)
python, s3, - 0.04% (3)
key's name. - 0.04% (3)
specify that - 0.04% (3)
- private - 0.04% (3)
net) networks: - 0.04% (3)
aka service - 0.04% (3)
network (10. - 0.04% (3)
a private - 0.04% (3)
(public ipv4) - 0.04% (3)
public network - 0.04% (3)
present # - 0.04% (3)
should wait - 0.04% (3)
exist state: - 0.04% (3)
want our - 0.04% (3)
means we - 0.04% (3)
aws using - 0.04% (3)
- present - 0.04% (3)
# state - 0.04% (3)
wait: yes - 0.04% (3)
before proceeding - 0.04% (3)
- files: - 0.04% (3)
key_name - - 0.04% (3)
note: instead - 0.04% (3)
a stored - 0.04% (3)
ssh pub - 0.04% (3)
key automatically - 0.04% (3)
of dropping - 0.04% (3)
rackspace key - 0.04% (3)
password # - 0.04% (3)
ssh in - 0.04% (3)
the location - 0.04% (3)
# when - 0.04% (3)
by editing - 0.04% (3)
file, you - 0.04% (3)
/users/nick/.rackspace_cloud_credentials # - 0.04% (3)
key_name below - 0.04% (3)
file we - 0.04% (3)
created earlier - 0.04% (3)
you build - 0.04% (3)
- credentials: - 0.04% (3)
credentials specifies - 0.04% (3)
route53 response - 0.03% (2)
our dns - 0.03% (2)
is not - 0.03% (2)
= "s3-website-%s.amazonaws.com" - 0.03% (2)
% (default_region) - 0.03% (2)
domain.com and - 0.03% (2)
a unique - 0.03% (2)
slow cooker. - 0.03% (2)
thomas edison, - 0.03% (2)
zone for - 0.03% (2)
edison thomas - 0.03% (2)
domain to - 0.03% (2)
new domain, - 0.03% (2)
have created - 0.03% (2)
the redirect - 0.03% (2)
set the - 0.03% (2)
edison the - 0.03% (2)
to slow - 0.03% (2)
root domain, - 0.03% (2)
demo bucket - 0.03% (2)
the www - 0.03% (2)
aws, we’ll - 0.03% (2)
this to - 0.03% (2)
we would - 0.03% (2)
for domain.com - 0.03% (2)
has been - 0.03% (2)
files to - 0.03% (2)
your registrar - 0.03% (2)
will have - 0.03% (2)
how to - 0.03% (2)
perform the - 0.03% (2)
setting for - 0.03% (2)
converts evernote - 0.03% (2)
pure text - 0.03% (2)
your name - 0.03% (2)
they were - 0.03% (2)
of all - 0.03% (2)
of their - 0.03% (2)
used evernote - 0.03% (2)
i only - 0.03% (2)
text notes. - 0.03% (2)
name server - 0.03% (2)
to get - 0.03% (2)
"s3-website-%s.amazonaws.com" % - 0.03% (2)
'hostedzoneid': s3_hosted_zone_ids[default_region], - 0.03% (2)
most important - 0.03% (2)
a second - 0.03% (2)
'action': 'upsert', - 0.03% (2)
'resourcerecordset': { - 0.03% (2)
'type': 'a', - 0.03% (2)
'aliastarget': { - 0.03% (2)
'evaluatetargethealth': false - 0.03% (2)
on high - 0.03% (2)
route53, we - 0.03% (2)
benefits of - 0.03% (2)
load the - 0.03% (2)
are the - 0.03% (2)
to aws - 0.03% (2)
nameservers at - 0.03% (2)
cook on - 0.03% (2)
to domain.com - 0.03% (2)
website bucket_website - 0.03% (2)
root domain.com - 0.03% (2)
ansible rackspace - 0.03% (2)
mixture. prep - 0.03% (2)
the flour - 0.03% (2)
edge locations - 0.03% (2)
meat with - 0.03% (2)
use my - 0.03% (2)
stir to - 0.03% (2)
a_record - - 0.03% (2)
delivery network - 0.03% (2)
mix together - 0.03% (2)
files that - 0.03% (2)
store the - 0.03% (2)
find the - 0.03% (2)
complete source - 0.03% (2)
python to - 0.03% (2)
dynamic web - 0.03% (2)
your end - 0.03% (2)
critical vulnerability - 0.03% (2)
small bowl, - 0.03% (2)
1/2 teaspoon - 0.03% (2)
seasoned salt - 0.03% (2)
application server. - 0.03% (2)
celery sticks - 0.03% (2)
inch cubes - 0.03% (2)
the ingredients. - 0.03% (2)
an example - 0.03% (2)
a critical - 0.03% (2)
vulnerability in - 0.03% (2)
the end - 0.03% (2)
after some - 0.03% (2)
6 quart - 0.03% (2)
for my - 0.03% (2)
to ensure - 0.03% (2)
for your - 0.03% (2)
that the - 0.03% (2)
s3 resource - 0.03% (2)
6 hours. - 0.03% (2)
configure the - 0.03% (2)
did any - 0.03% (2)
that are - 0.03% (2)
# make - 0.03% (2)
a basic - 0.03% (2)
will not - 0.03% (2)
edison i - 0.03% (2)
do not - 0.03% (2)
bucket and - 0.03% (2)
our bucket - 0.03% (2)
to set - 0.03% (2)
bucket, using - 0.03% (2)
things i - 0.03% (2)
cooker favorite - 0.03% (2)
bay leaf - 0.03% (2)
python sdk - 0.03% (2)
site as - 0.03% (2)
your domain - 0.03% (2)
the broth - 0.03% (2)
to manually - 0.03% (2)
rax_dns - - 0.03% (2)
mix the - 0.03% (2)
aws python - 0.03% (2)
files build - 0.03% (2)
installed, we - 0.03% (2)
will create - 0.03% (2)
1: create - 0.03% (2)
new static - 0.03% (2)
stored in - 0.03% (2)
new bucket - 0.03% (2)
recipe i - 0.03% (2)
in ansible - 0.03% (2)
i could - 0.03% (2)
settings: # - 0.03% (2)
admin@enhancedtest.net # - 0.03% (2)
means i - 0.03% (2)
address for - 0.03% (2)
admin email - 0.03% (2)
dns_email - - 0.03% (2)
host key - 0.03% (2)
domain - - 0.03% (2)
# rackspace - 0.03% (2)
new instance - 0.03% (2)
the ssh - 0.03% (2)
create rackspace - 0.03% (2)
directory for - 0.03% (2)
our ansible - 0.03% (2)
our rackspace - 0.03% (2)
dynamic ansible - 0.03% (2)
virtualenv with - 0.03% (2)
for ansible - 0.03% (2)
for pyrax - 0.03% (2)
working with - 0.03% (2)
we specified - 0.03% (2)
with pyrax - 0.03% (2)
the tasks - 0.03% (2)
already existed - 0.03% (2)
virtualenv for - 0.03% (2)
record was - 0.03% (2)
successfully the - 0.03% (2)
rackspace cloud. - 0.03% (2)
like this: - 0.03% (2)
configuration files - 0.03% (2)
test run - 0.03% (2)
let’s give - 0.03% (2)
it will - 0.03% (2)
virtualenv name - 0.03% (2)
to work - 0.03% (2)
pyrax will - 0.03% (2)
like on - 0.03% (2)
ansible inventory - 0.03% (2)
since we’re - 0.03% (2)
github: ansible-rackspace-servers-example - 0.03% (2)
and troubleshoot - 0.03% (2)
the group - 0.03% (2)
this tasks - 0.03% (2)
ansible group - 0.03% (2)
to have - 0.03% (2)
and ptr - 0.03% (2)
server, let’s - 0.03% (2)
as adding - 0.03% (2)
virtualenv-inventory.yml build-cloud-server.yml - 0.03% (2)
14.10 pvhvm - 0.03% (2)
ansible-playbook -i - 0.03% (2)
dynamic inventory - 0.03% (2)
what happens! - 0.03% (2)
and see - 0.03% (2)
run our - 0.03% (2)
can work - 0.03% (2)
by default - 0.03% (2)
when adding - 0.03% (2)
for ubuntu - 0.03% (2)
system python - 0.03% (2)
inventory file: - 0.03% (2)
installed in - 0.03% (2)
ansible-rackspace-servers directory - 0.03% (2)
file: virtualenv-inventory.yml - 0.03% (2)
reverse dns - 0.03% (2)
new dns - 0.03% (2)
created the - 0.03% (2)
ansible virtualenv - 0.03% (2)
piece here - 0.03% (2)
uuid is - 0.03% (2)
where we - 0.03% (2)
ansible will - 0.03% (2)
let’s add - 0.03% (2)
a simple - 0.03% (2)
exist in - 0.03% (2)
not yet - 0.03% (2)
of vars - 0.03% (2)
this image - 0.03% (2)
changes were - 0.03% (2)
servers example - 0.03% (2)
- admin - 0.03% (2)
is that - 0.03% (2)
preserving the - 0.03% (2)
playbook with - 0.03% (2)
role in - 0.03% (2)
on all - 0.03% (2)
other tasks - 0.03% (2)
to perform - 0.03% (2)
expand our - 0.03% (2)
new role - 0.03% (2)
to new - 0.03% (2)
- packages - 0.03% (2)
screen tags: - 0.03% (2)
with_items: - - 0.03% (2)
install apt - 0.03% (2)
apt: update_cache=yes - 0.03% (2)
name: run - 0.03% (2)
playbook, but - 0.03% (2)
playbook, we - 0.03% (2)
notebooks to - 0.03% (2)
title in - 0.03% (2)
packages here’s - 0.03% (2)
# dns_email - 0.03% (2)
text files. - 0.03% (2)
domain we - 0.03% (2)
# domain - 0.03% (2)
dns settings: - 0.03% (2)
our playbook: - 0.03% (2)
version of - 0.03% (2)
final version - 0.03% (2)
notes and - 0.03% (2)
evernote notes - 0.03% (2)
and notebooks - 0.03% (2)
to plain - 0.03% (2)
exporting evernote - 0.03% (2)
role we - 0.03% (2)
specified in - 0.03% (2)
run on - 0.03% (2)
export to - 0.03% (2)
the file - 0.03% (2)
server now - 0.03% (2)
packages that - 0.03% (2)
2016author nicholas - 0.03% (2)
virtualenv ansible - 0.03% (2)
servers and - 0.03% (2)
using ansible - 0.03% (2)
the future. - 0.03% (2)
set of - 0.03% (2)
other playbooks - 0.03% (2)
cloud servers. - 0.03% (2)
update_cache=yes - - 0.03% (2)
and then - 0.03% (2)
write an - 0.03% (2)
and installing - 0.03% (2)
the complete - 0.03% (2)
let’s go - 0.03% (2)
system administrator - 0.03% (2)
this ansible - 0.03% (2)
update apt: - 0.03% (2)
pkg={{ item - 0.03% (2)
new “base” - 0.03% (2)
lives in - 0.03% (2)
directory structure - 0.03% (2)
markdown for - 0.03% (2)
task in - 0.03% (2)
package installation - 0.03% (2)
of these - 0.03% (2)
“base” role, - 0.03% (2)
directory named - 0.03% (2)
the directory - 0.03% (2)
- screen - 0.03% (2)
will live - 0.03% (2)
a directory - 0.03% (2)
notebooks i - 0.03% (2)
but it - 0.03% (2)
clicking on - 0.03% (2)
the option - 0.03% (2)
file in - 0.03% (2)
tags: - - 0.03% (2)
kuechler - 0.03% (2)
rackspace cloud server - 0.37% (26)
create a new - 0.24% (17)
to create a - 0.23% (16)
new rackspace cloud - 0.17% (12)
"{{ credentials }}" - 0.17% (12)
credentials: "{{ credentials - 0.17% (12)
}}" name: "{{ - 0.17% (12)
local_action: module: rax - 0.17% (12)
we need to - 0.17% (12)
"{{ item.rax_accessipv4 }}" - 0.16% (11)
the rackspace cloud - 0.16% (11)
static web site - 0.16% (11)
rackspace cloud dns - 0.16% (11)
new cloud server - 0.16% (11)
rackspace cloud servers - 0.16% (11)
the new server - 0.14% (10)
plain text files - 0.13% (9)
"{{ name }}" - 0.13% (9)
- name: dns - 0.13% (9)
name: dns - - 0.13% (9)
name: "{{ name - 0.13% (9)
local_action: module: rax_dns - 0.13% (9)
a static web - 0.11% (8)
for the new - 0.11% (8)
quart slow cooker - 0.11% (8)
now that we - 0.1% (7)
a rackspace cloud - 0.1% (7)
request local_action: module: - 0.09% (6)
to add to - 0.09% (6)
rax_dns_record credentials: "{{ - 0.09% (6)
item.rax_accessipv4 }}" type: - 0.09% (6)
"{{ region }}" - 0.09% (6)
}}" data: "{{ - 0.09% (6)
add to the - 0.09% (6)
}}" region: "{{ - 0.09% (6)
need to create - 0.09% (6)
local_action: module: rax_dns_record - 0.09% (6)
region: "{{ region - 0.09% (6)
"{{ domain }}" - 0.09% (6)
credentials }}" name: - 0.09% (6)
we want to - 0.09% (6)
record local_action: module: - 0.09% (6)
our favorite packages - 0.09% (6)
3 quart slow - 0.09% (6)
with_items: rax.instances register: - 0.09% (6)
module: rax_dns_record credentials: - 0.09% (6)
data: "{{ item.rax_accessipv4 - 0.09% (6)
dns - create - 0.09% (6)
pyrax and ansible - 0.09% (6)
that we have - 0.09% (6)
our domain name - 0.09% (6)
cloud server to - 0.09% (6)
i like to - 0.09% (6)
group local_action: module: - 0.07% (5)
off of evernote - 0.07% (5)
role to install - 0.07% (5)
deploy with_items: rax.instances - 0.07% (5)
ansible_ssh_user: root groupname: - 0.07% (5)
item.name }}" ansible_ssh_host: - 0.07% (5)
add_host hostname: "{{ - 0.07% (5)
new server - - 0.07% (5)
task to create - 0.07% (5)
groupname: deploy with_items: - 0.07% (5)
host group local_action: - 0.07% (5)
name: add new - 0.07% (5)
a new rackspace - 0.07% (5)
root groupname: deploy - 0.07% (5)
"{{ item.name }}" - 0.07% (5)
ansible_ssh_host: "{{ item.rax_accessipv4 - 0.07% (5)
}}" ansible_ssh_user: root - 0.07% (5)
module: add_host hostname: - 0.07% (5)
beef stew recipe - 0.07% (5)
- name: add - 0.07% (5)
to host group - 0.07% (5)
local_action: module: add_host - 0.07% (5)
hostname: "{{ item.name - 0.07% (5)
}}" ansible_ssh_host: "{{ - 0.07% (5)
item.rax_accessipv4 }}" ansible_ssh_user: - 0.07% (5)
install our favorite - 0.06% (4)
at amazon aws - 0.06% (4)
with rackspace cloud - 0.06% (4)
run the playbook - 0.06% (4)
dropbox with plain - 0.06% (4)
for our server - 0.06% (4)
with_items: rax.instances - - 0.06% (4)
--- - name: - 0.06% (4)
make a new - 0.06% (4)
tasks: - name: - 0.06% (4)
a new file - 0.06% (4)
you can use - 0.06% (4)
a list of - 0.06% (4)
the name we - 0.06% (4)
to the new - 0.06% (4)
that we want - 0.06% (4)
specifies that we - 0.06% (4)
ever2text: migrating off - 0.06% (4)
to build our - 0.06% (4)
of evernote to - 0.06% (4)
a static website - 0.06% (4)
ansible playbook to - 0.06% (4)
ansible in a - 0.06% (4)
static web sites - 0.06% (4)
boto3 module import - 0.06% (4)
site at amazon - 0.06% (4)
to dropbox with - 0.06% (4)
can use a - 0.06% (4)
rax.instances - name: - 0.06% (4)
module import boto3 - 0.06% (4)
import boto3 # - 0.06% (4)
the newly created - 0.06% (4)
our s3 bucket - 0.06% (4)
migrating off of - 0.06% (4)
to point to - 0.06% (4)
to create the - 0.06% (4)
with plain text - 0.06% (4)
evernote to dropbox - 0.06% (4)
aws boto3 module - 0.06% (4)
key_name below to - 0.04% (3)
server by editing - 0.04% (3)
you build the - 0.04% (3)
key # when - 0.04% (3)
automatically when i - 0.04% (3)
a stored rackspace - 0.04% (3)
# so that - 0.04% (3)
specifies metadata to - 0.04% (3)
create the server - 0.04% (3)
a server group - 0.04% (3)
in a file, - 0.04% (3)
your key's name. - 0.04% (3)
instead of dropping - 0.04% (3)
password # note: - 0.04% (3)
in without a - 0.04% (3)
i can ssh - 0.04% (3)
new server with - 0.04% (3)
server build request - 0.04% (3)
- files: /root/.ssh/authorized_keys: - 0.04% (3)
upon creation #key_name: - 0.04% (3)
means we want - 0.04% (3)
state - present - 0.04% (3)
wait: yes # - 0.04% (3)
created before proceeding - 0.04% (3)
server is fully - 0.04% (3)
(10. aka service - 0.04% (3)
wait until the - 0.04% (3)
that we should - 0.04% (3)
wait - specifies - 0.04% (3)
files }}" # - 0.04% (3)
my_rackspace_key files: "{{ - 0.04% (3)
to the server - 0.04% (3)
# group - - 0.04% (3)
key to add - 0.04% (3)
key_name - specifies - 0.04% (3)
net) networks: - - 0.04% (3)
region }}" # - 0.04% (3)
image: "{{ image - 0.04% (3)
"{{ flavor }}" - 0.04% (3)
name }}" flavor: - 0.04% (3)
private - public - 0.04% (3)
drop in my - 0.04% (3)
name: rackspace cloud - 0.04% (3)
/users/nick/.ssh/id_rsa.pub tasks: - - 0.04% (3)
ssh pub key - 0.04% (3)
dfw # credentials - 0.04% (3)
#group: deploy # - 0.04% (3)
a comment on - 0.04% (3)
server side of - 0.04% (3)
flavor specifies the - 0.04% (3)
admin.enhancedtest.net # the - 0.04% (3)
server - name: - 0.04% (3)
of our new - 0.04% (3)
be the hostname - 0.04% (3)
this will also - 0.04% (3)
stew recipe for - 0.04% (3)
panel, and # - 0.04% (3)
the slow cooker - 0.04% (3)
rackspace cloud control - 0.04% (3)
flavor: performance1-1 # - 0.04% (3)
see in the - 0.04% (3)
name we will - 0.04% (3)
this is the - 0.04% (3)
for 3 quart - 0.04% (3)
quotes: thomas edison - 0.04% (3)
on work, success - 0.04% (3)
- domain: enhancedtest.net - 0.04% (3)
cloud server and - 0.04% (3)
edison quotes on - 0.04% (3)
work. – thomas edison - 0.04% (3)
our instance - - 0.04% (3)
}}" type: ptr - 0.04% (3)
credentials: /users/nick/.rackspace_cloud_credentials # - 0.04% (3)
create a record - 0.04% (3)
created earlier - - 0.04% (3)
configuration file we - 0.04% (3)
of our pyrax - 0.04% (3)
specifies the location - 0.04% (3)
register is an - 0.04% (3)
in - region: - 0.04% (3)
build our server - 0.04% (3)
ansible term to - 0.04% (3)
save the output - 0.04% (3)
variable named rax - 0.04% (3)
}}" domain: "{{ - 0.04% (3)
the image specifies - 0.04% (3)
rackspace cloud region - 0.04% (3)
domain }}" name: - 0.04% (3)
region is the - 0.04% (3)
}}" type: a - 0.04% (3)
ptr record local_action: - 0.04% (3)
0766e5df-d60a-4100-ae8c-07f27ec0148f # the - 0.04% (3)
server: "{{ item.id - 0.04% (3)
name }}" region: - 0.04% (3)
we will use - 0.04% (3)
the linux distro - 0.04% (3)
our server to - 0.04% (3)
the server # - 0.04% (3)
exist state: present - 0.04% (3)
files: /root/.ssh/authorized_keys: /users/nick/.ssh/id_rsa.pub - 0.04% (3)
roles: - base - 0.04% (3)
build the server - 0.04% (3)
to the list - 0.04% (3)
user: root gather_facts: - 0.04% (3)
install base packages - 0.04% (3)
base role to - 0.04% (3)
we’ve just created - 0.04% (3)
by editing key_name - 0.04% (3)
below to your - 0.04% (3)
key's name. - - 0.04% (3)
build request local_action: - 0.04% (3)
new base role - 0.04% (3)
module: rax credentials: - 0.04% (3)
}}" flavor: "{{ - 0.04% (3)
root gather_facts: true - 0.04% (3)
hosts: deploy user: - 0.04% (3)
run apt update - 0.04% (3)
flavor }}" image: - 0.04% (3)
"{{ image }}" - 0.04% (3)
task to install - 0.04% (3)
a new ansible - 0.04% (3)
of base packages - 0.04% (3)
list of packages - 0.04% (3)
# when you - 0.04% (3)
stored rackspace key - 0.04% (3)
to install a - 0.04% (3)
of dropping in - 0.04% (3)
pub key automatically - 0.04% (3)
in my ssh - 0.04% (3)
so that i - 0.04% (3)
can ssh in - 0.04% (3)
without a password - 0.04% (3)
like to drop - 0.04% (3)
# note: instead - 0.04% (3)
/users/nick/.rackspace_cloud_credentials # i - 0.04% (3)
earlier - credentials: - 0.04% (3)
file we created - 0.04% (3)
a file, you - 0.04% (3)
to install packages - 0.04% (3)
our pyrax configuration - 0.04% (3)
the location of - 0.04% (3)
# credentials specifies - 0.04% (3)
- region: dfw - 0.04% (3)
our server in - 0.04% (3)
want to build - 0.04% (3)
cloud region we - 0.04% (3)
is the rackspace - 0.04% (3)
# the region - 0.04% (3)
- image: 0766e5df-d60a-4100-ae8c-07f27ec0148f - 0.04% (3)
on our new - 0.04% (3)
}}" # key_name - 0.04% (3)
- specifies the - 0.04% (3)
# specify that - 0.04% (3)
with a server - 0.04% (3)
state: present # - 0.04% (3)
specify that we - 0.04% (3)
want both a - 0.04% (3)
rax register: rax - 0.04% (3)
a variable named - 0.04% (3)
output in to - 0.04% (3)
to save the - 0.04% (3)
an ansible term - 0.04% (3)
# register is - 0.04% (3)
group #group: deploy - 0.04% (3)
public network (public - 0.04% (3)
we want our - 0.04% (3)
- specifies metadata - 0.04% (3)
public # group - 0.04% (3)
- private - - 0.04% (3)
service net) networks: - 0.04% (3)
network (10. aka - 0.04% (3)
# a private - 0.04% (3)
(public ipv4) and - 0.04% (3)
ipv4) and # - 0.04% (3)
a public network - 0.04% (3)
when i create - 0.04% (3)
we want both - 0.04% (3)
server to exist - 0.04% (3)
- present means - 0.04% (3)
a new task - 0.04% (3)
credentials }}" domain: - 0.04% (3)
was added successfully - 0.04% (3)
ptr with_items: rax.instances - 0.04% (3)
rax.instances register: ptr_record - 0.04% (3)
item.id }}" name: - 0.04% (3)
}}" server: "{{ - 0.04% (3)
rackspace cloud key - 0.04% (3)
create ptr record - 0.04% (3)
a with_items: rax.instances - 0.04% (3)
the server upon - 0.04% (3)
creation #key_name: my_rackspace_key - 0.04% (3)
- create a - 0.04% (3)
yes # state - 0.04% (3)
}}" register: rax_dns - 0.04% (3)
email: "{{ dns_email - 0.04% (3)
rax_dns credentials: "{{ - 0.04% (3)
- domain create - 0.04% (3)
files: "{{ files - 0.04% (3)
}}" # wait - 0.04% (3)
- specifies that - 0.04% (3)
we should wait - 0.04% (3)
until the server - 0.04% (3)
is fully created - 0.04% (3)
before proceeding wait: - 0.04% (3)
a private network - 0.04% (3)
thomas edison quotes - 0.04% (3)
type: ptr with_items: - 0.04% (3)
to drop in - 0.04% (3)
a password # - 0.04% (3)
ssh in without - 0.04% (3)
that i can - 0.04% (3)
server # so - 0.04% (3)
i create the - 0.04% (3)
key automatically when - 0.04% (3)
my ssh pub - 0.04% (3)
- credentials: /users/nick/.rackspace_cloud_credentials - 0.04% (3)
dropping in a - 0.04% (3)
we created earlier - 0.04% (3)
pyrax configuration file - 0.04% (3)
location of our - 0.04% (3)
# specify the - 0.04% (3)
credentials specifies the - 0.04% (3)
region: dfw # - 0.04% (3)
server in - - 0.04% (3)
region we want - 0.04% (3)
note: instead of - 0.04% (3)
file, you can - 0.04% (3)
image: 0766e5df-d60a-4100-ae8c-07f27ec0148f # - 0.04% (3)
flavor: "{{ flavor - 0.04% (3)
#key_name: my_rackspace_key files: - 0.04% (3)
server upon creation - 0.04% (3)
cloud key to - 0.04% (3)
specifies the rackspace - 0.04% (3)
# key_name - - 0.04% (3)
image }}" region: - 0.04% (3)
}}" image: "{{ - 0.04% (3)
rax credentials: "{{ - 0.04% (3)
use a stored - 0.04% (3)
cloud server build - 0.04% (3)
- name: rackspace - 0.04% (3)
/root/.ssh/authorized_keys: /users/nick/.ssh/id_rsa.pub tasks: - 0.04% (3)
name. - files: - 0.04% (3)
to your key's - 0.04% (3)
editing key_name below - 0.04% (3)
the server by - 0.04% (3)
when you build - 0.04% (3)
the region is - 0.04% (3)
region to create - 0.04% (3)
should wait until - 0.04% (3)
for our new - 0.04% (3)
root connection: local - 0.04% (3)
hosts: localhost user: - 0.04% (3)
name: create a - 0.04% (3)
to use the - 0.04% (3)
default_region = "us-east-1" - 0.04% (3)
to redirect to - 0.04% (3)
need to specify - 0.04% (3)
new hosted zone - 0.04% (3)
gather_facts: false vars: - 0.04% (3)
ansible roles will - 0.04% (3)
for use with - 0.04% (3)
the output from - 0.04% (3)
# create the - 0.04% (3)
all of my - 0.04% (3)
favorite packages on - 0.04% (3)
a new python - 0.04% (3)
with ansible in - 0.04% (3)
aws resources in - 0.04% (3)
specify the region - 0.04% (3)
the aws resources - 0.04% (3)
the flavor specifies - 0.04% (3)
in default_region = - 0.04% (3)
use for our - 0.04% (3)
distro we will - 0.04% (3)
specifies the linux - 0.04% (3)
# the image - 0.04% (3)
- flavor: performance1-1 - 0.04% (3)
of our instance - 0.04% (3)
the server side - 0.04% (3)
name: admin.enhancedtest.net # - 0.04% (3)
# this is - 0.04% (3)
hostname of our - 0.04% (3)
also be the - 0.04% (3)
= boto3.resource('s3') # - 0.04% (3)
s3 bucket a - 0.04% (3)
# this will - 0.04% (3)
region }}" data: - 0.04% (3)
control panel, and - 0.04% (3)
will see in - 0.04% (3)
"{{ files }}" - 0.04% (3)
rackspace key # - 0.04% (3)
the server is - 0.04% (3)
fully created before - 0.04% (3)
python, s3, and - 0.04% (3)
newly created cloud - 0.04% (3)
a record local_action: - 0.04% (3)
domain: "{{ domain - 0.04% (3)
amazon aws using - 0.04% (3)
static website at - 0.04% (3)
name }}" data: - 0.04% (3)
type: a with_items: - 0.04% (3)
rax.instances register: a_record - 0.04% (3)
the domain name - 0.04% (3)
success and inventing - 0.04% (3)
the list of - 0.04% (3)
let’s make a - 0.04% (3)
task to add - 0.04% (3)
new task to - 0.04% (3)
domain create request - 0.04% (3)
domain }}" email: - 0.04% (3)
"{{ dns_email }}" - 0.04% (3)
edison on work, - 0.04% (3)
the top of - 0.04% (3)
favorite quotes: thomas - 0.04% (3)
recipe for 3 - 0.04% (3)
- create ptr - 0.04% (3)
credentials }}" server: - 0.04% (3)
cloud servers with - 0.04% (3)
"{{ item.id }}" - 0.04% (3)
using python, s3, - 0.04% (3)
be using for - 0.04% (3)
you can find - 0.04% (3)
created a new - 0.04% (3)
group - specifies - 0.04% (3)
- public # - 0.04% (3)
server with a - 0.04% (3)
networks: - private - 0.04% (3)
aka service net) - 0.04% (3)
server group #group: - 0.04% (3)
deploy # register - 0.04% (3)
private network (10. - 0.04% (3)
is an ansible - 0.04% (3)
term to save - 0.04% (3)
the output in - 0.04% (3)
network (public ipv4) - 0.04% (3)
present means we - 0.04% (3)
to a variable - 0.04% (3)
named rax register: - 0.04% (3)
both a public - 0.04% (3)
present # specify - 0.04% (3)
want our server - 0.04% (3)
proceeding wait: yes - 0.04% (3)
# state - - 0.04% (3)
to exist state: - 0.04% (3)
metadata to add - 0.04% (3)
s3 bucket for - 0.04% (3)
to create new - 0.04% (3)
when creating a - 0.04% (3)
= "s3-website-%s.amazonaws.com" % - 0.03% (2)
redirect to domain.com - 0.03% (2)
route53 response = - 0.03% (2)
"s3-website-%s.amazonaws.com" % (default_region) - 0.03% (2)
'action': 'upsert', 'resourcerecordset': - 0.03% (2)
create the new - 0.03% (2)
'type': 'a', 'aliastarget': - 0.03% (2)
{ 'hostedzoneid': s3_hosted_zone_ids[default_region], - 0.03% (2)
our s3 buckets - 0.03% (2)
our new static - 0.03% (2)
false } } - 0.03% (2)
to pure text - 0.03% (2)
evernote enex export - 0.03% (2)
to plain text - 0.03% (2)
notes and notebooks - 0.03% (2)
plain text files. - 0.03% (2)
thomas edison thomas - 0.03% (2)
thomas edison i - 0.03% (2)
text notes. i - 0.03% (2)
2016author nicholas kuechlercategories - 0.03% (2)
'upsert', 'resourcerecordset': { - 0.03% (2)
your name server - 0.03% (2)
and route53 ever2text: - 0.03% (2)
to add an - 0.03% (2)
files build rackspace - 0.03% (2)
first, we need - 0.03% (2)
slow cooker favorite - 0.03% (2)
'hostedzoneid': s3_hosted_zone_ids[default_region], 'dnsname': - 0.03% (2)
'a', 'aliastarget': { - 0.03% (2)
name we want - 0.03% (2)
# create s3 - 0.03% (2)
load the aws - 0.03% (2)
add new instance - 0.03% (2)
things i use - 0.03% (2)
a virtualenv beef - 0.03% (2)
load aws boto3 - 0.03% (2)
"us-east-1" # create - 0.03% (2)
register: rax - - 0.03% (2)
benefits of static - 0.03% (2)
a_record - name: - 0.03% (2)
option to export - 0.03% (2)
web sites are - 0.03% (2)
critical vulnerability in - 0.03% (2)
to the end - 0.03% (2)
for the user - 0.03% (2)
aws python sdk - 0.03% (2)
we will create - 0.03% (2)
s3 resource s3 - 0.03% (2)
stew recipe i - 0.03% (2)
www.domain.com to point - 0.03% (2)
register: rax_dns - - 0.03% (2)
dns records for - 0.03% (2)
will create a - 0.03% (2)
we have created - 0.03% (2)
the root domain, - 0.03% (2)
virtualenv beef stew - 0.03% (2)
resource s3 = - 0.03% (2)
2014author nicholas kuechlercategories - 0.03% (2)
demo bucket name - 0.03% (2)
to slow cooker - 0.03% (2)
a small bowl, - 0.03% (2)
1 inch cubes - 0.03% (2)
to the root - 0.03% (2)
cut in to - 0.03% (2)
6 quart slow - 0.03% (2)
make our new - 0.03% (2)
a new cloud - 0.03% (2)
preserving the note - 0.03% (2)
such as adding - 0.03% (2)
our playbook: - - 0.03% (2)
add the new - 0.03% (2)
for building a - 0.03% (2)
create rackspace cloud - 0.03% (2)
use ansible to - 0.03% (2)
all of these - 0.03% (2)
we can do - 0.03% (2)
set of base - 0.03% (2)
creating a new - 0.03% (2)
for ubuntu 14.10 - 0.03% (2)
playbook, we need - 0.03% (2)
see what happens! - 0.03% (2)
let’s run our - 0.03% (2)
can work with - 0.03% (2)
instance to host - 0.03% (2)
14.10 pvhvm - - 0.03% (2)
is for ubuntu - 0.03% (2)
this image uuid - 0.03% (2)
server # note: - 0.03% (2)
pvhvm - image: - 0.03% (2)
image uuid is - 0.03% (2)
specified in the - 0.03% (2)
admin email address - 0.03% (2)
create new rackspace - 0.03% (2)
here’s what the - 0.03% (2)
new server, and - 0.03% (2)
# rackspace cloud - 0.03% (2)
dns settings: # - 0.03% (2)
domain - the - 0.03% (2)
domain we will - 0.03% (2)
# dns_email - - 0.03% (2)
created the new - 0.03% (2)
# note: this - 0.03% (2)
domain name - - 0.03% (2)
dns_email: admin@enhancedtest.net # - 0.03% (2)
a new variable - 0.03% (2)
exist in rackspace - 0.03% (2)
does not yet - 0.03% (2)
yet exist in - 0.03% (2)
top of the - 0.03% (2)
vars at the - 0.03% (2)
rackspace cloud dns. - 0.03% (2)
register: a_record - - 0.03% (2)
the new dns - 0.03% (2)
title in the - 0.03% (2)
use with rackspace - 0.03% (2)
server hosts: deploy - 0.03% (2)
configuration files for - 0.03% (2)
true roles: - - 0.03% (2)
let’s go ahead - 0.03% (2)
to the virtualenv - 0.03% (2)
install ansible in - 0.03% (2)
to install the - 0.03% (2)
we can work - 0.03% (2)
python virtualenv for - 0.03% (2)
configuration file for - 0.03% (2)
with pyrax and - 0.03% (2)
example on my - 0.03% (2)
for this ansible - 0.03% (2)
the complete source - 0.03% (2)
the new server. - 0.03% (2)
the new server, - 0.03% (2)
dns entries for - 0.03% (2)
rackspace cloud servers. - 0.03% (2)
text files build - 0.03% (2)
to new cloud - 0.03% (2)
to have a - 0.03% (2)
successfully the new - 0.03% (2)
pkg={{ item }} - 0.03% (2)
added successfully the - 0.03% (2)
and ptr record - 0.03% (2)
new ansible role - 0.03% (2)
in the future. - 0.03% (2)
and install a - 0.03% (2)
name: install packages - 0.03% (2)
inventory file: virtualenv-inventory.yml - 0.03% (2)
virtualenv inventory file: - 0.03% (2)
apt: update_cache=yes - - 0.03% (2)
with_items: - vim - 0.03% (2)
to create rackspace - 0.03% (2)
screen tags: - - 0.03% (2)
since we’re using - 0.03% (2)
when adding the - 0.03% (2)
server to an - 0.03% (2)
use a dynamic - 0.03% (2)
directory for our - 0.03% (2)
our favorite packages. - 0.03% (2)
in the playbook, - 0.03% (2)
write an ansible - 0.03% (2)
a record for - 0.03% (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.