Hi Team,
The command to get tokens mentioned in the below link works locally on StarlingX setup.
In order to get a token from a remote server, we need to add Host corresponding to each service in curl command
| curl -i -H "Content-Type: application/json" -H "Host: keystone.hsc-starlingx-company.com" -d '{ "auth": {
"identity": {
"methods": ["password"],
"password": {
"user": {
"name": "admin",
"domain": { "id": "default" },
"password": "Centos@123"
}
}
},
"scope": {
"project": {
"name": "admin",
"domain": { "id": "default" }
}
}
}
}' http://192.168.121.141:80/v3/auth/tokens
TOKEN=<Set token retrieved from above request>
curl -i http://192.168.121.141:80/v2.1/flavors -X GET -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token:${TOKEN}" -H "Host: nova.hsc-starlingx-company.com" | tail -1 | python -m json.tool
where 192.168.121.141 - OAM IP which is publicly accessible.
|
Query:
It is not practically possible to pass FQDN hostname for every service request in the URL.
So, is there any way StarlingX automatically routes the ingress request internally ?
Or
Can we install all the Openstack Helm Chart services on Nodeport?
Please suggest the best way to resolve the issue?
Regards
Anirudh Gupta
-----Original Message-----
From: Anirudh Gupta
Sent: 04 November 2019 09:02
To: Chen, Haochuan Z <haochuan.z.chen@intel.com>
Cc: starlingx-discuss@lists.starlingx.io
Subject: RE: Starlingx 2.0 Service Endpoints not publicly accessed from External Entities
Hi,
Image service is ready to use, but the issue is that it is installed inside docker container which I feel is not accessible from external source.
controller-0:~$ openstack endpoint list | grep glance
I have also configured helm endpoint domain from the below link and updated the wild card entry in dnsmasq.conf file on StarlingX machine
Similar is the case for every service.
Regards
Anirudh Gupta
-----Original Message-----
Sent: 04 November 2019 07:38
Subject: Starlingx 2.0 Service Endpoints not publicly accessed from External Entities
Hi Anirudh
Maybe you can check in this way to ensure image service is ready firstly.
$ export OS_CLOUD=openstack_helm
$ openstack endpoint list
BR!
Martin, Chen
SSP, Software Engineer
021-61164330
-----Original Message-----
Sent: Sunday, November 3, 2019 8:30 PM
Subject: Starlingx-discuss Digest, Vol 18, Issue 35
Send Starlingx-discuss mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..."
Today's Topics:
1. Canceled: Weekly StarlingX Test meeting - 9:00 Pacific time
(Cabrales, Ada)
2. Starlingx 2.0 Service Endpoints not publicly accessed from
External Entities (Anirudh Gupta)
3. StarlingX platform-integ-apps docker images
----------------------------------------------------------------------
Message: 1
Date: Fri, 1 Nov 2019 22:45:35 +0000
Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Test meeting -
9:00 Pacific time
Message-ID:
Content-Type: text/plain; charset="utf-8"
Updates will be requested offline
Weekly meetings on Tuesdays at 9am Pacific
o Dialing in from phone:
o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923
o Meeting ID: 342 730 236
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 3486 bytes
Desc: not available
------------------------------
Message: 2
Date: Sat, 2 Nov 2019 21:04:08 +0000
Subject: [Starlingx-discuss] Starlingx 2.0 Service Endpoints not
publicly accessed from External Entities
Message-ID:
Content-Type: text/plain; charset="utf-8"
Hi Team,
I am trying to integrate StarlingX 2.0 with Open Source Mano 6.0, but facing errors as the public endpoints for every services are not exposed.
I have also configured helm endpoint domain from the below link and updated the wild card entry in dnsmasq.conf file on StarlingX machine
I am getting error 503
code: 503\\n description: 'VIM Exception vimconnUnexpectedResponse EndpointNotFound: public\\n endpoint for image service not found
However this was not the case with StarlingX previous release 2018.10.
I had successfully integrated it.
This is because now the openstack services are now containerized and URL is not publicly exposed.
Can someone please update the steps in order to expose all services public endpoints outside StarlingX.
Regards
Anirudh Gupta
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual
or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing,
copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Sun, 03 Nov 2019 02:50:11 -0600
Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker
images
List of docker images required for "platform-integ-apps":
BUILD_ID="20191103T013000Z"
rabbitmq:3.7-management
k8s.gcr.io/kube-proxy:v1.16.2
k8s.gcr.io/kube-apiserver:v1.16.2
k8s.gcr.io/kube-controller-manager:v1.16.2
k8s.gcr.io/kube-scheduler:v1.16.2
k8s.gcr.io/etcd:3.3.15-0
k8s.gcr.io/coredns:1.6.2
quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic
quay.io/calico/node:v3.6.2
quay.io/calico/cni:v3.6.2
quay.io/calico/kube-controllers:v3.6.2
rabbitmq:3.7.13-management
rabbitmq:3.7.13
gcr.io/kubernetes-helm/tiller:v2.13.1
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0
openstackhelm/mariadb:10.2.18
quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11
quay.io/stackanetes/kubernetes-entrypoint:v0.3.1
mariadb:10.2.13
memcached:1.5.5
k8s.gcr.io/pause:3.1
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0
nginx:1.13.3
gcr.io/google_containers/defaultbackend:1.0
------------------------------
Subject: Digest Footer
_______________________________________________
Starlingx-discuss mailing list
------------------------------
End of Starlingx-discuss Digest, Vol 18, Issue 35
*************************************************
DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended
for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic
mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from
virus.