From ildiko at openstack.org  Tue Aug  6 18:35:45 2019
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Tue, 6 Aug 2019 20:35:45 +0200
Subject: [Edge-computing] Edge Hacking Days - August 9, 16
In-Reply-To: <BDD4BB84-403A-4A0B-8102-1D8DAD7FB8BD@openstack.org>
References: <BDD4BB84-403A-4A0B-8102-1D8DAD7FB8BD@openstack.org>
Message-ID: <3E028E2F-4AB5-49D6-A754-4E0CD829155A@openstack.org>

Hi,

Based on the Doodle poll results __August 9 and August 16__ got the most votes.

You can find the dial in details on this etherpad: https://etherpad.openstack.org/p/osf-edge-hacking-days

If you’re interested in joining please __add your name and the time period (with time zone) when you will be available__ on these dates. You can also add topics that you would be interested in working on.

Potential topics to work on:
* Building and testing edge reference architectures
* Keystone testing and bug fixing

Please let me know if you have any questions.

See you on Friday! :)

Thanks and Best Regards,
Ildikó


> On 2019. Jul 30., at 14:00, Ildiko Vancsa <ildiko at openstack.org> wrote:
> 
> Hi,
> 
> I’m reaching out with an attempt to organize hacking days to work on edge related tasks.
> 
> The idea is to get together remotely on IRC/Zoom or any other platform that supports remote communication and work on items like building and testing our reference architectures or work on some project specific items like in Keystone or Ironic.
> 
> Here are Doodle polls for the next three months:
> 
> August: https://doodle.com/poll/ucfc9w7iewe6gdp4
> September: https://doodle.com/poll/3cyqxzr9vd82pwtr
> October: https://doodle.com/poll/6nzziuihs65hwt7b
> 
> Please mark any day when you have some availability to dedicate to hack even if it’s not a full day.
> 
> Please let me know if you have any questions.
> 
> As a reminder you can find the edge computing group’s resources and information about latest activities here: https://wiki.openstack.org/wiki/Edge_Computing_Group
> 
> Thanks and Best Regards,
> Ildikó
> (IRC: ildikov)
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



From Arkady.Kanevsky at dell.com  Fri Aug  9 19:45:45 2019
From: Arkady.Kanevsky at dell.com (Arkady.Kanevsky at dell.com)
Date: Fri, 9 Aug 2019 19:45:45 +0000
Subject: [Edge-computing] [ironic][ops] Taking ironic nodes out
	of	production
In-Reply-To: <CAF7gwdjunjOm=s_cnzjNACTBfobnNY2zyGG3aPsoA8_mN8XVpA@mail.gmail.com>
References: <d1fa2ae2-c7d0-2c6c-6289-638a247752b2@cern.ch>
 <08cb8294-04c8-e4ba-78c0-dec00f87156a@redhat.com>
 <6A205BFA-881E-4D2D-9A7D-E35935F6631B@est.tech>
 <09e4bfaa95404bcfba37ee63f6bf1189@AUSX13MPS304.AMER.DELL.COM>
 <CAF7gwdjunjOm=s_cnzjNACTBfobnNY2zyGG3aPsoA8_mN8XVpA@mail.gmail.com>
Message-ID: <0a38187f191c4a739fc7ed106a4188c9@AUSX13MPS308.AMER.DELL.COM>

Julia,
For #3 what I was trying to cover the case when Ironic is used to manage servers for multiple different platform clusters. Like 2 different OpenStack cluster that share single Ironic. Ore One OpenStack and one Kubernetes cluster with shared Ironic between them.
This use case support take a node from one platform cluster, clean it up, and allocate to another platform cluster.

Thanks,
Arkady

-----Original Message-----
From: Julia Kreger <juliaashleykreger at gmail.com> 
Sent: Tuesday, May 21, 2019 12:33 PM
To: Kanevsky, Arkady
Cc: Christopher Price; Bogdan Dobrelya; openstack-discuss; edge-computing at lists.openstack.org
Subject: Re: [Edge-computing] [ironic][ops] Taking ironic nodes out of production


[EXTERNAL EMAIL] 

On Tue, May 21, 2019 at 5:55 AM <Arkady.Kanevsky at dell.com> wrote:
>
> Let's dig deeper into requirements.
> I see three distinct use cases:
> 1. put node into maintenance mode. Say to upgrade FW/BIOS or any other life-cycle event. It stays in ironic cluster but it is no longer in use by the rest of openstack, like Nova.
> 2. Put node into "fail" state. That is remove from usage, remove from Ironic cluster. What cleanup, operator would like/can do is subject to failure. Depending on the node type it may need to be "replaced".

Or troubleshooted by a human, and could be returned to a non-failure state. I think largely the only way we as developers could support that is allow for hook scripts to be called upon entering/exiting such a state. That being said, At least from what Beth was saying at the PTG, this seems to be one of the most important states.

> 3. Put node into "available" to other usage. What cleanup operator wants to do will need to be defined. This is very similar step as used for Baremetal as a Service as node is reassigned back into available pool. Depending on the next usage of a node it may stay in the Ironic cluster or may be removed from it. Once removed it can be "retired" or used for any other purpose.

Do you mean "unprovision" a node and move it through cleaning? I'm not sure I  understand what your trying to get across. There is a case where a node would have been moved to a "failed" state, and could be "unprovisioned". If we reach the point where we are able to unprovision, it seems like we might be able to re-deploy, so maybe the option is to automatically move to state which is kind of like bucket for broken nodes?

>
> Thanks,
> Arkady
>
> -----Original Message-----
> From: Christopher Price <christopher.price at est.tech>
> Sent: Tuesday, May 21, 2019 3:26 AM
> To: Bogdan Dobrelya; openstack-discuss at lists.openstack.org; 
> edge-computing at lists.openstack.org
> Subject: Re: [Edge-computing] [ironic][ops] Taking ironic nodes out of 
> production
>
>
> [EXTERNAL EMAIL]
>
> I would add that something as simple as an operator policy could/should be able to remove hardware from an operational domain.  It does not specifically need to be a fault or retirement, it may be as simple as repurposing to a different operational domain. From an OpenStack perspective this should not require any special handling from "retirement", it's just to know that there may be time constraints implied in a policy change that could potentially be ignored in a "retirement scenario".
>
> Further, at least in my imagination, one might be reallocating 
> hardware from one Ironic domain to another which may have implications 
> on how we best bring a new node online.  (or not, I'm no expert) </ 
> end dubious thought stream>
>
> / Chris
>
> On 2019-05-21, 09:16, "Bogdan Dobrelya" <bdobreli at redhat.com> wrote:
>
>     [CC'ed edge-computing at lists.openstack.org]
>
>     On 20.05.2019 18:33, Arne Wiebalck wrote:
>     > Dear all,
>     >
>     > One of the discussions at the PTG in Denver raised the need for
>     > a mechanism to take ironic nodes out of production (a task for
>     > which the currently available 'maintenance' flag does not seem
>     > appropriate [1]).
>     >
>     > The use case there is an unhealthy physical node in state 'active',
>     > i.e. associated with an instance. The request is then to enable an
>     > admin to mark such a node as 'faulty' or 'in quarantine' with the
>     > aim of not returning the node to the pool of available nodes once
>     > the hosted instance is deleted.
>     >
>     > A very similar use case which came up independently is node
>     > retirement: it should be possible to mark nodes ('active' or not)
>     > as being 'up for retirement' to prepare the eventual removal from
>     > ironic. As in the example above, ('active') nodes marked this way
>     > should not become eligible for instance scheduling again, but
>     > automatic cleaning, for instance, should still be possible.
>     >
>     > In an effort to cover these use cases by a more general
>     > "quarantine/retirement" feature:
>     >
>     > - are there additional use cases which could profit from such a
>     >    "take a node out of service" mechanism?
>
>     There are security related examples described in the Edge Security
>     Challenges whitepaper [0] drafted by k8s IoT SIG [1], like in the
>     chapter 2 Trusting hardware, whereby "GPS coordinate changes can be used
>     to force a shutdown of an edge node". So a node may be taken out of
>     service as an indicator of a particular condition of edge hardware.
>
>     [0]
>     https://docs.google.com/document/d/1iSIk8ERcheehk0aRG92dfOvW5NjkdedN8F7mSUTr-r0/edit#heading=h.xf8mdv7zexgq
>     [1] 
> https://github.com/kubernetes/community/tree/master/wg-iot-edge
>
>     >
>     > - would these use cases put additional constraints on how the
>     >    feature should look like (e.g.: "should not prevent cleaning")
>     >
>     > - are there other characteristics such a feature should have
>     >    (e.g.: "finding these nodes should be supported by the cli")
>     >
>     > Let me know if you have any thoughts on this.
>     >
>     > Cheers,
>     >   Arne
>     >
>     >
>     > [1] https://etherpad.openstack.org/p/DEN-train-ironic-ptg, l. 360
>     >
>
>
>     --
>     Best regards,
>     Bogdan Dobrelya,
>     Irc #bogdando
>
>     _______________________________________________
>     Edge-computing mailing list
>     Edge-computing at lists.openstack.org
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>
>
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

From ildiko at openstack.org  Tue Aug 13 14:46:16 2019
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Tue, 13 Aug 2019 07:46:16 -0700
Subject: [Edge-computing] Edge Hacking Days - August 16
In-Reply-To: <3E028E2F-4AB5-49D6-A754-4E0CD829155A@openstack.org>
References: <BDD4BB84-403A-4A0B-8102-1D8DAD7FB8BD@openstack.org>
 <3E028E2F-4AB5-49D6-A754-4E0CD829155A@openstack.org>
Message-ID: <62A40854-2184-4334-8831-D984E3370852@openstack.org>

Hi,

It is a friendly reminder that we are having the second edge hacking days in August this Friday (August 16).

The dial-in information is the same, you can find the details here: https://etherpad.openstack.org/p/osf-edge-hacking-days

If you’re interested in joining please __add your name and the time period (with time zone) when you will be available__ on these dates. You can also add topics that you would be interested in working on.

We will keep on working on two items:
* Keystone to Keystone federation testing in DevStack
* Building the centralized edge reference architecture on Packet HW using TripleO

Please let me know if you have any questions.

See you on Friday! :)

Thanks,
Ildikó


> On 2019. Aug 6., at 11:35, Ildiko Vancsa <ildiko at openstack.org> wrote:
> 
> Hi,
> 
> Based on the Doodle poll results __August 9 and August 16__ got the most votes.
> 
> You can find the dial in details on this etherpad: https://etherpad.openstack.org/p/osf-edge-hacking-days
> 
> If you’re interested in joining please __add your name and the time period (with time zone) when you will be available__ on these dates. You can also add topics that you would be interested in working on.
> 
> Potential topics to work on:
> * Building and testing edge reference architectures
> * Keystone testing and bug fixing
> 
> Please let me know if you have any questions.
> 
> See you on Friday! :)
> 
> Thanks and Best Regards,
> Ildikó
> 
> 
>> On 2019. Jul 30., at 14:00, Ildiko Vancsa <ildiko at openstack.org> wrote:
>> 
>> Hi,
>> 
>> I’m reaching out with an attempt to organize hacking days to work on edge related tasks.
>> 
>> The idea is to get together remotely on IRC/Zoom or any other platform that supports remote communication and work on items like building and testing our reference architectures or work on some project specific items like in Keystone or Ironic.
>> 
>> Here are Doodle polls for the next three months:
>> 
>> August: https://doodle.com/poll/ucfc9w7iewe6gdp4
>> September: https://doodle.com/poll/3cyqxzr9vd82pwtr
>> October: https://doodle.com/poll/6nzziuihs65hwt7b
>> 
>> Please mark any day when you have some availability to dedicate to hack even if it’s not a full day.
>> 
>> Please let me know if you have any questions.
>> 
>> As a reminder you can find the edge computing group’s resources and information about latest activities here: https://wiki.openstack.org/wiki/Edge_Computing_Group
>> 
>> Thanks and Best Regards,
>> Ildikó
>> (IRC: ildikov)
>> 
>> 
>> 
>> _______________________________________________
>> Edge-computing mailing list
>> Edge-computing at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



From ildiko at openstack.org  Thu Aug 15 13:39:57 2019
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Thu, 15 Aug 2019 06:39:57 -0700
Subject: [Edge-computing] Edge Hacking Days - August 16
In-Reply-To: <62A40854-2184-4334-8831-D984E3370852@openstack.org>
References: <BDD4BB84-403A-4A0B-8102-1D8DAD7FB8BD@openstack.org>
 <3E028E2F-4AB5-49D6-A754-4E0CD829155A@openstack.org>
 <62A40854-2184-4334-8831-D984E3370852@openstack.org>
Message-ID: <A4C74C8F-EF58-4366-9362-D5619439F848@openstack.org>

Hi,

Be ready to hack tomorrow! :)

We are having the next occasion of the hacking days.

The dial-in information is the same, you can find the details here: https://etherpad.openstack.org/p/osf-edge-hacking-days

See you tomorrow!

Thanks,
Ildikó


> On 2019. Aug 13., at 7:46, Ildiko Vancsa <ildiko at openstack.org> wrote:
> 
> Hi,
> 
> It is a friendly reminder that we are having the second edge hacking days in August this Friday (August 16).
> 
> The dial-in information is the same, you can find the details here: https://etherpad.openstack.org/p/osf-edge-hacking-days
> 
> If you’re interested in joining please __add your name and the time period (with time zone) when you will be available__ on these dates. You can also add topics that you would be interested in working on.
> 
> We will keep on working on two items:
> * Keystone to Keystone federation testing in DevStack
> * Building the centralized edge reference architecture on Packet HW using TripleO
> 
> Please let me know if you have any questions.
> 
> See you on Friday! :)
> 
> Thanks,
> Ildikó
> 
> 
>> On 2019. Aug 6., at 11:35, Ildiko Vancsa <ildiko at openstack.org> wrote:
>> 
>> Hi,
>> 
>> Based on the Doodle poll results __August 9 and August 16__ got the most votes.
>> 
>> You can find the dial in details on this etherpad: https://etherpad.openstack.org/p/osf-edge-hacking-days
>> 
>> If you’re interested in joining please __add your name and the time period (with time zone) when you will be available__ on these dates. You can also add topics that you would be interested in working on.
>> 
>> Potential topics to work on:
>> * Building and testing edge reference architectures
>> * Keystone testing and bug fixing
>> 
>> Please let me know if you have any questions.
>> 
>> See you on Friday! :)
>> 
>> Thanks and Best Regards,
>> Ildikó
>> 
>> 
>>> On 2019. Jul 30., at 14:00, Ildiko Vancsa <ildiko at openstack.org> wrote:
>>> 
>>> Hi,
>>> 
>>> I’m reaching out with an attempt to organize hacking days to work on edge related tasks.
>>> 
>>> The idea is to get together remotely on IRC/Zoom or any other platform that supports remote communication and work on items like building and testing our reference architectures or work on some project specific items like in Keystone or Ironic.
>>> 
>>> Here are Doodle polls for the next three months:
>>> 
>>> August: https://doodle.com/poll/ucfc9w7iewe6gdp4
>>> September: https://doodle.com/poll/3cyqxzr9vd82pwtr
>>> October: https://doodle.com/poll/6nzziuihs65hwt7b
>>> 
>>> Please mark any day when you have some availability to dedicate to hack even if it’s not a full day.
>>> 
>>> Please let me know if you have any questions.
>>> 
>>> As a reminder you can find the edge computing group’s resources and information about latest activities here: https://wiki.openstack.org/wiki/Edge_Computing_Group
>>> 
>>> Thanks and Best Regards,
>>> Ildikó
>>> (IRC: ildikov)
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Edge-computing mailing list
>>> Edge-computing at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>> 
>> 
>> _______________________________________________
>> Edge-computing mailing list
>> Edge-computing at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing



From reza.tourani at slu.edu  Mon Aug 26 15:37:19 2019
From: reza.tourani at slu.edu (Reza Tourani)
Date: Mon, 26 Aug 2019 10:37:19 -0500
Subject: [Edge-computing] =?utf-8?q?CFP_=5BDeadline_in_2_Weeks=5D=3A_1st_A?=
 =?utf-8?q?CM_CoNEXT_Workshop_on_Emerging_in-Network_Computing_Paradigms_?=
 =?utf-8?b?KEVOQ1DigJkxOSk=?=
Message-ID: <3BB93524-E866-420A-A233-CB6F186CC8ED@slu.edu>

(Apologies if you have received multiple copies of this email)


Dear Colleagues,

Please consider contributing to the 1st ACM CoNEXT Workshop on Emerging in-Network Computing Paradigms (ENCP’19) to be held on 9-12 December 2019; Orlando, FL, USA.
Workshop links: http://www.cs.umsl.edu/~encp19/ <http://www.cs.umsl.edu/~encp19/> , https://conferences2.sigcomm.org/co-next/2019/#!/workshop-encp <https://conferences2.sigcomm.org/co-next/2019/#!/workshop-encp>

Scope and Topic List

The integration of computing and networking is considered a promising direction to fulfill the strict low latency and high data exchange requirements of a number of new and innovative application use-cases (e.g., augmented/virtual reality, autonomous driving, drone coverage). Context-aware networking can help maximize the compute utilization at the edge increasing the network capacity.  For instance, network functions may enable intelligent distribution of tasks to resources, the reuse of results from previously executed tasks, adaptability to the dynamic nature of edge ecosystems (e.g., network dynamics, bursty rates of tasks, dynamic resource availability).
The ENCP workshop has the integration of networking and computing as the central theme with a focus on mechanisms for the joint optimization of networking and computing resources, infrastructure virtualization, in-network caching, compute reuse, and security and privacy concerns.

The ENCP workshop has the goal of serving as a venue, where minds from the Distributed Computing, Information-Centric Networking (ICN), Network Function Virtualization (NFV), Software-Defined Networking (SDN), Edge Computing communities meet to advance the state-of-the-art in the area of systems for In-Network Computing. The workshop welcomes submissions from researchers and practitioners from academia and industry, who explore challenges and advances in architectures, algorithms, protocols, middleware, and technologies in the current or the future clean-slate Internet. We also encourage work-in-progress and position papers that describe original ideas, present new directions, or have the potential to stimulate insightful discussions. ENCP invites submissions of unpublished work on the following topics (but not limited to):

	• Architectures of in-network computing
	• In-network caching solutions
	• Virtualization for in-network computing systems
	• Network Function Virtualization (NFV) for in-network computing
	• Security, privacy, trust management, and access control in in-network computing architectures
	• Information-Centric Networking (ICN) for in-network computing
	• Software-Defined Networking for in-network computing
	• In-network computing for challenged networks (e.g., disaster scenarios)
	• Deployment and interoperability with traditional network architectures/functions
	• Network slicing for in-network computing systems
	• Internet of Things (IoT) for in-network computing
	• Pricing and billing in in-network computing systems
	• Highly available in-network computing systems
	• Management of in-network computing systems
	• In-network computing in the era of 5G
	• Scalability, performance advancements, and fault-tolerance
	• Tools for troubleshooting, monitoring, and validation of in-network computing systems and architectures
	• Innovative applications that in-network computing enables
	• In-network computing in public and private clouds, as well as edge computing paradigms
	• Resource allocation, modeling, and analysis
	• Applications of machine learning to in-network computing
	• Microservice architectures
	• Distributed consensus algorithms
	• Data processing frameworks

Important dates

Paper registration deadline: September 9, 2019
Paper submission deadline: September 16, 2019
Acceptance notification: October 4, 2019
Camera-ready deadline: October 13, 2019

Submission details
The workshop solicits papers written in the standard (2-column, 10pt ACM format). All the submissions will be double-blind and will be peer-reviewed. Per the anonymity guide, authors must remove their own names and any other information that may identify themselves to the reviewers. Submissions should be no more than 6 pages (including references, appendix, and all figures). The submission links will be announced shortly.

—

Best Regards,
Abderrahmen Mtibaa, Spyridon Mastorakis, and Dirk Kutscher
ENCP'19 General Chairs


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/edge-computing/attachments/20190826/39ce1234/attachment.html>

From ildiko at openstack.org  Wed Aug 28 12:59:26 2019
From: ildiko at openstack.org (Ildiko Vancsa)
Date: Wed, 28 Aug 2019 21:59:26 +0900
Subject: [Edge-computing] Edge white paper ToC brainstorming
Message-ID: <670C0D7F-C75A-4F1F-9DEE-1D7E0A8FB608@openstack.org>

Hi,

Following up on our discussion on yesterday’s weekly call I put together a Doodle poll to find a time slot next week to brainstorm about an outline and table of contents for a next edge white paper.

Please __fill out the poll asap__ if you’re interested in joining the call: https://doodle.com/poll/sv3nrgytcf4n6udv

I will send out a Zoom link and meeting invite once we have a slot we agree on.

Please let me know if you have any questions.

Thanks,
Ildikó




From David.Paterson at dell.com  Wed Aug 28 13:48:25 2019
From: David.Paterson at dell.com (David.Paterson at dell.com)
Date: Wed, 28 Aug 2019 13:48:25 +0000
Subject: [Edge-computing] Edge white paper ToC brainstorming
In-Reply-To: <670C0D7F-C75A-4F1F-9DEE-1D7E0A8FB608@openstack.org>
References: <670C0D7F-C75A-4F1F-9DEE-1D7E0A8FB608@openstack.org>
Message-ID: <73c55079a0eb4a909d7512ee91230bae@AUSX13MPC106.AMER.DELL.COM>

Dell Customer Communication - Confidential

Sept 2nd is a holiday in the US, I can make the call if that's the date we choose but may be tough for some folks in US.

Thanks,
dp

-----Original Message-----
From: Ildiko Vancsa <ildiko at openstack.org> 
Sent: Wednesday, August 28, 2019 8:59 AM
To: edge-computing
Cc: Csatari, Gergely (Nokia - FI/Espoo); Beth Cohen
Subject: [Edge-computing] Edge white paper ToC brainstorming


[EXTERNAL EMAIL] 

Hi,

Following up on our discussion on yesterday’s weekly call I put together a Doodle poll to find a time slot next week to brainstorm about an outline and table of contents for a next edge white paper.

Please __fill out the poll asap__ if you’re interested in joining the call: https://doodle.com/poll/sv3nrgytcf4n6udv

I will send out a Zoom link and meeting invite once we have a slot we agree on.

Please let me know if you have any questions.

Thanks,
Ildikó



_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

From ildiko.vancsa at gmail.com  Fri Aug 30 16:48:40 2019
From: ildiko.vancsa at gmail.com (Ildiko Vancsa)
Date: Fri, 30 Aug 2019 11:48:40 -0500
Subject: [Edge-computing] Edge white paper ToC brainstorming - NEW POLL
In-Reply-To: <73c55079a0eb4a909d7512ee91230bae@AUSX13MPC106.AMER.DELL.COM>
References: <670C0D7F-C75A-4F1F-9DEE-1D7E0A8FB608@openstack.org>
 <73c55079a0eb4a909d7512ee91230bae@AUSX13MPC106.AMER.DELL.COM>
Message-ID: <F54ABDED-84AA-4D4E-9B9A-B21C71BE5014@gmail.com>

The poll for next week so far doesn’t have a single slot that would work for more than one person so I assume the holiday weekend is affecting the whole week.

Here’s a poll for the week after next hoping for better results: https://doodle.com/poll/2ime3sug5q9qq9cc

Please fill it out as soon as you can if you’re interested and I hope I can come back with a time slot that works for a couple of people for the week of September 9.

Thanks,
Ildikó


> On 2019. Aug 28., at 8:48, David.Paterson at dell.com wrote:
> 
> Dell Customer Communication - Confidential
> 
> Sept 2nd is a holiday in the US, I can make the call if that's the date we choose but may be tough for some folks in US.
> 
> Thanks,
> dp
> 
> -----Original Message-----
> From: Ildiko Vancsa <ildiko at openstack.org> 
> Sent: Wednesday, August 28, 2019 8:59 AM
> To: edge-computing
> Cc: Csatari, Gergely (Nokia - FI/Espoo); Beth Cohen
> Subject: [Edge-computing] Edge white paper ToC brainstorming
> 
> 
> [EXTERNAL EMAIL] 
> 
> Hi,
> 
> Following up on our discussion on yesterday’s weekly call I put together a Doodle poll to find a time slot next week to brainstorm about an outline and table of contents for a next edge white paper.
> 
> Please __fill out the poll asap__ if you’re interested in joining the call: https://doodle.com/poll/sv3nrgytcf4n6udv
> 
> I will send out a Zoom link and meeting invite once we have a slot we agree on.
> 
> Please let me know if you have any questions.
> 
> Thanks,
> Ildikó
> 
> 
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing