[Starlingx-discuss] Public sandbox?
Hi All, 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 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. 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. There are a few ways we could do this as well: 1. A single virtualized instance that is reset every X hours 2. A single baremetal instance that is reset every X hours 3. Multiple virtualized instances with some kind of reservation system 4. Other??? #1 would be easiest as that looks a lot like what we are doing for the workshop. But again, that's just my initial thoughts. Open to ideas/comments/criticisms. :) Thanks, Curtis
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.
On Mon, Apr 15, 2019 at 10:28 AM Arce Moreno, Abraham < abraham.arce.moreno@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
Some people would love to see also a virtual showroom of StarlingX features, more below...
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.
It was an informal team talk while we were planning some self-learning activities for the next months. We can arrange a sync up meeting If you want to get more into the specific details.
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?
At Intel, we use the above artifacts when we do customer enablement and they are the core of our solutions libraries. Not a specific requirement from anyone but our proposal for ways to teach, give a working solution base or simply create awareness on StarlingX. Let us know how do we proceed with this proposal.
On Mon, Apr 15, 2019 at 8:27 PM Arce Moreno, Abraham < abraham.arce.moreno@intel.com> wrote:
Some people would love to see also a virtual showroom of StarlingX features, more below...
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.
It was an informal team talk while we were planning some self-learning activities for the next months. We can arrange a sync up meeting If you want to get more into the specific details.
Ok cool. My suggestion is going to be that we setup a Special Interest Group (SIG) around the packet.com work. This SIG would exist for a short time and we would funnel all the related packet.com work through it for the time being, at least in term of what resources are being used and how. Then, once we felt everything was well understood in terms of how we organize and use the packet.com infrastructure we would disband it and work would continue as normal in the teams that are using the infrastructure. I'll mention this at the community and TSC meetings this week.
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?
At Intel, we use the above artifacts when we do customer enablement and they are the core of our solutions libraries. Not a specific requirement from anyone but our proposal for ways to teach, give a working solution base or simply create awareness on StarlingX. Let us know how do we proceed with this proposal.
I think we would just want to make sure that whatever artifacts we generate are valuable to the community and we shouldn't just bring in an existing process if it doesn't match up with community requirements, though, of course, it might end up being exactly what we want. I mean I think I can understand what a reference architecture is, but I have no context for what an application note is. :) Thanks, Curtis
participants (2)
-
Arce Moreno, Abraham
-
Curtis