I've just joined - what is the usual place and time?
Thanks,
Miles
- Original Message -
From: "Beth Elwell"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Thursday, 22 October, 2015 8:33:03 AM
Subject: Re: [openstack-dev] [ironic] Next meeting is November 9
H
Thanks!
Miles
- Original Message -
From: "Dmitry Tantsur"
To: openstack-dev@lists.openstack.org
Sent: Thursday, 22 October, 2015 11:37:49 AM
Subject: Re: [openstack-dev] [ironic] Next meeting is November 9
On 10/22/2015 12:33 PM, Miles Gould wrote:
> I've just jo
- Original Message -
> From: "Lennart Regebro"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Sent: Tuesday, 10 November, 2015 1:42:52 PM
> Subject: Re: [openstack-dev] [TripleO] [Ironic] Let's stop hijacking other
> projects' OSC namespaces
>
> These changes
I also vote for baremetal-inspection - punning names are fun, but increase the
amount of stuff new developers have to learn.
I'm totally in for the Peter Sellers marathon, though.
Miles
- Original Message -
> From: "Jay Pipes"
> To: openstack-dev@lists.openstack.org
> Sent: Saturday, 5
On 31/05/16 21:03, Timofei Durakov wrote:
there is blueprint[1] that was approved during Liberty and resubmitted
to Newton(with spec[2]).
The idea is to define state machines for operations as live-migration,
resize, etc. and to deal with them operation states.
+1 to introducing an explicit sta
On 01/06/16 16:45, Joshua Harlow wrote:
Do u have any more details (perhaps an 'real-life' example that you can
walk us through) of this and how it played out. It'd be interesting to
hear (I believe it has happened a few times but I've never heard how it
was resolved or the details of it).
The
On 01/06/16 13:50, Andrew Laski wrote:
This is a great point. I think most people have an implicit assumption
that the state machine will be exposed to end users via the API. I would
like to avoid that for exactly the reason you've mentioned. Of course
we'll want to expose something to users but
On 09/06/16 23:21, Jay Faulkner wrote:
There was some discussion about whether or not the Ironic grenade job
should be in the check pipeline (even as -nv) for grenade,
Not having this would mean that changes to grenade could silently break
Ironic's CI, right? That sounds really bad.
Miles
_
Hi everyone,
tl;dr: the tests for the operator in
nova.scheduler.filters.extra_specs_ops do not test what it looks like
they're meant to test. This is confusing us, and holding up work in
Ironic. Does it match its arguments against a list of strings, or
against a single string?
---
On 07/07/16 17:43, Miles Gould wrote:
Further evidence that this isn't the intended behaviour: if you remove
all the calls to str(), then the original tests still pass, but the
' e' (substring matching) one doesn't.
I've now proposed this as a patch:
https://review
On 08/07/16 15:22, Miles Gould wrote:
On 07/07/16 17:43, Miles Gould wrote:
Further evidence that this isn't the intended behaviour: if you remove
all the calls to str(), then the original tests still pass, but the
' e' (substring matching) one doesn't.
I've now
On 02/05/16 18:43, Jay Pipes wrote:
This DB could be an RDBMS or Cassandra, depending on the deployer's
preferences
AFAICT this would mean introducing and maintaining a layer that
abstracts over RDBMSes and Cassandra. That's a big abstraction, over two
quite different systems, and it would be h
On 09/05/16 23:14, Joshua Harlow wrote:
Anyways, after doing that I wanted to get any thoughts from people on
the ML about that code, if they can see anything obviously bad about
having more formality in the matching/spec DSL and/or other usages of
things that I am not aware of that might be prob
On 06/03/17 20:46, Mario Villaplana wrote:
We also still have yet to decide what a suitable deprecation period is
for this change, as far as I'm aware. Please respond to this email
with any suggestions on the deprecation period.
One cycle?
Miles
___
On 07/03/17 12:14, Jim Rollenhagen wrote:
I'm also good with the standard deprecation period for this.
+1 to "standard deprecation period" - sorry, I'd misremembered what that
was.
Miles
__
OpenStack Development Mailing
On 10/03/17 16:28, Heidi Joy Tretheway wrote:
Hi Ironic team,
Here’s an update on your project logo. Our illustrator tried to be as
true as possible to your original, while ensuring it matched the line
weight, color palette and style of the rest. Thanks for your patience as
we worked on this! Fee
On 15/07/16 03:53, Britt Houser (bhouser) wrote:
Koala is the best by a long shot. These ideas are all total stretches:
Bee on a honeycomb – Its kinda like the bee is orchestrating
containers of honey.
That sounds more like a honeypot ant to me:
https://en.wikipedia.org/wiki/Honeypot_ant
http
On 13/12/16 14:07, Ana Krivokapic wrote:
If you'd like a calendar invite for this deep dive, email me and I'll
add you to the meeting invite.
Yes please!
Miles
__
OpenStack Development Mailing List (not for usage question
On 02/02/17 16:55, Loo, Ruby wrote:
I guess a 'peace sign' wouldn't work?
That also has several meanings:
https://en.wikipedia.org/wiki/V_sign
On the other hand, the palm-forward version has no offensive meanings
that I can see (the offensive version is palm-backwards).
I like the propose
On 01/02/17 01:28, arkady.kanev...@dell.com wrote:
I think Russian already owns the bear.
AIUI, trademark law allows for use of the same mark by different
entities provided they operate in different enough spheres to prevent
confusion. Hence the long-running litigation between Apple Music and
On 01/02/17 21:38, Lucas Alvares Gomes wrote:
But, let me ask something, what the foundation really wants to achieve
with this ? Cause I think we are conflating two things here: A logo (or
brand) and a mascot.
I think this is an excellent point. The constraints on logos make a lot
of sense *fo
On 13/09/16 20:30, Anish Bhatt wrote:
Is parsing iDrac/System attributes differently from BIOS attributes the
correct approach here (this will also make it match racadm output), or
should I be changing all Attributes to be parsed the same way ?
"Parse everything the same way" sounds like the si
On 26/09/16 10:24, Dmitry Tantsur wrote:
I suggest adding Milan Kovacik (milan or mkovacik on IRC) to the
ironic-inspector-core team. He's been pretty active on ironic-inspector
recently, doing meaningful reviews, and he's driving our HA work forward.
Please vote with +1/-1. If no objections are
On 14/10/16 12:33, Sean Dague wrote:
I kind of wonder if that hints to a better model here instead of the
deployments running services from master. Instead running periodics and
moving forward reference hashes every day if tests pass, and not if they
fail. That would let deployment tools automati
On 17/10/16 18:43, Chris Dent wrote:
On Mon, 17 Oct 2016, gordon chung wrote:
you forgot to add disclaimer how you broke every bone in your body a
while back.
\o/ Thanks for paying attention, you get a gold star. But actually
it was only three. And it was outside.
Maybe what you're really lo
On 19/10/16 18:33, Dan Sneddon wrote:
I am doing research to support the spec for TripleO deployment on
routed networks [1]. I would like some input on how to represent
multiple subnet ranges for the provisioning network in undercloud.conf.
[snip]
## inspector_dnsmasq_tftp.erb ##
port=0
Capsule rec.juggling-style review
-
**High:** Impossible to pick out one moment in particular, but in
general it was getting to chat informally over dinner/drinks/climbing
with other Stackers. Thanks everyone for making me feel welcome!
**Low:** Spending four hour
On 09/11/16 07:34, Renat Akhmerov wrote:
Ok, thank you all!
Dougal, welcome to the core team! I’m hoping for fruitful collaboration
with you :)
Congratulations, Dougal!
Miles
__
OpenStack Development Mailing List (not fo
On 14/11/16 20:52, Ian Cordasco wrote:
not_in is nice and explicit while nin and out are a bit, more clever. I think
we should avoid trying to be clever.
Agreed - I think not_in is more intelligible and guessable than the
other suggestions.
Miles
___
On 25/11/16 17:12, Jeremy Stanley wrote:
It came down less to safety and more to the fact that if you force
cgit to present rendered content then you lose the ability to
reference the source code for the same files.
I don't think this is an insurmountable problem: it should be possible
to all
30 matches
Mail list logo