fuel-dev team mailing list archive

[Dmitriy Novakovskiy <dnovakovskiy@xxxxxxxxxxxx>]

>
>
>
>
>
>
> *1) All networks support (multiple) ranges, only public has this shown
> (but they all should have them displayed). This is necessary in theevent
> that you have a large network, for example /20 but want to use addresses
> from multiple segments. Alternately your range may bepartially used in the
> middle, but you want/need to use the addresses around the range.*


So does it mean that there's a bug and other networks should have "plus"
button too? Is it reported, or do I need to report one?


> *really the floating network address should be under the public range,
> another issue I need to raise.*


Just to double-check - do you mean "under" on GUI (positioning) or "under"
- one range is a subset of another :) ?

---
Regards,
Dmitriy


On Sat, Jul 12, 2014 at 2:49 AM, Andrew Woodward <xarses@xxxxxxxxx> wrote:

> 1) All networks support (multiple) ranges, only public has this shown
> (but they all should have them displayed). This is necessary in the
> event that you have a large network, for example /20 but want to use
> addresses from multiple segments. Alternately your range may be
> partially used in the middle, but you want/need to use the addresses
> around the range.
>
> 2) All settings are locked after starting the deployment, it's a one
> time thing and they must be inside the public network, really the
> floating network address should be under the public range, another
> issue I need to raise.
>
> 3) private networks only corresponds to vlans, in which case the
> private network role should be visible.  In the case of encapsulated
> networks, br-tun will end up being patched through to management there
> is a bug open on this [1].
>
> [1] https://bugs.launchpad.net/fuel/+bug/1285059
>
> On Fri, Jul 11, 2014 at 4:17 PM, Dmitriy Novakovskiy
> <dnovakovskiy@xxxxxxxxxxxx> wrote:
> > Hi Fuelers,
> >
> > I was messing around "Networks" tab in Fuel and got some questions around
> > it. Victor Denisov helped me with most of them, but some that left I
> thought
> > I'd bring your attention
> >
> > 1) Why does Fuel allow multiple ranges for Public network?
> >
> > I understand why Floating needs multiple ranges, but can't quite
> understand
> > why Public does. Or, how Public is different from Management in this
> > context. Probably there's some specific use case when Public needs
> multiple
> > ranges, I just want to understand what...
> >
> > 2) Is it possible to add Floating IP range to a running cloud by pressing
> > blue "plus" button in "Neutron L3 settings" section, adding range and
> > pressing Save settings? Or it's one-time, pre-deployment decision?
> >
> > 3) Where is Internal network placed (the one which carriers
> > encapsulated/tunneled trafic of Private networks)? Is it co-located w/
> > Management? I can't see it on Interface setup screen
> >
> > Thanks
> >
> > ---
> > Regards,
> > Dmitriy
> >
> > --
> > Mailing list: https://launchpad.net/~fuel-dev
> > Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~fuel-dev
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
>
> --
> Andrew
> Mirantis
> Ceph community
>