correct relocation process

[Chris Burroughs]

So based on the existence of the Relocation maintenance status the right
way to update a RACK_POSITION was to put an asset into maintenance and
POST /api/asset/:tag. However, this does not appear [1] to work.

Instead I went through an Unallocated-->Maintenance-->New-->Unallocated
dance. Is that the right way to go?


[1]
https://github.com/tumblr/collins/blob/master/app/models/AssetLifecycle.scala#L227

[Blake Matheny]

You should just be able to put it into New to update the value, then back to the original status. The reason that this is 'the way' is that at Tumblr, if you relocate a machine, the RACK_POSITION does but so does all the power telemetry, which requires having the asset go through the web based intake process again. The web based intake is only available when an asset is in New status.

I'd be open to a patch to allow for more flexibility, but the default is the 'right' things for the Tumblr environment.

--
Blake Matheny
@bmatheny

--
You received this message because you are subscribed to the Google Groups "Collins" group.
To unsubscribe from this group and stop receiving emails from it, send an email to collins-sm+...@googlegroups.com.
To post to this group, send email to colli...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.