Hi Yipei,
Even running through neutron-lbaas I get the same successful test.
Just to double check, you are using the Octavia driver?
stack@devstackpy27-2:~$ sudo ip netns exec
qdhcp-4bcefe3e-038f-4a77-af4f-a560b6316a7a curl 172.21.1.16
Welcome to 172.21.1.17 connection 3
Michael
On Thu, Sep 28, 2017 at 7:46 AM, Yipei Niu <newy...@gmail.com> wrote:
> Hi, Michael,
>
> Thanks a lot. Look forward to your further test. I try deploying a new
> environment, too. Hope it can work well this time.
>
> Best regards,
> Yipei
>
> On Wed, Sep 27, 2017 at 10:27 AM, Yipei Niu <newy...@gmail.com> wrote:
>>
>> Hi, Michael,
>>
>> The instructions are listed as follows.
>>
>> First, create a net1.
>> $ neutron net-create net1
>> $ neutron subnet-create net1 10.0.1.0/24 --name subnet1
>>
>> Second, boot two vms in net1
>> $ nova boot --flavor 1 --image $image_id --nic net-id=$net1_id vm1
>> $ nova boot --flavor 1 --image $image_id --nic net-id=$net1_id vm2
>>
>> Third, logon to the two vms, respectively. Here take vm1 as an example.
>> $ MYIP=$(ifconfig eth0|grep 'inet addr'|awk -F: '{print $2}'| awk '{print
>> $1}')
>> $ while true; do echo -e "HTTP/1.0 200 OK\r\n\r\nWelcome to $MYIP" | sudo
>> nc -l -p 80 ; done&
>>
>> Fourth, exit vms and update the default security group shared by the vms
>> by adding a rule of allowing traffic to port 80.
>> $ neutron security-group-rule-create --direction ingress --protocol tcp
>> --port-range-min 80 --port-range-max 80 --remote-ip-refix 0.0.0.0/0
>> $default_security_group
>> Note: make sure "sudo ip netns exec $qdhcp-net1_id curl -v $vm_ip" works.
>> In other words, make sure the vms can accept HTTP requests and return its
>> IP, respectively.
>>
>> Fifth, create a lb, a listener, and a pool. Then add the two vms to the
>> pool as members.
>> $ neutron lbaas-loadbalancer-create --name lb1 subnet1
>> $ neutron lbaas-listener-create --loadbalancer lb1 --protocol HTTP
>> --protocol-port 80 --name listener1
>> $ neutron lbaas-pool-create --lb-algorithm ROUND_ROBIN --listener
>> listener1 --protocol HTTP --name pool1
>> $ neutron baas-member-create --subnet subnet1 --address $vm1_ip
>> --protocol-port 80 pool1
>> $ neutron baas-member-create --subnet subnet1 --address $vm2_ip
>> --protocol-port 80 pool1
>>
>> Finally, try "sudo ip netns qdhcp-net1_id curl -v $VIP" to see whether
>> lbaas works.
>>
>> Best regards,
>> Yipei
>>
>> On Wed, Sep 27, 2017 at 1:30 AM, Yipei Niu <newy...@gmail.com> wrote:
>>>
>>> Hi, Michael,
>>>
>>> I think the octavia is the latest, since I pull the up-to-date repo of
>>> octavia manually to my server before installation.
>>>
>>> Anyway, I run "sudo ip netns exec amphora-haproxy ip route show table 1"
>>> in the amphora, and find that the route table exists. The info is listed as
>>> follows.
>>>
>>> default via 10.0.1.1 dev eth1 onlink
>>>
>>> I think it may not be the source.
>>>
>>> Best regards,
>>> Yipei
>>
>>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
