[Neutron] Split Network node from controller Node

Zufar Dhiyaulhaq zufar at onf-ambassador.org
Mon Feb 11 16:46:45 UTC 2019


Hi

Thank you for your answer,
I just install the network agent in a network node,

with this following package

   - openstack-neutron.noarch
   - openstack-neutron-common.noarch
   - openstack-neutron-openvswitch.noarch
   - openstack-neutron-metering-agent.noarch

and configuring and appear in the agent list

[root at zu-controller1 ~(keystone_admin)]# openstack network agent list
+--------------------------------------+--------------------+----------------+-------------------+-------+-------+---------------------------+
| ID                                   | Agent Type         |
Host           | Availability Zone | Alive | State |
Binary                    |
+--------------------------------------+--------------------+----------------+-------------------+-------+-------+---------------------------+
| 025f8a15-03b5-421e-94ff-3e07fc1317b5 | Open vSwitch agent |
zu-compute2    | None              | :-)   | UP    |
neutron-openvswitch-agent |
| 04af3150-7673-4ac4-9670-fd1505737466 | Metadata agent     |
zu-network1    | None              | :-)   | UP    |
neutron-metadata-agent    |
| 11a9c764-e53d-4316-9801-fa2a931f0572 | Open vSwitch agent |
zu-compute1    | None              | :-)   | UP    |
neutron-openvswitch-agent |
| 1875a93f-09df-4c50-8660-1f4dc33b228d | L3 agent           |
zu-controller1 | nova              | :-)   | UP    |
neutron-l3-agent          |
| 1b492ed7-fbc2-4b95-ba70-e045e255a63d | L3 agent           |
zu-network1    | nova              | :-)   | UP    |
neutron-l3-agent          |
| 2fb2a714-9735-4f78-8019-935cb6422063 | Metering agent     |
zu-network1    | None              | :-)   | UP    |
neutron-metering-agent    |
| 3873fc10-1758-47e9-92b8-1e8605651c70 | Open vSwitch agent |
zu-network1    | None              | :-)   | UP    |
neutron-openvswitch-agent |
| 4b51bdd2-df13-4a35-9263-55e376b6e2ea | Metering agent     |
zu-controller1 | None              | :-)   | UP    |
neutron-metering-agent    |
| 54af229f-3dc1-49db-b32a-25f3fd62c010 | DHCP agent         |
zu-controller1 | nova              | :-)   | UP    |
neutron-dhcp-agent        |
| 9337c72b-8703-4c80-911b-106abe51ffbd | DHCP agent         |
zu-network1    | nova              | :-)   | UP    |
neutron-dhcp-agent        |
| a3c78231-027d-4ddd-8234-7afd1d67910e | Metadata agent     |
zu-controller1 | None              | :-)   | UP    |
neutron-metadata-agent    |
| aeb7537e-98af-49f0-914b-204e64cb4103 | Open vSwitch agent |
zu-controller1 | None              | :-)   | UP    |
neutron-openvswitch-agent |
+--------------------------------------+--------------------+----------------+-------------------+-------+-------+---------------------------+

I try to migrate the network (external & internal) and router into
zu-network1 (my new network node).
and success

[root at zu-controller1 ~(keystone_admin)]# openstack network agent list
--router $ROUTER_ID
+--------------------------------------+------------+-------------+-------------------+-------+-------+------------------+
| ID                                   | Agent Type | Host        |
Availability Zone | Alive | State | Binary           |
+--------------------------------------+------------+-------------+-------------------+-------+-------+------------------+
| 1b492ed7-fbc2-4b95-ba70-e045e255a63d | L3 agent   | zu-network1 |
nova              | :-)   | UP    | neutron-l3-agent |
+--------------------------------------+------------+-------------+-------------------+-------+-------+------------------+
[root at zu-controller1 ~(keystone_admin)]# openstack network agent list
--network $NETWORK_INTERNAL

+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+
| ID                                   | Agent Type | Host        |
Availability Zone | Alive | State | Binary             |
+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+
| 9337c72b-8703-4c80-911b-106abe51ffbd | DHCP agent | zu-network1 |
nova              | :-)   | UP    | neutron-dhcp-agent |
+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+
[root at zu-controller1 ~(keystone_admin)]# openstack network agent list
--network $NETWORK_EXTERNAL
+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+
| ID                                   | Agent Type | Host        |
Availability Zone | Alive | State | Binary             |
+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+
| 9337c72b-8703-4c80-911b-106abe51ffbd | DHCP agent | zu-network1 |
nova              | :-)   | UP    | neutron-dhcp-agent |
+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+

But, I cannot ping my instance after the migration.
I don't know why.

ii check my DHCP and router has already moved.

[root at zu-controller1 ~(keystone_admin)]# ip netns
[root at zu-controller1 ~(keystone_admin)]#

[root at zu-network1 ~]# ip netns
qdhcp-fddd647b-3601-43e4-8299-60b703405110 (id: 1)
qrouter-dd8ae033-0db2-4153-a060-cbb7cd18bae7 (id: 0)
[root at zu-network1 ~]#

What step do I miss?
Thanks

Best Regards,
Zufar Dhiyaulhaq


On Mon, Feb 11, 2019 at 3:13 PM Slawomir Kaplonski <skaplons at redhat.com>
wrote:

> Hi,
>
> I don’t know if there is any tutorial for that but You can just deploy new
> node with agents which You need, then disable old DHCP/L3 agents with
> neutron API [1] and move existing networks/routers to agents in new host
> with neutron API. Docs for agents scheduler API is in [2] and [3].
> Please keep in mind that when You will move routers to new agent You will
> have some downtime in data plane.
>
> [1] https://developer.openstack.org/api-ref/network/v2/#update-agent
> [2] https://developer.openstack.org/api-ref/network/v2/#l3-agent-scheduler
> [3]
> https://developer.openstack.org/api-ref/network/v2/#dhcp-agent-scheduler
>
> > Wiadomość napisana przez Zufar Dhiyaulhaq <zufar at onf-ambassador.org> w
> dniu 11.02.2019, o godz. 03:33:
> >
> > Hi everyone,
> >
> > I Have existing OpenStack with 1 controller node (Network Node in
> controller node) and 2 compute node. I need to expand the architecture by
> splitting the network node from controller node (create 1 node for
> network).
> >
> > Do you have any recommended step or tutorial for doing this?
> > Thanks
> >
> > Best Regards,
> > Zufar Dhiyaulhaq
>
>> Slawek Kaplonski
> Senior software engineer
> Red Hat
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190211/f6c2b60f/attachment.html>


More information about the openstack-discuss mailing list