Search results for "canceled meeting" - openstack-discuss

RE: [tacker] Recent FT errors

by ueha.ayumu＠fujitsu.com

There seems to be no objection, so I will update the patch. Thanks! Best Regards, Ueha -----Original Message----- On 2022/09/15 17:29, ueha.ayumu(a)fujitsu.com wrote: > Hi Yasufumi, > > I think waiting patches don't depend on these tests because these > tests are for legacy implementation of Tacker. Thanks for the reply quickly. I've realized that. So, could you update your patch for canceling these tests if no other one opposite to the temporary fix? Yasufumi > > -----Original Message----- > > Ayumu, > > On 2022/09/15 17:15, ueha.ayumu(a)fujitsu.com wrote: >> Hi Yasufumi, >> >> Thanks for your suggestion! I agree with you. >> >>> we can make the new tests non-voting >> I think it is better to make the old tests (legacy and lib-master) >> non-voting too, because the old tests has also failed recently. >> What do you think? > I'd agree if waiting patches don't depend on these tests. > >> >> Best regards, >> Ueha >> >> -----Original Message----- >> From: Yasufumi Ogawa <yasufum.o(a)gmail.com> >> Sent: Thursday, September 15, 2022 5:00 PM >> To: openstack-discuss <openstack-discuss(a)lists.openstack.org> >> Subject: [tacker] Recent FT errors >> >> Hi tacker team, >> >> We've several unexpected failures on functional tests since last week or so. It might be because of new tests introduced in the recent some updates, and some lackness of resources on zuul tests we usually meet the same situation at the end of release possibly. >> >> Thanks to ueha to propose a patch [1] as a remedy for the issue, but it doesn't work for now unfortunately. For plan B, we can make the new tests non-voting for a while because it's not related to all reamined patches being reviewed now actually. We can revert it and focus on to fix the problem after RC1 is released. What do you think? >> >> [1] https://review.opendev.org/c/openstack/tacker/+/857551 >> >> Yasufumi >>

2 years, 6 months

Re: [nova][ptg][ops] Nova at the vPTG (+ skipping next weekly meeting)

by Sylvain Bauza

Le jeu. 23 mars 2023 à 15:32, Sylvain Bauza <sbauza(a)redhat.com> a écrit : > > > Le jeu. 23 mars 2023 à 14:51, Sofia Enriquez <senrique(a)redhat.com> a > écrit : > >> >> Hi Sylvain, >> >> I hope you're doing well. Apologies for the delay in responding to your >> previous message. I wanted to suggest a cross-project topic with Cinder >> that involves adding support for NFS encryption. >> >> To complement the work on Cinder[3], I've proposed two patches [1][2] and >> would appreciate any feedback you may have. I believe it would be >> beneficial to discuss my approach during the PTG, but I'm open to >> discussing it during a weekly meeting as well. >> >> > Hey Sofia, I'm indeed well, thank you. I was actually considering to ping > Rajat over IRC since we weren't having any cinder-related topics yet in the > etherpad but I was almost sure that we would have some last-minute thoughts > during the week. > I'm quite OK with discussing your item into some cross-project session. > > I've looked at the etherpad and am considering the first slot on Wednesday >> or the last slot on Thursday or Friday. >> > > Cool, I'll arrange some common timeslot between teams with Rajat once he's > done with the OpenInfra Live presentation, like me :-) > -Sylvain > > Just a quick wrap-up : Rajat and I agreed on a cross-project session between Cinder and Nova on Thursday Mar30 1600UTC in the nova (diablo) room. -Sylvain >> Please let me know your thoughts. >> >> Thank you, >> Sofia >> >> [1] https://review.opendev.org/c/openstack/nova/+/854030 >> [2] https://review.opendev.org/c/openstack/nova/+/870012 >> [3] https://review.opendev.org/q/topic:bp%252Fnfs-volume-encryption >> >> On Wed, Mar 22, 2023 at 9:46 AM Sylvain Bauza <sbauza(a)redhat.com> wrote: >> >>> Hey folks, >>> >>> As a reminder, the Nova community will discuss at the vPTG. You can see >>> the topics we'll talk in https://etherpad.opendev.org/p/nova-bobcat-ptg >>> >>> Our agenda will be from Tuesday to Friday, everyday between 1300UTC and >>> 1700UTC. Connection details are in the etherpad above, but you can also use >>> PTGbot website : https://ptg.opendev.org/ptg.html (we'll use the diablo >>> room for all the discussions) >>> >>> You can't stick around for 4 hours x 4 days ? Heh, no worries ! >>> If you (as an operator or a developer) want to engage with us (and we'd >>> love this honestly), you have two possibilities : >>> - either you prefer to listen (and talk) to some topics you've seen in >>> the agenda, and then add your IRC nick (details how to use IRC are >>> explained by [1]) on the topics you want. Once we start to discuss about >>> those topics, I'll ping the courtesy ping list of each topic on >>> #openstack-nova. Just make sure you're around in the IRC channel. >>> - or you prefer to engage with us about some pain points or some >>> feature requests, and then the right time is the Nova Operator Hour that >>> will be on *Tuesday 1500UTC*. We have a specific etherpad for this session >>> : https://etherpad.opendev.org/p/march2023-ptg-operator-hour-nova where >>> you can preemptively add your thoughts or concerns. >>> >>> Anyway, we are eager to meet you all ! >>> >>> Oh, last point, given we will be at the vPTG, next week's weekly meeting >>> on Tuesday is CANCELLED. But I guess you'll see it either way if you lurk >>> the #openstack-nova channel ;-) >>> >>> See you next week ! >>> -Sylvain >>> >>> [1] >>> https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032853.h… >>> >>> >>> >> >> -- >> >> Sofía Enriquez >> >> she/her >> >> Software Engineer >> >> Red Hat PnT <https://www.redhat.com> >> >> IRC: @enriquetaso >> @RedHat <https://twitter.com/redhat> Red Hat >> <https://www.linkedin.com/company/red-hat> Red Hat >> <https://www.facebook.com/RedHatInc> >> <https://www.redhat.com> >> >>

2 years

Re: [openstack][ptg][InteropWG] : Interop WG Conclusion at PTG October 2021 and Seeking Volunteers for GoLang rewrites for Test Suites

by prakash RAMCHANDRAN

Hi all, We have few major Tasks to elevate Interop WG to enable OpenStack + Open Infrastructure Branding and Logo Programs: 1. https://opendev.org/osf/interop/src/branch/master/2020.06.json (To patch and update to 2020.10.json)All core module owners of Integrated OpenStack please respond before next Friday Nov 6 -Interop WG call on meetpad Interop Working Group - Weekly Friday 10-11 AM or UTC 17-18 (Next on Nov 6 & 13th)Lnink: https://meetpad.opendev.org/Interop-WG-weekly-meeting Checklist for PTLs (core - keystone, glance, nova, neutron, cinder & swift) and add-ons (heat & designate) 1. Did the Victoria switch for Jenkins to Zuul V3 and move to new Ubuntu Focal impact your DevStack and Tempesting module feature testing in any way for Interop? 2. Pease check https://opendev.org/osf/interop/src/branch/master/2020.06.json#L72We will drop stein and add wallaby, hence train release notes will be the base line for feature retention and compliance baseline testing Please verify what are the changes you may need for Victoria cycle for Logo program for your modules list all"required": [] - "advisory": [], - "deprecated": [], - "removed": [] 3. Reply by email the changes expected for us the review based on your Victoria release notes or add notes to https://releases.openstack.org/victoria/?_ga=2.174650977.277942436.16040126… 4. Discussions on Manila - Need Volunteer 5. Discussions on Ironic - Need Volunteers 6. Discussion on future Kata GoLang - Kata (with tempest vs k8s test tools or https://onsi.github.io/ginkgo/ + Airship, Starlingx, Zuul on infralab ?) - Need Volunteers ThanksPrakashFor Interop WG ================================================================================================================== Hi all, We have two sessions one at 13 UTC ( 6 AM PDT) and 16 UTC (9 AM PDT) Based on our interactions and collaborations - Manila team met and I could not attend their call but here is the link to their efforts: https://etherpad.opendev.org/p/wallaby-ptg-manila-interop We have 4 items to cover and seeking Volunteers for possible Manila & kubernetes Kata + RUNC based Container compliance (GoLang Must) Also we are planning to introduce GoLang based Refstak/Tempest if there are volunteers ready to work with QA team (Gmann). Thus we can finish in 1 session at 13 UTC and plan to cancel the second session at 16 UTC.====================================================================================================Your comments ======================================================================================================See you for Interop and add any comments above ThanksPrakashFor Interop WG On Monday, October 26, 2020, 08:38:32 AM PDT, prakash RAMCHANDRAN <pramchan(a)yahoo.com> wrote: Hi all My apology on the delayed start and here is the items we went over on first session. Refer : https://etherpad.opendev.org/p/interop-wallaby-ptg (Monday 10/26 recorded the meeting for everyone to see, its cloud recording and will know from PTG hosts where they have that?) Summary:1. Plan to Complete Victoria guidelines specs for interop in 2-6 weeks depending on adding new [OpenStack Powered File System Branding as Add-on Program] - last Ussuri guidelines are at https://opendev.org/osf/interop/src/branch/master/2020.06.json New one will be 2020.10.json to be added - For existing integrated modules [ Core OpenStack services including identity, compute, networking, block storage, and object storage ] - for two existing add-ons [Orchestration (heat) , DNS (designate) "Not a core capability, add-on program is available" - This is for Manila Filesystem add-on OpenDev Etherpad "Not a core capability, add-on program to be made available" | | | | OpenDev Etherpad | | | We have one more opportunity on 10/30 slot at the end of PTG if BMaaS (Ironic) if Julia has any proposals, besides (Open Infra Kata + Docker) Container has additional proposal community is working on. Look forward to seeing you all on October 30 as what the Road-map will look like for 2020 and 2021 going forward. ThanksPrakash On Monday, October 26, 2020, 06:09:00 AM PDT, Goutham Pacha Ravi <gouthampravi(a)gmail.com> wrote: Hi Prakash, We're here: https://zoom.us/j/92649902134?pwd=a01aMXl6ZlNEZDlsMjJMTGNMVUp1UT09 On Mon, Oct 26, 2020 at 6:06 AM prakash RAMCHANDRAN <pramchan(a)yahoo.com> wrote: https://meetpad.opendev.org/Interop-WG-weekly-meeting

4 years, 5 months

Re: [kolla-ansible][xena] Cell database HA/redundancy?

by Mark Goddard

On Fri, 3 Jun 2022 at 14:10, Norrie, Andrew <Andrew.Norrie(a)cgg.com> wrote: > > > Hi, > > > > We are currently planning some large OpenStack deployments utilizing > kolla-ansible and > > I’m curious what folks are doing with the cell database HA/redundancy. > > > > With kolla-ansible (xena) it appears that a loadbalancer setup is only > allowed for the > > default database shard (shard 0)... reference: > https://docs.openstack.org/kolla-ansible/latest/reference/databases/mariadb… > > > > If we are setting up separate cell database shards with Galera, I’m > wondering if there is a convenient work-around or configuration for > implementation of HA for these cell databases. > > > > In the inventory group_vars directory you can specify the group variables > (for each cell database) as: > > > > nova_cell_database_address: > > nova_cell_database_group: > > > > but these aren’t virtual IP hosts/addresses (non default db shard). This > works perfectly fine with > > a single server cell database but not Galera. If that db server goes down > the cell instance information is lost. > > > Hi Andrew, You are correct - only the first shard is load balanced. The sharding feature was actually just the first patch in a series intended to support proxysql. I believe this would add the functionality you are looking for. In fact, the proposed test case for proxysql in our CI is a multi-cell deployment. Here is the patch series: https://review.opendev.org/q/topic:proxysql Unfortunately it has been stuck for a while, largely due to core reviewer bandwidth. The author is Michael Arbet, who is often on IRC as kevko. I'd suggest registering your interest in these patches via gerrit, and at one of the weekly kolla IRC meetings (this week is cancelled due to the summit). If you have time available, then testing and providing reviews could help to get the patches moving. In the meantime, you can configure HAProxy to load balance additional services, by placing an HAProxy config snippet in /etc/kolla/config/haproxy/services.d/*.cfg. Regards, Mark Many thanks ... Andrew > ------------------------------ > “This e-mail and any accompanying attachments are confidential. The > information is intended solely for the use of the individual to whom it is > addressed. Any review, disclosure, copying, distribution, or use of the > email by others is strictly prohibited. If you are not the intended > recipient, you must not review, disclose, copy, distribute or use this > e-mail; please delete it from your system and notify the sender > immediately.” >

2 years, 9 months

Re: [openstack][InteropWG] : Interop weekly Friday call

by prakash RAMCHANDRAN

Hi all,Thanks Ghanshyam we may no impact based on zuul v3 for testing using tempest. If we submit a new guideline for 2020.10.json where will I see the patch under https://devops.org/osf/interior or patch?osf/interop Let's ho over the call tomorrow 10 AM PST.Please join and add your topics to https://etherpad.opendev.org/p/interop The meet pad link for call is on eitherpad. ThanksPrakash Sent from Yahoo Mail on Android On Sat, Oct 31, 2020 at 10:45 AM, Ghanshyam Mann<gmann(a)ghanshyammann.com> wrote: ---- On Fri, 30 Oct 2020 18:57:40 -0500 prakash RAMCHANDRAN <pramchan(a)yahoo.com> wrote ---- > Hi all, > We have few major Tasks to elevate Interop WG to enable OpenStack + Open Infrastructure Branding and Logo Programs: > 1. https://opendev.org/osf/interop/src/branch/master/2020.06.json (To patch and update to 2020.10.json)All core module owners of Integrated OpenStack please respond before next Friday Nov 6 -Interop WG call on meetpad > Interop Working Group - Weekly Friday 10-11 AM or UTC 17-18 (Next on Nov 6 & 13th)Lnink: https://meetpad.opendev.org/Interop-WG-weekly-meeting > Checklist for PTLs (core - keystone, glance, nova, neutron, cinder & swift) and add-ons (heat & designate) > 1. Did the Victoria switch for Jenkins to Zuul V3 and move to new Ubuntu Focal impact your DevStack and Tempesting module feature testing in any way for Interop? It is moved from zuulv2 native jobs to zuulv3 native and Ubuntu Bionic to Ubuntu Focal which basically are only testing framework side updates not on any user facing interface updates so it will not impact any interop way. -gmann > 2. Pease check https://opendev.org/osf/interop/src/branch/master/2020.06.json#L72We will drop stein and add wallaby, hence train release notes will be the base line for feature retention and compliance baseline testing > Please verify what are the changes you may need for Victoria cycle for Logo program for your modules list all"required": [] > "advisory": [], > "deprecated": [], > "removed": [] > > 3. Reply by email the changes expected for us the review based on your Victoria release notes or add notes to https://releases.openstack.org/victoria/?_ga=2.174650977.277942436.16040126… > > > 4. Discussions on Manila - Need Volunteer 5. Discussions on Ironic - Need Volunteers 6. Discussion on future Kata GoLang - Kata (with tempest vs k8s test tools or https://onsi.github.io/ginkgo/ + Airship, Starlingx, Zuul on infralab ?) - Need Volunteers > > ThanksPrakashFor Interop WG > ================================================================================================================== > > > Hi all, > We have two sessions one at 13 UTC ( 6 AM PDT) and 16 UTC (9 AM PDT) > Based on our interactions and collaborations - Manila team met and I could not attend their call but here is the link to their efforts: > https://etherpad.opendev.org/p/wallaby-ptg-manila-interop > We have 4 items to cover and seeking Volunteers for possible Manila & kubernetes Kata + RUNC based Container compliance (GoLang Must) > Also we are planning to introduce GoLang based Refstak/Tempest if there are volunteers ready to work with QA team (Gmann). > Thus we can finish in 1 session at 13 UTC and plan to cancel the second session at 16 UTC.====================================================================================================Your comments > > > > > ======================================================================================================See you for Interop and add any comments above > ThanksPrakashFor Interop WG > On Monday, October 26, 2020, 08:38:32 AM PDT, prakash RAMCHANDRAN <pramchan(a)yahoo.com> wrote: > > Hi all > My apology on the delayed start and here is the items we went over on first session. > Refer : https://etherpad.opendev.org/p/interop-wallaby-ptg (Monday 10/26 recorded the meeting for everyone to see, its cloud recording and will know from PTG hosts where they have that?) > Summary:1. Plan to Complete Victoria guidelines specs for interop in 2-6 weeks depending on adding new [OpenStack Powered File System Branding as Add-on Program] > - last Ussuri guidelines are at https://opendev.org/osf/interop/src/branch/master/2020.06.json > > > > New one will be 2020.10.json to be added > - For existing integrated modules [ Core OpenStack services including identity, compute, networking, block storage, and object storage ] - for two existing add-ons [Orchestration (heat) , DNS (designate) "Not a core capability, add-on program is available" - This is for Manila Filesystem add-on OpenDev Etherpad "Not a core capability, add-on program to be made available" > OpenDev Etherpad > > > > > > > > > We have one more opportunity on 10/30 slot at the end of PTG if BMaaS (Ironic) if Julia has any proposals, besides (Open Infra Kata + Docker) Container has additional proposal community is working on. Look forward to seeing you all on October 30 as what the Road-map will look like for 2020 and 2021 going forward. > ThanksPrakash > > On Monday, October 26, 2020, 06:09:00 AM PDT, Goutham Pacha Ravi <gouthampravi(a)gmail.com> wrote: > > Hi Prakash, > > We're here: https://zoom.us/j/92649902134?pwd=a01aMXl6ZlNEZDlsMjJMTGNMVUp1UT09 > > On Mon, Oct 26, 2020 at 6:06 AM prakash RAMCHANDRAN <pramchan(a)yahoo.com> wrote: > https://meetpad.opendev.org/Interop-WG-weekly-meeting >

4 years, 4 months

Re: [openstack][ptg][InteropWG] : Interop WG Conclusion at PTG October 2021 and Seeking Volunteers for GoLang rewrites for Test Suites

by Ghanshyam Mann

---- On Fri, 30 Oct 2020 18:57:40 -0500 prakash RAMCHANDRAN <pramchan(a)yahoo.com> wrote ---- > Hi all, > We have few major Tasks to elevate Interop WG to enable OpenStack + Open Infrastructure Branding and Logo Programs: > 1. https://opendev.org/osf/interop/src/branch/master/2020.06.json (To patch and update to 2020.10.json)All core module owners of Integrated OpenStack please respond before next Friday Nov 6 -Interop WG call on meetpad > Interop Working Group - Weekly Friday 10-11 AM or UTC 17-18 (Next on Nov 6 & 13th)Lnink: https://meetpad.opendev.org/Interop-WG-weekly-meeting > Checklist for PTLs (core - keystone, glance, nova, neutron, cinder & swift) and add-ons (heat & designate) > 1. Did the Victoria switch for Jenkins to Zuul V3 and move to new Ubuntu Focal impact your DevStack and Tempesting module feature testing in any way for Interop? It is moved from zuulv2 native jobs to zuulv3 native and Ubuntu Bionic to Ubuntu Focal which basically are only testing framework side updates not on any user facing interface updates so it will not impact any interop way. -gmann > 2. Pease check https://opendev.org/osf/interop/src/branch/master/2020.06.json#L72We will drop stein and add wallaby, hence train release notes will be the base line for feature retention and compliance baseline testing > Please verify what are the changes you may need for Victoria cycle for Logo program for your modules list all"required": [] > "advisory": [], > "deprecated": [], > "removed": [] > > 3. Reply by email the changes expected for us the review based on your Victoria release notes or add notes to https://releases.openstack.org/victoria/?_ga=2.174650977.277942436.16040126… > > > 4. Discussions on Manila - Need Volunteer 5. Discussions on Ironic - Need Volunteers 6. Discussion on future Kata GoLang - Kata (with tempest vs k8s test tools or https://onsi.github.io/ginkgo/ + Airship, Starlingx, Zuul on infralab ?) - Need Volunteers > > ThanksPrakashFor Interop WG > ================================================================================================================== > > > Hi all, > We have two sessions one at 13 UTC ( 6 AM PDT) and 16 UTC (9 AM PDT) > Based on our interactions and collaborations - Manila team met and I could not attend their call but here is the link to their efforts: > https://etherpad.opendev.org/p/wallaby-ptg-manila-interop > We have 4 items to cover and seeking Volunteers for possible Manila & kubernetes Kata + RUNC based Container compliance (GoLang Must) > Also we are planning to introduce GoLang based Refstak/Tempest if there are volunteers ready to work with QA team (Gmann). > Thus we can finish in 1 session at 13 UTC and plan to cancel the second session at 16 UTC.====================================================================================================Your comments > > > > > ======================================================================================================See you for Interop and add any comments above > ThanksPrakashFor Interop WG > On Monday, October 26, 2020, 08:38:32 AM PDT, prakash RAMCHANDRAN <pramchan(a)yahoo.com> wrote: > > Hi all > My apology on the delayed start and here is the items we went over on first session. > Refer : https://etherpad.opendev.org/p/interop-wallaby-ptg (Monday 10/26 recorded the meeting for everyone to see, its cloud recording and will know from PTG hosts where they have that?) > Summary:1. Plan to Complete Victoria guidelines specs for interop in 2-6 weeks depending on adding new [OpenStack Powered File System Branding as Add-on Program] > - last Ussuri guidelines are at https://opendev.org/osf/interop/src/branch/master/2020.06.json > > > > New one will be 2020.10.json to be added > - For existing integrated modules [ Core OpenStack services including identity, compute, networking, block storage, and object storage ] - for two existing add-ons [Orchestration (heat) , DNS (designate) "Not a core capability, add-on program is available" - This is for Manila Filesystem add-on OpenDev Etherpad "Not a core capability, add-on program to be made available" > OpenDev Etherpad > > > > > > > > > We have one more opportunity on 10/30 slot at the end of PTG if BMaaS (Ironic) if Julia has any proposals, besides (Open Infra Kata + Docker) Container has additional proposal community is working on. Look forward to seeing you all on October 30 as what the Road-map will look like for 2020 and 2021 going forward. > ThanksPrakash > > On Monday, October 26, 2020, 06:09:00 AM PDT, Goutham Pacha Ravi <gouthampravi(a)gmail.com> wrote: > > Hi Prakash, > > We're here: https://zoom.us/j/92649902134?pwd=a01aMXl6ZlNEZDlsMjJMTGNMVUp1UT09 > > On Mon, Oct 26, 2020 at 6:06 AM prakash RAMCHANDRAN <pramchan(a)yahoo.com> wrote: > https://meetpad.opendev.org/Interop-WG-weekly-meeting >

4 years, 5 months

RE: [openstack][InteropWG] : Interop weekly Friday call

by Kanevsky, Arkady

Team, I will have to miss today’s call From: prakash RAMCHANDRAN <pramchan(a)yahoo.com> Sent: Friday, November 6, 2020 12:48 AM To: Ghanshyam Mann Cc: openstack-discuss(a)lists.openstack.org; Voelker, Mark (VMware); Kanevsky, Arkady; Goutham Pacha Ravi Subject: Re: [openstack][InteropWG] : Interop weekly Friday call [EXTERNAL EMAIL] Hi all, Thanks Ghanshyam we may no impact based on zuul v3 for testing using tempest. If we submit a new guideline for 2020.10.json where will I see the patch under https://devops.org/osf/interior or patch? osf/interop Let's ho over the call tomorrow 10 AM PST. Please join and add your topics to https://etherpad.opendev.org/p/interop The meet pad link for call is on eitherpad. Thanks Prakash Sent from Yahoo Mail on Android<https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_And…> On Sat, Oct 31, 2020 at 10:45 AM, Ghanshyam Mann <gmann(a)ghanshyammann.com<mailto:gmann@ghanshyammann.com>> wrote: ---- On Fri, 30 Oct 2020 18:57:40 -0500 prakash RAMCHANDRAN <pramchan(a)yahoo.com<mailto:pramchan@yahoo.com>> wrote ---- > Hi all, > We have few major Tasks to elevate Interop WG to enable OpenStack + Open Infrastructure Branding and Logo Programs: > 1. https://opendev.org/osf/interop/src/branch/master/2020.06.json <https://opendev.org/osf/interop/src/branch/master/2020.06.json%20> (To patch and update to 2020.10.json)All core module owners of Integrated OpenStack please respond before next Friday Nov 6 -Interop WG call on meetpad > Interop Working Group - Weekly Friday 10-11 AM or UTC 17-18 (Next on Nov 6 & 13th)Lnink: https://meetpad.opendev.org/Interop-WG-weekly-meeting > Checklist for PTLs (core - keystone, glance, nova, neutron, cinder & swift) and add-ons (heat & designate) > 1. Did the Victoria switch for Jenkins to Zuul V3 and move to new Ubuntu Focal impact your DevStack and Tempesting module feature testing in any way for Interop? It is moved from zuulv2 native jobs to zuulv3 native and Ubuntu Bionic to Ubuntu Focal which basically are only testing framework side updates not on any user facing interface updates so it will not impact any interop way. -gmann > 2. Pease check https://opendev.org/osf/interop/src/branch/master/2020.06.json#L72We will drop stein and add wallaby, hence train release notes will be the base line for feature retention and compliance baseline testing > Please verify what are the changes you may need for Victoria cycle for Logo program for your modules list all"required": [] > "advisory": [], > "deprecated": [], > "removed": [] > > 3. Reply by email the changes expected for us the review based on your Victoria release notes or add notes to https://releases.openstack.org/victoria/?_ga=2.174650977.277942436.16040126… > > > 4. Discussions on Manila - Need Volunteer 5. Discussions on Ironic - Need Volunteers 6. Discussion on future Kata GoLang - Kata (with tempest vs k8s test tools or https://onsi.github.io/ginkgo/ <https://onsi.github.io/ginkgo/%20> + Airship, Starlingx, Zuul on infralab ?) - Need Volunteers > > ThanksPrakashFor Interop WG > ================================================================================================================== > > > Hi all, > We have two sessions one at 13 UTC ( 6 AM PDT) and 16 UTC (9 AM PDT) > Based on our interactions and collaborations - Manila team met and I could not attend their call but here is the link to their efforts: > https://etherpad.opendev.org/p/wallaby-ptg-manila-interop > We have 4 items to cover and seeking Volunteers for possible Manila & kubernetes Kata + RUNC based Container compliance (GoLang Must) > Also we are planning to introduce GoLang based Refstak/Tempest if there are volunteers ready to work with QA team (Gmann). > Thus we can finish in 1 session at 13 UTC and plan to cancel the second session at 16 UTC.====================================================================================================Your comments > > > > > ======================================================================================================See you for Interop and add any comments above > ThanksPrakashFor Interop WG > On Monday, October 26, 2020, 08:38:32 AM PDT, prakash RAMCHANDRAN <pramchan(a)yahoo.com<mailto:pramchan@yahoo.com>> wrote: > > Hi all > My apology on the delayed start and here is the items we went over on first session. > Refer : https://etherpad.opendev.org/p/interop-wallaby-ptg <https://etherpad.opendev.org/p/interop-wallaby-ptg%20> (Monday 10/26 recorded the meeting for everyone to see, its cloud recording and will know from PTG hosts where they have that?) > Summary:1. Plan to Complete Victoria guidelines specs for interop in 2-6 weeks depending on adding new [OpenStack Powered File System Branding as Add-on Program] > - last Ussuri guidelines are at https://opendev.org/osf/interop/src/branch/master/2020.06.json > > > > New one will be 2020.10.json to be added > - For existing integrated modules [ Core OpenStack services including identity, compute, networking, block storage, and object storage ] - for two existing add-ons [Orchestration (heat) , DNS (designate) "Not a core capability, add-on program is available" - This is for Manila Filesystem add-on OpenDev Etherpad "Not a core capability, add-on program to be made available" > OpenDev Etherpad > > > > > > > > > We have one more opportunity on 10/30 slot at the end of PTG if BMaaS (Ironic) if Julia has any proposals, besides (Open Infra Kata + Docker) Container has additional proposal community is working on. Look forward to seeing you all on October 30 as what the Road-map will look like for 2020 and 2021 going forward. > ThanksPrakash > > On Monday, October 26, 2020, 06:09:00 AM PDT, Goutham Pacha Ravi <gouthampravi(a)gmail.com<mailto:gouthampravi@gmail.com>> wrote: > > Hi Prakash, > > We're here: https://zoom.us/j/92649902134?pwd=a01aMXl6ZlNEZDlsMjJMTGNMVUp1UT09 <https://zoom.us/j/92649902134?pwd=a01aMXl6ZlNEZDlsMjJMTGNMVUp1UT09%20> > > On Mon, Oct 26, 2020 at 6:06 AM prakash RAMCHANDRAN <pramchan(a)yahoo.com<mailto:pramchan@yahoo.com>> wrote: > https://meetpad.opendev.org/Interop-WG-weekly-meeting >

4 years, 4 months

RE: [kolla-ansible][xena] Cell database HA/redundancy?

by Norrie, Andrew

Hi Mark, Thanks for the reply. I'll look into the HAProxy "custom config" as suggested and using different ports for the cell databases. Maybe that can be worked in. We are expanding our OpenStack/kolla-ansible personnel/knowledge so will look into the possibility for us to contribute as reviewers/testers as a start. Best regards .... Andrew From: Mark Goddard <mark(a)stackhpc.com> Sent: Monday, June 6, 2022 2:22 AM To: Norrie, Andrew <Andrew.Norrie(a)cgg.com> Cc: openstack-discuss(a)lists.openstack.org Subject: Re: [kolla-ansible][xena] Cell database HA/redundancy? On Fri, 3 Jun 2022 at 14:10, Norrie, Andrew <Andrew.Norrie(a)cgg.com<mailto:Andrew.Norrie@cgg.com>> wrote: Hi, We are currently planning some large OpenStack deployments utilizing kolla-ansible and I'm curious what folks are doing with the cell database HA/redundancy. With kolla-ansible (xena) it appears that a loadbalancer setup is only allowed for the default database shard (shard 0)... reference: https://docs.openstack.org/kolla-ansible/latest/reference/databases/mariadb…<https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.open…> If we are setting up separate cell database shards with Galera, I'm wondering if there is a convenient work-around or configuration for implementation of HA for these cell databases. In the inventory group_vars directory you can specify the group variables (for each cell database) as: nova_cell_database_address: nova_cell_database_group: but these aren't virtual IP hosts/addresses (non default db shard). This works perfectly fine with a single server cell database but not Galera. If that db server goes down the cell instance information is lost. Hi Andrew, You are correct - only the first shard is load balanced. The sharding feature was actually just the first patch in a series intended to support proxysql. I believe this would add the functionality you are looking for. In fact, the proposed test case for proxysql in our CI is a multi-cell deployment. Here is the patch series: https://review.opendev.org/q/topic:proxysql<https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.op…> Unfortunately it has been stuck for a while, largely due to core reviewer bandwidth. The author is Michael Arbet, who is often on IRC as kevko. I'd suggest registering your interest in these patches via gerrit, and at one of the weekly kolla IRC meetings (this week is cancelled due to the summit). If you have time available, then testing and providing reviews could help to get the patches moving. In the meantime, you can configure HAProxy to load balance additional services, by placing an HAProxy config snippet in /etc/kolla/config/haproxy/services.d/*.cfg. Regards, Mark Many thanks ... Andrew ________________________________ "This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited. If you are not the intended recipient, you must not review, disclose, copy, distribute or use this e-mail; please delete it from your system and notify the sender immediately." ________________________________ "This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited. If you are not the intended recipient, you must not review, disclose, copy, distribute or use this e-mail; please delete it from your system and notify the sender immediately."

2 years, 9 months

RE: openstack-discuss Digest, Vol 60, Issue 10 ~ Fwaas in Openstack 2023.1 antelope

by Asma Naz Shariq

Hi Openstack Community! I have set up OpenStack release 2023.1 antelope with Kolla-Ansible . However, I noticed that there is no enable_plugin option in the /etc/kolla/global.yml file. Now, I am trying to install FWaaS (Firewall-as-a-Service) following the instructions provided in this OpenStack's Firewall-as-a-Service (FWaaS) v2 scenario documentation. The documentation states, On Ubuntu and CentOS, modify the [fwaas] section in the /etc/neutron/fwaas_driver.ini file instead of /etc/neutron/neutron.conf. Unfortunately, I cannot find the fwaas_driver.ini file in the neutron-server, neutron-l3-agent, or neutron-openvswitch-agent containers Can someone guide me on how to properly install FWaaS in a Kolla environment using the information from the provided link? Best, -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Friday, October 6, 2023 1:27 PM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 60, Issue 10 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: [ops] [nova] "invalid argument: shares xxx must be in range [1, 10000]" after 1:25.2.0 to 1.25.2.1. update (Massimo Sgaravatto) 2. [TC][Monasca] Proposal to mark Monasca as an inactive project (S?awek Kap?o?ski) 3. [neutron] Neutron drivers meeting cancelled (Rodolfo Alonso Hernandez) ---------------------------------------------------------------------- Message: 1 Date: Fri, 6 Oct 2023 09:10:47 +0200 From: Massimo Sgaravatto <massimo.sgaravatto(a)gmail.com> To: Franciszek Przewo?ny <fprzewozny(a)opera.com> Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org>, smooney(a)redhat.com Subject: Re: [ops] [nova] "invalid argument: shares xxx must be in range [1, 10000]" after 1:25.2.0 to 1.25.2.1. update Message-ID: <CALaZjRGh6xnzX12cMgDTYx2yJYddUD9X3oh60JWnrB33ZdEf_Q(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Thanks a lot Franciszek ! I was indeed seeing the problem with a VM big 56 vcpus while I didn't see the issue with a tiny instance Thanks again ! Cheers, Massimo On Fri, Oct 6, 2023 at 8:58?AM Franciszek Przewo?ny <fprzewozny(a)opera.com> wrote: > Hi Massimo, > > We are using Ubuntu for our environments and we experienced the same > issue during upgrade from Yoga/Focal to Yoga/Jammy. On Yoga/Focal > cgroups_v1 were used, and cpu_shares parameter value was cpu count * > 1024. From Jammy > cgroups_v2 have been implemented, and cpu_shares value has been set by > default to 100. It has hard limit of 10000, so flavors with more than > 9vCPUs won't fit. If you need to fix this issue without stopping VMs, > you can set cpu_shares with libvirt command: virsh schedinfo $domain > --live > cpu_shares=100 > for more details about virsh schedinfo visit: > https://libvirt.org/manpages/virsh.html#schedinfo > > BR, > Franciszek > > On 5 Oct 2023, at 21:17, smooney(a)redhat.com wrote: > > On Thu, 2023-10-05 at 16:53 +0200, Massimo Sgaravatto wrote: > > Dear all > > We have recently updated openstack nova on some AlmaLinux9 compute > nodes running Yoga from 1:25.2.0 to 1.25.2.1. After this operation > some VMs don't start anymore. In the log it is reported: > > libvirt.libvirtError: invalid argument: shares \'57344\' must be in > range [1, 10000]\n'} > > libvirt version is 9.0.0-10.3 > > > A quick google search suggests that it is something related to cgroups > and it is fixed in libvirt >= 9.1 (which is not yet in the almalinux9 repos). > Did I get it right ? > > not quite > > it is reated to cgroups but the cause is that in cgroups_v1 the > maxvlaue of shares i.e. cpu_shares changed form make int to 10000 in > cgroups_v2 so the issue is teh vm requested a cpu share value of 57344 > which is not vlaid on an OS that is useing cgroups_v2 libvirt will not > clamp the value nor will nova. > you have to change the volue in your flavor and resize the vm. > > > > > Thanks, Massimo > > > > >

1 year, 5 months

Re: [kolla-ansible][xena] Cell database HA/redundancy?

by Michal Arbet

Hi, I think my patchsets are in good shape and ready for merge, just need some reviewers finally :(. I am glad that there is this type of question, who knows, maybe this will speed up the process of merge :) You can still backport it to your downstream branches, we are using it in this way for several kolla-ansible versions and it works. Thanks, Michal Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline> st 8. 6. 2022 v 16:37 odesílatel Norrie, Andrew <Andrew.Norrie(a)cgg.com> napsal: > Hi Mark, > > > > Thanks for the reply. > > > > I’ll look into the HAProxy “custom config” as suggested and using > different ports for the cell databases. > > Maybe that can be worked in. > > > > We are expanding our OpenStack/kolla-ansible personnel/knowledge so will > look into the possibility for > > us to contribute as reviewers/testers as a start. > > > > Best regards .... Andrew > > > > *From:* Mark Goddard <mark(a)stackhpc.com> > *Sent:* Monday, June 6, 2022 2:22 AM > *To:* Norrie, Andrew <Andrew.Norrie(a)cgg.com> > *Cc:* openstack-discuss(a)lists.openstack.org > *Subject:* Re: [kolla-ansible][xena] Cell database HA/redundancy? > > > > > > > > On Fri, 3 Jun 2022 at 14:10, Norrie, Andrew <Andrew.Norrie(a)cgg.com> wrote: > > > > Hi, > > > > We are currently planning some large OpenStack deployments utilizing > kolla-ansible and > > I’m curious what folks are doing with the cell database HA/redundancy. > > > > With kolla-ansible (xena) it appears that a loadbalancer setup is only > allowed for the > > default database shard (shard 0)... reference: > https://docs.openstack.org/kolla-ansible/latest/reference/databases/mariadb… > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.open…> > > > > If we are setting up separate cell database shards with Galera, I’m > wondering if there is a convenient work-around or configuration for > implementation of HA for these cell databases. > > > > In the inventory group_vars directory you can specify the group variables > (for each cell database) as: > > > > nova_cell_database_address: > > nova_cell_database_group: > > > > but these aren’t virtual IP hosts/addresses (non default db shard). This > works perfectly fine with > > a single server cell database but not Galera. If that db server goes down > the cell instance information is lost. > > > > > > Hi Andrew, > > > > You are correct - only the first shard is load balanced. The sharding > feature was actually just the first patch in a series intended to support > proxysql. I believe this would add the functionality you are looking for. > In fact, the proposed test case for proxysql in our CI is a multi-cell > deployment. > > > > Here is the patch series: > > > > https://review.opendev.org/q/topic:proxysql > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.op…> > > > > Unfortunately it has been stuck for a while, largely due to core reviewer > bandwidth. The author is Michael Arbet, who is often on IRC as kevko. I'd > suggest registering your interest in these patches via gerrit, and at one > of the weekly kolla IRC meetings (this week is cancelled due to the > summit). If you have time available, then testing and providing reviews > could help to get the patches moving. > > > > In the meantime, you can configure HAProxy to load balance additional > services, by placing an HAProxy config snippet in > /etc/kolla/config/haproxy/services.d/*.cfg. > > > > Regards, > > Mark > > > > Many thanks ... Andrew > ------------------------------ > > “This e-mail and any accompanying attachments are confidential. The > information is intended solely for the use of the individual to whom it is > addressed. Any review, disclosure, copying, distribution, or use of the > email by others is strictly prohibited. If you are not the intended > recipient, you must not review, disclose, copy, distribute or use this > e-mail; please delete it from your system and notify the sender > immediately.” > > ------------------------------ > “This e-mail and any accompanying attachments are confidential. The > information is intended solely for the use of the individual to whom it is > addressed. Any review, disclosure, copying, distribution, or use of the > email by others is strictly prohibited. If you are not the intended > recipient, you must not review, disclose, copy, distribute or use this > e-mail; please delete it from your system and notify the sender > immediately.” >

2 years, 9 months

openstack-discuss search results for query "canceled meeting"