We work with these Technologies + Partners
This is the first in what we hope to continue as a brief weekly update on the progress of the SIMP Project.
Our test automation framework is moving forward. We discovered that the Jenkins 2.0 Alpha release has a lot of the features that we’ve been looking for so we’ve started incorporating it into our workflow. We’re hoping that this paves the way toward a testing infrastructure that we can completely share in an easily repeatable manner.
We’re working on a new SIMP Project website which will be deployed at http://www.simp-project.com when complete.
Though this was completed last week, the augeasproviders_grub provider was patched with a lot of new features for more effective management of both GRUB Legacy and GRUB 2 environments. Acceptance tests were added via Beaker.
While debugging some NFS issues, we realized that not all sysctl values will be present on the system at the time that Puppet is executing. As such, we’ve updated the augeasproviders_sysctl module to have a :silent parameter. This parameter allows you to ignore failures in setting a live sysctl value at run time with the expectation that, at some point, the module will be loaded on the fly. This functionality really should be rarely used but is necessary in some cases.
The svckill module has been updated to output all results into the resource string if system resources are modified. This means that the full report is now available via PuppetDB for analysis over time. Additionally, a :verbose parameter was added to the system to allow for a more terse output message if you just want statistics.
The simp-rake-helpers rubygem was updated to incorporate all of the main Rake tasks from simp-core.
Our new module, simp-compliance_markup, used for ensuring that values in your classes and defined types do not deviate from expected compliance standards has been incorporated. A new blog post will be posted in the near future describing the benefit that this brings to the SIMP ecosystem.
For a full view of what we’ve been working on, take a look at our JIRA issues for the week.
Trevor has worked in a variety of IT fields over the last
decade, including systems engineering, operating system
automation, security engineering, and various levels of
development.
At OP his responsibilities include maintaining overall
technical oversight for Onyx Point solutions, providing
technical leadership and mentorship to the DevOps teams. He is
also responsible for leading OP’s solutions and intellectual
property development efforts, setting the technical focus of
the company, and managing OP products and related services. In
this regard, he oversees product development and delivery as
well as developing the strategic roadmap for OP’s product line.
At Onyx Point, our engineers focus on Security, System Administration, Automation, Dataflow, and DevOps consulting for government and commercial clients. We offer professional services for Puppet, RedHat, SIMP, NiFi, GitLab, and the other solutions in place that keep your systems running securely and efficiently. We offer Open Source Software support and Engineering and Consulting services through GSA IT Schedule 70. As Open Source contributors and advocates, we encourage the use of FOSS products in Government as part of an overarching IT Efficiencies plan to reduce ongoing IT expenditures attributed to software licensing. Our support and contributions to Open Source, are just one of our many guiding principles