Closed bbonaby closed 10 months ago
FYI @PlagueHO
Looks good! Thanks @bbonaby !
@PlagueHO FYI PR is out, added tests and examples to confirm unit test functionality. The Dev Drive feature isn't available in Windows server 2019 and as far as I know won't be in Server 2022 either at least for now. I'll have the virtual hard disk PR out hopefully today as well.
updated the issue statement to better reflect what's in the PR today.
The deploy fails because there is a space in the tag that was added in this PR. Dev Drive
should be changed to DevDrive
in the module manifest (in a new PR): https://github.com/dsccommunity/StorageDsc/pull/278/files#diff-8eee5c09560a979f88c375c8c47f71c0d85a219e61956b96f31efc5988fa2b02R55
Created a new issue to track it https://github.com/dsccommunity/StorageDsc/issues/280.
Problem description
Windows has released a new feature called Dev Drive that is currently being used by developers to increase their performance workloads. One thing that has come up is the need to be able to create a Dev Drive through a DSC configuration. Dev Drives are ReFS drives with special features under the hood. Currently to create a Dev Drive one can use the Format-Volume powershell cmdlet with the -DevDrive flag. The Dev Drive feature is now in GA with 10.0.22621.2338 or later.
The StorageDsc appears to be a good place to add this ability. The Disk resource already has the ability to format volumes among other volume related scenarios like:
GPT
orMBR
to an uninitialized disk.MBR
and vice versa.readonly
to write.Note: The Disk Dsc currently does not have a parameter for 'Present' and 'Absent', so the configuration is mostly "if x drive letter on y disk matches all the parameters inputted, do nothing. But if a parameter does not match what was inputted update it so matches the inputted parameters".
We just would like to add one more parameter to the disk resource called
DevDrive
that will allow users to create a Dev Drive volume using the Disk dsc resource. Note: Dev Drive volumes should only be created using 50 Gb of space. The disk resource will need to be aware of this when this new Flag is used.AllowDestructive
flag would be used.prototype in forked branch
example config could be:
Verbose logs
DSC configuration
Suggested solution
nothing here
Operating system the target node is running
PowerShell version and build the target node is running
StorageDsc version