octavia: what is the loadbalancer IP assigned to?












0















I am trying to understand how Octavia is put together. I created a loadbalancer on a vlan network. It was assigned an address of 10.40.0.7. When I do openstack loadbalancer list, I see a vip_address of 10.40.0.7 which is not assigned to any amphorae.



I want to understand where the loadbalancer address is mapped. It is not a host. I can't ssh to that address. Perhaps it is the amphora driver but what exactly is that? I can't see that address find it in any namespace. I can't see it assigned to any bridge. What is it assigned to?



Thanks



Ranga










share|improve this question





























    0















    I am trying to understand how Octavia is put together. I created a loadbalancer on a vlan network. It was assigned an address of 10.40.0.7. When I do openstack loadbalancer list, I see a vip_address of 10.40.0.7 which is not assigned to any amphorae.



    I want to understand where the loadbalancer address is mapped. It is not a host. I can't ssh to that address. Perhaps it is the amphora driver but what exactly is that? I can't see that address find it in any namespace. I can't see it assigned to any bridge. What is it assigned to?



    Thanks



    Ranga










    share|improve this question



























      0












      0








      0








      I am trying to understand how Octavia is put together. I created a loadbalancer on a vlan network. It was assigned an address of 10.40.0.7. When I do openstack loadbalancer list, I see a vip_address of 10.40.0.7 which is not assigned to any amphorae.



      I want to understand where the loadbalancer address is mapped. It is not a host. I can't ssh to that address. Perhaps it is the amphora driver but what exactly is that? I can't see that address find it in any namespace. I can't see it assigned to any bridge. What is it assigned to?



      Thanks



      Ranga










      share|improve this question
















      I am trying to understand how Octavia is put together. I created a loadbalancer on a vlan network. It was assigned an address of 10.40.0.7. When I do openstack loadbalancer list, I see a vip_address of 10.40.0.7 which is not assigned to any amphorae.



      I want to understand where the loadbalancer address is mapped. It is not a host. I can't ssh to that address. Perhaps it is the amphora driver but what exactly is that? I can't see that address find it in any namespace. I can't see it assigned to any bridge. What is it assigned to?



      Thanks



      Ranga







      openstack






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 16 '18 at 3:23







      LostInTheFrequencyDomain

















      asked Nov 16 '18 at 0:42









      LostInTheFrequencyDomainLostInTheFrequencyDomain

      618523




      618523
























          1 Answer
          1






          active

          oldest

          votes


















          1















          It is not a host.




          It is a host! An amphora is just a nova server -- the same thing you get when you run openstack server create. The difference is that the amphora is owned by the service project, so you'll only see it if you were to run (as admin) openstack server list --all-projects. For example:



          $ openstack --os-cloud as_me loadbalancer list
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | id | name | project_id | vip_address | provisioning_status | provider |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | 64a6a56d-beeb-4ee2-b495-1cdc26ffd399 | test_lb | 0ac1e30189da48b387cf3c2f5582b2a3 | 10.254.0.6 | ACTIVE | octavia |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+

          $ openstack --os-cloud as_admin server list --all-projects | grep amphora
          | f6cd75fe-8513-4aae-bee9-af9362525703 | amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af | ACTIVE | lb-mgmt-net=172.24.0.16; test_lb_net=10.254.0.11; test_net1=10.0.1.5; test_net0=10.0.0.4 | octavia-amphora-13.0-20181107.1.x86_64 | octavia_65 |


          If you look at that server, you'll see it has several ip addresses:




          • The one you assigned to it when created the loadbalancer, and

          • A management network address

          • Addresses on any subnets to which it is attached


          You can ssh into the amphora using the management network address. You should be able to reach it from your controllers. You'll need the appropriate ssh key; where to find that probably depends a lot on how you installed things. I'm using tripleo, and it looks as if the install uses ~/.ssh/id_rsa from the stack user for the amphora ssh key.



          [controller ~]$ ssh -i amphora_private_key cloud-user@172.24.0.7
          Last login: Thu Nov 15 22:01:16 2018 from 172.24.0.6
          [cloud-user@amphora-7d48e10b-5ba4-42c9-bcd5-941d224b2a46 ~]$


          Update



          The loadbalancer VIP is assigned to an interface inside a namespace on
          the amphora. Given the above configuration, I see:



          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns
          amphora-haproxy (id: 0)
          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns exec amphora-haproxy ip a
          1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
          link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
          3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:07:d2:26 brd ff:ff:ff:ff:ff:ff
          inet 10.254.0.11/24 brd 10.254.0.255 scope global eth1
          valid_lft forever preferred_lft forever
          inet 10.254.0.6/24 brd 10.254.0.255 scope global secondary eth1:0
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe07:d226/64 scope link
          valid_lft forever preferred_lft forever
          4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:21:9a:d1 brd ff:ff:ff:ff:ff:ff
          inet 10.0.0.4/24 brd 10.0.0.255 scope global eth2
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe21:9ad1/64 scope link
          valid_lft forever preferred_lft forever
          5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:2a:63:58 brd ff:ff:ff:ff:ff:ff
          inet 10.0.1.5/24 brd 10.0.1.255 scope global eth3
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe2a:6358/64 scope link
          valid_lft forever preferred_lft forever





          share|improve this answer


























          • I can ssh into the amphora. However, I have an address that is not assigned to any amphora. I see a VIP address in openstack loadbalancer list. What is this assigned to? I can log into the amphorae.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:22













          • I think I found my answer. It is assigned to an openstack port.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:36











          • Right. When you openstack loadbalancer show your load balancer, you can see the port id.

            – larsks
            Nov 16 '18 at 3:43











          • Still looking for what IP abstraction that the port maps to ( i.e. is it a namespace, veth pair in a namespace or virutal device .. what exactly?)

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:57











          • The vip is assigned to an interface in a namespace on the amphora. See my update to the answer for details.

            – larsks
            Nov 16 '18 at 17:50











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53329843%2foctavia-what-is-the-loadbalancer-ip-assigned-to%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1















          It is not a host.




          It is a host! An amphora is just a nova server -- the same thing you get when you run openstack server create. The difference is that the amphora is owned by the service project, so you'll only see it if you were to run (as admin) openstack server list --all-projects. For example:



          $ openstack --os-cloud as_me loadbalancer list
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | id | name | project_id | vip_address | provisioning_status | provider |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | 64a6a56d-beeb-4ee2-b495-1cdc26ffd399 | test_lb | 0ac1e30189da48b387cf3c2f5582b2a3 | 10.254.0.6 | ACTIVE | octavia |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+

          $ openstack --os-cloud as_admin server list --all-projects | grep amphora
          | f6cd75fe-8513-4aae-bee9-af9362525703 | amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af | ACTIVE | lb-mgmt-net=172.24.0.16; test_lb_net=10.254.0.11; test_net1=10.0.1.5; test_net0=10.0.0.4 | octavia-amphora-13.0-20181107.1.x86_64 | octavia_65 |


          If you look at that server, you'll see it has several ip addresses:




          • The one you assigned to it when created the loadbalancer, and

          • A management network address

          • Addresses on any subnets to which it is attached


          You can ssh into the amphora using the management network address. You should be able to reach it from your controllers. You'll need the appropriate ssh key; where to find that probably depends a lot on how you installed things. I'm using tripleo, and it looks as if the install uses ~/.ssh/id_rsa from the stack user for the amphora ssh key.



          [controller ~]$ ssh -i amphora_private_key cloud-user@172.24.0.7
          Last login: Thu Nov 15 22:01:16 2018 from 172.24.0.6
          [cloud-user@amphora-7d48e10b-5ba4-42c9-bcd5-941d224b2a46 ~]$


          Update



          The loadbalancer VIP is assigned to an interface inside a namespace on
          the amphora. Given the above configuration, I see:



          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns
          amphora-haproxy (id: 0)
          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns exec amphora-haproxy ip a
          1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
          link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
          3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:07:d2:26 brd ff:ff:ff:ff:ff:ff
          inet 10.254.0.11/24 brd 10.254.0.255 scope global eth1
          valid_lft forever preferred_lft forever
          inet 10.254.0.6/24 brd 10.254.0.255 scope global secondary eth1:0
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe07:d226/64 scope link
          valid_lft forever preferred_lft forever
          4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:21:9a:d1 brd ff:ff:ff:ff:ff:ff
          inet 10.0.0.4/24 brd 10.0.0.255 scope global eth2
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe21:9ad1/64 scope link
          valid_lft forever preferred_lft forever
          5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:2a:63:58 brd ff:ff:ff:ff:ff:ff
          inet 10.0.1.5/24 brd 10.0.1.255 scope global eth3
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe2a:6358/64 scope link
          valid_lft forever preferred_lft forever





          share|improve this answer


























          • I can ssh into the amphora. However, I have an address that is not assigned to any amphora. I see a VIP address in openstack loadbalancer list. What is this assigned to? I can log into the amphorae.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:22













          • I think I found my answer. It is assigned to an openstack port.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:36











          • Right. When you openstack loadbalancer show your load balancer, you can see the port id.

            – larsks
            Nov 16 '18 at 3:43











          • Still looking for what IP abstraction that the port maps to ( i.e. is it a namespace, veth pair in a namespace or virutal device .. what exactly?)

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:57











          • The vip is assigned to an interface in a namespace on the amphora. See my update to the answer for details.

            – larsks
            Nov 16 '18 at 17:50
















          1















          It is not a host.




          It is a host! An amphora is just a nova server -- the same thing you get when you run openstack server create. The difference is that the amphora is owned by the service project, so you'll only see it if you were to run (as admin) openstack server list --all-projects. For example:



          $ openstack --os-cloud as_me loadbalancer list
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | id | name | project_id | vip_address | provisioning_status | provider |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | 64a6a56d-beeb-4ee2-b495-1cdc26ffd399 | test_lb | 0ac1e30189da48b387cf3c2f5582b2a3 | 10.254.0.6 | ACTIVE | octavia |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+

          $ openstack --os-cloud as_admin server list --all-projects | grep amphora
          | f6cd75fe-8513-4aae-bee9-af9362525703 | amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af | ACTIVE | lb-mgmt-net=172.24.0.16; test_lb_net=10.254.0.11; test_net1=10.0.1.5; test_net0=10.0.0.4 | octavia-amphora-13.0-20181107.1.x86_64 | octavia_65 |


          If you look at that server, you'll see it has several ip addresses:




          • The one you assigned to it when created the loadbalancer, and

          • A management network address

          • Addresses on any subnets to which it is attached


          You can ssh into the amphora using the management network address. You should be able to reach it from your controllers. You'll need the appropriate ssh key; where to find that probably depends a lot on how you installed things. I'm using tripleo, and it looks as if the install uses ~/.ssh/id_rsa from the stack user for the amphora ssh key.



          [controller ~]$ ssh -i amphora_private_key cloud-user@172.24.0.7
          Last login: Thu Nov 15 22:01:16 2018 from 172.24.0.6
          [cloud-user@amphora-7d48e10b-5ba4-42c9-bcd5-941d224b2a46 ~]$


          Update



          The loadbalancer VIP is assigned to an interface inside a namespace on
          the amphora. Given the above configuration, I see:



          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns
          amphora-haproxy (id: 0)
          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns exec amphora-haproxy ip a
          1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
          link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
          3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:07:d2:26 brd ff:ff:ff:ff:ff:ff
          inet 10.254.0.11/24 brd 10.254.0.255 scope global eth1
          valid_lft forever preferred_lft forever
          inet 10.254.0.6/24 brd 10.254.0.255 scope global secondary eth1:0
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe07:d226/64 scope link
          valid_lft forever preferred_lft forever
          4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:21:9a:d1 brd ff:ff:ff:ff:ff:ff
          inet 10.0.0.4/24 brd 10.0.0.255 scope global eth2
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe21:9ad1/64 scope link
          valid_lft forever preferred_lft forever
          5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:2a:63:58 brd ff:ff:ff:ff:ff:ff
          inet 10.0.1.5/24 brd 10.0.1.255 scope global eth3
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe2a:6358/64 scope link
          valid_lft forever preferred_lft forever





          share|improve this answer


























          • I can ssh into the amphora. However, I have an address that is not assigned to any amphora. I see a VIP address in openstack loadbalancer list. What is this assigned to? I can log into the amphorae.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:22













          • I think I found my answer. It is assigned to an openstack port.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:36











          • Right. When you openstack loadbalancer show your load balancer, you can see the port id.

            – larsks
            Nov 16 '18 at 3:43











          • Still looking for what IP abstraction that the port maps to ( i.e. is it a namespace, veth pair in a namespace or virutal device .. what exactly?)

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:57











          • The vip is assigned to an interface in a namespace on the amphora. See my update to the answer for details.

            – larsks
            Nov 16 '18 at 17:50














          1












          1








          1








          It is not a host.




          It is a host! An amphora is just a nova server -- the same thing you get when you run openstack server create. The difference is that the amphora is owned by the service project, so you'll only see it if you were to run (as admin) openstack server list --all-projects. For example:



          $ openstack --os-cloud as_me loadbalancer list
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | id | name | project_id | vip_address | provisioning_status | provider |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | 64a6a56d-beeb-4ee2-b495-1cdc26ffd399 | test_lb | 0ac1e30189da48b387cf3c2f5582b2a3 | 10.254.0.6 | ACTIVE | octavia |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+

          $ openstack --os-cloud as_admin server list --all-projects | grep amphora
          | f6cd75fe-8513-4aae-bee9-af9362525703 | amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af | ACTIVE | lb-mgmt-net=172.24.0.16; test_lb_net=10.254.0.11; test_net1=10.0.1.5; test_net0=10.0.0.4 | octavia-amphora-13.0-20181107.1.x86_64 | octavia_65 |


          If you look at that server, you'll see it has several ip addresses:




          • The one you assigned to it when created the loadbalancer, and

          • A management network address

          • Addresses on any subnets to which it is attached


          You can ssh into the amphora using the management network address. You should be able to reach it from your controllers. You'll need the appropriate ssh key; where to find that probably depends a lot on how you installed things. I'm using tripleo, and it looks as if the install uses ~/.ssh/id_rsa from the stack user for the amphora ssh key.



          [controller ~]$ ssh -i amphora_private_key cloud-user@172.24.0.7
          Last login: Thu Nov 15 22:01:16 2018 from 172.24.0.6
          [cloud-user@amphora-7d48e10b-5ba4-42c9-bcd5-941d224b2a46 ~]$


          Update



          The loadbalancer VIP is assigned to an interface inside a namespace on
          the amphora. Given the above configuration, I see:



          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns
          amphora-haproxy (id: 0)
          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns exec amphora-haproxy ip a
          1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
          link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
          3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:07:d2:26 brd ff:ff:ff:ff:ff:ff
          inet 10.254.0.11/24 brd 10.254.0.255 scope global eth1
          valid_lft forever preferred_lft forever
          inet 10.254.0.6/24 brd 10.254.0.255 scope global secondary eth1:0
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe07:d226/64 scope link
          valid_lft forever preferred_lft forever
          4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:21:9a:d1 brd ff:ff:ff:ff:ff:ff
          inet 10.0.0.4/24 brd 10.0.0.255 scope global eth2
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe21:9ad1/64 scope link
          valid_lft forever preferred_lft forever
          5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:2a:63:58 brd ff:ff:ff:ff:ff:ff
          inet 10.0.1.5/24 brd 10.0.1.255 scope global eth3
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe2a:6358/64 scope link
          valid_lft forever preferred_lft forever





          share|improve this answer
















          It is not a host.




          It is a host! An amphora is just a nova server -- the same thing you get when you run openstack server create. The difference is that the amphora is owned by the service project, so you'll only see it if you were to run (as admin) openstack server list --all-projects. For example:



          $ openstack --os-cloud as_me loadbalancer list
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | id | name | project_id | vip_address | provisioning_status | provider |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+
          | 64a6a56d-beeb-4ee2-b495-1cdc26ffd399 | test_lb | 0ac1e30189da48b387cf3c2f5582b2a3 | 10.254.0.6 | ACTIVE | octavia |
          +--------------------------------------+---------+----------------------------------+-------------+---------------------+----------+

          $ openstack --os-cloud as_admin server list --all-projects | grep amphora
          | f6cd75fe-8513-4aae-bee9-af9362525703 | amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af | ACTIVE | lb-mgmt-net=172.24.0.16; test_lb_net=10.254.0.11; test_net1=10.0.1.5; test_net0=10.0.0.4 | octavia-amphora-13.0-20181107.1.x86_64 | octavia_65 |


          If you look at that server, you'll see it has several ip addresses:




          • The one you assigned to it when created the loadbalancer, and

          • A management network address

          • Addresses on any subnets to which it is attached


          You can ssh into the amphora using the management network address. You should be able to reach it from your controllers. You'll need the appropriate ssh key; where to find that probably depends a lot on how you installed things. I'm using tripleo, and it looks as if the install uses ~/.ssh/id_rsa from the stack user for the amphora ssh key.



          [controller ~]$ ssh -i amphora_private_key cloud-user@172.24.0.7
          Last login: Thu Nov 15 22:01:16 2018 from 172.24.0.6
          [cloud-user@amphora-7d48e10b-5ba4-42c9-bcd5-941d224b2a46 ~]$


          Update



          The loadbalancer VIP is assigned to an interface inside a namespace on
          the amphora. Given the above configuration, I see:



          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns
          amphora-haproxy (id: 0)
          [root@amphora-50dddb41-decf-4b3b-bb7a-f35a751d74af ~]# ip netns exec amphora-haproxy ip a
          1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
          link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
          3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:07:d2:26 brd ff:ff:ff:ff:ff:ff
          inet 10.254.0.11/24 brd 10.254.0.255 scope global eth1
          valid_lft forever preferred_lft forever
          inet 10.254.0.6/24 brd 10.254.0.255 scope global secondary eth1:0
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe07:d226/64 scope link
          valid_lft forever preferred_lft forever
          4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:21:9a:d1 brd ff:ff:ff:ff:ff:ff
          inet 10.0.0.4/24 brd 10.0.0.255 scope global eth2
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe21:9ad1/64 scope link
          valid_lft forever preferred_lft forever
          5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
          link/ether fa:16:3e:2a:63:58 brd ff:ff:ff:ff:ff:ff
          inet 10.0.1.5/24 brd 10.0.1.255 scope global eth3
          valid_lft forever preferred_lft forever
          inet6 fe80::f816:3eff:fe2a:6358/64 scope link
          valid_lft forever preferred_lft forever






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 16 '18 at 17:50

























          answered Nov 16 '18 at 3:07









          larskslarsks

          119k20199209




          119k20199209













          • I can ssh into the amphora. However, I have an address that is not assigned to any amphora. I see a VIP address in openstack loadbalancer list. What is this assigned to? I can log into the amphorae.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:22













          • I think I found my answer. It is assigned to an openstack port.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:36











          • Right. When you openstack loadbalancer show your load balancer, you can see the port id.

            – larsks
            Nov 16 '18 at 3:43











          • Still looking for what IP abstraction that the port maps to ( i.e. is it a namespace, veth pair in a namespace or virutal device .. what exactly?)

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:57











          • The vip is assigned to an interface in a namespace on the amphora. See my update to the answer for details.

            – larsks
            Nov 16 '18 at 17:50



















          • I can ssh into the amphora. However, I have an address that is not assigned to any amphora. I see a VIP address in openstack loadbalancer list. What is this assigned to? I can log into the amphorae.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:22













          • I think I found my answer. It is assigned to an openstack port.

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:36











          • Right. When you openstack loadbalancer show your load balancer, you can see the port id.

            – larsks
            Nov 16 '18 at 3:43











          • Still looking for what IP abstraction that the port maps to ( i.e. is it a namespace, veth pair in a namespace or virutal device .. what exactly?)

            – LostInTheFrequencyDomain
            Nov 16 '18 at 3:57











          • The vip is assigned to an interface in a namespace on the amphora. See my update to the answer for details.

            – larsks
            Nov 16 '18 at 17:50

















          I can ssh into the amphora. However, I have an address that is not assigned to any amphora. I see a VIP address in openstack loadbalancer list. What is this assigned to? I can log into the amphorae.

          – LostInTheFrequencyDomain
          Nov 16 '18 at 3:22







          I can ssh into the amphora. However, I have an address that is not assigned to any amphora. I see a VIP address in openstack loadbalancer list. What is this assigned to? I can log into the amphorae.

          – LostInTheFrequencyDomain
          Nov 16 '18 at 3:22















          I think I found my answer. It is assigned to an openstack port.

          – LostInTheFrequencyDomain
          Nov 16 '18 at 3:36





          I think I found my answer. It is assigned to an openstack port.

          – LostInTheFrequencyDomain
          Nov 16 '18 at 3:36













          Right. When you openstack loadbalancer show your load balancer, you can see the port id.

          – larsks
          Nov 16 '18 at 3:43





          Right. When you openstack loadbalancer show your load balancer, you can see the port id.

          – larsks
          Nov 16 '18 at 3:43













          Still looking for what IP abstraction that the port maps to ( i.e. is it a namespace, veth pair in a namespace or virutal device .. what exactly?)

          – LostInTheFrequencyDomain
          Nov 16 '18 at 3:57





          Still looking for what IP abstraction that the port maps to ( i.e. is it a namespace, veth pair in a namespace or virutal device .. what exactly?)

          – LostInTheFrequencyDomain
          Nov 16 '18 at 3:57













          The vip is assigned to an interface in a namespace on the amphora. See my update to the answer for details.

          – larsks
          Nov 16 '18 at 17:50





          The vip is assigned to an interface in a namespace on the amphora. See my update to the answer for details.

          – larsks
          Nov 16 '18 at 17:50




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53329843%2foctavia-what-is-the-loadbalancer-ip-assigned-to%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Bressuire

          Vorschmack

          Quarantine