{"id":9702,"date":"2017-01-26T14:31:25","date_gmt":"2017-01-26T13:31:25","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/"},"modified":"2023-07-12T09:17:42","modified_gmt":"2023-07-12T07:17:42","slug":"part2-vagrant-up-get-your-oracle-infrastructure-up-an-running","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/","title":{"rendered":"Part 2 – vagrant up – get your Oracle infrastructure up an running"},"content":{"rendered":"

Last week in the first part of this blog <\/a> we have seen a short introduction how to setup an Oracle Infrastructure with Vagrant and Ansible. Remember all the files for this example are available here https:\/\/github.com\/nkadbi\/oracle-db-12c-vagrant-ansible<\/a>
\nGet the example code:
\n
\ngit clone https:\/\/github.com\/nkadbi\/oracle-db-12c-vagrant-ansible
\n<\/code><\/p>\n

If you have prepared your environment with Ansible, Vagrant and Oracle Virtual Box installed – and provided the Oracle software zip files –
\nthan you can just start to build your Test Infrastructure with the simple call<\/strong>vagrant up<\/code>
\n cleanup is also easy- stop the vagrant machines and deletes all traces:<\/strong>
\nvagrant destroy <\/code>
\nHow does this work ? <\/strong>
\nvagrant up<\/em> starts Vagrant which will setup two virtual servers using a sample box with CentOS 7.2.
\nWhen this has been finished Vagrant calls Ansible for provisioning which configures the linux servers, installs the Oracle software and creates your databases on the target servers in parallel.<\/p>\n

Vagrant configuration <\/strong>
\nAll the configuration for Vagrant is in one file called Vagrantfile<\/a>
\nI used a box with CentOS 7.2 which you can find among other vagrant boxes here https:\/\/atlas.hashicorp.com\/search<\/a>
\nconfig.vm.box = \"boxcutter\/centos72\" <\/code> If you start vagrant up the first time it will download the vagrant box <\/strong>
\n$ vagrant up
\n\u2026
\nBringing machine 'dbserver1' up with 'virtualbox' provider...
\nBringing machine 'dbserver2' up with 'virtualbox' provider...
\n==> dbserver1: Box 'boxcutter\/centos72' could not be found. Attempting to find and install...
\ndbserver1: Box Provider: virtualbox
\ndbserver1: Box Version: >= 0
\n==> dbserver1: Loading metadata for box 'boxcutter\/centos72'
\ndbserver1: URL: https:\/\/atlas.hashicorp.com\/boxcutter\/centos72
\n==> dbserver1: Adding box 'boxcutter\/centos72' (v2.0.21) for provider: virtualbox
\ndbserver1: Downloading: https:\/\/atlas.hashicorp.com\/boxcutter\/boxes\/centos72\/versions\/2.0.21\/providers\/virtualbox.box
\n==> dbserver1: Successfully added box 'boxcutter\/centos72' (v2.0.21) for 'virtualbox'!
\n==> dbserver1: Importing base box 'boxcutter\/centos72'...
\n<\/code>
\nI have chosen a private network for the virtual servers and use vagrant hostmanager plugin<\/a> to take care of the \/etc\/hosts files on all guest machines (and optionally your localhost)
\nyou can add this plugin to vagrant with:
\nvagrant plugin install vagrant-hostmanager <\/code> The corresponding part in the Vagrantfile will look like this:
\nconfig.hostmanager.enabled = true
\nconfig.hostmanager.ignore_private_ip = false # include private IPs of your VM's
\nconfig.vm.hostname = \u201cdbserver1\u201d
\nconfig.vm.network \"private_network\", ip: \"192.168.56.31\" <\/code>
\n ssh Configuration <\/strong>
\nThe Vagrant box comes already with ssh key configuration and– if security does not matter in your demo environment – <\/strong> the easiest way to configure ssh connection to your guest nodes is to use the same ssh key for all created virtual hosts.
\nconfig.ssh.insert_key = false # Use the same insecure key provided from box for each machine <\/code> After bringing up the virtual servers you can display the ssh settings:
\nvagrant ssh-config <\/code> The important lines from the output are:
\nHost dbserver1
\nHostName 127.0.0.1
\nUser vagrant
\nPort 2222
\nIdentityFile \/home\/user\/.vagrant.d\/insecure_private_key <\/code> You should be able to reach your guest server without password with user vagrant
\nvagrant ssh dbserver1 <\/code>Than you can switch to user oracle ( password = welcome1 ) or root (default password for vagrant boxes vagrant) su - oracle <\/code>or directly connect with ssh ssh vagrant@127.0.0.1 -p 2222 -i \/home\/user\/.vagrant.d\/insecure_private_key <\/code>
\n Virtual Disks <\/strong>
\nI added additional virtual disks because I wanted to separate data file destination from fast recovery area destination. # attach disks only localy
\nif ! File.exist?(\"dbserver#{i}_disk_a.vdi\") # create disks only once
\nv.customize ['createhd', '--filename', \"dbserver#{i}_disk_a.vdi\", '--size', 8192 ]
\nv.customize ['createhd', '--filename', \"dbserver#{i}_disk_b.vdi\", '--size', 8192 ]
\nv.customize ['storageattach', :id, '--storagectl', 'SATA Controller', '--port', 1, '--device', 0, '--type', 'hdd', '--medium', \"dbserver#{i}_disk_a.vdi\"]
\nv.customize ['storageattach', :id, '--storagectl', 'SATA Controller', '--port', 2, '--device', 0, '--type', 'hdd', '--medium', \"dbserver#{i}_disk_b.vdi\"]
\nend # create disks only once <\/code>
\n Provisioning with Ansible <\/strong>
\nAt the end of the Vagrantfile provisioning with Ansible is called.
\nN = 2
\n(1..N).each do |i| # do for each server i
\n...
\nif i == N
\nconfig.vm.provision \"ansible\" do |ansible| # vm.provisioning
\n#ansible.verbose = \"v\"
\nansible.playbook = \"oracle-db.yml\"
\nansible.groups = { \"dbserver\" => [\"dbserver1\",\"dbserver2\"] }
\nansible.limit = 'all'
\nend # end vm.provisioning
\nend
\nend <\/code>To prevent the Ansible provisioning to start before all servers have been setup by Vagrant, I included the condition if i == N , where N is the number of desired servers.<\/p>\n

Ansible Inventory <\/strong>
\nThe Ansible Inventory is a collection of guest hosts against which Ansible will work.
\nYou can either put the information in an inventory file or let Vagrant create an Inventory file for you. Vagrant does this if you did not specify any inventory file.
\nTo enable Ansible to connect to the target hosts without password Ansible has to know the ssh key provided by the vagrant box.
\nExample Ansible Inventory:
\n# Generated by Vagrant
\ndbserver2 ansible_ssh_host=127.0.0.1 ansible_ssh_port=2200 ansible_ssh_user='vagrant' ansible_ssh_private_key_file='\/home\/user\/.vagrant.d\/insecure_private_key'
\ndbserver1 ansible_ssh_host=127.0.0.1 ansible_ssh_port=2222 ansible_ssh_user='vagrant' ansible_ssh_private_key_file='\/home\/user\/.vagrant.d\/insecure_private_key'
\n[dbserver]
\ndbserver1
\ndbserver2 <\/code> You can see that the inventory created by Vagrant presents the necessary information to Ansible to connect to the targets and has also defined the group dbserver which includes the server dbserver1 and dbserver2.<\/p>\n

Ansible configuration <\/strong>
\ntell Ansible where to find the inventory in the ansible.cfg.
\nnocows=1
\nhostfile = .vagrant\/provisioners\/ansible\/inventory\/vagrant_ansible_inventory
\nhost_key_checking = False<\/code>
\n Ansible Variables <\/strong>
\nIn this example I have put the general variables for all servers containing an Oracle Database into this file:
\n group_vars\/dbserver<\/a>
\nThe more specific variables including variables used to create the database like the database name, character set
\ncan be adapted individual for each server:
\nhost_vars\/dbserver1,host_vars\/dbserver2<\/a><\/p>\n

Ansible Playbook<\/strong>
\nThe Ansible playbook is a simple textfile written in YAML syntax, which is easy readable.
\nOur playbook oracle-db.yml<\/a> has only one play called \u201c Configure Oracle Linux 7 with Oracle Database 12c\u201d which will be applied on all servers belonging to the group dbserver<\/em>. In my example Vagrant creates the vagrant inventory and initiates the play of the playbook but you can also start it stand-alone or repeat it if you want.
\n ansible-playbook oracle-db.yml <\/code>
\nThis is the whole playbook, to configure the servers and install Oracle Databases:
\n$cat oracle-db.yml
\n---
\n- name: Configure Oracle Linux 7 with Oracle Database 12c
\nhosts: dbserver
\nbecome: True
\nvars_files:
\n# User Passwords hashed are stored here:
\n- secrets.yml
\nroles:
\n- role: disk_layout
\n- role: linux_oracle
\n- role: oracle_sw_install
\nbecome_user: '{{ oracle_user }}'
\n- role: oracle_db_create
\nbecome_user: '{{ oracle_user }}' <\/code><\/p>\n

Ansible roles<\/strong>
\nTo make the playbook oracle-db.yml lean and to be more flexible I have split all the tasks into different roles.<\/a>This makes it easy to reuse parts of the playbook or skip parts. For example if you only want to install the oracle software on the server, but do not want to create databases you can just delete the role oracle_db_create from the playbook.
\nYou (and Ansible ) will find the files containing the tasks for a role in the directory roles\/my_role_name\/main.yml<\/em>.
\nThere can be further directories. The default directory structure looks like below. If you want to create a new role you can even create the directory structure by using ansible-galaxy. Ansible Galaxy is Ansible\u2019s official community hub for sharing Ansible roles. https:\/\/galaxy.ansible.com\/intro<\/a>
\n
\n# example to create the directory structure for the role \"my_role_name\"
\nansible-galaxy init my_role_name
\n<\/code>
\n
\n# default Ansible role directory structure
\nroles\/
\nmy_role_name\/
\ndefaults\/
\nfiles\/
\nhandlers\/
\nmeta\/
\ntasks\/
\ntemplates\/
\nvars\/
\n<\/code><\/p>\n

Ansible Modules<\/strong>
\nAnsible will run the tasks described in the playbook on the target servers by invoking Ansible Modules.
\nThis Ansible Web Page http:\/\/docs.ansible.com\/ansible\/list_of_all_modules.html <\/a> shows information about Modules ordered by categories.
\nYou can also get information about all the Ansible modules from command line:
\n
\n# list all modules
\nansible-doc --list
\n# example to show documentation about the Ansible module \"copy\"
\nansible-doc copy <\/code><\/p>\n

One Example:
\nTo install the oracle software with response file I use the Ansible module called “template”<\/strong>. Ansible uses Jinja2, a templating engine for Python.
\nThis makes it very easy to design reusable templates. For example Ansible will replace {{ oracle_home }} with the variable, which I have defined in group_vars\/dbserver, and than copies the response file to the target servers:<\/p>\n

Snipped from the Jinja2 template db_install.rsp.j2<\/a>
\n
\n#-------------------------------------------------------------------------------
\n# Specify the complete path of the Oracle Home.
\n#-------------------------------------------------------------------------------
\nORACLE_HOME={{ oracle_home }}
\n<\/code>
\nSnipped from roles\/oracle_sw_install\/tasks\/main.yml<\/a>
\n
\n- name: Gerenerate the response file for software only installation
\ntemplate: src=db_install.rsp.j2 dest={{ installation_folder }}\/db_install.rsp
\n<\/code><\/p>\n

Ansible Adhoc Commands – Some Use Cases <\/strong>
\nImmediately after installing Ansible you already can use Ansible to gather facts <\/strong> from your localhost which will give you a lot of information:
\nansible localhost -m setup <\/code>
\nUse Ansible adhoc command with module ping <\/strong> to check if you can reach all target servers listed in your inventory file:
\n
\n$ ansible all -m ping
\ndbserver2 | SUCCESS => {
\n\"changed\": false,
\n\"ping\": \"pong\"
\n}
\ndbserver1 | SUCCESS => {
\n\"changed\": false,
\n\"ping\": \"pong\"
\n} <\/code><\/p>\n

File transfer <\/strong> – spread a file to all servers in the group dbserver
\nansible dbserver -m copy -b -a \"src=\/etc\/hosts dest=\/etc\/hosts\" <\/code><\/p>\n

Conclusion<\/strong>
\nWith the open source tools Vagrant and Ansible you can easily automate the setup of your infrastructure.
\nEven if you do not want to automate everything, Ansible still can help you with your daily work if you want to check or apply something on several servers.
\nJust group your servers in an inventory and run an Ansible Adhoc Command or write a small playbook.<\/p>\n

Please keep in mind that this is a simplified example for an automated Oracle Database Installation.
\nDo not use this example for productive environments.<\/p>\n","protected":false},"excerpt":{"rendered":"

Last week in the first part of this blog we have seen a short introduction how to setup an Oracle Infrastructure with Vagrant and Ansible. Remember all the files for this example are available here https:\/\/github.com\/nkadbi\/oracle-db-12c-vagrant-ansible Get the example code: git clone https:\/\/github.com\/nkadbi\/oracle-db-12c-vagrant-ansible If you have prepared your environment with Ansible, Vagrant and Oracle Virtual […]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[150,708,101,46,209,770,970],"type_dbi":[],"class_list":["post-9702","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-ansible","tag-automation","tag-installation","tag-linux-unix","tag-oracle-12c","tag-provisioning","tag-vagrant"],"acf":[],"yoast_head":"\nPart 2 - vagrant up - get your Oracle infrastructure up an running - dbi Blog<\/title>\n<meta name=\"description\" content=\"Blog Part 2 - automated setup of Oracle Infrastructure with Vagrant and Ansible. Oracle Database 12.1.0.2 , CentOS 7.2\" \/>\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\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Part 2 - vagrant up - get your Oracle infrastructure up an running\" \/>\n<meta property=\"og:description\" content=\"Blog Part 2 - automated setup of Oracle Infrastructure with Vagrant and Ansible. Oracle Database 12.1.0.2 , CentOS 7.2\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-01-26T13:31:25+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-07-12T07:17:42+00:00\" \/>\n<meta name=\"author\" content=\"Oracle 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=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 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\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Part 2 – vagrant up – get your Oracle infrastructure up an running\",\"datePublished\":\"2017-01-26T13:31:25+00:00\",\"dateModified\":\"2023-07-12T07:17:42+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/\"},\"wordCount\":1098,\"commentCount\":0,\"keywords\":[\"Ansible\",\"Automation\",\"Installation\",\"Linux\/UNIX\",\"Oracle 12c\",\"Provisioning\",\"Vagrant\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/\",\"name\":\"Part 2 - vagrant up - get your Oracle infrastructure up an running - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2017-01-26T13:31:25+00:00\",\"dateModified\":\"2023-07-12T07:17:42+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"Blog Part 2 - automated setup of Oracle Infrastructure with Vagrant and Ansible. Oracle Database 12.1.0.2 , CentOS 7.2\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Part 2 – vagrant up – get your Oracle infrastructure up an running\"}]},{\"@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\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Part 2 - vagrant up - get your Oracle infrastructure up an running - dbi Blog","description":"Blog Part 2 - automated setup of Oracle Infrastructure with Vagrant and Ansible. Oracle Database 12.1.0.2 , CentOS 7.2","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\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/","og_locale":"en_US","og_type":"article","og_title":"Part 2 - vagrant up - get your Oracle infrastructure up an running","og_description":"Blog Part 2 - automated setup of Oracle Infrastructure with Vagrant and Ansible. Oracle Database 12.1.0.2 , CentOS 7.2","og_url":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/","og_site_name":"dbi Blog","article_published_time":"2017-01-26T13:31:25+00:00","article_modified_time":"2023-07-12T07:17:42+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Part 2 – vagrant up – get your Oracle infrastructure up an running","datePublished":"2017-01-26T13:31:25+00:00","dateModified":"2023-07-12T07:17:42+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/"},"wordCount":1098,"commentCount":0,"keywords":["Ansible","Automation","Installation","Linux\/UNIX","Oracle 12c","Provisioning","Vagrant"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/","url":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/","name":"Part 2 - vagrant up - get your Oracle infrastructure up an running - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2017-01-26T13:31:25+00:00","dateModified":"2023-07-12T07:17:42+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"Blog Part 2 - automated setup of Oracle Infrastructure with Vagrant and Ansible. Oracle Database 12.1.0.2 , CentOS 7.2","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/part2-vagrant-up-get-your-oracle-infrastructure-up-an-running\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Part 2 – vagrant up – get your Oracle infrastructure up an running"}]},{"@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\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9702","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\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=9702"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9702\/revisions"}],"predecessor-version":[{"id":26667,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9702\/revisions\/26667"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=9702"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=9702"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=9702"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=9702"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}