Marin's profile - activity

2013-11-06 10:02:43 -0500 commented answer Instances running on VMware ESXi cannot access metadata service

I could try, but to what purpose?

2013-10-01 07:15:03 -0500 answered a question Instance directly connected to provider network does not receive DHCP reply

I have a somewhat similar setup, with three (external/provider) VMware networks that should be mapped to the VM in DevStack. I should have L2 connectivity to the provider networks. Will that work with GRE tunnels? I'm using VLAN option in OVS plugin for Neutron, but there are no flows created in OVS - I see you have some flows in your switch configuration.

2013-08-12 03:53:16 -0500 received badge  Teacher (source)
2013-07-24 06:39:46 -0500 received badge  Famous Question (source)
2013-07-05 08:22:54 -0500 received badge  Notable Question (source)
2013-07-05 08:22:54 -0500 received badge  Popular Question (source)
2013-07-01 09:23:27 -0500 answered a question Unable to Ping or SSH after installing RDO

Did you allow ping/ssh in the security group? You can see what's enabled with nova secgroup-list and nova secgroup-list-rules (http://docs.openstack.org/grizzly/openstack-compute/admin/content/instance-networking.html).

2013-06-29 15:32:21 -0500 answered a question how to configure IPv6 for openstack

I can confirm that IPv6 works (dual-stack IP4/6) on Ubuntu. I set it up with Folsom and 12.04 LTS. You might have troubles with duplicate address detection on Ubuntu guests, but it can be disabled (not sure if it's a bug on Debian/Ubuntu or what). I used nova networking (both Flat DHCP and VLAN) and nova starts radvd as necessary. Guests and host communicate with v6, firewall is not fully supported for v6 so it's for testing only. I didn't get v6 to the Internet though, as I have multiple interfaces on host and the one OpenStack is on is not connected to Internet - still looking into how to best connect this all :)

2013-06-28 08:29:23 -0500 asked a question Instances running on VMware ESXi cannot access metadata service

Hi,

I've configured OpenStack Grizzly to use ESXi 5.1 as hypervisor, following instructions in the docs. I have one machine running ESXi and another running a nova-compute instance that monitors it. Creating/deleting instances from OpenStack works as expected, instanced are created in ESXi (verified via vSphere Console) and started ok.

The trouble is that VMs can't access the nova metadata service and are unable to configure IPs. For instance, Ubuntu cloud images expect to access EC2 metadata-compatible service on http://169.254.169.254/.... Normally, with nova running on the same host as the hypervisor, this address is assigned to loopback interface and metadata service listens on it. Here I have two machines, and the ESXi host for VMs is not running nova-* anything. Is this setup ok? Should I enable anything else?

Thx, Marin