Hi, all
I think backup restore and disaster recovery is one the import things in
OpenStack, And our
company(ZTE) has already integrated freezer in our production. And did some
features base on
freezer, we could push those features to community. Could you give us a
chance to take over
freezer in
Hi Miguel,
Can we put the proposed topics to this PTG etherpad directly? Or we should
first discuss it in weekly Neutron project meeting?
Please advise; then we’ll follow the process to propose the PTG topics.
Thanks,
Forrest
From: Miguel Lavalle [mailto:mig...@mlavalle.com]
Sent: Friday,
*Are you an Active User Contributor (AUC)? Well you may be and not even
know it! Historically, AUCs met the following criteria: - Organizers of
Official OpenStack User Groups: from the Groups Portal- Active members and
contributors to functional teams and/or working groups (currently also
manually
> On 3 Aug 2018, at 13:46, Tobias Urdin wrote:
>
> Kubernetes:
> * Master etcd does not start because /run/etcd does not exist
This could be an issue with etcd rpm. With Systemd, /run is an in-memory tmpfs
and is wiped on reboots.
We’ve come across a similar issue in mariadb rpm on CentOS 7:
Howdy folks,
I think I forgot to send an email to alert everyone that we have a
planning etherpad [1] for the Stein PTG where we're collecting topics of
interest for discussion at the PTG.
Please add your topics and include your nick with your topics and
comments so we know who to talk to
Based on the fact that the Searchlight team missed the Rocky release
and Stein PTL elections, I have proposed a patch to remove the
project from governance. If the project is still being actively
maintained and someone wants to take over leadership, please let
us know here in this thread or on the
Based on the fact that the Freezer team missed the Rocky release and
Stein PTL elections, I have proposed a patch to remove the project from
governance. If the project is still being actively maintained and
someone wants to take over leadership, please let us know here in this
thread or on the
+1 from me!
On Fri, Aug 3, 2018 at 12:58 PM Ben Nemec wrote:
>
> Hi,
>
> Zane has been doing some good work in oslo.service recently and I would
> like to add him to the core team. I know he's got a lot on his plate
> already, but he has taken the time to propose and review patches in
>
+1!
On Fri, Aug 3, 2018 at 12:58 PM, Ben Nemec wrote:
> Hi,
>
> Zane has been doing some good work in oslo.service recently and I would like
> to add him to the core team. I know he's got a lot on his plate already,
> but he has taken the time to propose and review patches in oslo.service and
>
On 8/3/2018 11:58 AM, Ben Nemec wrote:
Hi,
Zane has been doing some good work in oslo.service recently and I
would like to add him to the core team. I know he's got a lot on his
plate already, but he has taken the time to propose and review patches
in oslo.service and has demonstrated an
Excerpts from Ben Nemec's message of 2018-08-03 11:58:29 -0500:
> Hi,
>
> Zane has been doing some good work in oslo.service recently and I would
> like to add him to the core team. I know he's got a lot on his plate
> already, but he has taken the time to propose and review patches in
>
On 08/03/2018 12:58 PM, Ben Nemec wrote:
Hi,
Zane has been doing some good work in oslo.service recently and I would
like to add him to the core team. I know he's got a lot on his plate
already, but he has taken the time to propose and review patches in
oslo.service and has demonstrated an
Hi,
Zane has been doing some good work in oslo.service recently and I would
like to add him to the core team. I know he's got a lot on his plate
already, but he has taken the time to propose and review patches in
oslo.service and has demonstrated an understanding of the code.
Please
Today the release team reviewed the rocky deliverables and their releases done
so far this cycle. There are a few areas of concern right now.
Unreleased cycle-with-intermediary
==
There is a much longer list than we would like to see of
cycle-with-intermediary
On Fri, Aug 03, 2018 at 11:23:56AM -0500, Sean McGinnis wrote:
> -
>
More information on deadlines since we appear to have some conflicting
information documented. According to the published release schedule:
https://releases.openstack.org/rocky/schedule.html#r-finalrc
we
Development Focus
-
The Release Candidate (RC) deadline is this Thursday, the 9th. Work should be
focused on any release-critical bugs and wrapping up and remaining feature
work.
General Information
---
All cycle-with-milestones and cycle-with-intermediary
+1
On Fri, Aug 3, 2018 at 11:39 AM Steve Wilkerson
wrote:
> +1
>
> On Fri, Aug 3, 2018 at 10:05 AM, MCEUEN, MATT wrote:
>
>> OpenStack-Helm core reviewer team,
>>
>> I would like to nominate Chris Wedgwood as core review for the
>> OpenStack-Helm.
>>
>> Chris is one of the most prolific
[Adding openstack-sigs list too; apologies for the extreme
cross-posting, but I think in this case the discussion deserves wide
visibility. Happy to be corrected if there's a better way to handle
this.]
Hi James,
James Page wrote:
Hi All
tl;dr we (the original founders) have not managed to
Forrest, Manjeet,
Here you go: https://etherpad.openstack.org/p/neutron-stein-ptg
Best regards
On Wed, Aug 1, 2018 at 11:49 AM, Bhatia, Manjeet S <
manjeet.s.bha...@intel.com> wrote:
> Hi,
>
>
>
> Yes, we need to refine spec for sure, once a consensus is reached focus
> will be on
Dear Stackers,
I have started an etherpad to collect topic proposals to be discussed
during the PTG in Denver, September 10th - 14th:
https://etherpad.openstack.org/p/neutron-stein-ptg . Please feel free to
add your proposals under the "Proposed topics to be scheduled" section.
Please also sign
+1
On Fri, Aug 3, 2018 at 10:05 AM, MCEUEN, MATT wrote:
> OpenStack-Helm core reviewer team,
>
> I would like to nominate Chris Wedgwood as core review for the
> OpenStack-Helm.
>
> Chris is one of the most prolific reviewers in the OSH community, but more
> importantly is a very thorough and
> I'm of two minds here.
>
> On the one hand, you have the case where the end user has accidentally
> requested some combination of things that isn't normally available, and
> they need to be able to ask the provider what they did wrong. I agree
> that this case is not really an exception, those
OpenStack-Helm core reviewer team,
I would like to nominate Chris Wedgwood as core review for the OpenStack-Helm.
Chris is one of the most prolific reviewers in the OSH community, but more
importantly is a very thorough and helpful reviewer. Many of my most
insightful reviews are thanks to
Hello Ling,
thank you for answering, I'm glad to see that Trio2o project will be
revived in the near future.
Meanwhile it would be nice to know what approach people use to deploy
multi-site openstack.
I mean, I've read somewhere about solutions using something like a
multi-site heat, but I
On Thu, Aug 2, 2018 at 11:32 PM, Cédric Jeanneret wrote:
>
>
> On 08/02/2018 11:41 PM, Steve Baker wrote:
>>
>>
>> On 02/08/18 13:03, Alex Schultz wrote:
>>> On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya
>>> wrote:
On 7/6/18 7:02 PM, Ben Nemec wrote:
>
>
> On 07/05/2018 01:23
On Tue, Jul 10, 2018 at 03:16:14PM -0400, Matthew Treinish wrote:
> On Tue, Jul 10, 2018 at 10:16:37AM +0100, Chris Dent wrote:
> > On Mon, 9 Jul 2018, Matthew Treinish wrote:
> >
> > > It's definitely a bug, and likely a bug in stestr (or one of the lower
> > > level
> > > packages like
On 08/02/2018 06:27 PM, Jay Pipes wrote:
On 08/02/2018 06:18 PM, Michael Glasgow wrote:
More generally, any time a service fails to deliver a resource which it is
primarily designed to deliver, it seems to me at this stage that should
probably be taken a bit more seriously than just "check
HTML: https://anticdent.org/placement-update-18-31.html
This is placement update 18-31, a weekly update of ongoing development
related to the [OpenStack](https://www.openstack.org/) [placement
service](https://developer.openstack.org/api-ref/placement/).
# Most Important
We are a week past
# Keystone Team Update - Week of 30 July 2018
## News
This week was relatively quiet, but we're working towards RC1 as our
next deadline.
## Recently Merged Changes
Search query: https://bit.ly/2IACk3F
We merged 20 changes this week.
Mainly changes to continue moving APIs to flask and we
Hello,
I'm testing around with Magnum and have so far only had issues.
I've tried deploying Docker Swarm (on Fedora Atomic 27, Fedora Atomic
28) and Kubernetes (on Fedora Atomic 27) and haven't been able to get it
working.
Running Queens, is there any information about supported images? Is
fwiw this appears to be due to a bug in nova. I've raised
https://bugs.launchpad.net/nova/+bug/1785235 and proposed a fix
https://review.openstack.org/588520
On Thu, Aug 2, 2018 at 5:47 PM Liam Young wrote:
> Hi,
>
> I have a fresh pike deployment and the guests are not getting metadata. To
>
Same.
On 3 August 2018 at 13:15, Renat Akhmerov wrote:
> Dougal, the policy looks good for me. I gave it the second +2 but didn’t
> approve yet so that others could also review (e.g. Adriano and Vitalii).
>
> Thanks
>
> Renat Akhmerov
> @Nokia
> On 3 Aug 2018, 16:46 +0700, Dougal Matthews ,
Dougal, the policy looks good for me. I gave it the second +2 but didn’t
approve yet so that others could also review (e.g. Adriano and Vitalii).
Thanks
Renat Akhmerov
@Nokia
On 3 Aug 2018, 16:46 +0700, Dougal Matthews , wrote:
> > On 9 July 2018 at 16:13, Dougal Matthews wrote:
> > > Hey
Lingxian, and any time welcome back as an active contributor if you wish! :) I
want to thank you for all contribution and achievements you made for our
project!
Renat Akhmerov
@Nokia
On 3 Aug 2018, 17:14 +0700, Lingxian Kong , wrote:
> +1 for me, i am still watching mistral :-)
>
> Cheers,
>
Hi Masahito,
Thank you very much for leading the Blazar project successfully! We
wouldn't have accomplished so much without your dedication.
Pierre
On 31 July 2018 at 11:58, Masahito MUROI wrote:
> Hi Blazar folks,
>
> I just want to announce that I'm not running the PTL for the Stein cycle. I
+1
On Thu, Aug 2, 2018 at 7:45 AM, Marios Andreou wrote:
> +1 !
>
>
>
> On Wed, Aug 1, 2018 at 2:31 PM, Giulio Fidente wrote:
>>
>> Hi,
>>
>> I would like to propose Lukas Bezdicka core on TripleO.
>>
>> Lukas did a lot work in our tripleoclient, tripleo-common and
>> tripleo-heat-templates
+1 for me, i am still watching mistral :-)
Cheers,
Lingxian Kong
On Fri, Aug 3, 2018 at 9:58 PM Dougal Matthews wrote:
> Hey,
>
> As we are approaching the end of Rocky I am doing some house keeping.
>
> The people below have been removed from the Mistral core team due to
> reviewing
Hey,
As we are approaching the end of Rocky I am doing some house keeping.
The people below have been removed from the Mistral core team due to
reviewing inactivity in the last 180 days[1]. I would like to thank them
for their contributions and they are welcome to re-join the Mistral core
team
On 9 July 2018 at 16:13, Dougal Matthews wrote:
> Hey folks,
>
> I'd like to propose that we start abandoning old Gerrit reviews.
>
> This report shows how stale and out of date some of the reviews are:
> http://stackalytics.com/report/reviews/mistral-group/open
>
> I would like to initially
Hi Jimmy,
thanks for announcement. Great stuff! It looks really great and it's
easy to navigate. I think a special thanks goes to Sebastian for
designing the pages. One small remark: have you tried text-align:
justify? I think it would be a little bit more readable, like a science
paper
Hi Jeffrey,
Thank you for your works as a PTL in OpenStack-kolla.
You were always friendly, Helpful and always a ready to approach guy
Thank you for all the help and support.
Thanks
Goutham Pratapa.
On Fri, Aug 3, 2018 at 1:10 PM, Ha Quang, Duong
wrote:
> Hi Jeffrey,
>
> Thank you for your
Hi Jeffrey,
Thank you for your works as PTL in Rocky cycle and release liaison from many
cycle ago (at least I joined Kolla community, you are already release liaison).
Hope that we still see you around then.
Regards,
Duong
> From: Jeffrey Zhang [mailto:zhang.lei@gmail.com]
> Sent:
42 matches
Mail list logo
