Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
I can confirm that the 1.0.0 release of neutron-lbaas-dashboard is working on stable/newton. I included my installation steps in the below linked bug. As mentioned in the first e-mail. The instructions say to only install one of the two files in the enabled directory. I suspect that is the issue you are seeing. Michael -Original Message- From: Saverio Proto [mailto:saverio.pr...@switch.ch] Sent: Monday, March 13, 2017 5:47 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2 On 10/03/17 17:49, Michael Johnson wrote: > Yes, folks have recently deployed the dashboard with success. I think > you had that discussion on the IRC channel, so I won't repeat it here. > > Please note, the neutron-lbaas-dashboard does not support LBaaS v1, > you must have LBaaS v2 deployed for the neutron-lbaas-dashboard to > work. If you are trying to use LBaaS v1, you can use the legacy > panels included in the older versions of horizon. > [..CUT..] > If you think there is an open bug for the dashboard, please report it > in https://bugs.launchpad.net/neutron-lbaas-dashboard Hello, I updated the bug https://bugs.launchpad.net/neutron-lbaas-dashboard/+bug/1621403 Can anyone clarify the version matrix to use between the horizon version and the neutron-lbaas-dashboard panels versions ? can anyone confirm that both files _1481_project_ng_loadbalancersv2_panel.py and file _1480_project_loadbalancersv2_panel.py need to be installed ? Is it okay to use branch master of neutron-lbaas-dashboard with horizon stable/newton ? thank you Saverio __ 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
Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
Hi Saverio, I did a fresh install today with master versions of both OpenStack and the neutron-lbaas-dashboard just to make sure the panels are working as expected. It went fine. https://usercontent.irccloud-cdn.com/file/4Zgl9SB3/ To answer your version question: Stable/mitaka neutron-lbaas-dashboard should work with stable/mitaka and stable/newton OpenStack Stable/ocata neutron-lbaas-dashboard works with stable/ocata OpenStack Per the instructions in the README.rst and on PyPi, ONLY install the _1481_project_ng_loadbalancersv2_panel.py file. Do not install both, it will fail. I am not sure if you can use the master branch of neutron-lbaas-dashboard with a newton version of horizon. This is not a combination we test and/or support. It may work. Someone from the horizon team may have more insights on that, but I think the best answer is to get it going with the known good combinations and then to test mixed releases. I will now start over on stable/newton and test it out. I will let you know if I find a problem. Michael -Original Message- From: Saverio Proto [mailto:saverio.pr...@switch.ch] Sent: Monday, March 13, 2017 5:47 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2 On 10/03/17 17:49, Michael Johnson wrote: > Yes, folks have recently deployed the dashboard with success. I think > you had that discussion on the IRC channel, so I won't repeat it here. > > Please note, the neutron-lbaas-dashboard does not support LBaaS v1, > you must have LBaaS v2 deployed for the neutron-lbaas-dashboard to > work. If you are trying to use LBaaS v1, you can use the legacy > panels included in the older versions of horizon. > [..CUT..] > If you think there is an open bug for the dashboard, please report it > in https://bugs.launchpad.net/neutron-lbaas-dashboard Hello, I updated the bug https://bugs.launchpad.net/neutron-lbaas-dashboard/+bug/1621403 Can anyone clarify the version matrix to use between the horizon version and the neutron-lbaas-dashboard panels versions ? can anyone confirm that both files _1481_project_ng_loadbalancersv2_panel.py and file _1480_project_loadbalancersv2_panel.py need to be installed ? Is it okay to use branch master of neutron-lbaas-dashboard with horizon stable/newton ? thank you Saverio __ 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
Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
On 10/03/17 17:49, Michael Johnson wrote: > Yes, folks have recently deployed the dashboard with success. I think you > had that discussion on the IRC channel, so I won't repeat it here. > > Please note, the neutron-lbaas-dashboard does not support LBaaS v1, you must > have LBaaS v2 deployed for the neutron-lbaas-dashboard to work. If you are > trying to use LBaaS v1, you can use the legacy panels included in the older > versions of horizon. > [..CUT..] > If you think there is an open bug for the dashboard, please report it in > https://bugs.launchpad.net/neutron-lbaas-dashboard Hello, I updated the bug https://bugs.launchpad.net/neutron-lbaas-dashboard/+bug/1621403 Can anyone clarify the version matrix to use between the horizon version and the neutron-lbaas-dashboard panels versions ? can anyone confirm that both files _1481_project_ng_loadbalancersv2_panel.py and file _1480_project_loadbalancersv2_panel.py need to be installed ? Is it okay to use branch master of neutron-lbaas-dashboard with horizon stable/newton ? thank you Saverio __ 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
Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
Yes, folks have recently deployed the dashboard with success. I think you had that discussion on the IRC channel, so I won't repeat it here. Please note, the neutron-lbaas-dashboard does not support LBaaS v1, you must have LBaaS v2 deployed for the neutron-lbaas-dashboard to work. If you are trying to use LBaaS v1, you can use the legacy panels included in the older versions of horizon. The question asked is a very old question and unfortunately the "Ask" site doesn't do search or notifications very well. This question hasn't come up on our notification lists. Sigh. If you think there is an open bug for the dashboard, please report it in https://bugs.launchpad.net/neutron-lbaas-dashboard Michael -Original Message- From: Saverio Proto [mailto:saverio.pr...@switch.ch] Sent: Friday, March 10, 2017 8:04 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2 I spent the all day trying to deploy an Horizon instance with working panels for LBaaSv2. https://github.com/openstack/neutron-lbaas-dashboard I tried stable/ocata and I am never able to list existing load balancers or create a new loadbalancer. Looks like I am not the only one with this issue: https://ask.openstack.org/en/question/96790/lbaasv2-dashboard-issues/ Is there anyone that has a working setup ? Should I open a bug here? https://bugs.launchpad.net/octavia/+filebug Thanks Saverio On 09/03/17 16:19, Saverio Proto wrote: > Hello, > > I managed to do the database migration. > > I had to skip this logic: > https://github.com/openstack/neutron-lbaas/blob/master/tools/database- > migration-from-v1-to-v2.py#L342-L353 > > I had to force flag=True > > That code obviously breaks if you have LBaaS used by more than 1 tenant. > > What was the goal ? to make sure that a given healthmonitor is not > reused in multiple pools ? > > Should the right approach be to check if these two values are the same ?: > > select count(DISTINCT monitor_id) from poolmonitorassociations; select > count(monitor_id) from poolmonitorassociations; > > Second question: should the old tables from LBaaSV1 be dropped ? > > Please give me feedback so I can fix the code and submit a review. > > thank you > > Saverio > > > On 09/03/17 13:38, Saverio Proto wrote: >>> I would recommend experimenting with the >>> database-migration-from-v1-to-v2.py >>> script and working with your vendor (if you are using a vendor load >>> balancing engine) on a migration path. >> >> >> Hello, >> there is no vendor here to help us :) >> >> I made a backup of the current DB. >> >> I identified this folder on our Neutron server: >> >> /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration ; tree . >> |-- alembic_migrations >> | |-- env.py >> | |-- env.pyc >> | |-- __init__.py >> | |-- __init__.pyc >> | |-- README >> | |-- script.py.mako >> | `-- versions >> | |-- 364f9b6064f0_agentv2.py >> | |-- 364f9b6064f0_agentv2.pyc >> | |-- 4b6d8d5310b8_add_index_tenant_id.py >> | |-- 4b6d8d5310b8_add_index_tenant_id.pyc >> | |-- 4ba00375f715_edge_driver.py >> | |-- 4ba00375f715_edge_driver.pyc >> | |-- 4deef6d81931_add_provisioning_and_operating_statuses.py >> | |-- 4deef6d81931_add_provisioning_and_operating_statuses.pyc >> | |-- CONTRACT_HEAD >> | |-- EXPAND_HEAD >> | |-- kilo_release.py >> | |-- kilo_release.pyc >> | |-- lbaasv2.py >> | |-- lbaasv2.pyc >> | |-- lbaasv2_tls.py >> | |-- lbaasv2_tls.pyc >> | |-- liberty >> | | |-- contract >> | | | |-- 130ebfdef43_initial.py >> | | | `-- 130ebfdef43_initial.pyc >> | | `-- expand >> | | |-- 3345facd0452_initial.py >> | | `-- 3345facd0452_initial.pyc >> | |-- mitaka >> | | `-- expand >> | | |-- 3426acbc12de_add_flavor_id.py >> | | |-- 3426acbc12de_add_flavor_id.pyc >> | | |-- 3543deab1547_add_l7_tables.py >> | | |-- 3543deab1547_add_l7_tables.pyc >> | | |-- 4a408dd491c2_UpdateName.py >> | | |-- 4a408dd491c2_UpdateName.pyc >> | | |-- 62deca5010cd_add_tenant_id_index_for_l7_tables.py >> | | |-- 62deca5010cd_add_tenant_id_index_for_l7_tables.pyc >> | | |-- 6aee0434f911_independent_pools.py >> | | `-- 6aee0434f911_independent_pools.pyc >> | |-- start_neutron_lbaas.py >> | `-- s
Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
I spent the all day trying to deploy an Horizon instance with working panels for LBaaSv2. https://github.com/openstack/neutron-lbaas-dashboard I tried stable/ocata and I am never able to list existing load balancers or create a new loadbalancer. Looks like I am not the only one with this issue: https://ask.openstack.org/en/question/96790/lbaasv2-dashboard-issues/ Is there anyone that has a working setup ? Should I open a bug here? https://bugs.launchpad.net/octavia/+filebug Thanks Saverio On 09/03/17 16:19, Saverio Proto wrote: > Hello, > > I managed to do the database migration. > > I had to skip this logic: > https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migration-from-v1-to-v2.py#L342-L353 > > I had to force flag=True > > That code obviously breaks if you have LBaaS used by more than 1 tenant. > > What was the goal ? to make sure that a given healthmonitor is not > reused in multiple pools ? > > Should the right approach be to check if these two values are the same ?: > > select count(DISTINCT monitor_id) from poolmonitorassociations; > select count(monitor_id) from poolmonitorassociations; > > Second question: should the old tables from LBaaSV1 be dropped ? > > Please give me feedback so I can fix the code and submit a review. > > thank you > > Saverio > > > On 09/03/17 13:38, Saverio Proto wrote: >>> I would recommend experimenting with the database-migration-from-v1-to-v2.py >>> script and working with your vendor (if you are using a vendor load >>> balancing engine) on a migration path. >> >> >> Hello, >> there is no vendor here to help us :) >> >> I made a backup of the current DB. >> >> I identified this folder on our Neutron server: >> >> /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration ; tree >> . >> |-- alembic_migrations >> | |-- env.py >> | |-- env.pyc >> | |-- __init__.py >> | |-- __init__.pyc >> | |-- README >> | |-- script.py.mako >> | `-- versions >> | |-- 364f9b6064f0_agentv2.py >> | |-- 364f9b6064f0_agentv2.pyc >> | |-- 4b6d8d5310b8_add_index_tenant_id.py >> | |-- 4b6d8d5310b8_add_index_tenant_id.pyc >> | |-- 4ba00375f715_edge_driver.py >> | |-- 4ba00375f715_edge_driver.pyc >> | |-- 4deef6d81931_add_provisioning_and_operating_statuses.py >> | |-- 4deef6d81931_add_provisioning_and_operating_statuses.pyc >> | |-- CONTRACT_HEAD >> | |-- EXPAND_HEAD >> | |-- kilo_release.py >> | |-- kilo_release.pyc >> | |-- lbaasv2.py >> | |-- lbaasv2.pyc >> | |-- lbaasv2_tls.py >> | |-- lbaasv2_tls.pyc >> | |-- liberty >> | | |-- contract >> | | | |-- 130ebfdef43_initial.py >> | | | `-- 130ebfdef43_initial.pyc >> | | `-- expand >> | | |-- 3345facd0452_initial.py >> | | `-- 3345facd0452_initial.pyc >> | |-- mitaka >> | | `-- expand >> | | |-- 3426acbc12de_add_flavor_id.py >> | | |-- 3426acbc12de_add_flavor_id.pyc >> | | |-- 3543deab1547_add_l7_tables.py >> | | |-- 3543deab1547_add_l7_tables.pyc >> | | |-- 4a408dd491c2_UpdateName.py >> | | |-- 4a408dd491c2_UpdateName.pyc >> | | |-- 62deca5010cd_add_tenant_id_index_for_l7_tables.py >> | | |-- 62deca5010cd_add_tenant_id_index_for_l7_tables.pyc >> | | |-- 6aee0434f911_independent_pools.py >> | | `-- 6aee0434f911_independent_pools.pyc >> | |-- start_neutron_lbaas.py >> | `-- start_neutron_lbaas.pyc >> |-- __init__.py >> `-- __init__.pyc >> >> 7 directories, 40 files >> >> Now here it says: "Create a revision file" >> >> https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migration-from-v1-to-v2.py#L30 >> >> There is some specific openstack-dev documentation to "Create a revision >> file" or I should just learn the Alembic tool ? I never used it before. >> >> So far I did copy the alembic.ini from here: >> https://github.com/openstack/neutron/blob/master/neutron/db/migration/alembic.ini >> >> into /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration >> >> then I did run the command: >> >> alembic revision -m "migrate to LBaaSv2" >> >> as a result it created the file: >> /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration/alembic_migrations/versions/24274573545b_migrate_to_lbaasv2.py >> >> Then I added the script to that file: >> wget -O - >> https://raw.githubusercontent.com/openstack/neutron-lbaas/master/tools/database-migration-from-v1-to-v2.py alembic_migrations/versions/24274573545b_migrate_to_lbaasv2.py >> >> I tried now: >> neutron-db-manage upgrade heads >> >> but it fails with a easy stacktrace. I get stuck here: >> https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migration-from-v1-to-v2.py#L346 >> >> of course the query: >> select tenant_id from pools; >> >> returns more than 1 tenant_id >> >> it means I cannot migrate if I
Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
Hello, I managed to do the database migration. I had to skip this logic: https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migration-from-v1-to-v2.py#L342-L353 I had to force flag=True That code obviously breaks if you have LBaaS used by more than 1 tenant. What was the goal ? to make sure that a given healthmonitor is not reused in multiple pools ? Should the right approach be to check if these two values are the same ?: select count(DISTINCT monitor_id) from poolmonitorassociations; select count(monitor_id) from poolmonitorassociations; Second question: should the old tables from LBaaSV1 be dropped ? Please give me feedback so I can fix the code and submit a review. thank you Saverio On 09/03/17 13:38, Saverio Proto wrote: >> I would recommend experimenting with the database-migration-from-v1-to-v2.py >> script and working with your vendor (if you are using a vendor load >> balancing engine) on a migration path. > > > Hello, > there is no vendor here to help us :) > > I made a backup of the current DB. > > I identified this folder on our Neutron server: > > /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration ; tree > . > |-- alembic_migrations > | |-- env.py > | |-- env.pyc > | |-- __init__.py > | |-- __init__.pyc > | |-- README > | |-- script.py.mako > | `-- versions > | |-- 364f9b6064f0_agentv2.py > | |-- 364f9b6064f0_agentv2.pyc > | |-- 4b6d8d5310b8_add_index_tenant_id.py > | |-- 4b6d8d5310b8_add_index_tenant_id.pyc > | |-- 4ba00375f715_edge_driver.py > | |-- 4ba00375f715_edge_driver.pyc > | |-- 4deef6d81931_add_provisioning_and_operating_statuses.py > | |-- 4deef6d81931_add_provisioning_and_operating_statuses.pyc > | |-- CONTRACT_HEAD > | |-- EXPAND_HEAD > | |-- kilo_release.py > | |-- kilo_release.pyc > | |-- lbaasv2.py > | |-- lbaasv2.pyc > | |-- lbaasv2_tls.py > | |-- lbaasv2_tls.pyc > | |-- liberty > | | |-- contract > | | | |-- 130ebfdef43_initial.py > | | | `-- 130ebfdef43_initial.pyc > | | `-- expand > | | |-- 3345facd0452_initial.py > | | `-- 3345facd0452_initial.pyc > | |-- mitaka > | | `-- expand > | | |-- 3426acbc12de_add_flavor_id.py > | | |-- 3426acbc12de_add_flavor_id.pyc > | | |-- 3543deab1547_add_l7_tables.py > | | |-- 3543deab1547_add_l7_tables.pyc > | | |-- 4a408dd491c2_UpdateName.py > | | |-- 4a408dd491c2_UpdateName.pyc > | | |-- 62deca5010cd_add_tenant_id_index_for_l7_tables.py > | | |-- 62deca5010cd_add_tenant_id_index_for_l7_tables.pyc > | | |-- 6aee0434f911_independent_pools.py > | | `-- 6aee0434f911_independent_pools.pyc > | |-- start_neutron_lbaas.py > | `-- start_neutron_lbaas.pyc > |-- __init__.py > `-- __init__.pyc > > 7 directories, 40 files > > Now here it says: "Create a revision file" > > https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migration-from-v1-to-v2.py#L30 > > There is some specific openstack-dev documentation to "Create a revision > file" or I should just learn the Alembic tool ? I never used it before. > > So far I did copy the alembic.ini from here: > https://github.com/openstack/neutron/blob/master/neutron/db/migration/alembic.ini > > into /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration > > then I did run the command: > > alembic revision -m "migrate to LBaaSv2" > > as a result it created the file: > /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration/alembic_migrations/versions/24274573545b_migrate_to_lbaasv2.py > > Then I added the script to that file: > wget -O - > https://raw.githubusercontent.com/openstack/neutron-lbaas/master/tools/database-migration-from-v1-to-v2.py >>> alembic_migrations/versions/24274573545b_migrate_to_lbaasv2.py > > I tried now: > neutron-db-manage upgrade heads > > but it fails with a easy stacktrace. I get stuck here: > https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migration-from-v1-to-v2.py#L346 > > of course the query: > select tenant_id from pools; > > returns more than 1 tenant_id > > it means I cannot migrate if I have more than 1 tenant using LBaaS v1 ? > > am I doing something completely wrong here ? am I on the right direction ? > > thank you > > Saverio > > > > > > > > > > > > > > > __ > 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 > -- SWITCH Saverio Proto, Peta Solutions Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 15, direct +41 44 268 1573 saverio.pr...@switch.ch, http://www.switch.ch
Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
> I would recommend experimenting with the database-migration-from-v1-to-v2.py > script and working with your vendor (if you are using a vendor load > balancing engine) on a migration path. Hello, there is no vendor here to help us :) I made a backup of the current DB. I identified this folder on our Neutron server: /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration ; tree . |-- alembic_migrations | |-- env.py | |-- env.pyc | |-- __init__.py | |-- __init__.pyc | |-- README | |-- script.py.mako | `-- versions | |-- 364f9b6064f0_agentv2.py | |-- 364f9b6064f0_agentv2.pyc | |-- 4b6d8d5310b8_add_index_tenant_id.py | |-- 4b6d8d5310b8_add_index_tenant_id.pyc | |-- 4ba00375f715_edge_driver.py | |-- 4ba00375f715_edge_driver.pyc | |-- 4deef6d81931_add_provisioning_and_operating_statuses.py | |-- 4deef6d81931_add_provisioning_and_operating_statuses.pyc | |-- CONTRACT_HEAD | |-- EXPAND_HEAD | |-- kilo_release.py | |-- kilo_release.pyc | |-- lbaasv2.py | |-- lbaasv2.pyc | |-- lbaasv2_tls.py | |-- lbaasv2_tls.pyc | |-- liberty | | |-- contract | | | |-- 130ebfdef43_initial.py | | | `-- 130ebfdef43_initial.pyc | | `-- expand | | |-- 3345facd0452_initial.py | | `-- 3345facd0452_initial.pyc | |-- mitaka | | `-- expand | | |-- 3426acbc12de_add_flavor_id.py | | |-- 3426acbc12de_add_flavor_id.pyc | | |-- 3543deab1547_add_l7_tables.py | | |-- 3543deab1547_add_l7_tables.pyc | | |-- 4a408dd491c2_UpdateName.py | | |-- 4a408dd491c2_UpdateName.pyc | | |-- 62deca5010cd_add_tenant_id_index_for_l7_tables.py | | |-- 62deca5010cd_add_tenant_id_index_for_l7_tables.pyc | | |-- 6aee0434f911_independent_pools.py | | `-- 6aee0434f911_independent_pools.pyc | |-- start_neutron_lbaas.py | `-- start_neutron_lbaas.pyc |-- __init__.py `-- __init__.pyc 7 directories, 40 files Now here it says: "Create a revision file" https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migration-from-v1-to-v2.py#L30 There is some specific openstack-dev documentation to "Create a revision file" or I should just learn the Alembic tool ? I never used it before. So far I did copy the alembic.ini from here: https://github.com/openstack/neutron/blob/master/neutron/db/migration/alembic.ini into /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration then I did run the command: alembic revision -m "migrate to LBaaSv2" as a result it created the file: /usr/lib/python2.7/dist-packages/neutron_lbaas/db/migration/alembic_migrations/versions/24274573545b_migrate_to_lbaasv2.py Then I added the script to that file: wget -O - https://raw.githubusercontent.com/openstack/neutron-lbaas/master/tools/database-migration-from-v1-to-v2.py >> alembic_migrations/versions/24274573545b_migrate_to_lbaasv2.py I tried now: neutron-db-manage upgrade heads but it fails with a easy stacktrace. I get stuck here: https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migration-from-v1-to-v2.py#L346 of course the query: select tenant_id from pools; returns more than 1 tenant_id it means I cannot migrate if I have more than 1 tenant using LBaaS v1 ? am I doing something completely wrong here ? am I on the right direction ? thank you Saverio __ 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
Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
Saverio, Unfortunately back when LBaaS v1 was deprecated (liberty) no automated migration path was developed to move from LBaaS v1 to v2. Some manual database migration scripts were contributed, but you may still have incompatible v1 load balancers that require manual intervention. There is a note about this in the networking guide: https://docs.openstack.org/ocata/networking-guide/config-lbaas.html I would recommend experimenting with the database-migration-from-v1-to-v2.py script and working with your vendor (if you are using a vendor load balancing engine) on a migration path. Michael -Original Message- From: Saverio Proto [mailto:saverio.pr...@switch.ch] Sent: Tuesday, March 7, 2017 9:35 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2 Hello Michael, thanks. Using your email I read this page: https://docs.openstack.org/ocata/networking-guide/config-lbaas.html It is still not clear to me if the command: neutron-db-manage --subproject neutron-lbaas upgrade head Will make the necessary database migrations from LBaaS v1 to v2 ? Does this command triggers the execution of this code ? https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migrat ion-from-v1-to-v2.py On what openstack version should I run that neutron-db-manage command ? I am currently in Mitaka. Here I read: https://docs.openstack.org/releasenotes/neutron-lbaas/newton.html LBaaS API v1 has been removed. Do not upgrade before migrating to LBaaS API v2. This means I have to run 'neutron-db-manage --subproject neutron-lbaas upgrade head' before upgrading ? am I missing the page where the migration from V1 to V2 is explained ? thank you Saverio On 07/03/17 17:33, Michael Johnson wrote: > Hi Saverio, > > I think the confusion is coming from neutron/neutron-lbaas/octavia. > > Neutron-lbaas, prior to the Ocata series was a sub-project of neutron > and as such has it's own release notes: > https://docs.openstack.org/releasenotes/neutron-lbaas/ > > As of Ocata, neutron-lbaas is part of the Octavia project > (https://governance.openstack.org/tc/reference/projects/octavia.html) > and is no longer a sub-project of neutron. In fact, we are actively > working to merge the neutron-lbaas v2 API into the Octavia API to > create a combined project. > > Going forward you will probably want to monitor both neutron-lbaas and > the octavia release notes: > https://docs.openstack.org/releasenotes/neutron-lbaas/ > https://docs.openstack.org/releasenotes/octavia/ > > To answer your original question, the LBaaS v1 API as removed in the > newton release of neutron-lbaas > (https://docs.openstack.org/releasenotes/neutron-lbaas/newton.html). > > Michael > > > -Original Message- > From: Saverio Proto [mailto:saverio.pr...@switch.ch] > Sent: Tuesday, March 7, 2017 1:09 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade > from LBaaS v1 to v2 > > Hello, > > I am upgrading from Mitaka to Newton. > > our Openstack cloud has in production LBaaSv1. > > I read all the following release notes: > > https://docs.openstack.org/releasenotes/neutron/liberty.html > https://docs.openstack.org/releasenotes/neutron/mitaka.html > https://docs.openstack.org/releasenotes/neutron/newton.html > > In the liberty release notes I read: > "The LBaaS V1 API is marked as deprecated and is planned to be removed > in a future release. Going forward, the LBaaS V2 API should be used." > > But which one is the release that drops LBaaS V1 ? > > I see this script is merged in stable/newton: > > https://review.openstack.org/#/c/289595/ > > Can I still use LBaaS V1 in newton and do the migration before > upgrading to Ocata ? > > The cherry-pick to Mitaka was abandoned: > https://review.openstack.org/#/c/370103/ > > The Ocata release notes again dont say anything about LBaaS: > https://docs.openstack.org/releasenotes/neutron/ocata.html > > thank you > > Saverio > > > > -- > SWITCH > Saverio Proto, Peta Solutions > Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 > 15, direct +41 44 268 1573 saverio.pr...@switch.ch, > http://www.switch.ch > > http://www.switch.ch/stories > > __ > 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/openstac
Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
Hello Michael, thanks. Using your email I read this page: https://docs.openstack.org/ocata/networking-guide/config-lbaas.html It is still not clear to me if the command: neutron-db-manage --subproject neutron-lbaas upgrade head Will make the necessary database migrations from LBaaS v1 to v2 ? Does this command triggers the execution of this code ? https://github.com/openstack/neutron-lbaas/blob/master/tools/database-migration-from-v1-to-v2.py On what openstack version should I run that neutron-db-manage command ? I am currently in Mitaka. Here I read: https://docs.openstack.org/releasenotes/neutron-lbaas/newton.html LBaaS API v1 has been removed. Do not upgrade before migrating to LBaaS API v2. This means I have to run 'neutron-db-manage --subproject neutron-lbaas upgrade head' before upgrading ? am I missing the page where the migration from V1 to V2 is explained ? thank you Saverio On 07/03/17 17:33, Michael Johnson wrote: > Hi Saverio, > > I think the confusion is coming from neutron/neutron-lbaas/octavia. > > Neutron-lbaas, prior to the Ocata series was a sub-project of neutron and as > such has it's own release notes: > https://docs.openstack.org/releasenotes/neutron-lbaas/ > > As of Ocata, neutron-lbaas is part of the Octavia project > (https://governance.openstack.org/tc/reference/projects/octavia.html) and is > no longer a sub-project of neutron. In fact, we are actively working to > merge the neutron-lbaas v2 API into the Octavia API to create a combined > project. > > Going forward you will probably want to monitor both neutron-lbaas and the > octavia release notes: > https://docs.openstack.org/releasenotes/neutron-lbaas/ > https://docs.openstack.org/releasenotes/octavia/ > > To answer your original question, the LBaaS v1 API as removed in the newton > release of neutron-lbaas > (https://docs.openstack.org/releasenotes/neutron-lbaas/newton.html). > > Michael > > > -Original Message- > From: Saverio Proto [mailto:saverio.pr...@switch.ch] > Sent: Tuesday, March 7, 2017 1:09 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from > LBaaS v1 to v2 > > Hello, > > I am upgrading from Mitaka to Newton. > > our Openstack cloud has in production LBaaSv1. > > I read all the following release notes: > > https://docs.openstack.org/releasenotes/neutron/liberty.html > https://docs.openstack.org/releasenotes/neutron/mitaka.html > https://docs.openstack.org/releasenotes/neutron/newton.html > > In the liberty release notes I read: > "The LBaaS V1 API is marked as deprecated and is planned to be removed in a > future release. Going forward, the LBaaS V2 API should be used." > > But which one is the release that drops LBaaS V1 ? > > I see this script is merged in stable/newton: > > https://review.openstack.org/#/c/289595/ > > Can I still use LBaaS V1 in newton and do the migration before upgrading to > Ocata ? > > The cherry-pick to Mitaka was abandoned: > https://review.openstack.org/#/c/370103/ > > The Ocata release notes again dont say anything about LBaaS: > https://docs.openstack.org/releasenotes/neutron/ocata.html > > thank you > > Saverio > > > > -- > SWITCH > Saverio Proto, Peta Solutions > Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 15, > direct +41 44 268 1573 saverio.pr...@switch.ch, http://www.switch.ch > > http://www.switch.ch/stories > > __ > 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 > -- SWITCH Saverio Proto, Peta Solutions Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 15, direct +41 44 268 1573 saverio.pr...@switch.ch, http://www.switch.ch http://www.switch.ch/stories __ 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
Re: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
Hi Saverio, I think the confusion is coming from neutron/neutron-lbaas/octavia. Neutron-lbaas, prior to the Ocata series was a sub-project of neutron and as such has it's own release notes: https://docs.openstack.org/releasenotes/neutron-lbaas/ As of Ocata, neutron-lbaas is part of the Octavia project (https://governance.openstack.org/tc/reference/projects/octavia.html) and is no longer a sub-project of neutron. In fact, we are actively working to merge the neutron-lbaas v2 API into the Octavia API to create a combined project. Going forward you will probably want to monitor both neutron-lbaas and the octavia release notes: https://docs.openstack.org/releasenotes/neutron-lbaas/ https://docs.openstack.org/releasenotes/octavia/ To answer your original question, the LBaaS v1 API as removed in the newton release of neutron-lbaas (https://docs.openstack.org/releasenotes/neutron-lbaas/newton.html). Michael -Original Message- From: Saverio Proto [mailto:saverio.pr...@switch.ch] Sent: Tuesday, March 7, 2017 1:09 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2 Hello, I am upgrading from Mitaka to Newton. our Openstack cloud has in production LBaaSv1. I read all the following release notes: https://docs.openstack.org/releasenotes/neutron/liberty.html https://docs.openstack.org/releasenotes/neutron/mitaka.html https://docs.openstack.org/releasenotes/neutron/newton.html In the liberty release notes I read: "The LBaaS V1 API is marked as deprecated and is planned to be removed in a future release. Going forward, the LBaaS V2 API should be used." But which one is the release that drops LBaaS V1 ? I see this script is merged in stable/newton: https://review.openstack.org/#/c/289595/ Can I still use LBaaS V1 in newton and do the migration before upgrading to Ocata ? The cherry-pick to Mitaka was abandoned: https://review.openstack.org/#/c/370103/ The Ocata release notes again dont say anything about LBaaS: https://docs.openstack.org/releasenotes/neutron/ocata.html thank you Saverio -- SWITCH Saverio Proto, Peta Solutions Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 15, direct +41 44 268 1573 saverio.pr...@switch.ch, http://www.switch.ch http://www.switch.ch/stories __ 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
[openstack-dev] [Neutron][LBaaS] - Best release to upgrade from LBaaS v1 to v2
Hello, I am upgrading from Mitaka to Newton. our Openstack cloud has in production LBaaSv1. I read all the following release notes: https://docs.openstack.org/releasenotes/neutron/liberty.html https://docs.openstack.org/releasenotes/neutron/mitaka.html https://docs.openstack.org/releasenotes/neutron/newton.html In the liberty release notes I read: "The LBaaS V1 API is marked as deprecated and is planned to be removed in a future release. Going forward, the LBaaS V2 API should be used." But which one is the release that drops LBaaS V1 ? I see this script is merged in stable/newton: https://review.openstack.org/#/c/289595/ Can I still use LBaaS V1 in newton and do the migration before upgrading to Ocata ? The cherry-pick to Mitaka was abandoned: https://review.openstack.org/#/c/370103/ The Ocata release notes again dont say anything about LBaaS: https://docs.openstack.org/releasenotes/neutron/ocata.html thank you Saverio -- SWITCH Saverio Proto, Peta Solutions Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 15, direct +41 44 268 1573 saverio.pr...@switch.ch, http://www.switch.ch http://www.switch.ch/stories __ 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
