How to create CentOS VM using Vagrant

By

Create CentOS VM using Vagrant


 1. Download and install the latest Oracle VM VirtualBox. 

https://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html

Like (For Mac OS X)
https://download.oracle.com/virtualbox/6.0.6/VirtualBox-6.0.6-130049-OSX.dmg

2. Download and install the latest Vagrant.

https://www.vagrantup.com/downloads.html

Like (For Mac OS X)
https://releases.hashicorp.com/vagrant/2.2.4/vagrant_2.2.4_x86_64.dmg

3. Download "centos/7" Vagrant Box using below command.

abhinavs-Air:~ agupta$ vagrant box add centos/7
==> box: Loading metadata for box 'centos/7'
    box: URL: https://vagrantcloud.com/centos/7
This box can work with multiple providers! The providers that it
can work with are listed below. Please review the list and choose
the provider you will be working with.


1) hyperv
2) libvirt
3) virtualbox
4) vmware_desktop


Enter your choice: 3
==> box: Adding box 'centos/7' (v1902.01) for provider: virtualbox
    box: Downloading: https://vagrantcloud.com/centos/boxes/7/versions/1902.01/providers/virtualbox.box
    box: Download redirected to host: cloud.centos.org
==> box: Successfully added box 'centos/7' (v1902.01) for 'virtualbox'!
abhinavs-Air:~ agupta$ 

 4. Create a directory "centos7-test-vm" and create Vagrant config file.

abhinavs-Air:~ agupta$ mkdir -p vagrant_box/centos7-test-vm

abhinavs-Air:~ agupta$ cd vagrant_box/centos7-test-vm

abhinavs-Air:centos7-test-vm agupta$ vagrant init
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.

abhinavs-Air:centos7-test-vm agupta$ ls -lrth
total 8
-rw-r--r--  1 agupta  staff   2.9K May 11 20:33 Vagrantfile 

 5. Check default vagrant file content.

abhinavs-Air:centos7-test-vm agupta$ cat Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :


# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.


  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://vagrantcloud.com/search.
  config.vm.box = "base"


  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false


  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080


  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"


  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"


  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"


  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"


  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.


  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
end
abhinavs-Air:centos7-test-vm agupta$ 

6. Edit below highlighted content inside the Vagrantfile.

 - Change config.vm.box = "base" to "centos/7"

 - Add config.vm.hostname = "centos7-test-vm"

 - Uncomment config.vm.network "private_network", ip: "192.168.33.10" [Note : If default IP is already been used by any other VM then change it.] 

 - Uncomment below section to define custom Physical RAM memory 

    config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true ---> This section can been uncommentted if you need GUI interface of VM.
  #
  #   # Customize the amount of memory on the VM:
      vb.memory = "1024"
    end 

 7. Below is the content of Vagrantfile after editing above content

abhinavs-Air:centos7-test-vm agupta$ vim Vagrantfile

abhinavs-Air:centos7-test-vm agupta$ cat Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :


# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.


  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://vagrantcloud.com/search.
  config.vm.box = "centos/7"
  config.vm.hostname = "centos7-test-vm"


  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false


  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080


  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"


  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
    config.vm.network "private_network", ip: "192.168.33.60"


  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"


  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"


  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
    config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
      vb.memory = "1024"
    end
  #
  # View the documentation for the provider you are using for more
  # information on available options.


  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
end
abhinavs-Air:centos7-test-vm agupta$ 

8. Now Start/UP CentOS VM. Verify current directory is "centos7-test-vm" directory. 

abhinavs-Air:centos7-test-vm agupta$ pwd
/Users/agupta/vagrant_box/centos7-test-vm

abhinavs-Air:centos7-test-vm agupta$ vagrant up

 9. Verify VM created successfully and it is up/running. 

abhinavs-Air:centos7-test-vm agupta$ pwd
/Users/agupta/vagrant_box/centos7-test-vm

abhinavs-Air:centos7-test-vm agupta$ vagrant status
Current machine states:


default                   running (virtualbox)


The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.
abhinavs-Air:centos7-test-vm agupta$ 

 10. Connect to CentOS VM

abhinavs-Air:centos7-test-vm agupta$ pwd
/Users/agupta/vagrant_box/centos7-test-vm

abhinavs-Air:centos7-test-vm agupta$ vagrant ssh
-bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory

[vagrant@centos7-test-vm ~]$ sudo su -

[root@centos7-test-vm ~]# 
Enjoy CentOS VM 😊

 Photo by Sai Kiran Anagani on Unsplash

Comments

Post a Comment

Popular

SLEEP thread causing "Waiting for table metadata lock"

By
Image
SLEEP thread causing "Waiting for table metadata lock" We might have faced some scenarios once our db connection threads are getting locked and we try to find the culprit thread id which is locking the thread, to kill and release the connections.  Here I am going to focus on one of the scenarios when db connection threads are locked at state " waiting for table metadata lock " and when we see the processlist, we can't find any thread which is running and using the same table, i.e., all threads are in SLEEP state except the locked threads. Such as :  mysql [localhost:5726] {msandbox} (world) > show processlist\G *************************** 1. row ***************************            Id: 5          User: rsandbox          Host: localhost:60624            db: NULL       Command: Binlog Dump       ...
Read more

MySQL Memory Calculator

By
Image
MySQL Memory Calculator Check out the “ MySQL Memory Calculator ” added to my blog page, which will be helpful to calculate MySQL memory usage during tuning of MySQL memory parameters. https://www.abhinavbit.com/p/mysql-memory-calculator.html Photo by  Kelly Sikkema  on  Unsplash
Read more

errno: 24 - Too many open files

By
Image
errno: 24 - Too many open files You might see this error inside MySQL's error log file or during mysql_upgrade operation. Can't open file: ‘./db/table.frm' (errno: 24 - Too many open files) To solve this issue, you will need to change the open files limit at system and db service level. --> To check and change this limit at the system level, we use ulimit client tool to set it dynamically. * Check current system open file limit. root@test:~# ulimit -a core file size          (blocks, -c) 0 data seg size           (kbytes, -d) unlimited scheduling priority             (-e) 0 file size               (blocks, -f) unlimited pending signals            ...
Read more

How to properly shutdown MySQL before any maintenance activity

By
Image
How to properly shutdown MySQL before any maintenance activity We might have different scenarios once we need to stop MySQL service before performing either server or database activity like patching/upgrade.   Before performing such activity, we need to make sure that we stop MySQL service properly to avoid any unforeseen crashes once our maintenance activity complete and MySQL service is started.  Here I would like to share the below steps which should be performed and take care to properly stop MySQL service.  Step 1: Ensure we don't have any long-running queries. Manually verify by checking the processlist. show processlist;  Step 2: If it is the master node, then ensure to stop application write hits on the database by doing either stop an app and put in maintenance OR if we have any failover solution then move write hits on another node.  Step 3: If it is a slave node, then STOP replication and note down t...
Read more

set --server-id to enable either a master or a slave

By
set --server-id to enable either a master or a slave Below issue can be faced, when we run CHANGE MASTER command to setup replication. mysql> change master to master_host='xx.xx.xx.xx',master_user='rep_user',master_password="xxxxxxx", master_log_file='db-01-test-bin.000064',master_log_pos=95854072,master_auto_position=0; ERROR 1794 (HY000): Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log. Solution :- Here It is assumed, We have already set server-id parameter value different on master and slave node but still, we have the above error. It happens once, you performed the server packages upgrade(like from 5.6 to 5.7) and just started MySQL service and going to run CHANGE MASTER command. So, to solve this issue, Run mysql_upgrade command to update/upgrade system tables and then restart M...
Read more

ERROR 1040 (HY000): Too many connections

By
Image
ERROR 1040 (HY000): Too many connections An application might face this issue when all the defined max_connections parameter value is exhausted.  mysqld reserve a  +1 connection (i.e., max_connections + 1) for the user who is having the SUPER privilege.  When this issue appears, Only the user with the SUPER privileges can be connected if any other user who has SUPER privileges is not already connected to the database and we have reached max_connections.  1. Always make sure to DON'T give the SUPER privilege to any application user or any user which is being used inside the scripts. Because if that user has already been connected to db when "too many connections" issue appears, then that time root user can't be connected even though root user is having all privileges along with SUPER privileges.  Here I am presenting 3 cases which will help us, how MySQL handles "too many connections" and reserve 1 connection. For below example,...
Read more

GTID Replication (Skip Transaction using empty transaction)

By
Image
GTID Replication (Skip Transaction using empty transaction) To skip SQL thread's error in GTID replication setup, Insert empty transaction. PROBLEM :  db -test (none ) > show slave status\G *************************** 1. row ***************************                Slave_IO_State: Waiting for master to send event                   Master_Host: xxxxx                   Master_User: rep_user                   Master_Port: 3306                 Connect_Retry: 60               Master_Log_File: db -test-02-bin . 006725           Read_Master_Log_Pos: 4508785                Relay_Log_File: db -test-relay-bin . 000015         ...
Read more

Master has purged binary logs containing GTIDs that the slave requires

By
Master has purged binary logs containing GTIDs that the slave requires Problem :  Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.' Solution : stop slave; Query OK, 0 rows affected (0.00 sec) CHANGE MASTER TO MASTER_AUTO_POSITION = 0; Query OK, 0 rows affected (0.01 sec) start slave; Query OK, 0 rows affected (0.00 sec)
Read more

How to Prepare for MySQL Certification Exam

By
Image
How to Prepare for MySQL Certification Exam Here I am going to suggest MySQL DBA, student or any newbie that how they can prepare for "Oracle's MySQL 5.x Database Administrator" certification exam.  Step 1: Lab -- Prepare your local MySQL lab environment and make sure to install the respective MySQL version on your lab. (i.e., if you are going to appear on MySQL 5.6 DBA exam 1Z0-883 then install MySQL 5.6 on your lab)  -- You can follow my below blog post to create your local MySQL lab environment.  How to create CentOS VM using Vagrant Install MySQL on CentOS using DBdeployer Step 2: Book + HandsOn Experience -- If you don't have below book, then go right now and purchase this book. (Here Please, you don't judge that below-suggested book is for 5.0 version whereas you are going to prepare for MySQL 5.6/5.7 DBA certification exam. Just go ahead and purchase below book. In the end, you will definitely say it was your...
Read more