Hi All,
There will be no team meeting today.
As usual, if you have something please ping at #openstack-storlets
Thanks,
Eran
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi all,
We have not met for quite some time, and unfortunately, I cannot make it this
week as well.
Any chance Wed April 26th 08:00UTC. works for you as am alternative time.
Otherwise, you can make the meeting without me.
Best,
Eran
Hi All,
Any feedbacks?
Personally I like it.
Thanks,
Eran
> Begin forwarded message:
>
> From: Heidi Joy Tretheway <heidi...@openstack.org>
> Subject: Re: mascot for the storlets project
> Date: April 22, 2017 at 1:14:27 AM GMT+3
> To: Eran Rom <e...@itsonlyme.name&
Hi All,
As these are holidays in Israel i will not be able to make it today and in the
next two weeks.
Feel free to hold the meetings without me. Just coordinate via the mailing list
so that others can join.
If there is anything you would like to discuss. please ping on IRC in
Just a quick reminder.
When: Today, Thursday March 30, @09:00 and @19:00 UTC
Where: https://zoom.us/j/7922255193
More details below.
Thanks!
Eran
Storlets PTL
Hi All,
If you care about unstructured data processing, and face bandwidth difficulties
don?t miss this talk!
On March 30th (next
Hi All,
If you care about unstructured data processing, and face bandwidth difficulties
don’t miss this talk!
On March 30th (next Thursday) I will give a web talk on the above subject.
Abstract below.
The talk will be given twice that day. Details below.
If you wish to, but cannot make it
Heidi,
Thanks very much for the draft.
The mascot is awesome. I guess I am struggling with how to distinguish a stork
from a storklet: The mascot looks more like a stork.
I think that what distinguishes a stork chick from other similar chicks (of
e.g. herons / gannets / ) is the long and thick
Hi,
I have wrote a summary for the discussions we had in the Etherpad [1]
there is a summary section under each of the topics.
Otherwise, I will not be able to attend the meeting this Tuesday
as I will be on a flight back from the US.
Thanks,
Eran
[1]
So the hard work getting into the big-tent was worth it!
While the storlets team should have the final word, I will be very happy if the
Swift community helped us in the process.
Below are few options I have thought about.
Comments / other suggestions are mostly welcome!
Thanks very much,
Eran
Apologies for the date confusion in the below mail.
This should happen on the week of the 13th, and clearly we need to base our
branch on Swift’s Ocata branch.
> On Feb 1, 2017, at 10:37 AM, Eran Rom <e...@itsonlyme.name> wrote:
>
> Hi all,
> I will create the stable/ocata
Dear storleters,
As the deadline approaches I was thinking about the following idea:
End-to-End deep learning with OpenStack Storlets
Imagine that you have a huge dataset from which you could extract
information using machine learning algorithms. The problem is that
datasets usually need to
Hi all,
I will create the stable/ocata branch tomorrow my end of day.
Would be great if we can land the python functional tests.
Thanks!
Eran
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
These submissions will be evaluated next week and grantees will be
notified by Friday, January 20th.
Were people who were not granted also get notifications?
I am not sure if I was not granted or if I simply did not apply as I
thought I did.
Thanks very much!
Eran
Hi All,
I have been leading the Storlets project from its infancy days as
a research project in IBM to its infancy days as a big-tent project :-)
This would not have been possible without the small yet top and seasoned
developers in our community.
There is still very much I would like to do:
wrote on 16/05/2016 04:32:58 AM:
> From:
> To:
> Date: 16/05/2016 04:36 AM
> Subject: Re: [openstack-dev] [Storlets] Swift copy middlleware
>
> > I agree with Kota, and I think this is the easiest way to fix
Today the Swift team has merged copy middleware - congrats!
For us, however, it breaks the copy code path, which in fact can get much
simpler now.
As a quick and temporary resolution I have changes the tox.ini dependency
to be 2.7.0
Instead of master. We still need, however, to port the code
Hi All,
I suggest that until we have functional tests in place, each commit
message should specify that:
(1) For a code change - the system tests were executed successfully with
the change -
(2) For installation related change that the installation was tested with
this.
I further suggest that
17 matches
Mail list logo