As we have more and more developer located in Asia and Europe timezone
rather
than Americas'. Current weekly meeting time is not proper. This was
discussed
at the last meeting and as a result, seems one hour earlier then now is
better
than now.
So I propose to move the weekly meeting from UTC
+1
Sorry for the long delay.
> -Original Message-
> From: Чадин Александр Сергеевич
> [mailto:ascha...@sbcloud.ru]
> Sent: Tuesday, June 5, 2018 5:27 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: [openstack-dev] [watcher] Nominating suzhengwei as
Hello Telemetry Team,
We would like to contribute a Monasca publisher to Ceilometer project [1] and
add it to the list of currently supported transports [2].
The goal of the plugin is to send Ceilometer samples to Monasca API.
I understand Gordon's concerns about adding maintenance overhead for
Option 2 for me. And the option switch to independant is IMO just fine.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
On Wed, 13 Jun 2018 05:09:03 +0900 Doug Hellmann
wrote
> I would like to create a version of the jobs that run as part of
> lib-forward-testing (legacy-tempest-dsvm-neutron-src) that works under
> python 3. I'm not sure the best way to proceed, since that's a legacy
> job.
>
>
+1
Thanks and Regards,
Aditi
IRC: adisky
-Original Message-
From: Hidekazu Nakamura [mailto:hid-nakam...@vf.jp.nec.com]
Sent: 13 June 2018 13:48
To: OpenStack Development Mailing List (not for usage questions)
Cc: Masahiko Hayashi
Subject: Re: [openstack-dev] [watcher] Nominating
Hello,
TL:DR; If you have spare cycles, join one of our interest groups!
In the Queens cycle, I have formalised the "liaisons" work, making
them an integral part of the Thursday's meeting agenda. Sadly, that
initiative didn't work, as almost no liaison worked/reported on those
meetings, and I
i just made the change as i haven't got any concerns.
welcome, kaz!
On Thu, May 31, 2018 at 2:36 PM, Takashi Yamamoto wrote:
> hi,
>
> i plan to add Kazuhiro Suzuki to tap-as-a-service-core group. [1]
> he is one of active members of the project.
> he is also the original author of
> - Drop tags, write a regular report instead that can account for the
> subtlety of each situation (ttx). One issue here is that it's obviously a
> lot more work than the current situation.
That's what I'd prefer personally.
We have a website with a nice project navigator now [1].
This is
Hi Team,
Kind reminder for the team meeting today about 30 mins later at
#openstack-cyborg .
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen
On Wed, Jun 13, 2018 at 6:49 AM, Dmitry Tantsur wrote:
> Slightly hijacking the thread to provide a status update on one of the items
> :)
Thanks for jumping in.
> The immediate plan right now is to wait for metalsmith 0.4.0 to hit the
> repositories, then start experimenting. I need to find a
Hi, Matthew
Solum removed pycryto dependency in [0]
[0]: https://review.openstack.org/#/c/574244/
--
Thanks,
Rong Zhu
On Tue, Jun 5, 2018 at 3:07 AM Matthew Thode
wrote:
> On 18-05-13 12:22:06, Matthew Thode wrote:
> > This is a reminder to the projects called out that they are using old,
Slightly hijacking the thread to provide a status update on one of the items :)
On 06/12/2018 07:04 PM, James Slagle wrote:
I wanted to provide an update on some next steps around config-download/Ansible
and TripleO. Now that we've completed transitioning to config-download by
default in Rocky,
On 06/11/2018 11:53 AM, Thierry Carrez wrote:
> Hi everyone,
>
> As some of the OpenStack deliverables get more mature, we need to adjust
> our release policies to best handle the case of deliverables that do not
> need to be updated that much. This discussion started with how to handle
> those
Hi,
On Wed, Jun 13, 2018 at 3:17 PM, James Slagle wrote:
> On Wed, Jun 13, 2018 at 6:49 AM, Dmitry Tantsur wrote:
>> Slightly hijacking the thread to provide a status update on one of the items
>> :)
>
> Thanks for jumping in.
>
>
>> The immediate plan right now is to wait for metalsmith 0.4.0
Hi all,
Apologies but have to cancel today's docs meeting due to a meeting
conflict.
Have questions for the docs team? We hang out at #openstack-doc.
Thanks,
pk
__
OpenStack Development Mailing List (not for usage
Excerpts from Ivan Kolodyazhny's message of 2018-06-13 18:01:26 +0300:
> Hi team,
>
> Last week on the Horizon meeting we discussed [1] possible options for
> Horizon release model to address current issues for plugins maintainers.
> Some background could be found here [2].
>
> The main issue is
Excerpts from Doug Hellmann's message of 2018-06-13 10:31:00 -0400:
> Excerpts from Ghanshyam's message of 2018-06-13 16:52:33 +0900:
> > On Wed, 13 Jun 2018 05:09:03 +0900 Doug Hellmann
> > wrote
> > > I would like to create a version of the jobs that run as part of
> > >
I was going through some recently reported nova bugs and came across [1]
which I opened at the Summit during one of the FFU sessions where I
realized the nova upgrade docs don't mention the nova-status upgrade
check CLI [2] (added in Ocata).
As a result, I was wondering how many deployment
On 18-06-13 20:53:06, Rong Zhu wrote:
> Hi, Matthew
>
> Solum removed pycryto dependency in [0]
>
> [0]: https://review.openstack.org/#/c/574244/
>
> --
> Thanks,
> Rong Zhu
Yep, just in time for the next reminder email too :D
>
Excerpts from Jean-Philippe Evrard's message of 2018-06-13 11:04:51 +0200:
> > - Drop tags, write a regular report instead that can account for the
> > subtlety of each situation (ttx). One issue here is that it's obviously a
> > lot more work than the current situation.
>
> That's what I'd
On 30-May-2018 08:45, Henry Nash wrote:
> Hi
>
> It is with a somewhat heavy heart that I have decided that it is time to hang
> up my keystone core status. Having been involved since the closing stages of
> Folsom, I've had a good run! When I look at how far keystone has come since
> the
> v2
On 06/13/2018 05:50 PM, Emilien Macchi wrote:
> Alan Bishop has been highly involved in the Storage backends integration
> in TripleO and Puppet modules, always here to update with new features,
> fix (nasty and untestable third-party backends) bugs and manage all the
> backports for stable
Excerpts from Ghanshyam's message of 2018-06-13 16:52:33 +0900:
> On Wed, 13 Jun 2018 05:09:03 +0900 Doug Hellmann
> wrote
> > I would like to create a version of the jobs that run as part of
> > lib-forward-testing (legacy-tempest-dsvm-neutron-src) that works under
> > python 3.
Excerpts from Matthew Thode's message of 2018-06-13 10:23:45 -0500:
> On 18-06-13 20:53:06, Rong Zhu wrote:
> > Hi, Matthew
> >
> > Solum removed pycryto dependency in [0]
> >
> > [0]: https://review.openstack.org/#/c/574244/
> >
> > --
> > Thanks,
> > Rong Zhu
>
> Yep, just in time for the
On Wed, Jun 13, 2018, 12:04 PM Marios Andreou wrote:
>
> On Wed, Jun 13, 2018 at 6:57 PM, Giulio Fidente
> wrote:
>
>> On 06/13/2018 05:50 PM, Emilien Macchi wrote:
>> > Alan Bishop has been highly involved in the Storage backends integration
>> > in TripleO and Puppet modules, always here to
Hi team,
Last week on the Horizon meeting we discussed [1] possible options for
Horizon release model to address current issues for plugins maintainers.
Some background could be found here [2].
The main issue is that we should have some stable API for plugins and be
able to release it as needed.
Alan Bishop has been highly involved in the Storage backends integration in
TripleO and Puppet modules, always here to update with new features, fix
(nasty and untestable third-party backends) bugs and manage all the
backports for stable releases:
On Wed, Jun 13, 2018 at 6:57 PM, Giulio Fidente wrote:
> On 06/13/2018 05:50 PM, Emilien Macchi wrote:
> > Alan Bishop has been highly involved in the Storage backends integration
> > in TripleO and Puppet modules, always here to update with new features,
> > fix (nasty and untestable
+1
From: John Fulton [mailto:johfu...@redhat.com]
Sent: Wednesday, June 13, 2018 11:23 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tripleo] Proposing Alan Bishop tripleo core on
storage bits
On Wed, Jun 13, 2018, 12:04 PM Marios Andreou
+1
On Wed, Jun 13, 2018 at 9:50 AM, Emilien Macchi wrote:
> Alan Bishop has been highly involved in the Storage backends integration in
> TripleO and Puppet modules, always here to update with new features, fix
> (nasty and untestable third-party backends) bugs and manage all the
> backports for
The fourth Project Teams Gathering will be held September 10-14th back at the
Renaissance Stapleton Hotel in Denver, Colorado (3801 Quebec Street, Denver,
Colorado 80207).
REGISTRATION AND HOTEL
Registration is now available here: https://denver2018ptg.eventbrite.com
On 18-06-13 13:29:54, Kendall Waters wrote:
> The fourth Project Teams Gathering will be held September 10-14th back at the
> Renaissance Stapleton Hotel in Denver, Colorado (3801 Quebec Street, Denver,
> Colorado 80207).
>
> REGISTRATION AND HOTEL
> Registration is now available here:
On 18-06-14 01:28:14, Zhang Fan wrote:
> Hi, Matthew
>
>
> Sorry for the late updates on patches. Trove team members recently are sort
> of busy with daily work. And it takes me awhile to get back focusing the
> upstream. Fortunately, we are still there, and trove is still alive :)
>
>
>
On 2018-06-13 14:11:22 -0500 (-0500), Matthew Thode wrote:
[...]
> What if we want that train experience. I feel like there will be
> something missing without it.
Sounds like it may require us to bring our own train whistles.
--
Jeremy Stanley
On 6/13/2018 3:33 PM, melanie witt wrote:
We've been experimenting with a new process this cycle, Review Runways
[1] and we're about at the middle of the cycle now as we had the r-2
milestone last week June 7.
I wanted to start a thread and gather thoughts and feedback from the
nova
Dell - Internal Use - Confidential
+1
From: Kanevsky, Arkady
Sent: Wednesday, June 13, 2018 12:52 PM
To: ful...@redhat.com; openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [tripleo] Proposing Alan Bishop tripleo core on
storage bits
+1
From: John Fulton
Excerpts from Doug Hellmann's message of 2018-06-13 12:19:18 -0400:
> Excerpts from Doug Hellmann's message of 2018-06-13 10:31:00 -0400:
> > Excerpts from Ghanshyam's message of 2018-06-13 16:52:33 +0900:
> > > On Wed, 13 Jun 2018 05:09:03 +0900 Doug Hellmann
> > > wrote
> > > > I
Howdy everyone,
We've been experimenting with a new process this cycle, Review Runways
[1] and we're about at the middle of the cycle now as we had the r-2
milestone last week June 7.
I wanted to start a thread and gather thoughts and feedback from the
nova community about how they think
Hello guys, just want to double check and make sure that this option can be
ignored if using vxlan.
NeutronNetworkVLANRanges (used in the network isolation template)
Thanks,
Remo
__
OpenStack Development Mailing List
On Thu, Jun 14, 2018 at 12:50 AM, Remo Mattei wrote:
> Hello guys, just want to double check and make sure that this option can
> be ignored if using vxlan.
>
> NeutronNetworkVLANRanges (used in the network isolation template)
>
>
Hi Remo, this parameter maps to the neutron config
On 6/7/2018 8:33 AM, Lucio Seki wrote:
Since Pike release, Cinder supports in-use volume extending [1].
By default, it assumes that every storage backend is able to perform
this operation.
Actually, by default, Tempest assumes that no backends support it, which
is why it's disabled by
Hi,
Thank you.
I'm glad to be able to support the TaaS community.
Regards,
Kaz
From: Takashi Yamamoto
Subject: Re: [openstack-dev] [tap-as-a-service] core reviewer update
Date: Wed, 13 Jun 2018 16:34:09 +0900
> i just made the change as i haven't got any concerns.
> welcome, kaz!
>
> On Thu,
Hi everybody,
Just a heads up that we have an intermittent gate failure of the
nova-cells-v1 job happening right now [1] and a revert of the tempest
change related to it has been approved [2] and will be making its way
through the gate. The nova-cells-v1 job will be failing until [2] merges.
https://review.openstack.org/575264 just landed (and didn't timeout in
check nor gate without recheck, so good sigh it helped to mitigate).
I've restore and rechecked some patches that I evacuated from the gate,
please do not restore others or recheck or approve anything for now, and
see how it
+1
Regards,
Saravanan KR
On Wed, Jun 13, 2018 at 9:20 PM, Emilien Macchi wrote:
> Alan Bishop has been highly involved in the Storage backends integration in
> TripleO and Puppet modules, always here to update with new features, fix
> (nasty and untestable third-party backends) bugs and manage
Greetings,
Please be aware the yum repo created in tripleo ci jobs is going to change
names to include the release [1]. This is done to ensure that only the
appropriate patches are installed when patches from multiple branches are
in play. This is especially important to upgrade jobs.
If you
TL;DR: gate queue was 25h+, we put all patches from gate on standby, do not
restore/recheck until further announcement.
We recently enabled the containerized undercloud for multinode jobs and we
believe this was a bit premature as the container download process wasn't
optimized so it's not
Hi, Matthew
Sorry for the late updates on patches. Trove team members recently are sort of
busy with daily work. And it takes me awhile to get back focusing the upstream.
Fortunately, we are still there, and trove is still alive :)
About removing pycryto dependency, there are two patches, as
49 matches
Mail list logo
