cor...@inaugust.com (James E. Blair) writes:
> Hi,
>
> Gerrit will be unavailable for a few hours starting at 1500 UTC on
> Saturday, March 21.
Gerrit is up and running on the new server. Actual downtime was about 1
hour from 1500 to 1600.
Please let us know either here or on
Hi,
Gerrit will be unavailable for a few hours starting at 1500 UTC on
Saturday, March 21.
Also, as Jeremy indicated in this email, its IP address will be changing:
http://lists.openstack.org/pipermail/openstack-infra/2015-February/002425.html
If you use Gerrit from a network with egress filt
Announcing Gertty 1.1.0
===
Gertty is a console-based interface to the Gerrit Code Review system.
Gertty is designed to support a workflow similar to reading network
news or mail. It syncs information from Gerrit to local storage to
support disconnected operation and easy man
Emilien Macchi writes:
> Infra & Puppet folks,
>
> I'm volunteer to be part of OPW mentors for round 5 (May 2015 to August
> 2015).
>
> Since my background in OpenStack is mainly focused on automation &
> Puppet, I think I could find a topic related to this for the next round.
>
> This is a full-
"Heald, Mike" writes:
> This shows the time taken in seconds by each nodepool task
> (e.g. AddFloatingIPTask). Yes, it's slow, but consistent. During high
> load, the tasks only get more densely packed, they don't get slower.
Quickly scanning the logs we see upstream, I think we are seeing rough
Ian Wienand writes:
> Hi,
>
> Firstly, being someone who is trying to keep several images going in
> nodepool and being some distance away from the nodepool servers, the
> current situation of it logging to a single rather large file is often
> annoying. Yes I do know how to use grep, but IMO th
Hi,
I've been wanting to make some structural changes to Zuul to round it
out into a coherent system. I don't want to change it too much, but I'd
also like a clean break with some of the baggage we've been carrying
around from earlier decisions, and I want it to be able to continue to
scale up (t
A group of folks from HP is interested in starting an effort to run a
cloud as part of the Infrastructure program with the purpose of
providing resources to nodepool for OpenStack testing. HP is supplying
two racks of machines, and we will operate each as an independent cloud.
I think this is a re
"Bruns, Curt E" writes:
> Problem Statement:
> When a review fails pep8 style checks, a developer has to dig through
> the logs to figure out what failed. e.g. In this review
> https://review.openstack.org/#/c/151737/, there is a pep8 failure. A
> developer has to click on the Jenkins gate-cinde
"Sullivan, Jon Paul" writes:
>> A change may depend on more than one Gerrit change ID as well. So it is
>> possible for a change in tempest to depend on a change in devstack and a
>> change in nova. Simply add more "Depends-On:" lines to the footer.
>
> Have you considered a case where changes
Amrith Kumar writes:
> This is awesome news!
>
> If I understand correctly, your description of "multiple changes"
> describes cases where a single change depends on multiple changes. My
> question is related to one-to-one dependencies in the form A -> B ->
> C.
>
> I'm assuming that this is supp
Hi,
We have added support for cross-repo dependencies (CRD) in Zuul. The
important bits:
* To use them, include "Depends-On: " in the footer of
your commit message. Use the full Change-ID ('I' + 40 characters).
* These are one-way dependencies only -- do not create a cycle.
* This is what a
cor...@inaugust.com (James E. Blair) writes:
> Hi,
>
> The Infrastructure program has a unique three-tier team structure:
> contributors (that's all of us!), core members (people with +2 ability
> on infra projects in Gerrit) and root members (people with
> administrative a
Hi,
As part of an effort to better support re-use of the Infrastructure
program's software, tooling, and systems-administration work, we have
moved all of our puppet modules out of the system-config repository.
Now each of them may be found in its own git repo, such as
openstack-infra/puppet-zuul
Hi,
The Infrastructure program has a unique three-tier team structure:
contributors (that's all of us!), core members (people with +2 ability
on infra projects in Gerrit) and root members (people with
administrative access). Read all about it here:
http://ci.openstack.org/project.html#team
El
Hi,
On Friday, January 30 at 19:00 UTC Gerrit will be unavailable for about
30 minutes while we rename some projects. Existing reviews, project
watches, etc, should all be carried over. Currently, we plan on
renaming the following projects (this list is subject to change):
openstack/oslo.ve
Ricardo Carrillo Cruz writes:
> Hi there
>
> I was writing a spec for an issue tracker agnostic update_bug.py on Jeepyb
> when this Story comment from Khai came to my attention:
>
> https://storyboard.openstack.org/#!/story/212
>
> "
> We should probably just deprecate jeepyb at this point. T
We have moved (most) project configuration data out of the
openstack-infra/config repository into a new repository called
openstack-infra/project-config.
This repo contains only config files related to configuring software
projects in the OpenStack project infrastructure. This includes:
* Zuul
Hi,
On Thursday, Sept 25 at 00:01 UTC we will freeze project-configuration
related changes to the openstack-infra/config repo.
This is part of an effort to move project-related configuration out of
the config repository and into its own repo. The goals are both to make
the existing config repo (
Ying Chun Guo writes:
> So I propose to create a translation check website on top of openstack
> infrastructure.
> It is a simple devstack setup where almost all services are enabled.
> Transifex translations are synchronized regularly, by cron in Akihiro's
> env.
> I think a regular Jenkins job
I just released 1.0.1 with some bug fixes for issues found by early
adopters. Thanks!
-Jim
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
cor...@inaugust.com (James E. Blair) writes:
> If you're ready to give it a shot, here's what to do:
>
> pip install gertty
> wget
> https://git.openstack.org/cgit/stackforge/gertty/plain/examples/openstack-gertty.yaml
> -O ~/.gertty.yaml
> # edit ~/.gertt
Announcing Gertty 1.0.0
Gertty is a console-based interface to the Gerrit Code Review system.
If that doesn't sound interesting to you, then just skip right on to
the next message. This mailing list gets a lot of traffic, and it's
going to take you a while to read it all in that web browser you'
"Bailey, Darragh" writes:
> Hi,
>
> Any chance that zuul could report back a 'WARNING' in yellow for non-voting
> jobs that fail? Still useful to know that it ran.
>
> Seems just a little too easy to miss that the text is different.
Sure, we're actually just overriding 'SUCCESS' and 'FAILURE',
Hi,
Jenkins-job-builder runs a job called "jenkins-job-builder-compare-xml"
which runs JJB master against openstack's JJB config, then runs it again
with the proposed change and compares the output.
Instead of success/failure, what it does is reports whether the output
changed or not. If you fol
Stefano Maffulli writes:
> On Fri 29 Aug 2014 12:47:00 PM PDT, Elizabeth K. Joseph wrote:
>> Third-party-request
>>
>> This list is the new place to request the creation or modification of
>> your third party account. Note that old requests sent to the
>> openstack-infra mailing list don't need t
Hi,
Gerrit will be unavailable starting at 1600-1630 UTC on Saturday,
August 30, 2014 to rename the glance.store project to glancestore.
I apologize for the late notice, however, in another thread on the -dev
list, you'll find the rationale for executing this change swiftly.
Thanks,
Jim
__
Yi Xuan YX Zhang writes:
> Hi Jim,
>
> Could you help to re-enable my service account since I have fixed the
> issue and I have move to project sanbox?
Done. Thanks!
-Jim
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://
"trinath.soman...@freescale.com" writes:
> Hi Jim-
>
> As you said,
>
> [ Strictly speaking, that will mean that every patchset will go through the
> merger and Jenkins.
>But if testing for a patchset is in progress when a new patchset is
> uploaded, the tests will abort. ]
>
>
> Th
Jeremy Stanley writes:
> On 2014-08-21 15:11:13 -0700 (-0700), James E. Blair wrote:
> [...]
>> Strictly speaking, that will mean that every patchset will go through
>> the merger and Jenkins. But if testing for a patchset is in progress
>> when a new patchset is upload
"trinath.soman...@freescale.com" writes:
> Hi-
>
> I configured Zuul with paramater, 'dequeue-on-new-patchset: true'.
>
> With this, for a change, if multiple patchsets are in queue, only the latest
> must be taken and rest all to be ignored.
>
> But I noticed that every patchset is going to zuu
Hi,
I have disabled the above CI system because it is in violation of the
following policies:
* Include a public link to all test artifacts.
In the change https://review.openstack.org/#/c/111460/ this system
left a link to:
http://172.31.18.245:8080/job/dsvm-tempest-full-dpl/159/
Which did
Hi,
I have disabled the above CI system because it is in violation of the
following policies:
* Include a public link to all test artifacts.
In the change https://review.openstack.org/#/c/111460/ this system
left a link to:
http://hood:8080/job/noop-check-communication/116/
Which did not re
Hi,
I have disabled the above CI system because it is in violation of the
following policies:
* Include a public link to all test artifacts.
In the change https://review.openstack.org/#/c/111460/ this system
left a link to:
http://9.115.251.56:8080/job/dsvm-tempest-full/78/
Which did not re
Hi,
I have disabled the above CI system because it is in violation of the
following policies:
* Include a public link to all test artifacts.
This system did not leave results at all, only "starting" comments.
Additionally, it was leaving "Starting check jobs" comments which is
unnecessary for
John Griffith writes:
> Yep, you're absolutely correct. This has been pointed out to folks and
> they're working on it. It might be a few days before it's taken care of
> but they are aware and have *promised* to get it sorted.
In the mean time, I'm happy to help everyone avoid the spam by dis
Hi,
We've updated the registration requirements for third-party CI systems
here:
http://ci.openstack.org/third_party.html
We now have 86 third-party CI systems registered and have undertaken an
effort to make things more user-friendly for the developers who interact
with them. There are two i
Matthew Treinish writes:
> Hi Everyone,
>
> Just a quick update, we have to close registration for the Infra/QA mid-cycle
> meet-up. Based on the number of people who have signed up on the wiki page [1]
> we are basically at the maximum capacity for the rooms we reserved. So if you
> had intended
Hi,
We've got a lot of people interested in working on puppet, which is
great. I'm hoping that as a result, we'll have a much cleaner and more
re-usable system. But at the moment, the primary purpose of what's in
the openstack-infra/config repo is to run the systems for the OpenStack
project. W
Chmouel Boudjnah writes:
> Just make sure you first start order wine and finish on beer, that's the
> way to drink here :) (but the mix will be heavy for the next morning)
start with wine, finish on beer
that's the way to drink o'er here
-jim
___
Ope
Thierry Carrez writes:
> So it looks like we should proceed with supporting proposed/foo on
> prerelease, but I wanted to do a last-minute check to make sure everyone
> was still OK with that.
That matches my recollection and I still think it's a good idea. We
probably need to update scripts in
Hi,
The Jenkins Job Builder project (part of the Infrastructure program) is
quite popular even outside of OpenStack and has a group of specialist
core reviewers supplemental to the rest of the Infrastructure program.
To that group I would like to add Darragh Bailey:
https://review.openstack.org/
Ian Wienand writes:
> On 06/19/2014 01:18 AM, James E. Blair wrote:
>> (This requires tracking a bit more state across allocation runs).
>
> This seems to be the crux of the matter; once we have some state all
> sorts of things become possible.
>
> I've made a pro
Ian Wienand writes:
> but eventually, at 30:1, the fedora node gets dropped
I think the formula at work for deciding if a single marginal node
should be allocated as a precise node is:
(demand_for_precise / total_demand) * available_nodes
Eg, round(20/40*1) = 1 so it's allocated as precise;
"trinath.soman...@freescale.com" writes:
> Hi-
>
>
> With Zuul version, 2.0.0.155, I'm facing a problem with layout.yaml
>
>
> The projects section is as follows in layout.yaml.
>
> projects:
> - name: openstack-dev/sandbox
> check:
> - TEST-SANDBOX
>
> but when the gerrit event arriv
Hi,
At the project meeting today, I cornered the PTLs and got consensus that
we should be using PROGRAM-specs as the name for the specs repos. Eg,
"compute-specs" instead of "nova-specs". This is to better support
programs with multiple projects (such as client and server projects).
Short names
"Elizabeth K. Joseph" writes:
> On Mon, May 19, 2014 at 9:40 AM, Elizabeth K. Joseph
> wrote:
>> Hi everyone,
>>
>> The OpenStack Infrastructure (Infra) team is hosting our weekly
>> meeting on Tuesday May 20th, at 19:00 UTC in #openstack-meeting
>
> Great post-summit meeting, thanks to everyone
Jerry Xinyu Zhao writes:
> Better send to infra's list too.
>
>
>
> On Mon, May 19, 2014 at 10:06 AM, Yi Sun wrote:
>
>> More info, I add a follow up comment on an old change set, and then it
>> happened.
>> Yi
>>
>>
>> On Mon, May 19, 2014 at 2:49 AM, Carlos Gonçalves wrote:
>>
>>> I was able t
On May 10, 2014 7:37:36 AM EDT, Andreas Jaeger wrote:
>On 05/10/2014 09:22 AM, Andreas Jaeger wrote:
>> My patch https://review.openstack.org/#/c/93129/ to inject properties
>> failed, see for example
>>
>http://logs.openstack.org/24/93124/1/check/gate-openstack-manuals-tox-doc-publish-checkbuild/
"Elizabeth K. Joseph" writes:
> On the Debian side, I also have a bug (with some mirror discussion and
> an attached review) here:
>
> https://bugs.launchpad.net/openstack-ci/+bug/1311855
>
> After discussing this particular patch+bug with the rest of the -infra
> team, there wasn't a ton of inte
Hi,
If you've proposed an infra session for the summit, would you please
make sure that you have started an etherpad for it and that it is listed
in the wiki? It should have a summary of the items you would like to
cover and potential outcomes.
You can find the index of etherpads here:
https:
"Kevin L. Mitchell" writes:
> On Wed, 2014-04-30 at 12:14 -0400, Anita Kuno wrote:
>> Are you able to file a bug with this information? It will help us track
>> progress on this easier than an email thread. If you reply with a link I
>> will confirm the bug.
>
> Sure, I just wasn't sure where to
"Cazzolato, Sergio J" writes:
> Hi,
>
> I am working on a bug (by another author) which has been automatically moved
> to abandoned.
>
> Is it possible to restore it? Any way to assign it to me?
>
> https://review.openstack.org/#/c/15104/
Done.
-Jim
___
Ian Wienand writes:
> Then we have the question of the nodepool setup scripts working on
> F20. I just tested the setup scripts from [3] and it all seems to
> work on a fresh f20 cloud image. I think this is due to kchamart,
> peila2 and others who've fixed parts of this before.
>
> So, is ther
Jérôme Gallard writes:
> Hi James,
>
> Thanks for your answer!
> As Mathieu said, we are currently working on the multi-node part of the
> project and try to understand how the multi-node feature of nodepool could
> be used by the other components of the infra.
>
> Does something like the followi
Jérôme Gallard writes:
> Hi all,
>
> I see the very nice set of patches merged for multi-node in nodepool.
> Now that this part is done, will the next step be to modify devstack-gate
> to allow it to take advantage of the new multi-node feature of nodepool?
> There is already some work on that pa
Tom Fifield writes:
> On 31/03/14 11:15, Ying Chun Guo wrote:
>> So in order to support build of Korean document, I need to add Korean
>> font files to document build server.
>> Please guide me how to do it.
>
> I believe it's just a matter of getting the following packages
> installed via some p
jebl...@openstack.org (James E. Blair) writes:
> If you're running nodepool from master, note that when this change
> merges, you will need to change your config file and either alter or
> drop the node table (to change the 'image_name' column to 'label_name').
Clint Byrum writes:
>> * The model does not specify an engine for MySQL (this is a difference
>>between the model and the alembic migrations). So when the unit tests
>>are run on MySQL, they may end up on MyISAM (they do in the gate).
>>
>
> Why MyISAM? The default has been InnoDB since
Hi,
I recently started looking into running the unit tests with MySQL. I
pushed the start of a change here to do that:
https://review.openstack.org/#/c/82872/
In particular, that change implements something we've wanted to do for a
long time elsewhere in OpenStack -- create a dedicated MySQL da
We've been discussing the thoroughly interesting problem of project
taxonomy recently, and I'd like to describe what I think we've mostly
decided we should do and make sure we're on the same page. If we are,
I'll invite the TC to weigh in and if they think we're completely wrong,
we can work on so
If you're running nodepool from master, note that when this change
merges, you will need to change your config file and either alter or
drop the node table (to change the 'image_name' column to 'label_name').
https://review.openstack.org/#/c/82147/
At some point I expect schema migrations and r
Khai suggested it's time (or past time) for a JJB release. Antoine
points out that before merging thread and pbr support might be a good
time for a release too. I note that we just fixed python 2.6 support as
well. So how about I tag:
6e72dc3781fcaed1526317c27762fba44cd8a43e
as 0.7.0?
-Jim
_
Antoine Musso writes:
> Hello,
>
> For a couple weeks I noticed the Zuul 'check' pipeline is being
> triggered when adding a single comment on an old patch.
>
> I find it annoying when a patchset review takes a couple weeks or so.
> The review would usually lead to a new patchset and I don't thin
"Aaron Greengrass" writes:
> ...
> 6. continued refactoring of all modules until:
> they can be used in any environmentthey can be used in puppet 2.7 or
> 3.x interchangeablythey don't implicitly include more than is
> required.
Thanks for this! I think that all sounds great. Regarding the las
Sean Dague writes:
> On 02/14/2014 03:43 PM, Robert Collins wrote:
>> Thanks to a massive push this week, both the seed *and* undercloud
>> jobs are now passing on tripleo-gate nodes, but they are not yet
>> voting.
>>
>> I'd kind of like to get them voting on tripleo jobs (check only). We
>> do
Antoine Musso writes:
> Seems the bottleneck is 400 or so fetches against a single host (Zuul).
> Maybe you could use the Gerrit replication system to replicate the git
> repositories to some mirror hosts then have Zuul push its references to
> them.
>
> Since Zuul publish the git repository to f
Hi,
When Zuul gets very busy, it can end up launching hundreds of jobs
nearly simultaneously. Each of them has to perform several git fetch
operations to obtain the changes needed for testing. They fetch from
the git repos on the Zuul server because Zuul itself is creating those
commits by local
"Varnau, Steve (Seaquest R&D)" writes:
> Antoine,
>
> Yes, I ran into same confusion recently. For dependent pipeline, Zuul will
> provide the same ZUUL_REF for each repo that has pipeline changes to test. So
> in test of second change, if you check out the $ZUUL_REF version for both
> repos,
Sean Dague writes:
> So as the review queues grow, and our gerrit becomes longer and longer
> in the tooth, we are now getting to the point where people are spending
> real time building local work arrounds for features lacking in gerrit
> 2.4 that have since been implemented upstream.
>
> For in
Thierry Carrez writes:
> Hi!
>
> There have been a few channel trolling situations in the past (in
> European mornings) where nobody present on the channel could solve the
> situation, and it made us look a bit bad.
>
> Current IRC chanserv op rights are limited to the infra-root team (4
> people
Hi,
Several folks who work on OpenStack infrastructure related projects will
be attending and speaking at linux.conf.au. Here are the ones I know
about:
* Systems Administration in the Open by Elizabeth Krumbach Joseph
http://linux.conf.au/schedule/30121/view_talk?day=wednesday
* Continuous I
Elizabeth Krumbach Joseph writes:
> If you rewind the publications repository back to commit
> 7eaa6ddf356ea00b4d798d6581000a42e063b531 you will get to the last
> change before our "delete everything" change and will see a bunch of
> directories, as you can see in the etherpad we split these off
jenk...@openstack.org writes:
> Build failed.
>
> - periodic-neutron-docs-grizzly
> http://logs.openstack.org/periodic-stable/periodic-neutron-docs-grizzly/98472d2
> : SUCCESS in 3m 30s
> - periodic-neutron-python26-grizzly
> http://logs.openstack.org/periodic-stable/periodic-neutron-python26-g
Lin BJL Liang writes:
> We're building CI system using puppet master. now we run into a problem
> that the log can't be published to the log server after job finished.
> Compared to the community jenkins, SCP plugin missed in my jenkins master
>
> I checked Jenkins.pp and Jenkins Job Builder conf
Hi,
Since they fall on the evenings of some major holidays, we're canceling
the next two Project Infrastructure meetings. Enjoy the holidays!
-Jim
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/
jebl...@openstack.org (James E. Blair) writes:
> Hi,
>
> The subject of a mid-cycle meetup for the infrastructure team has come
> up a few times recently, so I wanted to get an idea of who might be
> interested and what we want to get out of it.
>
> If you are interested i
Mate Lakat writes:
> Hi,
>
> We are working to get test coverage for XenServer, and wanted to share
> the ideas, to see if we are on the right path. The goal would be to use
> the official CI to run tests on XenServer.
>
> 1 - Installation
>
> So the issue, is that there is no XenServer image ava
jebl...@openstack.org (James E. Blair) writes:
> If you are interested in spending a few days focusing on OpenStack
> project infrastructure, would you please reply (privately is fine) with
> your area of interest. Some ideas:
Thanks for the replies so far -- but please make sure y
Hi,
The subject of a mid-cycle meetup for the infrastructure team has come
up a few times recently, so I wanted to get an idea of who might be
interested and what we want to get out of it.
If you are interested in spending a few days focusing on OpenStack
project infrastructure, would you please
Thierry Carrez writes:
> To script milestone-proposed branch creation, it looks like granting
> createReference to "Release managers" on refs/heads/proposed/* would do
> the job (although maybe the current "push" permission on
> "refs/for/refs/*" might already be enough). Then I suspect I could "
Stefano Maffulli writes:
> This lead us to give up trying for Hong Kong. We searched for
> alternatives (see the infra meeting logs a few months back and my
> personal experiments [1] based on UDS experience) and the only solid
> one was to use a land line to call in the crucial people that *h
Robert Collins writes:
> FWIW I want to put a testr front-end on all of this, to do fault
> correlation across test runs; this could be implemented a number of
> different ways, but I think the key thing is that we may want to stage
> things in a couple of different formats (raw, preprocessed for
Monty Taylor writes:
> On 10/10/2013 02:06 PM, Clark Boylan wrote:
>
> 1c - I think I'm pretty sold on as well. However, on what clark is
> saying, if we put the metadata for a run that _would_ be used for an
> index into a swift object, then we could, if we ever wanted one, write
> a log index s
Joshua Hesketh writes:
> On 9/25/13 2:47 AM, James E. Blair wrote:
>> Joshua Hesketh writes:
>>
>>> On 9/17/13 11:00 PM, Monty Taylor wrote:
>>>> On 09/16/2013 07:22 PM, Joshua Hesketh wrote:
>>>>> So if zuul dictates where a log goes and
Hi,
In Hong Kong there will be a design summit session to discuss
translation tools:
http://summit.openstack.org/cfp/details/169
>From our last round of evaluating tools, Pootle was a close second to
Transifex:
https://docs.google.com/spreadsheet/ccc?key=0Aqevw3Q-ErDUdFgzT3VNVXQxd095bFgzOD
Clark Boylan writes:
> On Tue, Oct 8, 2013 at 5:03 AM, Thierry Carrez wrote:
>> - would it be possible to reuse a classic repo clone (from git.o.o) and
>> add an option to git review to submit to the security gerrit ? Otherwise
>> we have to teach security patch developers to use specific clones
Ryan Lane writes:
> Making a provider is relatively simple and is a great way of providing SSO
> for a set of applications you maintain. There's a number of good provider
> implementations around. A good way of handling OpenID for our applications
> would be to make all of the applications use ou
Clint Byrum writes:
> Hello infra rockstars. First and foremost, thank you for keeping the
> well oiled machinery of the OpenStack infrastructure running. It is a
> marvel of modern engineering, and I am not just saying that because I
> am prone to hyperbole.
>
> Last night while the gate was exp
Joshua Hesketh writes:
> On 9/17/13 11:00 PM, Monty Taylor wrote:
>>
>> On 09/16/2013 07:22 PM, Joshua Hesketh wrote:
>>> So if zuul dictates where a log goes and we place the objects in swift
>>> with that path (change / patchset / pipeline / job / run) then zuul
>>> could also handle placing in
Robert,
Thank you for the excellent write up. I believe I understand in general
how this will work, and I agree with you about the non-technical aspects
(how to diversify and maintain this system in the long run).
Without getting too far into details, some of which may be better left
for a time
Paul Belanger writes:
> This was the only side effect of the silence change, we did see more
> 'hot mic' and background noise. I'd vote for another round of testing
> toggling some settings to see if we can find the sweet spot.
Shall we schedule another interactive session for this Friday at th
Joshua Hesketh writes:
> We could then use either psuedo folders[0] or have the worker generate
> an index. For example, why not create an index object with links to
> the other objects (using the known serving application URL prepended)?
> In fact, the reporter can choose whether to generate an
Thierry Carrez writes:
> Joshua Hesketh wrote:
>> Great overview and plan James, thanks for that :-).
>>
>> So it seems to me that we're duplicating the job of swift a little bit
>> by writing a program to accept an object over http and store it on disk.
>> If our end-game is logs stored in swif
Hi,
Thanks Russel, Paul, and everyone else who helped with the Asterisk
testing on Friday. Here's how I see the outcome:
The main problem we're trying to solve is that the audio is sometimes
choppy.
We found that moving the PBX to some specific Rackspace vms improved the
situation. Moving to a
Hi,
We're going to perform some testing of the Asterisk conference server
tomorrow, Friday September 6 at 1700 UTC. Hop into the #openstack-infra
channel if you want to help; we're going to be trying out several
different server configurations and will be dialing in several times.
Thanks,
Jim
Giri Basava writes:
> Hi,
>
> We are proposing a new project https://wiki.openstack.org/wiki/Raksha for
> OpenStack. Would like to have an IRC channel #openstack-raksha
>
> Can you guide us with the procedure to create this IRC channel? Thanks.
I've registered the channel with chanserv, so wh
Hi,
On Friday, August 16th at 1700 UTC, we'd like to get a bunch of people
calling into the Asterisk conference bridge in order to help load test
it. You can find connection instructions here (for SIP and PSTN):
https://wiki.openstack.org/wiki/Infrastructure/Conferencing
We'll use conference
Bob Ball writes:
> What are the thoughts on how an external system can add gating
> comments?
This is very unlikely to happen.
Multiple gating systems for one project (or set of projects in our case)
will not work. Zuul does quite a bit of work to try to merge changes as
quickly as possible, i
Congratulations to Khai Do, Arnaud Fabre, Mathieu Gagné, and Antoine
Musso who have all been added to the core developer group for Jenkins
Job Builder and can now approve or reject changes to the project!
http://lists.openstack.org/pipermail/openstack-dev/2013-July/012685.html
-Jim
_
201 - 300 of 312 matches
Mail list logo
