fuel-dev team mailing list archive

[Meg McRoberts <mmcroberts@xxxxxxxxxxxx>]

I'd like to capture this in the documentation.  The networking doc really
needs a major rewrite
and that isn't going to happen for 5.1.  But I see two possibilities:

- Add a section called "Logical network configuration options" -- maybe you
have a better title --
  to the Planning Guide.  Does anyone (maybe on the Support side?) have any
notes I could use
  for that?
- Augment the description of the logical networks in
http://docs.mirantis.com/openstack/fuel/master/reference-architecture.html#network-architecture
  I would rather not get this description bogged down with lots of details
but it's an option.

meg

On Wed, Sep 10, 2014 at 5:06 AM, Sergii Golovatiuk <sgolovatiuk@xxxxxxxxxxxx
> wrote:

> Hi,
>
> I know customers are asking for special network for 'live migrations' and
> ceph replication. However, that would be nice not to limit architecture to
> couple of roles and allow the customers to model networking topology on
> their own.
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
> On Wed, Sep 10, 2014 at 1:13 PM, Sergey Vasilenko <svasilenko@xxxxxxxxxxxx
> > wrote:
>
>> I propose following solution. Make multiple network roles (i.e.
>> storage/ceph/sync, storage/ceph/access) for possibility of divide this
>> networks. By default those roles may be mapped to the management network.
>>
>> /sv
>>
>>
>> --
>> 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
>>
>>
>
> --
> 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
>
>