ensor information?
Sadly, not really. I'm hoping some observers of this thread will chime
in.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstac
On Mon, 20 Oct 2014, Jim Mankovich wrote:
On 10/20/2014 6:53 AM, Chris Dent wrote:
On Fri, 17 Oct 2014, Jim Mankovich wrote:
See answers inline. I don't have any concrete answers as to how to deal
with some of questions you brought up, but I do have some more detail
that may be usef
e the UI for
people who want to do things with the data.
So from my perspective, with regard to naming IPMI (and other hardware
sensor) related samples, I think we need to make a better list of the
use cases which the samples need to satisfy and use that to drive a
naming scheme.
--
Chris Dent tw:@ant
thing).
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ity.
I think we should strive to worry less about such things, especially
when it's just names in data fields. Not always possible, or even a
good idea, but sometimes its a win.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__
thing that needs it
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
hat the 1.3 release of Docker ("any day now") will sport a
Yesterday:
http://blog.docker.com/2014/10/docker-1-3-signed-images-process-injection-security-options-mac-shared-directories/
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.co
lling on other stuff to do the work.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, 14 Oct 2014, Angus Lees wrote:
2. I think we should separate out "run the server" from "do once-off setup".
Yes! Otherwise it feels like the entire point of using containers
and dockerfiles is rather lost.
--
Chris Dent tw:@anticdent freenode:cdent
https://tan
ormation
about themselves.
There are solid arguments against each of these problems individually
but as a set I find them saying "services should make more
notifications" pretty loud and clear and obviously to make that work
we need tidy notifications with good clean semantics.
--
On Mon, 25 Aug 2014, Joe Gordon wrote:
On Mon, Aug 4, 2014 at 3:29 AM, Chris Dent wrote:
For constraints: Will tempest be available as a stable library? Is using
tempest (or other same library across all projects) a good or bad thing?
Seems there's some disagreement on both of these.
pporunities throughout
OpenStack, not just in telemetry/metering/eventing (choose your term
of art).
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http:/
on't gain much if you have people in a room with name A and all
you do is put a new name on the room and don't change the people or
the room.
We need to do more this time around than change some names.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
f-notifications
something worth tracking? I would say yes.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ere, just point out
a good example, since it has _no_ arrows.
[3] "their own", that's hateful, let's have less of that.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev m
#x27;s not. There's tyranny of choice all over OpenStack. Is
that good for real people or just large players and our corporate
hosts?
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing lis
sues than these, but I think some of
the above is being left out of the discussion, and this message
needs to stop.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
pproved) way to do 'make clean'.
I guess tox -eclean or something would be the same but it feels
wrong somehow.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.o
On Fri, 12 Sep 2014, Julien Danjou wrote:
I guess the problem is more likely that testrepository load the tests
From the source directory whereas maybe we could make it load them from
what's installed into the venv?
This rather ruins TDD doesn't it?
--
Chris Dent tw:@anticdent free
notifications in some way so we can also
constrain the consumer code.
Or maybe we should just use RDF and produce a super upper ontology
and consume all the world's knowledge as events? That's been super
successful in other contexts...
--
Chris Dent tw:@anticdent freenode:cd
o the existential questions of What is
OpenStack in the business of? and How do we stay sane while being in
that business?
Every long thread over the last couple of months has trended towards
those questions. It's getting pretty tiresome. We'd all be a lot
more focused if we knew
On Sun, 7 Sep 2014, Monty Taylor wrote:
1. Caring about end user experience at all
2. Less features, more win
3. Deleting things
Yes. I'll give away all of my list for any one of these.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/
o put all this another way: As we are evaluating what we want to do
and how we want to do it we need to think less about the projects and
technologies that are involved and more about the actions and results
that our efforts hope to allow and enable.
[1]
http://lists.openstack.org/piper
t of automated
hook?
Thoughts? Anybody wanna hack on it with me? I think it could wind up being a
pretty useful tool for folks outside of OpenStack too if we get it right.
Given availability (currently an unknown) I'd like to help with this.
--
Chris Dent tw:@anticde
x27;t know) that having more granularity in projects will
allow different teams to engage at different rates and thus get stuff
done, but I do not think it will do much with regard to external
perceptions of quality. That's going to take a much different kind of
work and attention.
--
Chris Den
to understand more clearly what's going on. My interest here comes
from a general interest in now events and notifications are handled
throughout OpenStack.
Thanks.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
that
existing notification use cases are satisfied with robustness and
provide a contract between two endpoints. The other is to allow a
fecund notification environment that allows and enables many
participants.
Is that a good summary? What did I leave out or get wrong?
--
Chris Dent
t, some discussion here on options to reach some
resolution.
* A cup of tea or other beverage of our choice and some sympathy
and commiseration. A bit of "I too have suffered at the hands of
grenade". Then we can all be friends.
From my side I can provide a promise to follow through
one developer not on the core team handle a graduation for us.
+many more for the relatively simple act of just writing stuff down
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack
x27;d _love_ to be more capable at gate debugging.
That said, it does get easier just by doing it. The first many times
is like beating my head against the wall, especially the constant
sense of where am I and where do I need to go.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermor
[1] I do think, when using namespaces, that you must have a namespace
for the extensions different from whatever the thing being
extended is using.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenS
(e.g. getting more nodes for CI, having more documentors,
etc.).
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ot;in tree functional tests":
* to reach places unit tests won't go
* to not have the noise of all that mock and OO mess
* to have some faith in the end to end
The sorts of things that require provisioning of temporary datastores,
interception of wsgi apps, in process message queues...
--
Chri
in the project and make some contributions? That is how this is
supposed to work isn't it?
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ll make it possible to do more flexible
testing.
I appreciate that searching through endless log files is a common
task in OpenStack but that doesn't make it the best way.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
l those potentially good reasons there's also just the
simple matter that it is good data hygiene to know where stuff came
from?
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailin
ach sample because as agents leave and join the group, where
samples are published from can change.
* How should it be named? The never-ending problem.
Thoughts?
[1] https://review.openstack.org/#/c/113549/
[2] https://review.openstack.org/#/c/115237/
--
Chris Dent tw:@anticdent freenode:c
On Mon, 18 Aug 2014, Chris Dent wrote:
The reason for doing this? I want to be able to confirm that some
sample data retrieved in a query against the ceilometer API has
samples that span the upgrade.
The associated change is here:
https://review.openstack.org/#/c/102354
--
Chris Dent tw
gainst the ceilometer API has
samples that span the upgrade.
Thoughts?
Thanks.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.o
hat can be applied to multiple strategic goals.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
" or "os-integration-tests".
This idea is best, but if a new name is required, tempit is good because it
is a) short b) might subconsciously remind people that testing ought to
be fast(-ish).
--
Chris Dent tw:@anticdent freenode:cdent
ht
roken: Every few days I'll update all my various repos and think "wow
that's an awful lot of changed code".
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent___
OpenStack-dev mailing list
OpenStack-dev@li
something worth
tracking as you explore and think.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
my code.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2014-July/thread.html#41057
[2]
http://lists.openstack.org/pipermail/openstack-dev/2014-July/041188.html
http://lists.openstack.org/pipermail/openstack-dev/2014-July/041252.html
--
Chris Dent tw:@anticdent fr
:
https://wiki.openstack.org/wiki/Testr#FAQ
and included it in there. With luck other people will add stuff.
Now to see about speed.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
f the swift dependencies
Will link to this thread from the bugs for visibility.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstac
ght argument,
either from the command line or in tox.ini.
Even if you don't know a way, I'd like to hear from other people who
would like it to be possible. It's one of several testing habits I
have from previous worlds that I'm missing and doing a bit of
commiseration would b
ter/objectstore/swift_middleware.py
[2] https://review.openstack.org/#/c/110302/
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/
On Tue, 29 Jul 2014, Chris Dent wrote:
Let me know whenever you have a new release, without mechanize as new
dependency, or with it being optional.
It will be soon (a day or so).
https://pypi.python.org/pypi/wsgi_intercept is now at 0.8.0
All traces of mechanize removed. Have at. Enjoy. If
to get their opinions on which way is the best way forward,
I'd prefer not to make the decision solo.
Let me know whenever you have a new release, without mechanize as new
dependency, or with it being optional.
It will be soon (a day or so).
--
Chris Dent tw:@anticdent freenode:cdent
https:/
f you get back to me by tomorrow morning (UTC) I can probably get the new
version out tomorrow too.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://list
ash around you.
Maybe you aren't looking at the most recent version (0.7.0)?
If there are issues please report them as bugs on github, they'll
get fixed:
https://github.com/cdent/python3-wsgi-intercept/issues
If there's a better way to do the optional-ness of mechanize
(witho
There's a review in progress for a generic event format for
PaaS-services which is a move with the right spirit: allow various
services to join the the notification party without needing special
handlers.
See: https://review.openstack.org/#/c/101967/
--
Chris Dent tw:@anticdent freenode:
d do in that small
environment (rather than the overwhelming context of the The Entire
Project™).
I'll pay a bit closer attention to the specific relationship
between the ceilometer exceptions (on the loops) and the logs and
when I find something that particularly annoys me, I'll submit a
pa
tionsIKnow) as exc:
LOG.warning('shame, no workie, but you know, it happens: %s', exc)
except Exception:
LOG.exception('crisis!')
This makes it easier to distinguish between the noise and the nasty,
which I've found to be quite challenging thus far.
--
Chris De
tely informative) failure
than 'something failed'.
So, my question: Is this something we who dig around in the ceilometer
code ought to care about and make an effort to clean up? If so, I'm
happy to get started.
Thanks.
--
Chris Dent tw:@anticdent freenod
a time. Seems like that will hurt parallelism
opportunities?
[1] There's vernacular here that I'd prefer to use but this is a
family mailing list.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-
that structure for the sake of less code
and more reuse. As part of this process I'll try to figure out if this
is true .
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
once landed -
https://review.openstack.org/#/c/97317/ - local testing gets us to an
unrelated ceilometer bug. However landing the 2 tempest patches first
should be done.
If you'd like me to look into that ceilometer bug, please let me
know what it is.
--
Chris Dent tw:@anticdent freenode:cdent
https:/
ith what's being used.
This feels like something that we should be thinking about with an eye
to the K* cycle - would you agree?
Yup.
Thanks for helping to tease this all out and provide some direction on
where to go next.
--
Chris Dent tw:@anticde
ke to see this move along and I'm happy to do the leg
work to make it so, but I need a bit of guidance on where to push.
Thanks.
[1] http://lists.openstack.org/pipermail/openstack-dev/2014-July/039078.html
[2] The TC did some gap analysis and one of the areas that needs work
is in resource
it is Ceilometer then it means that StackTach must also
keep its own mapping. And so does every other consumer. The general
provision here is to get more DRY about information authority.
If you can figure out how to do that in a concrete way ... then great,
I'd be receptive, let's hear s
de to make it possible:
http://paste.openstack.org/show/86071/
However on that however, if there's some chance that a large change could
happen, it might be better to wait, I don't know.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.
ome configured mapping rules?
I don't think there needs to be much, if any, mapping on the consumption
side of the notification process if there is a standard form in which
those notifications are emitted. In those cases where pipeline
transformation needs to be done ( multiple valu
rmat, we could have said,
in response to the initial proposal, "looks good but if you make the
data look like _this_ that would be totally wicked sweet!"
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
y
with a pre-warmed virtualenv.
My next hope is to get rid of unittest and just do the plain asserts
that py.test makes so nice and lovely.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
OpenStack-dev mailin
knowledge is being represented is
code. That is a BadThing™. I'm sure there are plenty of reasons for
why it has turned out that way, but if there is an opportunity for
change...?
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent__
new features
and functionality to it.
I'll press pause on the ceilometer stuff for a while. Thanks for the
quick response. I just wanted to make sure I wasn't crazy. I guess
not, at least not because of this stuff.
--
Chris Dent tw:@an
ill javelin have any knowledge of whether the
current check run is happening before or after the upgrade stage?
Thanks for any help and input. I'm on IRC as cdent if you want to find me
there rather than respond here.
[1] https://review.openstack.org/#/c/102354/
[2] https://review.open
on.
What's the recommended path to make this happen?
Thanks.
[1] https://github.com/openstack/tempest/blob/master/tempest/cmd/javelin.py
[2] Definition of "sane" to be determined.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
___
it is
somebody else's problem.
--
Chris Dent
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
701 - 771 of 771 matches
Mail list logo
