Open Stack

That file is not static file but I think it is generated at boot.
It reads your endpoint are on a network unreacheable by master node.
So....it is easier to change external network where you deploy your cluster
rather than modify the openstack configuration.
If you choos an external network which can speak with keystone endpoint on
5000 port the problem la solved.
Regards
Ignazio


Il giorno Sab 15 Dic 2018 20:10 Zufar Dhiyaulhaq <zufar at onf-ambassador.org>
ha scritto:

> Hi Ignazio,
>
> I think my problem is from this file to,
>
> [fedora at swarm-cluster-hekxryp2n6ke-primary-master-0 ~]$ sudo cat
> /etc/sysconfig/heat-params
> IS_PRIMARY_MASTER="True"
> WAIT_CURL="curl -i -X POST -H 'X-Auth-Token:
> gAAAAABcFVD3Lq8v3cBGbpnejxNtqkDZPIDBYg6LBXTifXQxPowzdWhYHnRT7MWE48fwPwTYTJxM6TS_v32gl4OZu5GInufoXmnBFApdOmUg9KzeJGz8iGvg0tl62ratgRN40SMXNM7ZEXIflDQHO9tKrVdpJ9v6KY8HV2rZ0mspzTUDnsg0NjE'
> -H 'Content-Type: application/json' -H 'Accept: application/json'
> http://10.60.60.10:8004/v1/c508af1f5ad741dbb2e3e2b5eee5855e/stacks/swarm-cluster-hekxryp2n6ke-swarm_primary_master-hkgjpiv34bcl-0-323fkifz7mim/a5cabefd-417c-41ad-bf43-2ab27d572d08/resources/master_wait_handle/signal
> "
> DOCKER_VOLUME="6101c99c-9072-4290-9691-e679dbb44f8f"
> DOCKER_VOLUME_SIZE="0"
> DOCKER_STORAGE_DRIVER="devicemapper"
> HTTP_PROXY=""
> HTTPS_PROXY=""
> NO_PROXY=""
> PRIMARY_MASTER_IP=""
> SWARM_API_IP="10.0.0.13"
> SWARM_NODE_IP="10.0.0.13"
> CLUSTER_UUID="17a9eb19-2d22-473a-a292-df2d06197974"
> MAGNUM_URL="http://10.60.60.10:9511/v1"
> TLS_DISABLED="False"
> API_IP_ADDRESS="10.61.61.111"
> TRUSTEE_USER_ID="f61ff2de879548e9b46bd5609a696b6c"
> TRUSTEE_PASSWORD="T6zjpQGjqcPwv7684F"
> TRUST_ID=""
> AUTH_URL="http://10.60.60.10:5000/v3"
> VOLUME_DRIVER=""
> REXRAY_PREEMPT="false"
> VERIFY_CA="True"
>
> Best Regards,
> Zufar Dhiyaulhaq
>
>
> On Sun, Dec 16, 2018 at 2:09 AM Zufar Dhiyaulhaq <zufar at onf-ambassador.org>
> wrote:
>
>> Hi, Ignazio,
>>
>> yes all of my endpoint is in 10.60.60.
>>
>> Ignazio, can you check `sudo cat /etc/sysconfig/heat-params` inside the
>> VM and see `DOCKER_VOLUME_SIZE="0"`
>> Maybe this give you solution.
>>
>> Best Regards,
>> Zufar Dhiyaulhaq
>>
>>
>> On Sun, Dec 16, 2018 at 2:03 AM Ignazio Cassano <ignaziocassano at gmail.com>
>> wrote:
>>
>>> Pobably you configured all services
>>> (Nova , magnum and so on) with endpoint on 10.60.60..... in keystone
>>> section
>>>
>>> Il giorno Sab 15 Dic 2018 19:39 Zufar Dhiyaulhaq <
>>> zufar at onf-ambassador.org> ha scritto:
>>>
>>>> Hi Ignazio,
>>>>
>>>> I try to change the heat configuration as you suggested, but still my
>>>> instance are try to 10.60.60.10.
>>>> this is the output :
>>>>
>>>> | 0c34c8b0dcdc459f818c2bab04913039 | RegionOne | keystone     |
>>>> identity        | True    | public    | http://10.60.60.10:5000/v3
>>>> |
>>>> | 8ca42fccdb774f9daf67c95ea61fd006 | RegionOne | keystone     |
>>>> identity        | True    | admin     | http://10.60.60.10:35357/v3
>>>> |
>>>> | 8d0a23730608495980dce151d466a579 | RegionOne | keystone     |
>>>> identity        | True    | internal  | http://10.60.60.10:5000/v3
>>>> |
>>>>
>>>> testing curl :
>>>>
>>>> @swarm-cluster-wtet5ppc5eqi-primary-master-0 ~]$ curl
>>>> http://10.60.60.10:5000/v3
>>>> ^C
>>>> [fedora at swarm-cluster-wtet5ppc5eqi-primary-master-0 ~]$ curl
>>>> http://10.61.61.10:5000/v3
>>>> {"version": {"status": "stable", "updated": "2018-02-28T00:00:00Z",
>>>> "media-types": [{"base": "application/json", "type":
>>>> "application/vnd.openstack.identity-v3+json"}], "id": "v3.10", "links":
>>>> [{"href": "http://10.61.61.10:5000/v3/", "rel":
>>>> "self"}]}}[fedora at swarm-cluster-wtet5ppc5eqi-primary-master-0 ~]$
>>>>
>>>>
>>>> Best Regards,
>>>> Zufar Dhiyaulhaq
>>>>
>>>>
>>>> On Sun, Dec 16, 2018 at 1:20 AM Ignazio Cassano <
>>>> ignaziocassano at gmail.com> wrote:
>>>>
>>>>> What reports the command
>>>>> openstack endpoint list | grep keystone
>>>>>
>>>>> ?
>>>>>
>>>>>
>>>>> Il giorno Sab 15 Dic 2018 19:16 Zufar Dhiyaulhaq <
>>>>> zufar at onf-ambassador.org> ha scritto:
>>>>>
>>>>>> By Design, my OpenStack have 2 networks.
>>>>>>
>>>>>> External Network (Floating IP) : 10.61.61.0/24
>>>>>> Management Network & Data Network (private): 10.60.60.0/24
>>>>>>
>>>>>> An instance that deploys with floating IP cant access to the
>>>>>> management network. It is possible to change the URL from the error log
>>>>>> (10.60.60.10) to 10.61.61.10?
>>>>>>
>>>>>> Best Regards,
>>>>>> Zufar Dhiyaulhaq
>>>>>>
>>>>>>
>>>>>> On Sun, Dec 16, 2018 at 1:12 AM Zufar Dhiyaulhaq <
>>>>>> zufar at onf-ambassador.org> wrote:
>>>>>>
>>>>>>> Yes. Master Node communicates with port 5000, but with a wrong IP
>>>>>>> address.
>>>>>>>
>>>>>>> Floating IP give to my instance is in 10.61.61.0/24 but all of my
>>>>>>> endpoints are in 10.60.60.0/24, but when I try to curl manual the
>>>>>>> endpoint with 10.61.61.0/24 it's working fine.
>>>>>>> It is possible to change the IP address installed on cloud-init to
>>>>>>> 10.61.61.X?
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> Zufar Dhiyaulhaq
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Dec 16, 2018 at 1:08 AM Ignazio Cassano <
>>>>>>> ignaziocassano at gmail.com> wrote:
>>>>>>>
>>>>>>>> Zufar, the master node must communicat with port 5000 on the
>>>>>>>> network where you deployed keystone endpoint.
>>>>>>>> Ignazio
>>>>>>>> Il giorno Sab 15 Dic 2018 18:58 Zufar Dhiyaulhaq <
>>>>>>>> zufar at onf-ambassador.org> ha scritto:
>>>>>>>>
>>>>>>>>> Hi I am creating a swarm cluster with this command :
>>>>>>>>>
>>>>>>>>>    - openstack coe cluster template create swarm-cluster-template
>>>>>>>>>    --image fedora-atomic-latest --external-network external --dns-nameserver
>>>>>>>>>    8.8.8.8 --master-flavor m1.small --flavor m1.small --coe swarm-mode
>>>>>>>>>    --docker-volume-size 4 --docker-storage-driver=devicemapper
>>>>>>>>>    - openstack coe cluster create swarm-cluster
>>>>>>>>>    --cluster-template swarm-cluster-template --master-count 1 --node-count 1
>>>>>>>>>    --keypair mykey
>>>>>>>>>
>>>>>>>>> but its stack on *swarm_primary_master *heat with
>>>>>>>>> *CREATE_IN_PROGRESS*. I try to login into swarm VM and see the
>>>>>>>>> log.
>>>>>>>>>
>>>>>>>>> I get this :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>    - requests.exceptions.ConnectionError:
>>>>>>>>>    HTTPConnectionPool(host='10.60.60.10', port=5000): Max retries exceeded
>>>>>>>>>    with url: /v3/auth/tokens (Caused by
>>>>>>>>>    NewConnectionError('<urllib3.connection.HTTPConnection object at
>>>>>>>>>    0x7f02f57321d0>: Failed to establish a new connection: [Errno 110]
>>>>>>>>>    Connection timed out',))
>>>>>>>>>    - Cloud-init v. 0.7.9 running 'modules:final' at Sat, 15 Dec
>>>>>>>>>    2018 17:36:44 +0000. Up 33.29 seconds.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Swarm Instance try to open connection to 10.60.60.10 which is my
>>>>>>>>> management ip address on OpenStack.  But it cannot (by design it cannot, I
>>>>>>>>> try to curl manual to 10.60.60.10 and error). When curl to 10.61.61.10
>>>>>>>>> which is my floating IP and external IP for OpenStack cluster, it works.
>>>>>>>>>
>>>>>>>>> Anyone know how to change the cloud-init to curl into 10.61.61.10?
>>>>>>>>>
>>>>>>>>> Best Regards,
>>>>>>>>> Zufar Dhiyaulhaq
>>>>>>>>>
>>>>>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20181215/cfc0edf7/attachment-0001.html>