SIP-disabled images not present when running 'orka3 remote-image list' via the CLI

[IanTaylor-catapult]

Is there a reason that the SIP-disabled images for Ventura and Sonoma are not present when running orka3 remote-image list?

ubuntu@ip-xxxxx:~$ orka3 remote-image list
NAME                           SIZE   TYPE
90gbigsurssh.img               90G    amd64
90gbmontereyssh.orkasi         90G    arm64
90gbsonomassh.img              90G    amd64
90gbsonomassh.orkasi           90G    arm64
90gbventurassh-13.5.1.orkasi   90G    arm64
90gbventurassh.img             90G    amd64
90gbventurassh.orkasi          90G    arm64
90gcatalinassh.img             90G    amd64
90gmontereyssh.img             90G    amd64
mojave-clean.img               22G    amd64
sonoma-90gb-orka3-arm          90G    arm64
ventura-90gb-orka3-arm         90G    arm64

Been trying to create a vm that I can save from the SIP-disabled images, but I can't pull them down from remote, and the vm deploy is taking over 30 minutes so far. I assume that this would be much faster if we could pull these to our orka cluster storage.

ubuntu@ip-xxxxx:~$ orka3 vm deploy test-sonoma-no-sip --image ghcr.io/macstadium/orka-images/sonoma:latest-no-sip
Waiting for VM test-sonoma-no-sip to be deployed.
ubuntu@ip-xxxxx:~$ orka3 vm deploy test-ventura-no-sip --image ghcr.io/macstadium/orka-images/ventura:no-sip
Waiting for VM test-ventura-no-sip to be deployed.
<insert 30 minute wait here>
ubuntu@ip-xxxxxx:~$ orka3 vm list
NAME                                     IP              SSH    VNC    SCREENSHARE   STATUS
macos-sequoia-arm64-499032-11255315688   xxx.xxx.xxx.xxx   8822   5999   5901          Running
test-sonoma-no-sip                                                                   Pending
test-ventura-no-sip                                                                  Pending

[abojak]

Hi Ian, new image deployments are unfortunately a necessary evil and if they are pulled from the cloud (MacStadium or GitHub etc.) the latency experienced is highly dependent on your network bandwidth and image size as you are experiencing. However, after initial deployment the image will be stored in the cache of the cluster node it deployed on. From that point, additional deployments take seconds. Another option is to use "orka3 remote-image pull

which will store the image from our repo onto your cluster's NFS mount. Doesn't eliminate a network latency penalty during image copy, but the subsequent deployment of a VM is much faster. ***@***.*** ~ % orka3 image list NAME DESCRIPTION IMAGE-ID SIZE TYPE STATE sonoma-90gb-orka3-arm sonoma-90gb-orka3-arm 8fdcb30befc9 90G arm64 Ready sonoma-90gb-orka3-arm-nfs Copy of sonoma-90gb-orka3-arm 8fdcb30befc9 90G arm64 Ready ventura-90gb-orka3-arm Pulled from ventura-90gb-orka3-arm 8666ab938a4a 90G arm64 Ready Deployment from NFS mount is about 75s on these base 90G images. In Orka version 3.2 (now called "Orka Cluster") we've added the ability for admin level user credentials to copy images to Kubernetes nodes to ensure rapid deployment of any image on any node. We refer to the feature as "Scheduled Caching" as the user must manage the times and operations to transfer images to a specific cluster node, but it eliminates any dependency on NFS or external network transfer times on cloud image pulls when running an automated build job with all necessary images stored locally on your cluster nodes (3s for a 90G VM deploy!). ***@***.*** ~ % orka3 imagecache info ghcr.io/macstadium/orka-images/sonoma_ios NODE-NAME IMAGE-ID SPACE-USED STATE arm-mini-001 ee27c37b1ec5 59G Ready K8s manages the node cache based on space and in general, the latest versions of cached images are what are available for rapid deployment. Do commit and save changes to the image if any are made. Hope this helps manage your latency issues. Cluster 3.2 releases next week. Your team can request an upgrade through MacStadium support. Cheers Andrew Bojak MacStadium Orka PM On Wed, Oct 9, 2024 at 8:38 AM Ian Taylor ***@***.***> wrote: > Is there a reason that the SIP-disabled images for Ventura and Sonoma are > not present when running orka3 remote-image list? > > ***@***.***:~$ orka3 remote-image list > NAME SIZE TYPE > 90gbigsurssh.img 90G amd64 > 90gbmontereyssh.orkasi 90G arm64 > 90gbsonomassh.img 90G amd64 > 90gbsonomassh.orkasi 90G arm64 > 90gbventurassh-13.5.1.orkasi 90G arm64 > 90gbventurassh.img 90G amd64 > 90gbventurassh.orkasi 90G arm64 > 90gcatalinassh.img 90G amd64 > 90gmontereyssh.img 90G amd64 > mojave-clean.img 22G amd64 > sonoma-90gb-orka3-arm 90G arm64 > ventura-90gb-orka3-arm 90G arm64 > > Been trying to create a vm that I can save from the SIP-disabled images, > but I can't pull them down from remote, and the vm deploy is taking over 30 > minutes so far. I assume that this would be much faster if we could pull > these to our orka cluster storage. > > ***@***.***:~$ orka3 vm deploy test-sonoma-no-sip --image ghcr.io/macstadium/orka-images/sonoma:latest-no-sip > Waiting for VM test-sonoma-no-sip to be deployed. > ***@***.***:~$ orka3 vm deploy test-ventura-no-sip --image ghcr.io/macstadium/orka-images/ventura:no-sip > Waiting for VM test-ventura-no-sip to be deployed. > > ***@***.***:~$ orka3 vm list > NAME IP SSH VNC SCREENSHARE STATUS > macos-sequoia-arm64-499032-11255315688 xxx.xxx.xxx.xxx 8822 5999 5901 Running > test-sonoma-no-sip Pending > test-ventura-no-sip Pending > > — > Reply to this email directly, view it on GitHub > , or unsubscribe > > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >