OneCompute Release Notes
Known issues
Release history
- Version 5.4 - May 19, 2022
- Version 5.3 - April 21, 2022
- Version 5.2 - March 17, 2022
- Version 5.1 - February 17, 2022
- Version 5.0 - January 20, 2022
- Version 4.6 - December 16, 2021
- Version 4.5 - November 18, 2021
- Version 4.4 - October 25, 2021
- Version 4.3 - September 29, 2021
- Version 4.2 - August 18, 2021
- Version 4.1 - April 28, 2021
- Version 4.0 - February 20, 2021
- Version 3.1 - September 25, 2020
- Version 3.0 - April 1, 2020
- Version 2.2.2 - November 24, 2019
- Version 2.2.1 - October 14, 2019
- Version 2.2 - July 12, 2019
- Version 2.1 - April 30, 2019
- Version 2.0 - February 13, 2019
- Version 1.2.2 - June 30, 2018
- Version 1.2.1 - April 5, 2018
- Version 1.2 - March 30, 2018
- Version 1.1.1 - February 5, 2018
- Version 1.1 - November 22, 2017
Version 5.4 - May 19, 2022
The 5.4 release of OneCompute focused on bugfixes, tech debt and performance improvements.
Enhancements
- Reintroduce logging of the ContainerUrl in a redacted form in the file transfer service
- Improve loading performance of Portal Home page - Part 2
- Upgrade platform services to .NET 6 - Part 3
- In Azure Batch WorkerHost, refactor Result Lake client factory handling to cater for SWiM needs
- Have multiple SRI hashes for JS/CSS dependencies, for improved browser support
- Quarterly JavaScript/CSS updates May 2022
- Monthly NuGet updates May 2022
- Consider using a "JsonSerializer.SerializationBinder" when deserializing, to satisfy SAST tool
Defects
- Application package upload based on Azure DevOps build artifact fails
- Filetransfer fails if subfolder is more than 200 characters on Linux
- Fix missing trace messages in Application Insights for JobScheduler and BackgroundWoker
- Azure Batch worker host unable to handle telemetry client configuration if instrumentation key is missing
Version 5.3 - April 21, 2022
The 5.3 release of OneCompute focused on bugfixes, security enhancements and upgrades to .NET 6 runtime.
Enhancements
- Update «moment» JavaScript library from 2.29.1 to 2.29.2 to fix security vulnerability reported by Snyk
- Improve loading performance of Portal Home page - Part 1
- Upgrade platform services to .NET 6 - Part 2 (the web API)
- Investigate whether we need to safe-guard against the "node-ipc" npm package situation ("peacenotwar")
Defects
- User jobs are not listed in My Jobs
- Remove logging of long-lived SAS token in BLOB container URLs in file transfer service
Version 5.2 - March 17, 2022
The 5.2 release of OneCompute focused on bugfixes and security enhancements.
Enhancements
- Should update client-side libraries to latest version
- Upgrade "bootstrap" library used in portal to improve Snyk web test score from "D"
- Update to latest OneDesign 2.8.1
Defects
- Credits for a Job not counted after 7 days
Version 5.1 - February 17, 2022
The 5.1 release of OneCompute focused on minor bugfixes.
Enhancements
- Various HTML issues are reported by Edge browser - Part 1
Defects
- Work items with more than 24 hours' duration only displays the time info for the last day
Version 5.0 - January 20, 2022
The 5.0 release of OneCompute focused on code cleanup and getting the platform ready for the migration to OneGateway, which will be done as soon as the infrastructure is ready.
The old, regional API endpoints (used prior to the 4.0 release) are now officially deprecated.
Version 4.6 - December 16, 2021
The 4.6 release of OneCompute focused on security updates and code refactoring.
Version 4.5 - November 18, 2021
The 4.5 release of OneCompute focused on minor bugfixes.
Enhancements
- Setup East US 2 deployment
Defects
- Report generation fails when user has only User role and with account which has no tag
- Connection string caching fails to provide fallbacks for non-set environment ID
- Create Linux Pool does not create pool supporting containers
- Getting job properties through platform client yields only minimum date for "CreationTimestamp" property
- Add Tag failed in My Jobs page
Version 4.4 - October 25, 2021
The 4.4 release of OneCompute focused on Kubernetes backend, improvements to the portal and minor bugfixes.
Enhancements
- Add default version of an application to a pool
- Backend services running on Kubernetes
- Filter jobs by environment or application on Jobs page
- Improve deletion experience
- Show tags in the "Compute: Credits per job" report
Defects
- Job deletion SignalR is sometimes unstable
- Application list is not correct for User role
- File upload from cloud nodes sometimes fails length part of validation
Version 4.3.1 - September 29, 2021
The 4.3(.1) release of OneCompute focused on improvements to the portal and minor bugfixes.
Enhancements
Defects
- JobScheduler does not remove the job orchestrator when the job terminates
- Correct title not shown when browsing to subfolder
- Accounting reports for all accounts time out
- Application - Delete: Error Message is not correct when user has no access to delete
- My Storage page shows incorrect Summary Size information
- Other internal bugfixes
Version 4.2.1 - August 18, 2021
The 4.2(.1) release of OneCompute focused on:
- Improvements to the portal and minor bugfixes
- Re-branding from "DNV GL" to "DNV"
As part of the re-branding, all portal endpoints have changed:
- https://onecompute.dnv.com: Global portal endpoint for the production deployment
- https://develop.onecompute.dnv.com: Global portal endpoint for the client application development deployment
- https://test.onecompute.dnv.com: Global portal endpoint for the client application test deployment
The new global API endpoints are:
- https://onecompute.dnv.com/api: Global API endpoint for the production deployment
- https://develop.onecompute.dnv.com/api: Global API endpoint for the client application development deployment
- https://test.onecompute.dnv.com/api: Global API endpoint for the client application test deployment
The old, regional API endpoints (used prior to the 4.0 release) are kept for compatibility reasons for some time still. The old "@dnvgl.com" endpoints are kept for compatibility reasons for some time still.
Enhancements
- Job and workspace tags
- Provide API to access usage data
- Improve accounting report with field filtering
- Refactoring of multiple batch account handling
- Updating applicable Azure related NuGet packages from SDK v11 "Microsoft.Azure." to SDK v12 "Azure."
Defects
- Newlines in 'notify users' text field are not taken into account in actual email
- No Batch account info in NodeCount, Scale, Restart, Reimage page in Operations
- Missing Batch account name in pool views
- Application access selection shows only 5 rows by default, even though it claims to show 10
- GetJobProperties times out occasionally
- Mixed content error - scripts are requested over HTTP rather than HTTPS
- JS errors on Users' Edit page when run on Linux image in Kubernetes
- Job Details page violates the Content Security Policy
- Missing UI feedback for a Delete Job operation
- Batch account selector doesn't reflect active environment
Version 4.1 - April 28, 2021
The 4.1 release of OneCompute was a minor servicing release of the OneCompute platform with no package updates. Its main purpose was to add support for the new authentication scheme introduced by Veracity in April 2021 to the OneCompute platform API and portal before the old authentication scheme is deprecated on July 1, 2021.
Version 4.0 - February 20, 2021
The 4.0 release of OneCompute focused on:
- Supporting multiple Batch accounts
- Globalization: Integrating the regional deployments into a single, global OneCompute
- Security enhancements
- Audit logging
- Worker communication and control
- Support for .NET 5.0-based workers
OneCompute 4.0 introduces a new concept, the environment. An environment contains the resources needed to execute jobs. Users are assigned a home environment, which corresponds to the region in which they run their jobs and store their files. The home environment of a user can be set through the OneCompute portal by a User Manager. Currently, the develop, test and prod deployments of OneCompute are set up with three environments:
- West Europe
- North Europe
- East US
What previously were three separate deployments of OneCompute have in version 4.0 been converted to environments.
The regional deployments of OneCompute are kept, but they are pooled behind common endpoints:
- https://onecompute.dnvgl.com: Global portal endpoint for the production deployment
- https://develop.onecompute.dnvgl.com: Global portal endpoint for the client application development deployment
- https://test.onecompute.dnvgl.com: Global portal endpoint for the client application test deployment
The new global API endpoints are:
- https://onecompute.dnvgl.com/api: Global API endpoint for the production deployment
- https://develop.onecompute.dnvgl.com/api: Global API endpoint for the client application development deployment
- https://test.onecompute.dnvgl.com/api: Global API endpoint for the client application test deployment
The old, regional API endpoints are kept for compatibility reasons.
Enhancements
- Support multiple Batch accounts (ADO#69264,171934,171933,172912,172914,177692,187727)
- Add .NET 5.0 to the target platforms of WorkerHost.AzureBatch (ADO#242624,242625)
- The Users views must list applications in all Batch accounts (ADO#187727)
- Show the user's home environment on the Home page (ADO#240898)
- Add an environment column to the jobs lists (ADO#240900)
- User Managers should be able to set home environment of users (ADO#186853)
- Assign home environment of a user (ADO#174096)
- Logging of user changes to the audit log (ADO#214645)
- OC does not block job input file upload while user has no storage/credits/access (ADO#151269)
- Add method to retrieve properties for all jobs of the user (ADO#249563)
- Misc. security enhancements (ADO#138334,140294,214081,246940,248611,251690,251691,251898,252639,252698,255442,255443,216243,216521,220325,221154,223140,223156,223157,223163,223182,223407,249677,249819,253128,257421)
- Misc. portal UI enhancements (ADO#171934,245229,258615,260492,215239)
- Add Service Manager to the CPU consumption report (ADO#171526)
- [Result Lake] Reduce number of requests to get access token needed by the worker host (ADO#183924)
- Delete Azure Batch job (ADO#209894)
- Logging of user changes to the audit log (ADO#214645)
- Worker communication and control (ADO#216508,170141,176929,176930)
- Improved background worker logging (ADO#221546)
- Delete pools with the same name from multi-batch-accounts (ADO#242617)
- Should block Result Lake download when user's account storage has expired (ADO#255688)
- The Create Application page should allow creating an application with the same in a different environment (ADO#244356)
Defects
- AccountAdministrationTab: Can not change credit limit (ADO#249783)
- Failure to delete big jobs (ADO#251924)
- When selecting more than 10 jobs for deletion it only deletes 10 (ADO#170630)
- Monitor service event reports wrong workitemId (ADO#185284)
- Unable to remove application from a pool (ADO#212443)
- Selecting jobs is only kept in the active page (ADO#212477)
- Selecting folders or files is only kept in the active page (ADO#212478)
- Portal: Accounting; Inconsistent number formatting across credit and storage reports (ADO#215275)
- "New user" e-mail does not link directly to accept the user (ADO#221270)
- [Background worker] Lacks error handling for sequential work executor execution (ADO#252682)
- UploadFileAsync fails to upload files in sub folders on Windows when targeting .NET Core 3.1 and .NET 5.0 (ADO#252855)
- Email notification issues (ADO#254241)
- Transaction Details fails for users with duplicate membership (UserId) entries (ADO#258105)
- Error in accounting reports after migration of accounting data (ADO#261676)
Version 3.1 - September 25, 2020
The 3.1 release of OneCompute focused on OneCompute portal enhancements.
Enhancements
- Miscellaneous security-related enhancements to tighten security of the portal and the API (ADO#140290,146348,159347,159349,214097,214107)
- Restrict the number of tasks loaded in the Job Details view
- Storage size calculation enhancements
- Added web API method to delete a specified job (ADO#182140)
- Extend the API with a method to get container URIs for all work items in a given job (ADO#182311)
- Improved UI in MyStorage and MyJobs views (ADO#173036)
- OneDesign alignments
- UI improvements to account management
- Misc. portal UI enhancements (ADO#82427,88166,91954,94991,94995,94997,95957,153322,158304,165453,165879,185424,189601)
- Administration page for Account Administrators (ADO#176223)
- Manually assign account admins to the proper account (ADO#79272)
- Improve the home page load performance (ADO#144310)
- Bulk delete of jobs from OCP portal (ADO#157078)
- Field for Account Administrators to change the credit limit (ADO#160553)
- Allow AccountAdministrators to see the account jobs (ADO#165711)
- Show size of jobs in the My jobs tab (ADO#183649)
- Show size of tasks in the My jobs tab (ADO#187202)
Defects
- Not able to send email notification to users without disabling Javascript
- Not able to delete files or Jobs from Result Lake
- Failure to upload files to Result Lake for long-running work
- AzureBatchWorkScheduler consistently times out for certain big jobs and fails to complete the job (ADO#177808)
Version 3.0 - April 1, 2020
The 3.0 release of OneCompute focused on enhancements to OneCompute Platform:
- Accounts and consumption control
- Improved consumption reports.
- Result Lake: providing scalable storage of result files
- Miscellaneous usability enhancements to the OneCompute Portal
Changes
All NuGet package references have been upgraded to their latest versions in this release. "Microsoft.WindowsAzure.Storage" has changed to "Microsoft.Azure.Storage.DataMovement" & "Microsoft.Azure.Storage.Blob." As of "Microsoft.Azure.Storage" v9.4 Table API support has been dropped. Table API support is now provided by the "Microsoft.Azure.Cosmos.Table" library. Applications using Azure storage may need to upgrade to these libraries.
There are a few breaking changes to the OneComputePlatformClient. See list of Enhancements below.
Enhancements
- New home page with usage data.
- Provide link from job directly to corresponding storage folder
- Scalable results storage, see Result Lake
- General Portal Improvements
- Implementation of Accounts
- Limit Credit consumption
- Limit Storage access
- Changes to the OC platforms
- Storage usage visible for users
- Extend portal reports and UI to account for consumption limits
- Add transactions into One Compute
- Access to Results Lake output files, see Using the OneCompute Result Lake
- The WorkUnit.Data property was removed. Its usage was to provide access to application input, which now can retrieved by using the WorkUnit.GetInput method.
- The asynchronous methods of OneComputePlatformClient was renamed with the Async postfix to give room for corresponding synchronous methods, in preparation for clients that require synchronous methods.
Defects
- Usage report error when user has no usage
- Portal: "Jobs" table does not show properly
- Unhandled authentication exception for external user
- Portal: Security; Penetration testing vulnerability 2.4.1.1 - W - A2-Broken Authentication and Session Management - Incorrect session management
- Portal: Size sorting is not working properly
- Portal: After "Log out" the user is not logged out nor redirected to home page
- OneCompute portal- Operation: Wrong VM sizes displayed
- Batch: File transfer to node fails occasionally
- Access denied to job details through developer portal
- Portal: Run time is not updated in Jobs view while job is running
- Portal: Applications; Upload fails when package version contains a space
- Exception for a non-VerIT user when accepting terms and conditions in the OCP portal
- Uploading big application package fails with HTTP error code 500
- Exception in JobScheduler when updating work item properties
- Credits are not properly accounted for in a faulted job
- West Europe production portal fails
- Errors experienced by a user that has no jobs or container content.
- Cloud storage navigation fails for users with high storage
- The home page is crashing in the production North-Europe environment.
- Dev+Test Prevent web jobs running on Structure compute portal resources
- Jobs getting stuck in states instead of moving to completed
- CSV report has column header Cost instead of Credits
- The Add-Application page fails to validate form inputs
- Pools listed in Application Default Pool drop down wrong
Version 2.2.2 - November 24, 2019
This is a patch release of version 2.2.
Changes
Defects
Version 2.2.1 - October 14, 2019
This is a patch release of version 2.2.
Changes
Defects
Version 2.2 - July 12, 2019
The 2.2 release of OneCompute focused on
- Portal accessibility
- Following up on findings from penetration tests
- Following up on findings from security review
Changes
Enhancements
- Azure Batch should wait for start task to finish
- Make job upload more resilient against network errors
- Implement support for Dockerised worker containers
- Add time zone to 'last activation time' when adding / modifying package.
- Security: Fill out DTC's ASSA (Application Security Self-Assessment) form prior to external penetration test
- PoC: Calling OneCompute API from a service
- Penetration testing follow up
- Security review follow up
- Increase ingress and egress limits for storage accounts
- Remove user storage when removing a user
- Improve input files mechanism to match output files
- Job preparation task
- Job release task
Defects
- The WorkerHost project depends on Azure
- AuthRedirectUri app setting not set in deployment scripts
- Question mark link in header is not working
- JobScheduler crashes when the size of the resource files collection is > 32K
- Account admins not assigned to any account can see all data
- User search box is not available anymore
- Should prevent unauthorized access to blob container
- Access to other users' storage through editing user in portal
- Prevent XSS attack in blob names
- Deleting multiple files from the cloud container fails
- OneCompute Platform API URL is wrong
- User registration fails after adding service principal user
- Sesam regression tests fail due to failure to authenticate the test user
- Job serialization problem
- Data transfer Including filters is picking up all files rather than the filtered
- Prevent worker host service reporting missing optional "ITelemetryClient"
- Delete selected blob storage fails
- Changing default version leads to error message
- Error when nothing is typed for the new application id
- Unable to delete selected content when "sibling", unselected content is present
Version 2.1 - April 30, 2019
The 2.1 release of OneCompute focused on:
- Consumption reporting in the OneCompute Portal
- Ability to specify default pools for Batch applications
- Enhanced pool management from the OneCompute portal
- Application properties on jobs and work items
Changes
Enhancements
- Application properties for jobs and work items
- Report data storage used per company and per user
- It should be possible for the users to see usage for their account (CPU hours and data storage) per month
- Report 'all companies' should show usage per company
- Accounting Report: Display credits value in the Usage table
- Change "created" status to "waiting to start" or similar
- Specify default pool per application
- Allow updating Terms of Use / Click To Accept without deploying portal
- Create "Company accountant" role
- It should be possible for the users to see usage for their account (Credits) per job
- Provide a dashboard for the user showing the company's usage so far this month, as well as their (company's) consumption limits.
- Portal: Jobs: Bring back show run/simulation time for the job
- Report more details for usage per company
- Add more options to the Operation tab
- Show current status of cloud nodes
- Store and retrieve job information
- Store and retrieve Work Item properties
- Portal: Jobs: Show overview of current and recently completed jobs
- Portal: Jobs: Administrator should be able to view jobs across all users
Defects
- OneComputePlatform test portal: "Show user storage per user" gives server error
- The current consumption .CSV file can not be opened in Excel
- The reduction task of a ParallelWork fails to run in Azure Batch
- Authorization not working in swagger
Version 2.0 - February 13, 2019
The 2.0 release of OneCompute focused on:
- Establishing OneCompute Platform, a shared, scalable compute service running in Azure.
- Increasing scalability and robustness of OneCompute components.
Features of OneCompute Platform
- OneCompute API with secure access through Veracity
- Schedule jobs for execution
- Monitor job execution
- Get job status and progress
- Provide secure access to a private blob container for every user
- OneCompute Portal with secure login through Veracity and role based security
- Every user can browse their own blob container and download files through the OneCompute Portal
- Every user can list their jobs
- Every user can get a consumption report
- Accountants can get consumption reports for companies and users
- Operators can manage compute pools
- Application Owners can manage applications
- User Managers can manage user access to applications
Changes
Enhancements
- Orchestration options on Job for error handling - Implementation Azure batch and console
- Extend WorkItem with description
- Allow jobs to run to completion even if one or more of the work units fail
- Get work items without deserializing json content
- Graceful shutdown and restart of Job Scheduler web job
- Application ownership implementation
- Assign the job to the pool
- Add ability to delete application packages in OneCompute portal
- Only send activation emails to user management role
- Create a user management role
- Also send activation emails to a specified additional non-user email address
- Remove multiple workspace at once
- Add async bulk insert method to AzureStorageTableHelper
- Allow files to be excluded from file upload after the work unit completes
- BlobStorageFileTransferService should invoke events on the original thread
- Accounting reports should report consumption in the form of credits used, not Core-hours
- Show credits for old jobs
- Store CPU consumption for on-going jobs, not just per finished job
- Application Owner can edit credit per consumption unit for an application
- Operator can edit CPU cost factor on a pool
- Aggregation of consumption and credits per job
- List jobs per user
Defects
- Cancelling an Azure Batch job does not work
- Job occasionally fails to complete even if all work units are completed
- Exception while monitoring Batch tasks terminates job
- The OneCompute storage connection string is exposed in the console output from the WorkerHost
- BlobFileTransferService fails to transfer files at high loads
- File transfer occasionally hangs when running at high load
- Unclear error message when trying to run in cloud without account
- Make AzureBatchWorkItemScheduler more resilient when scheduling a large job
- Status updates are lost in the WorkerExecutor
- When Azure Batch fails to run a CloudTask, the error information is not stored in the work item status table
- Fix Azure application package deployment script
- Job scheduling: Input files with space are not copied to compute node
- Task that fails to upload all files to cloud storage should fail
- Count time during copying files to Storage as part of task duration
Version 1.2.2 - June 30, 2018
This is a patch release of version 1.2.
Changes
Defects
- Aggregate CPU time as long
- WorkUnit is completed before files are uploaded and result stored
- Log the Job.ServiceName to the JobStatus record
- Add a PoolId property on the job to allow the client to choose backend pool to run on
- When a work unit fails, the file transfer is cancelled
- Log which pool is used
Version 1.2.1 - April 5, 2018
This is a patch release of version 1.2.
Changes
Enhancements
Version 1.2 - March 30, 2018
The 1.2 release focused on:
- Fixing defects
- Minor enhancements
- Enhancing the production environment of OneCompute
- Adding automatic regression testing of the supported back-ends
- Automatic build of examples and VSIX projects
- Standardizing on .NET Standard 2.0
- Standardizing on the new C# project format that simplifies NuGet packaging and avoids package dependency inconsistencies
Changes
Enhancements
- Scheduling a job with no user Id specified should throw a descriptive exception
- Reading job status for a non-existing job should return null
- Upgrade solution to .NET Standard
- Update third party NuGet dependencies to latest versions
- Correlate Azure Batch job id with 1C job id
- Support custom Azure Batch Worker Hosts
- Azure Batch Deployment Tools
- Allow user identities which are not email addresses. This enables an application to replace the default user id validator, which requires the user id to be a valid email address, with an alternative id validator. The application may provide a custom validator. OneCompute 1.2 provides a GUID validator, which requires the user id to be a GUID.
Defects
- BlobStorageFileTransferService generates incorrect blob names
- Job with WorkUnit that fails is recorded with status = Completed. Should be Faulted
Version 1.1.1 - February 5, 2018
This is a patch (bug fix release of version 1.1).
Changes
Version 1.1 - November 22, 2017
This was the initial release of OneCompute.