On Monday Solace released SolOS Version 7.2.2 for our hardware appliances. This release doubles the number of topics that can be stored by PubSub+ Cache, doubles the number of access control list (ACL) rules that can be configured on the appliance, and enhances dead-message-queue (DMQ) functionality so that any queue on the router can now be designated as a DMQ.
But that great stuff isn’t even the biggest news about the release. What we’re really excited about is the introduction of version 2 of Solace Element Management Protocol, aka SEMPv2. With SolOS Version 7.2.2 we’ve brought you the SEMP v2 objects you will need to perform the most common day-to-day message VPN configuration tasks on your routers. It’s our very first release, so we have a few more VPN level objects that we still need to implement, but those remaining objects will be coming soon. And we aren’t stopping there, subsequent SolOS releases will allow you to monitor the router using SEMPv2 and even complete the initial one-time commissioning operations that you go through when installing an appliance.
SEMPv2 is RESTful and object-oriented, with a cleanly structured schema. That makes it easy for you to programmatically apply configuration to your router either through tools and portals you develop yourself, or by integrating with common configuration automation tools like Chef, or Puppet, or Ansible (to name just a few). The entire protocol was defined using Swagger, so you don’t need to become a SEMPv2 guru to build your management system – you can use the Swagger definitions to auto-generate an API in whatever programming language you want to use.
Ready to get going with SEMP v2? We’ve published some SEMP tutorials that will help you get started quickly, and we’ve also got material to introduce you to both the SEMP Concepts and the entire SEMP API reference.