Thank you Tim,

I didn't know the dashboard is in the /usr/share TT...

By the way, I tried as you showed, but it showed Connection Refused.

So I had thought maybe firewall something like that can impact to this, I disabled iptables, ip6tables, and firewalld.
However, the result was same...

image.png

And I'm not sure what below figure means,  but attach anyway. Please it could be the key of the problem...

image.png


Best Regards,
Jaewook.


2019년 2월 20일 (수) 오후 3:23, xiongzhiwei@baicells.com <xiongzhiwei@baicells.com>님이 작성:
Hi Jaewook,
There is no horizon directory in /etc,  openstack-dashboard was installed in /usr/share/.
Can you ignore to access the installation directory and try to test with 'wget' command?
Just like below:

controller-0:~$ wget http://10.10.10.2/dashboard
--2019-02-20 06:15:23--  http://10.10.10.2/dashboard
Connecting to 10.10.10.2:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-02-20 06:15:23 ERROR 404: Not Found.

controller-0:~$ wget http://10.10.10.2/
--2019-02-20 06:15:38--  http://10.10.10.2/
Connecting to 10.10.10.2:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://10.10.10.2/auth/login/?next=/ [following]
--2019-02-20 06:15:38--  http://10.10.10.2/auth/login/?next=/
Connecting to 10.10.10.2:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9309 (9.1K) [text/html]
Saving to: ‘index.html’

100%[==================================================================================================================================================================================================>] 9,309       --.-K/s   in 0s      

2019-02-20 06:15:38 (55.8 MB/s) - ‘index.html’ saved [9309/9309]

controller-0:~$ wget http://192.168.107.232
--2019-02-20 06:16:31--  http://192.168.107.232/
Connecting to 192.168.107.232:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://192.168.107.232/auth/login/?next=/ [following]
--2019-02-20 06:16:31--  http://192.168.107.232/auth/login/?next=/
Connecting to 192.168.107.232:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9309 (9.1K) [text/html]
Saving to: ‘index.html.1’

100%[==================================================================================================================================================================================================>] 9,309       --.-K/s   in 0s      

2019-02-20 06:16:31 (137 MB/s) - ‘index.html.1’ saved [9309/9309]

BR
Tim Xiong
 
From: Jaewook Oh
Date: 2019-02-20 14:13
Subject: Re: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration
Hello StarlingX Team and Tim,

I'm still struggling to deploy StarlingX normally, but it seems it will never succeed.
I used the latest boot image, Feb 18th.

However the symptom is same.
And I found that there were no horizon directory in /etc/.
image.png

Do I need to install horizon manually?

BR,
Jaewook.

2019년 2월 19일 (화) 오후 8:52, Jaewook Oh <kyle.oh95@gmail.com>님이 작성:
Unfortunately, still I cannot access dashboard.

I'll try another latest boot image.

Thank you for all helps :)

BR.
Jaewook.

2019년 2월 19일 (화) 오후 4:16, xiongzhiwei@baicells.com <xiongzhiwei@baicells.com>님이 작성:
Hi Jaewook,

My ip setting is as below:
Actually, I had used three physical interface, enp2s0f0 is OAM inf with default ip 10.10.10.2/24,  because it is not inconvenient in my operation room, so I had configured enp2s0f1 for my romote access.
I can access the dashboard both with ip 10.10.10.2 in lab and 192.168.107.232/22 in my operation room.
The third inf enp2s0f2 is used to data interface, I had created three VMs and network worked normally.


controller-0:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet 192.168.204.3/28 brd 192.168.204.15 scope host lo
       valid_lft forever preferred_lft forever
    inet 169.254.202.2/24 scope host lo
       valid_lft forever preferred_lft forever
    inet 192.168.204.2/28 scope host secondary lo
       valid_lft forever preferred_lft forever
    inet 192.168.204.5/28 scope host secondary lo
       valid_lft forever preferred_lft forever
    inet 192.168.204.10/28 scope host secondary lo
       valid_lft forever preferred_lft forever
    inet 192.168.204.6/28 scope host secondary lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp4s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:1b:21:bc:ff:a8 brd ff:ff:ff:ff:ff:ff
3: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether f8:75:88:6e:8f:e2 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.2/24 brd 10.10.10.255 scope global enp2s0f0
       valid_lft forever preferred_lft forever
    inet6 fe80::fa75:88ff:fe6e:8fe2/64 scope link 
       valid_lft forever preferred_lft forever
4: enp2s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether f8:75:88:6e:8f:e3 brd ff:ff:ff:ff:ff:ff
    inet 192.168.107.232/22 brd 192.168.107.255 scope global enp2s0f1
       valid_lft forever preferred_lft forever
    inet6 fe80::fa75:88ff:fe6e:8fe3/64 scope link 
       valid_lft forever preferred_lft forever
6: enp2s0f3: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether f8:75:88:6e:8f:e5 brd ff:ff:ff:ff:ff:ff
7: ovs-netdev: <BROADCAST,PROMISC> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 8e:da:6c:1b:fd:15 brd ff:ff:ff:ff:ff:ff
8: br-int: <BROADCAST,PROMISC> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether f6:df:04:bf:a1:43 brd ff:ff:ff:ff:ff:ff
12: br-phy0: <BROADCAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether f8:75:88:6e:8f:e4 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fa75:88ff:fe6e:8fe4/64 scope link 
       valid_lft forever preferred_lft forever
13: lldp0d64ae5d-22: <BROADCAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 96:e0:03:51:17:6d brd ff:ff:ff:ff:ff:ff
    inet6 fe80::94e0:3ff:fe51:176d/64 scope link 
       valid_lft forever preferred_lft forever


BR
Tim Xiong
 
From: Jaewook Oh
Date: 2019-02-19 15:00
Subject: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration
Hello Tim,

thanks for your answer :)

However, still I cannot access to the dashboard.

I deployed StarlingX 3 times again, but the situation never changes..

If you don't mind, can I see your ip setting with (ip a command)?

Best Regards,
Jaewook.

2019년 2월 19일 (화) 오후 3:56, xiongzhiwei@baicells.com <xiongzhiwei@baicells.com>님이 작성:
Hi Jaewook,

I just finished stx all-in-one simplex on Bearmetal last week. The horizon service had been installed defaultly and you should be able to access the dashboard now.
Your service list is same as mine.

[wrsroot@controller-0 ~(keystone_admin)]$ openstack service list
+----------------------------------+------------+-----------------+
| ID                               | Name       | Type            |
+----------------------------------+------------+-----------------+
| c51dfde10adf4445a78113ad6e648b9a | barbican   | key-manager     |
| df07161f527b483292ac5aa5ed722687 | keystone   | identity        |
| 744183df128d414f97390fb70fcac72f | sysinv     | platform        |
| b9730f2e673443e4a6d003a7dad1d220 | fm         | faultmanagement |
| 5d7855696b1f440b8401670e1df6cb28 | glance     | image           |
| 814a777c22884c97ab44baf0a4c2c669 | aodh       | alarming        |
| 68362243cc214c4181a15e583894e495 | placement  | placement       |
| 375cfb87c5f6449e81512ead128a513e | gnocchi    | metric          |
| 2643dadbe71b4fc68ad4daa7d9d3859f | nova       | compute         |
| f312a1c459c245c5a045c69688f695db | heat-cfn   | cloudformation  |
| cbf811729020470a81b3c7be0d453fc9 | neutron    | network         |
| 0fb46b24873648f9bac3a3e4d9f1f4e2 | patching   | patching        |
| 52db1ccfca9d4033be5f1180c50d8234 | ceilometer | metering        |
| 094935b6dee245278bffc3f7ee21e9e9 | vim        | nfv             |
| bc5297541def4f8b8881254af9896824 | smapi      | smapi           |
| a388667479484a04824f07a672a331eb | panko      | event           |
| 8c982073cd6c4d04b6ecb49e76650d2c | heat       | orchestration   |
| 38c0b001ef514af5b1ba6947bed1bc6c | cinderv3   | volumev3        |
| 98699ea84e4543b6b0808e24395542bb | cinderv2   | volumev2        |
| 253390980b274178b7a16844e2c7a826 | cinder     | volume          |
+----------------------------------+------------+-----------------+

BR
Tim Xiong

From: Jaewook Oh
Date: 2019-02-19 12:48
Subject: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration
Hello StarlingX Teams,

I found that the horizon dashboard project were not installed automatically when I deployed StarlingX all-in-one simplex on Baremetal.
Are there any reason for this problem..?
I used  "2019-Feb-08 03:40:29 bootimage.iso".

[wrsroot@controller-0 ~(keystone_admin)]$ openstack service list
+----------------------------------+------------+-----------------+
| ID                               | Name       | Type            |
+----------------------------------+------------+-----------------+
| f8b821fdd8e44d8484a3521ade041340 | barbican   | key-manager     |
| 6f34b6874b624604a7f8798b95743dc4 | keystone   | identity        |
| d31b2325f40e4ce88ca6974ee852eff6 | sysinv     | platform        |
| cb68c2d74dc34caf91dfc92c9b099d22 | fm         | faultmanagement |
| a7f2ae41f2ff45bd904012a0a53b63ec | glance     | image           |
| 3daea4e7507a4568a132579b4f30e4d6 | aodh       | alarming        |
| af6e9c3f185f498a8f8b7d1afaeaa06d | placement  | placement       |
| b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi    | metric          |
| 0e21d579ddee4f2dbfe98ff4069ce321 | nova       | compute         |
| 15067bfe219b4645973f7399099c47da | heat-cfn   | cloudformation  |
| ecf3478c84334c2ba647740bde190739 | neutron    | network         |
| 28973cbc638c41c6b99b5e77264a2aec | patching   | patching        |
| a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering        |
| 12b32e4a181a4684ab05be02b3726d0c | vim        | nfv             |
| a9c28c1889a347359a9b77edf53e5833 | smapi      | smapi           |
| 2697e71aa8dc4f8b8d96c72b32c89440 | panko      | event           |
| 57a5cb58128445b5819747271c095a89 | heat       | orchestration   |
| 10c93aecb5a84278b940da2f8c3a1721 | cinderv3   | volumev3        |
| b569ff8b77364311bbf3a5dee38dd614 | cinderv2   | volumev2        |
| 449ceb89f8fe40779dd65c5a9c867161 | cinder     | volume          |
+----------------------------------+------------+-----------------+

I thought horizon should also be installed with StarlingX's deployment.
If not, please let me know how can I install horizon in this StarlingX.

Thanks for help in advance :)

Best Regards,
Jaewook.


2019년 2월 12일 (화) 오후 2:54, Jaewook Oh <kyle.oh95@gmail.com>님이 작성:
Hello starlingx team,

I deployed Starlingx All-in-one simplex setting on my server,
it seems deployment was done well.
However I cannot access to the dashboard.

I used  "2019-Feb-08 03:40:29 bootimage.iso".


Following log is the service that are now enabled,
[wrsroot@controller-0 ~(keystone_admin)]$ system service-list
+-----+-------------------------------+--------------+----------------+
| id  | service_name                  | hostname     | state          |
+-----+-------------------------------+--------------+----------------+
| 68  | aodh-api                      | controller-0 | enabled-active |
| 69  | aodh-evaluator                | controller-0 | enabled-active |
| 70  | aodh-listener                 | controller-0 | enabled-active |
| 71  | aodh-notifier                 | controller-0 | enabled-active |
| 102 | barbican-api                  | controller-0 | enabled-active |
| 103 | barbican-keystone-listener    | controller-0 | enabled-active |
| 104 | barbican-worker               | controller-0 | enabled-active |
| 43  | ceilometer-agent-notification | controller-0 | enabled-active |
| 14  | cgcs-export-fs                | controller-0 | enabled-active |
| 10  | cgcs-fs                       | controller-0 | enabled-active |
| 16  | cgcs-nfs-ip                   | controller-0 | enabled-active |
| 35  | cinder-api                    | controller-0 | enabled-active |
| 38  | cinder-backup                 | controller-0 | enabled-active |
| 58  | cinder-ip                     | controller-0 | enabled-active |
| 56  | cinder-lvm                    | controller-0 | enabled-active |
| 36  | cinder-scheduler              | controller-0 | enabled-active |
| 37  | cinder-volume                 | controller-0 | enabled-active |
| 23  | dnsmasq                       | controller-0 | enabled-active |
| 5   | drbd-cgcs                     | controller-0 | enabled-active |
| 55  | drbd-cinder                   | controller-0 | enabled-active |
| 75  | drbd-extension                | controller-0 | enabled-active |
| 3   | drbd-pg                       | controller-0 | enabled-active |
| 6   | drbd-platform                 | controller-0 | enabled-active |
| 4   | drbd-rabbit                   | controller-0 | enabled-active |
| 77  | extension-export-fs           | controller-0 | enabled-active |
| 76  | extension-fs                  | controller-0 | enabled-active |
| 24  | fm-mgr                        | controller-0 | enabled-active |
| 27  | glance-api                    | controller-0 | enabled-active |
| 26  | glance-registry               | controller-0 | enabled-active |
| 108 | gnocchi-api                   | controller-0 | enabled-active |
| 109 | gnocchi-metricd               | controller-0 | enabled-active |
| 62  | guest-agent                   | controller-0 | enabled-active |
| 64  | haproxy                       | controller-0 | enabled-active |
| 45  | heat-api                      | controller-0 | enabled-active |
| 46  | heat-api-cfn                  | controller-0 | enabled-active |
| 47  | heat-api-cloudwatch           | controller-0 | enabled-active |
| 44  | heat-engine                   | controller-0 | enabled-active |
| 51  | horizon                       | controller-0 | enabled-active |
| 22  | hw-mon                        | controller-0 | enabled-active |
| 57  | iscsi                         | controller-0 | enabled-active |
| 25  | keystone                      | controller-0 | enabled-active |
| 50  | lighttpd                      | controller-0 | enabled-active |
| 2   | management-ip                 | controller-0 | enabled-active |
| 20  | mtc-agent                     | controller-0 | enabled-active |
| 28  | neutron-server                | controller-0 | enabled-active |
| 9   | nfs-mgmt                      | controller-0 | enabled-active |
| 29  | nova-api                      | controller-0 | enabled-active |
| 63  | nova-api-proxy                | controller-0 | enabled-active |
| 31  | nova-conductor                | controller-0 | enabled-active |
| 33  | nova-console-auth             | controller-0 | enabled-active |
| 34  | nova-novnc                    | controller-0 | enabled-active |
| 83  | nova-placement-api            | controller-0 | enabled-active |
| 30  | nova-scheduler                | controller-0 | enabled-active |
| 48  | open-ldap                     | controller-0 | enabled-active |
| 82  | panko-api                     | controller-0 | enabled-active |
| 52  | patch-alarm-manager           | controller-0 | enabled-active |
| 7   | pg-fs                         | controller-0 | enabled-active |
| 15  | platform-export-fs            | controller-0 | enabled-active |
| 11  | platform-fs                   | controller-0 | enabled-active |
| 17  | platform-nfs-ip               | controller-0 | enabled-active |
| 12  | postgres                      | controller-0 | enabled-active |
| 65  | pxeboot-ip                    | controller-0 | enabled-active |
| 13  | rabbit                        | controller-0 | enabled-active |
| 8   | rabbit-fs                     | controller-0 | enabled-active |
| 49  | snmp                          | controller-0 | enabled-active |
| 19  | sysinv-conductor              | controller-0 | enabled-active |
| 18  | sysinv-inv                    | controller-0 | enabled-active |
| 59  | vim                           | controller-0 | enabled-active |
| 60  | vim-api                       | controller-0 | enabled-active |
| 61  | vim-webserver                 | controller-0 | enabled-active |
+-----+-------------------------------+--------------+----------------+

As you can see, I cannot find #1 service (oam-ip), and I think this is one of the main reasons.

And also I had a problem when I followed the installation instruction.

[wrsroot@controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan
[wrsroot@controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a
[wrsroot@controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a

Above instruction was not naturally worked, I mean the third command, 'host-if-modify' failed with the message "DataNetwork providernet-a could not be found."

So I googled and I figured out I should command 
$ system datanetwork-add providernet-a vlan
first.

But I remember when my first deployment succeed, I didn't need to use that command at all. (The deployment was implemented on Jan.)

Any help is appreciated, thank you for your help in advance.

Best Regards,
Jaewook.

================================================
Jaewook Oh (오재욱)
IISTRC - Internet Infra System Technology Research Center
369 Sangdo-ro, Dongjak-gu,
06978, Seoul, Republic of Korea


--
================================================
Jaewook Oh (오재욱)
IISTRC - Internet Infra System Technology Research Center
369 Sangdo-ro, Dongjak-gu,
06978, Seoul, Republic of Korea


--
================================================
Jaewook Oh (오재욱)
IISTRC - Internet Infra System Technology Research Center
369 Sangdo-ro, Dongjak-gu,
06978, Seoul, Republic of Korea


--
================================================
Jaewook Oh (오재욱)
IISTRC - Internet Infra System Technology Research Center
369 Sangdo-ro, Dongjak-gu,
06978, Seoul, Republic of Korea


--
================================================
Jaewook Oh (오재욱)
IISTRC - Internet Infra System Technology Research Center
369 Sangdo-ro, Dongjak-gu,
06978, Seoul, Republic of Korea


--
================================================
Jaewook Oh (오재욱)
IISTRC - Internet Infra System Technology Research Center
369 Sangdo-ro, Dongjak-gu,
06978, Seoul, Republic of Korea