Thanks for answering...

Sorry for beeing not precise enough.

In our environment we are working in a multidicipline domain.
Infrastructure staff and engineers are working in the same team. Users
of the system are engieers (not software engineers) able to understand
the pricipal and the basic usage of a version control system like SVN.
They are able to checkin and checkout themself and they in general
understand the riscs with could happen if they are checkin files with
bad content. The files they should checkin are basicly the files for
the user application layer and basicly not the OS layer which of
course stays under full control of the infrastructure.

We are managening a complex distributed control center (around 50
clients and 10 servers) including the installed user application.

Hope that makes things clearer...



On 26 Sep., 18:09, Bruce Richardson <itsbr...@workshy.org> wrote:
> On Sat, Sep 25, 2010 at 07:34:19AM -0700, Christian wrote:
> > Hello community,
>
> > As you all know a good infrastructure deployment in production state
> > should not involve much technical infrastructure staff anymore.
> > Routine work should be able to perform by the users themselfs who
> > should not know anything about the infrastructure implementation
> > details.
>
> I don't think I agree with this, but nothing in your message makes it
> clear what you mean by "users".  What kind of systems are you managing,
> what is the relationship between you and the users (are they people in
> another department, customers or what?) and what are their skills?
>
> --
> Bruce
>
> Hierophant: someone who remembers, when you are on the way down,
> everything you did to them on the way up.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to