1:01 p.m.
Today I went to a local University and did a "what is OpenStack"
presentation. When I got to the demo part, (all in one, on a laptop) I
couldn't log in to Horizon, and didn't have time to troubleshoot
on-site. Back home again, and everything works perfectly.
So, in retrospect, this was a case of poor planning, but I'd like to
figure out how to have it not happen again, preferably even if I have to
do a demo that is completely off-line.
Is it simply a matter of changing 192.168.0.x to 127.0.0.1 in all of my
OpenStack configuration files, or is there going to be more to it than that?
--Rich
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
1:26 p.m.
On Wed, Jun 25, 2014 at 02:01:06PM -0400, Rich Bowen wrote:
So, in retrospect, this was a case of poor planning, but I'd like
to figure
out how to have it not happen again, preferably even if I have to do a demo
that is completely off-line.
Rich,
It sounds like maybe you had services configured to use an ip address
that was attached to your external interface that -- predictably --
changed when booting in a new environment.
I like to run OpenStack demos inside virtual machines in my laptop.
This makes the network configuration completely independent from my
laptop's external interface.
I use a MASQUERADE rule on the host to give instances in this
environment external access. That is, rather than attaching a
physical nic to br-ex, I just give br-ex an ip address and then set up
a masquerade rule for anything FROM that address range to eth0;
something like:
iptables -t nat -A POSTROUTING -s 172.16.0.0/24 -o eth0 -j MASQUERADE
--
Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ irc
Cloud Engineering / OpenStack | " " @ twitter
1:32 a.m.
On Wed, Jun 25, 2014 at 02:26:02PM -0400, Lars Kellogg-Stedman wrote:
On Wed, Jun 25, 2014 at 02:01:06PM -0400, Rich Bowen wrote:
> So, in retrospect, this was a case of poor planning, but I'd like to figure
> out how to have it not happen again, preferably even if I have to do a demo
> that is completely off-line.
Rich,
It sounds like maybe you had services configured to use an ip address
that was attached to your external interface that -- predictably --
changed when booting in a new environment.
I like to run OpenStack demos inside virtual machines in my laptop.
Yep, I'd second the above comment. I do find it quite convenient to have
an OpenStack setup in virtual machines. I can even upload them to a
remote test machine to reproduce bugs, etc.
This makes the network configuration completely independent from my
laptop's external interface.
I use a MASQUERADE rule on the host to give instances in this
environment external access. That is, rather than attaching a
physical nic to br-ex, I just give br-ex an ip address and then set up
a masquerade rule for anything FROM that address range to eth0;
something like:
iptables -t nat -A POSTROUTING -s 172.16.0.0/24 -o eth0 -j MASQUERADE
Thanks for this tip, so far I got by w/o adding this rule.
--
/kashyap
4:22 a.m.
On Wed, Jun 25, 2014 at 02:01:06PM -0400, Rich Bowen wrote:
Is it simply a matter of changing 192.168.0.x to 127.0.0.1 in all of
my
OpenStack configuration files, or is there going to be more to it than that?
That's, what I regularly do in my packstack config. Saves me lots of
headaches, as I have OpenStack directly installed on my laptop.
--
Matthias Runge <mrunge(a)redhat.com>
3834
days inactive
3836
days old
3 comments
4 participants
participants (4)
-
Kashyap Chamarthy -
Lars Kellogg-Stedman -
Matthias Runge -
Rich Bowen