I get the impression from watching some of the videos that it is possible to create Resources for Bookings that are not based on elements. For ex., to create a list of IP addresses or a list of engineers that might be assigned to a booking.
Creating the resources are easy enough, but the part I'm missing is, how do you get the resources to show up when creating a booking? Since these resources are not coming from a protocol, I'm not sure how to create a Function. And, without the Function, I'm not sure how to get them into a Service Definition.
I'm probably missing something simple, so any push in the right direction would be appreciated. Thanks!
Hi Jamie,
I use this on Ziine for the SDMN demo. There I have an encoder application that needs to get an IP assigned from a pool of available multicast addresses. In below capture you can see how I've done this.
Note that you only need to do this when you work with the default booking scripts that comes with the SRM framework package. In case of a custom (silent) booking script you'll have to add logic in the script itself.
Thanks Jens! I will take a look.
Hi Jens… thanks again for this! I was thinking about booking IP addresses differently, but this makes perfect sense.
Hi Jamie, I’m sure that other teams in Skyline have used different approaches. This one works in my case when I use the default booking wizard script.
Hi Jamie, if your use case is to create pools and resource instances (one-by-one or in bulk) such as people, then we have a good blue print application that does exactly that on ziinedev : https://ziinedev.skyline.be/app/06951cc4-5695-4f6c-a49b-55582d72f611/page/Home
In this app, you have a nice example of how DataMiner users can create objects such as organizations, teams and people. In addtion, teams can be made ‘bookable’ as an optional selection. The latter will automatically create bookable resources in the background, and add capacity and capabilities to those (e.g. ‘Team Expertises’ will automatically translate into ‘SRM capabilities’ to all resources in the pool)
Adding to that, we are generalizing the resource administration in a new app, since there is so many use cases where DM users need a simple way to create resources in bulk. You can use this for any ‘unmanaged resource’ (i.e. resource not linked to a specific element, VF, etc), or resources linked to an element (the latter is on the backlog coming available in 1-2 weeks from now). The app is not in an MVP state yet, but could be used in case you need something almost off the shelf quickly
I’ll be happy to walk you through all of that ! Let me know !