Open Stack

Excellent!

You're going to want to remove the 192.* addresses and make sure both NICs
are cabled to the same layer-2 network.  One NIC will have your 133.*
address (host management and API access), and one will be completely
unnumbered (VM traffic).

So, if you have your 133.* NIC plugged in to one switch, and your 192.* NIC
plugged into another, just move the cables from the 192.* switch and plug
them in to the 133.* switch.  This is a very rudimentary explanation that
doesn't account for any fancy network topology on your side, so, depending
on the specific configs on your switches, it *may* not be as simple as that
in your environment.  The end-goal is that you want both of your NICs to be
able to talk on the same network, but only one of them has an address.

Does that clear things up?

On Thu Nov 20 2014 at 2:53:50 AM Georgios Dimitrakakis <giorgis at acmac.uoc.gr>
wrote:

>  Yes!
>
>  I am planning to assign 133.* IP addresses to all guest instances.
>
>  Best,
>
>  George
>
>  On Thu, 20 Nov 2014 02:42:08 +0000, Aaron Segura wrote:
> > Okay, I believe I see what youre going for now.  Are you planning on
> > assigning 133.* addresses directly to your guest instances?
> >
> > On Wed Nov 19 2014 at 5:53:36 PM Dimitrakakis Georgios  wrote:
> >
> >> Sorry about the confusion!
> >>
> >> I have two nodes, with two network interfaces each. One configured
> >> with 192.* IP and one with 133.*
> >> I can access them with SSH directly at 133.*
> >>
> >> Both nodes can ping one another and both nodes can ping Internet
> >> addresses e.g.  google. com
> >>
> >> No other router available for configuration.
> >> No openstack yet.
> >>
> >> So, my question is the following :
> >>
> >> If I want to install openstack should I modify the external network
> >> interface so that it doesnt have an IP address?  If I do that how
> >> can I access the server then?
> >>
> >> I was under the impression that the document was talking about a
> >> situation like the above when it clearly doesnt. Thats why I am
> >> looking for new guidelines.
> >>
> >> All the best,
> >>
> >> George
> >>
> >> ---- Ο χρήστης Aaron Segura έγραψε ----
> >>
> >> Im not sure I understand.  Are you able to ping from your nodes out
> >> to the internet at all?
> >>
> >> On Wed Nov 19 2014 at 3:29:54 PM Georgios Dimitrakakis wrote:
> >>
> >>>  Aaron it helps a lot and thank you for that.
> >>>
> >>>  Unfortunately in my setup there is no router for the management
> >>>  interface since it is much simpler and has two interfaces: one
> >>> that has
> >>>  an external IP and connects directly to the internet and a
> >>> second one
> >>>  with internal (management) network that cannot be reached from
> >>> the
> >>>  outside. In such a case can you recommend a setup or point me
> >>> at a
> >>>  documentation?
> >>>
> >>>  Thanks a lot again,
> >>>
> >>>  George
> >>>
> >>>  On Wed, 19 Nov 2014 20:39:10 +0000, Aaron Segura wrote:
> >>> > When the documentation refers to testing external connectivity
> >>> from
> >>> > the nodes, it does not mean to test connectivity via the
> >>> External
> >>> > Interface, irself.  It means that you should be able to reach
> >>> the
> >>> > external network (Internet) and the other nodes, from each
> >>> node, via
> >>> > the Management Interface.  The Management Interface is how you
> >>> will
> >>> > log in to the nodes via SSH, as well.  The network attached to
> >>> your
> >>> > Management Interface should have a route out to the Internet
> >>> and
> >>> > provide all the connectivity you need to manage the node,
> >>> install
> >>> > software, etc...
> >>> >
> >>> > Hope that helps!
> >>> >
> >>> > On Wed Nov 19 2014 at 2:19:07 PM Georgios Dimitrakakis  wrote:
> >>> >
> >>> >>  First of all let me thank you very much for your clear
> >>> replies!
> >>> >>
> >>> >>  Yes! That makes sense indeed for the Virtual Machines!
> >>> >>
> >>> >>  What about the compute node itself? If I am not wrong at
> >>> that
> >>> >> point of
> >>> >>  documentation nova-network hasnt been installed or
> >>> configured. So
> >>> >> how
> >>> >>  is it possible the connectivity tests with the external
> >>> network
> >>> >> to be
> >>> >>  successful as shown at that point?
> >>> >>
> >>> >>  Furthermore if someone wants to have direct SSH access to
> >>> the
> >>> >> node from
> >>> >>  the external network how is that achieved? In general how
> >>> does
> >>> >> the
> >>> >>  physical node itself access the external network?
> >>> >>
> >>> >>  All the best,
> >>> >>
> >>> >>  George
> >>> >>
> >>> >>  On Wed, 19 Nov 2014 14:25:29 +0000, Aaron Segura wrote:
> >>> >> > Think of your external interface as if it were a switch. The
> >>> >> guests
> >>> >> > are plugged in to the switch. They will have IP addresses
> >>> that
> >>> >> allow
> >>> >> > them to communicate on the network. The physical interface
> >>> just
> >>> >> ships
> >>> >> > packets back and forth between physical and virtual
> >>> networks, and
> >>> >> > doesnt need its own address. Make more sense?
> >>> >> >
> >>> >> > On Wed, Nov 19, 2014, 07:53 Georgios Dimitrakakis  wrote:
> >>> >> >
> >>> >> >>  Hello stackers!
> >>> >> >>
> >>> >> >>  In OpenStack documentation and specifically on Legacy
> >>> >> Networking
> >>> >> >>
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >>
> >>> >
> >>> >
> >>>
> >>
> >
> >  http://docs.openstack.org/juno/install-guide/install/yum/co
> ntent/ch_basic_environment.html#basics-networking-nova
> >>> [1]
> >>> >> [1]
> >>> >> >> [1]
> >>> >> >>
> >>> >> >>  says clearly that for a two node installation the
> >>> interface
> >>> >> >> dedicated
> >>> >> >>  to the external network should not be configured with an
> >>> IP
> >>> >> >> address.
> >>> >> >>
> >>> >> >>  Is this correct??
> >>> >> >>
> >>> >> >>  Furthermore at the "Verify Connectivity" part is pinging
> >>> >> >> successfully
> >>> >> >>  on the external network and my question is how is this
> >>> >> happening?
> >>> >> >> Does
> >>> >> >>  it assume that there is a third interface already
> >>> connected on
> >>> >> >> the
> >>> >> >>  external network??
> >>> >> >>
> >>> >> >>  How is accessing the external network without even
> >>> configuring
> >>> >> >> the
> >>> >> >>  interface dedicated at it?? Does it assume that the
> >>> internal
> >>> >> >> network
> >>> >> >>  somehow performs a routing??
> >>> >> >>
> >>> >> >>  Best regards,
> >>> >> >>
> >>> >> >>  G.
> >>> >> >>
> >>> >> >> _______________________________________________
> >>> >> >> Mailing list:
> >>> >> >>
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [2]
> >>> >> [2] [2]
> >>> >> >> Post to     : openstack at lists.openstack.org [3] [3] [3]
> >>> >> >> Unsubscribe :
> >>> >> >>
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [4]
> >>> >> [4] [4]
> >>> >> >
> >>> >> >
> >>> >> > Links:
> >>> >> > ------
> >>> >> > [1]
> >>> >> >
> >>> >> >
> >>> >>
> >>> >
> >>> >
> >>>
> >>
> >
> > http://docs.openstack.org/juno/install-guide/install/yum/con
> tent/ch_basic_environment.html#basics-networking-nova
> >>> [5]
> >>> >> [5]
> >>> >> > [2]
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [6]
> >>> >> [6]
> >>> >> > [3] mailto:openstack at lists.openstack.org [7] [7]
> >>> >> > [4]
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [8]
> >>> >> [8]
> >>> >> > [5] mailto:giorgis at acmac.uoc.gr [9] [9]
> >>> >
> >>> >
> >>> > Links:
> >>> > ------
> >>> > [1]
> >>> >
> >>> >
> >>>
> >>
> >
> > http://docs.openstack.org/juno/install-guide/install/yum/con
> tent/ch_basic_environment.html#basics-networking-nova
> >>> [10]
> >>> > [2]
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [11]
> >>> > [3] mailto:openstack at lists.openstack.org [12]
> >>> > [4]
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [13]
> >>> > [5]
> >>> >
> >>> >
> >>>
> >>
> >
> > http://docs.openstack.org/juno/install-guide/install/yum/con
> tent/ch_basic_environment.html#basics-networking-nova
> >>> [14]
> >>> > [6]
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [15]
> >>> > [7] mailto:openstack at lists.openstack.org [16]
> >>> > [8]
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [17]
> >>> > [9] mailto:giorgis at acmac.uoc.gr [18]
> >>> > [10] mailto:giorgis at acmac.uoc.gr [19]
> >>
> >>> --
> >
> >
> > Links:
> > ------
> > [1]
> >
> > http://docs.openstack.org/juno/install-guide/install/yum/con
> tent/ch_basic_environment.html#basics-networking-nova
> > [2] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > [3] mailto:openstack at lists.openstack.org
> > [4] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > [5]
> >
> > http://docs.openstack.org/juno/install-guide/install/yum/con
> tent/ch_basic_environment.html#basics-networking-nova
> > [6] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > [7] mailto:openstack at lists.openstack.org
> > [8] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > [9] mailto:giorgis at acmac.uoc.gr
> > [10]
> >
> > http://docs.openstack.org/juno/install-guide/install/yum/con
> tent/ch_basic_environment.html#basics-networking-nova
> > [11] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > [12] mailto:openstack at lists.openstack.org
> > [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > [14]
> >
> > http://docs.openstack.org/juno/install-guide/install/yum/con
> tent/ch_basic_environment.html#basics-networking-nova
> > [15] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > [16] mailto:openstack at lists.openstack.org
> > [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > [18] mailto:giorgis at acmac.uoc.gr
> > [19] mailto:giorgis at acmac.uoc.gr
> > [20] mailto:giorgis at acmac.uoc.gr
> > [21] mailto:giorgis at acmac.uoc.gr
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20141120/a7a2ea05/attachment.html>