Any news when Tensorflow 2 will be supported on Google Cloud AI platform?
According to the list, 1.15 is the last version to be supported: https://cloud.google.com/ml-engine/docs/runtime-version-list
we will support TF 2.1 officially in early Feb due to large corresponding changes on service. Thank you for your patience!
Add a dependency tensorflow-gpu==2.0 to setup.py file to train with Tensorflow 2.0 in AI Platform run-time version 1.15. Tensorflow 2.1 can't use GPUs due to mismatch in CUDA libraries, but you can train with CPUs. Be careful that other dependencies don't overwrite tensorflow-gpu. Disclaimer: I trained just one job this way, and this is a really hacky solution.
Tensorflow 2.1 runtime version is available as of March 9th
https://cloud.google.com/ai-platform/training/docs/runtime-version-list
Related
Is SageMaker Distributed Data-Parallel (SMDDP) supported for keras models?
In documentation it says "SageMaker distributed data parallel is adaptable to TensorFlow training scripts composed of tf core modules except tf.keras modules. SageMaker distributed data parallel does not support TensorFlow with Keras implementation." https://docs.aws.amazon.com/sagemaker/latest/dg/data-parallel-modify-sdp.html
But inside the training script and how to modify it, I can see the tf.keras and tf.keras.model is used. https://sagemaker.readthedocs.io/en/stable/api/training/sdp_versions/v1.0.0/smd_data_parallel_tensorflow.html
tf.keras.Sequential model is usable. However, not all other keras submodules are available yet. This may have changed over the subsequent version releases v1.4 and v1.5
I couldn't stomach purchasing the $150 for GCP's support service for this one question. I'm just looking to understand the schedule for Cloud Build Node.js versions. It's still stuck on Node.js v10.10 and my projects are starting to require higher versions to build. According to Cloud Build's changelog, I don't believe the Node.js version has updated in years. Any ideas?
As per the official Github repository:
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js.
So, this means it should work with Node.js 12 and the updates should be more constant. In addition to that, in here, it says that if you are using a Cloud Build config file, you can use Node.js 12, so the Node.js' latest version should be compatible with Cloud Build.
To summarize, by the repository, it should follow Node.js schedule. However, in case you think this is not occurring, I would recommend you to raise a bug on the Google's Issue Tracker - it's free, by the way - so they can assess this.
I have a tensorflow 2.0 model I would like to deploy to an AWS sagemaker endpoint. I have moved the model to S3 bucket and executed the following code, but get below error because there is no TF 2.0 image. If I try to deploy with different version (e.g. 1.4, 1.8) I get ping time out errors.
Is it possible to create one easily? I can't find a good tutorial to follow. Or will Amazon deploy one at some point.
Failed. Reason: The image '520713654638.dkr.ecr.eu-west-1.amazonaws.com/sagemaker-tensorflow:2.0-cpu-py2' does not exist..
from sagemaker.tensorflow.model import TensorFlowModel
sagemaker_model = TensorFlowModel(model_data = 's3://sagemaker-eu-west-1-
273649867642/model/model.tar.gz',
role = role,
framework_version = '2.0',
entry_point = 'train.py')
%%time
predictor = sagemaker_model.deploy(initial_instance_count=1,
instance_type='ml.m4.xlarge')
Also no images seem to support python 3 even though they suggest you define that when setting up the model.
"The Python 2 tensorflow images will be soon deprecated and may not be supported for newer upcoming versions of the tensorflow images.
Please set the argument "py_version='py3'" to use the Python 3 tensorflow image"
SageMaker currently do not support TensorFlow 2.0 yet (neither py2 or py3). But it will be available with SageMaker soon.
As regard with Python versions. For the current supporting TensorFlow versions, py2 is supported, however, after Jan. 1, 2020, all future framework versions will not support py2 anymore.
The docs for setting up Google Cloud ML suggest installing Tensorflow version r0.11. I've observed that TensorFlow functions newly available in r0.12 raise exceptions when run on Cloud ML. Is there a timeline for Cloud ML supporting r0.12? Will switching between r0.11 and r0.12 be optional or mandatory?
Yes, you can specify --runtime-version=0.12 to get a 0.12 build. This is a new feature and is documented at https://cloud.google.com/ml/docs/concepts/runtime-version-list
Note, however, that the 0.12 build is not yet considered stable and the exact Tensorflow build provided may change. Once the 1.0 version of Tensorflow is available, that will also be supported and the pre-1.0 versions of Tensorflow will begin to be deprecated.
(See https://cloud.google.com/sdk/gcloud/reference/beta/ml/jobs/submit/training for usage.)
The documentation for CloudFoundry indicates that Node.js version 0.8.2 is supported. However, when I run "vmc runtimes" against my local micro edition, it only lists node and node06 (not node08)
I'm running 0.8.2 locally on my box -- how can I upgrade Micro edition so that it also has 0.8.2 installed?
Micro Cloud Foundry 1.2 was released before Node.js 0.8.2 support was added. MCF currently cannot be upgraded to support it. However, a new MCF version is planned for the very near future which will bring parity to all the feature on CloudFoundry.com. We also plan a faster release cadence of MCF so it doesn't fall behind on features.
It's not completely trivial to patch MCF 1.2 to add node 0.8, you'd need to install the relevant packages as well as add information to the Cloud Foundry manifest files to enable it to advertise the node08 runtime.
However, the next Micro Cloud Foundry release should be available pretty soon so if you can hold on just a little longer, we should have some good news for you :-)
Out of interest, what application are you looking to build / run that requires 0.8.x?
Micro Cloud Foundry has just been updated to be in sync with the codebase on github so it now supports Node.js 0.8.2. Read the announcement here: http://blog.cloudfoundry.com/2012/11/08/new-release-of-micro-cloud-foundry/