Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

OnApp Boot from ISO

by | May 31, 2021

Wondering how to make OnApp Boot from ISO? We can help you.

OnApp allows us to upload custom bootable ISOs for recovery purposes. Furthermore, it can be different images for Windows/Linux/FreeBSD or any additional software.

Here at Bobcares, we often handle requests from our customers to assist for OnApp boot from ISO as a part of our Server Management Services. Today we will see how our support engineers do this for our customers.

OnApp Boot from ISO – Steps to follow

Following are the steps to make OnApp boot from ISO:

1. Viewing ISOs

To view the ISOs available we can use the following steps:

  1. First go to Control Panel, take Cloud, and click Templates.
  2. Then Select the ISO list from the menu.
  3. We can see the list of ISOs available split into four tabs given below:
    • All ISOs – the list of all ISOs available on the system.
    • System ISOs – the list of the ISOs that are publicly available to all users.
    • My ISOs – the list of custom ISOs that the currently logged-in user uploads.
    • User ISOs – the list of the ISOs that our users upload.

 

2. Boot from ISO

Now, for OnApp boot from ISO, we need to do the following steps first.

Share Location Where ISOs are Stored

The default configuration is to upload ISOs on the Control Panel server. Then we have to mount and share the location where the ISOs are stored at CP with all the compute resources.

Further, when the virtual servers are booted from the ISOs, it takes the ISO from the compute resource server. The on_app.yml have the location, which can be found in /onapp/interface/config/on_app.yml.

  • iso_path_on_cp – specifies the location where Control Panel Servers stores ISOs. By default the location is /data. You can change it to any other suitable location. Make sure that this location is shared with the specified iso_path_on_hv location.
  • iso_path_on_hv – specifies the location where ISOs are located on the compute resource servers. By default the location is /data.  You can change it to any other suitable location with the onapp owner and read/write access. Make sure that this location is mounted to the specified iso_path_on_cplocation.

 

Upload ISO(s) into the Cloud

To upload an ISO file, follow the next steps:

  1. Go to your Control Panel > Cloud and click the Templates menu from the left navigation pane.
  2. Select ISO list from the menu that expands.
  3. On the page that loads, click the Upload ISO button at the bottom of the screen.
  4. Further, choose the ISO to upload and fill its details:
    • Make public – move the slider to the right if you want to make the ISO publicly available
    • Allowed hot migrate – move the slider to the right if you want to be able to hot-migrate VS created from this ISO
    • Label – choose a name for the ISO
    • Version – fill in the version of the ISO
    • Min disk size – specify the minimum required disk size for the ISO (1 GB by default)
    • Min memory size – specify the minimum required RAM for the ISO (128 MB by default)
    • Operating system – choose the operating system of the ISO
    • Operating system distro – fill in the operating system distribution of the ISO in free form
    • Virtualization – tick the required virtualization type(s): XEN, KVM or KVM+Virtio
  5. Click Next. On the page that appears, click File or File Url tab depending on the upload method:
    • File – click Choose File to select the required ISO file from your file system. The yellow infobox will show the maximum file size for ISOs.  The Settings > Configuration (the Max upload size in bytes) has the max upload size. Click the Upload ISO button.
    • File URL – select this tab if you want to upload the ISO from URL and specify the link from which the ISO will be uploaded.
  6. Finally, Click Save to upload the ISO.

Notably, after you upload an ISO to the cloud, it can be found at Cloud > Templates > ISO List > My ISOs tab. The ISOs uploaded by your users are under the User ISOs tab.

Make ISO(s) Public

By default ISOs are available only to those users who uploaded them. Further, these ISO images are available in the My ISOs tab. In effect, to make your ISO public and accessible for all users:

  1. Go to your Control Panel > Cloud > Templates > ISO List menu.
  2. Click My ISOs tab.
  3. Click the Actions button next to the ISO you want to make public, then select Make public.
  4. Confirm the window that pops up.

Further, when you make a user ISO public, it moves to the System ISOs tab.

  • Make sure that you have enabled the Any power action on own virtual servers and Allow own virtual servers to boot from ISO permissions for the user to be able to boot servers from ISO.
  • Note that you should track the Operating System Type option of the compute resource where the current VS lives.
    • If the compute resource is set to Any, any ISO that has other suitable requirements is available to boot from.
    • Alternatively, if the compute resource has Windows only option enabled, the ISO that has Windows operating system is available for selection.
    • If the compute resource has the Non-Windows option enabled, the ISOs with OSs LInux and FreeBSD are available for selection.

 

Boot Virtual or Smart Server from ISO

Once you have shared the location where ISOs are stored and uploaded ISOs into the system, you can boot virtual or smart servers from them using the server’s power options menu. Thus, to boot a virtual/smart server from ISO:

  1. Go to your Control Panel > Cloud > Virtual Servers/Smart Servers menu.
  2. Click the label of the required server.
  3. Click the Tools button on the server’s screen to expand the Tools menu.
  4. Select Boot from ISO. You can boot virtual/smart servers from your own ISOs or the ISOs that are uploaded and made publicly available by other users. If you boot a server from an ISO with the RAM requirement larger than the server’s RAM, the transaction will fail.

[Need help to fix Plesk error? We are available 24*7]

Conclusion

In short, we need to follow a series of steps to boot from ISO on Onapp. Today, we have discussed the steps that our Support Engineers follow to perform it.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

OnApp Support

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management & end-user tech support to us, and use that time to focus on the growth and success of your business.

TALK TO US Or click here to learn more.
OnApp Support

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management & end-user tech support to us, and use that time to focus on the growth and success of your business.

TALK TO US Or click here to learn more.

Categories:

Tags:

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF