{"id":19465,"date":"2022-10-10T11:28:40","date_gmt":"2022-10-10T09:28:40","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=19465"},"modified":"2024-09-11T15:02:36","modified_gmt":"2024-09-11T13:02:36","slug":"add-on-premises-host-in-yak-core","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/add-on-premises-host-in-yak-core\/","title":{"rendered":"Add On-Premises Host in YaK Core"},"content":{"rendered":"\n

\"\"Even if YaK Core<\/a> does not manage on-premises servers provisioning, these can be easily added to YaK inventory. If you are too excited, can’t wait to test YaK and have no cloud account handy, you can use our demo<\/a> or deploy on premises.<\/p>\n\n\n\n

Infrastructure Definitions<\/h2>\n\n\n\n

For on premise, we have to create the directory structure under configuration\/infrastructure. Let’s call it on_prem.<\/p>\n\n\n\n

In my yak container, it looks like this:<\/p>\n\n\n

\nyak@315bd06eb7ad:~\/yak$ tree -d configuration\/infrastructure\/on_prem\/\nconfiguration\/infrastructure\/on_prem\/\n|-- srv-linux-ols-1\n|   `-- WLS_DOMAIN\n|       `-- secrets\n<\/pre><\/div>\n\n\n
As you can see, this server has one components declared (WLS_DOMAIN).<\/p>\n\n\n\n
Let’s create variables.yml<\/code> in on_prem<\/code> directory:<\/p>\n\n\n
\nis_cloud_environment: no\nenvironment: development\nansible_user: ansible\nprovider: on-premises\n<\/pre><\/div>\n\n\n
The important key here is “provider<\/code>“. For the cloud, this field can be equal to aws<\/code>, azure <\/code>or oci<\/code>. In our case, it is equal to “on-premises<\/code>“.<\/p>\n\n\n\n
And, we have to define hosts details in another variables.yml<\/code> inside srv-linux-ols-1<\/code> directory:<\/p>\n\n\n
\nhostname: srv-linux-ols-1\nhost_ip_access: private_ip\nprivate_ip:\n   mode: manual\n   ip: 192.168.222.111\n<\/pre><\/div>\n\n\n
Virtual Machine Provisioning<\/h2>\n\n\n\n
I will use Vagrant<\/a> to provision a local VM with Oracle Linux 8. Vagrantfile (without extension) will look like:<\/p>\n\n\n
\nVagrant.configure("2") do |config|\n  config.vm.box = "generic\/oracle8"\n  config.vm.network "private_network", ip: "192.168.222.111"\n  config.vm.provider "virtualbox" do |vb|\n    vb.memory = "4096"\n  end\nend\n<\/pre><\/div>\n\n\n
This file must be alone in a directory. Then, I simply trigger “vagrant up<\/code>” to bring it up and “vagrant ssh<\/code>” to ssh into it. This must be ran from that directory.<\/p>\n\n\n\n
Deployment<\/h2>\n\n\n\n
Keep in mind that Ansible controller (aka as our YaK container) must have ssh access with a user allowed to sudo. As for me, I have created a user named ansible and added sudo for it. We have to exchange ssh key to make connection from YaK to VM password-less:<\/p>\n\n\n
\nssh-copy-id ansible@192.168.222.111\n<\/pre><\/div>\n\n\n
As a main difference with cloud deployment, we do not need (and can’t) create VM on premises with YaK, thus step below is not necessary:<\/p>\n\n\n
\nansible-playbook servers\/deploy.yml -e target=on_prem\/srv-linux-ols-1\n<\/pre><\/div>\n\n\n
We can go directly to the deployment of our component:<\/p>\n\n\n
\nansible-playbook components\/weblogic_domain\/playbooks\/linux\/deploy.yml -e target=on_prem\/srv-linux-wls-ols-1\/WLS_DOMAIN\n<\/pre><\/div>\n\n\n
This command is doing the following tasks:<\/p>\n\n\n\n