[Starlingx-discuss] Public sandbox?

[Curtis]

On Mon, Apr 15, 2019 at 10:28 AM Arce Moreno, Abraham <
abraham.arce.moreno at intel.com> wrote:

> Thanks Curtis!
>
> > One of the ideas that came up in community discussion (not the only
> idea, just
> > one and we can do multiple) for using the packet.com <http://packet.com>
> > infrastructure was a public sandbox. I think this is a good idea.
> However, what
> > does that actually mean? It could be a lot of things.
>
> Some people would love to see also a virtual showroom of StarlingX
> features, more below...
>
> > My first thought is that it is a publicly accessible AIO Simplex node
> that people
> > can easily access and get a feel for what STX actually is, and that is
> completely
> > reset every X hours. But that's just me so I wanted to check with the
> community
> > and see what other thoughts are out there.
>
> Agree, this is a must have so new players can play around.
>
> > But again, that's just my initial thoughts. Open to
> ideas/comments/criticisms. :)
>
> Last week, we discussed, among other things, the usage for Packet and we
> determined it would be good to have a StarlingX virtual showroom, which is
> a space where any type of edge computing workloads are landed, which aligns
> perfectly to what Packet is looking for.
>
>
Sounds great, where did this discussion occur? I'd like to take part if I
can, though I am somewhat limited in N/A daytime meeting times.



> We can start easily right away, deploying the demos that you guys have
> presented in the past conferences, and for every demo / workload / whatever
> you want to call it, we must have generate a:
>
> - Reference Architecture
> - Solution Brief
> - Application Note
>
>
Where does these requirements come from?

Thanks,
Curtis



> This looks to contribute, among other things, into the definition of Edge
> Computing use cases.
>
> Best Regards
> Some people from StarlingX community.
>


-- 
Blog: serverascode.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190415/9d5d8ae4/attachment.html>