Creating a brev node from the CLI involves two tasks:
1.) Finding an instance type. These have provider specific names that are not human friendly.
2.) Creating an instance of that type.
Today, to find an instance type, you can either:
- Find it manually (not recommended, and may change due to availability).
- Use
brev search, which can be piped into brev create.
- Use
brev create, which has some but not all of the options of brev create.
Questions:
- Do both
brev create and brev search go through the same codepath for doing searching?
- Is
brev search | brev create the new best practice? If so we should say brev create is deprecated somewhere.
Creating a brev node from the CLI involves two tasks:
1.) Finding an instance type. These have provider specific names that are not human friendly.
2.) Creating an instance of that type.
Today, to find an instance type, you can either:
brev search, which can be piped intobrev create.brev create, which has some but not all of the options ofbrev create.brev createhas no "CPU" mode and can't search for CPU instances. Seebrev createshould have two subcommands,brev create gpuandbrev create cpu, mirroringbrev search#376.brev createdoesn't have all of the flags ofbrev search gpu: it's missing--archand--total-ram. Seebrev createandbrev searchflags for # of processors and amount of memory are confusing and inconsistent #373 andbrev createandbrev searchflags for processor architecture are inconsistent #374.Questions:
brev createandbrev searchgo through the same codepath for doing searching?brev search | brev createthe new best practice? If so we should saybrev createis deprecated somewhere.