All users were logged out of Bugzilla on October 13th, 2018
Can you please create 10 new win32 VMs, called: try-win32-slave10.build.mozilla.org ... try-win32-slave19.build.mozilla.org Phong: As discussed today, can you pls create these new VMs with the larger 3rd disk of 80gb? ie create 9.7gb/20gb/80gb disks?
10 years ago
Please hold off on creating these VMs until we resolve eql storage issues.
Should we update the template with the 80 GB drive? Is there any data on the current 30 GB drive? If there isn't, then I'll just disconnect and deploy VM from that and add the 80 GB drive after.
(In reply to comment #2) > Should we update the template with the 80 GB drive? Is there any data on the > current 30 GB drive? If there isn't, then I'll just disconnect and deploy VM > from that and add the 80 GB drive after. 1) The only thing on the current 30GB drive in win2k3sp2-vc8tools-ref-vm, is an empty directory "e:\builds\moz2_slave". Removing disk from template is fine, so long as you are ok to create this disk and this dir manually for every new VM request. 2) fyi: for the ntfs disks, we've found that certain non-default NTFS settings get us better performance. Specifically, see: https://wiki.mozilla.org/ReferencePlatforms/Win32#Add_drive_E Is it possible for you to set these at the same time you create the NTFS disk for the VMs?
nuking the 30 GB volume will dramatically reduce the deployment time. i'm fine with adding the 80 GB after.
Any update on these, now that we've added some diskspace?
try-win32-slave10/11/12 10.2.76.110/112/114 Should these have 80 GB E: drive as well?
Sorry Phong, looks like John did ask for the 80GB disks in comment #0.
try-win32-slave10/11/12 (10.2.76.110/112/114) are ready.
(In reply to comment #7) > Sorry Phong, looks like John did ask for the 80GB disks in comment #0. Yep, please do put the 80gb disks on these. While its a bit of a waste on TryServer specific slaves, I think having the try slaves identical to production slaves seems wise - we've swapped slaves back/forth between TryServer and production-master quite a bit recently, so seemed easiest way to not trip ourselves up in future. (In reply to comment #8) > try-win32-slave10/11/12 (10.2.76.110/112/114) are ready. Ah, cool. Can we finish up the last of the buildbot setup and testing on these three, while you continue on the other 7 VMs?
try-win32-slave13/14/15 10.2.76.119/120/122 are already ready.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
try-win32-slave13/14/15 were imaged off of the ref platform before version 15 went into effect and try-win32-slave16 isn't logging in correctly - it's asking for ctrl + alt + delete Can these 4 please be re-imaged, thank you.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Nevermind - releng will update these to match version 15. Closing.
Status: REOPENED → RESOLVED
Last Resolved: 10 years ago → 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.