Excerpts from Chris Friesen's message of 2018-09-12 16:52:16 -0600:
> On 9/12/2018 12:04 PM, Doug Hellmann wrote:
>
> >> This came up in a Vancouver summit session (the python3 one I think).
> >> General consensus there seemed to be that we should have grenade jobs that
> >> run python2 on the
Hi,
It seems that the Nova room (Ballroom A) does not have any projection
possibilities. In the other hand the Neutron room (
Vail Meeting Room, Atrium Level) does have a projector. So I suggest to
move the demo to the Neutron room.
Cheers,
gibi
On Fri, Aug 31, 2018 at 2:29 AM, Balázs
You're welcome!
--
Kind regards,
Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
On Wed, Sep 12, 2018, 5:52 PM Matt Riedemann wrote:
> On 9/12/2018 5:32 PM, Melvin Hillsman wrote:
> > We basically spent the day focusing on two things specific to what you
> > bring up and are in
On 9/12/2018 5:32 PM, Melvin Hillsman wrote:
We basically spent the day focusing on two things specific to what you
bring up and are in agreement with you regarding action not just talk
around feedback and outreach. [1]
We wiped the agenda clean, discussed our availability (set reasonable
On 9/12/2018 5:13 PM, Jeremy Stanley wrote:
Sure, and I'm saying that instead I think the influence of TC
members_can_ be more valuable in finding and helping additional
people to do these things rather than doing it all themselves, and
it's not just about the limited number of available hours
We basically spent the day focusing on two things specific to what you
bring up and are in agreement with you regarding action not just talk
around feedback and outreach. [1]
We wiped the agenda clean, discussed our availability (set reasonable
expectations), and revisited how we can be more
On 2018-09-12 17:05:17 -0600 (-0600), Lance Bragstad wrote:
[...]
> IMHO, I think the point Matt is making here is more about ensuring
> sure we have people to do what we've agreed upon, as a community,
> as being mission critical. Enablement is imperative, but no matter
> how good we are at it,
On 2018-09-12 17:03:10 -0600 (-0600), Matt Riedemann wrote:
> On 9/12/2018 4:14 PM, Jeremy Stanley wrote:
> > I think Doug's work leading the Python 3 First effort is a great
> > example. He has helped find and enable several other goal champions
> > to collaborate on this. I appreciate the
On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > So I encourage all elected TC members to work directly with the
> > various SIGs to figure out their top issue and then work on
> > managing those deliverables across
On 9/12/2018 4:14 PM, Jeremy Stanley wrote:
I think Doug's work leading the Python 3 First effort is a great
example. He has helped find and enable several other goal champions
to collaborate on this. I appreciate the variety of other things
Doug already does with his available time and would
On 9/12/2018 3:55 PM, Jeremy Stanley wrote:
I almost agree with you. I think the OpenStack TC members should be
actively engaged in recruiting and enabling interested people in the
community to do those things, but I don't think such work should be
solely the domain of the TC and would hate to
On 9/12/2018 3:30 PM, Dan Smith wrote:
I'm just a bit worried to limit that role to the elected TC members. If
we say "it's the role of the TC to do cross-project PM in OpenStack"
then we artificially limit the number of people who would sign up to do
that kind of work. You mention Ildiko and
On 9/12/2018 12:04 PM, Doug Hellmann wrote:
This came up in a Vancouver summit session (the python3 one I think). General
consensus there seemed to be that we should have grenade jobs that run python2
on the old side and python3 on the new side and test the update from one to
another through
On 2018-09-12 16:03:12 -0600 (-0600), Zhipeng Huang wrote:
> On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> > On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> > [...]
> > > So I encourage all elected TC members to work directly with the
> > > various SIGs to figure out their
Ian has been working for a while on enabling PDF and translation
support for our documentation build job [1][2]. After exploring a
few different approaches, today at the PTG I think we were able to
agree on a plan that will let us move ahead.
The tl;dr version is that we want to add some extra
On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote:
> On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
> [...]
> > So I encourage all elected TC members to work directly with the
> > various SIGs to figure out their top issue and then work on
> > managing those deliverables across
On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote:
[...]
> So I encourage all elected TC members to work directly with the
> various SIGs to figure out their top issue and then work on
> managing those deliverables across the community because the TC is
> particularly well suited to do so
On Wed, Sep 12, 2018 at 3:30 PM Dan Smith wrote:
> > I'm just a bit worried to limit that role to the elected TC members. If
> > we say "it's the role of the TC to do cross-project PM in OpenStack"
> > then we artificially limit the number of people who would sign up to do
> > that kind of work.
> I'm just a bit worried to limit that role to the elected TC members. If
> we say "it's the role of the TC to do cross-project PM in OpenStack"
> then we artificially limit the number of people who would sign up to do
> that kind of work. You mention Ildiko and Lance: they did that line of
> work
Hello everyone,
I have set up an etherpad to collect Ops related session ideas for the
Forum at the Berlin Summit. Please suggest any topics that you would
like to see covered, and +1 existing topics you like.
https://etherpad.openstack.org/p/ops-forum-stein
Cheers,
Erik
Excerpts from Doug Hellmann's message of 2018-09-12 12:04:02 -0600:
> Excerpts from Clark Boylan's message of 2018-09-12 10:44:55 -0700:
> > On Wed, Sep 12, 2018, at 10:23 AM, Jim Rollenhagen wrote:
> > > The process of operators upgrading Python versions across their fleet came
> > > up this
On 4/09/18 5:39 PM, Ben Nemec wrote:
Would it be helpful to factor some of the common code out into an Oslo
library so projects basically just have to subclass, implement check
functions, and add them to the _upgrade_checks dict? It's not a huge
amount of code, but a bunch of it seems like it
Excerpts from Ben Nemec's message of 2018-09-12 13:51:16 -0600:
>
> On 09/04/2018 06:49 PM, Matt Riedemann wrote:
> > On 9/4/2018 6:39 PM, Ben Nemec wrote:
> >> Would it be helpful to factor some of the common code out into an Oslo
> >> library so projects basically just have to subclass,
On 09/04/2018 06:49 PM, Matt Riedemann wrote:
On 9/4/2018 6:39 PM, Ben Nemec wrote:
Would it be helpful to factor some of the common code out into an Oslo
library so projects basically just have to subclass, implement check
functions, and add them to the _upgrade_checks dict? It's not a huge
Hi team,
Some time ago we've found an issue that there is no simple way to test
Horizon plugin locally with the current version of Horizon [1], [2].
It leads to the situation when plugins developers use the latest released
Horizon version instead of the latest master during new features
So +1
Tim
From: Lance Bragstad
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, 12 September 2018 at 20:43
To: "OpenStack Development Mailing List (not for usage questions)"
, OpenStack Operators
Subject: [openstack-dev] [all] Consistent policy
The topic of having consistent policy names has popped up a few times this
week. Ultimately, if we are to move forward with this, we'll need a
convention. To help with that a little bit I started an etherpad [0] that
includes links to policy references, basic conventions *within* that
service, and
Matt Riedemann wrote:
> [...]
> I want to see the TC be more of a cross-project project management
> group, like a group of Ildikos and what she did between nova and cinder
> to get volume multi-attach done, which took persistent supervision to
> herd the cats and get it delivered. Lance is
Excerpts from Clark Boylan's message of 2018-09-12 10:44:55 -0700:
> On Wed, Sep 12, 2018, at 10:23 AM, Jim Rollenhagen wrote:
> > The process of operators upgrading Python versions across their fleet came
> > up this morning. It's fairly obvious that operators will want to do this in
> > a
We do this in Octavia. The openstack-tox-cover calls the cover
environment in tox.ini, so you can add it there.
Check out the tox.ini in the openstack/octavia project.
Michael
On Wed, Sep 12, 2018 at 7:01 AM reedip banerjee wrote:
>
> Hi All,
>
> Has anyone ever experimented with including
On Wed, Sep 12, 2018, at 10:23 AM, Jim Rollenhagen wrote:
> The process of operators upgrading Python versions across their fleet came
> up this morning. It's fairly obvious that operators will want to do this in
> a rolling fashion.
>
> Has anyone considered doing this in CI? For example,
The process of operators upgrading Python versions across their fleet came
up this morning. It's fairly obvious that operators will want to do this in
a rolling fashion.
Has anyone considered doing this in CI? For example, running multinode
grenade with python 2 on one node and python 3 on the
Hi,
Wednesday is already here so let’s meet for lunch today!
We will have a table reserved for us in the lunch room (Ballroom D), let’s meet
there so we can catch up a little before the Berlin Summit. :)
Thanks,
Ildikó
> On 2018. Sep 9., at 15:20, Ghanshyam Mann wrote:
>
> I am in for Wed
Well Public Cloud WG has prepared the ammo as you know and to discuss with
TC on Friday :)
A hundred percent with you on this matter.
On Wed, Sep 12, 2018 at 9:47 AM Matt Riedemann wrote:
> Rather than take a tangent on Kristi's candidacy thread [1], I'll bring
> this up separately.
>
> Kristi
Rather than take a tangent on Kristi's candidacy thread [1], I'll bring
this up separately.
Kristi said:
"Ultimately, this list isn’t exclusive and I’d love to hear your and
other people's opinions about what you think the I should focus on."
Well since you asked...
Some feedback I gave to
Core membership application approved, welcome aboard Felipe!
FTR; I have also gathered a off-list +1 from David Ames
On Wed, Sep 12, 2018 at 4:04 AM Alex Kavanagh
wrote:
> +1 from me too.
>
> On Wed, Sep 12, 2018 at 7:29 AM, Liam Young
> wrote:
>
>> +1 and thanks for all your contributions
This is week 5 of the "Run under Python 3 by default" goal
(https://governance.openstack.org/tc/goals/stein/python3-first.html).
== What we learned last week ==
Lance started a thread to talk about the tox_install.sh that some
projects are encountering in their stable branches.
Adding the following to neutron-sriov.yaml solved the problem
OS::TripleO::Services::NeutronSriovHostConfig:
../../puppet/services/neutron-sriov-host-config.yaml
On Wed, Sep 12, 2018 at 11:53 AM Samuel Monderer <
smonde...@vasonanetworks.com> wrote:
> Hi Saravanan,
>
> I'm using RHOSP13.
> The
Hi All,
Has anyone ever experimented with including Functional Tests with
openstack-tox-cover job?
We would like to include Functional tests in the coverage jobs and already
have a dsvm-functional job in place. However, openstack-tox-cover is , if
I am correct, an infra job which is directly
Excerpts from Shyam Biradar's message of 2018-09-12 16:51:29 +0530:
> Hi,
>
> We have a proprietary openstack plugin. We want to commit deployment
> scripts like containers and heat templates to upstream in tripleo and kolla
> project but not actual product code.
>
> Is it possible? Or How can
Yes Andreas, whatever deployment scripts we will be pushing it will be
under apache license.
[image: logo]
*Shyam Biradar* * Software Engineer | DevOps*
M +91 8600266938 | shyam.bira...@trilio.io | trilio.io
On Wed, Sep 12, 2018 at 5:24 PM, Andreas Jaeger wrote:
> On 2018-09-12 13:21, Shyam
On 2018-09-12 13:21, Shyam Biradar wrote:
Hi,
We have a proprietary openstack plugin. We want to commit deployment
scripts like containers and heat templates to upstream in tripleo and
kolla project but not actual product code.
Is it possible? Or How can we handle this case? Any thoughts
Hi,
We have a proprietary openstack plugin. We want to commit deployment
scripts like containers and heat templates to upstream in tripleo and kolla
project but not actual product code.
Is it possible? Or How can we handle this case? Any thoughts are welcome.
[image: logo]
*Shyam Biradar* *
+1 from me too.
On Wed, Sep 12, 2018 at 7:29 AM, Liam Young
wrote:
> +1 and thanks for all your contributions Felipe!
>
> On Wed, Sep 12, 2018 at 6:51 AM Chris MacNaughton <
> chris.macnaugh...@canonical.com> wrote:
>
>> +1 Felipe has been a solid contributor to the Openstack Charms for some
>>
On 11.9.2018 18:53, Alex Schultz wrote:
Thanks everyone for coming and chatting. From the meeting we've had a
few items where we can collaborate together.
Here are some specific bullet points:
- TripleO folks should feel free to propose some minor structural
changes if they make the
Hi Saravanan,
I'm using RHOSP13.
The neutron-sriov-agent.yaml is
missing "OS::TripleO::Services::NeutronSriovHostConfig"
Regards,
Samuel
On Fri, Sep 7, 2018 at 1:08 PM Saravanan KR wrote:
> Not sure which version you are using, but the service
> "OS::TripleO::Services::NeutronSriovHostConfig"
+1 and thanks for all your contributions Felipe!
On Wed, Sep 12, 2018 at 6:51 AM Chris MacNaughton <
chris.macnaugh...@canonical.com> wrote:
> +1 Felipe has been a solid contributor to the Openstack Charms for some
> time now.
>
> Chris
>
> On 11-09-18 23:07, Ryan Beisner wrote:
>
> +1 I'm
On Tue, Sep 11, 2018 at 7:29 AM, Tony Breeds
wrote:
>
> So I think we have the required reviews lined up to fix master, but they
> need votes from zuul and core teams.
>
>
Thanks a lot for the work, Tony. On the n-odl side, when the Depends-On
gets merged I'll give it a +W.
+1
I agree with you
From: Duc Truong
Date: Mon, Sep 10, 2018 at 9:59 AM
Subject: [openstack-dev][senlin] Nominations to Senlin Core Team
To:
Hi Senlin Core Team,
I would like to nominate 2 new core reviewers for Senlin:
[1] Jude Cross (jucr...@blizzard.com)
[2] Erik Olof Gunnar Andersson
49 matches
Mail list logo
