Infrastructure for MacOS 13.x #3240
Comments
|
I was checking the availability for Orka resources, and we have some empty spots in the Node Current Status in OrkaVMs distributionYou can check this in Orka by running
Note that The NATThe NAT is quite tricky to process, but let me summarize it from #3112 (comment)
Nodes Physical resources distributionYou can check this in Orka by running
Future distribution (proposal)We might want to add at least 2 vms per MacOS test version, and 1 for release:
Resources Distribution
Nodes Physical resources availability
We will still have room for another 3 vms if we want to squeeze the nodes. |
|
Getting some new machines into the mix for 20.x makes a lot of sense to me. I think we usualy only release using one version so in terms of release I think should likely assess if we can move up to 12 or 13 for doing releases, but I don't think we'll have resources for both (particularly on the arm side) |
|
Possible Solution for ARM machines in Macstadium Seems like since Orka 2.0 we can add ARM based nodes to the existing intel Orka Cluster.
Currently, we use Bare Metal solution in Macstadium for ARM:
And I believe that the machines are bigger than our needs, but if we convert this resources into Orka Nodes. For Intel we use Orka C1 Build (24 vCPU + 60 GB) Node, so I assume that for ARM Nodes the resources are similar. Then we can extend the current Orka by converting the existing Bare Metal Resources and add 12.x and 13.x for ARM specific: Resources Distribution
Obviously we need to check with Macstadium if this is possible. I think that we are in Orka v2.0 or higher based on #3112 (comment) We can check also with Nearform if we can extend the current nodes in their infra to support 12.x and 13.x |
|
Our Orka cluster is 2.3.1 according to the support ticket when they upgraded. |
|
Using orka makes sense to me. Maybe the next stop is to open a ticket with Mac Stadium asking if we can get an ARM based machine added to our free account? |
|
I will start working in
Thanks @AshCripps!
@mhdawson do you want me to contact support? |
Related: nodejs#3240
Current progress I created the VM Regarding |
sure |
They confirmed that the current Intel Nodes (Macpro) are not supported for Ventura in this environment due Apple restrictions, so I am checking if we can use different Node type to run Ventura in Intel Arch with the current Orka settings, as well I am validating with them also if the ARM Nodes can run Ventura and Monterey |
If we migrate the existing nodes to mac minis then we can add Ventura VMs in Intel Arch. I am checking the specs with Support so I can update the
|
TL;DR:No changes have been made to any machine in the inventory yet. I have made some changes to the distribution of resources and node ideas based on feedback from customer support. The discussion with customer support is now complete, and we can move on to the next steps. Please refer to the "Next Steps" heading at the bottom. Current StatusResponse from Macstadium support:
I closed the support ticket SERVICE-157786. The recommendation from support team will be to discuss with the customer success team (not sure if we have a direct contact already, we can check it?), we can do that as a separate action before we start making changes in the nodes. Based on the last discussions with the support, most likely we can face this scenario with some minor changes in terms of Orka nodes or VM distribution inside the nodes: Macstadium resources:
The NAT
Resources Distribution
Opportunity The impact With this setup the impact in machines availability is lower than in previous comments, but still an impact. Future notes When we remove the support for macos10.14, we will be able to move the VMs from VM Resources
Next stepsImportant: Do we have any critical deadline? This can impact in Node 20 release?
|
|
I think to change hw we'll need to get the ok that it will be covered under the free sponsorship that we get. @UlisesGascon I assume we've not discussed that yet. We'll need to figure out who the right contact might be, maybe from the ticket where they helped remove the charges from creating new machines by accident? |
|
We made a good progress in #3299. 🎉 I will add a new estimation on how we can manage the current Orka / Bare Metal resources in order to add support for 12.x (and ignore 13.x for now) and use the empty slots generated after the drop support for 10.14 (#3087 (comment)) in the following days. |
|
After the progress made in #3087, the current VM distribution in Orka is: Resources Distribution
|
|
@UlisesGascon great to see the progress being made. |
|
Machine
I will create a separate PR to update the secrets inventory.yml once I am clear on the final Ansible settings. |
UlisesGascon
changed the title
|
As discussed in our last meeting (#3604) we will skip macos 12.x and jump to macos 13.x |
|
I created the first VM with Ventura (macos13) image and I am getting issues to login via VNC, so I opened the ticket SERVICE-177494. |
|
The login problem was solved already |
|
What's the status? Can I do anything to help move this forward? |
|
I'm asking because |
This comment was marked as outdated.
This comment was marked as outdated.
UlisesGascon
changed the title
UlisesGascon
changed the title
|
I close this is favor of #3686 that centralize the Orka changes including MacOS 13 addition in Orka. Feel free to reopen this issue if needed. |
It would be beneficial to begin brainstorming ideas on how we can incorporate MacOS 12.x and 13.x into our current infrastructure. I anticipate that we will need to make the machines accessible for both Intel and ARM devices.
To my recollection, we can utilize some of the existing resources in Orka for the Intel machines with our current configuration. However, to accommodate ARM machines, we may require additional infrastructure resources.
What is your opinion, @nodejs/build? Should we discuss this matter in our next meeting?
Issues related:
The text was updated successfully, but these errors were encountered: