@tcervi:matrix.org | Hi Ceyhun, sorry for my late response :( | 00:27 |
---|---|---|
@tcervi:matrix.org | I just replied to your email on STX list, but if you prefer we can continue discussing the topic here. Would be happy to help you :) | 00:27 |
Ceyhun Şen | ||
@ceyhunseninventron:matrix.org | No worries. Basically I followed https://docs.starlingx.io/r/stx.8.0/deploy_install_guides/release/bare_metal/aio_simplex_install_kubernetes.html this and https://docs.starlingx.io/r/stx.8.0/deploy_install_guides/release/openstack/install.html this tutorials to setup StarlingX to my server. I used 2 separate ethernet ports (did not configured them in any way at all, like getting an ip for it) for setting up data networks. This 2 ethernet ports are different from my OAM port. | 06:38 |
Looks like the NIC on my server (Intel Pro 1000) does not support any virtualization that StarlingX takes advantage of. Even though I used labels like "sriov=disabled" or "system modify --vswitch_type none" the result is the same: OpenStack can't see any networks and refuses to create vm's. | ||
Soon, I will have access to new and different hardware. I will be testing this again on that hardware to see that if problem is the hardware. This is my current guess. | ||
I will give an update when it happens. | ||
@tcervi:matrix.org | Yeap, I mean your starlingx network config seem to be fine. | 16:02 |
Once you have the new hardware and installation, would be good to check how you created the OpenStack networks so we can help you tracing why VMs can't find it. | ||
Please keep us on the looop | ||
@tcervi:matrix.org | Also, Ceyhun Şen I did not see if you followd the stx datanetwork creation process [2], those will be useful when creating openstack networks. | 19:49 |
For example, it your datanets have external connection and you want to reach outside world, you will want an OpenStack external network linked to you STX equivalent datanet ( --provider-network-type=vlan --provider-physical-network=group0-ext0). For internal only networks, the connection will be similar. | ||
The app plugins will be loaded by stx sysinv and be able to access your systems network configuration [2], and automatically generate the appropriate helm-overrides to configure your Neutron setup... | ||
You can check the auto generated () overrides using the follow command: | ||
And should see some configs similar to: | ||
ovs: {bridge_mappings: 'group0-data0:br-phy0,group0-data0b:br-phy0,group0-data1:br-phy0,group0-ext0:br-phy0,',datapath_type: system, integration_bridge: br-int, vhostuser_socket_dir: /var/run/openvswitch} | ||
[1] https://docs.starlingx.io/datanet/index-datanet-e316bf6c2f6a.html | ||
[2] https://opendev.org/starlingx/openstack-armada-app/src/branch/master/python3-k8sapp-openstack/k8sapp_openstack/k8sapp_openstack/helm/neutron.py#L136 | ||
@tcervi:matrix.org | * _Also,_ Ceyhun Şen I did not see if you followd the stx datanetwork creation process \[2\], those will be useful when creating openstack networks. | 19:49 |
For example, it your datanets have external connection and you want to reach outside world, you will want an OpenStack external network linked to you STX equivalent datanet ( --provider-network-type=vlan --provider-physical-network=group0-ext0). For internal only networks, the connection will be similar. | ||
The app plugins will be loaded by stx sysinv and be able to access your systems network configuration \[2\], and automatically generate the appropriate helm-overrides to configure your Neutron setup... | ||
You can check the auto generated () overrides using the follow command: | ||
**[sysadmin@controller-0 ~(keystone_admin)]$ system helm-override-show wr-openstack neutron openstack** | ||
And should see some configs similar to: | ||
ovs: {bridge\_mappings: 'group0-data0:br-phy0,group0-data0b:br-phy0,group0-data1:br-phy0,group0-ext0:br-phy0,',datapath\_type: system, integration\_bridge: br-int, vhostuser\_socket\_dir: /var/run/openvswitch} | ||
\[1\] https://docs.starlingx.io/datanet/index-datanet-e316bf6c2f6a.html | ||
\[2\] https://opendev.org/starlingx/openstack-armada-app/src/branch/master/python3-k8sapp-openstack/k8sapp\_openstack/k8sapp\_openstack/helm/neutron.py#L136 | ||
@tcervi:matrix.org | * _Also,_ Ceyhun Şen I did not see if you followd the stx datanetwork creation process \[2\], those will be useful when creating openstack networks. | 19:50 |
For example, it your datanets have external connection and you want to reach outside world, you will want an OpenStack external network linked to you STX equivalent datanet ( --provider-network-type=vlan --provider-physical-network=group0-ext0). For internal only networks, the connection will be similar. | ||
The app plugins will be loaded by stx sysinv and be able to access your systems network configuration \[2\], and automatically generate the appropriate helm-overrides to configure your Neutron setup... | ||
You can check the auto generated () overrides using the follow command: | ||
**\[sysadmin@controller-0 ~(keystone\_admin)\]$ system helm-override-show stx-openstack neutron openstack** | ||
And should see some configs similar to: | ||
ovs: {bridge\_mappings: 'group0-data0:br-phy0,group0-data0b:br-phy0,group0-data1:br-phy0,group0-ext0:br-phy0,',datapath\_type: system, integration\_bridge: br-int, vhostuser\_socket\_dir: /var/run/openvswitch} | ||
\[1\] https://docs.starlingx.io/datanet/index-datanet-e316bf6c2f6a.html | ||
\[2\] https://opendev.org/starlingx/openstack-armada-app/src/branch/master/python3-k8sapp-openstack/k8sapp\_openstack/k8sapp\_openstack/helm/neutron.py#L136 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!