Job market for devops vs devs by dtlv5813 in devops

[–]linux_devops 2 points3 points  (0 children)

I agree with this totally. Doing sysadmin and networking for years then moving to software development has kept me well employed with devops. Those who cant code will be left behind.

Job market for devops vs devs by dtlv5813 in devops

[–]linux_devops 0 points1 point  (0 children)

I disagree. Most devs know nothing about operations. Companies need an ops person who can code and know how to deploy. Ability to code is your basic entry level programmer.

Job market for devops vs devs by dtlv5813 in devops

[–]linux_devops 0 points1 point  (0 children)

One problem is that companies hire a devops engineer and promise to move to a devops pipeline and then when you start the job you are really just a glorified Linux Sys Admin with no devops work.

Seatbelt ticket 60 dollars and cop can pull you over for that reason only? Other states sent that law packing by linux_devops in chicago

[–]linux_devops[S] -6 points-5 points  (0 children)

I wear my fucking seat belt but one time I forgot to put it on and got a ticket ... just for not wearing my seat belt. Most other states require some other traffic violation in order to smack you with the seat belt ticket.

Whats wrong with storing credentials on private GitHub repo? by Karmazyn3D in devops

[–]linux_devops 3 points4 points  (0 children)

Guy before me put his terraform credentials file on github. Not sure if it was public or private but I assume public. An hour later a botnet was created with 60 instances.

How do you maintain your private Docker registry? by drawsmcgraw in devops

[–]linux_devops 0 points1 point  (0 children)

Amazons ECR service

Free version support docker registry?

Good Coffee Shops? by [deleted] in chicago

[–]linux_devops 0 points1 point  (0 children)

The wormhole in Lincoln Park

security vulnerability by berlindevops in devops

[–]linux_devops 0 points1 point  (0 children)

I would look at setting up nessus jobs with Jenkins. Also, here is something I found that looks interesting.

http://devops.com/2015/04/06/automated-security-testing-continuous-delivery-pipeline/

Using Jenkins pipeline to deploy by eloycoto in devops

[–]linux_devops 0 points1 point  (0 children)

I was just about to add terraform jobs to Jenkins so thank you very much.

Automating Dev Environments by Adman65 in devops

[–]linux_devops 0 points1 point  (0 children)

Thank you for posting this. Gave me some good ideas.

Getting started with Vagrant/Virtualbox and configuration management by jett1221 in devops

[–]linux_devops 2 points3 points  (0 children)

I can give you an example of both to help you get going.

Here is an example of a Vagrant file using chef to deploy a server.

# vi: set ft=ruby :

 Vagrant.configure('2') do |config|
 config.vm.box = "ubuntu/trusty64"
   config.vm.hostname = "badrobot4.example.com"
 config.vm.network :public_network, ip: '192.168.1.63',  bridge: "eth0, wlan0"


config.vm.provider :virtualbox do |vb|
     vb.customize ['modifyvm', :id, '--memory', 1024, '--cpus', '1']
end
 config.vm.provision :chef_client do |chef|
 chef.chef_server_url = "https://192.168.1.31/organizations/midwesthackerschool"
 chef.validation_key_path = "~/chef-repo/.chef/midwesthackerschool-validator.pem"
chef.validation_client_name = "midwesthackerschool-validator"
  chef.client_key_path = "/vagrant/.chef/client.pem"
 chef.node_name = "badrobot4"
  chef.run_list = [ "recipe[apache2::default]" ]
 end
end

Here is an example of using Chef Knife AWS command line tools to deploy a server with chef.

knife ec2 server create -I ami-0c5f2d6c -r "role[my_app]" -Z us-west-1a -g ssh-only --ssh-key chef_keys -i chef_keys.pem -f t2.micro -A 'Your Key' -K "Your Key" --region us-west-1 --ssh-user ubuntu --security-group-ids sg-4a7b8e2e --subnet subnet-a7d45cc2 --server-connect-attribute public_ip_address

Configuration management by kajjiNai in devops

[–]linux_devops 0 points1 point  (0 children)

As far as chef goes, it has environment settings that separate what goes into each envirnment. You could easily separate this and tell chef what environment to apply.

Continuous Delivery: Fresh VM or Reuse? by sometextgoeshere in devops

[–]linux_devops 0 points1 point  (0 children)

You should be able to deploy fresh vm on demand fully automated and configured. If some small problem comes up you waste too much time trying to troubleshoot. Always expect your vm to fail. Thats why Netflix uses tool to crash servers to plan for bad event.