VPS Open Ports - Thoughts?

stacksofplates

There are definitely use cases for everything being in a playbook. This playbook updates my DNS servers and sends a completed or failed message to Slack. It didn't make much sense to create a role for any of this.

---
- name: Update playbook
  hosts: dns_servers
  user: centos
  become: true
  gather_facts: true
  serial: 1   

  tasks:
    - block:
      - name: update packages
        package:
          name: '*'
          state: latest
      - name: reboot servers
        shell: sleep 2 && /sbin/shutdown -r now "Ansible system upgraded"
        async: 1
        poll: 0
        ignore_errors: true

      - name: wait for server to come back
        wait_for:
          host: "{{ openstack.networks.private[1] }}"
          port: 22
          delay: 10
        delegate_to: localhost

      - name: Send Slack notification
        slack:
          token: "{{ slack_token }}"
          channel: #ansible
          msg: "Updates completed on {{ openstack.name }} successfully"
        delegate_to: localhost

      rescue:
        - name: fail
          slack:
            token: "{{ slack_token }}"
            channel: #ansible
            msg: "Updates on {{ openstack.name }} failed"
          delegate_to: localhost

Obsolesce

Ansible looks confusing at first. It'd take me some getting used to.

With Salt, there's basically two parts:

A top file to say which hosts, groups, pillars, grains, etc get what (state files).
States that are applied according to the top file.

And you can include / chain other state files.

stacksofplates

@tim_g said in VPS Open Ports - Thoughts?:

Ansible looks confusing at first. It'd take me some getting used to.

With Salt, there's basically two parts:

A top file to say which hosts, groups, pillars, grains, etc get what (state files).

States that are applied according to the top file.

If I'm reading that right, that sounds similar. Ansible lets you assign different levels per variable as well. So the default directory in a role has the least priority. They are used as sane defaults. They can be overridden with the vars directory in a role. And those can be overridden in a playbook. And those can be overridden by the command line (or Tower/AWX).

Roles also have the test directory to allow you to test the role. If you look at that hardening role, there's a playbook in the test directory that tells Vagrant how to build everything.

Obsolesce

I'm thinking about a SaltStack certification path to help me really, really learn it. I feel like I've barely touched it and I already feel this (and similar like Ansible) are so insanely powerful and are the future of systems management.

scottalanmiller

@tim_g said in VPS Open Ports - Thoughts?:

I'm thinking about a SaltStack certification path to help me really, really learn it. I feel like I've barely touched it and I already feel this (and similar like Ansible) are so insanely powerful and are the future of systems management.

And they are! That's what I presented at MangoCon

And that's Sodium's idea... take what Salt and Ansible do and build on top of that for even more power.

Obsolesce

@scottalanmiller said in VPS Open Ports - Thoughts?:

And they are! That's what I presented at MangoCon

Still waiting on those videos!

scottalanmiller

@tim_g said in VPS Open Ports - Thoughts?:

@scottalanmiller said in VPS Open Ports - Thoughts?:

And they are! That's what I presented at MangoCon

Still waiting on those videos!

Yeah @Minion-Queen

Obsolesce

@scottalanmiller said in VPS Open Ports - Thoughts?:

And that's Sodium's idea... take what Salt and Ansible do and build on top of that for even more power.

Yeah, once I got into SaltStack, and realized Sodium is building on that, I threw myself on board and am waiting and watching Sodium.

stacksofplates

I really think if we could get a Kubernetes (or an ELB type thing) for systems management that would be the best case. It's such an awesome tool for it's use. I mean just being able to say I want 3 copies running and it makes sure that's what happens even when things die is awesome.

Obsolesce

I think if SodiumSuite plays their cards right, it has the potential to completely replace Microsoft's system management (like Group Policy and SCCM and others in the suite) as well as the major alternatives, such as Dell's KACE, etc.

stacksofplates

@tim_g said in VPS Open Ports - Thoughts?:

I think if SodiumSuite plays their cards right, it has the potential to completely replace Microsoft's system management (like Group Policy and SCCM and others in the suite) as well as the major alternatives, such as Dell's KACE, etc.

Quest bought KACE and it's gone downhill a bit.

scottalanmiller

@tim_g said in VPS Open Ports - Thoughts?:

I think if SodiumSuite plays their cards right, it has the potential to completely replace Microsoft's system management (like Group Policy and SCCM and others in the suite) as well as the major alternatives, such as Dell's KACE, etc.

That's our thoughts!

Obsolesce

@stacksofplates said in VPS Open Ports - Thoughts?:

@tim_g said in VPS Open Ports - Thoughts?:

I think if SodiumSuite plays their cards right, it has the potential to completely replace Microsoft's system management (like Group Policy and SCCM and others in the suite) as well as the major alternatives, such as Dell's KACE, etc.

Quest bought KACE and it's gone downhill a bit.

Yeah I know, old habit. I even see the new Quest branding every day when I log in to it.

stacksofplates

@tim_g said in VPS Open Ports - Thoughts?:

@stacksofplates said in VPS Open Ports - Thoughts?:

@tim_g said in VPS Open Ports - Thoughts?:

I think if SodiumSuite plays their cards right, it has the potential to completely replace Microsoft's system management (like Group Policy and SCCM and others in the suite) as well as the major alternatives, such as Dell's KACE, etc.

Quest bought KACE and it's gone downhill a bit.

Yeah I know, old habit. I even see the new Quest branding every day when I log in to it.

I don't know how I feel about the new interface. The K logo is weird.