Mission Control 2.1.1
January 23, 2018
Highlights
Helm Chart Repositories
This release adds full support in Mission Control for Helm Chart repositories which were introduced in JFrog Artifactory 5.8.
Mission Control 2.0
November 20, 2017
JFrog is pleased to release Mission Control 2.0.
This release introduces many changes from version 1.x to improve workflow and efficiency in managing your global Artifactory and Xray services. Yes, you read correctly, Mission Control now also manages your Xray services. In addition, Mission Control 2.0 introduces significant changes in installation and upgrade procedure, workflow for adding and managing services, a new concept of Sites that associate services to a geographic location, improvements in Usage Graphs and more.
Note that some of the new features and enhancements are breaking changes that are not compatible with version 1.x. In these cases, we offer a migration path to version 2.0.
For details about the changes introduced by Mission Control 2.0, please read the sections below.
Highlights
Artifactory and Xray Services
In addition to managing your Enterprise Artifactory instances, Mission Control can now also manage the JFrog Xray instances attached to them. This allows you to do things like configure connections between Artifactory and Xray services, use scripts to create Watches and more.
To manage Artifactory or Xray instances through Mission Control, they must be added as Services and be assigned to Sites.
Scripting
Scripting has undergone significant changes in Mission Control 2.0. Most importantly, configuration scripts are now much more flexible allowing you to operate on as many Artifactory or Xray services, and on any number of repositories as you want in a single script (previously, each script could only perform one action on a single service). To support this capability, Mission Control 2.0 introduces service closures in configuration scripts. These define the Artifactory and Xray instances on which the script operates and enclose the different configuration blocks that create or implement changes on Artifactory and Xray services.
The scripting DSL has also been significantly enhanced with new configuration blocks. These include configuration blocks to create and configure Xray services, a security block to configure users, groups and permissions in Artifactory services and more. Make sure to check out the Star Topology configuration blocks that make it very easy to set up a complex one-to-many replication relationship using three lines of code. Not also that applying a Star Topology configuration to all members of a star actually implements a full mesh topology.
Graphs
The Graphs UI has been enhanced to give you an easy way to focus on different Artifactory instances and repositories and also zoom in on specific time periods on historical usage graphs. From version 2.0, Mission Control uses a new Elasticsearch database to store historical usage data. Upon installation of the new version, the previous InfluxDB database will no longer be used, and usage data will only be collected in the new database.
Installation and Upgrade
Instructions for installing and upgrading to version 2.0 have changed, but remain simple procedures, with support for CentOS, Debian and Docker installations.
To install Mission Control 2.0 as CentOS or Debian distribution, please refer to Installing Mission Control.
To install and run the Mission Control Docker image, please refer to Running with Docker.
REST API
Mission Control 2.0 introduces a completely new REST API that accommodates all the new functionality introduced in this version. The new REST API adds several new endpoints, but also removes some, including endpoints related to configuring users, groups and permissions in Artifactory since this functionality is now available through JFMC scripting. From Mission Control 2.0, the REST API v3 is active, while the REST API v2 is deprecated.
Sites
Sites are a new concept in JFrog Mission Control. They represent physical locations (cities) into which you can aggregate the different Artifactory and Xray services serving them. Any service defined in Mission Control must be assigned to a site. Sites are displayed in the Explore module (which replaces the old Dashboard module) and can display sites as a list view or on a map.
Feature Enhancements
- Mission Control startup time has been greatly improved.
- Mission Control's DSL has been enhanced with new configuration blocks to allow extremely easy configuration of replication relationships that implement Star Topologies for geographically distant Artifactory services. starPush configures a multi-push replication relationship while starPull configures pull replication. As a result, the multipushReplication configuration block, which is now redundant, has been deprecated.
- The Execute Script REST API endpoint has been enhanced to provide more detailed error messages if script execution fails
Issues Resolved
- Fixed an issue that prevented Mission Control from implementing DR when the Master Artifactory instance was using encrypted passwords.