New Question
0

v-magine installation - network issues [closed]

asked 2016-12-09 20:32:57 +0300

Nebukazar gravatar image

Hi,

We've been installing v-magine on one of our hyperv node running windows 2012r2 std. So far, the installation worked, however, when we are trying to deploy VMs, networking is not working properly.

VMs are not able to reach the outside (eg: public network), however, VMs are able to see / ping each others.

The hyperv node has 2x NICs: - 1x OOB interface with public IP (no tagged vlan); - 1x external public network (no tagged vlan).

A /27 has been attributed to our public network, meaning we should be able to use that public subnet on any VMs running on that node.

The hyperv node has therefore 4x vswitches:

  • LOCAL (internal), previously created;
  • VRACK (external - should be the one being used by OpenStack), previously created;
  • v-magine-internal (internal), created by the vmagine installer;
  • v-magine-data (private), created by the vmagine installer.

Please note that VMs are getting the proper vswitch assigned:

PS C:\> Get-VM -Name instance-00000006,instance-00000007 | select -ExpandProperty NetworkAdapters | select VMName, SwitchName

VMName                                                      SwitchName
------                                                      ----------
instance-00000006                                           v-magine-data
instance-00000007                                           v-magine-data

The 2 VMs are using the subnet / network created by the vmagine installer.

The current network has the following values:

(neutron) net-show 612ebe38-47bd-454b-84d4-61de3db8638d
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | True                                 |
| availability_zone_hints   |                                      |
| availability_zones        | nova                                 |
| created_at                | 2016-12-09T17:35:15                  |
| description               |                                      |
| id                        | 612ebe38-47bd-454b-84d4-61de3db8638d |
| ipv4_address_scope        |                                      |
| ipv6_address_scope        |                                      |
| is_default                | False                                |
| mtu                       | 1500                                 |
| name                      | public                               |
| provider:network_type     | vlan                                 |
| provider:physical_network | physnet1                             |
| provider:segmentation_id  | 535                                  |
| router:external           | True                                 |
| shared                    | False                                |
| status                    | ACTIVE                               |
| subnets                   | 7043c4ae-a7d7-40e1-8672-b0594e1f5e21 |
| tags                      |                                      |
| tenant_id                 | 3b512d5359764ea1b018e413b580f728     |
| updated_at                | 2016-12-09T17:35:15                  |
+---------------------------+--------------------------------------+

And the current subnet values (please note that I have masked sensitive data):

(neutron) subnet-show 7043c4ae-a7d7-40e1-8672-b0594e1f5e21
+-------------------+--------------------------------------------------+
| Field             | Value                                            |
+-------------------+--------------------------------------------------+
| allocation_pools  | {"start": "xxx.xxx.xxx.36", "end": "xxx.xxx.xxx.45"} |
| cidr              | xxx.xxx.xxx.32/27                                  |
| created_at        | 2016-12-09T17:35:19                              |
| description       |                                                  |
| dns_nameservers   |                                                  |
| enable_dhcp       | True                                             |
| gateway_ip        | xxx.xxx.xxx.62                                     |
| host_routes       |                                                  |
| id                | 7043c4ae-a7d7-40e1-8672-b0594e1f5e21             |
| ip_version        | 4                                                |
| ipv6_address_mode |                                                  |
| ipv6_ra_mode      |                                                  |
| name              | public_subnet                                    |
| network_id        | 612ebe38-47bd-454b-84d4-61de3db8638d             |
| subnetpool_id     |                                                  |
| tenant_id         | 3b512d5359764ea1b018e413b580f728                 |
| updated_at        | 2016-12-09T18:04:57                              |
+-------------------+--------------------------------------------------+

I am not sure that I am missing, could you guys please help me out ? We are quite new to OpenStack and would definitely need some guidance.

Thanks!

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Nebukazar
close date 2017-01-23 23:18:23.683151

Comments

To begin with, let's ensure that the networking works as expected between VMs and Neutron: are the VMs getting an IP via DHCP? Can you ping the internal router IP from the VMs?

alexpilotti gravatar imagealexpilotti ( 2016-12-09 21:13:01 +0300 )edit

Hi Alex, Those VMs are getting the proper IPs assigned from the DHCP service. However, I don't seem to be able to ping the internal gateway (network:router_gateway). I can ping VMs from/to VMs fine tho. Please let me know if you need any further information / configuration snippets. Thanks!

Nebukazar gravatar imageNebukazar ( 2016-12-09 22:33:32 +0300 )edit

From inside the VMs, you should be able to ping the gateway 10.0.0.1 and DHCP server (usually 10.0.0.2), can you please confirm if this is or not the case? Thanks

alexpilotti gravatar imagealexpilotti ( 2016-12-09 22:49:29 +0300 )edit

Actually, those VMs are getting a floating / route able IPs assigned, not the private 10.x.x.x subnet I'm still able to ping the DHPC service at x.x.x.38 (routeable IP) From neutron, I'm able to ping the router gateway: ip netns exec qrouter-5e279681-fd39-4f0b-9ecc-36a66abd246c ping x.x.x.34

Nebukazar gravatar imageNebukazar ( 2016-12-09 22:51:47 +0300 )edit

FYI: I'm deploying those VMs in the "admin" project for testing purpose. I'd like those VMs to use external IPs to reach the outside.

Nebukazar gravatar imageNebukazar ( 2016-12-09 22:57:44 +0300 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2016-12-19 18:18:17 +0300

alexpilotti gravatar image

Please ensure that:

  • there's a router created in the tenant that owns the VMs (e.g. "demo")
  • the router is set to use the "public" network as gateway
  • the "private" subnet is connected to the router.

Note: if the router belongs to another tenant (e.g. "admin"), the demo user won't be able to associate floating IPs.

In Horizon, when logged in as "demo" you can check under "Project" -> "NETWORK" -> "Network Topology" as shown in the attached image:

image description

If the tenant does not have a router, just create a new one setting the proper external network (e.g. "public").

edit flag offensive delete link more

Comments

Thanks guys! You guys were very helpful and responsive. We are definately looking forward to do business with you guys. For those who are wondering how is the support... I'm telling you.. those guys know their stuff...!! Thanks once again, your products look promising :)

Nebukazar gravatar imageNebukazar ( 2016-12-19 20:07:18 +0300 )edit

Those guys ask only simple questions :)

semka_mesilov gravatar imagesemka_mesilov ( 2016-12-22 11:53:21 +0300 )edit

Question Tools

2 followers

Stats

Asked: 2016-12-09 20:32:57 +0300

Seen: 171 times

Last updated: Dec 19 '16