{"id":11905,"date":"2018-10-26T07:02:19","date_gmt":"2018-10-26T05:02:19","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/"},"modified":"2018-10-26T07:02:19","modified_gmt":"2018-10-26T05:02:19","slug":"deploy-dcos-using-ansible-part-2-playbooks","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/","title":{"rendered":"Deploy DC\/OS using Ansible (Part 2) &#8211; Playbooks"},"content":{"rendered":"<p> Finally, after all the configuration stuff is done, we can run the playbooks<\/p>\n<h3>Create SSH Access<\/h3>\n<p>First the SSH Access on all nodes need to be created. Therefore the access-onprem.yml is used:<br \/>\nBe careful, I used CentOS on my system, so I commented the apt-get and the debian-based part out.<br \/>\nIf you want to run the playbook on another operating system, adjust it carefully.<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1;]\">---\n# This playbook enable access to all ansible targets via ssh\n\n- name: setup the ansible requirements on all nodes\n  hosts: all:!localhost\n  #hosts: all\n  serial: 20\n  remote_user: \"{{ initial_remote_user | default('root') }}\"\n  become: true\n  tasks:\n\n#    - name: attempt to update apt's cache\n#      raw: test -e \/usr\/bin\/apt-get &amp;&amp; apt-get update\n#      ignore_errors: yes\n\n#    - name: attempt to install Python on Debian-based systems\n#      raw: test -e \/usr\/bin\/apt-get &amp;&amp; apt-get -y install python-simplejson python\n#      ignore_errors: yes\n\n    - name: attempt to install Python on CentOS-based systems\n      raw: test -e \/usr\/bin\/yum &amp;&amp; yum -y install python-simplejson python\n      ignore_errors: yes\n\n    - name: Create admin user group\n      group:\n        name: admin\n        system: yes\n        state: present\n\n    - name: Ensure sudo is installed\n      package:\n        name: sudo\n        state: present\n\n    - name: Remove user centos\n      user:\n        name: centos\n        state: absent\n        remove: yes\n\n    - name: Create Ansible user\n      user:\n        name: \"{{ lookup('ini', 'remote_user section=defaults file=..\/ansible.cfg') }}\"\n        shell: \/bin\/bash\n        comment: \"Ansible management user\"\n        home: \"\/home\/{{ lookup('ini', 'remote_user section=defaults file=..\/ansible.cfg') }}\"\n        createhome: yes\n        password: \"admin123\"\n\n    - name: Add Ansible user to admin group\n      user:\n        name: \"{{ lookup('ini', 'remote_user section=defaults file=..\/ansible.cfg') }}\"\n        groups: admin\n        append: yes\n\n    - name: Add authorized key\n      authorized_key:\n        user: \"{{ lookup('ini', 'remote_user section=defaults file=..\/ansible.cfg') }}\"\n        state: present\n        key: \"{{ lookup('file', lookup('env','HOME') + '\/.ssh\/ansible-dcos.pub') }}\"\n\n    - name: Copy sudoers file\n      command: cp -f \/etc\/sudoers \/etc\/sudoers.tmp\n\n    - name: Backup sudoers file\n      command: cp -f \/etc\/sudoers \/etc\/sudoers.bak\n\n    - name: Ensure admin group can sudo\n      lineinfile:\n        dest: \/etc\/sudoers.tmp\n        state: present\n        regexp: '^%admin'\n        line: '%admin ALL=(ALL) NOPASSWD: ALL'\n      when: ansible_os_family == 'Debian'\n\n    - name: Ensure admin group can sudo\n      lineinfile:\n        dest: \/etc\/sudoers.tmp\n        state: present\n        regexp: '^%admin'\n        insertafter: '^root'\n        line: '%admin ALL=(ALL) NOPASSWD: ALL'\n      when: ansible_os_family == 'RedHat'\n\n    - name: Replace sudoers file\n      shell: visudo -q -c -f \/etc\/sudoers.tmp &amp;&amp; cp -f \/etc\/sudoers.tmp \/etc\/sudoers\n\n    - name: Test Ansible user's access\n      local_action: \"shell ssh {{ lookup('ini', 'remote_user section=defaults file=..\/ansible.cfg') }}@{{ ansible_host }} 'sudo echo success'\"\n      become: False\n      register: ansible_success\n\n    - name: Remove Ansible SSH key from bootstrap user's authorized keys\n      lineinfile:\n        path: \"{{ ansible_env.HOME }}\/.ssh\/authorized_keys\"\n        state: absent\n        regexp: '^ssh-rsa AAAAB3N'\n      when: ansible_success.stdout == \"success\"\n<\/pre>\n<h4>Start the Playbook for the SSH access<\/h4>\n<pre class=\"brush: shell; gutter: true; first-line: 1;]\">[root@dcos-ansible ansible-dcos]# pwd\n\/root\/ansible-dcos\n\n[root@dcos-ansible ansible-dcos]# ansible-playbook plays\/access-onprem.yml\nPLAY [setup the ansible requirements on all nodes] \n****************************************************************************************\nTASK [Gathering Facts]\n****************************************************************************************\nok: [192.168.22.103]\nok: [192.168.22.102]\nok: [192.168.22.104]\nok: [192.168.22.101]\nok: [192.168.22.100]\n\n[....]\n\nPLAY RECAP \n**************************************************************************************\n192.168.22.100             : ok=14   changed=6    unreachable=0    failed=0\n192.168.22.101             : ok=14   changed=6    unreachable=0    failed=0\n192.168.22.102             : ok=14   changed=6    unreachable=0    failed=0\n192.168.22.103             : ok=14   changed=6    unreachable=0    failed=0\n192.168.22.104             : ok=14   changed=6    unreachable=0    failed=0\n<\/pre>\n<p>This is not the whole output of the playbook. Important to know, during the &#8220;TASK [Test Ansible user&#8217;s access]&#8221; I had to insert the Ansible password 5 times. After that the playbooks finished successfully.<\/p>\n<h4>Ping the servers using Ansible<\/h4>\n<p>After the playbook finished successfully do a test ping<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1;]\">[root@dcos-ansible ansible-dcos]# ansible all -m ping\n192.168.22.102 | SUCCESS =&gt; {\n    \"changed\": false,\n    \"ping\": \"pong\"\n}\n192.168.22.100 | SUCCESS =&gt; {\n    \"changed\": false,\n    \"ping\": \"pong\"\n}\n192.168.22.104 | SUCCESS =&gt; {\n    \"changed\": false,\n    \"ping\": \"pong\"\n}\n192.168.22.101 | SUCCESS =&gt; {\n    \"changed\": false,\n    \"ping\": \"pong\"\n}\n192.168.22.103 | SUCCESS =&gt; {\n    \"changed\": false,\n    \"ping\": \"pong\"\n}\n<\/pre>\n<p>In case of trouble it is really helpful to use the &#8220;-vvv&#8221; option.<br \/>\nIt is also possible to ping only one server using <\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1;]\">ansible 192.168.22.100 -m ping<\/pre>\n<h3>Rollout the DC\/OS installation<\/h3>\n<pre class=\"brush: shell; gutter: true; first-line: 1;]\">[root@dcos-ansible ansible-dcos]# pwd\n\/root\/ansible-dcos\n[root@dcos-ansible ansible-dcos]# cat plays\/install.yml\n---\n- name: setup the system requirements on all nodes\n  hosts: all\n  serial: 20\n  become: true\n  roles:\n    - common\n    - docker\n\n- name: generate the DC\/OS configuration\n  hosts: bootstraps\n  serial: 1\n  become: true\n  roles:\n    - bootstrap\n\n- name: deploy nodes\n  hosts: [ masters, agents, agent_publics]\n  serial: 20\n  become: true\n  roles:\n    - node-install\n\n<\/pre>\n<pre class=\"brush: shell; gutter: true; first-line: 1;]\">[root@dcos-ansible ansible-dcos]# pwd\n\/root\/ansible-dcos\n[root@dcos-ansible ansible-dcos]# ansible-playbook plays\/install.yml\n\nPLAY [setup the system requirements on all nodes]\n*********************************************************************\n\nTASK [Gathering Facts]\n*********************************************************************\nok: [192.168.22.102]\nok: [192.168.22.104]\nok: [192.168.22.101]\nok: [192.168.22.100]\n[....]\n<\/pre>\n<p>In case some installation steps fail, Ansible will skip for that server and gives you the opportunity to rerun the playbook on the failed server.<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1;]\">ansible-playbook plays\/install.yml --limit @\/root\/ansible-dcos\/plays\/install.retry\n<\/pre>\n<p>If you cannot connect to your master via browser: Check your \/var\/log\/messages for error messages. In my case the master searched for the eth0 interface. Which isn&#8217;t available on my VM.<br \/>\nJust change the detect-ip script as follows, according to your network interface. Same step is needed on all agent-nodes as well.<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1;]\">[root@dcos-master bin]# cat \/opt\/mesosphere\/bin\/detect_ip\n#!\/usr\/bin\/env bash\nset -o nounset -o errexit\nexport PATH=\/usr\/sbin:\/usr\/bin:$PATH\necho $(ip addr show enp0s8 | grep -Eo '[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}' | head -1)\n<\/pre>\n<h4>Install the CLI<\/h4>\n<p>For those of you, which prefer a CLI, just install it on your master.<\/p>\n<pre class=\"brush: shell; gutter: true; first-line: 1;]\">[root@dcos-master ~]#  [ -d \/usr\/local\/bin ] || sudo mkdir -p \/usr\/local\/bin\n[root@dcos-master ~]# curl https:\/\/downloads.dcos.io\/binaries\/cli\/linux\/x86-64\/dcos-1.11\/dcos -o dcos\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n100 13.9M  100 13.9M    0     0  1313k      0  0:00:10  0:00:10 --:--:-- 3920k\n[root@dcos-master ~]# sudo mv dcos \/usr\/local\/bin\n[root@dcos-master ~]# chmod +x \/usr\/local\/bin\/dcos\n[root@dcos-master ~]# dcos cluster setup http:\/\/192.168.22.101\nIf your browser didn't open, please go to the following link:\n\n    http:\/\/192.168.22.101\/login?redirect_uri=urn:ietf:wg:oauth:2.0:oob\n\nEnter OpenID Connect ID Token: eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6Ik9UQkVOakZFTWtWQ09VRTRPRVpGTlRNMFJrWXlRa015Tnprd1JrSkVRemRCTWpBM1FqYzVOZyJ9.eyJlbWFpbCI6Imp1bGlhLmd1Z2VsQGdtYWlsLmNvbSIsImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJpc3MiOiJodHRwczovL2Rjb3MuYXV0aDAuY29tLyIsInN1YiI6Imdvb2dsZS1vYXV0aDJ8MTA2NTU2OTI5OTM1NTc2MzQ1OTEyIiwiYXVkIjoiM3lGNVRPU3pkbEk0NVExeHNweHplb0dCZTlmTnhtOW0iLCJpYXQiOjE1NDA0NTA4MTcsImV4cCI6MTU0MDg4MjgxN30.M8d6dT4QNsBmUXbAH8B58K6Q2XvnCKnEd_yziiijBXHdW18P2OnJEYrKa9ewvOfFhyisvLa7XMU3xeBUhoqX5T6mGkQo_XUlxXM82Ohv3zNCdqyNCwPwoniX4vU7R736blcLRx1aB8TJnydNb0H0IzEAVzaYBQ1CRV-4a9KsiMXKBBPlskOSvek4b_FRghA6hsjMA2eO-G5r3B6UgHo6CCwdwVrhsOygvJ5NwDC0xiFrnkW-SjZRZztCN8cRj7b40VH43uY6R2ibxJfE7SaGpbWzLyp7juUJ766WXar3O7ww42bYIqLnAx6YmWG5kFeJnmJGT-Rdmhl2JuvdABoozA\n<\/pre>\n<p>That&#8217;s it, now you can configure and use your DC\/OS. Always keep in mind: the ntpd service is really essential for a working DC\/OS Node. Also use the \/var\/log\/messages, it really helps!<br \/>\nOne little thing I have to mention at the end. Don&#8217;t confide in the official documentation and the troubleshooting guide, it does not help as much as expected&#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Finally, after all the configuration stuff is done, we can run the playbooks Create SSH Access First the SSH Access on all nodes need to be created. Therefore the access-onprem.yml is used: Be careful, I used CentOS on my system, so I commented the apt-get and the debian-based part out. If you want to run&hellip;&nbsp;<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","neve_meta_reading_time":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[4133],"tags":[150,1472],"class_list":["post-11905","post","type-post","status-publish","format-standard","category-database","tag-ansible","tag-dc-os"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.9) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Deploy DC\/OS using Ansible (Part 2) - Playbooks - dbi services Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Deploy DC\/OS using Ansible (Part 2) - Playbooks\" \/>\n<meta property=\"og:description\" content=\"Finally, after all the configuration stuff is done, we can run the playbooks Create SSH Access First the SSH Access on all nodes need to be created. Therefore the access-onprem.yml is used: Be careful, I used CentOS on my system, so I commented the apt-get and the debian-based part out. If you want to run&hellip;&nbsp;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi services Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dbiservices\/\" \/>\n<meta property=\"article:published_time\" content=\"2018-10-26T05:02:19+00:00\" \/>\n<meta name=\"author\" content=\"Open source Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:site\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Open source Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/deploy-dcos-using-ansible-part-2-playbooks\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/deploy-dcos-using-ansible-part-2-playbooks\\\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\"},\"headline\":\"Deploy DC\\\/OS using Ansible (Part 2) &#8211; Playbooks\",\"datePublished\":\"2018-10-26T05:02:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/deploy-dcos-using-ansible-part-2-playbooks\\\/\"},\"wordCount\":319,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"keywords\":[\"Ansible\",\"DC\\\/OS\"],\"articleSection\":[\"Database\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/deploy-dcos-using-ansible-part-2-playbooks\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/deploy-dcos-using-ansible-part-2-playbooks\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/deploy-dcos-using-ansible-part-2-playbooks\\\/\",\"name\":\"Deploy DC\\\/OS using Ansible (Part 2) - Playbooks - dbi services Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2018-10-26T05:02:19+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/deploy-dcos-using-ansible-part-2-playbooks\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/deploy-dcos-using-ansible-part-2-playbooks\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/deploy-dcos-using-ansible-part-2-playbooks\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Deploy DC\\\/OS using Ansible (Part 2) &#8211; Playbooks\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi services Blog\",\"description\":\"#BeSharing\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\",\"name\":\"dbi services\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"width\":512,\"height\":512,\"caption\":\"dbi services\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/dbiservices\\\/\",\"https:\\\/\\\/x.com\\\/dbiservices\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/dbi-services\\\/\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/dbiservices\"],\"description\":\"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.\",\"email\":\"info@dbi-services.com\",\"telephone\":\"+41 32 422 96 00\",\"legalName\":\"dbi services SA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0b4548362cac3eeff8b3eaf329e3530a\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2022\\\/05\\\/open-source-author.png\",\"caption\":\"Open source Team\"},\"description\":\"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/open-source-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Deploy DC\/OS using Ansible (Part 2) - Playbooks - dbi services Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/","og_locale":"en_US","og_type":"article","og_title":"Deploy DC\/OS using Ansible (Part 2) - Playbooks","og_description":"Finally, after all the configuration stuff is done, we can run the playbooks Create SSH Access First the SSH Access on all nodes need to be created. Therefore the access-onprem.yml is used: Be careful, I used CentOS on my system, so I commented the apt-get and the debian-based part out. If you want to run&hellip;&nbsp;","og_url":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/","og_site_name":"dbi services Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2018-10-26T05:02:19+00:00","author":"Open source Team","twitter_card":"summary_large_image","twitter_creator":"@dbiservices","twitter_site":"@dbiservices","twitter_misc":{"Written by":"Open source Team","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a"},"headline":"Deploy DC\/OS using Ansible (Part 2) &#8211; Playbooks","datePublished":"2018-10-26T05:02:19+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/"},"wordCount":319,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"keywords":["Ansible","DC\/OS"],"articleSection":["Database"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/","url":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/","name":"Deploy DC\/OS using Ansible (Part 2) - Playbooks - dbi services Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-10-26T05:02:19+00:00","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Deploy DC\/OS using Ansible (Part 2) &#8211; Playbooks"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi services Blog","description":"#BeSharing","publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.dbi-services.com\/#organization","name":"dbi services","url":"https:\/\/www.dbi-services.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","width":512,"height":512,"caption":"dbi services"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/dbiservices\/","https:\/\/x.com\/dbiservices","https:\/\/www.linkedin.com\/company\/dbi-services\/","https:\/\/www.youtube.com\/user\/dbiservices"],"description":"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.","email":"info@dbi-services.com","telephone":"+41 32 422 96 00","legalName":"dbi services SA"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0b4548362cac3eeff8b3eaf329e3530a","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2022\/05\/open-source-author.png","caption":"Open source Team"},"description":"Posts published under the Open source Team account are collective contributions by the dbi services open infrastructure consultants. The practice covers open-source databases and platforms, PostgreSQL first of all, along with MySQL, MariaDB, and Linux, from architecture, replication, and high availability to performance tuning and operations under service level agreements, and contributes actively to the PostgreSQL community.","url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=11905"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11905\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=11905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=11905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=11905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}