Maximizing Performance with IBM Cloud VPC Images
IBM Cloud VPC instances are created using images. Choose a stock, custom, or catalog image based on your needs. What are stock pics?
What are stock images?
The default operating system for IBM Cloud VPC environments is a stock image. It deploys virtual or bare metal servers of various architectures.
These images have all the configurations needed to provision a server and deploy instances quickly. IBM updates stock images, but users should apply the latest vendor fixes and packages when provisioning an instance.
IBM offers many alternatives. On IBM Cloud VPC, IBM support Red Hat Enterprise Linux, Windows Server, SUSE Linux Enterprise Server, Debian, Ubuntu, Rocky Linux, CentOS Stream, and Fedora.
IBM will follow each vendor’s end-of-support (EOS) dates for most of these images. IBM will assign stock photos three statuses based on their stage to manage their lifecycle:
- Available
- Deprecated
- Obsolete
If an OS is supported by the vendor, IBM’s current stock image will always be “available”. Outdated versions will be marked “deprecated”. Stock photos with vendor-set OS expiration dates are marked “obsolete”.
Remember that you can launch instances using available and deprecated instances, but not obsolete stock images.
Stock photos may be deployed and used immediately for any purpose, which is a major benefit. Custom images can be made from stock photographs.
Instance deployment using stock pictures
1. Click Change image on the instance creation page’s image and profile section.
2. A side panel will display all stock photos for architecture selection:
3. Type the OS name into the filter on the Stock pictures tab, pick it, and click Save:
4. After closing the side panel, the UI should show the new stock image:
Describe custom images
Customers develop virtual servers using custom operating system images with their own specifications. Antivirus, databases, and other software can be added to custom images. You can generate a custom picture by leveraging an existing instance with a customized base stock image or by creating and importing it on-premises.
Custom image owners set the image status (available, deprecated, or obsolete), unlike IBM for stock photos.
End-of-support (EOS) photos are not instantly “deprecated” like stock photographs, but the same rules apply. Planning the lifecycle of your images will save your firm time and resources and help it innovate by adopting the newest OS versions.
Custom images let you preserve your settings and setups. Use a custom image to deploy more instances in the same area, control their lifespan, and export and import into another region to deploy instances there.
Custom image creation
1. Select Images and click Create on the VPC menu.
2. Name your custom image.
3. You can customize an instance image. Stop the instance before creating the custom image.
4. Select an instance’s boot volume to create a custom image. Like the previous step, halt the instance before creating the custom image.
5. You can import Cloud Object Storage images. You must save the picture in a COS bucket and specify the base operating system when importing.
6. Provide the picture file URL and base OS to import from COS.
7. Choose encryption.
8. Custom image lifecycle management is optional. You can set the deprecation date, obsolete date, or both in advance by date or days.
Custom image instance deployment
1. Click Change picture under picture and profile.
2. After choosing the architecture type, choose Custom images, select the custom image you need to deploy an instance, and click Save.
What are catalog images?
Catalog images are bespoke images you or an IBM partner add into a private or public catalog. Other cloud providers call them marketplace images. Each catalog image will include an IBM Cloud Catalog tile. Only virtual servers support catalog images; bare metal servers are not supported.
Enterprise accounts can exchange custom photos via private catalogs. Multiple accounts (or selected accounts) within the same enterprise can have product access managed. The only restriction is that encrypted images cannot be cataloged and must be “available”.
Image lifecycle management at the catalog level includes “available,” “deprecated,” and “obsolete” states. Set the following catalog statuses:
The Catalog lists “available” as “published/verified” in VPC.
“Deprecated” is the same in VPC and Catalog.
The Catalog lists VPC “obsolete” items as “archived”.
IBM Partners and ISVs can share IBM Catalog pictures using public catalogs. Partners and ISVs must undergo onboarding before publishing photographs publicly from the collection.
IBM partners can only accept free products today. In future project deliveries, they will be able to onboard charged images and get paid by IBM customers for consumption, exactly as other cloud providers in their markets.
Using catalog images to deploy instances
1. Select Change picture under picture and profile.
2. Select a catalog image from your account under the Catalog images tab.
3. Click Save and create instance.
Learn more
IBM offer several business images depending on your goals.
Stock images are best for quickly deploying instances. Custom images are best for replicating or moving setups to different regions or zones. Finally, a catalog picture is best for using the photographs of a trusted third-party seller or sharing them within your company.
0 Comments