From: Renat Akhmerov
Date: Monday, 23 April 2018 at 9:45
On 23 Apr 2018, 13:38 +0700, Jaewook Oh , wrote:
Hello Mistral and Vitrage team,
I've been testing vitrage with mistral workflow,
but it seems that there are no Vitrage actions in Mistral yet.
I think Vitrage actions should be added t
Works for me.
Tom
On 19.04.2018 16:17, Javier Pena wrote:
Hello fellow packagers,
During today's meeting [1], we discussed the schedule conflicts some of us have
with the current meeting slot. As a result, I would like to propose a new
meeting time:
- Wednesdays, 1 PM UTC (3 PM CEST)
So fa
On 4/20/18 8:56 PM, Emilien Macchi wrote:
So the role has proven to be useful and we're now sure that we need it
to deploy a container registry before any container in the deployment,
which means we can't use the puppet code anymore for this service.
I propose that we move the role to OpenStac
Added the kolla tag in the hope to get some feedback wrt the question
Forwarded Message
Subject: Re: [openstack-dev] [tripleo] roadmap on containers workflow
Date: Mon, 23 Apr 2018 10:08:36 +0200
From: Bogdan Dobrelya
Organization: Red Hat
To: [email protected]
Hi Sergey,
In magnum queens we can set the private ca as a service account key.
Here [1] we can set the ca.key file. When the label cert_manager_api is
set to true.
Cheers,
Spyros
[1]
https://github.com/openstack/magnum/blob/master/magnum/drivers/common/templates/kubernetes/fragments/configure-k
Hello,
the I18n team wants to change something in collaboration and
communication with other teams and users. Instead of team meetings we
offer around the Summit an open communication on Freenode IRC
#openstack-i18n channel. Feel free to add your topics on the wiki page
on [1]. Or better joi
I spoke with Jaewook briefly in #openstack-mistral, for anyone interested
in following this work there is now a blueprint to track it.
https://blueprints.launchpad.net/mistral/+spec/mistral-vitrage-actions
Thanks all
On 23 April 2018 at 07:57, Jaewook Oh wrote:
> Hello Renat,
>
> I'll join the
Hi horizon plugin developers,
As I announced in the quoted mail, Rocky-1 was released and mox is NOT
prepared in the horizon test helpers by default now [1].
If your horizon plugin still depends on mox, please ensure to set use_mox =
True in your test classes.
> 2) After Rocky-1, use_mox of opens
On Fri, 20 Apr 2018, Doug Hellmann wrote:
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
Thanks for getting the ball rolli
Hi All,
We moved our meeting time to 14:00UTC on Wednesdays, but attendance
has been low, and it is also the middle of the night for one of our
cores.
I would like to suggest we have an office hours style meeting, with
one in the UTC evening and one in the UTC morning.
If this seems reasonable -
7On 20/04/18 22:26, Doug Hellmann wrote:
> Without letting the conversation devolve too much into a discussion
> of Adjutant's case, please talk a little about how you would evaluate
> a project's application in general. What sorts of things do you
> consider when deciding whether a project "alig
On Thu, Apr 19, 2018 at 1:01 PM, Emilien Macchi wrote:
> Greetings,
>
> As you probably know mcornea on IRC, Marius Cornea has been contributing on
> TripleO for a while, specially on the upgrade bits.
> Part of the quality team, he's always testing real customer scenarios and
> brings a lot of go
ironic-inspector is using Flask, and it has been quite nice so far.
On 04/11/2018 12:56 AM, Michael Johnson wrote:
I echo Ben's question about what is the recommended replacement.
Not long ago we were advised to use WSME over the alternatives which
is why Octavia is using the WSME types and pec
Hey everyone!
We had a bug day about two weeks ago and it went pretty well! At last
week's IRC meeting the idea of having one every month was thrown around.
What does everyone think about having Bug Day the first Thursday of
every month?
Thanks,
Mike Turek
Hello Vitrage team,
A few days ago I used Devstack to install the Openstack master version,
which included Vitrage.
However, I found that the Vitrage graph does not work on the
Vitrage-dashboard.
The state of all Vitrage components is active.
Could you check it once?
Thanks.
Hi,
New week, new status mail.
Bugs
New bugs
[Undecided] https://bugs.launchpad.net/nova/+bug/1764927 Should send
out notification when instance metadata get updated
Nova already sends instance.update notification when instance.metadata
is changed so I marked the bug invalid.
Hi,
For a mix of good and bad reasons, we haven't been able to do this until now.
The upcoming RDO test days will be May 3rd and 4th and we'll be
testing the latest content from Rocky now that M1 has been released.
We can re-use the pad we had started last time around [1].
I'll be in touch.
[1]
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
We frequently have discussions about whether the TC is active enough,
in terms
Excerpts from Doug Hellmann's message of 2018-04-23 09:27:09 -0400:
> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
>
Greetings,
Could you please review the following bindep.txt[1] changes to your projects and
approve them, it would be helpful to the openstack-infra team. We are looking
to remove some legacy jenkins scripts from openstack-infra/project-config and
your projects are still using them. The followin
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
In the course of evaluating new projects that have asked to join
as official me
In general I would prefer TC take an active role regarding exploring new
use cases and technology directions leverage the existing OpenStack
infrastructure. I would against TC being too active on project level
governance.
For example we have been discussing about edge computing recently and we
don
I think this depends on the nature of the project.
For deployment tools, as we also have witnessed in OPNFV, it tends to have
multiple solutions. So it is normal to have multiple such projects although
they are solving the same problem generally speaking.
For projects that has a clear definition
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
Over the last year we have seen some contraction in the number of
companies and
Hello searchlighters,
The Rocky 1 milestone was last Thursday, and there has been no release request
was submitted for the searchlight deliverables [1].
I remember some discussion at the last Denver PTG about searchlight and that it
is basically considered "code complete" at this point until any
Culture wise, being too IRC-centric is definitely not helping, from my own
experience getting new Cyborg developer joining our weekly meeting from
China. Well we could always argue it is part of a open source/hacker
culture and preferable to commercial solutions that have the constant risk
of sudde
Excerpts from Zhipeng Huang's message of 2018-04-23 21:50:15 +0800:
> In general I would prefer TC take an active role regarding exploring new
> use cases and technology directions leverage the existing OpenStack
> infrastructure. I would against TC being too active on project level
> governance.
On Mon, Apr 23, 2018 at 09:16:03AM -0500, Sean McGinnis wrote:
> Hello searchlighters,
>
> The Rocky 1 milestone was last Thursday, and there has been no release request
> was submitted for the searchlight deliverables [1].
>
> I remember some discussion at the last Denver PTG about searchlight a
On 18/04/18 11:38, Chris Dent wrote:
> On Tue, 17 Apr 2018, Thierry Carrez wrote:
>
>> So... Is there any specific topic you think we should cover in that
>> meeting ?
>
> The topics:
>
> 1. What are we to do, as a community, when external pressures for
> results are not matched by contribution
Excerpts from Zhipeng Huang's message of 2018-04-21 07:06:30 +0800:
> As the one who just lead a new project into governance last year, I think I
> could take a first stab at it.
>
> For me the current requirements in general works fine, as I emphasized in
> my recent blog [0], the four opens are
I don't have specific ideas now, but it would be great to have TC publish
something like a new direction outlook per cycle or per year, to summarize
that these x,y,z new areas are what the OpenStack Technical Committee
considers worth exploring for new directions and we will sponsor projects
that w
Doug Hellmann wrote:
> [...]
> Please describe one case where we were either active or reactive
> and how that was shown to be the right choice over time.
I think that the work on documenting our key principles was proactive,
and it really helped to set expectations for new people in our community
On Mon, Apr 23, 2018 at 8:04 AM, Michael Turek
wrote:
> Hey everyone!
>
> We had a bug day about two weeks ago and it went pretty well! At last
> week's IRC meeting the idea of having one every month was thrown around.
>
> What does everyone think about having Bug Day the first Thursday of every
Excerpts from Rico Lin's message of 2018-04-22 16:50:51 +0800:
> Thanks, Doug, for raising this campaign question
>
>
> Here are my answers:
>
>
> ***How you would evaluate a project's application in general
>
> First I would work through the requirements ([1]) to evaluate projects.
> Since mo
I think it actually relies upon the new team to actively reaching out to
the existing team. The new team cannot be lazy and wait for something
happen for them, they have to keep reaching out and believe me the core
developers from the existing official project will lend a hand in the end :)
For Cy
big +1 to Graham's suggestion
On Mon, Apr 23, 2018 at 10:36 PM, Graham Hayes wrote:
> On 18/04/18 11:38, Chris Dent wrote:
> > On Tue, 17 Apr 2018, Thierry Carrez wrote:
> >
> >> So... Is there any specific topic you think we should cover in that
> >> meeting ?
> >
> > The topics:
> >
> > 1. Wha
Excerpts from Thierry Carrez's message of 2018-04-22 15:10:40 +0200:
> Doug Hellmann wrote:
> > [This is meant to be one of (I hope) several conversation-provoking
> > questions directed at prospective TC members to help the community
> > understand their positions before considering how to vote in
Excerpts from Sean McGinnis's message of 2018-04-22 21:01:46 -0500:
> >
> > We are discussing adding at least one new project this cycle, and
> > the specific case of Adjutant has brought up questions about the
> > criteria we use for evaluating new projects when they apply to
> > become official.
Excerpts from Chris Dent's message of 2018-04-23 12:09:42 +0100:
> On Fri, 20 Apr 2018, Doug Hellmann wrote:
>
> > [This is meant to be one of (I hope) several conversation-provoking
> > questions directed at prospective TC members to help the community
> > understand their positions before consid
Doug Hellmann wrote:
> Where do you draw the line at "gratuitous"?
The way I interpret "gratuitous" here is: is the new project using a
technically-different approach to the same problem, or is it just
another group working at the same problem in the same way ? Is the new
project just a way to avo
Excerpts from Graham Hayes's message of 2018-04-23 12:15:24 +0100:
> 7On 20/04/18 22:26, Doug Hellmann wrote:
>
> > Without letting the conversation devolve too much into a discussion
> > of Adjutant's case, please talk a little about how you would evaluate
> > a project's application in general.
Excerpts from Graham Hayes's message of 2018-04-23 15:36:32 +0100:
> On 18/04/18 11:38, Chris Dent wrote:
> > On Tue, 17 Apr 2018, Thierry Carrez wrote:
> >
> >> So... Is there any specific topic you think we should cover in that
> >> meeting ?
> >
> > The topics:
> >
> > 1. What are we to do, a
On 2018-04-23 15:36:32 +0100 (+0100), Graham Hayes wrote:
> I think as an add on to this, would to ask the board to talk to members
> and see what contributions they have made to the technical side of
> OpenStack.
>
> This should not just be Number of commits / reviews / bugs etc but
> also the mo
On 23/04/18 15:06, Doug Hellmann wrote:
> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> Over the last year we have
On 23/04/18 16:04, Doug Hellmann wrote:
> Excerpts from Graham Hayes's message of 2018-04-23 12:15:24 +0100:
>> 7On 20/04/18 22:26, Doug Hellmann wrote:
>>
>>> Without letting the conversation devolve too much into a discussion
>>> of Adjutant's case, please talk a little about how you would evalu
On Mon, 23 Apr 2018, Doug Hellmann wrote:
We frequently have discussions about whether the TC is active enough,
in terms of driving new policies, technology choices, and other
issues that affect the entire community.
Another good question. Like all the others I wish they had come a
bit earlier
> >
> > I think one of the important things is if it fits in to furthering what is
> > "OpenStack", as far as whether it is a service or functionality that is
> > needed
> > and useful for those running an OpenStack cloud. This is one of the parts
> > that
> > may be more on the subjective side.
100% on board with this, I think it was really productive!
Sam
On 23/04/2018, 15:44, "Jim Rollenhagen"
mailto:[email protected]>> wrote:
On Mon, Apr 23, 2018 at 8:04 AM, Michael Turek
mailto:[email protected]>> wrote:
Hey everyone!
We had a bug day about two weeks ago and it we
On 20/04/18 17:26, Doug Hellmann wrote:
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
Thanks Doug, I think this is a reall
On Mon, 23 Apr 2018, Doug Hellmann wrote:
Where do you draw the line at "gratuitous"?
What benefits and drawbacks do you see in supporting multiple tools
with similar features?
How would our community be different, in positive and negative ways,
if we were more strict about avoiding such overl
Doug Hellmann wrote:
> Over the last year we have seen some contraction in the number of
> companies and individuals contributing to OpenStack. At the same
> time we have started seeing contributions from other companies and
> individuals. To some degree this contraction and shift in contributor
>
Excerpts from Graham Hayes's message of 2018-04-23 16:27:04 +0100:
> On 23/04/18 16:04, Doug Hellmann wrote:
> > Excerpts from Graham Hayes's message of 2018-04-23 12:15:24 +0100:
> >> 7On 20/04/18 22:26, Doug Hellmann wrote:
> >>
> >>> Without letting the conversation devolve too much into a disc
Doug Hellmann wrote:
> Excerpts from Thierry Carrez's message of 2018-04-22 15:10:40 +0200:
>> For the product fit, there is also a lot of room for interpretation. For
>> me it boils down to whether "OpenStack" (the product) is better with
>> that project "in" rather than with that project "out". S
On 23/04/18 14:50, Doug Hellmann wrote:
> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> In the course of evaluating
On 23/04/18 17:14, Doug Hellmann wrote:
> Excerpts from Graham Hayes's message of 2018-04-23 16:27:04 +0100:
>> On 23/04/18 16:04, Doug Hellmann wrote:
>>> Excerpts from Graham Hayes's message of 2018-04-23 12:15:24 +0100:
7On 20/04/18 22:26, Doug Hellmann wrote:
> Without letting th
One of the challenges in the academic sector is the time from lightbulb moment
to code commit. Many of the academic resource opportunities are short term
(e.g. PhDs, student projects, government funded projects) and there is a
latency in current system to onboard, get the appropriate recognitio
Hi Folks,
Some of the Oslo libraries have a tox test that does the above [0].
This ensures that our requirements.txt file is kept current with the
code.
This test uses a tool called pip_check_reqs [1]. Unfortunately this
tool is not compatible with pip version 10, and it appears as if the
github
On Mon, 23 Apr 2018, Doug Hellmann wrote:
What aspects of our policies or culture make contributing to OpenStack
more difficult than contributing to other open source projects?
Size, isolation, and perfectionism.
Size in at least three dimensions:
* the entire community
* individual projects
On 23/04/18 09:50, Doug Hellmann wrote:
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
In the course of evaluating new proje
On Mon, 23 Apr 2018, Tim Bell wrote:
One of the challenges in the academic sector is the time from
lightbulb moment to code commit. Many of the academic resource
opportunities are short term (e.g. PhDs, student projects,
government funded projects) and there is a latency in current
system to onb
** What aspects of our policies or culture make contributing to
OpenStackmore difficult than contributing to other open source projects?To
fully understand the map of OpenStack services is a huge challenge,
especially for new join developers. And for project teams, might not
provide new contributor
*Thanks, Doug for bringing out this campaign questionI think we have a
start now with providing a decent map to show services in OpenStack and
fill in with projects. What we should have and will be nice is to ask
projects to search through the map (with a brief introduction of services)
when they'r
On 2018-04-23 12:02:14 -0400 (-0400), Zane Bitter wrote:
[...]
> The main thing I will be looking out for in those cases is that
> the project followed the Four Opens *from the beginning*. Projects
> that start from a code dump are much less likely to attract other
> contributors in my view. Open S
On Mon, 23 Apr 2018, Doug Hellmann wrote:
Excerpts from Chris Dent's message of 2018-04-23 12:09:42 +0100:
I'd like to see us work harder to refine the long term goals we are
trying to satisfy with the projects that make up OpenStack. This
will require us to continue the never-ending discussion
Excerpts from Graham Hayes's message of 2018-04-23 17:23:20 +0100:
> On 23/04/18 17:14, Doug Hellmann wrote:
> > Excerpts from Graham Hayes's message of 2018-04-23 16:27:04 +0100:
> >> On 23/04/18 16:04, Doug Hellmann wrote:
> >>> Excerpts from Graham Hayes's message of 2018-04-23 12:15:24 +0100:
>
Excerpts from Jeremy Stanley's message of 2018-04-23 17:02:07 +:
> On 2018-04-23 12:02:14 -0400 (-0400), Zane Bitter wrote:
> [...]
> > The main thing I will be looking out for in those cases is that
> > the project followed the Four Opens *from the beginning*. Projects
> > that start from a co
On Fri, 2018-04-20 at 14:44 +0200, Thomas Herve wrote:
> On Thu, Apr 19, 2018 at 2:59 PM, Harald Jensås
> wrote:
> > Hi,
>
> Hi, thanks for sending this. Responses inline.
>
> > When configuring TripleO deployments with nodes on routed ctlplane
> > networks we need to pass some per-network prope
Excerpts from Chris Dent's message of 2018-04-23 17:50:31 +0100:
> On Mon, 23 Apr 2018, Tim Bell wrote:
>
> > One of the challenges in the academic sector is the time from
> > lightbulb moment to code commit. Many of the academic resource
> > opportunities are short term (e.g. PhDs, student projec
On 2018-04-23 13:14:59 -0400 (-0400), Doug Hellmann wrote:
[...]
> I hope that no one considers any of this "noise," so thank you for
> highlighting that point.
Oh, yes I didn't mean to imply that any of the responses so far have
been noise, but I was walking a thin line on it being a hollow sort
Excerpts from Rico Lin's message of 2018-04-24 00:54:14 +0800:
> ** What aspects of our policies or culture make contributing to
> OpenStackmore difficult than contributing to other open source projects?To
> fully understand the map of OpenStack services is a huge challenge,
> especially for new jo
On 23/04/18 18:14, Doug Hellmann wrote:
> Excerpts from Graham Hayes's message of 2018-04-23 17:23:20 +0100:
>> On 23/04/18 17:14, Doug Hellmann wrote:
>>> Excerpts from Graham Hayes's message of 2018-04-23 16:27:04 +0100:
On 23/04/18 16:04, Doug Hellmann wrote:
> Excerpts from Graham Ha
On 4/23/2018 12:18 PM, Doug Hellmann wrote:
I would like for us to collect some more data about what efforts
teams are making with encouraging new contributors, and what seems
to be working or not. In the past we've done pretty well at finding
new techniques by experimenting within one team and t
*IMO TC should be more active as possible. Since we try to use this
position to make policies, we should also consider hard how we can
broadcast those policies to each developer to provide guidelines and to get
possible feedbacks.To reach out current/potential technical contributors,
to sell this t
Excerpts from Matt Riedemann's message of 2018-04-23 12:35:07 -0500:
> On 4/23/2018 12:18 PM, Doug Hellmann wrote:
> > I would like for us to collect some more data about what efforts
> > teams are making with encouraging new contributors, and what seems
> > to be working or not. In the past we've
2018-04-23 22:43 GMT+08:00 Doug Hellmann :
>
> Excerpts from Rico Lin's message of 2018-04-22 16:50:51 +0800:
> > Thanks, Doug, for raising this campaign question
> >
> >
> > Here are my answers:
> >
> >
> > ***How you would evaluate a project's application in general
> >
> > First I would work thr
On Mon, Apr 23, 2018 at 10:16 AM, Harald Jensås wrote:
> On Fri, 2018-04-20 at 14:44 +0200, Thomas Herve wrote:
> > On Thu, Apr 19, 2018 at 2:59 PM, Harald Jensås
> > wrote:
> > > Hi,
> >
> > Hi, thanks for sending this. Responses inline.
> >
> > > When configuring TripleO deployments with nodes
On 23/04/18 14:27, Doug Hellmann wrote:
> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> We frequently have discussi
On 2018-04-23 13:18:22 -0400 (-0400), Doug Hellmann wrote:
[...]
> I would like for us to collect some more data about what efforts
> teams are making with encouraging new contributors, and what seems
> to be working or not. In the past we've done pretty well at finding
> new techniques by experime
2018-04-24 1:26 GMT+08:00 Doug Hellmann :
>
> Excerpts from Rico Lin's message of 2018-04-24 00:54:14 +0800:
> > ** What aspects of our policies or culture make contributing to
> > OpenStackmore difficult than contributing to other open source
projects?To
> > fully understand the map of OpenStack s
On 23/04/18 09:27, Doug Hellmann wrote:
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
We frequently have discussions about
On 4/23/2018 1:24 PM, Jeremy Stanley wrote:
Some of us also urged existing leaders in various projects to record
videos encouraging contributors to get more involved by demystifying
processes like code review or bug triage. This could be as simple as
signing up for an available lightning talk slo
Hello Sean,
EC2-api team always used manual tagging because I know only this procedure.
I thought that it's more convenient for me cause I can manage
commits/branches.
But in fact I don't mind to switch to automatic scheme.
If somethig else is needed from please let me know.
Regards,
Andrey Pavlo
On 2018-04-23 16:28:13 + (+), Tim Bell wrote:
> One of the challenges in the academic sector is the time from
> lightbulb moment to code commit. Many of the academic resource
> opportunities are short term (e.g. PhDs, student projects,
> government funded projects) and there is a latency in
Hey Dougal,
I think I had said May 2nd in my initial email asking about attendance. If
you can get an answer out of your team by then I would greatly appreciate
it! If you need more time please let me know by then (May 2nd) instead.
-Kendall (diablo_rojo)
On Fri, Apr 20, 2018 at 8:17 AM Dougal M
See below for logs from a failed xstatic release job. It appears something is
not set up right with this job.
"can't open file 'xstatic_check_version.py': [Errno 2] No such file or
directory"
I missed it initially, but this release did not actually contain any functional
change, so I think it is
We seem to be at a bit of an impasse in this spec amendment [1] so I
want to try and summarize the alternative solutions as I see them.
The overall goal of the blueprint is to allow defining traits via image
properties, like flavor extra specs. Those image-defined traits are used
to filter hos
On Mon, Apr 23, 2018 at 07:32:40PM +, Kendall Nelson wrote:
> Hey Dougal,
>
> I think I had said May 2nd in my initial email asking about attendance. If
> you can get an answer out of your team by then I would greatly appreciate
> it! If you need more time please let me know by then (May 2nd)
On Mon, Apr 23, 2018 at 7:16 PM, Harald Jensås wrote:
> On Fri, 2018-04-20 at 14:44 +0200, Thomas Herve wrote:
>> To make it clear, what you want to prevent is the need to add more
>> keys in network_data.yaml?
>>
>> As those had to be provided at some point, I wonder if tripleo can't
>> find a w
On Mon, Apr 23, 2018 at 8:09 PM, Dan Sneddon wrote:
> We could add the ControlPlaneDefaultRoute and ControlPlaneSubnetCidr to
> network_data.yaml, but this would involve some duplication of configuration
> data, since those are currently defined in undercloud.conf. A more robust
> solution might
Hi Training Team,
It is a friendly reminder that we will have a conference call on Zoom today at
2200 UTC as opposed to the weekly meeting to better sync up before the training
in Vancouver.
You can find the call details here:
https://etherpad.openstack.org/p/openstack-upstream-institute-meeti
On 2018-04-23 21:45, Sean McGinnis wrote:
> See below for logs from a failed xstatic release job. It appears something is
> not set up right with this job.
>
> "can't open file 'xstatic_check_version.py': [Errno 2] No such file or
> directory"
>
> I missed it initially, but this release did not a
Submitted the following review on April 19,
https://review.openstack.org/#/c/562768/
Would like to know who else could be on the reviewer list and anything else for
the next step?
Thanks.
Louie
__
OpenStack Development Mai
Submitted the following review on January 17, 2018,
https://review.openstack.org/#/c/534958/
Would like to know who else could be on the reviewer list ? or anything else is
needed for the next step?
Also, I am planning to attend our coming Masakari Weekly meeting, April 24,
0400 UTC in #opens
Semantically, GET /allocation_candidates where we don't actually want to
allocate anything (i.e. we don't want to use the returned candidates) is
goofy, and talking about what the result would look like when there's no
`resources` is going to spider into some weird questions.
Like what does the re
On Mon, Apr 23, 2018 at 10:06 AM, Doug Hellmann wrote:
> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> Over the las
Looking over the things in the runways queue [1], excluding the zVM
driver (because I'm not sure what the status is on that thread), the
next in line is blueprint list-show-all-server-migration-types [2].
I know this has been approved since Pike, but I wanted to raise some
questions again [3]
On 23/04/18 10:06, Doug Hellmann wrote:
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
Over the last year we have seen some
On 4/23/2018 3:26 PM, Eric Fried wrote:
No, the question you're really asking in this case is, "Do the resource
providers in this tree contain (or not contain) these traits?" Which to
me, translates directly to:
GET /resource_providers?in_tree=$rp_uuid&required={$TRAIT|!$TRAIT, ...}
...which
>
> Over the last year we have seen some contraction in the number of
> companies and individuals contributing to OpenStack. At the same
> time we have started seeing contributions from other companies and
> individuals. To some degree this contraction and shift in contributor
> base is a natural
Following the discussion on IRC, here's what I think you need to do:
- Assuming the set of traits from your new image is called image_traits...
- Use GET /allocations/{instance_uuid} and pull out the set of all RP
UUIDs. Let's call this instance_rp_uuids.
- Use the SchedulerReportClient.get_provi
1 - 100 of 122 matches
Mail list logo
