Hi Gordon,
I've solved this issue.
I've checked event.sample queue and it has no information.
My publishers config of event_pipeline.yaml: - notifier://?topic=alarm.all,
therefore event information are poured only into alarm queue, instead of
event queue.
After I add - notifier:// and - notifier
Thierry Carrez wrote:
> Hi stable/requirements/release folks!
>
> We are trying to organize a dinner for one of the PTG nights for people
> involved with the Stable / Release Management / Requirements teams
> (including team liaisons !)
>
> If interested please enter your availability on:
> https
Hi,
I added a slot on the calendar to get a room from 2:30-3:30PM on Tuesday in
the Macon room.[1] Let me know if anyone has any conflicts with this.
1. https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms
On Thu, Feb 16, 2017 at 8:25 AM, Vasyl Saienko
wrote:
> Hello Ironic/Neutron teams,
Hi all!
I'd like to propose a few changes based on the recent contributor activity.
I have two candidates that look very good and pass the formal barrier of 3
reviews a day on average [1].
First, Vasyl Saienko (vsaienk0). I'm pretty confident in him, his stats [2] are
high, he's doing a lot
Hi Eric,
Both looks interesting, so I'm ok for either. If I need to pick one of
them, I prefer the Aquarium.
Masahito
On 2017/02/16 8:06, Eric K wrote:
Hi all,
Here are some options (thinrichs originally suggested) we could consider
for a Friday daytime outing for those interested.
Anyone
+1 to both, thanks for your contributions Vasyl and Mario!!!
Sam
On 17/02/2017, 09:40, "Dmitry Tantsur" wrote:
Hi all!
I'd like to propose a few changes based on the recent contributor activity.
I have two candidates that look very good and pass the formal barrier of 3
Ed Leafe wrote:
> On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote:
>
>> When we signed off on the Big Tent changes we said competition
>> between projects was desirable, and that deployers and contributors
>> would make choices based on the work being done in those competing
>> projects. Basica
Hi, guys
I find that nova define VIR_DOMAIN_SHUTDOWN and VIR_DOMAIN_SHUTOFF as equal.
And the comment in source code writes
'
# The libvirt API doc says that DOMAIN_SHUTDOWN means the domain
# is being shut down. So technically the domain is still
# running. SHUTOFF is the real
On Fri, Feb 17, 2017 at 11:40 AM, Dmitry Tantsur
wrote:
> Hi all!
>
> I'd like to propose a few changes based on the recent contributor activity.
>
> I have two candidates that look very good and pass the formal barrier of 3
> reviews a day on average [1].
>
> First, Vasyl Saienko (vsaienk0). I'm
Ok, I mailed separately about each of them but I work on them at once so
hard to split.
As you know I added support for non-x86 architectures: aarch64 and
ppc64le. Also resurrected Debian support.
# A bit of background
At Linaro we work on getting AArch64 (64-bit ARM, arm64) to be present
in man
Thanks! I wonder if 1 hour is actually enough though, given the complexity of
the problem (actually three problems already proposed for discussion in the
etherpad). I'd personally double it (at least).
On 02/17/2017 10:16 AM, Kevin Benton wrote:
Hi,
I added a slot on the calendar to get a roo
W dniu 17.02.2017 o 12:47, Marcin Juszkiewicz pisze:
> As you know I added support for non-x86 architectures: aarch64 and
> ppc64le. Also resurrected Debian support.
Forgot two things:
Blueprint:
https://blueprints.launchpad.net/kolla/+spec/multiarch-and-arm64-containers
Logs: http://people.lina
On 02/17/2017 12:01 AM, Chris Dent wrote:
On Thu, 16 Feb 2017, Dan Prince wrote:
And yes. We are all OpenStack developers in a sense. We want to align
things in the technical arena. But I think you'll also find that most
people more closely associate themselves to a team within OpenStack
than t
Hello everyone,
A new release candidate for mistral for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/mistral/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formall
Hello everyone,
A new release candidate for mistral-dashboard for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/mistral-dashboard/
Unless release-critical issues are found that warrant a release
candidate respin, this candi
On 2017-02-16 18:43:29 -0800 (-0800), John Dickinson wrote:
[...]
> Second, the foundation messaging around the PTG emphasizes
> per-project developers. From https://www.openstack.org/ptg/
>
> The event is not optimized for non-contributors or people who
> can’t relate to a specific project team.
Thanks to edleafe for doing last week's resource providers and placement
update. This one will try to situate things for next week's PTG. Because of the
PTG there will be no update next week. If everything goes to plan there should
be a wealth of etherpads and some summaries which will be fur
Hello,
Our team will be attending the Atlanta PTG next week. We don't have a dedicated
session, but if you want to meet up and discuss about various Windows / Hyper-V
related features in OpenStack projects (what has been done, what's in the
pipeline, future plans, or what you'd like to see in f
Replying more to the "thread" and stream of thought than a specific message.
1) Yes, it is confusing. Rikimaru's description is more or less what I
believe.
2) Because it is confusing, I continue to use NovaClient commands instead
of OpenstackClient
I don't know what drove the creation of the Ope
Hi David:
We have not find the perfect solution to solve the fernet performance
issue, we will try the different crypt strength setting with fernet in
future.
There are multiple customers have more than 6-region cascade, how to
synchronous keystone data between these region disturbed us a lot.
The project is officially retired now.
On 02/14/2017 02:28 PM, Dmitry Tantsur wrote:
Hi everyone!
Following the discussion below, we would like to officially retire
python-wsmanclient as soon as possible. We haven't maintained it for a while, it
hasn't had any commits and releases since Aug 201
Hi Lance:
We may try cache or other setting to test fernet token in future.
Mentioned the uuid as default token, it must remind there have a big reason
to solve uuid performance issue, with the implement of pkitoken.
Openstack API using restful protocol, which built on top of Http, but these
Hi Dolph:
We made the keystone.conf same with the example.
[token]
provider = fernet
[fernet_tokens] //all configuration is default
#
# From keystone
#
# Directory containing Fernet token keys. (string value)
#key_repository = /etc/keystone/fernet-keys/
# This controls how many ke
There is no project that can stand on its own.
Even Swift need some identity management.
Thus, even if you are contributing to only one project your are still dependent
on many others. Including QA and infrastructure and so on.
While most Customers are looking on a few projects together and not
As always, if these topics interest you and you want to contribute to
the discussion, feel free to join the next meeting:
Time: Thursdays, 15:30-16:30 UTC
Place: https://bluejeans.com/4113567798/
Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
* We discussed about the s
Hi,
I have no opinion on where/when this should happen, but will be
interested to participate.
-Thomas
Tue Feb 14 2017 15:39:22 GMT+0100 (CET), Duarte Cardoso, Igor:
Hi neutron,
Me and David would like to discuss the Common Classification Framework
(CCF) (current approach based on opensta
On 2/15/2017 12:40 PM, Zane Bitter wrote:
Traditionally Heat has given current and former PTLs of the project +2
rights on stable branches for as long as they remain core reviewers.
Usually I've done that by adding them to the heat-release group.
At some point the system changed so that the revi
On Fri, Feb 17, 2017 at 4:14 PM, Matt Riedemann wrote:
> On 2/15/2017 12:40 PM, Zane Bitter wrote:
>>
>> Traditionally Heat has given current and former PTLs of the project +2
>> rights on stable branches for as long as they remain core reviewers.
>> Usually I've done that by adding them to the he
Hi Matt,
Thanks for adding Hierarchical quotas at the PTG.
Following was the spec made for Kilo.
https://review.openstack.org/#/c/129420/
best regards,
sajeesh
From: Ma
Dear L3-subteam,
Due to the PTG next week in Atlanta, we will cancel our weekly meeting on
February 23rd. We will resume normally on March 2nd.
See you in Atlanta!
__
OpenStack Development Mailing List (not for usage question
Hi All,
It is heard that Cinder faced some issues while implementing
hierarchical quotas.I would be nice if somebody from Cinder team can share the
issues , as it will be useful for the PTG next week.
Later today we will be entering the freeze period between the release
candidates and the final release next Wednesday. We have a couple
of releases in progress now for senlin and python-magnumclient, but
after those are completed we will not be releasing anything until
after the PTG.
I hope to see
The magnum team has requested a very late release of python-magnumclient
[1]. Given that the request is coming 4 weeks after the client
release deadline, the release team discussed it carefully and decided
we have 3 options:
1. approve the new release and branch from that BEFORE the final
deadl
Following Doug's suggestion in [0], I'm revising the Glance core list
before next week's PTG.
First, I'd again like to thank the following former Glance cores, who
stepped down during the Ocata cycle, for their past service to Glance:
- Sabari Murugesan
- Stuart McLaren
Second, I'd like to mentio
Hello everyone,
A new release candidate for senlin for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/senlin/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
On Fri, Feb 17, 2017 at 4:40 AM, Dmitry Tantsur wrote:
> Hi all!
>
> I'd like to propose a few changes based on the recent contributor activity.
>
> I have two candidates that look very good and pass the formal barrier of 3
> reviews a day on average [1].
>
> First, Vasyl Saienko (vsaienk0). I'm
Hi,
Thanks Dmitry for putting this up!
> I'd like to propose a few changes based on the recent contributor activity.
>
> I have two candidates that look very good and pass the formal barrier of 3
> reviews a day on average [1].
>
> First, Vasyl Saienko (vsaienk0). I'm pretty confident in him, his
Brian, thanks for revamping the rotation. I don't have any comments on
specific cores and their inactivity but I like the idea of we checking up
on the activeness of the glance community in a regular manner.
:thumbsup:
On Fri, Feb 17, 2017 at 11:19 AM, Brian Rosmaita wrote:
> Following Doug's s
+2 to all proposed -- Vasyl and Mario have been great folks to work with, and
I'm glad they're gettting core access.
Thanks for all the work over the years, Devananda, I know I learned quite a few
things working with you. Hopefully you'll be able to dedicate time to ironic
again someday. o/
On Fri, Feb 17, 2017 at 8:44 PM, Matt Riedemann wrote:
> On 2/15/2017 12:40 PM, Zane Bitter wrote:
>
>> Traditionally Heat has given current and former PTLs of the project +2
>> rights on stable branches for as long as they remain core reviewers.
>> Usually I've done that by adding them to the he
On Fri, Feb 17, 2017 at 4:19 PM, Brian Rosmaita
wrote:
> Finally, the following people are dropped from the Glance core list due
> to inactivity during Ocata. On behalf of the entire Glance team, I
> thank each of you for your past service to Glance, and hope to see you
> again as Glance contribu
-Original Message-
From: Thomas Herve
Reply: OpenStack Development Mailing List (not for usage questions)
Date: February 17, 2017 at 09:40:23
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [stable][heat] Heat stable-maint additions
> On Fr
Excerpts from 王玺源's message of 2017-02-17 14:08:30 +:
> Hi David:
>
> We have not find the perfect solution to solve the fernet performance
> issue, we will try the different crypt strength setting with fernet in
> future.
>
One important thing: did you try throwing more hardware at Keystone
On Fri, Feb 17, 2017 at 11:22 AM, Clint Byrum wrote:
> Excerpts from 王玺源's message of 2017-02-17 14:08:30 +:
> > Hi David:
> >
> > We have not find the perfect solution to solve the fernet performance
> > issue, we will try the different crypt strength setting with fernet in
> > future.
> >
>
Hello, I'm looking forward to seeing many of you next week in Atlanta.
We're going to be working on Arch-WG topics all day Tuesday, and if
you'd like to join us for that in general, please add your topic here:
https://etherpad.openstack.org/p/ptg-architecture-workgroup
I specifically want to call
On Fri, Feb 17, 2017 at 03:39:44PM +0100, Attila Darazs wrote:
> As always, if these topics interest you and you want to contribute to the
> discussion, feel free to join the next meeting:
>
> Time: Thursdays, 15:30-16:30 UTC
> Place: https://bluejeans.com/4113567798/
>
> Full minutes: https://et
The Product Work Group and the Foundation have created a new track for the
Boston Summit dedicated exclusively to project updates. We wanted to give you
some additional details so that you can speak with your PTLs at the Project
Teams Gathering and plan to update the community on your efforts.
Thank you Dmitry!
I’m +1 to all of these actions. Vasyl and Mario will be great additions. As
for Devananda, it saddens me but I agree and I hope to work with him again in
the future.
-Julia
> On Feb 17, 2017, at 4:40 AM, Dmitry Tantsur wrote:
>
> Hi all!
>
> I'd like to propose a few chan
Time flies and the PTG is going to start in a few days.
If you've been using OpenStack Health or Stackviz to debug a gate issue, or
if you're building devstack grenade and tempest plugins for your projects,
or using any other QA tool, please take a comment to share your experience
in [0], so we ca
Hi all,
I'm organizing a Neutron social event for Thursday evening in Atlanta
somewhere near the venue for dinner/drinks. If you're interested, please
reply to this email with a "+1" so I can get a general count for a
reservation.
Cheers,
Kevin Benton
_
Hi all,
I've booked us an hour slot on Tuesday from 3:30PM to 4:30PM in the Macon
room for some Nova/Neutron cross project discussions. We can use this to
discuss high-level goals and then people can make plans to meet up in
smaller groups later in the week to discuss specifics about each goal.
C
Early on in the inception of device role tagging, it was decided that
it's acceptable that the device metadata on the config drive lags
behind the metadata API, as long as it eventually catches up, for
example when the instance is rebooted and we get a chance to
regenerate the config drive.
So far
Top posting this thread because we're entering the Pike cycle. So as
we enter Pike, we are officially dropping support for Puppet 3. We
managed to not introduce any puppet 4 only requirements for the puppet
OpenStack modules during the Ocata cycle. The Ocata modules[0] are
officially the last cy
We should use this session to discuss the issues at a high-level to agree
on a direction and then we can break into smaller groups for discussion
later in the week.
On Fri, Feb 17, 2017 at 3:57 AM, Dmitry Tantsur wrote:
> Thanks! I wonder if 1 hour is actually enough though, given the complexity
Count me in.
From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Friday, February 17, 2017 11:19 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday
Hi all,
I'm organizing a Neutron social event for Thursday evening in Atlanta s
+1
--Anindita Das (irc: dasanind)
From: "Vasudevan, Swaminathan (PNB Roseville)"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, February 17, 2017 at 2:30 PM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev]
+1
On 2/17/17 2:18 PM, Kevin Benton wrote:
Hi all,
I'm organizing a Neutron social event for Thursday evening in Atlanta
somewhere near the venue for dinner/drinks. If you're interested,
please reply to this email with a "+1" so I can get a general count
for a reservation.
Cheers,
Kevin B
On Fri, Feb 17, 2017 at 5:48 PM, Ian Cordasco wrote:
> -Original Message-
> From: Thomas Herve
[snip]
>> Respecting the guidelines is totally fair, but review stats won't tell
>> you much, at least in my case: I barely do any stable reviews because
>> I don't have approve rights. In the c
+1.
On Fri, Feb 17, 2017 at 11:18 AM, Kevin Benton wrote:
> Hi all,
>
> I'm organizing a Neutron social event for Thursday evening in Atlanta
> somewhere near the venue for dinner/drinks. If you're interested, please
> reply to this email with a "+1" so I can get a general count for a
> reservati
W dniu 17.02.2017 o 13:19, Marcin Juszkiewicz pisze:
> W dniu 17.02.2017 o 12:47, Marcin Juszkiewicz pisze:
>> As you know I added support for non-x86 architectures: aarch64 and
>> ppc64le. Also resurrected Debian support.
>
> Forgot two things:
>
> Blueprint:
> https://blueprints.launchpad.net/k
Hello Everyone,
If you are in Atlanta next week and care about interop, please join us.
Schedule: https://etherpad.openstack.org/p/RefStackInteropWGAtlantaPTG
Thank you,
Egle
On 2/17/17, 3:20 PM, "Mark Voelker" wrote:
>Hi Folks,
>
>We¹re looking forward to seeing many of you in Atlanta next wee
+2
sent from phone
Darek
On Feb 17, 2017 15:33, "Ihar Hrachyshka" wrote:
> +1.
>
> On Fri, Feb 17, 2017 at 11:18 AM, Kevin Benton wrote:
> > Hi all,
> >
> > I'm organizing a Neutron social event for Thursday evening in Atlanta
> > somewhere near the venue for dinner/drinks. If you're intereste
+1
Thanks for setting this up,
Michael
From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Friday, February 17, 2017 11:19 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday
Hi all,
I'm organizing a Neutron so
We have had this discussion several times in the past for other reasons.
The reality is that some people will never deploy the metadata API, so I
feel like we need a better solution than what we have now.
However, I would consider it probably unsafe for the hypervisor to read the
current config dr
Hello!
Is everyone free Thursday at 11:20AM (right before lunch break) for 10
minutes for a group photo?
Cheers,
Kevin Benton
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@
+1
From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Friday, February 17, 2017 1:19 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday
Hi all,
I'm organizing a Neutron social event for Thursday evening in Atlanta somewhere
n
Hi all,
I¹d like to request an exception to release Congress RC2. I¹m really sorry
that we got bogged down by a tricky, critical bug that we didn¹t manage to
root cause and patch until the very last minute. I replied to Doug earlier
about it, but neglected to reply to the list.
Here¹s the release
+1 to both Vasyl and Mario.
Hopefully Deva will be able to come back again to Ironic in the future.
On Fri, Feb 17, 2017 at 10:42 AM, Julia Kreger
wrote:
> Thank you Dmitry!
>
> I’m +1 to all of these actions. Vasyl and Mario will be great additions.
> As for Devananda, it saddens me but I agre
Eric,
No worries. thanks for the heads up. +1 to the exception
-- Dims
On Fri, Feb 17, 2017 at 6:18 PM, Eric K wrote:
> Hi all,
>
> I¹d like to request an exception to release Congress RC2. I¹m really sorry
> that we got bogged down by a tricky, critical bug that we didn¹t manage to
> root caus
As I announced in our last bug team meeting, I will be stepping down
from the Bug Coordinator role. Since taking on the Bug Team Coordinator
role I was laid off from my position where I was able to focus on
upstream Openstack 100% of the time. I've had less time for upstream
Nova work in my new pos
Excerpts from Eric K's message of 2017-02-17 15:18:46 -0800:
> Hi all,
>
> I¹d like to request an exception to release Congress RC2. I¹m really sorry
> that we got bogged down by a tricky, critical bug that we didn¹t manage to
> root cause and patch until the very last minute. I replied to Doug ea
Excerpts from Michael Still's message of 2017-02-18 09:41:03 +1100:
> We have had this discussion several times in the past for other reasons.
> The reality is that some people will never deploy the metadata API, so I
> feel like we need a better solution than what we have now.
>
> However, I woul
Voting for presentations closes next Tuesday/Wednesday (TUESDAY, FEBRUARY 21
AT 11:59PM PST / WEDNESDAY, FEBRUARY 22 AT 6:59AM UTC).
If you have not already voted for sessions of interest, please do here:
https://www.openstack.org/summit/boston-2017/vote-for-speakers
Somehow this announcement e-
I've been told that the original subject of this broke some mail
clients. Hopefully this gets past their brokenness and you can all see
the content now. :)
Excerpts from Clint Byrum's message of 2017-02-17 10:16:05 -0800:
> Hello, I'm looking forward to seeing many of you next week in Atlanta.
> W
Hello everyone,
A new release candidate for congress for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/congress/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be forma
+1 :)
On Sat, Feb 18, 2017 at 4:42 AM, MCCASLAND, TREVOR wrote:
> +1
>
>
>
> *From:* Kevin Benton [mailto:ke...@benton.pub]
> *Sent:* Friday, February 17, 2017 1:19 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [neutron] - Neutron team social in Atlanta on
> Thursday
On Thu, Feb 16, 2017 at 11:24 AM, Joshua Harlow
wrote:
> Alex Schultz wrote:
>
>> On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote:
>>
>>> On Feb 16, 2017, at 10:07 AM, Doug Hellmann
>>> wrote:
>>>
>>> When we signed off on the Big Tent changes we said competition
between projects was desira
Hi all,
Thanks for the inputs. By aggregating feedback from different source, the
choice is as below:
* Barrel
* Storks
* Falcon (I am not sure this one since another team already chose Hawk)
* Dolphins
* Tiger
We will make a decision at the next team meeting.
Best regards,
Hongbin
From: Prade
+1
On Feb 17, 2017 1:22 PM, "Kevin Benton" wrote:
> Hi all,
>
> I'm organizing a Neutron social event for Thursday evening in Atlanta
> somewhere near the venue for dinner/drinks. If you're interested, please
> reply to this email with a "+1" so I can get a general count for a
> reservation.
>
>
Hello everyone,
A new release candidate for nova_powervm for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/nova-powervm/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will
Excerpts from Thomas Goirand's message of 2017-02-17 01:54:55 +0100:
> On 02/16/2017 05:55 PM, Clint Byrum wrote:
> > Excerpts from Thomas Goirand's message of 2017-02-15 13:43:46 +0100:
> >> All this to say that, unless someone wants to hire me for it (which
> >> would be the best outcome, but I f
Hey folks,
To take some load off Michal I’ve setup remote participation for day #1 of the
PTG.
Michal had suggested he might setup zoom instead of webex, however, I haven’t
seen that happen and several people have asked on IRC how remote participation
will work at the PTG. If Michal sets up r
Hey folks,
To take some load off Michal I’ve setup remote participation for day #2 of the
PTG.
Michal had suggested he might setup zoom instead of webex, however, I haven’t
seen that happen and several people have asked on IRC how remote participation
will work at the PTG. If Michal sets up r
83 matches
Mail list logo
