ttps://review.openstack.org/12345 - nova
Depends-On: https://review.openstack.org/12346 - python-neutronclient
Just as a quick way to remember, without having to link follow, which of
multiple depends on are which projects. I've resorted to putting them on
top, but for short things would love
loud pip mirrors.
Break downs of wide internet connectivity is very hard to diagnose, and
just as often the fault of the upstream source as the downstream
network. My suggestion is to work with the infra team to mirror whatever
content you need within their existin
On 05/26/2016 03:07 PM, Jeremy Stanley wrote:
> On 2016-05-26 14:23:38 -0400 (-0400), Sean Dague wrote:
> [...]
>> It does run on a custom port... so the great firewall of China is still
>> probably an issue.
> [...]
>
> I had assumed websockets could be a solution ther
of doing what everyone does and polls once an hour. As long as the topic
trees are well structured, it should make for an easy way to get the
slice they needed and only react to that.
-Sean
--
Sean Dague
http://dague.net
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
e nice. (You can even do it straight in javascript for web based
things).
-Sean
--
Sean Dague
http://dague.net
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
On 02/12/2016 12:03 PM, Jeremy Stanley wrote:
> On 2016-02-12 06:41:56 -0500 (-0500), Sean Dague wrote:
> [...]
>> What bug / issue tracker should I be using so that we can build up
>> profiles of things like this? I know story board isn't a thing atm. The
>> openstac
I don't think gets looked at (we
mostly use it as a dumping ground for ER signatures that don't have a
clear home).
Would love to have a better model for writing down what we see that can
get looked at when folks are around to poke at the issues.
-Sean
--
Sean Dagu
s there a problem with my query or the backend?
>
> Just to be clear, I don't mean this email to sound like I'm complaining, I'm
> just confused and looking for help.
>
>
> Yours Tony.
>
>
>
> ___
> OpenStack-Infra m
On 10/16/2015 10:24 AM, Matthew Treinish wrote:
> On Fri, Oct 16, 2015 at 08:51:21AM -0400, Sean Dague wrote:
>> On 10/16/2015 07:45 AM, Tony Breeds wrote:
>>> Hi Everybody,
>>> So it looks to me like we recently updated logstash.openstack.org to a
>>> ne
> Just to be clear, I don't mean this email to sound like I'm complaining, I'm
> just confused and looking for help.
I noticed that we've appeared to deploy v3.1.2, which was released Nov
2014. Is there a reason we're not on 4.1.2 which is a more recent version?
's resolved, our DB2 CI will not publish result
>> to community.
>>
>> Actually, not long ago, we met merge failure errors. We configured our zuul
>> to stop publishing "Merge failure" errors on specific patch. But we were
>> not aware that patches that depends
at deal of confusion when addressing a cross
repo patch series recently. Hence my annoyance and reporting.
-Sean
--
Sean Dague
http://dague.net
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
, and I'd like the
CI system turned off if it's not fixed in the near term.
-Sean
--
Sean Dague
http://dague.net
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
On 04/03/2015 12:12 PM, Monty Taylor wrote:
> On 04/03/2015 12:06 PM, Jeremy Stanley wrote:
>> On 2015-04-03 11:54:00 -0400 (-0400), Sean Dague wrote:
>> [...]
>>> 2) is there an event stream of changes (either real time or rss) that
>>> can be consumed by sai
data transformation can be
> found here:
>
> https://github.com/emonty/puppet-phabricator
>
> It's not perfect - but I figured that a conversation can't really be had
> without something to point at.
2 specific phabricator questions (which I'm running into in dealin
perator intends: let this repo manage layouts
> for itself.
>
> BTW, having this is really interesting because in theory one can disable
> a job that a change breaks in the same patch, or enable a job in the
> same change that fixes it. I really like that aspect.
Agreed, I think that
orkspace-new.txt.gz#_2015-02-11_04_00_05_825
However because of the name mismatch devstack isn't picking it up.
Will try to tighten this up in the future to make the issues more obvious.
-Sean
--
Sean Dague
http://dague.net
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
On 12/03/2014 12:38 PM, Elizabeth K. Joseph wrote:
> On Wed, Dec 3, 2014 at 9:09 AM, Sean Dague wrote:
>> On 12/03/2014 12:03 PM, Elizabeth K. Joseph wrote:
>>> Hi everyone,
>>>
>>> I do a fair number of presentations about our infrastructure, and a
>>&g
lications/sysadmin-codereview/#(4)
> [1] http://commondatastorage.googleapis.com/gerrit-static/diffy-w200.png
>
--
Sean Dague
http://dague.net
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
python -m SimpleHTTPServer
... to manually verify
And how does setup.py install for this project do the right thing?
-Sean
--
Sean Dague
http://dague.net
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
t the app
would still work)?
- Regardless of where they go, how should we get them there via puppet?
- wget + file install?
- npm ?
- bower?
- some 3rd thing?
Would be good to have a pattern here so we can repeat as required in the
future.
-Sean
--
Sean Dague
h
Cloudwatt seems to have some jenkins environment up and is spamming a
ton of people with Jenkins messages.
There is no contact info that looks real here, so I don't know how to
direct connect them. Can anyone in infra / 3rd party testing reach out
to them?
-Sean
Forwarded Messa
#x27;t make anything better, it would just also stall out ceilometer
and marconi unit tests in the same scenario.
I think the real issue is to come up with a fairer algorithm that
prevents any node class from starving, even in the extreme case. And get
that implemented and accepted i
mix of nodes that we need any given hour
kind of changes. But as jeblair said, this is non trivial to implement.
Ensuring a minimum number of nodes (where that might be 1 or 2) for each
class would have helped this particular situation. We actually had 0
nodes in use or ready of the type at the
eed to figure out pretty soon if we can keep Elastic
Search or we should start considering other options.
-Sean
--
Sean Dague
http://dague.net
signature.asc
Description: OpenPGP digital signature
___
OpenStack-Infra mailing list
OpenS
functional tests.
Honestly, though, this is currently having the good side effect of
running tests an extra set of times on people's code. And given that the
biggest issue we are fighting right now is that too many bugs landed,
running tests on change sets more times before they go
on.
Ian, thanks for this really clear roadmap. I've gone through and left
feedback on most of the patches. This is looking pretty good, just a
couple of things I think we need to clean up first.
-Sean
--
Sean Dague
http://dague.net
signature.asc
Description: OpenPGP digita
empest core team, without infra needing to be involved.
However, I'm not sure I see a path in how that would happen given the
weird gerrit ref structure. Anyone have thoughts on a sane way to do that?
-Sean
--
Sean Dague
http://dague.net
signature.asc
Descript
a/config/tree/modules/openstack_project/files/nodepool/scripts
I can't speak to #1, however I'm +1 on this effort. Would love to have
devstack running on Fedora as well on changes in general, and especially
on devstack, as we accidentally break Fedora f
d be a great Summit Session for Atlanta as
hopefully we'll have some prelim work happening and can figure out next
steps.
This - https://github.com/sdague/devstack-vagrant - has some
demonstration of multi node devstack in a local environment. There may
be handy bits in there to figure out how
On 03/18/2014 07:49 AM, Monty Taylor wrote:
> On 03/18/2014 06:55 AM, Sean Dague wrote:
>> On 03/18/2014 06:04 AM, Thierry Carrez wrote:
>>> Monty Taylor wrote:
>>>> Which means, although I tend to have a side which agrees with Clint and
>>>> Clark tha
letes). It also means
that for UI that wasn't completed yet, it could fall back to gerrit
interfaces.
Anyway, realize that unlike launchpad, gerrit actually has fans. And
while I 100% agree Google doesn't know how to run an open source project
(which I think is the a challenge for any org
idea¹s for integration are purely through API. Integrating beyond that
> will cause more headaches they benefits it might create.
Have you considered other open source efforts to build upon, like
phabricator? That came up on IRC a few nights ago by Ryan Lane. And it
seems like a lot of mileage
lib/jenkins/devstack/lib/nova:618:git_clone
> 2014-03-11 14:14:02.324 |
> /var/lib/jenkins/devstack/functions-common:543:git_timed
> 2014-03-11 14:14:02.326 | /var/lib/jenkins/devstack/functions-common:596:die
> 2014-03-11 14:14:02.327 | [ERROR]
> /var/lib/jenkins/devstack/funct
se OS is 12.04 Precise.
>
> The problem is intermittent in that it takes maybe 15 to 20 cycles of
> unstack/stack to get it into the failure mode, but once in the failure mode,
> it appears that tgt daemon is 100% dead-in-the-water.
>
> -Original Message-
> From: Sean
gt; http://128.107.233.28:8080/job/neutron/1390/artifact/vpnaas_console_log.txt
> http://128.107.233.28:8080/job/neutron/1390/artifact/vpnaas_stack_sh_log.txt
>
> Does anyone have any advice on how to debug this, or recover from this
> (beyond rebooting the node)? Or am I missing any Cinder config?
>
> Thanks in advance for any help
>
>> --
>> Antoine "hashar" Musso
>>
>> ___
>> OpenStack-Infra mailing list
>> OpenStack-Infra@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
>
&g
On 02/24/2014 04:46 AM, Antoine Musso wrote:
> Le 24/02/2014 02:09, Sean Dague a écrit :
>> After seeing grenade jobs fail the inner / outer timeout because it
>> turns out there are > 5 minutes of time outside the main run job, I
>> pulled together this new approach - http
hat happen?
-Sean
--
Sean Dague
Samsung Research America
s...@dague.net / sean.da...@samsung.com
http://dague.net
signature.asc
Description: OpenPGP digital signature
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
h
experimental
jobs are done.
We've seen really substantial delays, plus a 5 day complete outage a
week ago, on the tripleo cloud. I'd like to see that much more proven
before it starts to impact core projects, even in experimental.
-Sean
--
Sean Dague
Sams
they do, and often
> times we're not told what they do when we set up an account.
I do like the idea of a requirement of a bot is to provide a link back
to a learn more page about it.
I think it would be educational for everyone.
-Sean
--
Sean Dague
Samsung Research America
s..
could have been happening earlier than that).
-Sean
--
Sean Dague
Samsung Research America
s...@dague.net / sean.da...@samsung.com
http://dague.net
signature.asc
Description: OpenPGP digital signature
___
OpenStack-Infra mailing list
Open
Question: is there any way to get gerrit to generate the idempotent ids
on a revert through the web ui?
Because today it does not. So if you want to amend the commit message it
means you end up pushing a second change.
-Sean
--
Sean Dague
Samsung Research America
s...@dague.net
On 01/19/2014 11:38 PM, Joe Gordon wrote:
>
>
>
> On Sun, Jan 19, 2014 at 7:01 AM, Monty Taylor <mailto:mord...@inaugust.com>> wrote:
>
> On 01/19/2014 05:38 AM, Sean Dague wrote:
>
> So, we're currently 70 deep in the gate, top of queue we
On 01/19/2014 03:50 PM, Michael Still wrote:
> On Sun, Jan 19, 2014 at 11:01 PM, Monty Taylor wrote:
>> On 01/19/2014 05:38 AM, Sean Dague wrote:
>
> [snip]
>
>>> = Periodic recheck on old changes =
>>>
>>> I think Michael Still said he was working o
, tend to approve things with really stale test
results (> 1 month old). These fail, and then tumble. They are a be
source of the wrecking balls.
Tests results > 1 week are clearly irrelevant. For something like nova,
> 3 days can be problematic.
I'm sure there are some other id
it will
always timeout waiting for results of the first failure that it gets,
then if you get lucky, it might classify the 2nd fail.
Given that, we really need to be tracking and alerting on ES delays some
how, otherwise we're going to loose a lot of the value on this.
-Sean
--
Sean
report on a bug, but it did not, because ER actually
waits for all expected files to land for a job (console.html is a
required file) before it reports.
-Sean
--
Sean Dague
Samsung Research America
s...@dague.net / sean.da...@samsung.com
http://dague.net
___
the differences, but it would
demonstrate another metric about failure.
If it was put in the console log crm114 might even pick it up as likely
reason for the failure.
-Sean
--
Sean Dague
http://dague.net
___
OpenStack-Infra mailing list
On 01/03/2014 12:15 PM, Antoine Musso wrote:
Le 02/01/14 16:35, Sean Dague a écrit :
For instance, Gerrit 2.5 added the ability to put UnifiedDiffs in email
templates, which would let you know if the review in question touched
files that you like to keep an eye on (and trigger local filtering
.
We also apparently got custom dashboards somewhere along the way.
What's actually currently blocking the upgrade? Is it just time? or are
we still waiting on feature(s)? If so, do those feature(s) outweigh what
we are missing by being so far behind master?
-Sean
--
Sean Dague
Sa
On 12/19/2013 05:58 AM, Thierry Carrez wrote:
> Sean Dague wrote:
>> I think there are 2 approaches that I see being fruitful, depending on
>> the kind of problem the team is going after.
>>
>> 1) the yaml -> ical converter.
>>
>> Bulk of invention i
ld be that a lot of the UI and ical bits would be handled
already.
I've got experience both ways, so hit me up on irc with questions on
either approach.
-Sean
--
Sean Dague
http://dague.net
signature.asc
Description: OpenPGP digital signature
and have done a
bunch of fixing of the drupal implementation), I'd just say do this in
ical native with a validator.
ical is ugly, but it's mostly understandable (and I'd be happy to mentor
on it). For the intents and purposes for this it would probably be fine.
-Sean
--
S
/stable/grizzly/exercises/aggregates.sh#L101
to be more permissive for the new UI format. (It's L104 in master, and
probably should be synced master, havana, & grizzly).
Once that is done, the change could go forward, and should pass grenade.
-Sean
--
Sean Dague
http://
s so many nice features of negotiation worked into the
spec, which we're actually using today, and makes life easier for folks.
And I'd really like to not loose that.
So 2a has strong vote from me.
-Sean
--
Sean Dague
http://dague.net
_
ng the way. "Outsource" is the wrong model.
-Sean
--
Sean Dague
http://dague.net
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
;>
>> Even without gating, the advisory reporting from smokestack is hugely
>> valuable. I think any increase in reliability and speed (such as
>> automating the failure detection as you were talking about) will be
>> perceived by the review community and they will act ac
enstack-qa mailing list
openstack...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa
--
Sean Dague
IBM Linux Technology Center
email: sda...@linux.vnet.ibm.com
alt-email: slda...@us.ibm.com
___
OpenStack-Infra ma
This is up for review now - https://review.openstack.org/#/c/20762/
And would turn on full tempest in the gate assuming all the affected
PTLs sign off on it, feedback welcomed.
-Sean
--
Sean Dague
IBM Linux Technology Center
email: sda...@linux.vnet.ibm.com
alt-email: slda
60 matches
Mail list logo
