New Features

This article presents the new features in App Workbench 4.0:

  • Support Document Template: The new support document template provides the user with both overview and detailed information for an App Store application when the Documentation link is clicked. Developers may use this template to provide the following kinds of information:

    • Application details.
    • Test cases to perform after creating a cluster with the application.
    • More example/sample links for users to try.
    • Detailed requirements/prerequisites.

    • Release Notes.

  • The Overview section presents a high-level application information. The Details section presents the following additional information:
    • Details
    • Application Image Details
    • AppName
    • DistroId
    • Version
    • Cluster Type
    • Software Included
    • Kibana Access
    • Elasticsearch Access
    • Systemctl service names and commands
    • OS
    • Testcases
    • Prerequisites
    • Release notes
  • Support for load-balanced services: Service endpoints may be marked for EPIC to configure a load balancer when deploying virtual clusters.
  • Simplified AWB installation: All Python dependencies have been prepackaged in a virtual environment.
  • Define AI/ML categories: Application developers can use predefined AI/ML categories that control where the application appears in the project App Store screen.
  • Minimize catalog JSON requirement: App Workbench 4.0 improves the app development workflow with commands that provide direct control over JSON file contents.
  • Support for attachable clusters: EPC 4.0 introduces "attachable" clusters for AI/ML projects. App Workbench 4.0 supports developing apps that include this feature.
  • Support authorization tokens in service endpoints: App developers can specify that a service should have an authorization token endpoint.
  • Faster app build speed: If a container image has not changed since the last build, then App Workbench will use the previously-staged container file to speed up the build process.
  • Ignore invalid image metadata: App Workbench 4.0 disregards invalid image metadata and correctly uses new repotags specified by the developer.
  • Allow auto-code generation in various lifecycle config scripts: Auto code generation was previously only supported during the creation portion of the cluster lifecycle. This support is now extended to other phases, such as cluster expansion and deletion.
  • Support for additional Docker build options: Developers may now specify additional Docker build options when building container images, such as --no-cache.
  • API to be invoked when deleting a cluster: A --delete API can be specified that will be invoked on all containers prior to deletion, so that the application can perform any necessary clean-up.

x