Hi Renat,
I was more just saying that depending on your situation it might be
better to switch to using tenacity (not that the retry decorator is
deprecated, though I wouldn't personally use it).
As you mentioned in
https://bugs.launchpad.net/oslo.service/+bug/1718635/comments/1 this
class
On 22 September 2017 at 17:21, Paul Belanger wrote:
> On Fri, Sep 22, 2017 at 02:31:20PM +, Jeremy Stanley wrote:
>> On 2017-09-22 15:04:43 +0200 (+0200), Attila Fazekas wrote:
>> > "if DevStack gets custom images prepped to make its jobs
>> > run faster, won't Triple-O, Kolla, et cetera want
On 09/22/2017 08:34 PM, Zhipeng Huang wrote:
> Hi Paul,
>
> Unfortunately I know better on this matter and it is not the matter of
> topic dispute as many people on this thread who has been disturbed and
> annoyed by the padding/trolling.
>
> So yes I'm sticking with stupid because it hurts the
Just confirmed the git history and compared the code with current Mogan
master, it is OK!, Thanks a lot for dims to help that. we will very
appreciate that Infra team can help us to replace the current Mogan master.
--
Best Regards
liusheng
2017-09-22 21:53 GMT+08:00 Zhenguo Niu :
> Hi infra,
>
On Sat, Sep 23, 2017 at 8:34 AM, Zhipeng Huang wrote:
> Hi Paul,
>
> Unfortunately I know better on this matter and it is not the matter of topic
> dispute as many people on this thread who has been disturbed and annoyed by
> the padding/trolling.
>
> So yes I'm sticking with stupid because it hur
Hi Paul,
Unfortunately I know better on this matter and it is not the matter of
topic dispute as many people on this thread who has been disturbed and
annoyed by the padding/trolling.
So yes I'm sticking with stupid because it hurts the OpenStack community as
a whole and hurts the reputation of t
On Fri, Sep 22, 2017 at 02:31:20PM +, Jeremy Stanley wrote:
> On 2017-09-22 15:04:43 +0200 (+0200), Attila Fazekas wrote:
> > "if DevStack gets custom images prepped to make its jobs
> > run faster, won't Triple-O, Kolla, et cetera want the same and where
> > do we draw that line?). "
> >
> >
On Fri, Sep 22, 2017 at 10:26:09AM +0800, Zhipeng Huang wrote:
> Let's not forget the epic fail earlier on the "contribution.rst fix" that
> almost melt down the community CI system.
>
> For any companies that are doing what Matt mentioned, please be aware that
> the dev community of the country y
A recent extreme example:
https://review.openstack.org/#/c/494981/1/specs/version0.8/active_passive_loadbalancer.rst
I would love to have a boilerplate statement I can use as a template
for things like this. I feel bad -1/-2 these as I want to encourage
involvement, but they are a drain on the sy
PDF:
http://www.openstack.org/blog/wp-content/uploads/2017/09/devdigest-20170922.pdf
HTML:
https://www.openstack.org/blog/2017/09/openstack-developer-mailing-list-digest-20170922/
# OpenStack Developer Mailing List Digest September 16-22
## Summaries
* [Technical Committee Status
update](http
Hi Doug,
Absolutely glad to help on this matter. We could take this offline first
via email or irc chat and then comes up with a solution for the broader
community to review
On Sat, Sep 23, 2017 at 2:47 AM, Doug Hellmann
wrote:
> Excerpts from Davanum Srinivas (dims)'s message of 2017-09-22 13:
On 08:50 Sep 22, Doug Hellmann wrote:
> Excerpts from Tom Barron's message of 2017-09-22 08:10:35 -0400:
> >
> > On 09/21/2017 10:21 PM, Matt Riedemann wrote:
> > > I just wanted to highlight to people that there seems to be a series of
> > > garbage patches in various projects [1] which are basic
On 15:04 Sep 22, Jeremy Stanley wrote:
> On 2017-09-22 14:50:55 + (+), Rajath Agasthya (rajagast) wrote:
> > On 9/21/17, 10:19 PM, "Jeremy Freudberg" wrote:
> > > 3) Delay spin-up of resource-intensive/long-running CI jobs
> > > until after some initial review has been added or time has
>
Hi,
this email is a courtesy message to make sure you're all aware that at the
PTG we decided to try to convert all of nova-compute to privsep for the
Queens release. This will almost certainly have an impact on out of tree
drivers, although I am hoping the fall out is minimal.
A change like this
On 11:33 Sep 21, Alexandra Settle wrote:
> > For me, a tutorial is something that teaches. So after I've gone through a
> > tutorial I would expect to have learned how installs work and would
> > just know
> > these things (with an occasional need to reference a few points) going
>
On 21:21 Sep 21, Matt Riedemann wrote:
> I just wanted to highlight to people that there seems to be a series of
> garbage patches in various projects [1] which are basically doing things
> like fixing a single typo in a code comment, or very narrowly changing http
> to https in links within docs.
Excerpts from Ildiko Vancsa's message of 2017-09-22 13:20:31 -0600:
> Hi All,
>
> Another forum we try to put emphasis on this is the Upstream Institute
> trainings we have before the Summits and on some smaller events as well.
>
> We usually try to spend some quality time on review best practic
On 22 September 2017 at 11:45, Clark Boylan wrote:
> On Fri, Sep 22, 2017, at 08:58 AM, Michał Jastrzębski wrote:
>> Another, more revolutionary (for good or ill) alternative would be to
>> move gates to run Kolla instead of DevStack. We're working towards
>> registry of images, and we support mos
Exactly. Thursday the 28th. Thanks.
On Fri, 22 Sep 2017 at 17:39 Jeremy Freudberg
wrote:
> Enjoy the time off. You've earned it.
>
> Quick note, the cancelled meeting date will actually be Thursday Sept
> *28* not 29 (which evidently coincides with Czech Statehood Day).
>
> On Fri, Sep 22, 2017 a
On Fri, Sep 22, 2017, at 01:18 PM, Attila Fazekas wrote:
> The main offenders reported by devstack does not seams to explain the
> growth visible on OpenstackHealth [1] .
> The logs also stated to disappear which does not makes easy to figure
> out.
>
>
> Which code/infra changes can be related ?
Enjoy the time off. You've earned it.
Quick note, the cancelled meeting date will actually be Thursday Sept
*28* not 29 (which evidently coincides with Czech Statehood Day).
On Fri, Sep 22, 2017 at 3:29 PM, Telles Nobrega wrote:
> Hi Saharans and interested parties,
>
> Next week I will be on PT
The main offenders reported by devstack does not seams to explain the
growth visible on OpenstackHealth [1] .
The logs also stated to disappear which does not makes easy to figure out.
Which code/infra changes can be related ?
http://status.openstack.org/openstack-health/#/test/devstack?resolut
On 17-09-22 15:07:14, Doug Hellmann wrote:
> Excerpts from Tony Breeds's message of 2017-09-21 20:20:22 -0500:
> > On Thu, Sep 21, 2017 at 12:13:23PM -0400, Doug Hellmann wrote:
> > > Excerpts from Tony Breeds's message of 2017-09-21 08:36:39 -0400:
> > > > On Wed, Sep 20, 2017 at 06:08:22PM -0400,
Hi Saharans and interested parties,
Next week I will be on PTO, I don't think pointing a temporary PTL is
necessary since we have active cores that can handle the work without a
problem.
Also, since I will on PTO and Thursday is a public holiday in Tchech
Republic I'm canceling the meeting.
Than
Hi All,
Another forum we try to put emphasis on this is the Upstream Institute
trainings we have before the Summits and on some smaller events as well.
We usually try to spend some quality time on review best practices and on
metrics as well. The aim is to make people realize that if they need
Excerpts from Tony Breeds's message of 2017-09-21 20:20:22 -0500:
> On Thu, Sep 21, 2017 at 12:13:23PM -0400, Doug Hellmann wrote:
> > Excerpts from Tony Breeds's message of 2017-09-21 08:36:39 -0400:
> > > On Wed, Sep 20, 2017 at 06:08:22PM -0400, Doug Hellmann wrote:
> > >
> > > > I like the ide
Excerpts from Davanum Srinivas (dims)'s message of 2017-09-22 13:47:06 -0400:
> Doug,
> Howard (cc'ed) already did a bunch of reaching out especially on
> wechat. We should request his help.
>
> Howard,
> Can you please help with communications and follow up?
>
> Thanks,
> Dims
Thanks, Dims and
On Fri, Sep 22, 2017, at 08:58 AM, Michał Jastrzębski wrote:
> Another, more revolutionary (for good or ill) alternative would be to
> move gates to run Kolla instead of DevStack. We're working towards
> registry of images, and we support most of openstack services now. If
> we enable mixed install
On 09/22/2017 09:26 AM, Matt Riedemann wrote:
> On 9/22/2017 7:10 AM, Tom Barron wrote:
>> FWIW I think it is better not to attribute motivation in these cases.
>> Perhaps the code submitter is trying to pad stats, but perhaps they are
>> just a new contributor trying to learn the process with a
# Contributor Portal Next Steps
## Landing Page Mock ups
* Current mock up:
https://drive.google.com/file/d/0BxMh9oiou2xMLVRvRWRFVklHa2c/view
* Limited click through mock up:
https://invis.io/CSDEZTBDJ#/252645774_Landing
## Todo
- [ ] thingee: A proposal for the *second level* of what the landing
Doug,
Howard (cc'ed) already did a bunch of reaching out especially on
wechat. We should request his help.
Howard,
Can you please help with communications and follow up?
Thanks,
Dims
On Fri, Sep 22, 2017 at 1:43 PM, Doug Hellmann wrote:
> Excerpts from Matt Riedemann's message of 2017-09-22 08:
Excerpts from Matt Riedemann's message of 2017-09-22 08:26:31 -0500:
> On 9/22/2017 7:10 AM, Tom Barron wrote:
> > FWIW I think it is better not to attribute motivation in these cases.
> > Perhaps the code submitter is trying to pad stats, but perhaps they are
> > just a new contributor trying to l
Oops hit send to early.
1) git-review shows some community guidelines
2) auto-review of known lower-quality patches
And those do relieve some reviewer burden.
On Fri, Sep 22, 2017 at 12:43 PM, Jeremy Freudberg
wrote:
> You're right. The amount of wasted reviewer time is far more
> drastic+probl
You're right. The amount of wasted reviewer time is far more
drastic+problematic then the amount of "wasted" CI resources.
My prior email did contain these suggestions:
On Fri, Sep 22, 2017 at 11:04 AM, Jeremy Stanley wrote:
> On 2017-09-22 14:50:55 + (+), Rajath Agasthya (rajagast) wro
On 22 September 2017 at 07:31, Jeremy Stanley wrote:
> On 2017-09-22 15:04:43 +0200 (+0200), Attila Fazekas wrote:
>> "if DevStack gets custom images prepped to make its jobs
>> run faster, won't Triple-O, Kolla, et cetera want the same and where
>> do we draw that line?). "
>>
>> IMHO we can try
I'd love to join you on Oct 14th, but I'm out of town.
- Qiming
On Tue, Sep 19, 2017 at 10:04:03PM +0800, YUAN RUIJIE wrote:
> Hi all,
>
> We are going to have a meetup to discuss the features and some other
> details about Senlin in Oct.
> Tentatively schedule：
> Date: 15th Oct.
>
Welcome back to our regular release countdown email. Now that the PTG is over,
we will send regular weekly countdown emails.
Development Focus
-
Hopefully the PTG last week gave everyone a jump start on Queens development.
We are only four weeks out from Queens-1. Team focus shou
On Sep 22, 2017 07:59, "Matt Riedemann" wrote:
On 9/22/2017 9:50 AM, Rajath Agasthya (rajagast) wrote:
> On 9/21/17, 10:19 PM, "Jeremy Freudberg"
> wrote:
>
> 3) Delay spin-up of resource-intensive/long-running CI jobs until after
> some
> initial review has been added or time has passed.
On 2017-09-22 14:50:55 + (+), Rajath Agasthya (rajagast) wrote:
> On 9/21/17, 10:19 PM, "Jeremy Freudberg" wrote:
> > 3) Delay spin-up of resource-intensive/long-running CI jobs
> > until after some initial review has been added or time has
> > passed. Authorized contributors, not necessar
On 9/22/2017 9:24 AM, Csatari, Gergely (Nokia - HU/Budapest) wrote:
Isn't it possible to ignore these patches in stackalytics? If the motivation is
to look better there, this would solve the problem.
That's a technical solution to a social problem. See my reply elsewhere
in this thread. How y
On 9/22/2017 9:59 AM, Matt Riedemann wrote:
Figuring out what is useless or not is probably not worth the effort
here. We already skip long running tempest dsvm jobs in certain patches,
like with docs or unit test only changes. Updating a code comment in
code isn't going to catch that.
And it
On 9/22/2017 9:50 AM, Rajath Agasthya (rajagast) wrote:
On 9/21/17, 10:19 PM, "Jeremy Freudberg" wrote:
3) Delay spin-up of resource-intensive/long-running CI jobs until after some
initial review has been added or time has passed. Authorized
contributors, not necessarily synonymous wi
On 9/21/17, 10:19 PM, "Jeremy Freudberg" wrote:
3) Delay spin-up of resource-intensive/long-running CI jobs until after some
initial review has been added or time has passed. Authorized
contributors, not necessarily synonymous with cores, can override the
delay if there's a critical p
On Fri, Sep 22, 2017 at 7:03 AM, Jay Pipes wrote:
> On 09/21/2017 11:37 PM, Joe Topjian wrote:
>
>>
>> Microversions also reared their head in the form of a long
>> discussion about how SDK developers and users are consuming
>> microversions at a very granular level. This discussion o
On 22.9.2017 15:30, Jiri Tomasek wrote:
Will it be possible to send Zaqar messages at each deployment step to make
the deployment process more interactive?
If we go the way of allowing the wrapping playbook to execute per step,
i think we could send messages to Zaqar after each step. Mistral c
On 2017-09-22 15:04:43 +0200 (+0200), Attila Fazekas wrote:
> "if DevStack gets custom images prepped to make its jobs
> run faster, won't Triple-O, Kolla, et cetera want the same and where
> do we draw that line?). "
>
> IMHO we can try to have only one big image per distribution,
> where the pac
Hi,
Isn't it possible to ignore these patches in stackalytics? If the motivation is
to look better there, this would solve the problem.
Br,
Gerg0
-Original Message-
From: Jeremy Stanley [mailto:fu...@yuggoth.org]
Sent: Friday, September 22, 2017 4:20 PM
To: OpenStack Development Mai
At Queens PTG in Denver, we worked on getting the documentation refreshed,
as well as incorporating the new format laid out by the documentation team.
To get this started, I have pushed a WIP ToC patch(1) that incorporates all
the points we discussed. Also, here is the start for the queens doc
res
On 2017-09-22 08:30:21 -0400 (-0400), Amrith Kumar wrote:
[...]
> When can we take some concrete action to stop these same kinds of
> things from coming up again and again?
Technical solutions to social problems rarely do more than increase
complexity for everyone involved. Communication, document
> -Original Message-
> From: pranab boruah [mailto:pranabjyotibor...@gmail.com]
> Sent: Friday, September 22, 2017 5:06 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Cc: Moshe Levi
> Subject: [openstack-dev] [networking-ovn] Support for direct vnic_type
>
>
Thanks Moshe for the quick reply.
I can definitely use some guidance for contributing on this( a newbie
here). Few questions:
1. Do you think this support could be added in queens release cycle? I
think blueprints submission for queens is closed right?
2. For adding this support, some changes to t
Thanks Kevin. It’s so funny!! :-)
Best regards,
Yushiro Furukawa
From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Thursday, September 21, 2017 10:16 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] team ptg photos
https://photos.app.goo.gl/Aqa51E2aVkv5b4ah1
__
Last week at the PTG someone asked me about best practices for
changing or deprecating default values for configuration options.
Unfortunately I failed to make any notes at the time and I'm
embarrassed to say that I don't remember who it was or exactly what
the use case was. If that was you, could
The ODL part is still not ready. We need to do code changes in odl to make it
work see [1] [2]
[1] https://git.opendaylight.org/gerrit/#/c/62481/
[2] https://git.opendaylight.org/gerrit/#/c/60259/
We try to make the design as generic as possible so if you have a SR-IOV NIC
that support switch
Hi infra,
In order to show respect to the original authors, we would like to replace
the current mogan master [1] with a new forked repo [2] which includes the
history of files which copied from other projects.
The detailed discussion is here: http://lists.openstack.
org/pipermail/openstack-dev/2
Thanks Sean for such a descriptive answer. It definitely helped.
>the hardware offload support for melonox nics is only supported with the
>openvswitch or odl >ml2 dirvers
[Pranab] Okay. We have the option of using ODL as the mechanism driver
too. I am building the cluster with ODL as the mechani
Thanks Sean for the suggestion, os-brick is indeed a good example for
sharing codes. Will discuss with the team to see if it's possible to move
that code into such a library.
On Fri, Sep 22, 2017 at 9:26 PM, Sean McGinnis
wrote:
> > >
> > > Luckily, since these things are part of the ABI of Nova
Hi,
From Mellanox perspective supporting direct port in OVN is in the plan.
One of the reason that we did not contribute this change to OVN was because of
that OVN support geneve tunnel and not vxlan.
(Mellanox card don't support hw-offloading of geneve).
If you want to contribute please go
Will it be possible to send Zaqar messages at each deployment step to make
the deployment process more interactive? in case of driving separate
playbooks from mistral workflow, that would be absolutely possible. As it
seems we're more keen on driving everything from wrapping ansible playbook,
is it
> >
> > Luckily, since these things are part of the ABI of Nova, they are
> > versioned in many cases, and in all have a well defined interfaces on
> > one side. Seems like it should be relatively straight forward to wrap
> > the other side of them and call it a library.
> >
> > ___
On 9/22/2017 7:10 AM, Tom Barron wrote:
FWIW I think it is better not to attribute motivation in these cases.
Perhaps the code submitter is trying to pad stats, but perhaps they are
just a new contributor trying to learn the process with a "harmless"
patch, or just a compulsive clean-upper who ha
Hi,
I request you to go through this thread :
http://lists.openstack.org/pipermail/openstack-dev/2017-September/122447.html
As Sean pointed out that Direct vnic_type is not yet supported in OVN,
while it is supported in ODL and OVS.
I wanted to know if there is any plan to add this support in OVN
On 22.9.2017 13:44, Giulio Fidente wrote:
On 09/21/2017 07:53 PM, Jiří Stránský wrote:
On 21.9.2017 18:04, Marios Andreou wrote:
On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský wrote:
[...]
That way we could run the whole thing end-to-end via
ansible-playbook, or
if needed one could execute
"if DevStack gets custom images prepped to make its jobs
run faster, won't Triple-O, Kolla, et cetera want the same and where
do we draw that line?). "
IMHO we can try to have only one big image per distribution,
where the packages are the union of the packages requested by all team,
minus the pac
On 09/21/2017 11:37 PM, Joe Topjian wrote:
Microversions also reared their head in the form of a long
discussion about how SDK developers and users are consuming
microversions at a very granular level. This discussion opened many
surprised eyes as we learned how different SDK pla
@Dims, sure, will make a formal request, thanks!
On Fri, Sep 22, 2017 at 8:45 PM, Davanum Srinivas wrote:
> @Zhenguo,
>
> Can you make a formal request via email? add "[infra]" and "[mogan]"
> tags so everyone in mogan is aware of this and the infra folks give
> their ok. Then we can ping infra
Excerpts from Tom Barron's message of 2017-09-22 08:10:35 -0400:
>
> On 09/21/2017 10:21 PM, Matt Riedemann wrote:
> > I just wanted to highlight to people that there seems to be a series of
> > garbage patches in various projects [1] which are basically doing things
> > like fixing a single typo
@Zhenguo,
Can you make a formal request via email? add "[infra]" and "[mogan]"
tags so everyone in mogan is aware of this and the infra folks give
their ok. Then we can ping infra using "infra-root" on the
#openstack-infra channel and ask them to replace.
Sounds good?
Thanks,
Dims
On Fri, Sep 2
@Dims,
Yes, I think the history is OK, do I need to ping some infra guys or if you
can help to replace the repo?
On Fri, Sep 22, 2017 at 7:22 PM, Davanum Srinivas wrote:
> @Zhenguo,
>
> Can you please confirm that the history looks good?
>
> Thanks,
> Dims
>
> On Fri, Sep 22, 2017 at 1:35 AM, Z
Thanks Matt for highlighting this (again). Please also see
http://openstack.markmail.org/thread/iaqsha7hbiitwqe2
http://markmail.org/thread/k62gcehxg6gv5ep4
http://markmail.org/thread/n753w3wljii67yug
When can we take some concrete action to stop these same kinds of things
from coming up again an
On 09/21/2017 10:21 PM, Matt Riedemann wrote:
> I just wanted to highlight to people that there seems to be a series of
> garbage patches in various projects [1] which are basically doing things
> like fixing a single typo in a code comment, or very narrowly changing
> http to https in links with
Hi Greg,
Can you revisit your policy configuration and try again?
See here:
http://git.openstack.org/cgit/openstack/magnum/plain/etc/magnum/policy.json?h=stable/newton
Cheers,
Spyros
On 22 September 2017 at 13:49, Waines, Greg wrote:
> Just another note on this ...
>
>
>
> We have
>
> ·
Update 35, after a hiatus for travel and the PTG, is playing catchup.
# Most Important
There was a great deal of discussion about many placement things at
the PTG, some near term, some very long term. The most important stuff
was that we adjusted some priorities and attitudes so that we're able
Just another note on this ...
We have
· setup a ‘magnum’ domain, and
· setup a ‘trustee_domain_admin’ user within that domain, and
· gave that user and domain the admin role, and <-- actually not
100% sure about this
· referenced these items in magnum.conf
On 09/21/2017 07:53 PM, Jiří Stránský wrote:
> On 21.9.2017 18:04, Marios Andreou wrote:
>> On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský wrote:
[...]
>>> That way we could run the whole thing end-to-end via
>>> ansible-playbook, or
>>> if needed one could execute smaller bits by themselves (st
@Zhenguo,
Can you please confirm that the history looks good?
Thanks,
Dims
On Fri, Sep 22, 2017 at 1:35 AM, Zhenguo Niu wrote:
> Thanks dims, that's cool :D
>
> I'll make sure there's no new patches landed to master before replacing the
> repo.
>
> On Fri, Sep 22, 2017 at 9:53 AM, Davanum Srini
Hi!
This is the weekly update on Technical Committee initiatives. Following
feedback at the PTG, I moved the full list of all open topics to a new
wiki page. Update your bookmarks to:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
If you are working on something (or plan to work on
Hi Kaitlin, great to hear this, thank you. However I can't access document
you have referenced, 'aplweb.jhuapl.edu’s server DNS address could not be
found.'
On Thu, Sep 21, 2017 at 7:15 PM, Farr, Kaitlin M.
wrote:
> Hi everyone,
>
> I will be presenting a recap of the "Data Protection in OpenSta
It could be that too TBH I'm not sure :)
On Fri, Sep 22, 2017 at 11:02 AM, Sławomir Kapłoński
wrote:
> Isn't OVS setting MTU automatically MTU for bridge as lowest value from
> ports connected to this bridge?
>
>
> > Wiadomość napisana przez Miguel Angel Ajo Pelayo
> w dniu 22.09.2017, o godz.
Isn't OVS setting MTU automatically MTU for bridge as lowest value from ports
connected to this bridge?
> Wiadomość napisana przez Miguel Angel Ajo Pelayo w dniu
> 22.09.2017, o godz. 10:32:
>
> I believe that one of the problems is that if you set a certain MTU in an OVS
> switch, new conne
I believe that one of the problems is that if you set a certain MTU in an
OVS switch, new connected ports will be automatically assigned to such MTU
the ovs-vswitchd daemon.
On Wed, Sep 20, 2017 at 10:45 PM, Ian Wells wrote:
> Since OVS is doing L2 forwarding, you should be fine setting the MT
Thanks! :)
On Thu, Sep 21, 2017 at 3:16 AM, Kevin Benton wrote:
> https://photos.app.goo.gl/Aqa51E2aVkv5b4ah1
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.o
82 matches
Mail list logo
