First time here? Check out the FAQ!
2018-02-20 13:06:19 -0600 | received badge | ● Famous Question (source) |
2017-08-23 12:10:39 -0600 | received badge | ● Famous Question (source) |
2017-08-10 11:01:23 -0600 | commented answer | DNS Resolution fails Unfortunatly I never digged deeper into that issue. I assume that the l3 agent is missing the functionality to load the user data from the config, but I'm not sure since I'm quite new to openstack. |
2017-08-10 11:01:23 -0600 | received badge | ● Commentator |
2017-07-13 05:56:50 -0600 | received badge | ● Teacher (source) |
2017-07-13 05:56:50 -0600 | received badge | ● Self-Learner (source) |
2017-07-13 05:56:47 -0600 | received badge | ● Student (source) |
2017-07-13 04:38:59 -0600 | received badge | ● Notable Question (source) |
2017-07-08 06:27:25 -0600 | received badge | ● Notable Question (source) |
2017-07-07 17:17:45 -0600 | answered a question | Where is the getting started documentation for dummies?
Seriously, DON'T use ptivate openstack in production for that. Please. And if you don't need to scale that much, even consider 'classic' VPS hosting at another provider. |
2017-07-07 15:03:15 -0600 | answered a question | VM traffic isolation in same tenant network Either Tenant Segregation or using the FWaaS module. Using security Groups woulkd be quite a hassler. |
2017-07-06 11:52:43 -0600 | answered a question | Attach instance to Provider Network It's working now - awesome, thank to Bernd Bausch! I created a br-ex, added the needed cfg parameters to the openvswitch-agent.ini/ml2_conf.ini and created the patch ports towards the int interface. And now, everything works like a charm - wonderful :) |
2017-07-06 07:34:14 -0600 | received badge | ● Popular Question (source) |
2017-07-06 04:26:03 -0600 | commented question | Attach instance to Provider Network Ohhhhh, networking just got so much clearer to me. Awesome Bernd. I'ld like this to add a general Thank you for the amount of knowledge and tips you provide here. People like you are the reason I love working with OS projects rather than dark magic like Oracle or SAP <3 |
2017-07-06 03:01:52 -0600 | commented question | Attach instance to Provider Network Thank you for your input. I added some output to the initial post due the character limitation in the comment section :) |
2017-07-05 12:48:45 -0600 | asked a question | Attach instance to Provider Network Hi all together, I have a working Openstack Newton Cluster, running on Ubuntu 16.04. I'm using OpenVSwitch for networking in general and VLAN for provider networks, VXLAN for tenant networks. I now created two networks: While connecting to 'Externes-Netz' should happen via Router and a tenant network (which works absolutly fine btw, including floating IPs), I want to connect instances directly to the 'VPN-Netz' since they will be reachable from a VPN without floating IPs. A for testing purposes created router on that network can ping reached via ping from the vpn net, which lets me think that the network side is fine. However, I can't connect instances directly to the VPN-Netz. While I can use my regular user (not admin) to create a port, attaching a VM to it will fail with Can anyone give me a hint where to find the error? Log files are leaving me clueless too: (more) |
2017-07-05 11:28:36 -0600 | answered a question | DNS Resolution fails Just fyi: In Mitaka the domain name for the metadata is always set via nova.conf. Ping an Instance via Hostname is not possible. After upgrading to Newton, this now works :) |
2017-07-05 11:27:41 -0600 | received badge | ● Popular Question (source) |
2017-06-20 17:09:26 -0600 | asked a question | DNS Resolution fails Hi, on my Mitaka installation on Ubuntu I use Neutron for networking. I have some issues with DNS Resolution at the moment. I set my own domain name by setting I also set For test reasons. This results in the following:
I then set the following Now I get:
But still:
Further confusion ensures when taking a look at the dnsmasq config files: but those are now missing from the leases file I have a hard time understanding what is happening here and how to fix. All I want is a working hostname -f (which will result in working sudo without touching any files on the instance) and my custom domain. Also I read this spec: https://specs.openstack.org/openstack/neutron-specs/specs/liberty/internal-dns-resolution.html (https://specs.openstack.org/openstack...) Does anybody know if this was already implemented in newton/ocata? |
2017-06-14 08:04:22 -0600 | commented answer | Nested virtualization with KVM/OpenVSwitch You were totally right. I was missing the exit point with the correct VLAN Tag. Turns out you need no promiscous mode when using OpenVSwitch. After adding the VLAN tag everything works now as intended an I have a multi node OpenStack Lab Setup. On a single Hetzner node for about $60 per month :) |
2017-06-13 03:42:30 -0600 | received badge | ● Enthusiast |
2017-05-10 11:24:28 -0600 | received badge | ● Famous Question (source) |
2017-05-10 05:41:15 -0600 | commented answer | Sudo commands are very slow in VM Execute the command with sudo or allow passwordless sudo for this account. I do not want to sound rude, but you are not really familiar with linux, aren't you? Maybe you should try to get used to this environment before using OpenStack. |
2017-05-10 05:17:15 -0600 | commented answer | Sudo commands are very slow in VM On the instance you want to access. Change |
2017-05-10 05:16:03 -0600 | commented answer | Nested virtualization with KVM/OpenVSwitch I added the VLANs via |
2017-05-10 04:32:51 -0600 | answered a question | Sudo commands are very slow in VM This could be because of a missing connection to the openstack dns service. Installing and enabling dnsmasq could help, since the name resolution for your hostname will then happen locally. You may need to add the hostname to the /etc/hosts. For the ssh password login you need to set PasswordAuthentication yes in /etc/ssh/sshd_config |
2017-05-10 04:07:31 -0600 | received badge | ● Editor (source) |
2017-05-10 04:07:06 -0600 | commented answer | Nested virtualization with KVM/OpenVSwitch Added info to the start post since there is no 'reply' function here. |
2017-05-10 04:05:12 -0600 | answered a question | Nested virtualization with KVM/OpenVSwitch Oh, just remembered I can't be sure the instance got the IP - I was just checking the metadata (which may be incorrect). The network is not configured in virsh (yet - should I do that?), I attached the instances by editing their config file and adding another interface like this: However, I also found out that virsh apparently does some security implementation: ovs-vsctl show on the host: vnet6, vnet7 and vnet8 are the ports of the network instance. vnet10 and vnet12 are the compute nodes. and on the network node: |
2017-05-07 12:26:55 -0600 | received badge | ● Notable Question (source) |
2017-05-05 04:12:26 -0600 | commented question | Nested virtualization with KVM/OpenVSwitch Since the router resides (afaik) in the same security group as the node, it should be pingable by the default mitaka rules. This would also not explain why I can't ping the external public IPs. Can somebody tell me if the IP after boot is assigned via DHCP or if there is some voodoo happening? |
2017-05-04 12:36:34 -0600 | received badge | ● Popular Question (source) |
2017-05-04 01:50:26 -0600 | asked a question | Nested virtualization with KVM/OpenVSwitch Hi all together, I have a OpenStack Installation running on an bunch of old hardware we put together from old PCs. Now I want to set up OpenStack on a single host, but inside multiple VMs virtualized with KVM. The KVMs are connected via OpenVSwitch. The network setup is the following: https://imgur.com/a/HZzYw (Openstack Network Setup) I can successfully ping each instance over the Management network, running over intbr0. I can also ping the compute1, compute2 and network via their IP Addresses on the second NIC, which is connected to the tunbr0. A third NIC on the network node is set to 'manual' and attached to the br-ext. I then set up keystone, glance, neutron and nova. Inside the VMs I use OpenVSwitch again, which is this time managed by OpenStack, for the inter-vm traffic I use vxlan tunnels. The connection to the outer world is done via VLAN, where I implemented trunking on both OpenVSwitches (br-ext and databr0) I was able to create multiple instances which appear correctly on the compute nodes and are shown without an error. I also created two networks - one internal Test-Customer network and one external network. I also created the needed subnets and the router and attached it to both networks correctly. After doing so I was able to: Ping the Router IPs from Routers Namespace (Internal IP and gateway IP) I was NOT able to: Ping the attached VMs Ping another machine in the same Subnet attached to databr0 Ping the Router Gateway from the machine attached to databr0 However, my instances got IPs from the correct subnet after booting up, so I assume some DHCP magic was working (but why is my ping failing then?). I had a setup like that running on ESXI. I remember I had to set the vSwitch to promiscous mode. However, I did nothing like that on databr0, tunbr0 or intbr0 which is - as I assume - the reason packets may get dropped there. I found https://darabi.wordpress.com/2014/10/06/howto-set-promiscuous-mode-and-enable-it-in-openvswitch/ (THIS) article, however I'm not sure how to set that up. If anyone could help me to get this working, I would highly appreciate it. OpenVSwitch and OpenFlow looks like some dark art to me right now and I'm stuck at this point for over a week. If you need more information, please feel free to ask :) Greetings from Germany Micha EDIT: More infos: Oh, just remembered I can't be sure the instance got the IP - I was just checking the metadata (which may be incorrect). The network is not configured in virsh (yet - should I do that?), I attached the instances by editing their config file and adding another interface like this: However, I also found out that virsh apparently does ... (more) |
2017-05-03 12:31:06 -0600 | commented question | Launching instance with Ansible Hi, please try to use the os_auth token first for debug reasons. This way you can ensure it's not a problem with your credentials. Please also try to create the instance with the python-openstackclient. I suspect that a part of your API is not reachable from the remote host. |
2017-05-03 12:31:05 -0600 | answered a question | Launching instance with Ansible Hi, please try to use the os_auth token first for debug reasons. This way you can ensure it's not a problem with your credentials. Please also try to create the instance with the python-openstackclient. I suspect that a part of your API is not reachable from the remote host. Greetings from Germany Micha |