@ecksdeexd said in Run virt-manager on Windows 10:

my name jeff

I read that with the accent.

@nadnerB said in Random Thread - Anything Goes:

Hey that meme is written with Go.

This is the provider I use to clone KVM guests with Terraform https://github.com/dmacvicar/terraform-provider-libvirt

So I told @fuznutz04 the other night I'd send him my Ansible role that creates KVM guests and I completely forgot. Here's a link to what I wrote: https://hooks.technology/2017/10/create-vms-on-kvm-with-ansible/

There is also a library that Larry Smith wrote. Here's a link to the PR https://github.com/ansible/ansible/pull/39340. I just copied what he wrote and put it in my libraries folder so I can use it as a custom module. This module will actually clone a template for you. Here's his example:

---
- hosts:          kvm
  vars:
    vm_template:  ubuntu1604-packer-template
    vms:
      - name:     app01
        state:    started
        template: "{{ vm_template }}"
      - name:     db01
        state:    started
        template: "{{ vm_template }}"
      - name:     lb01
        state:    started
        template: "{{ vm_template }}"
      - name:     web01
        state:    started
        template: "{{ vm_template }}"
  tasks:
    - name:       Cloning VMs
      virt_clone:
        name:     "{{ item['name'] }}"
        state:    "{{ item['state'] }}"
        template: "{{ item['template'] }}"
        uuid:     "{{ item['uuid']|default(omit) }}"
      become:     true
      loop:       "{{ vms }}"

Sorry it took so long to get this out there.

@scottalanmiller said in The Death of Sysadmin:

@stacksofplates said in The Death of Sysadmin:

@scottalanmiller said in The Death of Sysadmin:

@stacksofplates said in The Death of Sysadmin:

@scottalanmiller said in The Death of Sysadmin:

@stacksofplates said in The Death of Sysadmin:

Pick a project on GitHub/GitLab. If they have a .travis yml, Jenkinsfile, .gitlab-ci.yml, bamboo.yml, etc they are leveraging at least CI. I don't think I've noticed one without a build file for quite some time.

Yeah, but that's why I pointed out that most projects aren't up to using Git yet. You are filtering out the most likely to have CI as a starting point.

Yeah I don't believe that, and anyway just because you're not using Git doesn't mean you're not using CI/CD.

True, but essentially no one moves to CI without code management first, it's so hard and cart before the horse.

You are looking at big, public repos and viewing the world that way. But remember, most development is done in languages like Java on old code bases in big silos where all of these concepts remain uncommon.

Ant, Maven, and Gradle are the building blocks of Java build tools leveraged in CI/CD. Its odd you would pick Java as a language that wouldn't be a part of that process.

Not really at all, as Java was popular and entrenched before those were popular. And bottom line, no matter what tools are out there, most developers currently in the work force were not taught those approaches (they were unheard of in university even in 2006) and went to work at companies that had never heard of them.

I've worked in new Java west coast start ups in the last two years that chose Java and had never heard of this stuff. Is it odd that they picked Java? Yes, but not for that reason. They were just "normal developers" without these kinds of skills, and they weren't kids who learned this as "the one way to do it" like it is taught only extremely recently.

It might seem like these approaches are super obvious today, but this is an extremely recent phenomenon. It seems so obvious that we feel like it must have been how people did this for forever, but it just wasn't. CI wasn't popular until XP made it so, and XP was still one of those "niche things" that people thought was a crazy developer cult well into the 2000s.

Ant and Junit were released only 4 years after Javas initial release. This stuff has been around for a long time. XP was the end of the 90s. Just because some small Java companies haven't heard of it doesn't represent most of Java development or development overall.

@scottalanmiller said in The Death of Sysadmin:

@stacksofplates said in The Death of Sysadmin:

@scottalanmiller said in The Death of Sysadmin:

@stacksofplates said in The Death of Sysadmin:

Pick a project on GitHub/GitLab. If they have a .travis yml, Jenkinsfile, .gitlab-ci.yml, bamboo.yml, etc they are leveraging at least CI. I don't think I've noticed one without a build file for quite some time.

Yeah, but that's why I pointed out that most projects aren't up to using Git yet. You are filtering out the most likely to have CI as a starting point.

Yeah I don't believe that, and anyway just because you're not using Git doesn't mean you're not using CI/CD.

True, but essentially no one moves to CI without code management first, it's so hard and cart before the horse.

You are looking at big, public repos and viewing the world that way. But remember, most development is done in languages like Java on old code bases in big silos where all of these concepts remain uncommon.

Ant, Maven, and Gradle are the building blocks of Java build tools leveraged in CI/CD. Its odd you would pick Java as a language that wouldn't be a part of that process.

@scottalanmiller said in The Death of Sysadmin:

@stacksofplates said in The Death of Sysadmin:

@scottalanmiller said in The Death of Sysadmin:

@stacksofplates said in The Death of Sysadmin:

Pick a project on GitHub/GitLab. If they have a .travis yml, Jenkinsfile, .gitlab-ci.yml, bamboo.yml, etc they are leveraging at least CI. I don't think I've noticed one without a build file for quite some time.

Yeah, but that's why I pointed out that most projects aren't up to using Git yet. You are filtering out the most likely to have CI as a starting point.

Yeah I don't believe that, and anyway just because you're not using Git doesn't mean you're not using CI/CD.

True, but essentially no one moves to CI without code management first, it's so hard and cart before the horse.

You are looking at big, public repos and viewing the world that way. But remember, most development is done in languages like Java on old code bases in big silos where all of these concepts remain uncommon.

Well we have thousands of applications 99% in Java in both SVN and Git and most are pipelined. Maybe not all are good pipelines, but they are pipelines.

@scottalanmiller said in The Death of Sysadmin:

@stacksofplates said in The Death of Sysadmin:

Pick a project on GitHub/GitLab. If they have a .travis yml, Jenkinsfile, .gitlab-ci.yml, bamboo.yml, etc they are leveraging at least CI. I don't think I've noticed one without a build file for quite some time.

Yeah, but that's why I pointed out that most projects aren't up to using Git yet. You are filtering out the most likely to have CI as a starting point.

Yeah I don't believe that, and anyway just because you're not using Git doesn't mean you're not using CI/CD.

Pick a project on GitHub/GitLab. If they have a .travis yml, Jenkinsfile, .gitlab-ci.yml, bamboo.yml, etc they are leveraging at least CI. I don't think I've noticed one without a build file for quite some time.

@scottalanmiller said in The Death of Sysadmin:

@stacksofplates said in The Death of Sysadmin:

Uh what are the "other" approaches?

Frequent Integration is more common, for example. If you work with developers, CI is something everyone knows, but the majority don't do. In fact, almost none do in the real world. Good ones might mostly do it, but the average developer isn't a good developer. The average development shop is still struggling with source control, CI isn't even on their horizon.

That's not an other. That's part of CI/CD.