Send openstack-discuss mailing list submissions to
openstack-discuss@lists.openstack.org
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
openstack-discuss-request@lists.openstack.org
You can reach the person managing the list at
openstack-discuss-owner@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. [all][ptls][release] Action needed to move forward Unmaintained branch policy
(Jay Faulkner)
2. Re: [blazar] Proposing Mark Powers and Matt Crees as core reviewers
(Pierre Riteau)
3. [oslo] Removing feature branches of oslo.messaging
(Takashi Kajinami)
4. Re: [all][ptls][release] Action needed to move forward Unmaintained branch policy
(Dmitriy Rabotyagov)
5. Re: Need Help to setup Bumblebee VDI project (Andy Botting)
----------------------------------------------------------------------
Message: 1
Date: Thu, 29 Feb 2024 14:18:36 -0800
From: Jay Faulkner <jay@gr-oss.io>
Subject: [all][ptls][release] Action needed to move forward
Unmaintained branch policy
To: OpenStack Discuss <openstack-discuss@lists.openstack.org>
Message-ID:
<CA+sTGNekJcbP3-ePYjq90ghSiYO-QiNB1dSd0XbVtjV6nktstQ@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="0000000000009bb91406128ca449"
Hi all,
If you are a PTL of a project, a release liason, or a person generally
interested in older OpenStack branches, please make sure you take a look at
the topic here: https://review.opendev.org/q/topic:%22vwx-unmaintained%22
and vote appropriately on projects you care about.
More information can be found in the commit message for the patches
themselves.
A lot of folks have done work behind the scenes to enable this transition;
please help us by doing your part and getting these reviews done in a
timely manner is one way we can show gratitude to the releases team and
others who have worked to make this transition possible.
Thanks,
Jay Faulkner
OpenStack TC Chair
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 903 bytes
Desc: not available
------------------------------
Message: 2
Date: Fri, 1 Mar 2024 07:37:20 +0100
From: Pierre Riteau <pierre@stackhpc.com>
Subject: Re: [blazar] Proposing Mark Powers and Matt Crees as core
reviewers
To: OpenStack Discuss <openstack-discuss@lists.openstack.org>
Cc: Mark Powers <markpowers@uchicago.edu>
Message-ID:
<CA+ny2sznbiieYXe_mg7XXA7eWmu8CQ-o0aw7E24njE7OJ=2_4w@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="000000000000c3835d0612939d56"
I have granted them both access to the blazar-core and blazar-release
groups. Welcome to the team!
On Fri, 23 Feb 2024 at 10:51, Pierre Riteau <pierre@stackhpc.com> wrote:
> Hello,
>
> I would like to nominate two new core reviewers for the Blazar project:
>
> - Mark Powers from University of Chicago
> - Matt Crees from StackHPC
>
> Mark Powers has been operating Blazar for several years for the Chameleon
> project (https://www.chameleoncloud.org) and maintains a fork of Blazar
> with many changes for this environment. The most useful changes are
> gradually being contributed upstream.
> Matt Crees has contributed several useful features to Blazar in the past
> few releases and helps to maintain the code.
>
> The Blazar project will benefit from their expertise and I trust their
> input as reviewers.
>
> Best wishes,
> Pierre Riteau (priteau)
>
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 1403 bytes
Desc: not available
------------------------------
Message: 3
Date: Fri, 1 Mar 2024 16:25:47 +0900
From: Takashi Kajinami <kajinamit@oss.nttdata.com>
Subject: [oslo] Removing feature branches of oslo.messaging
To: OpenStack Discuss <openstack-discuss@lists.openstack.org>
Message-ID: <a4904a15-e062-47bf-a207-10a68b0da13d@oss.nttdata.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hello,
# I already discussed this with a few people but am sending this email
# mostly for records.
Currently we have a few feature branches in oslo.messaging but it seems
these are not actually used now.
feature/amqp-dispatch-router : the feature was already merged into master
feature/nats-driver : this branch contains no meaningful change
feature/pika : the feature was already merged into master
feature/zmq : the feature was already merged into master
I'd propose deleting these useless branches. Note that currently the nats-driver
branch is causing config error in zuul, which was triggered by TripleO's retirement,
and my quick attempt revealed that, as I expected, CI in that branch is badly broken.
Please let me know if you have any concern.
Thank you,
Takashi
--
Takashi Kajinami
irc: tkajinam
github: https://github.com/kajinamit
launchpad: https://launchpad.net/~kajinamit
------------------------------
Message: 4
Date: Fri, 1 Mar 2024 09:32:33 +0100
From: Dmitriy Rabotyagov <noonedeadpunk@gmail.com>
Subject: Re: [all][ptls][release] Action needed to move forward
Unmaintained branch policy
To: Jay Faulkner <jay@gr-oss.io>
Cc: OpenStack Discuss <openstack-discuss@lists.openstack.org>
Message-ID:
<CAPd_6As6NsGJVUZ_vUcSfVQ+JEVX7ycfYX-uXVXgaffWOAwmUA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hey,
I, as OSA PTL, have quite some concerns for approving further
transition of branches to unmaintained state. There are multiple
underlying reasons for that:
1. Currently our master branch is blocked by removal of stable/yoga,
since `reno` is not ready to handle unmaintaned/* branches as well as
eom-* tags. So all releasenotes jobs are failing right now. I've
attempted to workaround the issue through the local reno config file
[1], but this seems not working still. The only way I was able to pass
releasenotes tox test, was by applying [2]. But even if it's proper
approach and patch will be merged, reno still needs to be tagged and
updated in upper-constraints, which can't be done as we're in a freeze
right now.
2. I am not getting part regarding permissions to unmaintained/*
branches that Brian was writing a while ago [3]. Sorry, I meant to
answer that thread instead, but it was pushed slightly out of sight by
other things. From what I recall during the original discussion of the
unmaintained policy, core team of the project should be able to have
access to such branches and take care of them if they want to. But now
it was told not to do so.
With that I'm really having a question, of who is intended to take
care of reviewing, let's say OSA's unmaintained branches, even if
there're outstanding patches being proposed by the community? I highly
doubt that anybody, except cores and the community around the project
care about that. And highly unlikely that openstack-unmaintained-core
will take care of that. I also do see that some projects already
created individual groups for themselves, which makes me even more
confused about what projects should do.
3. We've started getting bugs [4] regarding Yoga transition to
unmaintained status, since I assumed that we will have access to do
some post-migration fixes to the branch, allowing users to continue
using them if needed. But now Yoga is completely borked after
transition with no clear way of fixing it, keeping 1 and 2 points in
mind.
Based on that I'm slightly reluctant to continue with the process
until all points will be figured out. And what makes things even worse
- is the timing for these activities, since we are not a huge team,
and have our hands completely full especially close to the release,
and figuring out how this new process should work was not part of the
project plan as it was assumed as relatively simple change, which
appears to be quite major one that is also blocking ongoing
development.
[1] https://review.opendev.org/c/openstack/openstack-ansible/+/908499
[2] https://review.opendev.org/c/openstack/reno/+/910547
[3] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/ID6BUMR7XCGQQ6LPNLGYGPHCJAFYWJ5I/
[4] https://bugs.launchpad.net/openstack-ansible/+bug/2055417
чт, 29 февр. 2024 г. в 23:30, Jay Faulkner <jay@gr-oss.io>:
>
> Hi all,
>
> If you are a PTL of a project, a release liason, or a person generally interested in older OpenStack branches, please make sure you take a look at the topic here: https://review.opendev.org/q/topic:%22vwx-unmaintained%22 and vote appropriately on projects you care about.
>
> More information can be found in the commit message for the patches themselves.
>
> A lot of folks have done work behind the scenes to enable this transition; please help us by doing your part and getting these reviews done in a timely manner is one way we can show gratitude to the releases team and others who have worked to make this transition possible.
>
> Thanks,
> Jay Faulkner
> OpenStack TC Chair
------------------------------
Message: 5
Date: Fri, 1 Mar 2024 21:16:50 +1100
From: Andy Botting <andy@andybotting.com>
Subject: Re: Need Help to setup Bumblebee VDI project
To: Artemio Mendoza <artemiom681@gmail.com>
Cc: openstack-discuss@lists.openstack.org, kaushik.ramesh@ardc.edu.au
Message-ID:
<CAHj+3C7j3RdATeFuCzFPJizK2x-f-2R9ynyPcExQjA-=LgQ8FQ@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="0000000000004d8bb0061296ada2"
Hi Artemio,
We're thrilled you're interested in trying out Bumblebee!
Unfortunately, there's quite a few moving parts, so it's a bit complicated
to install. We're actually just dusting off some updates right now that I
hope will be done next week that should make testing it out easier. We
haven't run it against devstack though, but there's no reason why it
shouldn't work.
If you can wait until next week, I can point you to an updated
docker-compose stack that should make testing it out much easier.
cheers,
Andy
On Thu, 29 Feb 2024 at 01:27, Artemio Mendoza <artemiom681@gmail.com> wrote:
> Hello,
>
> I'm trying to set up the Bumblebee (https://github.com/NeCTAR-RC/bumblebee)
> project on my local computer to test. So I installed docker and tried setup
> by following the readme.
>
> But I'm really new in OpenStack (only tried to run OpenStack through
> devstack) so I would appreciate it if I could have a very detailed guide.
>
> So please share any idea, online video link, or guide document. anything
> is good to me.
>
> Looking forward to hearing from you.
>
> Thanks,
> Artemio Mendoza
>
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 1744 bytes
Desc: not available
------------------------------
Subject: Digest Footer
_______________________________________________
openstack-discuss mailing list -- openstack-discuss@lists.openstack.org
To unsubscribe send an email to openstack-discuss-leave@lists.openstack.org
------------------------------
End of openstack-discuss Digest, Vol 64, Issue 122
**************************************************