Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

New and Changed Features

date_range 17-Nov-23

We have introduced the following new features in APM 3.2.0.

We have introduced the following changed features in APM 3.2.0.

  • The APM utility script is re-factored to use a common Juniper software module that orchestrates and manages Kubernetes workloads through Helm. Helm enables APM to support rolling upgrades and also ensures that workloads update when changes are made to the environment or setup. Additionally, the utility script was adjusted to interact with the Kubernetes cluster from a separate host (jump host) allowing the utility script to manage APM releases across one or more clusters.

  • The APM management micro-service was refactored to enable more safeguards during configuration operations and also to provide an interface that is more consistent with the Junos OS for both configuration and CLI operations.
  • The cluster installation utility (bbecloudsetup), that was previously packaged with APM is now packaged and distributed separately.

  • The svc-logs feature is replaced by the Broadband Edge Event Collection and Visualization application.

  • The utility script aligns the defaults it uses during setup with the Kubernetes cluster dimensions established by the bbecloudsetup 2.0.0 script. If the Broadband Edge Event Collection and Visualization is installed before APM, the setup uses defaults to export logs to it.

  • Support for rolling upgrades is added.

footer-navigation