Also, on a completely unrelated note (but still very important) My nova resource tracker only reports that I have 49 GB of available disk space for the creation of VMs. This seems to reflect the approximate size of my root partition. I'm wondering if I missed a setting that controls this? I have a cinder-volumes group that is approx 450GB in size, so I'm not sure how nova-compute is getting its numbers wrong. Thanks.
On Fri, Aug 2, 2013 at 11:01 AM, Brandon Adams < [email protected]> wrote: > Hi all, > > I'm attempting to set up an installation of OpenStack Grizzly on a single > node running Centos 6.4 with two NICs. eth0 is 192.168.0.x (public, other > computers in the office are on this network) and eth1 is 10.0.0.x (using as > private). A few questions: > > Does it make a difference that eth1, my private network, has internet > access? My box is the only thing that has access to this network. It is > managed by my offices router. I have a feeling this might be causing a > problem somewhere. > > When I created my bridge, I gave it the default value of 192.168.100.1, > and bridged it to eth1. When I did this, eth1 lost its IP address. Is this > normal? > > When I spawn an instance through nova, it is assigned an IP from the range > of the internal network (192.168.100.x). I've created a set of floating > IPs, and assigned one to it. But whenever I try and access it with iptables > up, the host is unreachable. When I disable iptables, it allows me to > connect, but I'm connecting to the localhost, not the VM. Any thoughts? > > I can also dump any .conf files if anyone thinks it would help. I'd really > appreciate any tips you all might have. Thanks. > > Brandon >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
