Boot a new Vultr VX1 Cloud Compute instance from Block Storage with local NVMe scratch space, via Console or API.
Vultr VX1™ Cloud Compute provides dedicated CPU resources. VX1™ supports booting from Vultr Block Storage and can also use local NVMe storage as scratch space.
Follow this guide to provision a Vultr VX1™ Cloud Compute instance using the Vultr Console or Vultr API.
VX1™ is available in select locations. To check availability, open the Create Instance page in the Vultr Console, select the required VX1™ plan, and verify that it is available in your preferred location.
Windows operating systems are not available for VX1™ instances. Set block_type to high_perf when you create bootable Block Storage volumes.
Navigate to Compute and click Instances.
Click Create Instance +.
Under Plan, select Dedicated CPU.
Select VX1 from the Plan Selection sidebar.
Select a plan from the list:
vx1-g-*): Provides a balanced combination of vCPUs and memory, suitable for most workloads, including web servers, application servers, development environments, container workloads, and moderate database deployments.vx1-m-*): Provides a higher memory-to-vCPU ratio, suitable for workloads that require large in-memory datasets, such as caching engines, analytics workloads, JVM applications, high-memory web services, and large databases. Plans that report Block Storage in the Storage column boot from a bootable Block Storage volume. Plans ending with a -###s suffix, such as vx1-g-4c-16g-240s, include local NVMe storage.
Under Location, select a Vultr location for the instance.
Click Configure.
On plans with local NVMe storage, select a Boot Configuration:
You cannot reinstall a VX1™ instance that boots from a bootable Block Storage volume. Instances that boot from local storage support reinstallation.
If the instance boots from Block Storage, select the target volume in the Bootable Block Storage section, or create a new one:
If the instance boots from Block Storage, select an Attachment Method:
The Summary shows the selected volume in the Boot Storage field.
If the instance boots from local storage, select an image source under Image Selection and Configuration:
Under Server Settings, optionally select an IP Address, SSH Keys, a Startup Script, and a Firewall Group. Instances that boot from Block Storage do not show the Startup Script option.
Enter a value in the Server 1 Hostname field and the Server 1 Label field to identify the instance.
Configure Additional Features for the instance:
linuxuser non-root user with sudo privileges as the default user account instead of root.Review the instance details in the Summary panel and click Deploy to provision the instance.
0 Comments
Be the first to comment and share your perspective with the community.