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,
On 10/25/2018 08:06 AM, Alexandru Sorodoc wrote:
Hello,
I'm trying to set up metering for neutron in Pike. I tested it with a
centralized router and it works, but when I try with a distributed router it
doesn't record any usage samples. I have one compute node and one
network node
and I've
Hi Mike,
Interesting - nice detective work! FWIW, I do have that explicitly set
in my config, based on the recommendation at:
https://docs.openstack.org/glance/latest/install/install-rdo.html#install-and-configure-components
Your github PR will no go anywhere - all changes must go through
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
TL;DR: glance config doesn’t honor documented default setting for
paste_deploy.flavor. Solution is to add setting to glance-api.conf. Patch to be
submitted.
After the deep debugging yesterday Jonathan did a deep compare of our Mitaka
configuration compared to Queens.
He noted that this
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
You configure an LVM volume group for each Cinder backend. A CInder
volume on that backend corresponds to an LVM volume in that volume
group. The LVM volume is exposed as an iSCSI target, usually via LIO,
but I believe this is configurable. The compute node uses /iscsiadm /to
import that volume as
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
> >> -
> >>
> >>
Hi,
How are you calculating which flows you're missing?
We thought we're missing the flow for "if you're looking for this MAC go
this way", but it turned out that what's actually missing is a bunch of
interfaces on the multicast-flow for the vlan that we're investigating.
Is that what you're
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 11:29:27 +0700 (+0700), Adhi Priharmanto wrote:
> I have setup rocky release at my openstack lab, now all of tenant
> (user) can see non-public glance image create by another tenant
> (user)
[...]
This sounds very similar to https://launchpad.net/bugs/1799588 which
the Glance team
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
I am using Rocky release and configuring for NVMe backend with LVM. Can you
please tell me how this one might flow, or redirect me to the documentation?
I have not been able to found much documentation regarding this.
--
Tushar Tyagi
t...@fastmail.com
On Fri, Oct 26, 2018, at 17:48, Bernd
Volume I/O won't flow through the controller. The LVM reference driver,
for example, sets up an iSCSI target on the storage node, which the
compute node then imports. The NFS driver has the compute node mount the
exported filesystem. Depending on the driver, I/O may even flow directly
between an
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
> -
Hello,
I have a requirement to create a multi node setup with Controller, Compute and
Storage nodes on different machines.
In case I create a virtual machine on the compute node, it's going to be
provisioned by the Controller node and the storage is going to be provided by
the Storage node.
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
23 matches
Mail list logo
