Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Mateusz Kurek
@mkurek
and i forgot about business owners and technical owners, which could be assigned to service - so there is no need to involve team here :)
damian1976
@damian1976
I think @msuszko rather meant "User Info" section in Asset add/edit form, not Support Group. Please correct me if I'm wrong.
Michał Suszko
@msuszko
@mkurek could you assign person to a support?
Mateusz Kurek
@mkurek
@msuszko afaik no - why you want to assign a person to a support?
Michał Suszko
@msuszko
@damian1976 Yes, I'm looking for assigning person to a data center asset as it is done with back office asset
damian1976
@damian1976
@mkurek, once you described me why in 3.x this info has been discarded. I don't remember the reasons why.
Michał Suszko
@msuszko
My security department is looking for a way to address vulnerability scan results, they need to identify person administering system with specific IP
Mateusz Kurek
@mkurek
@msuszko @damian1976 it useless (at least from our point of view) to assign single person to a single person - we rather prefer to assign person to service and then this service to asset; advantage of this flow is when the person is gone or the owner is changed - then you're just replacing it in one place, not in every asset; the only problem which I see here is when there is more than one person administering servers within one service - is it your case @msuszko (and @damian1976 too)?
damian1976
@damian1976
It happens quite often. But from my point of view - a single person is enough. In the worst case this person can contact another person or provide the info who is really responsible for given servers.
So the given flow should be ok for me.
✪ vi4m Marcin Kliks
@vi4m
@msuszko we are in the middle of integration of similar product (security scanner) which will integrate with ralph
to dump scan results to the Security Tab
✪ vi4m Marcin Kliks
@vi4m
@msuszko what's the use case behing assigning each admin to each asset ? can't you identify service (for example data dabases: service name"DB", 4 assets assigned to this service, service owner: John)
when you grow bigger(more servers, more people) you will likely end up with this "service" oriented idea
Michał Suszko
@msuszko
@vi4m I'm quite big at the moment, and there is infrastructure support department with teams for each software/technology. Still, formal approach is to identify one person directly responsible for a host even he can share this with coworkers
Anyway, there is no way to add people though support either. One can only attach support to an asset.
✪ vi4m Marcin Kliks
@vi4m
we can think about that, how to solve it correctly
Michał Suszko
@msuszko
I could use support groups, the problem is there are no groups nor other way to attach people to support.
and most fields in support doesn't apply to sysops teams
✪ vi4m Marcin Kliks
@vi4m
no msuszko, current 'support' tab is a different beast from 'support groups'
the only way to set the person responsible for a server is to assign it to the asset's service
what will happen when we add another field for similar purpose - for example "Supporting person" "Responsible person"
✪ vi4m Marcin Kliks
@vi4m
we can assign it independent from service owner, but when this person leaves company, we have to change it in number of places
what's your idea for it?
Mateusz Kurek
@mkurek
@msuszko so it'll be ok for you to attach Team to support? if yes then maybe you'll create PR for that (it should be only a couple of lines + migration) and we'll make sure that it is fine for us too (I don't see any objections now)?
Michał Suszko
@msuszko
I could implement it and submit pull request, just need to agree with you on the details
✪ vi4m Marcin Kliks
@vi4m
@mkurek keep it mind, that the Support wich is visible at Support tab is for asset manfuacturer support terms, which is not we're talking about here.
Michał Suszko
@msuszko
Ah, i see. You ment ralph.acconts.models.Team and Asset.support_team
Mateusz Kurek
@mkurek
yeah, but rather ralph.assets.models.assets.Service.support_team
Michał Suszko
@msuszko
At the moment RalphUser can be member of one team only. Is this intended?
Mateusz Kurek
@mkurek
yes; i guess that your users belong to more than one team?
Michał Suszko
@msuszko
usually, yes
We have tree organization structure, and each employee is in one department/unit, but this is different than support teams.
Michał Suszko
@msuszko
hmm models.PositiveIntegerField is to small to store ip address for Network.min_ip and .max.ip
why don'y you use GenericIPAddressField?
Michał Suszko
@msuszko
PositiveIntegerField is just IntegerField with > 0 constraint, so max value is 2^31 and last address you can store in it is 127.255.255.255
✪ vi4m Marcin Kliks
@vi4m
looks like really shitty bug - we should use only GenericIPAddressField
Michał Suszko
@msuszko
I have test env with 806 networks and 2342 IPs and ralph.data_center.models.networks.get_network_tree has been running for 10 minutes before I interrupted it, so it needs better algorithm probably
@vi4m we spent some time discussing how to squeeze our current CMDB (asset <-> administrator) mess into Ralph's model, and one support team for an asset could work for us, but one team for a person is a problem
✪ vi4m Marcin Kliks
@vi4m
@msuszko could you propose some REP with possible solutions? i'm sure we can adapt some solution which is elegant and flexible
either extending asset model(to obey team requirement)
and leaving just concrete support person - as a 1 scenario
or changing user/team structure
we will decide then
Michał Suszko
@msuszko
OK
Michał Suszko
@msuszko
djangorestframework 3.3 is out
✪ vi4m Marcin Kliks
@vi4m
Cool!
✪ vi4m Marcin Kliks
@vi4m
@msuszko what about the IP address field? are you going to fix it?
Michał Suszko
@msuszko
@vi4m I can fix it later today. What is you approach on migrations? Shouold I update latest one?
Mateusz Kurek
@mkurek
@msuszko no - just create a new one