- Mail original -
> De: "Swapnil Kulkarni"
> À: "OpenStack Development Mailing List (not for usage questions)"
>
> Envoyé: Lundi 4 Décembre 2017 12:57:36
> Objet: Re: [openstack-dev] [rally]404 on docker rallyforge/rally
>
> On Mon, Dec 4, 2
Hi,
Monday morning and it seems that docker images for rally aren't reachable
anymore.
https://hub.docker.com/r/rallyforge/rally/
Did I miss something ? Is the doc up-to-date[1] ?
[1]:
http://rally.readthedocs.io/en/0.10.0/install_and_upgrade/install.html#rally-docker
Matt
_
Hi all,
The next meeting is planned tomorrow/today
Wed. 11 Oct. 15:00 UTC
A draft agenda is available in the etherpad :
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017
(line 1317 - at the end)
You are very welcome to amend it.
Best,
Matt
- Mail original -
> D
hould have stored them in github
> or something. It shouldn't be hard to replicate though if you follow the
> oslo_messaging docs.
>
>
>
> On Wed, Sep 20, 2017 at 9:58 AM, Matthieu Simonin > wrote:
>
> > Hello,
> >
> > In the Neutron docs about R
Hello,
In the Neutron docs about RPCs and Callbacks system, it is said[1] :
"With the underlying oslo_messaging support for dynamic topics on the receiver
we cannot implement a per “resource type + resource id” topic, rabbitmq seems
to handle 1’s of topics without suffering, but creating 100’
emand :)
Best,
Matt
- Mail original -
> De: "Matthieu Simonin"
> À: "OpenStack Development Mailing List (not for usage questions)"
>
> Envoyé: Jeudi 6 Juillet 2017 16:31:46
> Objet: Re: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman proposal
&g
Hello,
If it helps, we are building on a regular basis a subset of the kolla images.
They are pushed in dockerhub under beyondtheclouds namespace [1].
stable/ocata images should be up-to-date, master is tagged latest.
Nevertheless some caveats of relying on those tags are mentionned in this
thr
en notification and RPC messaging is interesting in this area.
Bye,
Matt
>
> Regards,
>
> Paul-Andre
>
>
>
> -Original Message-
> From: Matthieu Simonin
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> Paul-Andre
>
>
> -Original Message-
> From: Matthieu Simonin
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: Wednesday, June 21, 2017 at 6:54 PM
> To: "OpenStack D
Hi Ken,
Thanks for starting this !
I've made a first pass on the epad and left some notes and questions there.
Best,
Matthieu
- Mail original -
> De: "Ken Giusti"
> À: "OpenStack Development Mailing List (not for usage questions)"
>
> Envoyé: Mercredi 21 Juin 2017 15:23:26
> Objet: [o
- Mail original -
> De: "Thierry Carrez"
> À: openstack-dev@lists.openstack.org
> Envoyé: Lundi 22 Mai 2017 11:02:21
> Objet: Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master
>
> Mike Bayer wrote:
> > On 05/18/2017 06:13 PM, Adrian Turjak wrote:
> >>
> >> So, specifi
deploy files
>
> On Mon, May 29, 2017 at 4:08 AM, Matthieu Simonin > wrote:
>
> > Hello,
> >
> > I'd like to have more insight on OSProfiler support in paste-deploy files
> > as it seems not similar across projects.
> > As a result, the way you can e
- Mail original -
> De: "Eduardo Gonzalez"
> À: "OpenStack Development Mailing List (not for usage questions)"
>
> Envoyé: Lundi 29 Mai 2017 11:53:53
> Objet: Re: [openstack-dev] [kolla][osprofiler][keystone][neutron][nova]
> osprofiler in paste deploy files
>
> Hi Matt,
>
> A), As
Hello,
I'd like to have more insight on OSProfiler support in paste-deploy files as it
seems not similar across projects.
As a result, the way you can enable it on Kolla side differs. Here are some
examples:
a) Nova paste.ini already contains OSProfiler middleware[1].
b) Keystone paste.ini do
- Mail original -
> De: "Jay Pipes"
> À: openstack-dev@lists.openstack.org
> Envoyé: Vendredi 6 Janvier 2017 21:42:46
> Objet: Re: [openstack-dev] [kolla] Multi-Regions Support
>
> On 01/06/2017 03:23 PM, Sam Yaple wrote:
> > This should be read as MariaDB+Galera for replication. It is
o-yaml) :
graph:
- [A, B],1
- [B, C],2
- [C, A],3
- [A, B],4
- [B, C],5
- [C, A],6
all pairs with a number less or equal to the concurrency will be considered
active.
>
> Please check whether my approach suits your use case, feedback appreciated
> :)
I like it !
>
> Thanks,
&
shouldn't be hard to implement though. Let me check what needs to be
> done.
>
> Thanks,
> Ilya
>
> 2016-11-24 13:49 GMT+03:00 Matthieu Simonin :
>
> > Hello,
> >
> > I'm looking to shaker capabilities and I'm wondering if this kind
> > of
Hello,
I'm looking to shaker capabilities and I'm wondering if this kind
of accomodation (see attachment also) can be achieved
Ascii (flat) version :
CN1 (2n VMs) <- n flows -> CN2 (2n VMs)
CN1 (2n VMs) <- n flows -> CN3 (2n VMs)
CN2 (2n VMs) <- n flows -> CN3 (2n VMs)
In this situation conc
er will join our team
on July, the 1st. He can re-implement ROME from scratch in an appropriate way
(as we know now what is required to make Nova work with Redis, and with the
support of OpenStack core-developers, we would be able to improve our
proposition and continue to increase its performance)
- Mail original -
> De: "Edward Leafe"
> À: "OpenStack Development Mailing List (not for usage questions)"
>
> Envoyé: Samedi 23 Avril 2016 19:12:03
> Objet: Re: [openstack-dev] [nova] Distributed Database
>
> On Apr 23, 2016, at 10:10 AM, Thierry Carrez wrote:
>
> >> I think replac
20 matches
Mail list logo
