Luo, Lujin wrote:
> Can someone be nice enough to point me to the Rocky Fast Forward Upgrading
> etherpad page?
>
> I am seeing Fast Forward Upgrading scheduled on Monday [1], but the etherpad
> for it is not listed in [2].
Indeed, the etherpad is missing, and I realize we don't have anyone
sig
Hi,
Since I'm getting some pressure from other DDs to actively remove Py2
support from my packages, I'm very much considering switching all of the
Debian packages for Queens to using exclusively Py3. I would have like
to read some opinions about this. Is it a good time for such move? I
hope it is,
On 15-02-18 02:19:48, Luo, Lujin wrote:
> Hello everyone,
>
> Can someone be nice enough to point me to the Rocky Fast Forward Upgrading
> etherpad page?
>
> I am seeing Fast Forward Upgrading scheduled on Monday [1], but the etherpad
> for it is not listed in [2].
>
> Thanks in advance.
>
>
On 15-02-18 09:28:09, Thierry Carrez wrote:
> Luo, Lujin wrote:
> > Can someone be nice enough to point me to the Rocky Fast Forward Upgrading
> > etherpad page?
> >
> > I am seeing Fast Forward Upgrading scheduled on Monday [1], but the
> > etherpad for it is not listed in [2].
>
> Indeed, the
Hi everyone,
In two weeks some of us will congregate in Dublin for the 3rd OpenStack
PTG. The event is made of several 'tracks' (organized around a specific
team or a specific theme).
Topics of discussions are loosely scheduled in those tracks, based on
the needs of the attendance. This allows to
Hi everyone,
At every PTG we have additional reservable space for extra un-scheduled
discussions, or smaller teams to take advantage of. In past PTGs we've
been using an ethercalc document to book that space.
The issue with that approach was that we were using two separate systems
and it was not
Lee Yarwood wrote:
> On 15-02-18 09:28:09, Thierry Carrez wrote:
>> Luo, Lujin wrote:
>>> Can someone be nice enough to point me to the Rocky Fast Forward Upgrading
>>> etherpad page?
>>>
>>> I am seeing Fast Forward Upgrading scheduled on Monday [1], but the
>>> etherpad for it is not listed in
Kendall Nelson wrote:
> Thank you to the electorate, to all those who voted and to all
> candidates who put their name forward for Project Team Lead (PTL) in
> this election. A healthy, open process breeds trust in our decision
> making capability thank you to all those who make this process possib
On Wed, Feb 14, 2018 at 11:16 PM, Ben Nemec wrote:
>
>
> On 02/09/2018 08:49 AM, Jiri Tomasek wrote:
>
>> *Step 2. network-environment -> NIC configs*
>>
>> Second step of network configuration is NIC config. For this
>> network-environment.yaml is used which references NIC config templates
>> wh
Hi Adam,
Sorry I forgot the link in my first email, you can find it here [1].
Best Regards,
Saad!
[1] https://etherpad.openstack.org/p/freezer-ptg-rocky
On Mon, Feb 12, 2018 at 2:51 PM, Adam Heczko wrote:
> Hello Saad, I think you missed link to the [1] etherpad.
>
> On Mon, Feb 12, 2018 at
Hi Thomas,
As noted on the patch, XenServer only has python 2 (and some versions of
XenServer even has Python 2.4) in domain0. This is code that will not run in
Debian (only in XenServer's dom0) and therefore can be ignored or removed from
the Debian package.
It's not practical to convert thes
Hi,
I would like to ask for a exception to add tooz 1.60.0 to
stable/queens. As part of the msgpack-python -> msgpack switch over we
converted all
dependencies, but the tooz release did not include the dependency
switch (not sure why, the branch point was just before the fix).
As it is a one line
Hi team,
As was discussed at the weekly meeting on December, 20th, Horizon team is
going to bump minimum Django version to the next LTS release which is 1.11.
Django 1.8 will be supported at least until April 2018 [2].
In Rocky release, we agreed to support Django 1.11 and Django 2.x as
experimen
We submitted the first implementation patch for the following blueprint
https://blueprints.launchpad.net/openstack/?searchtext=intrusive-instance-monitoring
i.e. https://review.openstack.org/#/c/534958/
The second patch will be pushed within a week time or so.
One item we would like to seek cl
Agreed!
Congratulations to all our newly elected PTLs. For past PTLs, thanks a bunch
for your service!
The election process I'm certain is very difficult to execute, and as a
community member, I'd like to thank the election officials for their work.
Cheers
-steve
On 2/15/18, 2:47 AM, "Thier
If your networking project is using neutron/neutron-lib, please read on.
SUMMARY:
If you're using neutron or neutron-lib code (for example extensions),
please ensure you import/use the respective attributes of those modules
rather than duplicate such values (str constants and such).
DETAILS:
To
Re-sending from the account I'm subscribed with.
On 02/15/2018 10:40 AM, Ben Nemec wrote:
On 02/15/2018 04:00 AM, Jiri Tomasek wrote:
With this approach, we'll create common API provided by Mistral to
generate NIC config templates which can be reused by CLI and other
clients, not TripleO UI
+1
Takashi, thanks for your contribution!
2018-02-11 4:48 GMT+02:00 Alex Xu :
> +1
>
> 2018-02-09 23:01 GMT+08:00 Matt Riedemann :
>
>> I'd like to add Takashi to the python-novaclient core team.
>>
>> python-novaclient doesn't get a ton of activity or review, but Takashi
>> has been a solid rev
Greetings OpenStack community,
Today's meeting was brief and primarily covered planning for the PTG.
Here's a quick recap.
We began by continuing to discuss the bug [8] that is the result of the
Nova API not properly including caching information in the headers of
its replies. Dmitry Tantsur
Thanks for the reply. I will take the subclass approach for now.
It will be nice if we can dynamically register additional info or even a
callback function after building a machine from a state space listing.
-LK
From: Joshua Harlow [harlo...@fastmail.c
On 2/9/2018 9:01 AM, Matt Riedemann wrote:
I'd like to add Takashi to the python-novaclient core team.
python-novaclient doesn't get a ton of activity or review, but Takashi
has been a solid reviewer and contributor to that project for quite
awhile now:
http://stackalytics.com/report/contrib
Dear all,
since it's now RC1 time, C1 we're setting up CI jobs for stable branches
and periodic-stable jobs for stable/queens.
In the past, we used to run the py27 based tempest-full integration job
(legacy-tempest-dsvm-neutron-full).
With all the effort that went into py3 support, I think it's t
\o/
Welcome to the team!
2018-02-15 19:18 GMT+02:00 Matt Riedemann :
> On 2/9/2018 9:01 AM, Matt Riedemann wrote:
>
>> I'd like to add Takashi to the python-novaclient core team.
>>
>> python-novaclient doesn't get a ton of activity or review, but Takashi
>> has been a solid reviewer and contrib
I would encourage everyone who is interested in providing input into the
Rocky planning cycle for Trove to put their ideas into the etherpad at:
https://etherpad.openstack.org/p/trove-ptg-rocky
There are a good number of topics posted already. We would welcome input
from operators as well.
We
2018-02-15 11:25 GMT+01:00 Bob Ball :
> Hi Thomas,
>
> As noted on the patch, XenServer only has python 2 (and some versions of
> XenServer even has Python 2.4) in domain0. This is code that will not run in
> Debian (only in XenServer's dom0) and therefore can be ignored or removed
> from the D
Hi,
> If this code is meant to run on Dom0, fine, then we won't package it,
> but we also have to decouple that dependency from Nova, Neutron,
> Ceilometer etc... to either
communicate directly through an API
> endpoint or a light wrapper around it.
There is already a light wrapper here - other p
Hello Everyone,
Over the last few elections, with changes to the election cycle (i.e. the
separation of PTL and TC elections not being back to back), the scripts in
place have become somewhat outdated and brittle.
A few days ago after fixing a number of candidates names in an exceptions
file[1] d
TL;DR: we would like to change the way HA is tested upstream to avoid
being hitten by evitable bugs that the CI process should discover.
Long version:
Today HA testing in upstream consist only in verifying that a three
controllers setup comes up correctly and can spawn an instance. That's
somethi
On 2018-02-15 02:09 PM, Kendall Nelson wrote:
Hello Everyone,
Over the last few elections, with changes to the election cycle (i.e. the
separation of PTL and TC elections not being back to back), the scripts in
place have become somewhat outdated and brittle.
A few days ago after fixing a numbe
On 18-02-15 09:31:19, Thomas Goirand wrote:
> Hi,
>
> Since I'm getting some pressure from other DDs to actively remove Py2
> support from my packages, I'm very much considering switching all of the
> Debian packages for Queens to using exclusively Py3. I would have like
> to read some opinions ab
On 18-02-15 15:13:59, Dirk Müller wrote:
> Hi,
>
> I would like to ask for a exception to add tooz 1.60.0 to
> stable/queens. As part of the msgpack-python -> msgpack switch over we
> converted all
> dependencies, but the tooz release did not include the dependency
> switch (not sure why, the bran
My downstream responsibilities have shifted over the last few months and it
probably comes as no surprise that I am not going to be able to be as
involved in the kolla project, including being the doc liaison. I'm having
to remove myself from that role and will also not be attending PTG. The
Kolla
On 18-02-15 13:38:45, Matthew Thode wrote:
> On 18-02-15 09:31:19, Thomas Goirand wrote:
> > Hi,
> >
> > Since I'm getting some pressure from other DDs to actively remove Py2
> > support from my packages, I'm very much considering switching all of the
> > Debian packages for Queens to using exclus
W dniu 15.02.2018 o 20:48, Kurt Taylor pisze:
> My downstream responsibilities have shifted over the last few months
> and it probably comes as no surprise that I am not going to be able
> to be as involved in the kolla project, including being the doc
> liaison. I'm having to remove myself from th
Manila sessions at the PTG are scheduled for Tuesday and Friday.
Ben Swartzlander and I worked together to distribute topics across the two
days and you can see the results here:
https://etherpad.openstack.org/p/manila-rocky-ptg
We'll of course end up shifting topics and times around as require
Hi All,
Just wondering, how can we clean up the masakari notification list or purging
all old records in the DB?
openstack notification list
returns too many old records
During semi-auto testing, I created a long list of history of records and would
like to clean it up and avoid unnecessary
Am 2018-02-15 20:09, schrieb Kendall Nelson:
Hello Everyone,
Over the last few elections, with changes to the election cycle (i.e.
the separation of PTL and TC elections not being back to back), the
scripts in place have become somewhat outdated and brittle.
[...]
3. Create separate jobs for b
On Feb 15, 2018, at 2:41 PM, Marcin Juszkiewicz
wrote:
>
>> Second, there will be 2 others from my ppc64le team getting involved
>> in Kolla, Mark Hamzy and Ed Leafe. Ed will be attending PTG and will
>> try to get a chance to meet a few of you there.
>
> Please tell him that I would like to ch
Updates!
So, we have gotten permission to do photos down on the pitch at the stadium
which is awesome!
The only issue is that we need to condense into a more dense blocks
(Tuesday afternoon or Thursday morning) so looking at the schedule we have
to move some teams. If the following teams could mo
I set Thursday 12:00-12:10 for the QA team.
Andrea Frittoli (andreaf)
On Thu, Feb 15, 2018 at 9:56 PM Kendall Nelson
wrote:
> Updates!
>
> So, we have gotten permission to do photos down on the pitch at the
> stadium which is awesome!
>
> The only issue is that we need to condense into a more d
On 2018-02-15 22:24:31 +0100 (+0100), Frank Kloeker wrote:
[...]
> There is one task with validation openstackid, which validated the given
> email address. Problem is here, translators using different email addresses
> for Zanata and it's not possible to validate the user with his name.
> Difficul
On Thu, Feb 15, 2018 at 09:56:25PM +, Kendall Nelson wrote:
> Updates!
>
> So, we have gotten permission to do photos down on the pitch at the stadium
> which is awesome!
>
> The only issue is that we need to condense into a more dense blocks
> (Tuesday afternoon or Thursday morning) so looki
On 18-02-15 21:56:25, Kendall Nelson wrote:
> Updates!
>
> So, we have gotten permission to do photos down on the pitch at the stadium
> which is awesome!
>
> The only issue is that we need to condense into a more dense blocks
> (Tuesday afternoon or Thursday morning) so looking at the schedule w
Hi all,
We’re getting the Queens Release communications ready, and I’ve seen a handful
of video demos and tutorials of new Queens features. We’d like to compile a
list of these to share with the marketing community. If you have a demo, would
you please send a link my way so we can make sure to
Dear all,
this is the first or a series of ~regular updates on the migration of
Tempest / Grenade jobs to Zuul v3 native.
The QA team together with the infra team are working on providing the
OpenStack community with a set of base Tempest / Grenade jobs that can be
used as a basis to write new C
All,
I have moved Cinder's time to the slot before lunch on Thursday. We can
just break early for lunch so it will not be a huge disruption.
Jay
On 2/15/2018 3:56 PM, Kendall Nelson wrote:
Updates!
So, we have gotten permission to do photos down on the pitch at the
stadium which is awesom
Kendall,
I updated the Neutron team slot to 12:20 - 12:30 on Thursday? Hope that is
ok
Thanks
On Thu, Feb 15, 2018 at 3:56 PM, Kendall Nelson
wrote:
> Updates!
>
> So, we have gotten permission to do photos down on the pitch at the
> stadium which is awesome!
>
> The only issue is that we need
Hi Kwan Louie,
I think you are looking for this:
https://review.openstack.org/#/c/487430/
Thank you,
Dinesh Bhor
From: Kwan, Louie
Sent: 16 February 2018 02:46:14
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [
I totally understand the concern.
I don't know if I have stressed it before, but team photos are 100%
optional. If its going to be too much of a distraction for anyone's team,
they definitely don't need to sign up.
The plan is to meet at reg, walk to the field entrance where the escort
will take
On Thu, Feb 15, 2018 at 05:28:29PM +, Andrea Frittoli wrote:
> Dear all,
>
> since it's now RC1 time, C1 we're setting up CI jobs for stable branches
> and periodic-stable jobs for stable/queens.
>
> In the past, we used to run the py27 based tempest-full integration job
> (legacy-tempest-dsv
Andrea Frittoli writes:
> Dear all,
>
> this is the first or a series of ~regular updates on the migration of
> Tempest / Grenade jobs to Zuul v3 native.
>
> The QA team together with the infra team are working on providing the
> OpenStack community with a set of base Tempest / Grenade jobs that
On Wed, Feb 14, 2018 at 01:59:29PM -0600, Matthew Thode wrote:
> On 18-02-14 13:55:53, Sean McGinnis wrote:
> > On Wed, Feb 14, 2018 at 10:09:47AM -0600, Matthew Thode wrote:
> > > Development has stalled, (since 2014). It's been forked but now would
> > > be a good time to move to a more actively
On Feb 15, 2018, at 9:43 AM, Steven Dake (stdake) wrote:
>
> The election process I'm certain is very difficult to execute, and as a
> community member, I'd like to thank the election officials for their work.
Having done it once, I can agree! Thanks for making things run so smoothly.
-- Ed L
Hi Anne,
I'm wondering if I can send a demo video for heat-dashboard which is a
new feature in Queens.
Is there any format of the video ?
Regards,
Kaz
2018-02-16 8:09 GMT+09:00 Anne Bertucio :
> Hi all,
>
> We’re getting the Queens Release communications ready, and I’ve seen a
> handful of vid
Hello everyone,
A new release candidate for glance for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/glance/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
hi,
1. i'm going to create a release and stable branch for tap-as-a-service/queens.
2. to clean up the queue before a release, i approved a bunch of
patches today without waiting for two +2s.
given the current review bandwidth, i guess we should relax the policy.
how do you think?
3. what to do
Welcome to one of the last countdown emails for Queens!
Development Focus
-
Teams should be working on release critical bugs in preparation of the final
release.
Teams attending the PTG should also be preparing for those discussions and
capturing information in the etherpads:
Hello everyone,
A new release candidate for nova for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/nova/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally rel
58 matches
Mail list logo
