Devnet Always on not really always on????

[Cisco-man]

Cisco Devnet Always on instances meant no reservation required and you could actually use them as nodes for your testbeds. With the new temporary credential, one has to reserve an instance. This seems to be okay until you require multiple nodes. Cisco Devnet accounts have a restriction to only allow one active reservation at a time.

This really defeats the whole point of having always-on instance. If you have to reserve an instance for a limited time and only work with one particular node better to change the instance type to reservable and avoid using the Always-on Tag.

Has Cisco DevNet Team ever thought about this? How is our Devnet community working with multiple Always-on nodes?

[Jesus Illescas]

I think it makes sense what you describe to allow more active reservations for always on sandboxes. I will share your idea with the sandbox team. I'm not sure if they can implement it soon though, they are a small team now. 

As a side note, if they allow to use have multiple reservations for always on, you might need to use different credentials. This was a requirement pushed by security which the sandbox team didn't have control over.