Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel1

...

  • Storing credentials for IPMI Platform Server can now store the IPMI username and password for an externally managed Swarm chassis. By storing these credentials, you do not there is no need to enter them whenever when Platform runs power on/off commands using IPMI over LAN. To use these new options, add Add --ipmiUser and --ipmiPassword to the CLI command 'platform deploy storage' to use these options. See Legacy Platform CLI Commands. (ZINC-627)

Info

Required integrations

This version requires Swarm 10.0 or later, Gateway version 5.4 or later, and SwarmNFS version 2.1 or later, if used.

Known Issues

  • If you Platform is installed Platform without having offline mode enabled, you cannot use offline mode cannot be used for future operations. (ZINC-582)

  • When an X.509 certificate is added via using the Swarm UI (pointed at Platform Server), the newlines are correctly converted to {{\n}} escaped chars for use by Storage, but the escaped chars still display in Swarm UI.(ZINC-581)

Changes in Platform 10.0

This release features these major improvements:

  • Self-service migration from CSN to Platform Server — Direct upgrades from CSN 8.3 are now supported. Swarm 10 now includes tools and documentation for upgrading from CSN 8.3 to the new generation of Platform server. These enable you to extract the live configuration and run-time information from the CSN Platform 8.3.x server and perform a live migration to a Platform 10 server without downtime for your the storage cluster. See Migrating from CSN 8.3.2/wiki/spaces/DOCS/pages/2443827978. (ZINC-433)

  • Offline installation, for sites without Internet access — With this release, Platform Server supports offline usage (for "dark" sites): it can install and run Swarm Storage with no connection to the outside world needed, beyond the usual (such as NTP servers). See Platform Installation. (ZINC-76)

  • Support for multiple subnet architectures — You can now configure Platform Platform can be configured to work across multiple subnets, an architecture in which each subnet uses its own PXE boot server. This is performing by installing Platform Server for the first subnet, then installing additional MaaS rack servers for each additional subnet. These additional rack servers register with the primary Platform Server, which is used for all normal operations. See Setting up Multiple Subnets(ZINC-547)

  • Support both iPXE and gPXE — To broaden support for network booting, Platform allows specifying use of the older network bootloader, gPXE, instead of the newer, default bootloader, iPXE. See Legacy Platform Troubleshooting /wiki/spaces/KBI/pages/2443828226. (ZINC-557)

Info

Required integrations

This version requires Swarm 10.0 or later, Gateway version 5.4 or later, and SwarmNFS version 2.1 or later, if used.

Known Issues

  • Upgrade impact: The new default kernel argument applies to chassis deployed after the upgrade. For existing chassis, you must use Use the existing CLI commands for kernel args existing chassis. (ZINC-478)

  • If you installed Platform without having offline mode enabled, you cannot use offline mode for future operations. (ZINC-582)

  • When an X.509 certificate is added via the Swarm UI (pointed at Platform Server), the newlines are correctly converted to {{\n}} escaped chars for use by Storage, but the escaped chars still display in Swarm UI.(ZINC-581)