+1 to use parseable ids. Regarding the format, let's pick one that allows us to easily extend it in the future, in case we need to add there other hardware profile information such as disk sizes, etc, but keep it as simple as possible to cover the current use case.
I. El 13 jun. 2016 1:47 p. m., "Iván Lomba" <ivanlo...@gmail.com> escribió: > Hi! > > I'm going to start with the implementation to support cpu and ram. > According with discussed here before, I understand that the best approach > will be to have auto-generated hardwares, and to take advantage of minCores > and minRAM to avoid interface changes and casts. > > Regarding the ids, I'm not sure about what is better or what has more > sense: if using randomIds, parseableIds or even combine it? What do you > think? > > Parseable ids that allow to reconstruct the hardware from the id seems to > me an useful option. If we decide to use that approach, what format can we > use? Something like: > > "automatic-cpu-5-ram-2048..." > > Regards. >
