Originally I created this post with only 2 updated and one new fling. Some engineers though added two more new flings so 3 new ones and 2 have received an update. The new ones are the Distributed Trust Incident Reporting fling, vRealize Build Tools and Cloud Automation Services SDK for Python. while the Horizon Toolbox and Horizon Migration Tool have received updates.
[sta_anchor id=”vrealizebuildtools” /]
vRealize Build Tools
vRealize Build Tools provides tools to development and release teams implementing solutions based on vRealize Automation (vRA) and vRealize Orchestrator (vRO). The solution targets Virtual Infrastructure Administrators and Solution Developers working in parallel on multiple vRealize-based projects who want to use standard DevOps practices.
This Fling is focused on code quality, code reusability, unit testing, dependency management and parallel releases of vRealize projects. In practice, it is a set of Maven extensions, packaged in a Maven repository format, that support the use of IDE (via Maven) and CLI to develop, test and deliver vRA and vRO-based solutions. It includes a vRO plug-in that exposes autocomplete information for standard and third-party scripting objects and actions and CLI that can deploy packages to vRO and vRA via the standard APIs.
[sta_anchor id=”cassdkpyth” /]
Cloud Automation Services SDK for Python
The Cloud Automation Services SDK for Python is a set of Python classes to simplify automation against several aspects of the Cloud Assembly, Service Broker, and Code Stream API when using Python.
Note: The github repo will be public soon!
[sta_anchor id=”dtir” /]
Distributed Trust Incident Reporting
The Distributed Trust Incident Reporting fling is an open source security incident tracker.
Security incidents are important to track so that all parties know the status of a breach and can respond in concert and with appropriate speed. Current methods to track incidents are generally paper-based manual processes. More recent systems are based on a centralized database with some web interface to interact with the record and response tracking.
We propose that this does not work well enough in the scenarios where:
- security incidents may affect more than a single entity
- where more than one entity must respond to an incident
- some or all entities have no trust in the others
- no party can or will be responsible for hosting the full system
For example, a security breach in the supply chain for a food manufacturer could result in several retail businesses with products on shelf that contain a pathogen. Current methods of notifying the proper authorities require a phone tree to call all the correct parties which then react as individuals or local committees. In addition the incident must either be initially submitted to each entity separately or one entity must take responsibility to notify the others.
- allows all parties (e.g. retail, governmental, public) to see the incident via a single report transaction
- allows all parties to respond in concert as required
- allows automated systems to report incidents
- allows transparency across all organizations
[sta_anchor id=”horizontoolbox” /]
The Horizon toolbox is an extension to the Horizon Admin Console giving all kinds of user and session information. It is no replacement for the Horizon Helpdesk (or the fling).
May 28, 2019, 7.8.0
- Fix some incompatible issues
- Only support Horizon View 7.7 & 7.8
[sta_anchor id=”horizonmigtool” /]
Horizon Migration Tool
The Horizon Migration Tool helps you migrating from Citrix to an On-Prem Horizon Environment.
- Updated the binary package and the document accordingly