How to use compute nodes

1. Basic user operations

Administrators and users can perform operations such as reserving compute nodes for server groups that can be used by the user groups they belong to. The following describes the operation procedures for using compute nodes and checking their usage status.

2. Use of compute nodes

Cloud Bouquet allows you to use compute nodes in the regions you have set up.
This section describes the flow and operations for reserving, using, and terminating compute nodes.

2.1. Confirmation of compute nodes reservations

To reserve a computation node, it is necessary to confirm in advance whether the specifications of the computation node you wish to reserve can be reserved for the desired period. To confirm the availability, select 【Availability Calendar】 from the menu bar on the left side of the screen (click and hold down the mouse button) to open the 【Availability Calendar】 screen.

Select “User Group” from the menu on the left side of the Availability Calendar】 and click the [Server Type] button to display the 【Server Type】 (list of computation node specifications).

Select the plan you want to use in 【Server Type】(Calculation Node Specification List) and click the [Select] button to display the availability of the selected plan in a block on the calendar in 【Availability Calendar】. During the period when the availability block is displayed, the selected Plan can be reserved. To check the availability of another Plan, click the [Server Type] button again and reselect the Plan whose availability you want to check in the 【Server Type】 (computation node specification list).

TIPS!
Availability can be checked until the end of the month two months from the current date and time.
In the case of 2024/12/20 10:00, the period from 2024/12/20 10:00 to 2025/2/2/28 23:59 will be displayed.

You can change the month to be displayed by clicking [<] and [>] at the top of the 【Availability Calendar】. You can also change the month by clicking on the calendar in the upper left corner of the 【Availability Calendar】.
You can narrow down the availability by period of use in “Server Availability” on the lower left of the 【Availability Calendar】. By selecting either [over] or [less than] and entering the period of use, you can narrow down the availability displayed according to the conditions you set.

By pressing the block of availability shown in the calendar, you will see the period of availability and detailed information about the selected Plan.

Pressing the date on the calendar switches the month view calendar to the week view calendar. In the weekly calendar, occupied periods are marked with gray occupied blocks. Pressing the [MONTH] button at the top of the weekly display calendar switches to the monthly display calendar.

These are the methods to check before booking a computation node.

2.2. Reserving a compute node

The procedure for reserving a compute node consists of Steps 1-4. The contents of each Step are explained below.

2.2.1. Reserving a compute node (Step 1)

To reserve a compute node, first select [Cloud Servers] from the left menu bar (click and hold) to open the [Cloud Servers] screen. Then, click the “+Add Server” button in the upper right corner of the 【Cloud Servers】 screen to open the 【Select Server Group】 screen.

The 【Select Server Group】 screen displays predefined server groups (groups of servers per region) (only server groups that can be used by the user in question will be displayed). The server group to be displayed can be selected from the drop-down menu in the User Group column near the upper left corner of the screen. You can also filter the data displayed by using the “Columns” menu or the “Filters” menu.

The [Select Server Group] screen is Step 1 in the procedure for reserving a compute node. The current step can be confirmed by “❶Select Server Group” at the top of the screen.

TIPS!
If the user in operation belongs to more than one user group, check the “Server Group Name” field to select the user group (wallet) for which you want to consume points when reserving the compute nodes.

For each server group, the following information is shown

2.2.2. Reserving a compute node (Step 2)

To reserve a compute node, click the “Select” button for one of the server groups on the 【Select Server Group】 screen (Step 1). This will take you to the 【Select Server Type】 screen (Step 2).
On the [Select Server Type] screen, “Selected Server Group” (the currently selected server group) and “Selected Region” (the currently selected region) are displayed at the top, and a list of compute nodes specifications is displayed in the center of the screen. On this screen, you can select the specification of the compute nodes you want to launch.
(You can return to the [Select Server Group] screen (Step 1) by clicking the [Back] button in the upper right corner of the screen.

For each compute node, the following information is shown. For points, “User Group:” and “Balance:” in the upper right corner of the [Select Server Type] screen show the user group name (user group wallet from which points are consumed) and the number of points used.

TIPS!
The System Information column will contain notes on the use of calculation nodes. Please hover over the appropriate section of the table to see the full text.

2.2.3. Reserving a compute node (Step 3)

On the [Select Server Type] screen (Step 2), click the [Select] button for any of the compute nodes specifications to move to the [Settings] screen (Step 3). On this screen, you can configure detailed settings for the calculation node. After filling in the necessary information, confirm the information displayed and click the [Confirm] button at the bottom of the screen if you want to proceed to reserve the compute nodes (Moves to Step 4).
(You can return to the [Select Server Type] screen (Step 2) by clicking the [Back] button in the upper right corner of the screen.

The detailed settings for a compute node consist of the following entry fields

TIPS!

• Either “End Time” or “Usage Time” must be filled in.
  
• When “End Time” is entered, “Usage Time” is automatically entered.
  
• When “Usage Time” is entered, “End Time” is automatically entered.
  
  

TIPS!

• The scheduled start and end times set in the calculation node reservation operation are not available for points that expire.
  
• As an example, you cannot reserve a compute node from 2025/03/05-2025/03/15 while holding only 5000 points that will expire on 2025/03/10. If you want to make a reservation for 2025/03/05-2025/03/15, you need points with an expiration date longer than 2025/03/15.

The following information will also be displayed, combining the selections made above with the specifications selected in the process described above. For “Pre-Calculated Points,” the results are estimated each time according to the inputs above.

TIPS!

• If the point balance of the user group in question is less than the required number of points when the server is reserved, the server cannot be reserved.
  
  

TIPS!

• When the [Confirm] button is clicked, the reservation confirmation process is executed based on the computation node specifications and usage period.
  
• If you are unable to make a reservation with the target setting, return to the reservation confirmation and confirm it, then perform the reservation operation again.
• Reservation confirmation of computation nodes (2.1.)

2.2.4. Reserving a compute node (Step 4)

In the [Settings] screen (Step 3), click the [Select] button for any of the compute nodes specifications to move to the [Confirmation] screen (Step 4). On this screen, you can perform final confirmation of the calculation node to be reserved. (You can return to the [Settings] screen (Step 3) by clicking the [Back] button in the upper right corner of the screen.

Also, check the terms of service at the bottom of the screen, and if you agree, place a check mark in the check box to the left of “I agree to the terms of service.

After reviewing the information displayed, click the [Reserve] button at the bottom of the screen if you want to proceed to reserve the compute nodes.

TIPS!
The information displayed on the [Confirmation] screen (Step 4) is the same as on the [Settings] screen (Step 3).

TIPS!
If you agree to the Terms of Use and fill in the check mark, the [Reserve] button will be enabled.

After pressing the [Reserve] button, a confirmation pop-up window will appear again.
Please read the notes on the pop-up screen, and if there are no problems, press the [Reserve] button on the pop-up screen to start launching the compute nodes.

Once a node is reserved, the reservation status can be viewed in the 〈Usage Calendar〉 (【Usage Calendar】 screen on the left menu bar).
The 【Usage Calendar】 screen displays an arbitrary one-week calendar in the main part of the screen, with the reservation periods for the computation nodes listed in block form. The week to be displayed can be changed by selecting (clicking on) a date from the monthly calendar in the upper left corner of the 【Usage Calendar】 screen. Similarly, by selecting any item from the “Server Group” and “Server Status” columns, you can change the computation nodes to be displayed. In the “Server Status” column, you can select “Downtime on login nodes” to display on the calendar when a login node is down for some reason.
The block of reserved periods for the computation node is displayed in any color.

By clicking on the block of the computation node reservation period displayed on the calendar, you can view the details of the computation node (scheduled start time of use, scheduled end time of use, status, etc.).

With the above Steps 1 to 4, the compute node is reserved.
Thereafter, the startup process of the reserved computation node is executed at the set “Start Time” and the computation node can be used until the “End Time” is reached.

NOTICE!
The start-up of a reserved computation node usually takes 5~15 minutes.

NOTICE!
After the “End Time” is reached, the configuration environment of the relevant compute nodes and all stored data will be discarded.
Please be sure to back up your data in advance.Confirm in advance whether or not a backup is available and if so, whether or not it is required.

2.3. Change reserved compute nodes

This section describes the operation to change the reserved period after the calculation node has been reserved.
Changes to the reserved period can be made by updating the scheduled start time and scheduled end time for compute nodes whose Status is Reserved and not yet one hour before the scheduled start time (Start Time).
To change the reserved period, first select 〈Cloud Servers1〉 from the left menu bar to open the 【Cloud Servers】 screen. In the 【Cloud Servers】 screen, a list of the computation nodes that have been reserved so far and the computation nodes that have been launched are displayed. From the list, identify the computation node for which you wish to change the reserved period, and click the [Detail] button.

TIPS!

• Changes to a server’s reserved time period can only be performed by users who are members of the user group that made the reservation (the same user group wallet).
  
• For example, if users belonging to multiple user groups A and B make a reservation for any server from user group A (user group wallet A), only users belonging to user group A (user group wallet A) will be able to change the reserved period, and users belonging to user Group B (User Group Wallet B) cannot change the reserved period.

Moves to the 【Details of individual calculation nodes】 screen, where details of individual calculation nodes are displayed.
Go to the bottom of the screen and press the [Change Reservation] button.

[Change Reservation]ボタンを押下後、再度確認の【Change Reservation】のポップアップ画面が表示されます。

The following information will be displayed on the 【Change Reservation】 pop-up screen.

If you fill in the “New Start Time” or “New End Time” fields above, the “Time Extended” and “Pre-Calculated Points” at the bottom of the screen will show the new start time, the points needed to process the change, and the point balance before and after the change. The “Time Extended” and “Pre-Calculated Points” columns at the bottom will display the new time, the points required for the change, and the point balance before and after the change.
After reviewing the above information, click the “Change Reservation” button at the bottom of the page to change the reservation period.

The screen will move to the 【Final Confirmation: Change Reservation】 screen, where a warning message will be displayed.
After confirming the displayed information, click the [Change Reservation] button at the bottom of the screen to execute the change. When the process is completed, “Start Time” and “End Time” will be updated.

TIPS!

• If the User Group’s point balance is less than the required number of points when changing the reservation period for a server, the reservation period cannot be extended.
  
• Changes in the reservation period for a server depend on the reservation status before and after the reserved computation node.

This is the end of the explanation about changing the reservation period of a computation node.

2.4. Cancellation of reserved compute node

This section describes how to cancel the reservation of a reserved computation node.
Reservations can be canceled by canceling a reservation for a compute node whose Status is Reserved and which has not yet reached ten minutes before the scheduled start time (Start Time).
To cancel a reservation, first select 〈Cloud Servers〉 from the left menu bar to open the 【Cloud Servers】 screen. In the 【Cloud Servers】 screen, a list of the computation nodes that have been reserved so far and the computation nodes that have been launched will be displayed. Confirm the computation node whose reservation you want to cancel from the list, and click the [Detail] button.

TIPS!

• Cancellation of a reservation can only be performed by a user who is a member of the user group that made the reservation (in the same user group wallet).
  
• For example, if users belonging to multiple user groups A and B make a reservation for any server from user group A (user group wallet A), only the user belonging to user group A (user group wallet A) can cancel the reservation. Group B (User Group Wallet B) cannot cancel the reservation.

Moves to the 【Details of individual calculation nodes】 screen, where details of individual calculation nodes are displayed.
Go to the bottom of the screen and press the [Cancel Reservation] button.

After clicking the [Cancel Reservation] button, a confirmation pop-up screen will appear with a warning message. After confirming the displayed information, click the [Cancel Reservation] button on the pop-up screen to cancel the reservation for the computation node.

TIPS!

• Points will be returned when the reservation is cancelled.
  
• For point return, please click Point Refunds
  

2.5. Use of compute nodes

This section describes the procedure for using a compute node after it has been started up.
Use of a compute node can be done when the following has already been done.

• Preparation of the connection key (private key file) to the login node
  (Information from us at the start of use)
• Reserving the compute nodes (see 2.2.)
• Startup of reserved computation nodes
• Prepare the client PC (which will be the source of the ssh connection)

2.5.1. check the Alias of the compute nodes

First, confirm the Alias required to connect from the login node to the compute nodes by the following procedure.

Log in to Cloud Bouquet and display the 【Cloud Servers】 screen from the left menu.
(For details on the 【Cloud Servers】 screen, please refer to 3.2. On the [Cloud Servers] screen, click the [Detail] button of the compute nodes you want to login.

TIPS!
The compute node you want to log in must have the Status as Running.

Moves to the [Server Name:~] screen (compute node details screen), where detailed information about the compute node is displayed. < br>

The information displayed is as follows.

Confirm the contents of Alias (alias name of compute node) among the displayed information and go to 2.5.2..

2.5.2. Connect to login node

Next, we explain how to connect to a login node. You can connect to a compute node via a login node. To connect to the login node, please refer to Information provided by us when you start using the service. The following is an example.

• e.g.) Login key: sample.key
• Example) Login node and account: sample@morgenrot.cloud
• Example) Port number: 12345
  

Based on the above information, connect to the login node from the client PC using the ssh command.
(Please change the key reference according to your client PC’s environment.)

ssh -i . /sample.key sample@morgenrot.cloud -p 12345

If you can make an ssh connection without any problems, you are done checking the connection to the login node.

If the ssh connection is successful, copy the login key onto the login node in preparation for the next step. (Cloud Bouquet uses the same authentication key between the login node and the compute node as between the client PC and the login node. In order to enable the connection from the login node to the compute node, a copy of the login key to the login node is required.)
The following is an example command to perform the copy from the client PC to the login node. (Please change the destination/reference of the key according to your environment.)

scp -i . /sample.key -P 12345 . /sample.key sample@morgenrot.cloud:~

This completes the confirmation of the connection to the login node and preparation for connection to the compute node.

TIPS!
One of the most common login errors we see with SSH connections is that the key file (sample.key) does not have proper permissions to be referenced.

ll sample.key

Please make sure that the execution permissions are restricted as follows.

-rw-------@ 1 user user  399B  4  1 10:00 sample.key

If execution rights are not restricted as follows,

-rwxrwxrwx@ 1 user user 399B 4 1 10:00 sample.key

Please change the execution privilege by chmod command.

chmod 600 sample.key

2.5.3. Connection from login node to compute node

This section describes how to connect from a login node to a compute node using the Alias (alias name of the compute nodes) confirmed in 2.5.1.. The following information is used as an example.

• e.g.) Alias (alias name of compute nodes): sample-alias

After logging in to the login node from a client PC as described in 2.5.2., execute the following command on the login node. (Assume that you have already copied the login key onto the login node.)

ssh -i . /sample.key ubuntu@sample-alias

The above will log you into the compute node.
After logging in, you can use the compute node until the compute node termination operation is performed.

NOTICE!
Reboot command (“sudo reboot”) is available on the compute node.
However, the shutdown command is not available on the compute node. But if you execute the shutdown command (“sudo shutdown”), you will not be able to reboot from your side. Please avoid using the shutdown command. If you have executed the shutdown command, please contact us. (Cloud Bouquet Contact)

2.6. Extension of compute node usage time

This section describes the operations used to extend the usage time of a compute node.
Extending the usage time can be performed by updating the End Time for a compute node whose Status is Running and whose End Time has not yet been reached.

To extend the usage time of a compute node, first select “Cloud Servers” from the left menu bar to open the “Cloud Servers” window. The [Cloud Servers] screen displays a list of the compute nodes that have been launched so far. Confirm the compute nodes whose usage time you want to extend from the list, and click the [Detail] button.

TIPS!

• Extending server usage time can only be done from the same user group (same user group wallet) as when you started using it.
• For example, if users belonging to multiple user groups A and B start using a given server from user group A (user group wallet A), the extension can only be performed from user group A (user group wallet A) and not from user group B ( User Group Wallet B) cannot perform the extension operation.

The user will be redirected to the [Individual Calculation Node Details] screen, where the details of the individual calculation node will be displayed.
Go to the bottom of the screen and press the [Extend] button.

After pressing the [Extend] button, a confirmation [Server Time Extension] pop-up screen will appear again.

The [Server Time Extension] pop-up screen will display the following information.

If you fill in the “New end Time” field above, the “Time Extended” and “Pre-Calculated Points” at the bottom will show the new extension time, the points required for the extension process, and the point balance before and after the process. The “Total Time of Termination” and “Precalculated Points” columns at the bottom will display the new extended time, the points required for the extension, and the point balance before and after the transaction.
After reviewing the above information, click the “Extend” button at the bottom of the screen to execute the extension.

You will be redirected to the [Final Confirmation: Server Time Extention] screen, where you will see a warning message.

After confirming the displayed contents, if you want to execute the extension, click the [Extend] button at the bottom. When the process is complete, the End Time will be updated.

TIPS!

• If the point balance of the user group in question is less than the required number of points when extending the server, the extension will not be possible
• Changes in the reservation period for a server depend on the reservation status before and after the reserved computation node.

This is the end of the explanation about the extension of compute nodes.

2.7. Termination of compute nodes

This section describes the operations for terminating the use of a compute node.

TIPS!

• In the event of a server termination operation, points will be returned multiplied by a fixed return rate based on the specifications of the For point return, please click Point Refunds.

Log in to Cloud Bouquet and display the [Cloud Server] screen from the left menu bar. Click the [Detail] button of the calculation node you want to terminate on the [Cloud Server] screen.

TIPS!

• On the [Cloud Server] screen, only compute nodes whose Status is Running can be terminated.
• As with the extension operation, the server termination operation can only be performed from the same user group (same user group wallet) as when you started using the server.

The screen will be redirected to the [Details of individual compute nodes] screen, where the details of individual compute nodes will be displayed.
Go to the bottom of the screen and press the [Terminate] button. After pressing the [Terminate] button, a confirmation pop-up screen will appear with a warning message again. After confirming the displayed contents, click the [Execute] button on the pop-up screen to terminate the use of the compute nodes.

NOTICE!
After clicking the [Execute] button, the configuration environment of the relevant compute node and all saved data will be discarded.
Please make sure to confirm in advance whether or not a backup is available or required.

3. Checking the usage status

Cloud Bouquet allows you to check the history of compute nodes, including compute nodes launched in the past, including their usage fees. This section describes the fee structure regarding compute nodes and how to check the history of compute nodes.

3.1. Fee structure of this service

First, the fee structure of this service is explained.
The basic fee structure for the Service is as follows.

• The fee for this service (point consumption) is charged for login nodes, compute nodes, etc. Login nodes: servers located in each region.

  • Login node: A server installed in each region. 1 login node/region or less will not incur a fee. 2 login nodes/region or more will incur a fee.
  • compute nodes: Charges are based on the time from startup to shutdown, with a separately set unit price. The unit price varies depending on the compute node specifications and storage capacity.
  • Storage node: Available only when a storage node is installed in addition to the login node and compute nodes in accordance with the customer’s request, and a fee is charged.
    

• Point Consumption for Compute Node Use

  • The number of points required to use a compute node is calculated based on a separately determined unit price and time of use.
  • The unit price is set per hour. The unit price can be confirmed on the screen when reserving a compute node, in the history of the compute nodes, etc.
  • The time used is from “Start Time of the computation node you entered when you reserved the computation node” to “End Time of the compute nodes entered at the time of reservation of the compute nodes”.
  • The number of points consumed can be checked during the process of reservation operation of a compute node. The time spent for point consumption is counted in hours, with each 3600 seconds counted as one hour. For fractional hours, 1 to 3600 seconds is treated as one hour. Fractional hours are counted as one hour. (For example, 1 hour for 1 to 3600 seconds of operation time, 2 hours for 3601 to 7200 seconds, and so on.)
  • The compute node will start up at the Start Time, and will be available 5-15 minutes after the start of the startup process. It takes about 2 minutes for the status to change to Running on Cloud Bouquet. After that, it will be available until the scheduled end time of the compute node (or until the extended scheduled end time if the scheduled end time is extended).
  • For operating conditions, please refer to About Points and Wallets.
    
    

• About Login Nodes and Storage Nodes

  • Login node: If more than 1 login node/region is required, it can be installed as requested by the customer. Login node specifications are also available upon request.
  • Storage Nodes: Storage nodes can be installed upon customer request. Storage Nodes: Storage nodes can be installed upon customer request, specifications also available upon request.

TIPS!
Additional login nodes and specifications are available upon customer request.
We are happy to assist you in adding or modifying login nodes, or in using storage nodes. (Cloud Bouquet Contact)

3.2. Checking the usage of compute nodes

Cloud Bouquet allows you to check the history of compute nodes.
This section describes how to check the usage of individual compute nodes.

The utilization status of individual compute nodes can be viewed from the [Cloud Servers] screen.

The items shown are as follows.

The “Status” (the operating state of the compute node) displays one of the following: Reserved, Cancelled, Running, Preparing, Finished, or Error. Reserved compute nodes are hatched in blue. The running compute nodes is displayed in red for less than 6 hours, orange for between 6 and 24 hours, and yellow for between 24 and 72 hours, depending on the time remaining relative to the “End Time”. A legend for each color is displayed in the upper right corner of the screen under “Reserved” and “Remaining time until server termination”.

In addition, the Cloud Servers screen allows you to filter the data displayed by using the Columns or Filters menus located near the upper left corner of the screen.
For example, the <Columns> menu allows you to select whether or not to display table items.

Some items are hidden by default in the 【Cloud Servers】 screen.
The hidden items are as follows.

The <Filters> menu allows filtering by data congruency for any of the table items.

TIPS!
In the initial state of the [Cloud Servers] screen, the settings for displaying Reserve, Running and Preparing compute nodes information (The display check is turned on in the [Status] menu) are as follows. The following is the setting for displaying the compute nodes information.
To display information on all compute nodes, including those that have been executed in the past, set the checkboxes for Cancelled, Finished, and Error to ON in the Status menu.

TIPS!
The data displayed on the [Cloud Servers] screen is split into multiple lines if an item has multiple values. For example, compute node X launched by users belonging to multiple user groups A and B will be displayed on two lines: “compute node X of user group A” and “compute node X of user group B” (actually one node).

The information displayed is as follows.

By following the above procedure, you can check the usage status of individual compute nodes.

3.3. Checking the usage of the Service as a whole

This section describes how to check the usage of the Service as a whole. The usage status of the entire Service can be checked from the history of the compute node.
The history of a compute node can be checked by launching the [Usage History] screen from the left menu bar.

The [Usage History] screen allows you to view the history of a compute node. The [Usage History] screen displays usage history information for each individual server group associated with a user group. The month to be displayed can be selected from the drop-down menu in the Month column near the upper left corner of the screen. You can also filter the data displayed by using the “Columns” menu or the “Filters” menu.

The following items are displayed as usage history information.

TIPS!
In some cases, such as when a user belongs to multiple user groups, the data displayed on the [Usage History] screen will show multiple lines. For example, if a user belongs to multiple user groups A and B, and both user groups A and B can use server group X, two lines of information corresponding to “Server Group X for User Group A” and “Server Group X for User Group B” will be displayed.

Clicking the [Detail] button will display information about the compute nodes associated with a particular server group.
The selected server group is displayed in the “Selected Server Group:” column at the top.
You can select the month to display by using the drop-down menu in the Month column near the upper left corner of the screen. You can also filter the data displayed by using the “Columns” menu or the “Filters” menu.

The following items are displayed as usage history information.

4. Confirmation of Notices

4.1. Notification by Notification Screen

Cloud Bouquet will provide you with notices regarding your use, etc., as necessary.
When a notification is posted, the bell mark near the upper right corner of the screen will display a “!” will be displayed in the upper right corner of the screen. To view the contents, press the bell mark.



When the bell mark is pressed, the [Notifications] modal screen will appear. Here, you can check the date, time, and title of each notification. To view specific details, click on the title of the notification.



Press the title to review the content of the selected notification item.
This is all about how to check notifications.

TIPS!
Notifications will include information about system maintenance and updates, information about outages and recovery, and information about the server. Please check the contents of the notifications as they are related to your use of the system.

4.2. Notification by e-mail

Cloud Bouquet provides email notifications at specific times.
See below for the content and timing of notifications.

That’s all for how to use compute nodes (for administrators and users).