3-15
Start using openstack-discuss ML: November 19
Stein-2 Milestone: January 10
--
Sean McGinnis (smcginnis)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack
I'm interested in some feedback from the community, particularly those running
OpenStack deployments, as to whether FIPS compliance [0][1] is something folks
are looking for.
I've been seeing small changes starting to be proposed here and there for
things like MD5 usage related to its
On Thu, Nov 01, 2018 at 03:08:09PM +, Jeremy Stanley wrote:
> On 2018-11-01 09:27:03 -0400 (-0400), Doug Hellmann wrote:
> > Jeremy Stanley writes:
> >
> > > On 2018-11-01 08:52:05 -0400 (-0400), Doug Hellmann wrote:
> > > [...]
> > >> Did I miss any options or issues with this approach?
> >
es & Dates
--
Forum at OpenStack Summit in Berlin: November 13-15
Start using openstack-discuss ML: November 19
Stein-2 Milestone: January 10
--
Sean McGinnis (smcginnis)
__
OpenStack Developmen
On Tue, Oct 30, 2018 at 11:10:42PM +0900, Ian Y. Choi wrote:
> Hello,
>
> I got involved organizing & mentoring Korean people for OpenStack upstream
> contribution for about last two months,
> and would like to share with community members.
>
Very cool! Thanks for organizing this Ian. And thank
On Fri, Oct 26, 2018 at 12:53:17PM -0400, David Moreau Simard wrote:
> Hi openstack-dev,
>
> I stumbled on odd and sudden pep8 failures with ARA recently and
> brought it up in #openstack-infra [1].
>
> It was my understanding that appending " # flake8: noqa" to a line of
> code would have
On Fri, Oct 26, 2018 at 4:42 AM wrote:
> Build failed.
>
> - release-openstack-python3
> http://logs.openstack.org/d3/d39466cf752f2a20a3047b9ca537b2b6adccb154/release/release-openstack-python3/345a591/
> : POST_FAILURE in 3m 57s
> - announce-release announce-release : SKIPPED
> -
On Wed, Oct 24, 2018 at 12:08 AM Tony Breeds
wrote:
> On Wed, Oct 24, 2018 at 03:23:53AM +, z...@openstack.org wrote:
> > Build failed.
> >
> > - release-openstack-python3
> http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/
> :
On Tue, Oct 23, 2018 at 10:30:23AM -0400, Ben Nemec wrote:
>
>
> On 10/23/18 9:58 AM, Matt Riedemann wrote:
> > On 10/23/2018 8:09 AM, Ben Nemec wrote:
> > > Can't we just add a noop command like we are for the services that
> > > don't currently need upgrade checks?
> >
> > We could, but I was
On Mon, Oct 22, 2018 at 07:49:35AM -0700, Morgan Fainberg wrote:
> I should be able to do a write up for Keystone's removal of paste *and*
> move to flask soon.
>
> I can easily extract the bit of code I wrote to load our external
> middleware (and add an external loader) for the transition away
This appears to be another in-transit job conflict with the py3 work.
Things should be fine, but we will need to manually propose the constraint
update since it was skipped.
On Fri, Oct 19, 2018, 09:14 wrote:
> Build failed.
>
> - release-openstack-python3
>
/135689.html
[2] http://eavesdrop.openstack.org/#Release_Team_Meeting
Upcoming Deadlines & Dates
--
Stein-1 milestone: October 25 (R-24 week)
Forum at OpenStack Summit in Berlin: November 13-15
--
Sean McGinnis (smcgi
On Wed, Oct 17, 2018 at 10:41:36AM -0500, Matt Riedemann wrote:
> On 10/17/2018 9:24 AM, Ivan Kolodyazhny wrote:
> >
> > As you may know, unfortunately, Horizon doesn't support all features
> > provided by APIs. That's why we created feature gaps list [1].
> >
> > I'd got a lot of great
On Tue, Oct 16, 2018 at 06:03:54PM +0530, ʂʍɒρƞįł Ҟưȴķɒʁʉɨ wrote:
> Dear OpenStackers,
>
> For a few months now, I am not able to contribute to code or reviewing
> Kolla and Requirements actively given my current responsibilities, I
> would like to take a step back and release my core reviewer
On Mon, Oct 15, 2018 at 03:01:07PM -0500, Jimmy McArthur wrote:
> Hi -
>
> The Forum schedule is now up
> (https://www.openstack.org/summit/berlin-2018/summit-schedule/#track=262).
> If you see a glaring content conflict within the Forum itself, please let me
> know.
>
I have updated the Forum
On Fri, Oct 12, 2018 at 11:44:11AM -0400, Doug Hellmann wrote:
> Sean McGinnis writes:
>
> > [snip]
> >
> > One of the big motivators in the past was also to have output that
> > downstream
> > distros and users could pick up for testing and early packagi
On Mon, Oct 15, 2018 at 01:40:37PM +0100, Chris Dent wrote:
>
> Back in August [1] there was an email thread about the Paste package
> being essentially unmaintained and several OpenStack projects still
> using it. At that time we reached the conclusion that we should
> investigate having
On Fri, Oct 12, 2018 at 11:25:20AM +0200, Martin Magr wrote:
> Greetings guys,
>
> On Thu, Oct 11, 2018 at 4:19 PM, Miguel Angel Ajo Pelayo <
> majop...@redhat.com> wrote:
>
> > Adding the mailing lists back to your reply, thank you :)
> >
> > I guess that +melvin.hills...@huawei.com can
> >
Libraries should be released early and often so their consumers can pick up
merged changes, and issues with those changes can be identified close to when
the change is made. To help with this, we are considering forcing at least one
library release per milestone (if there are unreleased merged
> >
> >
> > What I mean is that we run too into a situation where we have a large
> > backlog of CI jobs since we have to many changes and jobs in flight.
> >
> > So, I'm asking whether there is a good way to not duplicating all jobs
> > to run on all three interpreters. Do we really need testing
On Mon, Oct 08, 2018 at 10:27:06AM -0400, Doug Hellmann wrote:
> TC members,
>
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
>
> Last term we went
> >
> > I think we can definitely manage the agenda to minimize the number of
> > complex discussions. If that proves to be too hard, I wouldn't mind
> > meeting more often, but there does seem to be a lot of support for
> > preferring other venues for those conversations.
> >
> >
> +1 I think
On Mon, Oct 08, 2018 at 03:09:36PM +0800, Yikun Jiang wrote:
> In Denver, we agree to add a new "re-image" API in cinder to support upport
> volume-backed server rebuild with a new image.
>
> An initial blueprint has been drafted in [3], welcome to review it, thanks.
> : )
>
> [snip]
>
> The
On Thu, Oct 04, 2018 at 05:47:53PM +, Jeremy Stanley wrote:
> On 2018-10-04 13:40:05 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > TC members, please reply to this thread and indicate if you would
> > find meeting at 1300 UTC on the first Thursday of every month
> > acceptable, and of course
the cycle goals [1]. Please
prioritize reviews for these appropriately.
[1] https://governance.openstack.org/tc/goals/stein/index.html
Upcoming Deadlines & Dates
--
Stein-1 milestone: October 25 (R-24 week)
Forum at OpenStack Summit in Berlin: November 13-15
--
On Wed, Oct 03, 2018 at 09:45:25AM -0500, Jay S. Bryant wrote:
> Team,
>
> We had discussed the possibility of adding Gorka to the stable core team
> during the PTG. He does review a number of our backport patches and is
> active in that area.
>
> If there are no objections in the next week I
On Tue, Oct 02, 2018 at 01:45:38PM -0500, Matt Riedemann wrote:
> On 10/2/2018 10:41 AM, Miguel Lavalle wrote:
> > Hi Stable Team,
> >
> > I want to nominate Bernard Cafarrelli as a stable core reviewer for
> > Neutron and related projects. Bernard has been increasing the number of
> > stable
On Fri, Sep 28, 2018 at 01:54:01PM -0500, Lance Bragstad wrote:
> On Fri, Sep 28, 2018 at 1:03 PM Harry Rybacki wrote:
>
> > On Fri, Sep 28, 2018 at 1:57 PM Morgan Fainberg
> > wrote:
> > >
> > > Ideally I would like to see it in the form of least specific to most
> > specific. But more
> On Fri, Sep 28, 2018 at 8:48 AM Lance Bragstad wrote:
>
> > Bumping this thread again and proposing two conventions based on the
> > discussion here. I propose we decide on one of the two following
> > conventions:
> >
> > *::*
> >
> > or
> >
> > *:_*
> >
> > Where is the corresponding
This probably applies to all deployment tools, so hopefully this reaches the
right folks.
In Havana, Cinder deprecated the use of specifying the module for configuring
backup drivers. Patch https://review.openstack.org/#/c/595372/ finally removed
the backwards compatibility handling for configs
During the Stein PTG in Denver, the release management team talked about ways
we can make things simpler and reduce the "paper pushing" work that all teams
need to do right now. One topic that came up was the usefulness of pushing tags
around milestones during the cycle.
There were a couple of
On Fri, Sep 21, 2018 at 04:19:35PM -0500, Ben Nemec wrote:
>
>
> On 09/21/2018 03:53 PM, Matt Riedemann wrote:
> > Updates for this week:
> >
> > * As bnemec noted in the last update [1], he's making some progress with
> > the oslo.upgradecheck library. He's retrofitting the nova-status upgrade
On Fri, Sep 21, 2018 at 08:26:41AM -0600, Doug Hellmann wrote:
> Excerpts from Elõd Illés's message of 2018-09-21 16:08:28 +0200:
> > Hi,
> >
> > Here is an etherpad with the teams that have stable:follow-policy tag on
> > their repos:
> >
> >
On Wed, Sep 19, 2018 at 08:43:24PM -0500, Jay S Bryant wrote:
> All,
>
> In the last year we have had some changes to Core team participation. This
> was a topic of discussion at the PTG in Denver last week. Based on that
> discussion I have reached out to John Griffith and Winston D (Huang
nstack.org/cgit/openstack/governance/tree/reference/projects.yaml
[2]
https://docs.openstack.org/infra/manual/creators.html#prepare-an-initial-release
--
Sean McGinnis (smcginnis)
__
OpenStack Development Mailing List (not f
On Thu, Sep 20, 2018 at 05:30:32PM -0500, Melvin Hillsman wrote:
> Hey everyone,
>
> During the TC meeting at the PTG we discussed the ideal way to capture
> user-centric feedback; particular from our various groups like SIGs, WGs,
> etc.
>
> Options that were mentioned ranged from a wiki page
On Thu, Sep 20, 2018 at 03:46:43PM -0600, Doug Hellmann wrote:
> Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +:
> > tl;dr: The openstack, openstack-dev, openstack-sigs and
> > openstack-operators mailing lists (to which this is being sent) will
> > be replaced by a new
nstack.org/#Release_Team_Meeting
Upcoming Deadlines & Dates
--
Stein-1 milestone: October 25 (R-24 week)
Forum at OpenStack Summit in Berlin: November 13-15
--
Sean McGinnis (smcginnis)
__
OpenStack Developmen
On Tue, Sep 18, 2018 at 02:27:03PM -0500, Matt Riedemann 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
> >
> > Plan
> >
> > We would now like to have the driverfixes/ocata branch deleted so there is
> > no
> > confusion about where backports should go and we don't accidentally get
> > these
> > out of sync again.
> >
> > Infra team, please delete this branch or let me know if there is a
Hello Cinder and Infra teams. Cinder needs some help from infra or some
pointers on how to proceed.
tl;dr - The openstack/cinder repo had a driverfixes/ocata branch created for
fixes that no longer met the more restrictive phase II stable policy criteria.
Extended maintenance has changed that and
>
> > I also have technical questions about 'wechat' (like how do you
> > use it without a smartphone?) and the relevance of tools we
> > currently use, but this will open Pandora's box, and I'd rather
> > not spend my energy on closing that box right now :D
>
> Not that I was planning on
On Sat, Sep 08, 2018 at 09:54:33AM +0900, Trinh Nguyen wrote:
> Hi,
>
> Thanks for the summary.
>
> I just added Searchlight to the Stein deliverable [1]. One concern is we
> moved our projects to Storyboard last week, do I have to change the project
> file to reflect that and how?
>
> Thanks,
the Summit and Forum in
Berlin.
Upcoming Deadlines & Dates
--
Stein-1 milestone: October 25 (R-24 week)
Forum at OpenStack Summit in Berlin: November 13-15
--
Sean McGinnis (smcginnis)
__
OpenS
>
> +-+--+---+-++
> | Team| Open | Total | Status
> | Champion |
>
/rocky/
Congratulations to all of the teams who have contributed to this release!
Our next production cycle, Stein, has already started. We will meet in Denver,
Colorado, USA September 10-14 at the Project Team Gathering to plan the work
for the upcoming cycle. I hope to see you there!
Thanks,
Sean
> >
> > Yeah it's already on the PTG agenda [1][2]. I started the thread because I
> > wanted to get the ball rolling as early as possible, and with people that
> > won't attend the PTG and/or the Forum, to weigh in on not only the known
> > issues with cross-cell migration but also the things I'm
On Tue, Aug 28, 2018 at 03:26:02PM -0500, Matt Riedemann wrote:
> I hereby nominate Melanie Witt for nova stable core. Mel has shown that she
> knows the stable branch policy and is also an active reviewer of nova stable
> changes.
>
> +1/-1 comes from the stable-maint-core team [1] and then
On Fri, Aug 24, 2018 at 04:20:21PM -0500, Matt Riedemann wrote:
> On 8/20/2018 10:29 AM, Matthew Booth wrote:
> > Secondly, is there any reason why we shouldn't just document then you
> > have to delete snapshots before doing a volume migration? Hopefully
> > some cinder folks or operators can
>
> After some prompting from gibi, that code has now been adjusted so
> that requirements.txt and tox.ini [1] make sure that the extract
> placement branch is installed into the test virtualenvs. So in the
> gate the unit and functional tests pass. Other jobs do not because
> of [1].
>
> In the
See below for links to a release job failure for python-jenkins.
This was a ReadTheDocs publishing job. It appears to have failed due to the
necessary steps missing from this earlier post:
http://lists.openstack.org/pipermail/openstack-dev/2018-August/132836.html
- Forwarded message from
> >
> > We are still missing releases for the following tempest plugins. Some are
> > pending getting pypi and release jobs set up, but please try to prioritize
> > getting these done as soon as possible.
> >
> > barbican-tempest-plugin
> > blazar-tempest-plugin
> >
> >
> > We are still missing releases for the following tempest plugins. Some are
> > pending getting pypi and release jobs set up, but please try to prioritize
> > getting these done as soon as possible.
> >
> > barbican-tempest-plugin
> > blazar-tempest-plugin
> >
r 10-14
Cycle trailing Rocky release: November 28
--
Sean McGinnis (smcginnis)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > >
> > > I've approved it for a UC only bump
> > >
>
> We are still waiting on https://review.openstack.org/594541 to merge,
> but I already voted and noted that it was FFE approved.
>
> --
> Matthew Thode (prometheanfire)
And I have now approved the u-c update. We should be all set now.
On Wed, Aug 22, 2018 at 08:23:41PM -0500, Matt Riedemann wrote:
> Hi everyone,
>
> I have started an etherpad for cells topics at the Stein PTG [1]. The main
> issue in there right now is dealing with cross-cell cold migration in nova.
>
> At a high level, I am going off these requirements:
>
>
>
> The solution is conceptually simple. We add a new API microversion in
> Cinder that adds and optional parameter called "generic_keep_source"
> (defaults to False) to both migrate and retype operations.
>
> This means that if the driver optimized migration cannot do the
> migration and the
On Fri, Aug 17, 2018 at 12:47:10PM -0500, Ed Leafe wrote:
> On Aug 17, 2018, at 12:30 PM, Dan Smith wrote:
> >
> > Splitting it out to another repository within the compute umbrella (what
> > do we call it these days?) satisfies the _technical_ concern of not
> > being able to use placement
>
> Has there been a discussion on record of how use of placement by cinder
> would affect "standalone" cinder (or manila) initiatives where there is a
> desire to be able to run cinder by itself (with no-auth) or just with
> keystone (where OpenStack style multi-tenancy is desired)?
>
> Tom
On Fri, Aug 17, 2018 at 10:59:47AM -0500, Ed Leafe wrote:
> On Aug 17, 2018, at 10:51 AM, Chris Dent wrote:
> >
> > One of the questions that has come up on the etherpad is about how
> > placement should be positioned, as a project, after the extraction.
> > The options are:
> >
> > * A repo
On Fri, Aug 17, 2018 at 04:51:10PM +0100, Chris Dent wrote:
>
> [snip]
>
> One of the questions that has come up on the etherpad is about how
> placement should be positioned, as a project, after the extraction.
> The options are:
>
> * A repo within the compute project
> * Its own project,
Just reminding folks with deliverables following the cycle-with-intermediary
release model that next Thursday is the final deadline to get those out.
There are a handful of deliverables that have not done a release yet in Rocky.
If we do not get a release request from these teams we will need to
On Thu, Aug 16, 2018 at 06:24:22PM +, Jeremy Stanley wrote:
> In response to some recent but misguided proposals from well-meaning
> contributors in various projects, I've submitted a change[*] for the
> openstack-dev/cookiecutter .gitignore template inserting a comment
> which recommends
ates
--
Final RC deadline: August 23
Rocky Release: August 29
Cycle trailing RC deadline: August 30
Cycle trailing Rocky release: November 28
--
Sean McGinnis (smcginnis)
__
OpenStack Development Mailing List (not for u
On Tue, Aug 14, 2018 at 11:13:13AM -0500, Matthew Thode wrote:
> This is to warn and call out all those projects that do not have a
> stable/rocky branch yet.
>
> If you are in the folloing list your project will need to realize that
> your master is testing against the requirements/constraints
On Wed, Aug 15, 2018 at 07:52:47AM -0500, Sean McGinnis wrote:
> On Wed, Aug 15, 2018 at 09:32:45AM +0200, Artem Goncharov wrote:
> > Hi all,
> >
> > I have recently faced an interesting question: is there no backup restore
> > functionality in block-storage api v2? The
On Wed, Aug 15, 2018 at 09:32:45AM +0200, Artem Goncharov wrote:
> Hi all,
>
> I have recently faced an interesting question: is there no backup restore
> functionality in block-storage api v2? There is possibility to create
> backup, but not to restore it according to
>
On Tue, Aug 14, 2018 at 11:13:13AM -0500, Matthew Thode wrote:
> This is to warn and call out all those projects that do not have a
> stable/rocky branch yet.
>
> If you are in the folloing list your project will need to realize that
> your master is testing against the requirements/constraints
> On 08/10/2018 10:15 AM, Ade Lee wrote:
> > Hi all,
> >
> > I'd like to request a feature freeze exception to get the following
> > change in for castellan.
> >
> > https://review.openstack.org/#/c/575800/
> >
> > This extends the functionality of the vault backend to provide
> > previously
On Sun, Aug 12, 2018 at 05:41:20PM +0900, Ghanshyam Mann wrote:
> Hi All,
>
> Rocky release is few weeks away and we all agreed to release Tempest plugin
> with cycle-with-intermediary. Detail discussion are in ML [1] in case you
> missed.
>
> This is reminder to tag your project tempest
On Mon, Aug 13, 2018 at 04:50:40PM +, Fox, Kevin M wrote:
> Since the upgrade checking has not been written yet, now would be a good time
> to unify them, so you upgrade check your openstack upgrade, not status check
> nova, status check neutron, status check glance, status check cinder
We now have two cycle goals accepted for the Stein cycle. I think both are very
beneficial goals to work towards, so personally I am very happy with where we
landed on this.
The two goals, with links to their full descriptions and nitty gritty details,
can be found here:
This is a requirements FFE to raise the upper-constraints for
python-tricircleclient.
This client only has some requirements and CI changes merged, but it has not
done any releases during the rocky cycle. It is well past client lib freeze,
but as stated in our policy, we will need
This is requesting a requirements FFE to raise u-c for python-karborclient.
This client only has some requirements and CI changes merged, but it has not
done any releases during the rocky cycle. It is well past client lib freeze,
but as stated in our policy, we will need to force a final release
Resending the below since several projects using ReadTheDocs appear to have
missed this. If your project publishes docs to ReadTheDocs, please follow these
steps to avoid job failures.
On Fri, Aug 03, 2018 at 02:20:40PM +1000, Ian Wienand wrote:
> Hello,
>
> tl;dr : any projects using the
.
Thanks!
Sean
On Thu, Aug 09, 2018 at 09:58:06AM -0500, Sean McGinnis wrote:
> Development Focus
> -
>
> Teams should be working on any release critical bugs that would require
> another
> RC before the final release, and thinking about plans for Stein.
>
reate a stable/rocky branch. The release team would rather not be the ones
initiating this release.
Upcoming Deadlines & Dates
--
Final RC deadline: August 23
Rocky Release: August 29
Stein PTG: September 10-14
--
On Wed, Aug 08, 2018 at 05:15:26PM +, Sean McGinnis wrote:
> On Tue, Aug 07, 2018 at 05:27:06PM -0500, Monty Taylor wrote:
> > On 08/07/2018 05:03 PM, Akihiro Motoki wrote:
> > >Hi Cinder and API-SIG folks,
> > >
> > >During reviewing a horizon bug [0],
On Tue, Aug 07, 2018 at 05:27:06PM -0500, Monty Taylor wrote:
> On 08/07/2018 05:03 PM, Akihiro Motoki wrote:
> >Hi Cinder and API-SIG folks,
> >
> >During reviewing a horizon bug [0], I noticed the behavior of Cinder API
> >3.0 was changed.
> >Cinder introduced more strict schema validation for
> > >
> > > Previously, Cinder API like 3.0 accepts unused fields in POST requests
> > > but after [1] landed unused fields are now rejected even when Cinder API
> > > 3.0 is used.
> > > In my understanding on the microversioning, the existing behavior for
> > > older versions should be
The recent release of rally failed the docs publishing to readthedocs. This
appears to be related to the actions required below.
The failure from the job can be found here:
On Tue, Aug 07, 2018 at 03:25:39PM -0500, Sean McGinnis wrote:
> Added requirements tag to the subject since this is a requirements FFE.
>
> On Tue, Aug 07, 2018 at 11:44:04PM +0800, liu.xuefe...@zte.com.cn wrote:
> > hi, all
> >
> >
> > I'd like to request an
Added requirements tag to the subject since this is a requirements FFE.
On Tue, Aug 07, 2018 at 11:44:04PM +0800, liu.xuefe...@zte.com.cn wrote:
> hi, all
>
>
> I'd like to request an FFE to release 1.8.0(stable/rocky)
> for python-senlinclient.
>
> The CURRENT_API_VERSION has been changed to
On Mon, Aug 06, 2018 at 09:53:36AM -0500, Lance Bragstad wrote:
>
> >
>
> Morgan has been working through the migration since June, and it's been
> quite involved [0]. At one point he mentioned trying to write-up how he
> approached the migration for keystone. I understand that not every
>
>
> I didn't have time to investigate these, but at least Glance was
> affected, and a patch was sent (as well as an async patch). None of them
> has been merged yet:
>
> https://review.openstack.org/#/c/586050/
> https://review.openstack.org/#/c/586716/
>
> That'd be ok if at least there was
previous milestone deadlines and will be dropped
from the Rocky coordinated release.
If there are any questions or concerns, please respond here or get ahold of
someone from the release management team in the #openstack-release channel.
--
Sean McGinnis (smcginnis
On Fri, Aug 03, 2018 at 11:23:56AM -0500, Sean McGinnis wrote:
> -
>
More information on deadlines since we appear to have some conflicting
information documented. According to the published release schedule:
https://releases.openstack.org/rocky/schedule.html#r-final
& Dates
--
RC1 deadline: August 9
Stein PTG: September 10-14
--
Sean McGinnis (smcginnis)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-
On Thu, Aug 02, 2018 at 05:56:23PM +, Jeremy Stanley wrote:
> On 2018-08-02 10:09:48 -0500 (-0500), Sean McGinnis wrote:
> [...]
> > I was able to find part of how that is implemented in jeepyb:
> >
> > http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jee
On Thu, Aug 02, 2018 at 05:59:20PM +0200, Radomir Dopieralski wrote:
> To be honest, I don't see much point in automatically creating bugs that
> nobody is going to look at. When you implement a new feature, it's up to
> you to make it available in Horizon and CLI and wherever else, since the
>
I'm wondering if someone on the infra team can give me some pointers on how to
approach something, and looking for any general feedback as well.
Background
==
We've had things like the DocImpact tag that could be added to commit messages
that would tie into some automation to create a
> >
> > Packaging_Rpm has a late candidate (Dirk Mueller). We always have a few
> > teams per cycle that miss the election call, that would fall under that.
> >
+1 for appointing Dirk as PTL.
> > Trove had a volunteer (Dariusz Krol), but that person did not fill the
> > requirements for
On Tue, Jul 31, 2018 at 04:15:16PM -0500, Matt Riedemann wrote:
> On 7/31/2018 12:39 PM, Graham Hayes wrote:
> > I would like to nominate 2 new stable core reviewers for Designate.
> >
> > * Erik Olof Gunnar Andersson
> > * Jens Harbott (frickler)
> >
> Looks OK to me on both.
>
> --
>
>
A critical bug has been found in python-cinderclient that is impacting both
horizon and python-openstackclient (at least).
https://bugs.launchpad.net/cinder/+bug/1784703
tl;dr is, something new was added with a microversion, but support for that was
done incorrectly such that nothing less than
On Mon, Jul 30, 2018 at 12:02:50PM -0500, Ben Nemec wrote:
> According to https://bugs.launchpad.net/pbr/+bug/1742809 our github release
> tarballs don't actually work. It seems to be a github-specific issue
> because I was unable to reproduce the problem with a tarball from
>
-0500, Sean McGinnis wrote:
>
> General Information
> ---
>
> For deliverables following the cycle-with-milestones model, we are now (after
> the day I send this) past Feature Freeze. The focus should be on determining
> and fixing release-critical bugs. At thi
On Thu, Jul 26, 2018 at 02:06:01PM -0500, Matt Riedemann wrote:
> On 7/26/2018 12:00 PM, Sean McGinnis wrote:
> > I wouldn't think so. Nothing is changing with the policy, so it is still of
> > interest to see which projects are following that. I don't believe the
> > polic
>
> Only question I have is will the stable:follows-policy governance tag [1]
> also be removed?
>
> [1]
> https://governance.openstack.org/tc/reference/tags/stable_follows-policy.html
>
I wouldn't think so. Nothing is changing with the policy, so it is still of
interest to see which projects
> >
> > A good news is recently a team from Samsung R Center in Krakow, Poland
> > joined us, they're building a product on OpenStack, have done improvments
> > on Trove(internally), and now interested in contributing to the community,
> > starting by migrating the intergating tests to the tempest
ot done so, remember to file Rocky goal completion
information, as explained in:
https://governance.openstack.org/tc/goals/index.html#completing-goals
Upcoming Deadlines & Dates
--
PTL self-nomination ends: July 31
PTL election starts: August 1
RC1 deadline: August 9
--
1 - 100 of 607 matches
Mail list logo
