fuel-dev team mailing list archive

[Vladimir Kozhukalov <vkozhukalov@xxxxxxxxxxxx>]

Andrey,

Technically, all networks are written down in
nailgun/nailgun/fixtures/openstack.json, but actually we have some hard
coded names for network groups in
nailgun/nailgun/api/models/network.py:NetworkGroup model. And we also have
hard coded logic about how to assign those networks to nodes according to
their roles
nailgun/nailgun/orchestrator/deployment_serializers.py:NetworkDeploymentSerializer.

So, in order to add another network for role you need to do all that hacks
to break default network assigning logic.

Vladimir Kozhukalov


On Mon, Mar 10, 2014 at 7:05 PM, Andrey Grebennikov <
agrebennikov@xxxxxxxxxxxx> wrote:

> Hello there all,
> Let me firstly introduce that I'm working with 3.2.1 because my customer
> uses Grizzly.
> Can anyone explain how can I add one more network in to the UI?
> The problem is that we are using external ceph cluster for glance
> purposes, but at the same time there is external storage as well. I'd like
> to avoid CLI usage, but for now it is necessary to configure additional
> interface for every node there.
> I need only network interface configuration at the moment.
>
> --
> 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
>
>