how do I utilize shared networks?

[paulczar]

My networks aren't owned by my tenant, but are shared.

$ openstack=1 vagrant openstack network-list

+----+------+
| Id | Name |
+----+------+
+----+------+

I discovered I can run

vagrant openstack network-list all

+--------------------------------------+----------+
| Id                                   | Name     |
+--------------------------------------+----------+
| 06dc9d5a-f55a-410d-a7fd-4c7cb34ad927 | external |
| ba0fdd03-72b5-41eb-bb67-fef437fd6cb4 | internal |
+--------------------------------------+----------+

how do I specify the all arg in the Vagrantfile so that I can use them ?

[julienvey]

Hi Paul,

We had a bug about this that was fixed just after the 0.5 release (2 days ago). See #148
I just released a bug fix version (0.5.1) that includes the fix

You need to update the version of the plugin and hopefully it should work

vagrant plugin update vagrant-openstack-provider

Let me know if this fixed your issue

[ggiamarchi]

Duplicate of #129

[paulczar]

thanks! that takes me further ... now I get -

014-11-06 13:13 |  INFO | Reading SSH info
2014-11-06 13:13 | DEBUG | block in get_server_details - start
2014-11-06 13:13 | DEBUG | request  => method  : GET
2014-11-06 13:13 | DEBUG | request  => url     : https://openstack.example.com:8777/v2/8c7863ba8e014089b895c8e1a6813464/servers/c2822ad1-77f6-4469-aec0-9ac412c0fc20
2014-11-06 13:13 | DEBUG | request  => headers : {"X-Auth-Token"=>"13bf34cba1a548468b4cc5524abaf62b", :accept=>:json}
2014-11-06 13:13 | DEBUG | response => code    : 200
2014-11-06 13:13 | DEBUG | response => headers : {:content_type=>"application/json", :content_length=>"1953", :x_compute_request_id=>"req-dd02bd11-525b-41ce-896c-f4eeddf02816", :date=>"Thu, 06 Nov 2014 19:13:07 GMT", :connection=>"close"}
2014-11-06 13:13 | DEBUG | response => body    : {"server": {"status": "ACTIVE", "updated": "2014-11-06T19:11:20Z", "hostId": "40c4941caac7b377e106469a348b342718abb3ff804fd34433d44bb3", "OS-EXT-SRV-ATTR:host": "ds1263", "addresses": {"internal": [{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:3d:d7:76", "version": 4, "addr": “y.y.y.y”, "OS-EXT-IPS:type": "fixed"}], "external": [{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:85:d3:66", "version": 4, "addr": “x.x.x.x”, "OS-EXT-IPS:type": "fixed"}]}, "links": [{"href": "http://openstack.example.com:8777/v2/8c7863ba8e014089b895c8e1a6813464/servers/c2822ad1-77f6-4469-aec0-9ac412c0fc20", "rel": "self"}, {"href": "http://openstack.example.com:8777/8c7863ba8e014089b895c8e1a6813464/servers/c2822ad1-77f6-4469-aec0-9ac412c0fc20", "rel": "bookmark"}], "key_name": "vagrant-generated-qucrrmnd", "image": {"id": "1525c3f3-1224-4958-bd07-da9feaedf18b", "links": [{"href": "http://openstack.example.com:8777/8c7863ba8e014089b895c8e1a6813464/images/1525c3f3-1224-4958-bd07-da9feaedf18b", "rel": "bookmark"}]}, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": "active", "OS-EXT-SRV-ATTR:instance_name": "instance-00004e57", "OS-SRV-USG:launched_at": "2014-11-06T19:11:20.000000", "OS-EXT-SRV-ATTR:hypervisor_hostname": "server1.openstack.example.com", "flavor": {"id": "2", "links": [{"href": "http://openstack.example.com:8777/8c7863ba8e014089b895c8e1a6813464/flavors/2", "rel": "bookmark"}]}, "id": "c2822ad1-77f6-4469-aec0-9ac412c0fc20", "security_groups": [{"name": "default"}, {"name": "default"}], "OS-SRV-USG:terminated_at": null, "OS-EXT-AZ:availability_zone": "nova", "user_id": "d1f0da423aee410692f085e55d834422", "name": "workstation", "created": "2014-11-06T19:11:06Z", "tenant_id": "8c7863ba8e014089b895c8e1a6813464", "OS-DCF:diskConfig": "MANUAL", "os-extended-volumes:volumes_attached": [], "accessIPv4": "", "accessIPv6": "", "progress": 0, "OS-EXT-STS:power_state": 1, "config_drive": "", "metadata": {}}}
2014-11-06 13:13 | DEBUG | block in get_server_details - end
ERROR warden: Error occurred: Vagrant was unable to resolve a valid ip to ssh on your OpenStack instance.

[paulczar]

Never mind, I got it figured out. list the internal network in the networks field and the external in 'floating_ip_pool'.

[ggiamarchi]

I reopen the issue because actually there is a bug. Your use case should work (at least go further). As long as your instance have an IP address, vagrant should try to SSH on it. @julienvey is working on the bugfix.

[paulczar]

@julienvey is a wonderful human being.

[julienvey]

:P

Just proposed a simple fix but it wouldn't certainly not have made you case work.

When you are not using floating ips, we try to look for other ips, and if there are more than one, we take the first one and hope it will work...

A long term fix would be to try to access each one and use the first one we can reach. I will create another issue to track this