On Oct 18, 2018, at 11:43 AM, Michał Dulko wrote:
>
> I'm totally supportive for OpenStack Train, but got to say that
> OpenStack Troublesome is a wonderful name as well. :)
Yeah, I’m sure that the marketing people won’t have a problem vetting that
name. :)
--
pleted, or are we planning on encouraging its use?
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.o
, solid code that doesn't encourage
technical debt accumulation. We have no way to prevent bad decisions by others,
but we should never document that such usages are fine.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
_
to be overly clever and try to overload a
trait name, it's up to them to deal with the resulting mess. But in no way
should we *ever* encourage, even tacitly, this approach.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
_
i-sig
[7] http://eavesdrop.openstack.org/#API_Special_Interest_Group
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.lau
On Sep 19, 2018, at 10:25 AM, Chris Dent wrote:
>
> I'd like to nominate Tetsuro Nakamura for membership in the
> placement-core team.
I’m not a core, but if I were, I’d +1 that.
-- Ed Leafe
__
#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
ement
IRC channel.
-- Ed Leafe
[0] https://etherpad.openstack.org/p/placement-extract-stein-3
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
utcome of that decision. Revisiting it now would be painful, as Chris
notes, and do nothing to advance the progress we have been making. Let’s focus
on the work in front of us, and not waste time revisiting past decisions.
-- Ed
e I don’t know enough about Open API to
compare them.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.
iltered directory and a nova directory to get a list
of what has been removed, but that can be somewhat messy. I just want to set
expectations when reviewing the extracted code in gerrit.
-- Ed Leafe
__
OpenStack Deve
d to
> know to do the eventual merging correctly and efficiently.
I’ve re-run the extraction, re-arranged the directories, and cleaned up most of
the import pathing. The code is here: https://github.com/EdLeafe/placement. I
did a forced push to remov
As there were only 2 nominations for the 2 open seats, elections will not be
needed. Congratulations to Matt Van Winkle and Joseph Sandoval!
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions
among the Nova core developers is that the consensus
among Placement cores will certainly not align with the needs of Nova. I
personally think that's ridiculous, and, as one of the very opinionated people
involved, a bit insulting. No one wants to see either Nova or Placement to fail.
-- Ed Leafe
etwork in the past.
That detail aside, the question is still valid: did the split from working
within the Nova project to working as an independent project have positive or
negative effects? Or both?
-- Ed Leafe
__
OpenStack
are political factors; it would be naive to think otherwise.
That’s why I’d like to get input from those people who are not in the middle of
it, and have no political motivation. I’d like this to be a technical
discussion, with as little political over
nful it will be to
extract, and hence the likelihood of that every happening is greatly diminished.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-
them (with their
permission, of course)! Help make a difference for Operators, Users and the
Community!
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
genda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
is
then confirmed by one of the election officials, after verification of the
electorate status of the candidate.
[0] Sorry, southern hemisphere people!
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions
html/draft-ietf-httpbis-bcp56bis-06
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-
o be sure that there was nothing
blocking you that we could help with.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubsc
ss!
We have migrated the API-SIG from Launchpad to StoryBoard [0], specifically so
that your group has a place to record stories, tasks, etc. Please feel free to
use this to help coordinated your work.
[0] https://storyboard.open
ght turn out to be the
"wrong" thing that nothing gets done.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not for usage questions)
Unsubscri
cords
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
contributors/cores are
>> from one company, maybe it should be an internal project for that company,
>> and not a community project.
>>
>> -- Ed Leafe
>
> Where was the rule added, though? I am aware of some individual teams
> with the rule, but AFAIK it w
to keep them. If a
project is so small that the majority of its contributors/cores are from one
company, maybe it should be an internal project for that company, and not a
community project.
-- Ed Leafe
signature.asc
Descrip
ink they can create a more impressive PoC with
another API, the API-SIG will support that.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not for usage q
in my OpenStack experience. Nitpicking, on the other hand, is
much more prevalent, and I welcome these efforts to reduce it.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing
ack, but I would have preferred to fix the whole thing by not storing the
marker in the first place.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ..
you (and everyone else) would want to see.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.o
g
[7] http://lists.openstack.org/pipermail/openstack-dev/2018-April/129987.html
[8] http://graphql.org/
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-
und like a good
approach to (all of) you?
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/c
es, and maintain outside of OpenStack?
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?
t be specified sounds pretty sane to me.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
enda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
__
OpenStack Development Mailing List (not
n-starter.
I need to work on my communication skills. This is what I’ve been saying all
along.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openst
the unnecessary extra directory level in
nova/api/openstack. There is only one Nova API, so the extra ‘openstack’ level
is no longer needed.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Uns
return that. So if you have 100 hosts, you don’t need to make 100 calls to
Cyborg; only 1.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?
ason?
By default, hosts are weighed one by one. You can subclass the BaseWeigher (in
nova/weights.py) to weigh all objects at once.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
ctivate this discussion.
What range of times would work for you?
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:/
od to me. I've updated the PEP to say 2.7 is completely dead on Jan 1
> 2020." adding "The final release may not literally be on January 1st".
>
> https://www.python.org/dev/peps/pep-0373/ now says
> "2.7 will receive bugfix support un
d out a summary of the
> summaries later :)
When is your meeting? I don’t see it listed on http://eavesdrop.openstack.org.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
nstack/api-wg
[7] https://twitter.com/anticdent/status/968503362927972353
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-
-ptg-rocky
[8] https://ethercalc.openstack.org/xja22ghws13i
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack
g things run so smoothly.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/m
On Feb 15, 2018, at 2:41 PM, Marcin Juszkiewicz <marcin.juszkiew...@linaro.org>
wrote:
>
>> Second, there will be 2 others from my ppc64le team getting involved
>> in Kolla, Mark Hamzy and Ed Leafe. Ed will be attending PTG and will
>> try to get a chance to meet a fe
On Feb 12, 2018, at 9:57 AM, Chris Dent <cdent...@anticdent.org> wrote:
>
> Tuesday would be best for me as Monday is api-sig day.
Same, for the same reason.
-- Ed Leafe
__
OpenStack Development
ck.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage qu
we included a suggestion for how to
make your RPC-ish API consistent with other projects that also use an RPC-like
approach to parts of their API.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usag
the BODY instead of relying upon the URL to determine
what action to perform.
You might also want to contact the Kong developers to see if there is a way to
work with a RESTful API design.
-- Ed Leafe
[0]
http://eavesdrop.openstack.org/meetings/api_sig/2018/api_s
ss disorder in the meantime.
I still don't understand how anyone could do what you have done over these past
two years and not a) had a stress-induced heart attack or b) gotten divorced.
Thanks for the hard work!
-- Ed Leafe
_
penstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
__
OpenStack Development Mailing List (not fo
e a good way to convert to the
new paradigm.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
the advantages you mention aren’t real. I’m just pointing
out that there are downsides to stretching things out.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-
On Dec 14, 2017, at 3:01 AM, Thomas Goirand <z...@debian.org> wrote:
>
> As a package maintainer who no longer can follow the high pace, I very
> much support this change.
So you’re saying that you would be ignoring any intermediate release
ile I agree, where we're at is a tightly coupled mess, what I don't agree
> with is that the answer is to keep shipping the mess.
I agree 100% with that sentiment. However, *until* we achieve something close
to that, we have to continue to ship “this mess”. Taking a mess and shipping it
to make sure
that we're all still working together well.
[0] https://blog.leafe.com/on_swift/
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not for usage questions)
ore
like the original events, where there is no distraction by the corporate
marketing machines, and we can focus on getting shit done.
My question is: if we only have a release once a year, why do we need two
Summits a year?
-- Ed Leafe
signature.asc
Desc
est of the codebase onto the deployers.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?
be able to wait a whole year for some improvements.
Maybe it’s just the dev in me, but I prefer shorter cycles (CD, anyone?).
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
>
> https://doodle.com/poll/bec9gfff38zvh3ud
>
> If you’re interested in attending API-SIG meetings, please fill out the form
> at that URL with your preferences. I’ll summarize the results at the next
> API-SIG meeting.
>
>
> -- Ed Leafe
>
>
>
>
>
On Dec 7, 2017, at 11:22 AM, Ed Leafe <e...@leafe.com> wrote:
> That brought up another issue: the current meeting time for the API-SIG is
> 1600UTC, which is not very convenient for APAC contributors. Gilles is in
> Australia, and so it was the middle of the night for him! As o
ck.org/#/c/524467/
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-
-wg,n,z
[4] https://wiki.openstack.org/wiki/API_SIG
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-
On Nov 2, 2017, at 4:17 AM, Dmitry Tantsur <dtant...@redhat.com> wrote:
>
> The recording of the call is https://bluejeans.com/s/K3wZZ
Ugh: "To watch the video, you need Adobe Flash Player 10.1 or high
hat you could end up with a machine
with 100 GPUs - ok, I know that's not realistic, but it illustrates my point.
Each hardware combination is a separate resource class. If your workload
requires 2 GPUs and SSD, there are a finite number of hardware combinations
available. You pick the
nd IRC
archives to find the answers for the people I am considering voting for.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?
o see a good response to the questions this time, and the answers
(and non-answers) strongly influenced my vote. So I would rather see a shorter
nomination period and a longer “campaign” period in the future.
-- Ed Leafe
rg/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
__
OpenStack Development Mailing List (not
> of somebodies.
I wish all candidates, not just TC candidates, got follow-up questions like
this. Bravo, Zane!
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
ebase of Zuul and other system administration related tasks.
Thanks for the answer, and I definitely agree. But I don't feel that you
answered the important part: what would you have wanted the TC to do about this?
-- Ed Leafe
signature.asc
Descriptio
In the past year or so, has there been anything that made you think “I wish the
TC would do something about that!” ? If so, what was it, and what would you
have wanted the TC to do about it?
-- Ed Leafe
__
OpenStack
pressure to go along with accommodating
the change to the previous design.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not for usage questions)
Unsubscrib
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.ope
had one
of the other resource class available, and would include that if another
request for that class is received, which would then fail as the node is
already in use.
-- Ed Leafe
__
OpenStack Development
cessing the VFs, so I would go for the
first. And I’m not sure that we will be able to get the “inherited” traits used
in the second model implemented any time soon.
-- Ed Leafe
__
OpenStack Development Mailing List (no
484935 is correct?
That’s what I thought, too, but apparently [0] we need both in Pike. The
zeroing out can’t happen until Queens.
[0] https://review.openstack.org/#/c/484949/2/nova/virt/ironic/driver.py@471
-- Ed Leafe
_
enda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
signature.asc
Description: Message signed wi
won’t confuse people as to what OpenStack is. But that
doesn’t require any of the other projects be stopped or in any way discouraged.
-- Ed Leafe
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
aving leading
solutions in IaaS, PaaS, and SaaS. And Azure PaaS platform services can help
you be more productive and increase your ROI according to this Forrester Total
Economic Impact study.”
So I don’t think that this distinction is pec
#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Deve
hese should not be errors. You are calling the API to set a particular
condition. The result of that call is that the service is in that condition.
That should be a 2xx, most likely a 204. So yeah, it should be idempotent.
-- Ed Leafe
signature.asc
Descriptio
re to remove Glance and replace it with Glare, are you saying
that nothing would break? Operators, users, scripts, SDKs, etc., would all work
unchanged?
-- Ed Leafe
__
OpenStack Development Mailing List (not for usa
Now I know, I work on Nova, so I'm expecting responses that "of course you
don't care", or "OpenStack is people, and you're hurting our feelings!". So
flame away!
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
ve the information to a)
select the best fit and then b) claim it with the specific uuid. Same for all
the other nested/shared devices.
I don't mean to belabor this, but to my mind this seems a lot less disruptive
to the existing code.
-- Ed Leafe
signature.asc
Description: Message signed with O
cement engine, which knows about these relationships already, or the compute
service itself, which has to handle the management of these complex virtualized
resources.
I don't know the answer. I'm hoping that we can have a discussion that might
uncover a clear approach, or, at the very l
#/c/446138/
Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
signature.asc
Description: Message signed wi
of the mess that is "flavors", but the goal is to have a single flavor for
each Ironic machine type, rather than the current state of flavors pretending
that an Ironic node is a VM with certain RAM/CPU/disk quantities.
-- Ed Leafe
signature.asc
De
sers really care about what resources they got
> instead of just the performance. We also create a mogan horizon plugin which
> adds separated baremetal servers panel[1].
So Mogan does not use the placement service for tracking resources?
-- Ed Leafe
signature.asc
Descrip
to interact with the TC, as it follows the same naming
convention as #openstack-nova, #openstack-ironic, etc.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (n
e 5 minutes per week that we end up
> dedicating to open discussion in the meetings does not encourage people
> to load large topics of discussions in it.
Simple: *start* the meeting with Open Discussion.
-- Ed Leafe
signature.asc
Descri
-WG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_wg/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Developme
d consistent interfaces among the various projects to create a
platform that solutions can be built upon.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not for us
iscovery of the Higgs boson, and I'm sure that someday it will
enable technologies that haven't yet been dreamed up. Being able to look back
someday and say "I helped to build that" will be pretty satisfying.
-- Ed Leafe
signature.asc
Des
or you succeed at it or not (i swear
> i'm not a manager).
Very good point. In my case, I presented the goal, knowing that at best I might
be able to nudge the OpenStack world a bit closer in that direction.
-- Ed Leafe
signature
er project? Those things shouldn't matter (outside of
the IaaS core projects). Teams should be free to decide if working with another
team is the best approach, or going it alone, for example.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
___
ng to talk, Thierry usually
lets people speak in order of "raising their hand". This reduces cross-talk and
lets everyone get their turn to state what's on their mind. Normally, though,
it is a bit of an acquired skill to be able to follow along.
-- Ed Leafe
signature.a
s. There will be winners,
and there will be losers, and that's not only OK, it's how it should be.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not for usage questions)
Un
Hello! I am once again announcing my candidacy for a position on the OpenStack
Technical Committee.
For those who do not know me, I'm easy to find. My name is Ed Leafe; I'm
'edleafe' on IRC, and @edleafe on Twitter. I have been involved with OpenStack
since the very beginning, when I
1 - 100 of 318 matches
Mail list logo
