+1 for both.
On Sun, Jan 15, 2017 at 9:05 AM, Irena Berezovsky
wrote:
>
>
> On Fri, Jan 13, 2017 at 6:49 PM, Antoni Segura Puimedon <
> celeb...@gmail.com> wrote:
>
>> Hi fellow kuryrs!
>>
>> We are getting close to the end of the Ocata and it is time to look back
>> and appreciate the good work
On Fri, Jan 13, 2017 at 6:49 PM, Antoni Segura Puimedon
wrote:
> Hi fellow kuryrs!
>
> We are getting close to the end of the Ocata and it is time to look back
> and appreciate the good work all the contributors did. I would like to
> thank you all for the continued dedication and participation i
Thank a lot for your great work on release management team.
Also, I would like to express my appreciation to Doug especially for
communications with I18n team.
I remember that Doug kindly came to I18n room at Austin Design Summit,
and we discussed some
release management issues for I18n team.
Thank you very much for your guide, Doug, this is the first time for Tricircle
to release as one big-tent project.
Best Regards
Chaoyi Huang (joehuang)
From: Doug Hellmann [d...@doughellmann.com]
Sent: 14 January 2017 4:00
To: openstack-dev
Subject: [open
HTML version:
https://www.openstack.org/blog/2017/01/openstack-developer-mailing-list-digest-20170113/
SuccessBot Says
===
* dims [1]: Rally running against Glance (Both Rally and Glance using py3.5).
* AJaegar [2]: docs.openstack.org is served from the new Infra file server that
is
Doug,
Thanks for your leadership and your consistent help with helping Kolla solve
how to use the release team’s tooling.
I have to say that manually tagging as we did previously as PTLs (when I was a
PTL) was pure madness. I really like what the releases team has done for
OpenStack!
Regards,
On 1/13/2017 11:15 AM, Chris Dent wrote:
Hi, more resource providers and placement information for your reading
pleasure. Things continue to move along, with plenty of stuff to
review and a new bug that someone could work on.
# What Matters Most
The main priority remains the same: Getting the
Kolla now add cell support. hope can help review.
https://review.openstack.org/#/c/418116/
On Sat, Jan 14, 2017 at 8:56 AM, Matt Riedemann
wrote:
> On 1/13/2017 2:05 PM, Matt Riedemann wrote:
>
>>
>> Documenting this is going to be a priority. We should have something up
>> for review in Nova b
Hi Ifat,
Sorry for reply too late. Please see my inline comments for your
question.
It won’t solve the general problem of two different monitors that raise the
same alarm
[yinliyin] Generally, we would only deploy one monitor for a same alarm.
It won’t solve possible conflicts
