{"id":2509,"date":"2023-02-27T19:28:26","date_gmt":"2023-02-27T19:28:26","guid":{"rendered":"https:\/\/blog.samarthya.me\/wps\/?p=2509"},"modified":"2023-02-28T17:36:30","modified_gmt":"2023-02-28T17:36:30","slug":"venv-ansible","status":"publish","type":"post","link":"https:\/\/blog.samarthya.me\/wps\/2023\/02\/27\/venv-ansible\/","title":{"rendered":"VENV: Ansible"},"content":{"rendered":"\n
\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

Ansible and Molecule are popular tools for configuration management and testing in the world of DevOps. To avoid conflicts between different projects and their dependencies, it is recommended to use a virtual environment for each project. In this blog post, we’ll show you how to set up and use a virtual environment using Python’s built-in venv<\/code> module on macOS<\/code> and CentOS 7<\/code>.<\/p>\n\n\n\n

Pre-requisites<\/h2>\n\n\n\n

Before we begin, you’ll need the following:<\/p>\n\n\n\n

    \n
  • Python 3 installed on your system<\/li>\n\n\n\n
  • pip<\/code> installed on your system<\/li>\n\n\n\n
  • Basic knowledge of the command line interface<\/li>\n<\/ul>\n\n\n\n

    On Centos7<\/h2>\n\n\n\n
      \n
    1. Open a terminal window and create a directory for your project:\n
        \n
      • mkdir my-ansible-project <\/code><\/li>\n\n\n\n
      • cd my-ansible-project<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
      • Install the python3-venv<\/code> package:\n
          \n
        • sudo yum install python3-venv<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
        • Create a new virtual environment:\n
            \n
          • python3 -m venv venv <\/code>\n
              \n
            • This will create a new directory named venv<\/code> in your project directory, which contains the virtual environment.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n
            • Activate the virtual environment:\n
                \n
              • source venv\/bin\/activate<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
              • Install Ansible and Molecule:\n
                  \n
                • pip install ansible molecule<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
                • Verify that Ansible and Molecule are installed:\n
                    \n
                  • ansible --version <\/code><\/li>\n\n\n\n
                  • molecule --version <\/code>\n
                      \n
                    • This should display the version of Ansible and Molecule installed in the virtual environment.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                    • When you’re done working with Ansible and Molecule, you can deactivate the virtual environment:\n
                        \n
                      • deactivate<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

                        On OSX<\/h2>\n\n\n\n
                          \n
                        1. Open a terminal window and create a directory for your project:\n
                            \n
                          • mkdir my-ansible-project <\/code><\/li>\n\n\n\n
                          • cd my-ansible-project<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
                          • Create a new virtual environment:\n
                              \n
                            • python3 -m venv venv <\/code>\n
                                \n
                              • This will create a new directory named venv<\/code> in your project directory, which contains the virtual environment.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                              • Activate the virtual environment:\n
                                  \n
                                • source venv\/bin\/activate<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                • Install Ansible and Molecule:\n
                                    \n
                                  • pip install ansible molecule<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                  • Verify that Ansible and Molecule are installed:\n
                                      \n
                                    • ansible --version <\/code><\/li>\n\n\n\n
                                    • molecule --version <\/code>\n
                                        \n
                                      • This should display the version of Ansible and Molecule installed in the virtual environment.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                                      • When you’re done working with Ansible and Molecule, you can deactivate the virtual environment:\n
                                          \n
                                        • deactivate<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

                                          Using the Virtual Environment<\/h2>\n\n\n\n

                                          To use Ansible and Molecule inside the virtual environment, you need to activate the environment first. <\/p>\n\n\n\n

                                          This is done with the source<\/code> command:<\/p>\n\n\n\n

                                          source venv\/bin\/activate\n<\/code><\/code><\/pre>\n\n\n\n
                                          Once the virtual environment is activated, you can use Ansible and Molecule as you normally would. When you’re done, you can deactivate the virtual environment with the deactivate<\/code> command:<\/p>\n\n\n\n
                                          deactivate\n<\/code><\/code><\/pre>\n\n\n\n
                                          Conclusion<\/h2>\n\n\n\n
                                          In this blog post, we showed you how to set up and use a virtual environment using Python’s built-in venv<\/code> module on macOS and CentOS 7 for Ansible and Molecule. Using a virtual environment helps keep your projects isolated and avoids conflicts between different dependencies.<\/p>\n","protected":false},"excerpt":{"rendered":"
                                          Ansible and Molecule are popular tools for configuration management and testing in the world of DevOps. To avoid conflicts between different projects and their dependencies, it is recommended to use a virtual environment for each project. In this blog post, we’ll show you how to set up and use a virtual environment using Python’s built-in […]<\/p>\n","protected":false},"author":2,"featured_media":2510,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[34],"tags":[278,270,290],"class_list":["post-2509","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technical","tag-ansible","tag-python","tag-venv"],"_links":{"self":[{"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/posts\/2509","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/comments?post=2509"}],"version-history":[{"count":2,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/posts\/2509\/revisions"}],"predecessor-version":[{"id":2512,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/posts\/2509\/revisions\/2512"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/media\/2510"}],"wp:attachment":[{"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/media?parent=2509"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/categories?post=2509"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/tags?post=2509"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}