Thanks for all who participated in the discussion and/or voted. The most
votes, such as there were, went for the name 'Accelerator Requests'
abbrev. ARQs. The specs will be updated over the next couple of days.
Have a good weekend.
Best Regards,
Sundar
On 10/22/2018 11:37 AM, Nadathur,
There isn't much news this week except some of the base framework
changes being proposed to projects are getting merged which is nice to see.
https://storyboard.openstack.org/#!/story/2003657
https://review.openstack.org/#/q/topic:upgrade-checkers+status:merged
And there are a lot of patches
Just a heads up. I've been battling with some unit test issues with
the latest version of puppet 5.5. I've proposed some fixes[0][1], but
it appears that there is a larger issue with legacy functions which
affects the stable branches. I've reported the issues[2][3] upstream
to Puppetlabs, but
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 26/10/18 5:09 AM, Thomas Goirand wrote:
On 10/22/18 9:12 PM, Zane Bitter wrote:
On 22/10/18 10:33 AM, Thomas Goirand wrote:
This can only happen if we have supporting distribution packages for it.
IMO, this is a call for using Debian Testing or even Sid in the gate.
It depends on which
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 flake8 ignore this line if it happened to violate any
linting rules.
It turns out that,
We have officially moved off of the instack-undercloud deployment
process in Rocky and have officially removed it's support from
python-tripleoclient in Stein. In order to prevent confusion I have
proposed a patch to start the retirement of instack-undercloud[0]. We
will continue to support the
On 10/25/18 3:43 PM, Zane Bitter wrote:
On 25/10/18 1:38 PM, William M Edmonds wrote:
Zane Bitter wrote on 10/22/2018 03:12:46 PM:
> On 22/10/18 10:33 AM, Thomas Goirand wrote:
> > On 10/19/18 5:17 PM, Zane Bitter wrote:
> >> Integration Tests
> >> -
> >>
> >>
On 10/25/2018 02:44 PM, melanie witt wrote:
On Thu, 25 Oct 2018 14:00:08 -0400, Jay Pipes wrote:
On 10/25/2018 01:38 PM, Chris Friesen wrote:
On 10/24/2018 9:10 AM, Jay Pipes wrote:
Nova's API has the ability to create "quota classes", which are
basically limits for a set of resource types.
HTML: https://anticdent.org/placement-update-18-43.html
A placement update for you.
# Most Important
Same as last week: The major factors that need attention are
managing database migrations and associated tooling and getting the
ball rolling on properly producing documentation. More on both
On 2018-10-26 06:46:23 -0500 (-0500), Sean McGinnis wrote:
[...]
> Release failed for this due to openstackci not being properly configured
> for the pypi package upload.
If whoever "pineunity" is can add the "openstackci" account as
another maintainer for
Hi,
The Release Management team is handling release management for
deliverables from all official OpenStack teams. However, there are a
number of exceptions:
- deliverables that are not using tags or branches for their 'release',
or that are directly published (docs, specs,
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 10/22/18 9:12 PM, Zane Bitter wrote:
> On 22/10/18 10:33 AM, Thomas Goirand wrote:
>> This can only happen if we have supporting distribution packages for it.
>> IMO, this is a call for using Debian Testing or even Sid in the gate.
>
> It depends on which versions we choose to support, but if
14 matches
Mail list logo
