Finally, after all the configuration stuff is done, we can run the playbooks<\/p>\n
First the SSH Access on all nodes need to be created. Therefore the access-onprem.yml is used:
\nBe careful, I used CentOS on my system, so I commented the apt-get and the debian-based part out.
\nIf you want to run the playbook on another operating system, adjust it carefully.<\/p>\n
---\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 && 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 && 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 && 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 && 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>\nStart the Playbook for the SSH access<\/h4>\n[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>\nThis is not the whole output of the playbook. Important to know, during the “TASK [Test Ansible user’s access]” I had to insert the Ansible password 5 times. After that the playbooks finished successfully.<\/p>\n
Ping the servers using Ansible<\/h4>\n
After the playbook finished successfully do a test ping<\/p>\n
[root@dcos-ansible ansible-dcos]# ansible all -m ping\n192.168.22.102 | SUCCESS => {\n \"changed\": false,\n \"ping\": \"pong\"\n}\n192.168.22.100 | SUCCESS => {\n \"changed\": false,\n \"ping\": \"pong\"\n}\n192.168.22.104 | SUCCESS => {\n \"changed\": false,\n \"ping\": \"pong\"\n}\n192.168.22.101 | SUCCESS => {\n \"changed\": false,\n \"ping\": \"pong\"\n}\n192.168.22.103 | SUCCESS => {\n \"changed\": false,\n \"ping\": \"pong\"\n}\n<\/pre>\nIn case of trouble it is really helpful to use the “-vvv” option.
\nIt is also possible to ping only one server using <\/p>\n
ansible 192.168.22.100 -m ping<\/pre>\nRollout the DC\/OS installation<\/h3>\n[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[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>\nIn 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
ansible-playbook plays\/install.yml --limit @\/root\/ansible-dcos\/plays\/install.retry\n<\/pre>\nIf 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’t available on my VM.
\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
[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>\nInstall the CLI<\/h4>\n
For those of you, which prefer a CLI, just install it on your master.<\/p>\n
[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>\nThat’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!
\nOne little thing I have to mention at the end. Don’t confide in the official documentation and the troubleshooting guide, it does not help as much as expected…<\/p>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[150,1472],"type_dbi":[],"class_list":["post-11905","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-ansible","tag-dc-os"],"acf":[],"yoast_head":"\n
Deploy DC\/OS using Ansible (Part 2) - Playbooks - dbi 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:url\" content=\"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-10-26T05:02:19+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-12-19T15:54:27+00:00\" \/>\n<meta name=\"author\" content=\"Open source Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\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\/59554f0d99383431eb6ed427e338952b\"},\"headline\":\"Deploy DC\/OS using Ansible (Part 2) – Playbooks\",\"datePublished\":\"2018-10-26T05:02:19+00:00\",\"dateModified\":\"2025-12-19T15:54:27+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/\"},\"wordCount\":319,\"commentCount\":0,\"keywords\":[\"Ansible\",\"DC\/OS\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"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 Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2018-10-26T05:02:19+00:00\",\"dateModified\":\"2025-12-19T15:54:27+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b\"},\"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\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Deploy DC\/OS using Ansible (Part 2) – Playbooks\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"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\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"caption\":\"Open source Team\"},\"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 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_url":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/","og_site_name":"dbi Blog","article_published_time":"2018-10-26T05:02:19+00:00","article_modified_time":"2025-12-19T15:54:27+00:00","author":"Open source Team","twitter_card":"summary_large_image","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\/59554f0d99383431eb6ed427e338952b"},"headline":"Deploy DC\/OS using Ansible (Part 2) – Playbooks","datePublished":"2018-10-26T05:02:19+00:00","dateModified":"2025-12-19T15:54:27+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/deploy-dcos-using-ansible-part-2-playbooks\/"},"wordCount":319,"commentCount":0,"keywords":["Ansible","DC\/OS"],"articleSection":["Database Administration & Monitoring"],"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 Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-10-26T05:02:19+00:00","dateModified":"2025-12-19T15:54:27+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b"},"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":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Deploy DC\/OS using Ansible (Part 2) – Playbooks"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","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":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","caption":"Open source Team"},"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":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11905\/revisions"}],"predecessor-version":[{"id":42104,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11905\/revisions\/42104"}],"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"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=11905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}