Recent Posts

Pages: 1 ... 6 7 [8] 9 10

Rendering in the Cloud / GCP Preemptible VMs now up to 33% cheaper

« Last post by Render Guru on August 10, 2016, 04:33:46 AM »

Announcements / Qube! Core (core/supervisor/worker) 6.8-3c patch release is available

« Last post by shinya on August 04, 2016, 01:50:38 AM »

A new patch release, 6.8-3c, of the Qube! Core, Supervisor, and Worker software is now available.

This is a recommended update to all 6.8 users, but especially to those on the 6.8-3 supervisor, as it fixes a critical issue found in the said version where priority- or cluster-based preemption refuses to work.

For those using the Qube Installer utility, the 6.8-3 manifest file has been updated. If you are using version 2.1-0 or later of the QubeInstaller installer utility, it will auto-detect if a manifest has a newer version and offer to download it.

##############################################################################
@RELEASE: 6.8-3c

This is a patch release of core/supe/worker only, with some critical fixes to
6.8-3 for all platforms.

==== CL 16389 ====
@FIX: calls to qb.reportwork that happen very close together can cause the supervisor to deadlock on a single frame's status

==== CL 16379 ====
@FIX: case-insensitive parsing of template names in qbwrk.conf when listed for template inheritance

The following now works (hostA will be in the "big" group):

[BigNode]
worker_groups = "big"

[hostA] : bignode

JIRA: QUBE-1809

==== CL 16369 ====
@FIX: don't mark the instance as failed if there is one more command to run, the child process has already exited, and the command is sys.exit(0); happens when maya is shut down with its native quit() function.

==== CL 16338 ====
@CHANGE: database checks script splits logging levels between stdout and stderr

==== CL 16286 ====
@FIX: checkDiskUsage fails when --mysql option is used and root can't authenticate

==== CL 16266 ====
@NEW: a new command-line utility for performing both database health checks and data integrity checks

==== CL 16247 ====
@FIX: fixed qb.workid() in callbacks to return the correct workid of the current callback context (it had been always returning None)

Also changed qb.jobstatus(), workstatus(), and subjobstatus() so that, if
invoked in a callback giving no args (like a jobid and workid or subjobid),
they return the status of the respective thing (job, work, or subjob) of
the current callback context.

JIRA: QUBE-1763
ZD: 16105

==== CL 16235 ====
@FIX: a problem with the filtering added to avoid jobs with an ID of 0, in CL15821

ZD: 16006

==== CL 16229 ====
@FIX: On Windows, daemons (supe, worker) now ignore VMWare Virtual Ethernet Adapters when trying to pick a primary mac address (QbConnection.cpp) for the host, which is used to uniquely identify hosts

ZD: 14481

==== CL 16214 ====
@FIX: aerender AppFinder mangling first path conversion on Windows when using UNC

==== CL 16064 ====
@FIX: when job 'dev' attribute True, printing the job package with regex_errors causes the logParser to generate a false positive for the regex_errors match

==== CL 16049 ====
@NEW: add 'outputPath match required' to python-based jobs, frame/work is failed if no match is found

Announcements / Qube! ArtistView 6.8-3a patch release is available

« Last post by jburk on July 28, 2016, 07:40:50 PM »

A 6.8-3a patch release is now available for the Qube 6.8-x ArtistView. This is a recommended patch release for all customers running any version of Qube v6.8, and can be installed directly on top of any 6.8 version of Qube.

For those using the Qube Installer utility, the 6.8-3 manifest file has been updated. If you are using version 2.1-0 or later of the QubeInstaller installer utility, it will auto-detect if a manifest has a newer version and offer to download it.

Or you can download the patched version directly at: http://repo.pipelinefx.com/downloads/pub/qubeArtistView/current/

Full release notes are available on our documentation site: http://docs.pipelinefx.com/display/RELNOTES/ArtistView+6.8+Complete+Release+Notes

##############################################################################
@RELEASE: 6.8-3a
##############################################################################

==== CL 16405 ====
@FIX: agenda and instance timeouts are stripped from a job during resubmission
@FIX: resubmitted jobs have duplicate callbacks

==== CL 16340 ====
@FIX: agenda and instance timeouts set in AV submission UI's don't add the necessary callbacks to the job

==== CL 16100 ====
@FIX: frame batch and partition sizes can't be set larger than 99

==== CL 16098 ====
@FIX: appFinder (cross-platform) job submission UI fails to submit a job
@FIX: AttributeError: 'str' object has no attribute 'isEmpty'

==== CL 16079 ====
@CHANGE: change default VRED installation root on linux to /opt

==== CL 16077 ====
@FIX: VRED sequencer frames job fails to submit

==== CL 16068 ====
@CHANGE:Make package relocatable

==== CL 16022 ====
@FIX: VRED in-app submission is not compatible between VRED v8.0 and v8.5

==== CL 16018 ====
@NEW: add support for VRED Design users with "Viewpoint" rendering that doesn't use the sequencer

==== CL 16017 ====
@INTEG: main -> rel-6.8
-----
@FIX: per-frame logs not displayed when agenda name is not an integer

==== CL 16015 ====
@FIX: per-frame logs not displayed when agenda name is not an integer

==== CL 15989 ====
@CHANGE:Support for Maya's "Extension 2" by adding '.5' to the year in the path to Render.exe for Maya batch submission.

Rendering in the Cloud / 8 Tips for Scaling Rendering to the Cloud

« Last post by Render Guru on June 27, 2016, 08:31:58 PM »

Moonbot Studios Lead Pipeline TD Brennan Chapman, Google Product Manager Todd Prives and PipelineFX co-founder and CEO Richard Lewis, share "Tips and Tricks for Scaling Rendering Workloads into the Cloud" , including understanding data traffic patterns, matching hardware, and syncing data.

Whether you

Announcements / QubeInstaller 2.1-6 maintenance release is available

« Last post by BrianK on June 17, 2016, 06:14:34 PM »

QubeInstaller 2.1-6 maintenance release addresses the following issues:

qubeInstaller.exe --upgrade qube_manifest_<version>.qmf will do a forced upgrade based on the given qmf - even if upgrading to the same version. This effectively does the same thing as qubeInstaller.exe qube-upgrade_<version>.qks, but obviously, no qks needs to exist for the --upgrade option.
Fix issue where installer would crash if it couldn't write its kickstart (qks) file.
Fix issue where the installer would write a benign "UNKNOWN.plist" file in ~/Library/LaunchAgents when uninstall non-service components
Fix issue where supervisor installs would not show the "finished" button because of an internal crash.
Put a stopping condition on supervisor discovery which should prevent the occasional slow startup.
When installing a second supervisor and changing qb_supervisor/qb_domain via installer dialog, the qb_supervisor setting was being ignored if it was set to localhost or the local loopback.
When installing a second supervisor and changing qb_supervisor/qb_domain via installer dialog, the final page would ping the original supervisor and report that as being newly installed.
Support for new OSs CentOS 7.2, Ubuntu 16.04.
Improved support for OS X 10.10+

Rendering in the Cloud / 5 Steps to Move to the Google Cloud

« Last post by Render Guru on June 06, 2016, 04:41:07 PM »

Moving to the cloud can be daunting; often organizations struggle understanding where to begin and the steps required to realize a migration. In this one hour webinar, Google's migration architect, Peter-Mark Verwoerd will walk through a framework on how to assess cloud migration. Though the course of this presentation, you will also become familiarized with the services offered by Google Cloud Platform.

https://www.brighttalk.com/webcast/10619/205217

Developer Customization / Re: Hostorder by custom CPU-ranking

« Last post by Alexander on June 02, 2016, 08:09:32 AM »

Quote from: BrianK on June 01, 2016, 09:30:05 PM

This is an excellent tip.

For what it's worth, there also exists +host.processor_speed and +host.processors.avail. You can combine them in a host_order like so:

+host.processors.avail,+host.processor_speed

... which would mean, "Choose the machines with the fastest processors AND the most number of currently available processors (e.g. those processors not reserved by other jobs)".

Having said that, Alexander's suggestion is also perfectly valid and some may prefer it, as it is somewhat more concrete than the multi-key host order I've suggested, which is a bit too "black-box" for some.

Thanks for the tip, Alexander!

Thank you for the kind words!

Question about "+host.processors.avail", if the user has designer-license, will that one work or will it just think that the worker has 1 cpu?

Developer Customization / Re: Hostorder by custom CPU-ranking

« Last post by BrianK on June 01, 2016, 09:30:05 PM »

This is an excellent tip.

For what it's worth, there also exists +host.processor_speed and +host.processors.avail. You can combine them in a host_order like so:

+host.processors.avail,+host.processor_speed

... which would mean, "Choose the machines with the fastest processors AND the most number of currently available processors (e.g. those processors not reserved by other jobs)".

Having said that, Alexander's suggestion is also perfectly valid and some may prefer it, as it is somewhat more concrete than the multi-key host order I've suggested, which is a bit too "black-box" for some.

Thanks for the tip, Alexander!

Developer Customization / Hostorder by custom CPU-ranking

« Last post by Alexander on May 29, 2016, 04:27:40 PM »

Maybe this can help someone.
Scenario: You want to have the hostorder based on cpu. Ex Arnold-render etc

The job properties
Host Order: +host.comprank

qbwrk.conf on supe:
add this to each worker
worker_properties = "host.comprank=<INSERT NUMBER HERE>"

To find the comprank number I made a little python script. Not the prettiest code... :-)

Code: [Select]

import multiprocessing, cpuinfo, decimal, socket
host = socket.gethostname()
info = cpuinfo.get_cpu_info()

speed = info['hz_actual']
speed = speed[:-4]
speed = float(speed)

amount = multiprocessing.cpu_count()
rank = amount * speed
rank = decimal.Decimal(str(rank))
rank = int(round(rank,0))
line = host + ' ' + str(rank)

f = open('\\\\SERVER\\\\qube\\ranking\\ranking.log','a')
f.write(line + '\n')
f.close()

edit \\\\SERVER\\\\qube\\ranking\\ranking.log to where you want it saved.

module cpuinfo can be found here: https://pypi.python.org/pypi/py-cpuinfo

Run that script on each machine, one at the time.

This script could probably be done so that it writes direct to the qbwrk.conf. ;-)

Enjoy

Announcements / Qube! 6.8-3 released

« Last post by jburk on May 25, 2016, 04:06:21 AM »

This is a maintenance release of the Qube! Core/Supervisor/Worker/ArtistView/WranglerView products.

This is a recommended release for all customers running Qube v6.8.

Please see http://docs.pipelinefx.com/display/RELNOTES/PipelineFX+Release+Notes for complete release notes.

Pages: 1 ... 6 7 [8] 9 10