microsoft / microsoft/AzureTRE

Wanted: suggestions for speeding up the airlock review process

Open
#4,311 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Python
Stars
235
Forks
192
Avg merge
1d 23h
Merged PRs (30d)
13

Description

The airlock review process requires the reviewer to boot up a Windows VM, then RDP into it to check the data. This is currently a very slow process, taking about 15 minutes or more from clicking the button to create the review VM to being able to look at the data. This is enough to be burdensome, so I'd be very much interested to hear ideas about how to improve the speed of this process.

Some possibilities I can think of are:

  1. Use a custom VM with stripped down post-boot installation, so it doesn't do much other than just boot.
  2. Use a (custom) Linux VM, which normally boot much faster
  3. Create the VM at the time the request is submitted, let it do the slow stuff while waiting for the reviewer to turn up. That's not too expensive if the machine is small enough, but given that a lot of stuff happens on first-login, not just first boot, this may not help much.

Does anyone else have any ideas how to speed this part up? Any thoughts on the difficulty of implementing these options?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing the airlock review flow from VM creation through first login and RDP access, then compare the three proposed approaches. Done requires an agreed, scoped improvement and evidence that review VM startup is faster.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, linux
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.