Post has attachment
This devops series of videos enables you to understand what exactly is devops, how would be the devops culture, what are the different automation tools used in devops and how devops benefits the software organisations.

This video is an introduction to devops course and we are trying to make the videos suitable for both beginners and experienced learners.

Going forward, As part of this series, we are going to give you an idea on

1) software configuration management tools like SVN,GIT etc
2) Build tools like Ant,Maven etc
3) Continuous Integration tools like Jenkins etc
4) Configuration Management tools like chef,puppet etc
5) Job Monitoring tools like COntrol M etc
6) Artifact Repository tools like Nexus etc
7) Testing automation tools like Selenium etc
8) Cloud technologies like AWS, Azure etc
9) Middle ware technologies like WAS, Weblogic etc
10) Server monitoring tools like Nagios
11) Container technologies like docker etc

Many more automation tools

Please subscribe to our channel and click on the bell button to get our video uploads.

Please like, share and comment.

Feel free to reach us on our email id for devops courses both online & offline and other technologies.

softwareacademy1@gmail.com

Happy learning !

https://youtu.be/VV3nmYVB5j4

#devops #automation #jenkins #chef #puppet #aws #cloud #nagios #sonarqube #git #svn #ansible 

Post has attachment
We train on Vagrant virtualization in the DevOps course
https://youtu.be/CZHbbfB7NgQ

Post has attachment
Read this tutorial to learn how to use Vagrant for automating a dev environment and cloud infrastructure testing, and see some of its basic use cases.

Post has attachment

Post has shared content

heres a script to clean up all those vboxnets left by private_networks.

make sure you dont have any vagrant files running and remember to fill in "exceptions" if you have any host onlys your want to keep!

https://gist.github.com/xahare/df35087c0411bd214519

I have installed vagrant, but when I try to get to it via web browser I get site can't be reached.

[derrick@antergos ~]$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'base'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: derrick_default_1458382922039_51289
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 4.2.0
default: VirtualBox Version: 5.0
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: Mounting shared folders...
default: /vagrant => /home/derrick

Is there a formal term for the "works on my machine" problem that Vagrant is used to prevent and resolve?

Hi everybody!! I have a real problem with Gitlab installation with Vagrant VM.
I have done the installation of Gitlab correctly , but when I restart Vagrant
I can't use "gitlab-ctl" command . I verify on "/etc" I don't see "gitlab-ctl" repertory.
What's the problem ?

Post has attachment
If you vagrant up a lot with debian based systems, it sucks to keep reaching out to the internet. One solution is to keep a permanent VM running with an apt-cache (i use squid-deb-proxy)

This way, if someone using your vagrantfile doesnt have one, it just skips it.

https://groups.google.com/forum/#!topic/vagrant-up/R31Bu-enX-k
Wait while more posts are being loaded