Hi,
The neutron agents are implemented in such a way that key functionality is
implemented in terms of haproxy, dnsmasq, keepalived and radvd
configuration. The agents manage instances of these services but, by
design, the parent is the top-most (pid 1).
On baremetal this has the advantage that,
Hi Watchers,
As many of you asked, we have changed odd weekly meeting time from 13:00 UTC
to 08:00 UTC. We will have meeting tomorrow at 08:00 UTC on
#openstack-meeting-alt.
Don’t forget to make changes in your calendar[1] ;)
[1]: http://eavesdrop.openstack.org/#Watcher_Team_Meeting
Best
On Mon, Feb 12, 2018 at 8:47 PM, Matt Riedemann
wrote:
On 2/12/2018 11:11 AM, Balázs Gibizer wrote:
Add the user id and project id of the user initiated the instance
action to the notification
-
The bp
> Looks heat-dashboard does not have stable/queens branch yet.
> I got an indication about this from Horizon core and they are waiting for
that heat-dashboard will have it.
> (we want to drop django <= 1.10 support along with Horizon for Rocky)
> Cloud you kindly take care of this issue ?
Thanks
On Fri, 2018-02-09 at 14:39 -0800, Emilien Macchi wrote:
> On Fri, Feb 9, 2018 at 2:30 PM, James Slagle
> wrote:
> [...]
>
> > You may want to add an item for the routed ctlplane work that
> > landed
> > at the end of Queens. Afaik, that will need to be supported with
> >
Hi everyone,
The TC members selected the topics for the post-lunch presentations at
the PTG. The idea is to finish the lunch break with some light infusion
of knowledge.
Those will happen starting at 1pm in the lunch room. Discussions restart
at 1:30pm so we recommend targeting a 20-min talk +
Hi,
I have to cancel todays Neutron QoS IRC meeting.
If You have something related to QoS that You want to talk about, please catch
me on openstack-neutron irc channel.
—
Best regards
Slawek Kaplonski
sla...@kaplonski.pl
On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote:
> Hi Infra Team,
>
> I have 1 quick question on zuulv3 jobs and their migration part. From
> zuulv3 doc [1], it is clear about migrating the job definition and use
> those among cross repo pipeline etc.
>
> But I did not find clear
Hi all,
The Barbican weekly meeting has been fairly sparsely attended for a
little while now, and the most active contributors these days appear to
be in Asia.
Its time to consider moving the weekly meeting to a time when more
contributors can attend. I'm going to propose a couple times below
On Tue, Feb 13, 2018 at 3:06 PM Paul Belanger wrote:
> On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote:
> > Hi Infra Team,
> >
> > I have 1 quick question on zuulv3 jobs and their migration part. From
> > zuulv3 doc [1], it is clear about migrating the job definition
On 2018-02-13 10:08 AM, Chris Dent wrote:
>
> # PostgreSQL and Triggers
>
> Later in the [same
> day](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-02-07.log.html#t2018-02-07T17:18:56)
>
>
> there was some discussion about the state of PostgreSQL support and
>
Hi Infra Team,
I have 1 quick question on zuulv3 jobs and their migration part. From
zuulv3 doc [1], it is clear about migrating the job definition and use
those among cross repo pipeline etc.
But I did not find clear recommendation that whether project's
pipeline definition should stay in
On Tue, Feb 13, 2018 at 2:40 AM, Harald Jensås wrote:
> On Fri, 2018-02-09 at 14:39 -0800, Emilien Macchi wrote:
> > On Fri, Feb 9, 2018 at 2:30 PM, James Slagle
> > wrote:
> > [...]
> >
> > > You may want to add an item for the routed ctlplane work
Hi Eric,
glad to hear the problems are solved :)
What are your plans around integration with Monasca? Please let us know if you
have related feature requests.
Cheers
Witek
> -Original Message-
> From: Eric K [mailto:ekcs.openst...@gmail.com]
> Sent: Dienstag, 13. Februar 2018 03:59
>
HTML: https://anticdent.org/tc-report-18-07.html
A few things to report from the past week of TC interaction. Not much
in the way of opportunities to opine or editorialize.
# Goals
Still more on the topic of OpenStack wide goals. There was some robust
Dear all,
A gentle reminder for our tomorrow meeting at 15:00 UTC.
A draft of the agenda is available at line 202, you are very welcome to
add any item:
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018
Best regards,
Dimitri
On 2018-02-13 11:31 AM, gordon chung wrote:
>
>
> was there a resolution for this? iiuc, pgsql is not supported by glance
> based on:
> https://github.com/openstack/glance/commit/f268df1cbc3c356c472ace04bd4f2d4b3da6c026
>
err... nevermind. it seems
On 2/13/2018 10:31 AM, gordon chung wrote:
was there a resolution for this? iiuc, pgsql is not supported by glance
based on:
https://github.com/openstack/glance/commit/f268df1cbc3c356c472ace04bd4f2d4b3da6c026
i don't know if it was a bad commit but it seems to break any case that
tries to use
Since python 2.7 will not be maintained past 2020 [1] it is a
reasonable conjecture that downstream distributions
will drop support for python 2 between now and then, perhaps as early
as next year.
In Pike, OpenStack projects, including TripleO, added python 3 unit
tests. That effort was a
Note: this is the ninth edition of a weekly update of what happens in
TripleO.
The goal is to provide a short reading (less than 5 minutes) to learn where
we are and what we're doing.
Any contributions and feedback are welcome.
Link to the previous version:
https://github.com/openstack/automaton
Friendly state machines for python.
A few questions about automaton.
1. I would like to know can we addition parameters on on_enter or on_exit
callbacks. Right now, it seems it only allows state and triggered_event.
a. I have many FSM
Hello Kolla, Mistral & QA contributors,
Just a quick reminder that elections are closing soon, if you haven't
already you should use your right to vote and pick your favourite candidate!
You have until Feb 14, 2018 23:45 UTC.
Thanks for your time!
-Kendall Nelson(diablo_rojo)
Dear Neutrinos,
We will have our traditional PTG team dinner on Thursday March 1st at 7pm.
The place is to be defined. In the meantime, if you will attend the PTG,
please put your name in the "Attendees" section at to the top of the
etherpad (https://etherpad.openstack.org/p/neutron-ptg-rocky)
On 13 February 2018 at 14:02, Brent Eagles wrote:
> Hi,
>
> The neutron agents are implemented in such a way that key functionality is
> implemented in terms of haproxy, dnsmasq, keepalived and radvd
> configuration. The agents manage instances of these services but, by
>
On 02/13/2018 01:57 PM, Tom Barron wrote:
Since python 2.7 will not be maintained past 2020 [1] it is a reasonable
conjecture that downstream distributions
will drop support for python 2 between now and then, perhaps as early as
next year.
I'm not sure I agree. I suspect python 2 support
Following this up since we have a few bugs that need to be addressed for
RC2, all of which are tagged and targeted appropriately in Launchpad for
the stable/queens backport process [0]. All bugs have fixes in review to
both master and stable/queens [1]. I'll keep an eye on them and respond to
Hello everyone,
Last PTG the infra helproom seemed to work out for projects that knew about it.
The biggest problem seemed to be that other projects either just weren't aware
that there is/was an Infra helproom or didn't know when an appropriate time to
show up would be. We are going to try a
On Wed, Dec 13, 2017 at 7:30 AM, Michel Peterson wrote:
> Through my work in networking-odl I've found what I believe is an issue
> present in a majority of ML2 drivers. An issue I think needs awareness so
> each project can decide a course of action.
>
> The issue stems from
I'm not aware of plans for OVN to supported distributed SNAT, therefor
a networking node will still be required for the foreseeable future.
On Mon, Jan 15, 2018 at 2:18 AM, wenran xiao wrote:
> Hey all,
> I have found Network OVN will support to distributed floating ip
>
On Sat, Jan 27, 2018 at 2:57 AM, James E. Blair wrote:
> Balázs Gibizer writes:
>
>> Hi,
>>
>> I'm getting more and more confused how the zuul job hierarchy works or
>> is supposed to work.
>
> Hi!
>
> First, you (or others) may or may not have
@melanie yes Cyborg has its meeting room I think :) Room details should be
fixed this week or early next week I suppose.
So it will be 2:00pm on Tuesday, first thing of buisness after lunch :)
On Wed, Feb 14, 2018 at 7:20 AM, melanie witt wrote:
> > On Feb 12, 2018, at
> On Feb 12, 2018, at 16:06, Zhipeng Huang wrote:
>
> Let's settle on Tuesday afternoon session then, thanks a lot :)
Do we have a proposed time and place for the session already? I checked the
cyborg etherpad [1] and it looks like we’re thinking 2:00pm on Tuesday. Do we
Hi all,
In lieu of planning sessions at the PTG, let's have asynchronous
brainstorming and a sync-up telecon.
(I will still be available at the PTG for discussions).
If you're interested, please:
1. Jot down your thoughts and ideas (problems, features, use cases, etc.)
in this
On Tue, Feb 13, 2018 at 5:53 PM, Ben Nemec wrote:
>
> I guess if RDO has chosen this path then we don't have much choice.
This makes it sound like we had a choice to begin with.
We've already had a lot of discussions around the topic but we're
ultimately stuck between a
On Wed, Feb 14, 2018 at 12:34 AM, Andrea Frittoli
wrote:
>
>
> On Tue, Feb 13, 2018 at 3:06 PM Paul Belanger wrote:
>>
>> On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote:
>> > Hi Infra Team,
>> >
>> > I have 1 quick question on zuulv3 jobs
+1, I'm interested also.
2018-02-12 23:27 GMT+08:00 Eric Fried :
> I'm interested. No date/time preference so far as long as it sticks to
> Monday/Tuesday.
>
> efried
>
> On 02/12/2018 09:13 AM, Zhipeng Huang wrote:
> > Hi Nova team,
> >
> > Cyborg will have ptg sessions on
On Wed, Feb 14, 2018 at 12:06 AM, Paul Belanger wrote:
> On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote:
>> Hi Infra Team,
>>
>> I have 1 quick question on zuulv3 jobs and their migration part. From
>> zuulv3 doc [1], it is clear about migrating the job definition
Hi team,
We won't have team meetings in the next two weeks. This is because next
week is Lunar New Year and the next next week is the PTG. We will resume
the weekly team meeting at Mar 6, 2018. Please find the schedule in:
https://wiki.openstack.org/wiki/Zun#Meetings .
Happy holiday everyone!
Hi Team,
Due to Chinese new year and the approaching PTG, let's cancel this week and
next week's team meeting. But as usual we will lurk around the IRC channel
still, so if you got anything, feel free to shoot on #openstack-cyborg
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard &
On Wed, Feb 14, 2018 at 4:19 AM, Assaf Muller wrote:
> I'm not aware of plans for OVN to supported distributed SNAT, therefor
> a networking node will still be required for the foreseeable future.
>
> On Mon, Jan 15, 2018 at 2:18 AM, wenran xiao wrote:
>
2018-02-13 23:53 GMT+01:00 Ben Nemec :
>
>
> On 02/13/2018 01:57 PM, Tom Barron wrote:
>>
>> Since python 2.7 will not be maintained past 2020 [1] it is a reasonable
>> conjecture that downstream distributions
>> will drop support for python 2 between now and then, perhaps
On 02/13/2018 05:08 PM, Armando M. wrote:
On 13 February 2018 at 14:02, Brent Eagles > wrote:
Hi,
The neutron agents are implemented in such a way that key
functionality is implemented in terms of haproxy, dnsmasq,
keepalived
On 2018-02-14 01:28, Ghanshyam Mann wrote:
> On Wed, Feb 14, 2018 at 12:06 AM, Paul Belanger wrote:
>> On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote:
>>> Hi Infra Team,
>>>
>>> I have 1 quick question on zuulv3 jobs and their migration part. From
>>> zuulv3 doc [1],
As far a 1, I'd recommend just use functools.partial or make an object
with all the extra stuff u want and have that object provide a __call__
method.
As far as 2, you might have to subclass the FSM baseclass and add those
into the internal data-structure (same for 3 I think); ie this one @
Hi Ade,
Thank you for proposing this change!
I'm in China, and the second time slot works better for me.
Regards,
Jiong
> Message: 35
> Date: Tue, 13 Feb 2018 10:17:59 -0500
> From: Ade Lee
> To: "OpenStack Development Mailing List (not for usage questions)"
>
45 matches
Mail list logo