+1
Looks so nice to me!
Thanks for the great illustration, Heidi!
Thank you,
Takashi
From: Eran Rom [mailto:e...@itsonlyme.name]
Sent: Monday, April 24, 2017 2:35 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev]
Hi Eran,
08:00 UTC is good for me.
I'm ok with Tuesday.
Thank you,
Takashi
-Original Message-
From: e...@itsonlyme.name [mailto:e...@itsonlyme.name]
Sent: Wednesday, July 20, 2016 2:28 AM
To: OpenStack Development Mailing List (not for usage questions)
Hi Eran,
Thanks for your suggestion.
Is it possible to make the meeting time one hour earlier (08:00 UTC) or one
hour later (09:00 UTC)?
Thank you,
Takashi
-Original Message-
From: e...@itsonlyme.name [mailto:e...@itsonlyme.name]
Sent: Wednesday, July 13, 2016 10:35 PM
To:
Hi Eran,
Thank you for bringing up a great idea.
> 1. Much easier to upgrade.
> 2. Less time from fix to test.
That's a big problem I experienced in my testing.
Storlet agent should be managed by infra operator side,
not by application developer side, as a part of infra software.
It's a little
> I agree with Kota, and I think this is the easiest way to fix the problem.
I noticed that placing storlets_middleware outside copy may require some
changes about slo handling,
because now it is assumed that storlets_middleware is placed "inside" slo,
right?
(I noticed this just after sending
Hi Eran and Kota,
> For temprary, that would work but I thought we could (*not sure*) fix the
> issue just replace the order of pipeline, right? (i.e. storlets handler
> should be the left of copy middleware) That is because the storlets middlware
> have the logic to translate
Hi,
I’m interested in container-sync to take a snapshot of swift.
I want to sync data between two swift clusters distributed in multiple
locations.
It is assumed that there are two swift clusters located in two places,
and the container-sync syncs data from one cluster to the other cluster