Well, if you’re flying solo on this whole thing, you could run with a simpler
system where you just push versions manually using MCollective (or execute
remote auto-installs on all machines), rather than trying to set up a sync
system. Regardless, I would say it’s almost a requirement that you or whoever
does your systems upkeep have some kind of tool to perform remote executions on
any machine in the building, and the permissions to go along with it.
Back to the remote install question: that’s something I would personally be
very nervous about relying on, especially during high-volume periods. On the
stability side, if you ever experience any kind of network interruption,
suddenly your apps are hanging, crashing, or unable to start.
Additionally, I imagine pretty much everything you do would take a performance
hit, since every library call and script invocation would need to traverse a
network pipe and hit centralized remote storage. Layered on top of this would
be any latency issues your storage has when receiving lots of small file access
requests (we see latency from this fairly frequently with our storage array).
Now, obviously some of these issues would depend on the number of users and
storage setup you’ve got, but those are some more thoughts.
-Nathan
From: Gary Jaeger
Sent: Thursday, December 15, 2011 10:51 AM
To: Nuke user discussion
Subject: Re: [Nuke-users] central nuke install
Sounds like I need your systems guys
On Thu, Dec 15, 2011 at 9:38 AM, Nathan Rusch <[email protected]> wrote:
Our systems guys use a combination of remote execution tools (Puppet,
MCollective) and custom RPMs to enforce software installations (including
things like PyQt builds and other "pre-rolled" libraries/modules) and other
scripts that we need to have maintained locally (shell setup scripts, etc.).
Basically each machine calls home at staggered intervals to check for new
versions of things, and things can be pushed out on demand if it’s an emergency.
-Nathan
From: Gary Jaeger
Sent: Thursday, December 15, 2011 7:54 AM
To: Nuke user discussion
Subject: [Nuke-users] central nuke install
so now that we finally have our house in order with a central
plug-in/gizmo/whatever install and the NUKE_PATH set, I'm wondering if it makes
sense to do a central install of the binaries? It would be nice if all the
workstations and render nodes are all on the same version, all the time. How do
people manage that?
--
Gary Jaeger // Core Studio
249 Princeton Avenue
Half Moon Bay, CA 94019
650 728 7060
http://corestudio.com
------------------------------------------------------------------------------
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
Gary Jaeger // Core Studio
249 Princeton Avenue
Half Moon Bay, CA 94019
650 728 7060
http://corestudio.com
--------------------------------------------------------------------------------
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
