![]() If you see ORPHANED at any point, immediately clean it up. ORPHANED - The task is hung because the coordinator went away.COMPLETE - The task is completed and waiting to be cleaned up.Other than that, go nuts! $ find -type f | womm parallel -kube-pods 10 - wc -l ' Use womm parallel the same way you would use the normal GNU parallel command (if you're not familiar with it, it's a lot like xargs).Ī small caveat - you are required to specify the -kube-pods parameter, and you are required to separate your input from your options with. If you want more (and clearly you do), you need to express your desire for compute in a way that can be distributed across multiple machines. You can use the above up to a certain point but if you go too far you won't be able to schedule your container - no machine on the cluster will have enough spare cores at once to give you your shell. If you ever want to change any of these parameters again, just run womm setup in the same directory. The push refers to repository ĩf54eef41275: Pushing 13.04MB/72.78MB Any environment variables you export from this shell will make their way into the runtime environment.Īfter quitting the shell, WOMM will perform a quick dependency check and then ask you whether your application works: $ logout.This will not be there during actual execution. If you need to reference content from your host filesystem, it's mounted at /mnt.Do make sure to test your application and only quit the shell once it works. The command to "make it work" is prudent.This is the same as it will be during actual execution. This shell has your current directory mounted in as, uh, your current directory.The goal is that if your application works here, it will work on the cloud too.Īlso make sure our dependencies are installed: perl This is a *local* shell where any dependencies you install will be saved. What is a prefix of a docker image name that you are authorized to push to a secure location?Į.g. What is the docker hub name for the base image for your operating system? Next, setup will prompt you to choose the docker base image for your application, as well as the prefix for how it should tag your application's image.Īfter answering, you will be sent to the depths of a shell where you can install dependencies for your application. Enter namespace :Įnter image pull secret name : If you have a working kube setup and are okay with pushing your work to a public repository, you can leave these options at their defaults. Next, you will be asked for some information related to how the application will be deployed to kubernetes. ![]() How do you want to share /home/audrey/proj/womm to your cloud?ģ) eagerly (syncback on complete, not recommended) If you're not sure what to choose, "lazily" is a good option. This will run a configuration wizard and save the results to a dotfile in the current directory.įirst, choose the share method for getting your local directory into the cloud. Navigate to the directory with the application you would like to distribute: $ cd proj/supercool
0 Comments
Leave a Reply. |