Atšķirības starp "Hostnet OpenStack Cloud instances izveidošana/en" versijām
No ''Hostnet Wiki''
| (2 starpversijas, ko mainījis viens dalībnieks, nav parādītas) | |||
| 22. rindiņa: | 22. rindiņa: | ||
* Choose Instance resources. Currently we can offer SSD on local disks or combination of disks which are indicated on resource menu. If the instance startup source is “ Image “ then the instance disk size will be the same as at the resources menu. If the instance startup source is "Volume", then the disk size will be the same, as it is defined on the disk combination. | * Choose Instance resources. Currently we can offer SSD on local disks or combination of disks which are indicated on resource menu. If the instance startup source is “ Image “ then the instance disk size will be the same as at the resources menu. If the instance startup source is "Volume", then the disk size will be the same, as it is defined on the disk combination. | ||
[[Attēls:Hpc_launch_instance_4.png]] | [[Attēls:Hpc_launch_instance_4.png]] | ||
| − | * Choose a network for your department. Network should have already been created. On how to set up a network and virtual routers, you can find information [[Hostnet_OpenStack_Cloud_virtuālā_tīkla_veidošana | Here]]. | + | * Choose a network for your department. Network should have already been created. On how to set up a network and virtual routers, you can find information [[Hostnet_OpenStack_Cloud_virtuālā_tīkla_veidošana/en | Here]]. |
[[Attēls:Hpc_launch_instance_5.png]] | [[Attēls:Hpc_launch_instance_5.png]] | ||
| − | * Select the SSH key. It must be made previously or already imported. More information about it can be found [[Hostnet_OpenStack_Cloud_ssh_atslēgas_ģenerēšana | Here]]. | + | * Select the SSH key. It must be made previously or already imported. More information about it can be found [[Hostnet_OpenStack_Cloud_ssh_atslēgas_ģenerēšana/en | Here]]. |
[[Attēls:Hpc_launch_instance_6.png]] | [[Attēls:Hpc_launch_instance_6.png]] | ||
* Instance is ready to run. Instance startup process will start by pressing the "Launch Instance". | * Instance is ready to run. Instance startup process will start by pressing the "Launch Instance". | ||
| − | * You need to add a public IP address to instance, this can be done in various ways, one of the options described [[Hostnet_OpenStack_Cloud_publiskās_ip_adreses_piešķiršana_instancei | here]]. | + | * You need to add a public IP address to instance, this can be done in various ways, one of the options described [[Hostnet_OpenStack_Cloud_publiskās_ip_adreses_piešķiršana_instancei/en | here]]. |
* After adding a public IP address, connection to the instance occurs with the SSH key. Linux and MacOS systems it is done with the command: | * After adding a public IP address, connection to the instance occurs with the SSH key. Linux and MacOS systems it is done with the command: | ||
Pašreizējā versija, 2017. gada 24. marts, plkst. 09.51
It is easy to create Instance with a few clicks in Hostnet OpenStack Cloud service. But first of all you have to decide on which drives your instance will work ( HDD SAS, HDD SATA vai SSD). Secondly do you need a new internal network and what are requirements about CPU and RAM? Below we will describe all possible options.
- You can Launch instance in section "Instance" by clicking on "Launch instance".
- Insert a name of new instance
- Select the system disk source. This is an important point because many possible configurations. Let's look at some of them:
- Choosing Instance launch source "Image", you need to specify the disk OS template, which can be found below. We describe the "Create New Volume" option variations:
- If the menu "Create New Volume" is "No", the instance will start on a physical server for local drives, which are the SSD. This is recommend if you require high-performance drive.
- If the menu "Create New Volume" is "Yes", the instance will start on disk array with SATA HDD connection. In addition you have to specify the desired size of the system disk (!!! for some server templates minimum disk size is more than 2 GB).
- Choosing Instance launch source "Snapshot Instance" it will start on local server SSD drives.
- Choosing Instance launch source "Volume", it is possible to run an instance of the disk volume that was created previously and which is marked as (Bootable). We recommend that you always choose the option "Delete Volume Instance on Delete" to "No". More information about how to create a SAS or SATA disk volume, you can find Here.
- Choosing Instance launch source "Volume Snapshot", the instance will be formed from the disk volume snapshot.
- Choosing Instance launch source "Image", you need to specify the disk OS template, which can be found below. We describe the "Create New Volume" option variations:
- Choose Instance resources. Currently we can offer SSD on local disks or combination of disks which are indicated on resource menu. If the instance startup source is “ Image “ then the instance disk size will be the same as at the resources menu. If the instance startup source is "Volume", then the disk size will be the same, as it is defined on the disk combination.
- Choose a network for your department. Network should have already been created. On how to set up a network and virtual routers, you can find information Here.
- Select the SSH key. It must be made previously or already imported. More information about it can be found Here.
- Instance is ready to run. Instance startup process will start by pressing the "Launch Instance".
- You need to add a public IP address to instance, this can be done in various ways, one of the options described here.
- After adding a public IP address, connection to the instance occurs with the SSH key. Linux and MacOS systems it is done with the command:
$ ssh -i cels_till_key
root@server_ip_address
For example:
$ ssh -i demo-ssh-key-1.pem root@89.111.XX.YYY
Some OS templates do not allow to connect as “root” user, if it happens, will appear message similar to our example with CentOS systems:
Please login as the user "centos" rather than the user "root".
To log in, use the user presented by the statement:
$ ssh -i demo-ssh-key-1.pem centos@89.111.XX.YYY
To connect from Windows systems using putty, you will have to Regenerate RSA key to putty to understandable version. How to do it: http://www.electrictoolbox.com/PuTTY-rsa-dsa-keys/




