Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=zed-eol 2020-09-30T16:45:03+00:00 2020-09-30T16:45:03+00:00 Radosław Piliszek radoslaw.piliszek@gmail.com 2020-09-30T16:45:03+00:00 urn:sha1:faaa38f9c4320e90a8ecd199f7610ed343e25f74 It seems I mixed up the order when commenting/uncommenting. Neutron base has to go first. Change-Id: Ib2bf51d4c6e2a574b98671a699777cd8a9a22768 2020-09-23T08:24:29+00:00 Radosław Piliszek radoslaw.piliszek@gmail.com 2020-09-23T08:24:29+00:00 urn:sha1:7261c3b1704590f492206096df4625f9abb871c6 For details see [1]. Note this will also be amended on the Kolla-Ansible side to squash [2] as well. [1] https://review.opendev.org/750075 [2] https://bugs.launchpad.net/kolla-ansible/+bug/1894380 Change-Id: Id47ea8a5ea5318a69cf6814162db2115b40c7e6f 2020-09-05T17:42:22+00:00 Radosław Piliszek radoslaw.piliszek@gmail.com 2020-09-05T15:49:35+00:00 urn:sha1:2725ed9d842622078e31165d91718e58d07620e0 1) makes bifrost unbuildable as it evolves rapidly at the moment 2) makes neutron bootstrap/upgrade only the core service [1] 1) will be reverted 2) will be made more flexible [1] https://bugs.launchpad.net/bgpvpn/+bug/1894056 Change-Id: I1eefcfceded985b5f61ee8d796f9d8994c9ee97c 2020-06-18T22:12:05+00:00 Alfredo Moralejo amoralej@redhat.com 2020-06-18T14:03:55+00:00 urn:sha1:d3742fb9d819b6be3818842ba990bf4739d59051 FWaaS is being retired upstream [1][2] in V cycle. [1] https://review.opendev.org/#/c/735838/ Change-Id: I45679c8596844780565644e52034bd3de0915ff4 2020-03-18T08:31:31+00:00 Michal Nasiadka mnasiadka@gmail.com 2020-03-17T12:15:40+00:00 urn:sha1:aec0b95fa72689404cc15bd7a3e890d42b394dcd A followup to change [1]. Remove networking-ovn sources from kolla/common/config.py and neutron-db-manage call in neutron-server/extend_start.sh [1]: https://review.opendev.org/712762/ Change-Id: I976d60e5f2bf3e8a55b90485a77584d9e7579d62 2020-01-08T08:37:35+00:00 Michal Nasiadka mnasiadka@gmail.com 2020-01-04T07:18:13+00:00 urn:sha1:17982e5817ccb9e8b20d3c073805c6b9d63b90ec Currently neutron-server-ovn container does not run db setup for networking-ovn subproject when bootstrapping - since it uses extend_start from neutron-server (where networking-ovn is not installed). Since OVN is being added as in-tree driver to Neutron and there is no rationale behind supporting separate container images for neutron-server-ovn and neutron-metadata-agent-ovn, hile networking-ovn driver uses around 1-2MB of space - this change adds networking-ovn installation to neutron-base image and deprecates neutron-server-ovn and neutron-metadata-agent-ovn images. Change-Id: Ib2dbdd7e7d34f56985b7a5b2494c3b89034688cb 2019-11-19T21:51:42+00:00 Viktor Michalek viktor.michalek@ultimum.io 2019-10-17T13:18:14+00:00 urn:sha1:89372f0c5f312c222fe769a2aab8d1fce445dd84 Change-Id: Id84d5a1b3c70c0260b85ed7c24aa7f1e007c12d6 Closes-Bug: 1848572 2019-06-15T21:11:57+00:00 Zuul zuul@review.opendev.org 2019-06-15T21:11:57+00:00 urn:sha1:45ef7176aead8d8b59135f8c168094600ea05f31 2019-06-05T21:25:05+00:00 Jason jasonanderson@uchicago.edu 2019-04-30T16:44:53+00:00 urn:sha1:f36d7aacf28bc75a4b0ece73b45aa09591cd262c Instead of migrating all Neutron subprojects at bootstrap time, target specifically the neutron, neutron-fwaas, and neutron-vpnaas subprojects speficially. If a subproject is not specified, all subprojects are migrated, which is not the intended behavior. Change-Id: Icb8d572b7f084804e0423a8a3171dd66646b3885 2018-06-21T09:34:37+00:00 Duong Ha-Quang duonghq@vn.fujitsu.com 2018-05-17T09:26:41+00:00 urn:sha1:4f4de70594d3d9060c262438ddd87f768b4dda00 Due to only neutron, vpnass and fwaas have supported for rolling upgrade database migration, this patch set add --subproject argument to limited the upgrade to these. Co-Authored-By: Ha Manh Dong <donghm@vn.fujitsu.com> Change-Id: I007e0068622fd630eb9f2f29b604015376ae7cd3 Implements: blueprint apply-service-upgrade-procedure