let facility ID be used multiple times. #410

Closed
opened 2025-12-29 16:21:46 +01:00 by adam · 4 comments
Owner

Originally created by @aoyawale on GitHub (Sep 1, 2016).

Hello,

We use openstack and they use the concept of regions. We have started using the facility ID as the region name. It would be nice if we can reuse this ID in every rack we have in that location.

Originally created by @aoyawale on GitHub (Sep 1, 2016). Hello, We use openstack and they use the concept of regions. We have started using the facility ID as the region name. It would be nice if we can reuse this ID in every rack we have in that location.
adam closed this issue 2025-12-29 16:21:46 +01:00
Author
Owner

@jeremystretch commented on GitHub (Sep 1, 2016):

The facility ID is meant to uniquely identify a physical equipment rack. It sounds like you're trying to use it for something else entirely.

@jeremystretch commented on GitHub (Sep 1, 2016): The facility ID is meant to uniquely identify a physical equipment rack. It sounds like you're trying to use it for something else entirely.
Author
Owner

@aoyawale commented on GitHub (Sep 2, 2016):

thanks for the info. We will use another field for this.

@aoyawale commented on GitHub (Sep 2, 2016): thanks for the info. We will use another field for this.
Author
Owner

@jeremystretch commented on GitHub (Sep 6, 2016):

FYI custom fields are functional in the develop branch and will be released in v1.6.

@jeremystretch commented on GitHub (Sep 6, 2016): FYI custom fields are functional in the `develop` branch and will be released in v1.6.
Author
Owner

@aoyawale commented on GitHub (Sep 6, 2016):

that is awesome :) thank you. That will probably solve our issue.

On Tue, Sep 6, 2016 at 3:14 PM, Jeremy Stretch notifications@github.com
wrote:

FYI custom fields are functional in the develop branch and will be
released in v1.6.


You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/526#issuecomment-245058405,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATM8EASWkmITr2rdJd4-pT1rBQEVwDFzks5qnbuLgaJpZM4JzEhQ
.

@aoyawale commented on GitHub (Sep 6, 2016): that is awesome :) thank you. That will probably solve our issue. On Tue, Sep 6, 2016 at 3:14 PM, Jeremy Stretch notifications@github.com wrote: > FYI custom fields are functional in the develop branch and will be > released in v1.6. > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub > https://github.com/digitalocean/netbox/issues/526#issuecomment-245058405, > or mute the thread > https://github.com/notifications/unsubscribe-auth/ATM8EASWkmITr2rdJd4-pT1rBQEVwDFzks5qnbuLgaJpZM4JzEhQ > .
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#410