All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Li Wang <liwang@ubuntukylin.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: testing the teuthology OpenStack backend
Date: Wed, 19 Aug 2015 12:23:41 +0200	[thread overview]
Message-ID: <55D4592D.9060704@dachary.org> (raw)
In-Reply-To: <55D44D1A.10607@ubuntukylin.com>

[-- Attachment #1: Type: text/plain, Size: 2033 bytes --]

Hi,

[cc'ing the ceph-devel list for Zack or Andrew's input]

On 19/08/2015 11:32, Li Wang wrote:
> Hi Loic,
>   we did a test, the results are attached. We found that the
> network may be the bottleneck, it seems it will fetch all
> the packages from ceph website on the fly, that does take time
> and cause many failed jobs, and there are also many dead
> jobs, what do those mean? Do you have some suggestions,
> if possible to enable it fetch the packages from configurable
> mirror or even private package repositories?

You can ssh to the teuthology instance (the host that runs pulpito) and modify the ~/.teuthology.yaml with

   gitbuilder_host: gitbuilder.ubuntukylin.com

which will override the default of 

   gitbuilder_host: gitbuilder.ceph.com

I've never done that however and maybe Zack or Andrew have advices on how to establish a mirror properly.

I think having a private package repository that is useable by teuthology is complicated because the package locations, naming conventions and build methods are difficult to reproduce (and I don't fully understand what they are right now).

Cheers

> 
> Cheers,
> Li Wang
> 
> On 2015/8/8 23:23, Loic Dachary wrote:
>>
>>
>> On 08/08/2015 16:22, Li Wang wrote:
>>> Hi Loic,
>>>    Glad to talk with you on IRC about setting up
>>> the teuthology OpenStack backend. Once it is ready
>>> to run the test in private cloud, and the results
>>> could be exported and uploaded to a public place,
>>> please let me know asap :)
>>
>> I'm working on it, should be ready RSN.
>>
>>>
>>> Cheers,
>>> Li Wang
>>>
>>>
>>> On 2015/8/6 23:05, Loic Dachary wrote:
>>>> Hi,
>>>>
>>>> I'm looking into testing the OpenStack backend for teuthology on a new cluster to verify it's portable. I think it is but ... ;-) I'm told you have an OpenStack cluster and would be interested in running teuthology workloads on it. Does it have a public facing API ?
>>>>
>>>> Cheers
>>>>
>>

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2015-08-19 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 15:05 testing the teuthology OpenStack backend Loic Dachary
     [not found] ` <55C6108C.7010803@ubuntukylin.com>
     [not found]   ` <55C61F0C.3000903@dachary.org>
2015-08-10 13:09     ` Loic Dachary
2015-08-11  1:02       ` Li Wang
     [not found]     ` <55D44D1A.10607@ubuntukylin.com>
2015-08-19 10:23       ` Loic Dachary [this message]
2015-08-21  6:09         ` Zhou, Yuan
2015-08-21 16:45           ` Loic Dachary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55D4592D.9060704@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=liwang@ubuntukylin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.