{"id":71410,"date":"2023-02-21T09:01:11","date_gmt":"2023-02-21T09:01:11","guid":{"rendered":"https:\/\/www.cryptocabaret.com\/?p=71410"},"modified":"2023-02-21T09:01:11","modified_gmt":"2023-02-21T09:01:11","slug":"automate-openstack-using-ansible","status":"publish","type":"post","link":"https:\/\/www.cryptocabaret.com\/?p=71410","title":{"rendered":"Automate OpenStack using Ansible"},"content":{"rendered":"

Automate OpenStack using Ansible<\/span>
\najscanlas<\/a><\/span>
\nTue, 02\/21\/2023 – 03:00<\/span><\/p>\n

\n

I demonstrated how I manage OpenStack using Terraform in my previous article<\/a>. Using Terraform as Infrastructure as Code (IaC) is a significant advantage, but it also requires the staff to support it. Sometimes, all you really need is the ability to provision infrastructure as timed resources, with no intention of building lasting data structures. When I design a flexible environment, I prefer the declarative language of Ansible.<\/p>\n

Ansible’s flexibility allows me to design for use cases that include:<\/p>\n

    \n
  1. A test environment that’s timed and can be deleted after use.<\/li>\n
  2. A training environment provided for a specific amount of time and then destroyed.<\/li>\n
  3. Moving from a manual to an automated infrastructure when Terraform is difficult because it maps your existing infrastructure.<\/li>\n<\/ol>\n

    Install Ansible and OpenStack SDK<\/h2>\n

    First, you need to install Ansible and its SDK. For this, you must have Docker or Podman<\/a> installed.<\/p>\n

    I use the pip<\/a> installation of Ansible:<\/p>\n

    \n$ python3 -m pip install ansible-navigator --user<\/code><\/pre>\n
    The ansible-navigator<\/code> command gets used by AWX or Red Hat Ansible Automation Platform to run Ansible playbooks. Unlike the previous ansible-playbook<\/code> or ansible<\/code> ad-hoc commands, this creates a container and execution environment.<\/p>\n
    You must build your execution environment with an OpenStack SDK. For this, I strongly recommend the article by Gineesh Madapparambath on how to create an execution environment<\/a>.<\/p>\n
    After creation, use your Ansible execution environment to configure your image:<\/p>\n
    \n$ ansible-navigator images<\/code><\/pre>\n
    Choose which image to use and run a playbook:<\/p>\n
    \n$ ansible-navigator run main.yaml --stdout<\/code><\/pre>\n<\/p>\n
    \n
    More on Ansible<\/div>\n
    \n
    5 reasons to migrate to Red Hat Ansible Automation Platform 2<\/a><\/div>\n
    A quickstart guide to Ansible<\/a><\/div>\n
    Ansible cheat sheet<\/a><\/div>\n
    Free online course: Ansible essentials<\/a><\/div>\n
    Download and install Ansible<\/a><\/div>\n
    eBook: The automated enterprise<\/a><\/div>\n
    eBook: Ansible for DevOps<\/a><\/div>\n
    Free Ansible eBooks<\/a><\/div>\n
    Latest Ansible articles<\/a><\/div>\n<\/p><\/div>\n<\/p><\/div>\n
    Sample playbook<\/h2>\n
    My sample playbook uses the same structure I demonstrated in my Terraform article:<\/p>\n
    \n$ cat >> main.yaml <\/code><\/pre>\n
    Results<\/h2>\n
    After you run the playbook, you get networks:<\/p>\n
    \n
      \"Network<\/div>\n
    Image by: <\/span><\/p>\n
    (AJ Canlas, CC BY-SA 4.0)<\/p>\n<\/div>\n<\/article>\n
    You also get flavors:<\/p>\n
    \n
      \"flavors\"<\/div>\n
    Image by: <\/span><\/p>\n
    (AJ Canlas, CC BY-SA 4.0)<\/p>\n<\/div>\n<\/article>\n
    And images:<\/p>\n
    \n
      \"images\"<\/div>\n
    Image by: <\/span><\/p>\n
    (AJ Canlas, CC BY-SA 4.0)<\/p>\n<\/div>\n<\/article>\n
    And a demo project:<\/p>\n
    \n
      \"projects\"<\/div>\n
    Image by: <\/span><\/p>\n
    (AJ Canlas, CC BY-SA 4.0)<\/p>\n<\/div>\n<\/article>\n
    The right tool<\/h2>\n
    There’s no single right or wrong answer for how you automate. How you implement your automation depends on your organization’s needs, infrastructure, system design, and staff resources. Select one of the great open source tools out there to get started. Put in the effort now, and save yourself a lot of work in the future.<\/p>\n<\/div>\n
    \n
    Ansible offers unique flexibility when automating your infrastructure.<\/p>\n<\/div>\n
    \n
    \n
      \"Looking<\/div>\n
    Image by: <\/span><\/p>\n
    opensource.com<\/p>\n<\/div>\n<\/article>\n<\/div>\n
    \n
    OpenStack<\/a><\/div>\n
    Ansible<\/a><\/div>\n
    Cloud<\/a><\/div>\n
    Automation<\/a><\/div>\n<\/p><\/div>\n
    What to read next<\/div>\n
    \n
    How to use GitOps to automate Terraform<\/a><\/div>\n<\/p><\/div>\n

    \n        \"Creative<\/a>This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.<\/div>\n
    \n
    \n
    Register<\/a> or Login<\/a> to post a comment.<\/div>\n<\/p><\/div>\n<\/section>\n
    Powered by WPeMatico<\/a><\/small><\/p>\n","protected":false},"excerpt":{"rendered":"
    Automate OpenStack using Ansible ajscanlas Tue, 02\/21\/2023 – 03:00 I demonstrated how I manage OpenStack using Terraform in my previous article. Using Terraform as Infrastructure as Code (IaC) is a significant advantage, but it also requires the staff to support it. Sometimes, all you really need is the ability to provision infrastructure as timed resources, […]<\/p>\n","protected":false},"author":1,"featured_media":71411,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[307],"tags":[],"class_list":["post-71410","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-open-source"],"_links":{"self":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts\/71410","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=71410"}],"version-history":[{"count":0,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/posts\/71410\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=\/wp\/v2\/media\/71411"}],"wp:attachment":[{"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=71410"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=71410"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cryptocabaret.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=71410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}