openstack-discuss

openstack-discuss@lists.openstack.org

September 2020

  • 217 participants
  • 289 discussions
All,A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner.I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole.Thoughts?[1]http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653…Chris ApseyDirector | Georgia Cyber RangeGEORGIA CYBER CENTER100 Grace Hopper Lane | Augusta, Georgia | 30901https://www.gacybercenter.org
2 2
0 0

04 Oct '21
Hi,As you may know, eventlet is incompatible with dnspython >= 2.0.0.0rc1.See [1] for the details. However, Debian unstable has 2.0.0.Would there be some good soul willing to help me fix this situation? Iwould need a patch to fix this, but I'm really not sure how to start.Cheers,Thomas Goirand (zigo)
8 15
0 0

27 May '21
Hi everyone,This has been discussed several times on this mailing list in the past, but we never got to actually pull the plug.Ask.openstack.org was launched in 2013. The reason for hosting our own setup was to be able to support multiple languages, while StackOverflow rejected our proposal to have our own openstack-branded StackExchange site. The Chinese ask.o.o side never really took off. The English side also never really worked perfectly (like email alerts are hopelessly broken), but we figured it would get better with time if a big community formed around it.Fast-forward to 2020 and the instance is lacking volunteers to help run it, while the code (and our customization of it) has become more complicated to maintain. It regularly fails one way or another, and questions there often go unanswered, making us look bad. Of the top 30 users, most have abandoned the platform since 2017, leaving only Bernd Bausch actively engaging and helping moderate questions lately. We have called for volunteers several times, but the offers for help never really materialized.At the same time, people are asking OpenStack questions on StackOverflow, and sometimes getting answers there[1]. The fragmentation of the "questions" space is not helping users getting good answers.I think it's time to pull the plug, makeask.openstack.org read-only (so that links to old answers are not lost) and redirect users to the mailing-list and the "OpenStack" tag on StackOverflow. I picked StackOverflow since it seems to have the most openstack questions (2,574 on SO, 76 on SuperUser and 430 on ServerFault).We discussed that option several times, but I now proposed a change to actually make it happen:https://review.opendev.org/#/c/746497/It's always a difficult decision to make to kill a resource, but I feel like in this case, consolidation and simplification would help.Thoughts, comments?[1]https://stackoverflow.com/questions/tagged/openstack-- Thierry
10 18
0 0
[stein][neutron] gratuitous arp
by Ignazio Cassano 13 May '21

13 May '21
Hello, I have a problem on stein neutron. When a vm migrate from one nodeto another I cannot ping it for several minutes. If in the vm I put ascript that ping the gateway continously, the live migration works fine andI can ping it. Why this happens ? I read something about gratuitous arp.Please, help me ?Any workaround , please ?Best RegardsIgnazio
3 33
0 0
Hi all,Following up to the previous mailing list [1] and virtual meetup [2]discussions, I would like to announce the plans to deprecate the 'iscsi'deploy interface.This is the updated plan discussed on the virtual meetup:1) In the Victoria cycle (i.e. right now): - Fill in the detected feature gaps [3]. - Switch off the iscsi deploy interface by default. - Change [agent]image_dowload_source to HTTP by default. - Give the direct deploy a higher priority, so that it's used by defaultunless disabled. - Mark it as deprecated in the code (causing warnings when enabled). - Release a major version of ironic to highlight the defaults changes.2) In the W cycle: - Keep the iscsi deploy deprecated. - Listen to operators' feedback.3) In the X cycle - Remove the iscsi deploy completely from ironic and IPA. - Remove support code from ironic-lib with a major version bump.Please let us know if you have any questions or concerns.Dmitry[1]http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016681.h…[2]https://etherpad.opendev.org/p/Ironic-Victoria-midcycle[3]https://storyboard.openstack.org/#!/story/2008075-- Red Hat GmbH,https://de.redhat.com/ , Registered seat: Grasbrunn,Commercial register: Amtsgericht Muenchen, HRB 153243,Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, MichaelO'Neill
1 1
0 0
On Tue, Sep 18, 2018 at 1:30 PM Alex Schultz <aschultz(a)redhat.com> wrote:>> On Tue, Sep 18, 2018 at 1:27 PM, Matt Riedemann <mriedemos(a)gmail.com> wrote:> > The release page says Ocata is planned to go into extended maintenance mode> > on Aug 27 [1]. There really isn't much to this except it means we don't do> > releases for Ocata anymore [2]. There is a caveat that project teams that do> > not wish to maintain stable/ocata after this point can immediately end of> > life the branch for their project [3]. We can still run CI using tags, e.g.> > if keystone goes ocata-eol, devstack on stable/ocata can still continue to> > install from stable/ocata for nova and the ocata-eol tag for keystone.> > Having said that, if there is no undue burden on the project team keeping> > the lights on for stable/ocata, I would recommend not tagging the> > stable/ocata branch end of life at this point.> >> > So, questions that need answering are:> >> > 1. Should we cut a final release for projects with stable/ocata branches> > before going into extended maintenance mode? I tend to think "yes" to flush> > the queue of backports. In fact, [3] doesn't mention it, but the resolution> > said we'd tag the branch [4] to indicate it has entered the EM phase.> >> > 2. Are there any projects that would want to skip EM and go directly to EOL> > (yes this feels like a Monopoly question)?> >>> I believe TripleO would like to EOL instead of EM for Ocata as> indicated by the thead>http://lists.openstack.org/pipermail/openstack-dev/2018-September/134671.ht…>Bringing this backup to see what we need to do to get the stable/ocatabranches ended for the TripleO projects. I'm bringing this upbecause we havehttps://review.openstack.org/#/c/647009/ which is forthe upcoming rename but CI is broken and we have no interest incontinue to keep the stable/ocata branches alive (or fix ci for them).Thanks,-Alex> Thanks,> -Alex>> > [1]https://releases.openstack.org/> > [2]> >https://docs.openstack.org/project-team-guide/stable-branches.html#maintena…> > [3]> >https://docs.openstack.org/project-team-guide/stable-branches.html#extended…> > [4]> >https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.…> >> > --> >> > Thanks,> >> > Matt> >> > __________________________________________________________________________> > OpenStack Development Mailing List (not for usage questions)> > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
5 11
0 0
[largescale-sig] OpenStack DB Archiver
by Arnaud Morin 10 Feb '21

10 Feb '21
Hello large-scalers!TLDR: we opensource a tool to help reducing size of databases. Seehttps://github.com/ovh/osarchiver/Few months ago, we released a tool, name osarchiver, which we are usingon our production environment (at OVH) to help reduce the size of ourtables in mariadb (or mysql)In fact, some tables are well know to grow very quickly.We use it, for example, to clean the OpenStack mistral database from oldtasks, actions and executions which are older than a year.Another use case could be to archive some data in another table (e.g. with_archived as suffix) if they are 6 months old, and delete this data after1 year.The source code of this tool is available here:https://github.com/ovh/osarchiver/We were wondering if some other users would be interested in using thetool, and maybe move it under the opendev governance?Feel free to contact us and/or answer this thread.Cheers,-- Arnaud, Pierre-Samuel and OVH team
12 18
0 0

05 Jan '21
Hello,I would like to start a discussion regarding the topic.At this moment in time we have an opportunity to be a more open andinclusive project by eliminating outdated naming conventions from tempestcodebase, such as blacklist, whitelist.We should take the opportunity and do our best to replace outdated termswith their more inclusive alternatives.As you can see in [1] the TripleO project is already working on thisinitiative, and I would like to work on this as well on the tempest side.Any thoughts? Shall I start with a sepc, adding deprecation warnings?[1]https://review.opendev.org/#/c/740013/1/specs/victoria/renaming_rules.rstKind regards,-- Arx CruzSoftware EngineerRed Hat EMEA <https://www.redhat.com>arxcruz(a)redhat.com@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>
6 9
0 0
Placement has been a separate project with its own governance sinceStein [1]. Since then, the main drivers behind the separation havemoved onto pastures new and with Tetsuro sadly declaring his non-candidacy for the PTL position for Wallaby [2], we're left in theunenviable position of potentially not having a PTL for the Wallabycycle. As such, it's probably time to discuss the future of Placementgovernance.Assuming no one steps forward for the Placement PTL role, it wouldappear to me that we have two options. Either we look at transitioningPlacement to a PTL-less project, or we move it back under novagovernance. To be honest, given how important placement is to nova andother projects now, I'm uncomfortable with the idea of not having apoint person who is ultimately responsible for things like cutting arelease (yes, delegation is encouraged but someone needs to herd thecats). At the same time, I do realize that placement is used by morethat nova now so nova cores and what's left of the separate placementcore team shouldn't be the only ones making this decision.So, assuming the worst happens and placement is left without a PTL forVictoria, what do we want to do?StephenPS: Apologies if I missed other projects with an interest in placement.I did try to catch them all /o\[1]http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002575…[2]http://lists.openstack.org/pipermail/openstack-discuss/2020-September/01749…
8 10
0 0

01 Nov '20
Thanks Andy.Regards.Forwarded ConversationSubject: [MURANO] DevStack Murano "yaql_function" Error------------------------Gönderen: Andy Botting <andy(a)andybotting.com>Date: 30 Nis 2020 Per, 14:13To: İzzettin Erdem <root.mch(a)gmail.com>Cc: Rong Zhu <aaronzhu1121(a)gmail.com>, <openstack-discuss(a)lists.openstack.org>Hi İzzettin,Thanks for your interest. Complete log link is at below. It is happening> when i try to deploy or update an environment.>>http://paste.openstack.org/show/792444/>I've encountered the errorAttributeError: 'method' object has no attribute '__yaql_function__'in our environment recently. I believe it started after we upgraded to theStein release.I haven't tracked it down yet, but calls to the YAQL function:std:Project.getEnvironmentOwner()in a Murano app seem to generate it.It's good to know that at least someone else has reproduced this.cheers,Andy----------Gönderen: İzzettin Erdem <root.mch(a)gmail.com>Date: 2 May 2020 Cmt, 16:08To: Andy Botting <andy(a)andybotting.com>Hi Andy,I solved this problem, it is happening when you try to create or update anenvironment on existing network. If you change the network with "createnew" parameter, it stuck on "creating -or updating- environment" state andafter that throws connection error. So i searched Murano network errors andi found this:https://docs.oracle.com/cd/E73172_01/E73173/html/issue-21976631.html. Iapplied these steps and i created successfully an environment just onlywith "create new" network parameter. After all these, i realized mydevstack environment has no internet connection and because of thismurano-agent could not install. So i tried to install Murano on my OSAstable/train test environment and i came with success until last step.Murano-agent installed but this time agent could not connect to rabbitmqinstance. I discussed this with OSA IRC channel and i think i have tostruggle with this for a long time.Apologize for this long mail but i wanted to inform you.Thanks. Regards.----------Gönderen: Andy Botting <andy(a)andybotting.com>Date: 3 May 2020 Paz, 14:24To: İzzettin Erdem <root.mch(a)gmail.com>Hi İzzettin,Glad you got it sorted. I think you've probably just worked around theissue. Using your new method, you're probably just avoiding thestd:Project.getEnvironmentOwnerYAQL call now. I've also worked around it in our environment, but I'dlike to solve it properly. When I get some time to look into itproperly, I'll let you know.cheers,Andy
3 3
0 0