visual indentation, the standard is to indent two levels (i.e.,
8 spaces), to distinguish it from typical blocks. But yes, I much prefer this
than creating temporary names to accommodate the visual indentation style.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using
. The second exception should most likely be
'AuthenticationFailure', and should have the error text from the
Authentication exception.
I've seen confusion between authz and authn in many projects; looks like
OpenStack is no different, unfortunately.
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version
, I
think the approaches are more alike than different, which is encouraging.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
knowledgeable
contributors is a big win.
-- Ed Leafe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
are not limited to testing.
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iQIcBAEBAgAGBQJUJY6MAAoJEKMgtcocwZqLuxwP/1QSoHhhegZETtxVyrxBisOs
sjJfh+wzLqjfEqkwUOZ0SX2aEFHuimNE5lWmPPB7hzffc6Z4aNxITjP/fCry77Ax
IQsGTbTGG0gsXiyO/+/x6c6Yfkcmu6fui8L/hde0u7klN/8tATkp/5xwW4qvGXY7
content into an etherpad/wiki page and
trying to wade through it. If people want to dump content somewhere and use
that to help inform their contributions to the repo, that’s okay too.
+1 from me too. Etherpads for active discussions tend to devolve into a
mess.
- -- Ed Leafe
-BEGIN PGP
in a French
traditional restaurant. At best you get a bowl of rice. At worse you get
Canton rice with bacon and shrimps.
Maybe can you provide a translation for Does this dish have any meat in
it?. That seems to work best for me, since 'vegetarian' means so many
different things.
- -- Ed Leafe
saner than 68!
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iQIcBAEBAgAGBQJURUVUAAoJEKMgtcocwZqLwXgQAKEdX/Ir5ud6DJIwyBgbBwIW
ScFcfIuNQZmZ5OWx/YGsiTBo9bkuARmknOcQm0TwUtXvKJkjPVzFl+6oSYov+fzT
aF4qsk7tAJaDbCi06YEAxGfy2yqQKO6D5FayTBwXUmMwg1IUQhZXMLhPlkbu65F1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/22/2014 08:03 AM, Dugger, Donald D wrote:
Just a reminder that, as we mentioned last week, no meeting today.
The meetings are supposed to be on Tuesday, no? And yeah, no one showed
up yesterday.
- -- Ed Leafe
-BEGIN PGP SIGNATURE
a lot worse days!
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.29_team_meeting
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iQIcBAEBAgAGBQJUR9WMAAoJEKMgtcocwZqLcWsP/jqoiVyYS0kEjEO0XHUIuWDG
ZQa1V7CE749hM/PZTNSbu979uDnJTE7hF5Xi0CCfNsKRwS419ZEPnPkNglNslmO9
riReo5oQ04i4iWF/Ou5+ZVp4OeWrVuigKW6wUW1f8digzcLGuD7qpIsFFBEmkviM
On Nov 17, 2014, at 2:18 PM, Jay Pipes jaypi...@gmail.com wrote:
Please, can we as a community kill the term flavor in a fire?
+1
One of the first (but certainly not the last) battle I lost in the early days
of Nova.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
for different levels of service, and not something that you would need to make
a working CDN API.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
for that time value.
-- Ed Leafe
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ideal
as much. I'd be interested in your feedback, as well as everyone else's.
I think that this simpler approach will also be much more doable in the
Kilo timeframe.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iQIcBAEBAgAGBQJU1VpIAAoJEKMgtcocwZqLHeEP
about going through the ones listed on the agenda, rather than
having a free-for-all shouting match?
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iQIcBAEBAgAGBQJU052HAAoJEKMgtcocwZqLHiIP/A7vIQsh219+7mnxttDPLc4A
Av25XW6WJDVciPlR5VIlDIQTdl
I sent this at the beginning of the exception process, but it did not appear on
the list of exceptions mikal posted at today's nova meeting, so I'm re-sending.
Begin forwarded message:
Date: January 8, 2015 at 8:50:57 AM CST
From: Ed Leafe e...@leafe.com
To: OpenStack Development Mailing
exception.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
and let me try to provide again
a quick explanation about my view here...
OK, thanks for clarifying!
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iQIcBAEBAgAGBQJUvYGRAAoJEKMgtcocwZqLugoP/ij8CV3btpkm25mj5GoIGAKi
+kC5zNf0ecaFbS0snuF6FnmHbaNme/n8nXDIqx2xtC3KK
.
So please read up on that spec, and come to the meeting tomorrow
prepared to discuss it.
BTW, the latter approach is very similar to an earlier version of the
spec: https://review.openstack.org/#/c/138444/8/ . We seem to be going
in circles!
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE
, you can also be a jerk about how you tell someone they can improve, but
that's certainly not the norm in this community.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack
.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iQIcBAEBAgAGBQJUyle8AAoJEKMgtcocwZqLRX4P/j3LhEhubBOJmWepfO6KrG9V
KxltAshKRvZ9OAKlezprZh8N5XUcxRTDxLhxkYP6Qsaf1pxHacAIOhLRobnV5Y+A
oF6E6eRORs13pUhLkL+EzZ07Kon+SjSmvDDZiIo+xe8OTbgfMpo5j7zMPeLJpcr0
RUSS+knJ
cleanup effort that has been
identified as a priority for Kilo.
Thanks for your consideration!
[1] https://review.openstack.org/#/c/138444/
[2]
https://github.com/openstack/nova-specs/blob/master/specs/kilo/approved/isolate-scheduler-db-aggregates.rst
- -- Ed Leafe
-BEGIN PGP SIGNATURE
. People who feel they need it can add it back.
Agreed on this. The less cruft we carry, the better.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List
stability vs. innovation.
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iQIcBAEBAgAGBQJVAMjCAAoJEKMgtcocwZqLkKIP/0ReARgypM+eXnu7xDguJIF/
6QW8RI7tdHpBFrRZfrBaRahDstFdPQiaBxj1XhFbzoKP+BrUvvfLMnxhJ5cRX0ey
mz842khScuGmLFzteKvLWwyOia425CZQRnNNaHYjiwii3Agu3a5JTnUi0FeDxZi4
, openstackclient has an impossible task: taking the varied (and flawed) CLI
clients and unite them under a single CLI interface. It is better to create the
clean separation of the API wrapping into a Python library, and keep the CLI
completely separate.
-- Ed Leafe
signature.asc
Description
presentation. It's been a while since I was involved with that project, but it
seems that decoupling the command line interface from the Python API wrapper
would make testing much, much easier.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
, and intense integration testing is done on that, with bug fixes as
needed. But how to get developers who are intent on coding their new features
to hold off and work on fixing bugs identified by the stable testing is a big
question mark to me.
-- Ed Leafe
signature.asc
Description
,
the release cycle scheduler *helps* immeasurably. We can't be both.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
vendor, to distribute.
I don't think that anyone is implying that it is easy to do, no matter where it
is done. It does seem that there are significant disadvantages on the
development side of things to have one group doing it all.
-- Ed Leafe
signature.asc
Description: Message signed
to this trend. Much of the debate that used to happen with
patch sets now happens on the spec, which delays the first submission of
a patch, and shortens the time for review, since reviewers are already
familiar with the changes being proposed.
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version
be available.
I took one, and might be there for more.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
) justify splitting it out. Splitting for
the sake of splitting is pointless.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net
-but-also-a-bunch-of-cats
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
to answer what was asked.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJVOkqtAAoJEKMgtcocwZqLkhEQAJub3Ae6+4/8Cf08kiB8vTd4
f3U8s7SOnfP371Jv72F1QbA1Ar4qSL7eTQF2
returning.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJVOmE5AAoJEKMgtcocwZqLQXkQAKCaFJ0u4/RvPMPj5n1OCsoZ
vx3lqGshJa2aHGhiX20e9EFIBDzSTPuM06ZJdsKWsRskdK3U
to every review? It won't affect the flow, and damn, they'll
get to 14 bazillion reviews without breaking a sweat!
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net
within and between projects,
being both willing and capable to jump in and address them when necessary;
and on the other hand, representing that constituency to the broader
community.
Thanks for writing this, as well as your other points. I couldn't agree more
with those sentiments.
-- Ed
of the other candidates!), and I will be
happy to answer any questions.
Thanks for your consideration,
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List
.
For now, I think this is best. When and if the scheduler is a separate entity,
it will need its own docs; nova will still need to document *its* filters, but
not *how to* filter.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
On Apr 30, 2015, at 6:30 AM, John Garbutt j...@johngarbutt.com wrote:
I propose we add Melanie to nova-core.
I know I'm not core, so my vote doesn't count, but I think that this would be a
great addition.
+1
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using
to you all! I am disappointed that I did not win, but I'm glad
to have such an excellent group representing us on the TC.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack
improving, and how the TC can find advocates in the
contributor community to sponsor bugs and blueprints that operators need
worked on.
+1!
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
isn't innovating.
Finding a way to do something significantly better is innovating.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage
with that tool that makes it so. However, you can also
use innovative tools for common tasks and I could get really
philosophical about this so I'll stop here :)
Oh, I know you know. I was just commenting on the common reaction to
Oooh, shiny! as a persuasive technical argument. :)
- --
- -- Ed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/11/2015 03:18 PM, Everett Toews wrote:
I would like to propose Michael McCune (elmiko) as an API Working
Group core.
I'm not core, but I have been impressed by his work. +1 from me.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE
such a request), it would be surprising to developers to
allow such requests.
REST APIs are difficult enough. Let’s avoid things with no
defined semantics.
Wise words.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG
message count as an API change? Or are we saying
that it's such a small API change that any discussion can happen in the
blueprint?
I don't think that the notification system is the same as the API. It is
something that you can subscribe to or not, and is distinct from the API.
-- Ed Leafe
some of said badges. It sounds like you more or less agree
with that goal. So how do you propose we get there?
Because having 15 core reviewers for all of nova is just not
cutting it.
My $.02 on this: http://blog.leafe.com/the-core-deficiency/
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE
. A year later when I was considering joining IBM, the
fact that he would be on my team was a very strong positive factor in
my decision. He was always a joy to work with, even these past few
months when he was fighting the ultimate battle. He was, and still is,
a true inspiration.
- --
- -- Ed
debt.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJVHVuCAAoJEKMgtcocwZqLjcwQAIOzkKTLCjWLV84bqoCJX6Ai
D/zzqMCoOOYyj341lrfVM2SxkJX6
.
Gantt was dead when I re-joined the nova team 7 months ago, and so its
name should also die.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net
of said campaign literature and adding one
line at the bottom.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJVHrS/AAoJEKMgtcocwZqLQ6YP
arbitrary; it's well thought out and widely understood. I
haven't heard a reason *why* nova can't work with semver, only that a few
proposed version schemes don't follow semver.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
Please note that if you are interested in the scheduler meeting times, today is
the last day to get in your vote. We will be choosing a new time at tomorrow's
meeting, based on the results of the vote.
On Jun 2, 2015, at 4:09 PM, Ed Leafe e...@leafe.com wrote:
Signed PGP part
Hi
was just about to write something similar, but you beat me to it.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions
a spec for
removing flavors from the scheduler.
So did I miss anything? :)
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage
and update the calendar.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJVbhuBAAoJEKMgtcocwZqLS3cP/iCP8d6piLUBcMNUCSZFehcD
have to
address that change via a microversion instead. The change itself is
still valid, but the means of implementing it might have to be updated.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird
looking to possibly moving
it to Mondays.
If you're involved with the Scheduler, please register your
availability here:
http://doodle.com/cuxa6xk63yb5y5tn
We will discuss the results at next Tuesday's meeting at 1500 UTC.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment
, are they? If not, let's do them
ASAP, and then iterate from there.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJViuMJAAoJEKMgtcocwZqLp2EQAIFOeEJgfVZoVOeFIpEkr7wy
ask a question: Would there be any particular problem with
using X-OpenStack-API-Version?
Well, perhaps we should consider OpenStack-API-Version instead
and drop the X-. Ref https://tools.ietf.org/html/rfc6648.
That makes the most sense to me.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE
system
before discussing on how other projects could add more resources to Nova.
Yes, this is important in making it possible to transition to a different model
in an organized way. I just wanted to start the discussion on what that new
model might look like.
-- Ed Leafe
signature.asc
for some of those resources?
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
of them is if you want to consider the request as a
single operation that can either fail or succeed.
Even in that case, succeed would mean that you were able to create min_count
instances. If that isn't what was wanted, then the min_count should be the same
as the max_count.
-- Ed Leafe
for all of the above. :)
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
to
reflect this, but I wanted to send something out now so that you can
update your calendars. See you Monday!
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net
was that while this is an interesting approach, and that
experimenting with novel approaches can be very worthwhile, it was not
considered a priority, as there is too much work already on everyone's
plate for Liberty. So the experiment isn't going to happen any time soon
.
- --
- -- Ed Leafe
-BEGIN PGP
with real-world
ironic deployments, please share your insights.
[1] https://review.openstack.org/#/c/206736/
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sorry, I'm going to have to miss this one. Got some engineers coming
to re-level my house. :)
I don't have anything much to discuss from my end, as I've been
heads-down on the v3 cleanup stuff.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE
to
create a new v3 API that would be backwards-incompatible, which was
later abandoned in favor of the microversion approach.
There is a current effort to clean up the code base by removing the
old 'v3' references since, as you have learned, the current layout is
confusing.
- --
- -- Ed Leafe
stuff. :)
[1] https://review.openstack.org/193725
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJVrlx9AAoJEKMgtcocwZqL9SQP/3JMFtpOPNRlndap3pZqfpqB
).
Why we still need this option?
Agreed - it isn't needed anymore.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJVp7fGAAoJEKMgtcocwZqL0McP
to introduce a new technology.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
have a completely different environment. New operators coming into
OpenStack will soon recognize which tags are relevant to their environment, and
give them much more credence when it comes to evaluating the state of the
various projects.
-- Ed Leafe
signature.asc
Description: Message
://www.datastax.com/
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJVpmvCAAoJEKMgtcocwZqLSNYP/0b8s7pZnXaF3tTYF+WtNppr
lHyQMHSXLQ3CESoS4961ZWOCMtV2hCxvcioXem
necessarily be accepted back in the main
repo.
Yes, that's sort of the whole point. First prove that it can work;
then and only then do we sit down and discuss the best way to
implement. The odds that any of the changes made would be able to be
pulled directly into master would be slim.
- --
- -- Ed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/14/2015 05:52 AM, John Garbutt wrote:
Please note, the non-priority feature freeze is on: July 30
Exception: subject and body not in agreement.
:)
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools
every project gets equivalent,
trackable, audit-able, process-oriented support.
+1
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage
integrate with the openstackclient
project as well. We're trying to move from the current state of a
bunch of separate CLIs that all work differently to a single,
consistent driver.
- --
- -- Ed Leafe
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: GPGTools - https://gpgtools.org
Comme
ght savings ended in the US last
week.
> Japan 21:00 (Tue)
> China 20:00 (Tue)
> United Kingdom 13:00 (Tue)
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Dev
ard in some small
> way on this.
I can see this generating a lot of controversy! :)
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for u
vers that works
> for everybody!
I think that this is a great idea, but we also need some people familiar with
Consul to do this work. Otherwise, ZK (and hence Java) is a defacto dependency.
-- Ed Leafe
signature.asc
Description: Message signed with Ope
very clear that they would
*not* run any Java applications, and that if OpenStack required a Java app to
run, they would no longer use it.
I like the idea of using Zookeeper as the DLM, but I don't think it should be
set up as a default, even for devstack, given the vehement opposition expressed.
-- Ed
VM and using it to create another
VM that appears to the user as the same (ID, networking, attached volumes,
metadata, etc.)
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack
se respond with comments, +1s, or objections within one week.
Well deserved! +1 from me.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List
spond with comments, +1s, or objections within one week.
I'm not a core, but would like to add my hearty +1.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mai
a similar instance, both processes would most likely come up
with the same set of hosts ordered in the same way. One of those processes
would "win", and claim the first choice. The other would fail the transaction,
and would then claim the second choice on the list. IMO, this is how
ar test bed and try it out. IOW, instead of bikeshedding,
if you want a different color, you build another shed and we can all have a
look.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
_
e this type of change, or some other type of change, or keep
things the way they are, having the data to justify that decision is always
important.
-- Ed Leafe
[0] http://lists.openstack.org/pipermail/openstack-dev/2015-July/069593.
ir state to the scheduler both on a scheduled task, and in
response to changes. The impetus for the Cassandra proposal was to eliminate
this duplication, and have the resources being scheduled and the scheduler all
working with the same data.
-- Ed Leafe
signature.asc
Descripti
im, forcing them to select a different host without
having to first go through the fail/retry cycle of the current design.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
_
Cool! I don't really care if my particular ideas are selected; I just want to
make OpenStack better.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not fo
k how-to for setting up a
small cluster: http://blog.leafe.com/small-scale-cassandra/. Using docker
images makes it a breeze!
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack D
out there. That
> would get you a stampeding herd and a bunch of retries.
>
> I admit that the current system does not solve well for (3).
IMO, this is identical to (2).
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
* Russell Bryant (russellb)
> * Kyle Mestery (mestery)
Congratulations to all of you - it's well deserved. And it makes losing feel
much better knowing how well we'll all be represented on the TC.
-- Ed Leafe
signature.asc
Description: Message sig
as the advantage that it might give sufficient
time to weed out undesirable names, such as what happened with the M naming
process.
-- Ed Leafe
signature.asc
Description: Message signed with OpenPGP using GPGMail
__
and
discussion here on the dev list, so that all can see your ideas, but I will be
in Tokyo for the summit, and would also welcome some informal discussion there,
too.
-- Ed Leafe
[0] http://lists.openstack.org/pipermail/openstack-dev/2015-July/069593.html
[1] http://blog.leafe.com
1 - 100 of 318 matches
Mail list logo
