[Starlingx-discuss] Starlingx 2.0 Service Endpoints not publicly accessed from External Entities
Anirudh Gupta
Anirudh.Gupta at hsc.com
Tue Nov 5 06:47:33 UTC 2019
Hi Team,
The command to get tokens mentioned in the below link works locally on StarlingX setup.
https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#rest-apis
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 at 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 at intel.com>
Cc: starlingx-discuss at 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
| 55b3d034819f4cecb8650779df6c543d | RegionOne | glance | image | True | internal | http://glance-api.openstack.svc.cluster.local:9292/ |
| a40b33d549bb4cac96f00ceb820aabb5 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ |
| c60c2fa05b94472d8c0e29aabced774b | RegionOne | glance | image | True | admin | http://glance-api.openstack.svc.cluster.local:9292/
I think that the public endpoint http://glance.openstack.svc.cluster.local:80 is not accessible from outside.
I have also configured helm endpoint domain from the below link and updated the wild card entry in dnsmasq.conf file on StarlingX machine
https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#configure-helm-endpoint-domain
Similar is the case for every service.
Regards
Anirudh Gupta
-----Original Message-----
From: Chen, Haochuan Z <haochuan.z.chen at intel.com<mailto:haochuan.z.chen at intel.com>>
Sent: 04 November 2019 07:38
To: Anirudh Gupta <Anirudh.Gupta at hsc.com<mailto:Anirudh.Gupta at hsc.com>>
Cc: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
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-----
From: starlingx-discuss-request at lists.starlingx.io<mailto:starlingx-discuss-request at lists.starlingx.io> <starlingx-discuss-request at lists.starlingx.io<mailto:starlingx-discuss-request at lists.starlingx.io>>
Sent: Sunday, November 3, 2019 8:30 PM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: Starlingx-discuss Digest, Vol 18, Issue 35
Send Starlingx-discuss mailing list submissions to
starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
To subscribe or unsubscribe via the World Wide Web, visit
https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.starlingx.io%2Fcgi-bin%2Fmailman%2Flistinfo%2Fstarlingx-discuss&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=3eG1Ca5bMgCpxKGy%2F9Vk9kKvatId0xjqz6YkkeQOx8E%3D&reserved=0
or, via email, send a message with subject or body 'help' to
starlingx-discuss-request at lists.starlingx.io<mailto:starlingx-discuss-request at lists.starlingx.io>
You can reach the person managing the list at
starlingx-discuss-owner at lists.starlingx.io<mailto:starlingx-discuss-owner at lists.starlingx.io>
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
(cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>)
----------------------------------------------------------------------
Message: 1
Date: Fri, 1 Nov 2019 22:45:35 +0000
From: "Cabrales, Ada" <ada.cabrales at intel.com<mailto:ada.cabrales at intel.com>>
To: "starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>"
<starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Cc: "Martinez Monroy, Elio" <elio.martinez.monroy at intel.com<mailto:elio.martinez.monroy at intel.com>>,
"'Seiler, Glenn'" <glenn.seiler at windriver.com<mailto:glenn.seiler at windriver.com>>, "Hernandez Gonzalez,
Fernando" <fernando.hernandez.gonzalez at intel.com<mailto:fernando.hernandez.gonzalez at intel.com>>, "'Komiyama, Takeo'"
<Takeo.Komiyama at windriver.com<mailto:Takeo.Komiyama at windriver.com>>, "Xu, YizhouX" <yizhoux.xu at intel.com<mailto:yizhoux.xu at intel.com>>,
"Armstrong, Robert H" <robert.h.armstrong at intel.com<mailto:robert.h.armstrong at intel.com>>, "Martinez Landa,
Hayde" <hayde.martinez.landa at intel.com<mailto:hayde.martinez.landa at intel.com>>, "Alonso, Juan Carlos"
<juan.carlos.alonso at intel.com<mailto:juan.carlos.alonso at intel.com>>, 'Peng Tan' <Peng.Tan at telus.com<mailto:Peng.Tan at telus.com>>,
"Gomez, Juan P" <juan.p.gomez at intel.com<mailto:juan.p.gomez at intel.com>>, "Sun, Austin"
<austin.sun at intel.com<mailto:austin.sun at intel.com>>, Banszel Martin <Martin.Banszel at tieto.com<mailto:Martin.Banszel at tieto.com>>
Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Test meeting -
9:00 Pacific time
Message-ID:
<4F6AACE4B0F173488D033B02A8BB5B7E7CF01B94 at FMSMSX114.amr.corp.intel.com<mailto:4F6AACE4B0F173488D033B02A8BB5B7E7CF01B94 at FMSMSX114.amr.corp.intel.com>>
Content-Type: text/plain; charset="utf-8"
Updates will be requested offline
Weekly meetings on Tuesdays at 9am Pacific
* Zoom link: https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fj%2F342730236&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=UqST7HL4GAjPpXlyt9Bx1uxTORAU945uMr%2F9VBuqwWM%3D&reserved=0
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
o International numbers available: https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fu%2Fed95sU7aQ&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=4ZjWIMiKjPTFOA%2BENxYwMDSCQbD64GbpXfC46LbalX0%3D&reserved=0
Agenda and meeting minutes: https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fetherpad.openstack.org%2Fp%2Fstx-test&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=UfJsFkKFIkGrcBDJBxn%2FXaUVNCLmlcwXXYMzf1a7YEQ%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.starlingx.io%2Fpipermail%2Fstarlingx-discuss%2Fattachments%2F20191101%2F7bf1a4c8%2Fattachment-0001.html&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=NEI2%2FK65WhYIbeakijKhtkjly%2BU%2FTYaDgU4xghK7PAA%3D&reserved=0>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/calendar
Size: 3486 bytes
Desc: not available
URL: <https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.starlingx.io%2Fpipermail%2Fstarlingx-discuss%2Fattachments%2F20191101%2F7bf1a4c8%2Fattachment-0001.ics&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=%2FoQLIZOIoYgg5mL2lpEZMtQPx6L0M9HYq3qivD5K61I%3D&reserved=0>
------------------------------
Message: 2
Date: Sat, 2 Nov 2019 21:04:08 +0000
From: Anirudh Gupta <Anirudh.Gupta at hsc.com<mailto:Anirudh.Gupta at hsc.com>>
To: "starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>"
<starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>,
"starlingx-discuss-owner at lists.starlingx.io<mailto:starlingx-discuss-owner at lists.starlingx.io>"
<starlingx-discuss-owner at lists.starlingx.io<mailto:starlingx-discuss-owner at lists.starlingx.io>>
Subject: [Starlingx-discuss] Starlingx 2.0 Service Endpoints not
publicly accessed from External Entities
Message-ID:
<MAXPR0101MB12115A2874F56200BE790139F97D0 at MAXPR0101MB1211.INDPRD01.PROD.OUTLOOK.COM<mailto:MAXPR0101MB12115A2874F56200BE790139F97D0 at MAXPR0101MB1211.INDPRD01.PROD.OUTLOOK.COM>>
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
https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.starlingx.io%2Fdeploy_install_guides%2Fr2_release%2Fopenstack%2Faccess.html%23configure-helm-endpoint-domain&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=sWOsa5YN8H8Tpw%2FjAU%2FJqLNtdrsPlBR4kYt0szC3sak%3D&reserved=0
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...
URL: <https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.starlingx.io%2Fpipermail%2Fstarlingx-discuss%2Fattachments%2F20191102%2F7659ca8e%2Fattachment-0001.html&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=ckrtZCrQgAAhPrXCG31m4bqZKPq4xxMiL7UTQA1KnmQ%3D&reserved=0>
------------------------------
Message: 3
Date: Sun, 03 Nov 2019 02:50:11 -0600
From: cristopher.j.lemus.contreras at intel.com<mailto:cristopher.j.lemus.contreras at intel.com>
To: <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker
images
Message-ID: <3cea8d$6t0227 at fmsmga002.fm.intel.com<mailto:3cea8d$6t0227 at fmsmga002.fm.intel.com>>
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
Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>
https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.starlingx.io%2Fcgi-bin%2Fmailman%2Flistinfo%2Fstarlingx-discuss&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711498181&sdata=bEJTXZe41hnithU8mgFdzin57Q5fvOiNUjeNwSDiH8w%3D&reserved=0
------------------------------
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20191105/c10b2f3a/attachment-0001.html>
More information about the Starlingx-discuss
mailing list