Project

General

Profile

Feature #3099

Adding parameters to locations

Added by Jon Shanks almost 6 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Organizations and Locations
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Hey,

It would be nice to be able to add parameters to locations as oppose just host groups.

We might want a specific set of data tied to a location that is a set of parameters, which then would enable you to inherit that data for your hostgroup. i.e. i might want

Location/Datacentre/Datacentre_hall -> which would contain a set of parameters tied to that hall

When i add a new host, i would choose it's location and then the hostgroup i.e. role of the server it belongs to.

Currently i have locations and then a load of hostgroups for al the varying locations.

Associated revisions

Revision 2de7832d (diff)
Added by Ohad Levy over 5 years ago

fixes #3099 - Adding parameters to locations and organizations

History

#1 Updated by Dominic Cleal almost 6 years ago

  • Category set to Organizations and Locations
  • Target version deleted (1.3.0)

#2 Updated by Jon Shanks almost 6 years ago

To add clarity. If i have a set of data tied to a location i want to define it at a location level. Not have to create a host group, named the same name as the location to then associate with the location. as it's duplicating elements.

#3 Updated by Dominic Cleal over 5 years ago

  • Status changed from New to Assigned
  • Assignee set to Amos Benari
  • Target version set to 1.10.0

#4 Updated by Dominic Cleal over 5 years ago

  • Target version changed from 1.10.0 to 1.9.3

#5 Updated by Ohad Levy over 5 years ago

what would be the order of override e.g.

currently

if something is defined in the hostgroup, it can be overridden per host, and normally the order is:
global -> domain -> os -> hostgroup -> host

where would we put org and locations?

#6 Updated by Ohad Levy over 5 years ago

  • Status changed from Assigned to Ready For Testing
  • Assignee changed from Amos Benari to Ohad Levy

#7 Updated by Dmitri Dolguikh over 5 years ago

  • Target version changed from 1.9.3 to 1.9.2

#8 Updated by Jon Shanks over 5 years ago

Hey,

I guess from my point of view, as a user, it would be

global -> location -> domain -> OS -> Hostgroup -> host

As you may tie many domains to locations so you would want a location to be the top and global wouldn't be global if it was placed beneath something more global.

Thanks

Jon

#9 Updated by Ohad Levy over 5 years ago

what about orgs, on top of locations on the other way around? I tend to put them on top, but that's just my preference.

#10 Updated by Jon Shanks over 5 years ago

Hey.

Yep that makes sense to me too ;-) .

I'd logically think of it as an organization have a presence in one or many locations as oppose a location having one or more organizaional presences when it comes to the infrasdtructure as the infrastructure really ties to the organization first and foremost.

Jon

#11 Updated by Dominic Cleal over 5 years ago

  • Legacy Backlogs Release (now unused) set to 2

Thanks for the feedback Jon, very useful.

#12 Updated by Ohad Levy over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF