tiger's profile - activity

server.log:2017-10-02 16:16:12.588 9672 ERROR neutron.plugins.ml2.managers [req-89b68dfd-a3ec-4146-8c00-75798c495619 8a9170d389604942b93fda9b7ef8fe5a b73fda708d5746a087ff2c1fce882e9e - - -] Failed to bind port c94ea7db-ce48-46da-9b22-05b26427c6d7 on host kvm8.ims1.mia.ccncore.net for vnic_type normal using segments [{'segmentation_id': None, 'physical_network': u'provider', 'id': u'7c8ff657-61fe-4011-ae65-9f777d79980c', 'network_type': u'flat'}]

Trying to bring up an instance on a provider network and getting the error above.

openstack server create --flavor 1 --image fdb2ec8e-7d97-4487-8dba-40495e6ac6f4 --nic net-id=02d9e1a9-5da8-41f7-9990-36a37bf116ba kef

+-------------------------------------+-----------------------------------------------------+
| Field                               | Value                                               |
+-------------------------------------+-----------------------------------------------------+
| OS-DCF:diskConfig                   | MANUAL                                              |
| OS-EXT-AZ:availability_zone         |                                                     |
| OS-EXT-SRV-ATTR:host                | None                                                |
| OS-EXT-SRV-ATTR:hypervisor_hostname | None                                                |
| OS-EXT-SRV-ATTR:instance_name       |                                                     |
| OS-EXT-STS:power_state              | NOSTATE                                             |
| OS-EXT-STS:task_state               | scheduling                                          |
| OS-EXT-STS:vm_state                 | building                                            |
| OS-SRV-USG:launched_at              | None                                                |
| OS-SRV-USG:terminated_at            | None                                                |
| accessIPv4                          |                                                     |
| accessIPv6                          |                                                     |
| addresses                           |                                                     |
| adminPass                           | fTJ4h32GhQWU                                        |
| config_drive                        |                                                     |
| created                             | 2017-10-02T16:10:33Z                                |
| flavor                              | m1.tiny (1)                                         |
| hostId                              |                                                     |
| id                                  | 7e823c4b-7d56-4d5b-a20b-07ebd53c6e58                |
| image                               | cirros image (fdb2ec8e-7d97-4487-8dba-40495e6ac6f4) |
| key_name                            | None                                                |
| name                                | kef                                                 |
| progress                            | 0                                                   |
| project_id                          | 32bbb96442094b91813ec556dfd4ff30                    |
| properties                          |                                                     |
| security_groups                     | name='default'                                      |
| status                              | BUILD                                               |
| updated                             | 2017-10-02T16:10:33Z                                |
| user_id                             | ff0b41615dd749e39267a5f6ead17b19                    |
| volumes_attached                    |                                                     |
+-------------------------------------+-----------------------------------------------------+

[root@kvm8 ~(keystone_admin)]# openstack network list
+--------------------------------------+---------------------+--------------------------------------+
| ID                                   | Name                | Subnets                              |
+--------------------------------------+---------------------+--------------------------------------+
| 02d9e1a9-5da8-41f7-9990-36a37bf116ba | kef_vlan505_em4_net | 2bdb31fe-5faf-4291-a370-7a7a727ced21 |
| 15e543fe-7330-48ad-851b-f8e17f5658a5 | external_em3        | bcdd93fe-bb2d-43a4-8528-1cbb3caee4af |
| fb3f2f93-d477-4e04-a737-5f932a8ca91d | Internal            | 5462272d-3195-4e7c-a091-83425e6f878d |
+--------------------------------------+---------------------+--------------------------------------+

[root@kvm8 ~(keystone_admin)]# openstack server list
+--------------------------------------+-------------------+---------+-----------------------+--------------+
| ID                                   | Name              | Status  | Networks              | Image Name   |
+--------------------------------------+-------------------+---------+-----------------------+--------------+
| a12d3bc4-8b5e-4d64-b1b2-66f18b34c66d | kef               | ERROR   |                       | cirros image |
+--------------------------------------+-------------------+---------+-----------------------+--------------+

What would be nice if it said why it failed, rather than always speaking in riddles.

Thanks in advance

Thanks for all the replies. In case anyone wants to know how I fixed it, make sure "extnet" is in the "physical network" field that appears after you select "flat" in the field above it. By default, it will be "local" and the "physical network" field will be missing. After you select "flat" and the "physical network" appears, it will have "default" in it. Change that to "extnet" which needs to have been mentioned in the "answers" file:

CONFIG_NEUTRON_OVS_EXTERNAL_PHYSNET=extnet CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=extnet:br-ex

In retrospect I suppose I should have guessed this. Would be wonderful if the documentation were useful. I have an idea! How about an OpenStack "cookbook" with basic recipes for setting this shit up?

I know this is an old thread, but Sam's answer is the closest thing to a clue I have been able to find on the topic of "bringing up a VM on a provider network". Most all that I read is nonsensical. Any elaboration would be appreciated.

Unfortunately, it didn't work. It was as if once the VM is instantiated, the various meta-data are frozen

You may be right but I am trying to avoid floating IPs! I should be able to boot up an instance with "--nic net-id=xxxxxx" specifying a provider network and thus avoid private networks, routers and floating IPs

I have set up Openstack "Newton" on one physical host. I have gotten "self-service" networking to work. Two private networks, 10.0.0.0/24 and 10.0.1.0/24 along with one external 192.168.140.0/24. A router binds them together. External is "flat". Private is "vxlan". A route on the host grants access from the outside to the private without "floating" IP.

Want to simplify this a bit by granting the VM access to the physical host interfaces (em1, em2) and VLANs like em1.100, etc.

So if em1's network address is 192.168.140.100/24, subnet 192.168.140.0/24 and gateway 192.168.140.1 I want spun up VMs to be able to have alias addresses .101, .102, .103, etc.

The outside world then will try to access .101, send an ARP, something replies with ARP reply, then the VM see the traffic directly. Everything I read ends up going down the rabbit hole of floating IPs which will not work when there is application-layer IP addresses that NAT will not touch. NAT will fix the layer-3 IP address, but the application layer IP will be wrong, hence the need for a simpler / cleaner / less-wacked-out networking scheme.

Hoping someone can help, thanks.

I've gotten floating IP to work. It's OK for granting SSH access but no one would seriously offer access to the outside world into a VM using a floating IP.

Sorry, I replied in the wrong place. The provided link does not address the objective of passing through access to the host's physical / actual Ethernet interfaces. Like everything else I stumbled onto, it drives off into the woods with floating IP and other such nonsense.

Then on the host I have "route add -net 10.0.0.0/24 gw 192.168.140.99 br-ex" and then I can SSH into a VM via its private network address, e.g. "ssh root@10.0.0.12". No need for floating IP or "ip netns exec" or other nonsense like that. Bringing up VM that can access the host Ethernet is the goal

IP addresses in the SIP header. I am getting along with "self-service" networks by creating a flat external and a VXLAN private. Then in the host, add a route that uses the router IP as a gateway to access the private. So if the private network is 10.0.0.0/24 and the router gateway is 192.168.140.99

Hi there. Thank you for your reply. Unfortunately, this "method should allow any machine on the network to be able to access launched instances via their floating IPs" for me is a non-starter. Floating IPs is neat, with bidirectional NAT taking place, but we can't use it unless it will also modify

Just blew away my lab system for the eleventy-third time. Going to try "provider" networks this time around. Who knows, maybe I'll get lucky with it. I have a host with four Ethernet cards. Would like to end up with VM's that transparently have access to the host's Ethernet cards without any BS about neutron nor plugins nor agents nor INI files.

em1 will have 192.168.140.0/24 The host is .217 I want the VMs to come up seeing em1 and being assigned .218, .219, .220 etc via DHCP To make this happen, OpenStack would have to listen out for ARP requests for these other IP addresses. I assume it can do that without too much pain.

Oh, and the documentation on the topic is crap. Thanks in advance.

I don't mean add additional metadata tags. Suppose in my metadata catalog I have "peanut=butter". I start a VM with that data. I want to change "butter" to "margarine". From the GUI, it looks like it is only possible to add new metadatas. I want to change the value of an existing metadata. Thanks in advance.

Oh, and a search on metadata brings up tons of unrelated posts but not the answer to "how to change value"