cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ahmad Emneina <aemne...@gmail.com>
Subject Re: [best practices] reserved system IPs
Date Thu, 07 Feb 2013 20:10:53 GMT
ok, phew.

Our convo did go private for an email or two. Lucian did have to make an
effort to bring it back.


On Thu, Feb 7, 2013 at 12:07 PM, Sebastien Goasguen <runseb@gmail.com>wrote:

> no we did not !
>
> I like reading you guys having a chat, it's very instructive.
>
> thanks
>
> -sebastien
>
> On Feb 7, 2013, at 9:04 PM, Ahmad Emneina <aemneina@gmail.com> wrote:
>
> > boogers, i think everyone missed out on this convo because of the awesome
> > new reply modifications.
> >
> >
> > On Thu, Feb 7, 2013 at 12:03 PM, Ahmad Emneina <aemneina@gmail.com>
> wrote:
> >
> >> yes, exactly.
> >>
> >>
> >> On Thu, Feb 7, 2013 at 12:00 PM, Nux! <nux@li.nux.ro> wrote:
> >>
> >>> On 07.02.2013 19:13, Ahmad Emneina wrote:
> >>>
> >>>> i believe what you want to do is have 2 nics on the host. 1 for guest
> >>>> traffic (public) and another for management traffic (private). Giving
> a
> >>>> hypervisor a public ip is not advisable.
> >>>>
> >>>
> >>> So in this case, could I connect all hypervisors and management servers
> >>> on their secondary interface and use some private range there? And when
> >>> asked for reserved IPs at pod creation give out IPs from this range?
> >>>
> >>>
> >>> Lucian
> >>>
> >>> --
> >>> Sent from the Delta quadrant using Borg technology!
> >>>
> >>> Nux!
> >>> www.nux.ro
> >>>
> >>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message