Huge +1 from me. Miguel has been doing an excellent job chairing the
l3-subteam meetings for a long time now. Well deserved!
On 12/16/16, 11:00 AM, "Rossella Sblendido" wrote:
>well deserved, +1!
>
>On 12/16/2016 09:32 AM, Miguel Angel Ajo Pelayo wrote:
>> +1 :)
>>
>> On
I appreciate that even libvirt 2.0.0 will be ancient history by now, to its
developers, but I am seeing further issues that look associated with the
recent CentOS 7 transition from libvirt 1.2.7 to libvirt 2.0.0, and would
appreciate any comments on them that people may have. I believe these
Another thought/query about this: is the libvirt transition from 1.2.7 to
2.0.0 less than usually conservative for an RHEL/CentOS series, and if so,
is there a wider reason or move there that it would help to be aware of?
Also is there a way of continuing to use CentOS 7 as a platform but still
hi,
we're trying to address in TripleO a couple of use cases for which we'd
like to trigger a Mistral workflow from a Heat template.
One example where this would be useful is the creation of the Swift
rings, which need some data related to the Heat stack (like the list of
Swift nodes and
Hi Anirudh,
Please try out the suggestion as per our IRC chat and post your
experience
Thanks.,
Mohankumar.N
On Thu, Dec 15, 2016 at 3:56 PM, Anirudh Gupta
wrote:
> Hi Mohan,
>
>
>
> Yes, we are getting timeout messages in q-agt logs.
>
>
>
> We have
Hi all,
At this moment we have a couple of services that need to consume
connections from a message queue on the client side.
This raised change requests to fix the issue with different approaches.
Those change requests have several implications on Kolla's overall
architecture and security,
On 07/12/16 14:29 +0100, Thierry Carrez wrote:
Dolph Mathews wrote:
[...]
I think it honestly reflects our current breakdown of contributors &
collaboration. The artificial scarcity model only helps a vocal minority
with cross-project focus, and just results in odd meeting times for the
On Fri, Dec 16, 2016 at 02:03:10PM +0100, Thomas Herve wrote:
> On Fri, Dec 16, 2016 at 1:17 PM, Giulio Fidente wrote:
> > hi,
> >
> > we're trying to address in TripleO a couple of use cases for which we'd like
> > to trigger a Mistral workflow from a Heat template.
> >
> >
Armando M. wrote:
Hi neutrinos,
Miguel Lavalle has been driving the project forward consistently and
reliably. I would like to propose him to be entrusted with +2/+A rights
in the areas he's been most prolific, which are L3 and DHCP.
At the same time, I'd like to
Minutes:
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-12-16-07.59.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-12-16-07.59.txt
Log:
Le 16/12/2016 03:53, Matt Riedemann a écrit :
> A few of us have talked about writing a command to tell when you're
> ready to upgrade (restart services with new code) for Ocata because we
> have a few things landing in Ocata which are going from optional to
> required, namely cells v2 and the
Armando M. wrote:
Hi neutrinos,
I would like to propose Ryan and Nate as the go-to fellows for
service-related patches.
Both are core in their repos of focus, namely neutron-dynamic-routing and
neutron-fwaas, and have a good understanding of the service framework,
+1 :)
On Fri, Dec 16, 2016 at 2:44 AM, Vasudevan, Swaminathan (PNB Roseville) <
swaminathan.vasude...@hpe.com> wrote:
> +1
>
>
>
> *From:* Armando M. [mailto:arma...@gmail.com]
> *Sent:* Thursday, December 15, 2016 3:15 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
>
I wonder if it really makes sense to put WIP patches on the priority list.
I think it's a bit counter-productive, considering that the prioritizing of
patches was supposed to make them merge faster -- but we don't want to
merge WIP patches, do we?
On Fri, Dec 16, 2016 at 5:31 AM, Richard Jones
I think the intent is to get eyes on those patches, to prevent a 1000 line
rewrite only for a core to say “I think this is a bad idea”. So for important
patches, its probably good to get earlier feedback.
Rob
On 16 Dec 2016, at 08:13, Radomir Dopieralski
Hello Denis,
unfortunately, I don't have deep knowledge of Zun so i can speak from Glare
side only.
So Glare can serve as some kind of artifact storage for container files but
we need to define artifact structure first.
Please note that artifact is immutable after activation so once you need to
This will be the last resource provider/placement update for the
year. Except the next one at the end of the first week of January.
There's a lot of work happening related to placement, on multiple
concurrent threads.
# What Matters Most
The most important placement-related stuff right now is
Hi,
What is the expected behavior of accessing a nullable and
not set versioned object field?
See the following example code:
from oslo_versionedobjects import base
from oslo_versionedobjects import fields
@base.VersionedObjectRegistry.register
class MyObject(base.VersionedObject):
> we're trying to address in TripleO a couple of use cases for which we'd
> like to trigger a Mistral workflow from a Heat template.
>
> One example where this would be useful is the creation of the Swift
> rings, which need some data related to the Heat stack (like the list of
> Swift nodes and
On 12/16/2016 01:56 PM, Christian Schwede wrote:
we're trying to address in TripleO a couple of use cases for which we'd
like to trigger a Mistral workflow from a Heat template.
One example where this would be useful is the creation of the Swift
rings, which need some data related to the Heat
On Fri, Dec 16, 2016 at 1:17 PM, Giulio Fidente wrote:
> hi,
>
> we're trying to address in TripleO a couple of use cases for which we'd like
> to trigger a Mistral workflow from a Heat template.
>
> One example where this would be useful is the creation of the Swift rings,
>
More likely, my vote doesn’t count but I’ve seen them very actively
contributing, so +1
From: "Armando M." >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Hello L2GW devs!
I'm currently working on the RPM packaging of networking-l2gw project.
My undestanding is that depending on the config, I could use whether
OpenDaylight or the neutron-l2gw-agent as backend.
For the latter case, I'm writing a systemd unit file, but I'd love to get
the command
On 12/16/2016 3:20 AM, Sylvain Bauza wrote:
Le 16/12/2016 03:53, Matt Riedemann a écrit :
A few of us have talked about writing a command to tell when you're
ready to upgrade (restart services with new code) for Ocata because we
have a few things landing in Ocata which are going from optional
On 14/12/16 21:44 -0500, Emilien Macchi wrote:
On Wed, Dec 14, 2016 at 7:22 PM, Wesley Hayutin wrote:
On Fri, Dec 2, 2016 at 12:04 PM, Wesley Hayutin wrote:
Greetings,
I wanted to send a status update on the quickstart based containerized
compute
On 14/12/16 12:05 -0500, Doug Hellmann wrote:
Excerpts from Michał Jastrzębski's message of 2016-12-14 09:56:46 -0600:
OK, I think we had some grave misunderstandings here.
1. ad-hoc meetings *are not* and *were never meant to be* replacement
for weekly meetings. Kolla community is single
Excerpts from Zane Bitter's message of 2016-12-15 15:16:07 -0500:
> The next 'generation' of core reviewers will acquire their knowledge
> largely from discussions between the current cores. It's important to
> the long-term health of the project not to cut them off from those
> discussions,
On Fri, Dec 16, 2016 at 2:57 PM, Steven Hardy wrote:
> On Fri, Dec 16, 2016 at 02:03:10PM +0100, Thomas Herve wrote:
>> On Fri, Dec 16, 2016 at 1:17 PM, Giulio Fidente wrote:
>> > I was wondering if it would make sense to have a property for the existing
On 12/16/2016 07:42 AM, Balázs Gibizer wrote:
Hi,
What is the expected behavior of accessing a nullable and
not set versioned object field?
See the following example code:
from oslo_versionedobjects import base
from oslo_versionedobjects import fields
@base.VersionedObjectRegistry.register
+1 for Miguel, he's been doing a great job :)
On 12/15/2016 06:14 PM, Armando M. wrote:
Hi neutrinos,
Miguel Lavalle has been driving the project forward consistently and reliably. I
would like to propose him to be entrusted with +2/+A rights in the areas he's
been most prolific, which are L3
+1
On 12/15/2016 06:58 PM, Armando M. wrote:
Hi neutrinos,
I would like to propose Ryan and Nate as the go-to fellows for service-related
patches.
Both are core in their repos of focus, namely neutron-dynamic-routing and
neutron-fwaas, and have a good understanding of the service framework,
- Original Message -
> From: "Neil Jerram"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Friday, December 16, 2016 6:40:57 AM
> Subject: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0
>> NotImplementedError: Cannot load 'nullable_string' in the base class
>>
>> Is this the correct behavior?
>
> Yes, that's the expected behaviour.
Yes.
>> Then what is the expected behavior if the field is also defaulted to
>> None?
>>
>> fields = {
>> 'nullable_string':
Excerpts from Michał Jastrzębski's message of 2016-12-15 14:57:10 -0600:
> I will defend this thing as something what we needed at the time.
> Sometimes heated up video discussion helps to resolve
> misunderstandings which otherwise could grow up and become conflicts
> in community, which would
+1 for both of them
On Thu, Dec 15, 2016 at 5:58 PM, Armando M. wrote:
> Hi neutrinos,
>
> I would like to propose Ryan and Nate as the go-to fellows for
> service-related patches.
>
> Both are core in their repos of focus, namely neutron-dynamic-routing and
> neutron-fwaas,
Most of the release team will be on PTO the week of 26-30 Dec, so
there are not likely to be any releases performed that week. Please
plan accordingly.
Doug
__
OpenStack Development Mailing List (not for usage questions)
On Fri, Dec 16, 2016 at 4:08 PM Steve Gordon wrote:
> - Original Message -
> > From: "Neil Jerram"
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> > Sent: Friday, December 16, 2016
Awesome! Well done Miguel! +1
Edgar
From: "Armando M."
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Thursday, December 15, 2016 at 3:14 PM
To: "OpenStack Development Mailing List (not for usage
Hi Everyone,
In the last IRC meeting [1], the RefStack team had decided to cancel the
next two meetings in 2016. The next meeting will be held on January 3,
2017.
Happy Holidays!
[1]
http://eavesdrop.openstack.org/meetings/refstack/2016/refstack.2016-12-13-19.00.log.txt
Catherine Diep
On 2016-12-16 13:58:58 +1100 (+1100), Tony Breeds wrote:
[...]
> Due to a failure in the release pipline [1] some of the release
> jobs haven't been done.
[...]
> [1]
> http://lists.openstack.org/pipermail/release-job-failures/2016-December/000324.html
[...]
The failure looks an awful lot like
portdirect +1
srwilkers +1
Great to have these gents on the team.
Serguei
-Original Message-
From: Fox, Kevin M [mailto:kevin@pnnl.gov]
Sent: Wednesday, December 14, 2016 2:49 PM
To: OpenStack Development Mailing List (not for usage questions)
Excerpts from joehuang's message of 2016-12-16 01:03:03 +:
> Hello, Doug,
>
> This is great. One question about the branch patches. In the past, when a new
> branch was created, we often have to update the devstack plugin to pull the
> code from correct branch. So if self-service branch
+1!
On Fri, 2016-12-16 at 00:58 +0100, Armando M. wrote:
> Hi neutrinos,
>
> I would like to propose Ryan and Nate as the go-to fellows for
> service-related patches.
>
> Both are core in their repos of focus, namely neutron-dynamic-routing
> and neutron-fwaas, and have a good understanding of
+1!
On Fri, 2016-12-16 at 00:14 +0100, Armando M. wrote:
> Hi neutrinos,
>
> Miguel Lavalle has been driving the project forward consistently and
> reliably. I would like to propose him to be entrusted with +2/+A
> rights in the areas he's been most prolific, which are L3 and DHCP.
>
> At the
We had good movement in the Glance priority list this past week, with
most items being resolved. Good work, everyone! Here's what we're
focusing on now:
(1) Patch to enable better request-id tracking:
https://review.openstack.org/#/c/352892/
This has been sitting on the list for a few weeks and
On 12/15/2016 09:00 AM, Matt Riedemann wrote:
On 12/15/2016 3:11 AM, Andrey Volkov wrote:
Hi,
I totally agree with Matt than `os-quota-class-sets` is inconsistent.
It has that hardcoded default class can't be changed.
API call is documented neither Nova nor Cinder (has the same API for
Checking name: Vedams DotHillDriver CI
last seen: 2016-02-20 02:24:48 (300 days, 15:04:30 old)
last success: 2016-02-17 20:46:49 (302 days, 20:41:26 old)
success rate: 83%
Per Cinder's non-compliance policy [1] this patch [2] marks
the driver as unsupported and deprecated and it will be
approved
Checking name: CloudByte CI
last seen: 2016-09-27 11:49:45 (80 days, 5:38:50 old)
last success: 2016-09-27 11:49:45 (80 days, 5:38:30 old)
success rate: 72%
Per Cinder's non-compliance policy [1] this patch [2] marks
the driver as unsupported and deprecated and it will be
approved if the issue
Hi API working group,
I am from the Zun team and I wanted to consult with you about the API design.
Our team was discussing what is the best API design for exposing different
container operations [1]. There are two proposed options:
1. Expose multiple URLs for individual container operation.
On 12/12/2016 5:40 PM, Nick Chase wrote:
OK, so if you were putting together New Year's Resolutions for OpenStack
development for 2017, what would they be?
Nova will create <= 1 new database in 2017!
--
Thanks,
Matt Riedemann
On 12/16/2016 2:20 PM, Jay Pipes wrote:
For problems with placing data like this as configuration options, see
the hassle we went through in making the allocation_ratio options into
fields stored in the DB...
Better long-term to have all this kind of configuration live in a data
store (not a
On Fri, Dec 16, 2016 at 4:40 PM, Ben Nemec wrote:
> Just a heads up for everyone, I've added some DB cleanup jobs to rh1 which
> will hopefully prevent the performance degradations over time that we've
> been seeing in that environment. Specifically, the crontab now looks
Checking name: Nexenta Edge CI
last seen: 2016-12-16 17:24:40 (0:08:08 old)
last success: 2016-11-23 10:54:16 (23 days, 6:33:59 old)
success rate: 34%
Per Cinder's non-compliance policy [1] this patch [2] marks
the driver as unsupported and deprecated and it will be
approved if the issue is not
Checking name: Tintri CI
last seen: 2016-12-16 16:50:50 (0:43:36 old)
last success: 2016-11-16 20:42:29 (29 days, 20:45:46 old)
success rate: 19%
Per Cinder's non-compliance policy [1] this patch [2] marks
the driver as unsupported and deprecated and it will be
approved if the issue is not
Checking name: Huawei FusionStorage CI
last seen: 2016-09-30 08:36:22 (77 days, 8:53:56 old)
last success: 2016-09-30 08:36:22 (77 days, 8:51:53 old)
success rate: 54%
Per Cinder's non-compliance policy [1] this patch [2] marks
the driver as unsupported and deprecated and it will be
approved if
Checking name: XP Cinder CI
last seen: 2016-08-16 09:34:42 (122 days, 7:56:25 old)
last success: 2016-08-09 14:39:13 (129 days, 2:49:02 old)
success rate: 32%
Per Cinder's non-compliance policy [1] this patch [2] marks
the driver as unsupported and deprecated and it will be
approved if the issue
Checking name: Synology DSM CI
last seen: 2016-12-16 06:37:25 (10:56:44 old)
last success: 2016-11-23 21:51:22 (22 days, 19:36:53 old)
success rate: 52%
Per Cinder's non-compliance policy [1] this patch [2] marks
the driver as unsupported and deprecated and it will be
approved if the issue is not
Hello Hiroyuki.
Congrats on public release. So, i'd like to clarify few things. I know that
for running ML jobs Meteos needs Spark instances and Meteos talks to Sahara
to deploy them. So, i'm not quite familiar with infrastructure drives in
Sahara, but would that make sense to work with Docker
Just a heads up for everyone, I've added some DB cleanup jobs to rh1
which will hopefully prevent the performance degradations over time that
we've been seeing in that environment. Specifically, the crontab now
looks like this:
# Clean up heat db
0 5 * * * heat-manage purge_deleted 7
#
+1 (even if I can’t vote)
From: Edgar Magana
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, December 16, 2016 at 12:46 PM
To: "OpenStack Development Mailing List (not for usage questions)"
+ srwilkers
+ portdirect
:)
On 12/14/16, 9:06 AM, "Michał Jastrzębski" wrote:
I'm happy to start nomination process for our 2 colleagues:
srwilkers and portdirect
to kolla-k8s core team!
This nomination will is open for 1 week. Kolla-k8s core team,
Hey Tony,
Could we also EOL tripleo-incubator and tripleo-image-elements
stable/icehouse please?
Thanks,
On Mon, Nov 21, 2016 at 9:35 PM, Tony Breeds wrote:
> Hi all,
> I'm late in sending this announement, but I'm glad to see several projects
> have already
+1 Good work. :)
On Fri, Dec 16, 2016 at 11:59 AM, Rossella Sblendido
wrote:
> +1
>
> On 12/16/2016 09:25 AM, Ihar Hrachyshka wrote:
> > Armando M. wrote:
> >
> >> Hi neutrinos,
> >>
> >> I would like to propose Ryan and Nate as the go-to fellows for
>
well deserved, +1!
On 12/16/2016 09:32 AM, Miguel Angel Ajo Pelayo wrote:
> +1 :)
>
> On Fri, Dec 16, 2016 at 2:44 AM, Vasudevan, Swaminathan (PNB Roseville)
> >
> wrote:
>
> +1
>
> __ __
>
> *From:*Armando
+1
On 12/16/2016 09:25 AM, Ihar Hrachyshka wrote:
> Armando M. wrote:
>
>> Hi neutrinos,
>>
>> I would like to propose Ryan and Nate as the go-to fellows for
>> service-related patches.
>>
>> Both are core in their repos of focus, namely neutron-dynamic-routing
>> and
As we discussed in today's meeting, the release team meetings for
23 Dec and 30 Dec are canceled. Our next team meeting will be 6
Jan.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
All milestone-based deliverables have been tagged with the Ocata-2
milestone tags. Thank you, liaisons, for handling the milestone so
smoothly!
Focus
-
Feature work and major refactoring should be well under way as we pass
the second milestone.
The deadline for non-client library releases
Checking name: Quobyte CI
last seen: 2016-11-18 08:23:05 (28 days, 9:10:41 old)
last success: 2016-11-18 08:23:05 (28 days, 9:05:10 old)
success rate: 35%
Per Cinder's non-compliance policy [1] this patch [2] marks
the driver as unsupported and deprecated and it will be
approved if the issue is
On 12/16/2016 04:36 PM, Matt Riedemann wrote:
On 12/16/2016 2:20 PM, Jay Pipes wrote:
For problems with placing data like this as configuration options, see
the hassle we went through in making the allocation_ratio options into
fields stored in the DB...
Better long-term to have all this kind
On 13.12.2016 19:29, Augustina Ragwitz wrote:
> Previously Markus Z. did some great work in putting together a dashboard
> we've been using for bug queue maintenance. Are there additional reports
> or visualizations of the bug queue that might be interesting or useful
> for the team? Is there some
-Original Message-
From: Michał Jastrzębski
Reply: OpenStack Development Mailing List (not for usage questions)
Date: December 15, 2016 at 14:58:48
To: OpenStack Development Mailing List (not for usage questions)
On Fri, Dec 16, 2016 at 3:35 PM Steve Gordon wrote:
>
>
> - Original Message -
> > From: "Neil Jerram"
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> > Sent: Friday, December 16, 2016
Folks,
you may have noticed the releases.openstack.org now shows the PGP
signatures of all release artifacts, example:
https://releases.openstack.org/ocata/index.html#ocata-nova
Many thanks to the Infra team to making this happen, details are here:
Seconding Doug's call.
On concrete suggestion from me is to give enough time ahead of the
video meeting so folks who are not able to participate can provide
their input via other medium for consideration during the meeting.
Folks will also be able to chime in about if the time would work or
not
- Original Message -
> From: "Neil Jerram"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Friday, December 16, 2016 10:53:02 AM
> Subject: Re: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0
75 matches
Mail list logo