CentOS 6 no longer supported for Mu Master installations
Maintenance updates of CentOS 6 ceased November 30th, 2020. Update repositories and EPEL have been shut down. As such, this platform is effectively not installable.
CentOS 7 is now the preferred platform for Mu Master installations. Standard official machine images of CentOS 7 should work on all cloud providers.
Chef updates
Mu Masters now run Chef Server 14.0.65-1
. This release appears to eliminate Chef's internal use of rabbitmq, which was the culprit in many stability issues. https://github.com/chef/chef-server/blob/master/CHANGELOG.md#14065-2020-10-26
The default Chef Client version is now 16.9.29
. https://docs.chef.io/release_notes_client/
Master Master enhancements
New installations will now attempt to provision a separate /opt
disk for Mu, Chef, Ruby, Python, and other assorted support packages. The install process now delays installation of alternative cloud provider SDKs until this is available,, to relieve disk pressure on small machine images. This functionality is tested on AWS and GCP-hosted masters.
Apache 2.4 configuration for locally-generated documentation should be significantly more reliable.
NVME disks are now properly handled by mu_tools_disk
, which will embed requested device names in disk metadata on creation and dynamically map between those and the real, kernel-generated device paths.
We now package our own Python 3.8.3, used by bundled SDKs for Azure, AWS, and Google. Available under /opt/pythons/Python-3.8.3
.
Also shipping Git 2.30.0 in /opt/git/git-2.30.0
, so that Bundler won't complain.
Packaged Ruby version is now 2.7.2, available in /opt/rubies/ruby-2.7.2
.
The mu-tools
cookbook now uses the AWS Ruby SDK v3 (from v2).
mu-configure
should do a better job of detecting public IP addresses assigned by the cloud provider.
Google::Function
Regrooms will now update Cloud Functions with altered function code.
The code
block now supports the path
method, in addition to zip_file
or gs_url
.
Azure
Use KeyVault to store deploy secrets so that Windows instances can use them to configure WinRM in the future.
Improve detection of non-functional regions returned by the list_locations
API call, and excise them from our own internal list.
Transient API errors should be less noisy.
Bugfixes
Google::VPC
: Covered all cases of intra-subnet naming for lookupAWS::VPC
: properly initialize@region
,@credentials
, etc; tag EIPs used for NAT gateways so we can properly deallocate them later- Use
URI.open
to quiet deprecation warnings AWS::Server
: Guard some rare transient API responsesmu-configure
: Callgethostbyaddr
correctly, which we apparently haven't been for a long time- Each major provider seems to have an edge case where invalid beta regions can appear in API call results, while breaking others. There are now filters to catch many of these cases.