Cluster automated delete request now has reason displayed
Admin users now can see Impersonated By on resource provision and destroy records
Users can now use a custom subdomain when creating a session
The command pw kube ls is now available to list available kubernetes clusters. In addition to basic listing, it also supports output format flags -o json and -o table.
You can now manually create sessions of the "link" type. Link sessions are simply links to other applications or services from within the platform. In the past, a workflow would've created these in case a session is managed outside of the ACTIVATE platform.
Added more details to cluster provision status records. You can now click on individual provision status lines to see more details.
When attempting to shut down a cluster you will now be given the option to stop the controller. While stopped, costs will be reduced to only the cluster's storage. When you try to start a stopped cluster, you will be prompted to restart the cluster.
Auto Reconnect option has been added to existing cluster options. If enabled we will try to automatically connect to the remote vm. You must first connect manually by pressing the power button.
Workflows now have a password field which can be used by workflow developers to hide text as its being entered.
If a cluster fails to provision, a red banner will be shown at the top of the page indicating that the cluster should be destroyed.
You can now cancel a workflow run and view running sessions from a workflow's Run page
We now show the required disk size you will need to use an image in the image selection dropdown.
You can now create snapshots from disks that were configured inline in the cluster configuration page. You may do so from the clusters "Sessions" page in the attached storages table.
You can now see CPU usage, Memory Usage, and Storage usage for kubernetes workloads (statefulsets, deployments, etc). These are viewable from the workload pages. These metrics show combined usage for all pods managed by that resource. We will have individual pod metrics in an upcoming release.
Platform administrators will now receive an alert whenever the platform detects that a resource deletion might not have been processed correctly.
You can now edit Kubernetes resources by modifying them directly on the YAML editor.
You can now provision and chat with OpenAI models on Azure. To enable this feature preview, use the feature preview menu.
Cloud clusters will now have CPU, Memory, and Root Disk charts at the top of the cluster details page.
In addition to keyboard-interactive, the existing cluster provider can now support older password ssh connections
Kubernetes workload pages now use a more readable format to show relevant information.
You can now receive runtime alerts for storage. You may choose to turn on/off runtime alert in storage's properties tab. This will send you a notification after your storage has been running longer than the interval specified. You can configure if you receive the notifications via the platform inbox or via email through your account settings.
Admins can now set the latest image directly from the admin panel
Users can now update cluster bootstrap script and its toggles (controller/compute) while cluster is running
Organizations can now add kubernetes clusters and share them with specific groups. Users in those groups will be able to use the pw CLI to add a context to their local kubeconfig, allowing users to run kubectl commands. Kubernetes resources are now visible in the platform for users that have access to the cluster.
You can now snapshot AWS root disks and then boot your cluster using that snapshot.
OS Snapshots are now a generally available feature. You can create a snapshot by going to your cluster, and selecting create snapshot next to the root disk. After doing so, you can choose that snapshot as the image to use when starting a cluster. This is a direct replacement for the old scripted method of creating OS images via the account settings page. We will be removing that method of creating snapshots in an upcoming release.
You can now set descriptions on Capacity Reservations
You can now manually create sessions without having to start a workflow. Try this out by clicking the Add session button on the Sessions page.
You can now specify custom NFS mounts via the cluster configuration form. This applies to cloud clusters and OpenStack clusters.
Use Load Balancer as Nat Gateway option has been added to azure infrastructures. This will make it so a load balancer is created with each cluster and all egress traffic from partitions will go through the load balancer allowing tracking of egress cost.
The Azure ML Workspace feature preview has been made publicly available. To try this feature out, enable it from the feature preview section.
Capacity reservations are now supported on Azure and Google Cloud. Organization administrators can now specify which CSP the capacity reservation is for when adding the capacity reservation. On the cluster edit form, the input field for capacity reservations has been changed to a dropdown.
We now support managing NetApp ONTAP volumes directly from the ACTIVATE platform. These volumes can also be mounted to OpenStack clusters which have network access to the NFS exports provided by the ONTAP service.
You can now see which cluster a session is targeting from the Sessions widget and from the Sessions page.
Storage items now appear in the platform search
The admin panel platform image list now shows the CSP's unique identifier for the image.
Organizations can now reset the organization-wide default sidebar settings to the platform defaults by using the radio button available on the user defaults page.
You can now search the platform and documentation via a new search bar at the top of the UI. Open this with cmd + k on Mac OS or ctrl + k on Windows.
Use Controllers as NAT Gateways option has been added on AWS/Google infrastructure configurations. Enabling this option will make it so all traffic from compute nodes are proxied through the controller. All compute nodes will share the same IP as the controller node. This will enable tracking egress costs from compute nodes.
You can now provision public IP addresses on Azure independently of other compute resources. After provisioning a public IP it can then be assigned to a compute cluster controller node.
Improved provisioning status logs shown when creating an AI Chat resource
Organizations can now define a default sidebar for new users. Users that have not customized their sidebar will automatically use the organization's default settings. If the organization does not specify a customized sidebar then all sidebar items will be visible by default.
Adds an optional DNS service to platform deployments which can resolve slurm cluster hostnames if needed
Added Cost Alert notification type and user preferences.
Added cluster cost estimation for openstack
Platform administrators can now toggle Debug Mode in cluster Advanced Settings section.
When turned on, users can ssh into the node without waiting for it to be ready using ssh root@<nodeip>. Can be done from the user workspace or user's personal computer (if public key is added in the platform). Node clean up will not happen if there is any error in provisioning.
Realtime now processes openstack data.
You can now edit widget names on home page. Click Customize and you will now see an edit icon next to the widgets name.
Sessions that were created by workflows will now show the workflow icon next to the session
The resource monitor module has been removed from the front page. In order to not disturb saved layouts you will need to manually remove the module where the resource monitor was previously.
You can now edit the workflow home page widget to change which workflow type to show. The default home page widgets have been updated to include the Favorite Apps and the Sessions widgets. Users that have modified their home page will not receive the new layout, and can instead add these widgets by choosing "Customize" from the top right of the home page.
pw nfs ls command to the cli
pw cluster attach-storage command to the cli
nfs ls and cluster attach-storage commandsYou can now use the new pw nfs ls and pw cluster attach-storage commands from an authenticated cluster session.
Sessions are now available as a home page module which can be added using the customize button on the home page.
Users can now customize the items that appear on their sidebar. In a future update, organizations will also be able to customize the default sidebars for users in their organization.
Can now provision Azure OpenAI resources from within the platform and directly chat via the UI.
Apps and sessions are now generally available.
Apps provide a layer on top of workflows which make additional interfaces available for workflow developers to make interactive experiences easier. Sessions expose ports on compute resources to the browser so users can run interactive apps on their computing resources and access them directly via ACTIVATE.
Read our documentation for apps and sessions to learn more.
On a session's page, current running workflow steps will be shown while the session is pending.
We've updated the default layout of the home page. If you have not customized your home page, you will automatically be moved to the new default layout which shows:
To customize your layout, use the customize button at the top right of the home page. Note that users with a custom layout are not affected by this change.
Platform level slurm cluster images can be managed through the admin panel.
You can now set default session names on workflows:
session:
mySession:
prompt-for-name:
default: "defaultname"
Allows setting environment variables on a job level. Environment variables set at a step level will override the environment variables set at a job level.
jobs:
main:
env:
foo: "bar"
steps:
- run: echo ${foo} # bar
- run: echo ${foo} # baz
env:
foo: "baz" # will override env variable set on job level
Stopping a session will now also stop the workflow run that started the session and any sessions associated with the workflow run.
Logs and input validation for updating session has been improved.
if being falseclient_secret_basic token endpoint auth methodThere is now a dropdown on the OIDC auth method to allow choosing either client_secret_basic or client_secret_post. These auth methods are used for the platform to authenticate to the token endpoint after a successful OIDC user authentication.
Scopes can now be specified when adding or updating an OIDC auth method in organization settings.
View logs button to see the details of what happened.OIDC endpoints can now be manually provided instead of using the issuer to discover them. This makes the OIDC authentication method more flexible for cases where applications do not have a proper well-known endpoint or the well-known endpoint is behind a firewall but the other endpoints are not.
This update also has slight visual enhancements to the auth method page, with the "configure" button being changed to a link.
The new provisioning experience is live for Azure NetApp files.
Adds an input box when attaching filesystems only for Hammerspace. This input allows users to define the export path the cluster will use to mount the hammerspace file share from.
You can now specify remoteHost and slug when updating a session.
- uses: parallelworks/update-session
with:
slug: 'string' // (optional) appends this slug to the session url
remoteHost: 'string' // (optional) host to forward session to from the target, defaults to "localhost"
... other inputs
You can now also specify if the session will use TLS.
sessions:
mySession:
useTLS: true // (optional) Will use https when connecting to session, should only be turned on if the app requires https.
Changes the Hammerspace provision status UI to only show the main components getting created, Anvil, DSX, DataNodes. Also adds deletion statuses.
When a resource supports the new provisioning experience, you will now see the deletion records directly below the provisioning records in the provisioning status panel.
When provisioning Azure storage accounts, if a name was unavailable the provisioning would silently fail. You will now receive an error that the name is already in use in these cases. This update also fixes other minor issues and typographical problems with the new provisioning UI.
Failed nodes are now also returned in cluster data. This is useful for workflow that need to know nodes provision status to make decision instead of waiting for slurm to time out
The new provisioning experience is now generally available for our next-generation cloud clusters and most cloud storage options.
Next-generation cloud clusters are now generally available. With this update, previous generation clusters will be marked with the text "Legacy".
Workspace mount points now have tooltips for substitutions
Added inputs on Hammerspace configuration form that show up when selecting UltraSSD_LRS disks. These options are for configuring the IOPS and Mbps Throughput for all disks within the Hammerspace deployment.
All users can now enable the "apps" feature preview from the feature preview menu.
Adds a summary box above the workflow dependency graph
Can use PW_API_KEY environment variable with tokens to authenticate
Adds a command pw auth identify-platform to the CLI to help identify which platform host the CLI is configured to run commands against.
Make nodes provisioning more stable for azure
Introduced a new structure for the changelogs, where changes are categorized into three sections: Enhancements and Features, Bug Fixes, and Other Changes.