I have a feature request for Torizon Cloud that I (and probably others) would find very useful.
When we provision devices, the device itself sets a device name based on its product type and serial number so that it can be easily identified in the web platform.
I would find it very useful to be able to supply basic wildcard or regex “rules” of some kind to facilitate auto-assigning devices to a particular fleet when they are provisioned. For example, if my device name contains “PRODUCT-DEV”, auto assign it to my fleet called “Development Units”. If it matches “PRODUCT-[0-9]+”, assign it to “Customer Units” instead. It would be helpful if these filters could be applied both on the device name and/or the device HardwareID.
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
The context provided does not include specific information about feature request rules for auto-assigning devices to fleets in Torizon Cloud. However, based on the general capabilities of Torizon Cloud, it seems like a reasonable feature request to enhance device management and provisioning. For such feature requests, it would be best to contact Toradex support or use the appropriate channels for submitting feature requests to see if this can be considered for future updates.
Please, also check if these links can help you solve your problem:
Correct, the platform account (or maybe the specific fleet) would have a rule associated with it that says “a device name matching PRODUCT-[0-9]+ should be automatically added to fleet PRODUCT”
I had initially thought only for fleet assignment, but perhaps (given the other discussion we are having regarding lockboxes) I could see further use cases such as to automatically filter or bin platform packages to specific fleets or HWIDs.
Now that I think about this more, maybe a better approach would be the concept of a “product” in the platform as a means to bin the different components:
Ex: I can create a product called “MyWidget” in the web platform. For this product, I can then define:
Fleets to organize devices of this type (development, customer, etc) with the previously discussed rules to facilitate automatic assignment of devices to a fleet
Package → product associations to limit what packages can be installed on any given product.
Lockboxes on a per-product basis, such that (per our other discussion), the lockboxes for one product do not contribute to the size of another product’s metadata.
Something like this could theoretically be done with separate platform accounts per product, but that somewhat defeats the purpose of having a single central place for managing the ecosystem.
We can connect outside the forums if you would like to discuss our exact use cases a bit more with concrete examples.
Those are some interesting ideas/use-cases. Let me bring this up internally to start some initial discussion. I’m not too familiar with the actual technical details of our server/web UI for our cloud platform. Let me bring this up to the relevant technical people here and get their thoughts.
Just to follow-up. After having a brief discussion with the technical team about this it seems like a sensible idea. They’ve already created a ticket in their backlog to further discuss and plan the potential feature.
Also just for planning sake, this is like a nice-to-have feature right? It’s not super urgent or anything, correct?
The device-to-fleet filtering is indeed a nice-to-have, but my further musings on being able to group/isolate lockboxes and devices under a particular “product” category are a bit more urgent and an actual “need” (per the other discussion we are having regarding limitations on the number of lockboxes in an account and our specific use cases).
but my further musings on being able to group/isolate lockboxes and devices under a particular “product” category are a bit more urgent and an actual “need”
Are you saying this for the purpose of being able to organize your Lockboxes based on product. Or is this more for the idea of having separate Lockbox “limits” per product, as you mentioned prior?
From a technical standpoint this is a bit tricky. What you asked for initially with the “device-to-fleet filtering” is actually quite doable. I just learned from our team that there is a foundation for a filtering function in our server backend.
But with regards to having separate metadata for each designated “product group” this would probably require much discussion and be a more significant change on our backend. Also I’m saying this without even knowing yet if this is doable within the limitations of our security standard we follow.
In any case, if this is about the Lockbox limit again we can discuss this in our upcoming call as well. I believe someone from our sales team should reach out to you soon about this.
Okay understood. I just wanted to make sure I was understanding the goal behind your request.
Just to summarize your initial request for auto-assigning devices via a user-defined filter has already been recorded as a ticket in our R&D team’s backlog. As for your other topic regarding the Lockbox limit, we can discuss this in more detail during our upcoming call.
