Weekly meeting tomorrow will be held tomorrow at the usual time10AM
EST/10PM BJ time
Planned Agenda:
1. Status updates on patches:
https://review.openstack.org/#/q/status:open%20project:openstack/cyborg
https://review.openstack.org/#/q/project:openstack/cyborg-specs
2. Berlin Summit Planning
Hi All,
TC office hour is started on #openstack-tc channel. Feel free to reach to us
for anything you want discuss/input/feedback/help from TC.
-gmann
__
OpenStack Development Mailing List (not for usage questions)
Hi Geng and team,
This is just a reminder that we are in the probation period of keeping
Freezer as an official project (deadline is Stein-2). So, we need to
release Freezer at Stein-1 this week (actually it's last week). Even though
it's not required anymore [1], we need to do this to evaluate
On Tue, Oct 30, 2018 at 11:25:02AM -0700, iain macdonnell wrote:
> I must be losing it. On what planet is "Tiny Town" a single word, and
> "Troublesome" not more than 10 characters?
Sorry for the mistake. Should either of these names win the popular
vote clearly they would not be viable.
Yours
Ian,
Great job by yourself, your mentees and last but not least your mentors!
Way to go!!!
Amy (spotz)
On Tue, Oct 30, 2018 at 9:10 AM, Ian Y. Choi wrote:
> Hello,
>
> I got involved organizing & mentoring Korean people for OpenStack upstream
> contribution for about last two months,
> and
Awesome work, Ian \m/\m/\m/
On Wed, Oct 31, 2018 at 6:19 AM Sean McGinnis wrote:
> On Tue, Oct 30, 2018 at 11:10:42PM +0900, Ian Y. Choi wrote:
> > Hello,
> >
> > I got involved organizing & mentoring Korean people for OpenStack
> upstream
> > contribution for about last two months,
> > and
Thanks :)
On Wed, Oct 31, 2018 at 4:00 AM Mohammed Naser wrote:
> Yay!
>
> Congratulations on the first Stein release, well done with your work
> in looking after Searchlight so far.
> On Tue, Oct 30, 2018 at 6:37 AM Trinh Nguyen
> wrote:
> >
> > Hi team,
> >
> > I'm doing a release for
With the discussion of CI jobs and the fact that I have been finding myself
checking job status several times a day so early in the cycle, I think it
is time for ironic to revisit many of our CI jobs.
The bottom line is ironic is very resource intensive to test. A lot of that
is because of the
On 10/30/2018 11:03 AM, Clark Boylan wrote:
If you find any of this interesting and would like to help feel free to reach
out to myself or the infra team.
I find this interesting and thanks for providing the update to the
mailing list. That's mostly what I wanted to say.
FWIW I've still
On Tue, Oct 30, 2018 at 11:10:42PM +0900, Ian Y. Choi wrote:
> Hello,
>
> I got involved organizing & mentoring Korean people for OpenStack upstream
> contribution for about last two months,
> and would like to share with community members.
>
Very cool! Thanks for organizing this Ian. And thank
d if it helps.
>
> This seems like good information to start capturing, otherwise we are
> kind of just guessing. Is there something in infra already that we could
> use or would it need to be new tooling?
Digging around in graphite we currently track mean in pipelines. This is
probably a r
On Tue, Oct 30, 2018 at 12:25 PM Clark Boylan wrote:
>
> On Tue, Oct 30, 2018, at 10:42 AM, Alex Schultz wrote:
> > On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec wrote:
> > >
> > > Tagging with tripleo since my suggestion below is specific to that
> > > project.
> > >
> > > On 10/30/18 11:03 AM,
A bit of an update here:
- We merged the patch in openstack/paunch that stop the Docker container if
we try to start a Podman container.
- We switched the undercloud upgrade job to test upgrades from Docker to
Podman (for now containers are stopped in Docker and then started in
Podman).
- We are
On 10/30/18 1:25 PM, Clark Boylan wrote:
On Tue, Oct 30, 2018, at 10:42 AM, Alex Schultz wrote:
On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec wrote:
Tagging with tripleo since my suggestion below is specific to that project.
On 10/30/18 11:03 AM, Clark Boylan wrote:
Hello everyone,
A
Yay!
Congratulations on the first Stein release, well done with your work
in looking after Searchlight so far.
On Tue, Oct 30, 2018 at 6:37 AM Trinh Nguyen wrote:
>
> Hi team,
>
> I'm doing a release for Searchlight projects (searchlight, searchlight-ui,
> python-searchlightclient) [1]. Please
On Tue, 30 Oct 2018, Mohammed Naser wrote:
We spoke about this today in the OpenStack Ansible meeting, we've come
up with the following steps:
Great! Thank you, Guilherme, and Lee very much.
1) Create a role for placement which will be called `os_placement`
located in
In echoing the words of everyone, it takes a tremendous amount of effort and
patience to lead this effort.
THANK YOU!
Sent from my iPhone
> On Oct 30, 2018, at 6:14 PM, Doug Hellmann wrote:
>
> "Ian Y. Choi" writes:
>
>> Hello,
>>
>> I got involved organizing & mentoring Korean people
On the TripleO side, it sounds like Lee Yarwood is taking the lead with a
first commit in puppet-placement:
https://review.openstack.org/#/c/604182/
Lee, can you confirm that you and your team are working on it for Stein
cycle?
On Thu, Oct 25, 2018 at 1:34 PM Matt Riedemann wrote:
> Hello
I must be losing it. On what planet is "Tiny Town" a single word, and
"Troublesome" not more than 10 characters?
~iain
On Mon, Oct 29, 2018 at 10:41 PM Tony Breeds wrote:
>
> Hi folks,
>
> It is time again to cast your vote for the naming of the T Release.
> As with last time we'll use a
On Tue, Oct 30, 2018, at 10:42 AM, Alex Schultz wrote:
> On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec wrote:
> >
> > Tagging with tripleo since my suggestion below is specific to that project.
> >
> > On 10/30/18 11:03 AM, Clark Boylan wrote:
> > > Hello everyone,
> > >
> > > A little while back I
Hi there:
We spoke about this today in the OpenStack Ansible meeting, we've come
up with the following steps:
1) Create a role for placement which will be called `os_placement`
located in `openstack/openstack-ansible-os_placement`
2) Integrate that role with the OSA master and stop using the
On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec wrote:
>
> Tagging with tripleo since my suggestion below is specific to that project.
>
> On 10/30/18 11:03 AM, Clark Boylan wrote:
> > Hello everyone,
> >
> > A little while back I sent email explaining how the gate queues work and
> > how fixing bugs
Brief meeting today on #openstack-operators, minutes below.
If you are attending Berlin, please start contributing to the Forum by
selecting sesions of interest and then adding to the etherpads (see
https://wiki.openstack.org/wiki/Forum/Berlin2018). I hear there's going to
be a really great one
TC members,
The TC will be meeting on 1 Nov at 1400 UTC in #openstack-tc to discuss
some of our ongoing initiatives. Here is the agenda for this week.
* meeting procedures
* discussion of topics for joint leadership meeting at Summit in
Berlin
* completing TC liaison assignments
**
Tagging with tripleo since my suggestion below is specific to that project.
On 10/30/18 11:03 AM, Clark Boylan wrote:
Hello everyone,
A little while back I sent email explaining how the gate queues work and how
fixing bugs helps us test and merge more code. All of this still is still true
"Ian Y. Choi" writes:
> Hello,
>
> I got involved organizing & mentoring Korean people for OpenStack
> upstream contribution for about last two months,
> and would like to share with community members.
>
> Total nine mentees had started to learn OpenStack, contributed, and
> finally survived
On 10/26/18 7:11 PM, Zane Bitter wrote:
> On 26/10/18 5:09 AM, Thomas Goirand wrote:
>> On 10/22/18 9:12 PM, Zane Bitter wrote:
>>> On 22/10/18 10:33 AM, Thomas Goirand wrote:
This can only happen if we have supporting distribution packages for
it.
IMO, this is a call for using
This is awesome Ian. Thanks for all of the work on this!
Michael
On Tue, Oct 30, 2018 at 8:28 AM Frank Kloeker wrote:
>
> Hi Ian,
>
> thanks for sharing. What a great user story about community work and
> contributing to OpenStack. I think you did a great job as mentor and
> organizer. I want
Hello everyone,
A little while back I sent email explaining how the gate queues work and how
fixing bugs helps us test and merge more code. All of this still is still true
and we should keep pushing to improve our testing to avoid gate resets.
Last week we migrated Zuul and Nodepool to a new
Zane Bitter writes:
> On 19/10/18 11:17 AM, Zane Bitter wrote:
>> I'd like to propose that we handle this by setting up a unit test
>> template in openstack-zuul-jobs for each release. So for Stein we'd have
>> openstack-python3-stein-jobs. This template would contain:
>>
>> * A voting gate
Good news! The Foundation found space for us to do a project update
session, so now we need to figure out what to talk about. I've started
an etherpad at
https://etherpad.openstack.org/p/oslo-project-update-stein to list the
possible topics. Please add or expand on the ones I've pre-populated
Hi Ian,
thanks for sharing. What a great user story about community work and
contributing to OpenStack. I think you did a great job as mentor and
organizer. I want to keep you with us.
Welcome new contributors any many thanks for translation and
programming. Hopefully you feel comfortable
Hi,
Basically we should kill quota classes.
It required out of tree stuff that was never implemented, AFAIK.
When I checked with Kevin about this, my memory says the idea was out
of tree authorization plugin would populate context.quota_class with
something like "i_have_big_credit_limit" or
Earlier today I learned that we have a few repositories with linter jobs
failing (or at least reporting warnings) because they are running
"python setup.py check" to test that the packaging meta-data is OK.
This method of testing has been deprecated in favor of using the command
"twine check",
Hello,
I got involved organizing & mentoring Korean people for OpenStack
upstream contribution for about last two months,
and would like to share with community members.
Total nine mentees had started to learn OpenStack, contributed, and
finally survived as volunteers for
1) developing
Thanks Doug for quick response. I will start working accordingly.
Akhil
From: Doug Hellmann
Sent: Tuesday, October 30, 2018 6:03:24 PM
To: AKHIL Jain; openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [goals][upgrade-checkers] [telemetry]
Hi openstack-dev@,
During the weekly meeting today the topic of moving the weekly meeting
forward by an hour to adjust for US Daylight Savings Time ending was
brought up. All contributors in attendance unanimously voted for the
move. [1]
If you would like to participate in the meetings and
AKHIL Jain writes:
> Hi Matt and Telemetry Team,
>
> I was going through the remaining project to be implemented with
> upgrade-checkers placeholder framework. I would like to know about the
> projects to implement the same under telemetry tab.
>
> According to my understanding from below
Dear OpenStack community,
FOSDEM 2019 will feature a Virtualization & IaaS DevRoom again. Here is
the call for proposals. Please check it out if you would like to submit
a talk.
Regards,
Kashyap
---
We are excited to
Hi all
To continue our discussion in Denver, we will have a forum [1] in Berlin on
*Wednesday, November 14, 11:50am-12:30pm CityCube Berlin - Level 3 -
M-Räume 8*
We will host the forum in an open discussion format, and try to get actions
from forum to make sure we can keep push what people need.
Hi Matt and Telemetry Team,
I was going through the remaining project to be implemented with
upgrade-checkers placeholder framework. I would like to know about the projects
to implement the same under telemetry tab.
According to my understanding from below link, multiple projects come under
Hi All,
TC office hour is started on #openstack-tc channel. Feel free to reach to us
for anything you want discuss/input/feedback/help from TC.
-gmann
__
OpenStack Development Mailing List (not for usage questions)
42 matches
Mail list logo
