SUSE® Manager 3 & SaltStack @ Tyson FoodsCAS91938

Patrick Swartz

Lead Technical Analyst/Linux

Tyson Foods, patrick.swartz@tyson.com

Robert Booth

Solutions Consultant

SaltStack, rbooth@saltstack.com

Agenda• Who are we

• Our companies

• Tyson environment

• Tyson requirements

• Bumps we encountered

• How we overcame them, or plowed through them

• What we ended up with (for now)

• Value Tyson has found in having SUMA with SaltStack integrated

2

3

5

Systems management software for

intelligent automation of enterprise

DevOps, IT operations and Web-

scale infrastructure

Tyson Environment• Multiple Datacenters

• Multiple Server OS flavors (SUSE, RHEL, AIX, Windows)

• VMware infrastructures

• Multiple Teams (Linux Admin, AIX Admin, Windows Admin, SAP App, SAP DB, Others)

• Follow SAP development flow

6

7

Tyson Requirements• Development trees isolation

• Team collaboration

• Code/Configuration standardization

• Command line complexity reduction

• Patch deployments/Audit remediation (Linux and AIX)

• Create an “Automated Level-1” support structure

7

8

Bumps• Vmware template clones

• Non-unique machine-ids, our original clones hadn’t cleared the “/var/lib/dbus/machine-id” file. This caused SUMA to randomly

display different machine information

• Our original migration failed because of multiple machines with the same machine-id

• Early SUMA 3.0 GUI did not display the machine-id

• Incorporating our GIT-Labs environment

• Minion keys and machine-id

• If minion salt keys are deleted (testing, etc.) a new machine-id must be generated for SUMA to add the system again.

• Salt-cloud not supported in SLES

• RHEL support in SUMA 3.0

• In our mixed environment this was a key issue initially (expected resolution by SUSECon2016… ☺ )

• SLES-for-SAP not recognized

• Unrecognized OS flavors prevents SUMA from properly applying keys/repos

8

99

Bumps (cont.)• Salt state file conflicts (top.sls)

• Grains/System Set Manager/Groups/Organizations

• Salt versioning conflicts

• SUSE additions/compatibilities

9

10

How we overcame the bumps• Clear template machine-id !

• Took control of some of the key salt files (top.sls) through GitFS

• Wrote our own salt modules (i.e. recognize SLES-for-SAP )

• Stand up multiple SUMA servers

• Possibly a temporary measure until the command line salt commands can respect/enforce the environment settings

• Salt-cloud (don’t ask)

• Created manual “direct” repos for non-supported distros (RHEL, SLES4SAP)

10

1111

What we ended up with (for now):• Multiple SUMA/Salt-Masters

11

Where we want to end up:

12

13

How do we make this happen?

- Team work! -