Get location auto-assignment back in Racks

[Igor Shishkin]

Hello,

Since [0] is Invalid please get locations auto assignment feature back no matter based on what details it will be done(puppet or DCIM or whatever else). It blocks us from providing location-based reports on hardware so setting to High.

[0] https://bugs.launchpad.net/fuel/+bug/1558040

[Alexander Charykov (acharykov)]

It doesn't block your work, you can update location by hands.
However it requires additional manual updates and because we trust DCIM about HW location we'll use it as location source. But inside Racks facter_location is used, and it should be set somehow inside.

[Igor Shishkin (teran)]

@Alexander, unfortunately blocks since we're unable to do that for all of servers so performing this action manually is technically impossible.

Can't get what do you mean on "But inside Racks facter_location is used, and it should be set somehow inside." please clarify.

[Alexander Charykov (acharykov)]

Manual update is possible, but takes time.

> But inside Racks facter_location is used, and it should be set somehow inside.
I mean that we're using facter_location which is inside to determine exact association to internal/external subnet, dmz, etc.

[Alexander Charykov (acharykov)]

Replaced with jira issue https://mirantis.jira.com/browse/RACKS-16.