<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hi</div><div><br></div><div>Thank you for your answer,<br></div><div>I just install the network agent in a network node,</div><div><br></div><div>with this following package</div><ul><li>openstack-neutron.noarch</li><li>openstack-neutron-common.noarch</li><li>openstack-neutron-openvswitch.noarch</li><li>openstack-neutron-metering-agent.noarch</li></ul><div><div><div dir="ltr" class="gmail-m_-1911359730429591229gmail_signature"><div dir="ltr"><span><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>and configuring and appear in the agent list</span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span><br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>[root@zu-controller1 ~(keystone_admin)]# openstack network agent list<br>+--------------------------------------+--------------------+----------------+-------------------+-------+-------+---------------------------+<br>| ID | Agent Type | Host | Availability Zone | Alive | State | Binary |<br>+--------------------------------------+--------------------+----------------+-------------------+-------+-------+---------------------------+<br>| 025f8a15-03b5-421e-94ff-3e07fc1317b5 | Open vSwitch agent | zu-compute2 | None | :-) | UP | neutron-openvswitch-agent |<br>| 04af3150-7673-4ac4-9670-fd1505737466 | Metadata agent | zu-network1 | None | :-) | UP | neutron-metadata-agent |<br>| 11a9c764-e53d-4316-9801-fa2a931f0572 | Open vSwitch agent | zu-compute1 | None | :-) | UP | neutron-openvswitch-agent |<br>| 1875a93f-09df-4c50-8660-1f4dc33b228d | L3 agent | zu-controller1 | nova | :-) | UP | neutron-l3-agent |<br>| 1b492ed7-fbc2-4b95-ba70-e045e255a63d | L3 agent | zu-network1 | nova | :-) | UP | neutron-l3-agent |<br>| 2fb2a714-9735-4f78-8019-935cb6422063 | Metering agent | zu-network1 | None | :-) | UP | neutron-metering-agent |<br>| 3873fc10-1758-47e9-92b8-1e8605651c70 | Open vSwitch agent | zu-network1 | None | :-) | UP | neutron-openvswitch-agent |<br>| 4b51bdd2-df13-4a35-9263-55e376b6e2ea | Metering agent | zu-controller1 | None | :-) | UP | neutron-metering-agent |<br>| 54af229f-3dc1-49db-b32a-25f3fd62c010 | DHCP agent | zu-controller1 | nova | :-) | UP | neutron-dhcp-agent |<br>| 9337c72b-8703-4c80-911b-106abe51ffbd | DHCP agent | zu-network1 | nova | :-) | UP | neutron-dhcp-agent |<br>| a3c78231-027d-4ddd-8234-7afd1d67910e | Metadata agent | zu-controller1 | None | :-) | UP | neutron-metadata-agent |<br>| aeb7537e-98af-49f0-914b-204e64cb4103 | Open vSwitch agent | zu-controller1 | None | :-) | UP | neutron-openvswitch-agent |<br>+--------------------------------------+--------------------+----------------+-------------------+-------+-------+---------------------------+<br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span><br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>I try to migrate the network (external & internal) and router into zu-network1 (my new network node). <br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>and success</span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span><br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>[root@zu-controller1 ~(keystone_admin)]# openstack network agent list --router $ROUTER_ID<br>+--------------------------------------+------------+-------------+-------------------+-------+-------+------------------+<br>| ID | Agent Type | Host | Availability Zone | Alive | State | Binary |<br>+--------------------------------------+------------+-------------+-------------------+-------+-------+------------------+<br>| 1b492ed7-fbc2-4b95-ba70-e045e255a63d | L3 agent | zu-network1 | nova | :-) | UP | neutron-l3-agent |<br>+--------------------------------------+------------+-------------+-------------------+-------+-------+------------------+<br>[root@zu-controller1 ~(keystone_admin)]# openstack network agent list --network $NETWORK_INTERNAL<br><br>+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+<br>| ID | Agent Type | Host | Availability Zone | Alive | State | Binary |<br>+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+<br>| 9337c72b-8703-4c80-911b-106abe51ffbd | DHCP agent | zu-network1 | nova | :-) | UP | neutron-dhcp-agent |<br>+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+<br>[root@zu-controller1 ~(keystone_admin)]# openstack network agent list --network $NETWORK_EXTERNAL<br>+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+<br>| ID | Agent Type | Host | Availability Zone | Alive | State | Binary |<br>+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+<br>| 9337c72b-8703-4c80-911b-106abe51ffbd | DHCP agent | zu-network1 | nova | :-) | UP | neutron-dhcp-agent |<br>+--------------------------------------+------------+-------------+-------------------+-------+-------+--------------------+<br><br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>But, I cannot ping my instance after the migration.</span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>I don't know why.</span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span><br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>ii check my DHCP and router has already moved.</span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span><br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>[root@zu-controller1 ~(keystone_admin)]# ip netns<br>[root@zu-controller1 ~(keystone_admin)]# <br><br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>[root@zu-network1 ~]# ip netns<br>qdhcp-fddd647b-3601-43e4-8299-60b703405110 (id: 1)<br>qrouter-dd8ae033-0db2-4153-a060-cbb7cd18bae7 (id: 0)<br>[root@zu-network1 ~]# <br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span><br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>What step do I miss?</span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>Thanks<br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span><br></span></span></span></div><div><span style="font-family:arial,helvetica,sans-serif"><span lang="en"><span>Best Regards,<br></span></span></span></div><span lang="en"><span><span style="font-family:arial,helvetica,sans-serif">Zufar Dhiyaulhaq</span></span></span></span></div></div></div><br></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 11, 2019 at 3:13 PM Slawomir Kaplonski <<a href="mailto:skaplons@redhat.com" target="_blank">skaplons@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
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].<br>
Please keep in mind that when You will move routers to new agent You will have some downtime in data plane.<br>
<br>
[1] <a href="https://developer.openstack.org/api-ref/network/v2/#update-agent" rel="noreferrer" target="_blank">https://developer.openstack.org/api-ref/network/v2/#update-agent</a><br>
[2] <a href="https://developer.openstack.org/api-ref/network/v2/#l3-agent-scheduler" rel="noreferrer" target="_blank">https://developer.openstack.org/api-ref/network/v2/#l3-agent-scheduler</a><br>
[3] <a href="https://developer.openstack.org/api-ref/network/v2/#dhcp-agent-scheduler" rel="noreferrer" target="_blank">https://developer.openstack.org/api-ref/network/v2/#dhcp-agent-scheduler</a><br>
<br>
> Wiadomość napisana przez Zufar Dhiyaulhaq <<a href="mailto:zufar@onf-ambassador.org" target="_blank">zufar@onf-ambassador.org</a>> w dniu 11.02.2019, o godz. 03:33:<br>
> <br>
> Hi everyone, <br>
> <br>
> 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). <br>
> <br>
> Do you have any recommended step or tutorial for doing this? <br>
> Thanks<br>
> <br>
> Best Regards,<br>
> Zufar Dhiyaulhaq<br>
<br>
— <br>
Slawek Kaplonski<br>
Senior software engineer<br>
Red Hat<br>
<br>
</blockquote></div>