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. 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 This looks to contribute, among other things, into the definition of Edge Computing use cases. Best Regards Some people from StarlingX community.