Meluncurkan sebuah instance pada jaringan self-service

Meluncurkan sebuah instance pada jaringan self-service

Tentukan opsi instance

Untuk memulai sebuah instance, Anda harus setidaknya menentukan flavor, nama image, jaringan, grup keamanan, key, dan nama instance.

  1. Pada controller node, dapatkan sumber kredensial demo untuk mendapatkan akses ke user-only CLI commands:

    $ . demo-openrc
    
  2. Flavor menentukan profil alokasi sumber daya virtual yang meliputi prosesor, memori, dan penyimpanan.

    Daftar flavor yang tersedia:

    $ openstack flavor list
    
    +----+---------+-----+------+-----------+-------+-----------+
    | ID | Name    | RAM | Disk | Ephemeral | VCPUs | Is Public |
    +----+---------+-----+------+-----------+-------+-----------+
    | 0  | m1.nano |  64 |    1 |         0 |     1 | True      |
    +----+---------+-----+------+-----------+-------+-----------+
    

    Catatan

    Anda juga dapat referensi flavor dengan ID.

  3. Daftar image yang tersedia:

    $ openstack image list
    
    +--------------------------------------+--------+--------+
    | ID                                   | Name   | Status |
    +--------------------------------------+--------+--------+
    | 390eb5f7-8d49-41ec-95b7-68c0d5d54b34 | cirros | active |
    +--------------------------------------+--------+--------+
    

    Instance ini menggunakan image cirros.

  4. Daftar jaringan yang tersedia:

    $ openstack network list
    
    +--------------------------------------+-------------+--------------------------------------+
    | ID                                   | Name        | Subnets                              |
    +--------------------------------------+-------------+--------------------------------------+
    | 4716ddfe-6e60-40e7-b2a8-42e57bf3c31c | selfservice | 2112d5eb-f9d6-45fd-906e-7cabd38b7c7c |
    | b5b6993c-ddf9-40e7-91d0-86806a42edb8 | provider    | 310911f6-acf0-4a47-824e-3032916582ff |
    +--------------------------------------+-------------+--------------------------------------+
    

    Instance ini menggunakan jaringan self-service selfservice. Namun, Anda harus referensi jaringan ini menggunakan ID bukan nama.

  5. Daftar grup keamanan yang tersedia:

    $ openstack security group list
    
    +--------------------------------------+---------+------------------------+
    | ID                                   | Name    | Description            |
    +--------------------------------------+---------+------------------------+
    | dd2b614c-3dad-48ed-958b-b155a3b38515 | default | Default security group |
    +--------------------------------------+---------+------------------------+
    

    Instance ini menggunakan grup keamanan default.

  6. Peluncuran instance:

    Ganti SELFSERVICE_NET_ID dengan ID dari jaringan selfservice.

    $ openstack server create --flavor m1.nano --image cirros \
      --nic net-id=SELFSERVICE_NET_ID --security-group default \
      --key-name mykey selfservice-instance
    
    +--------------------------------------+---------------------------------------+
    | Field                                | Value                                 |
    +--------------------------------------+---------------------------------------+
    | OS-DCF:diskConfig                    | MANUAL                                |
    | OS-EXT-AZ:availability_zone          |                                       |
    | OS-EXT-STS:power_state               | 0                                     |
    | OS-EXT-STS:task_state                | scheduling                            |
    | OS-EXT-STS:vm_state                  | building                              |
    | OS-SRV-USG:launched_at               | None                                  |
    | OS-SRV-USG:terminated_at             | None                                  |
    | accessIPv4                           |                                       |
    | accessIPv6                           |                                       |
    | addresses                            |                                       |
    | adminPass                            | 7KTBYHSjEz7E                          |
    | config_drive                         |                                       |
    | created                              | 2016-02-26T14:52:37Z                  |
    | flavor                               | m1.nano                               |
    | hostId                               |                                       |
    | id                                   | 113c5892-e58e-4093-88c7-e33f502eaaa4  |
    | image                                | cirros (390eb5f7-8d49-41ec-95b7-68c0d |
    |                                      | 5d54b34)                              |
    | key_name                             | mykey                                 |
    | name                                 | selfservice-instance                  |
    | os-extended-volumes:volumes_attached | []                                    |
    | progress                             | 0                                     |
    | project_id                           | ed0b60bf607743088218b0a533d5943f      |
    | properties                           |                                       |
    | security_groups                      | [{u'name': u'default'}]               |
    | status                               | BUILD                                 |
    | updated                              | 2016-02-26T14:52:38Z                  |
    | user_id                              | 58126687cbcc4888bfa9ab73a2256f27      |
    +--------------------------------------+---------------------------------------+
    
  7. Periksa status instance Anda:

    $ openstack server list
    
    +--------------------------------------+----------------------+--------+------------------------+
    | ID                                   | Name                 | Status | Networks               |
    +--------------------------------------+----------------------+--------+------------------------+
    | 113c5892-e58e-4093-88c7-e33f502eaaa4 | selfservice-instance | ACTIVE | selfservice=172.16.1.3 |
    | 181c52ba-aebc-4c32-a97d-2e8e82e4eaaf | provider-instance    | ACTIVE | provider=203.0.113.103 |
    +--------------------------------------+----------------------+--------+------------------------+
    

    Status perubahan dari BUILD ke ACTIVE ketika proses membangun berhasil menyelesaikan.

Mengakses instance menggunakan konsol virtual

  1. Mendapatkan URL sesi Virtual Network Computing (VNC) instance Anda dan mengaksesnya dari web browser:

    $ openstack console url show selfservice-instance
    
    +-------+---------------------------------------------------------------------------------+
    | Field | Value                                                                           |
    +-------+---------------------------------------------------------------------------------+
    | type  | novnc                                                                           |
    | url   | http://controller:6080/vnc_auto.html?token=5eeccb47-525c-4918-ac2a-3ad1e9f1f493 |
    +-------+---------------------------------------------------------------------------------+
    

    Catatan

    Jika web browser Anda berjalan pada host yang tidak dapat menyelesaikan nama host controller, Anda dapat mengganti controller dengan alamat IP dari antarmuka manajemen pada controller node Anda.

    Image CirrOS memasukkan otentikasi nama/password pengguna konvensional dan memberikan mandat ini pada prompt login. Setelah masuk ke CirrOS, kami sarankan Anda memverifikasi konektivitas jaringan menggunakan ping.

  2. Verifikasi akses ke gateway jaringan self-service:

    $ ping -c 4 172.16.1.1
    
    PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data.
    64 bytes from 172.16.1.1: icmp_req=1 ttl=64 time=0.357 ms
    64 bytes from 172.16.1.1: icmp_req=2 ttl=64 time=0.473 ms
    64 bytes from 172.16.1.1: icmp_req=3 ttl=64 time=0.504 ms
    64 bytes from 172.16.1.1: icmp_req=4 ttl=64 time=0.470 ms
    
    --- 172.16.1.1 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2998ms
    rtt min/avg/max/mdev = 0.357/0.451/0.504/0.055 ms
    
  3. Verifikasi akses ke internet:

    $ ping -c 4 openstack.org
    
    PING openstack.org (174.143.194.225) 56(84) bytes of data.
    64 bytes from 174.143.194.225: icmp_req=1 ttl=53 time=17.4 ms
    64 bytes from 174.143.194.225: icmp_req=2 ttl=53 time=17.5 ms
    64 bytes from 174.143.194.225: icmp_req=3 ttl=53 time=17.7 ms
    64 bytes from 174.143.194.225: icmp_req=4 ttl=53 time=17.5 ms
    
    --- openstack.org ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3003ms
    rtt min/avg/max/mdev = 17.431/17.575/17.734/0.143 ms
    

Mengakses instance jarak jauh

  1. Buat floating IP address pada jaringan virtual provider:

    $ openstack floating ip create provider
    
    +-------------+--------------------------------------+
    | Field       | Value                                |
    +-------------+--------------------------------------+
    | fixed_ip    | None                                 |
    | id          | 3d05a9b1-b1af-4884-be1c-833a69744449 |
    | instance_id | None                                 |
    | ip          | 203.0.113.104                        |
    | pool        | provider                             |
    +-------------+--------------------------------------+
    
  2. Mengasosiasikan alamat IP mengambang dengan instance:

    $ openstack server add floating ip selfservice-instance 203.0.113.104
    

    Catatan

    Command ini tidak memberikan output.

  3. Periksa status alamat IP mengambang Anda:

    $ openstack server list
    
    +--------------------------------------+----------------------+--------+---------------------------------------+
    | ID                                   | Name                 | Status | Networks                              |
    +--------------------------------------+----------------------+--------+---------------------------------------+
    | 113c5892-e58e-4093-88c7-e33f502eaaa4 | selfservice-instance | ACTIVE | selfservice=172.16.1.3, 203.0.113.104 |
    | 181c52ba-aebc-4c32-a97d-2e8e82e4eaaf | provider-instance    | ACTIVE | provider=203.0.113.103                |
    +--------------------------------------+----------------------+--------+---------------------------------------+
    
  4. Memverifikasi konektivitas untuk instance melalui mengambang alamat IP dari controller node atau semua host pada jaringan fisik provider:

    $ ping -c 4 203.0.113.104
    
    PING 203.0.113.104 (203.0.113.104) 56(84) bytes of data.
    64 bytes from 203.0.113.104: icmp_req=1 ttl=63 time=3.18 ms
    64 bytes from 203.0.113.104: icmp_req=2 ttl=63 time=0.981 ms
    64 bytes from 203.0.113.104: icmp_req=3 ttl=63 time=1.06 ms
    64 bytes from 203.0.113.104: icmp_req=4 ttl=63 time=0.929 ms
    
    --- 203.0.113.104 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3002ms
    rtt min/avg/max/mdev = 0.929/1.539/3.183/0.951 ms
    
  5. Mengakses instance Anda menggunakan SSH dari controller node atau semua host pada jaringan fisik provider:

    $ ssh cirros@203.0.113.104
    
    The authenticity of host '203.0.113.104 (203.0.113.104)' can't be established.
    RSA key fingerprint is ed:05:e9:e7:52:a0:ff:83:68:94:c7:d1:f2:f8:e2:e9.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added '203.0.113.104' (RSA) to the list of known hosts.
    

Jika instance Anda tidak memulai atau tampaknya bekerja seperti yang Anda harapkan, lihat bagian Instance Boot Failures di OpenStack Operations Guide untuk informasi lebih lanjut atau menggunakan salah satu many other options untuk mencari bantuan. Kami ingin instalasi pertama Anda untuk bekerja!

Kembali ke Launch an instance.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.