Puppet Integration with Device42
- Foreman Smart Proxy
- Jira Cloud
- Jira Service Management
- Microsoft LAPS
- Microsoft SCCM
- ServiceNow Express
- VMWare VRealize
- Node Name
- Node Type
- Virtual or Physical
- Virtual Subtype
- Operating System and Version
- CPU Count (Physical)
- CPU Core Count
- CPU Power
- Memory Details (RAM)
- HDD Count
- HDD Size
- Puppet node ID (if Puppetmaster)
- MAC Address
- Service Level
Leverage Device42 as a Puppet ENC (External Node Classifier) for Two Way Data Sync!
Control your Puppet node’s classifications right within Device42.
Device42 itself can also be leveraged as a Puppet ENC (external node classifier). Teaming ENC’s with the Device42-Puppet integration, you can now both populate Device42 with data from your Puppet master and at the same time control node classifications with the Puppet ENC Integration from Device42!
With Device42 & Puppet, you’ll never miss a beat — Any changes that are made to your infrastructure are reflected immediately within Device42, and any changes to node classifications are pushed back out to Puppet!
Each time Puppet performs a configuration task on its nodes, Puppet will also check for and apply the relevant classification as stored by the Device42 ENC custom field. Device42 can also be configured to sync any changes that were made by Puppet to the CIs as part of that job.
Visualizations are spot on, reports are accurate, and inventory counts are always up-to-date. With Puppet & Device42, this can be an easily achieved reality. You’ll impress your boss … and your boss’s boss!
Visualize Details of Your Puppet’s Configurations With Custom Fields in Device42!
Device42 is the go-to source for up-to-date details about your entire deployment.
Are there specific or custom CI details you want to keep track of? No problem! Create one or more custom fields in Device42, and map the content of any string and/or count array field over to them using your integration’s setting.yaml file. If it’s in your Puppet master’s .yaml file, you can see it in Device42. For more details on custom fields in Puppet, check out our Puppet Integration: Extended Custom CI Attributes blog post.
Once the initial sync has been performed, you can get details about almost any device your Puppet Master controls, including the Puppet master itself, from Device42. A few clicks or a quick search by name is all it takes, and you’ll have all the details – deployment date, date last updated, CPU, Memory, Network, OS, Software and Services … the list goes on.
Need to quickly see how many web servers you’ve deployed with a puppet? Simply search for httpd, the apache service, and in seconds, view all the instances that are running that particular web server. Narrow it further by version, if necessary, and easily produce a shortlist of machines in need of updates. With Puppet & Device42, your toolbox just got a lot more useful.
Understand Your Deployment’s Interdependencies with Device42!
Quickly and easily view the details of your deployment, connections, and interdependencies.
You put in the hours capturing the inner workings and subtle nuances of your infrastructure in code. Now everything appears as though it’s working as expected … but how can you easily show management the breadth of the accomplishment?
Visualize the entirety – or a subset – of your deployment right in Device42, and be sure everything looks exactly as you’d expect. Ensure the right number of server instances are exposing the right services on the right IP’s. See your physical, cloud, or hybrid layout and all of your infrastructure’s dependency details any time.
Eliminate Disconnects between DevOps & Security.
Remediate Faster, and Let Device42 Generate On-Demand Compliance Reports!
Locate and remediate vulnerabilities across your infrastructure faster with Device42 & Puppet. You can quickly query Device42 for a list of servers running vulnerable software, and Puppet can take care of removing or updating the vulnerable build.
Showing your security team that remediations are complete is as easy as running an on demand report in Device42 – or, schedule the report. Simply specify the security team’s inbox and let Device42 handle communicating the rest.