Wtr.: the role of allocators
1 view
Skip to first unread message
Frank Weiler
Nov 24, 2008, 10:06:06 AM11/24/08
to jar...@googlegroups.com
OOps, I stood in the forrest and didn't see the trees !!!!
Forget the pool confusion remarks please ! Sorry...
But the allocator permissions remarks remain...
Frank
----- weitergeleitete Nachricht ---------
Betreff: the role of allocators
Datum: Mo, 24. Nov 2008
Von: Frank Weiler
Hello to all,
If I logon to Jarifa as an allocator, I can add projects, for which the suppliers hosts should do work for me.
But - I can freely edit (and worse - delete) all projects, not only my own.
Is this the way it should work ? Or made I something wrong ?
At our organisation we do not have a problem with this, because we are the only supplier and allocator in one, and there is only one person (actually me), that have control over the Jarifa server. But if you imagine, that there are several departments, that act as allocators, there will be some kind of competition about the resources. Should we prevent access to projects of different allocators ?
And - perhaps I didn't understood the concept right - what are pools good for ? At the moment two pools can have different preferences, but how are hosts distibuted to the pools ? Who (and where) did I as a supplier decide, to which pool a host belongs ? I am a bit confused with this...
Greetings, Frank
---- weitergeleitete Nachricht Ende ----
Forget the pool confusion remarks please ! Sorry...
But the allocator permissions remarks remain...
Frank
----- weitergeleitete Nachricht ---------
Betreff: the role of allocators
Datum: Mo, 24. Nov 2008
Von: Frank Weiler
Hello to all,
If I logon to Jarifa as an allocator, I can add projects, for which the suppliers hosts should do work for me.
But - I can freely edit (and worse - delete) all projects, not only my own.
Is this the way it should work ? Or made I something wrong ?
At our organisation we do not have a problem with this, because we are the only supplier and allocator in one, and there is only one person (actually me), that have control over the Jarifa server. But if you imagine, that there are several departments, that act as allocators, there will be some kind of competition about the resources. Should we prevent access to projects of different allocators ?
And - perhaps I didn't understood the concept right - what are pools good for ? At the moment two pools can have different preferences, but how are hosts distibuted to the pools ? Who (and where) did I as a supplier decide, to which pool a host belongs ? I am a bit confused with this...
Greetings, Frank
---- weitergeleitete Nachricht Ende ----
Daniel Lombraña González
Nov 24, 2008, 11:25:17 AM11/24/08
to jar...@googlegroups.com
Hi,
About the allocators and suppliers. Jarifa is thought to have only one allocator. Basically, each organization should have a committee, who decides which projects enter in Jarifa. Thus, despite of having several allocator users, all of them follow the same rules.
Frank, what you are requesting was discussed in the past, when we were designing Jarifa. At the end we conclude that it is better to have only one allocator team with the same interests, instead of having one allocator per supplier. As we were talking about this, we also talked about the possibility of having two different Jarifas, that agree to collaborate between them, so each Jarifa server have its own allocator team, without disturbing the other Jarifa server.
What do you think about this solution?
Daniel--
··························································································································································
PhD Candidate
Cátedra Ceta-Ciemat de la Universidad de Extremadura
http://gea.unex.es/catedra-ceta-ciemat/
Universidad de Extremadura
··························································································································································
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··························································································································································
About the allocators and suppliers. Jarifa is thought to have only one allocator. Basically, each organization should have a committee, who decides which projects enter in Jarifa. Thus, despite of having several allocator users, all of them follow the same rules.
Frank, what you are requesting was discussed in the past, when we were designing Jarifa. At the end we conclude that it is better to have only one allocator team with the same interests, instead of having one allocator per supplier. As we were talking about this, we also talked about the possibility of having two different Jarifas, that agree to collaborate between them, so each Jarifa server have its own allocator team, without disturbing the other Jarifa server.
What do you think about this solution?
Daniel
··························································································································································
PhD Candidate
Cátedra Ceta-Ciemat de la Universidad de Extremadura
http://gea.unex.es/catedra-ceta-ciemat/
Universidad de Extremadura
··························································································································································
Por favor, NO utilice formatos de archivo propietarios para el
intercambio de documentos, como DOC y XLS, sino HTML, RTF, TXT, CSV
o cualquier otro que no obligue a utilizar un programa de un
fabricante concreto para tratar la información contenida en él.
··························································································································································
Frank Weiler
Nov 25, 2008, 2:23:25 AM11/25/08
to jar...@googlegroups.com
Hello Daniel,
at the moment only our IT department is supplier and also allocator, but I imagine a situation, when we decide to open Jarifa to the whole organization. And there might be conflicts which project to support with how many resource share between the different departments. But we can handle this installing a committee, and with adjusting ressource share between projects. Two Jarifa servers didn't come into my mind and I don't would prefer this.
BTW: Is there a reason why the allocator can't see the statistics ?
Greetings from Berlin under snow
Frank
----- original Nachricht --------
Betreff: Re: Wtr.: the role of allocators
Gesendet: Mo, 24. Nov 2008
Von: Daniel Lombraña González
at the moment only our IT department is supplier and also allocator, but I imagine a situation, when we decide to open Jarifa to the whole organization. And there might be conflicts which project to support with how many resource share between the different departments. But we can handle this installing a committee, and with adjusting ressource share between projects. Two Jarifa servers didn't come into my mind and I don't would prefer this.
BTW: Is there a reason why the allocator can't see the statistics ?
Greetings from Berlin under snow
Frank
----- original Nachricht --------
Betreff: Re: Wtr.: the role of allocators
Gesendet: Mo, 24. Nov 2008
Von: Daniel Lombraña González
--- original Nachricht Ende ----
Daniel Lombraña González
Nov 25, 2008, 2:58:55 AM11/25/08
to jar...@googlegroups.com
Hi,
What you have said is how Jarifa is thought. The idea is using the share resources to apply some kind of priority between projects. I'm still thinking that the solution could be the two Jarifa servers, as long as we have implemented the relationships between Jarifas. I think that these solution, could be the most fair one, because each Jarifa will handle its resources and projects.
About the statistics and allocator. There is not a reason, we can open the statistics to them ;).
Best regards,
Daniel
What you have said is how Jarifa is thought. The idea is using the share resources to apply some kind of priority between projects. I'm still thinking that the solution could be the two Jarifa servers, as long as we have implemented the relationships between Jarifas. I think that these solution, could be the most fair one, because each Jarifa will handle its resources and projects.
About the statistics and allocator. There is not a reason, we can open the statistics to them ;).
Best regards,
Daniel
Reply all
Reply to author
Forward
0 new messages