google-managed-vm

Managed VM not running Cloud SQL Proxy

由 萝らか妹 提交于 2019-12-12 02:17:18
问题 Launching a Managed VM with a Java application, the following appengine-web.xml <?xml version="1.0" encoding="utf-8"?> <appengine-web-app xmlns="http://appengine.google.com/ns/1.0"> <application>thmadmin-ben</application> <version>master</version> <threadsafe>true</threadsafe> <vm>true</vm> <manual-scaling> <instances>1</instances> </manual-scaling> </appengine-web-app> I don't appear to have a Cloud SQL proxy running on the managed VM. Do I need to add an app.yaml file or define something

Failure deploying AppEngine version because of Cloud Storage JSON API enablement

由 こ雲淡風輕ζ 提交于 2019-12-11 05:01:03
问题 I am trying to deploy to Google AppEngine. (More precisely: Managed VM.) I ran gcloud preview app deploy d:\dev\mytest\yaml-war\app.yaml --version=joshua20160316d --project=mytest-test1 . After about 30 minutes, it failed. The error message directs me to log lines in the Cloud Developer Console (see below) which tell me that access to the Cloud Storage JSON API needs to be enabled. However, the Developer Console shows that the Cloud Storage JSON API is already enabled. (See screenshot.) Also,

gcloud socketIO is not working on multi-instances

由 ￡可爱￡侵袭症＋ 提交于 2019-12-10 22:24:42
问题 I am working with socketIO + Nodejs over gcloud app-engine with managed vms. I am facing a problem that when I use manual scaling, the gcloud working well with sockets. But when I use dynamic scaling, sockets not working at all, I think it doesn't work because of the port forwarding problem with two instances! here's my app.yaml instances handling that works. manual_scaling: instances: 1 resources: cpu: 0.1 memory_gb: 0.1 disk_size_gb: 10 When I remove them, sockets not works at all. Is there

Appengine deployments are extraodinarily slow today?

由 ▼魔方 西西 提交于 2019-12-06 10:37:48
We have a small java project need to deploy it include 9000+ files command : mvn gcloud:deploy but I get the Log: ... [INFO] INFO: Uploading [/home/steven/work/idigisign/target/appengine-staging/__static__/node_modules/rx/src/core/linq/observable/when.js] to [7dfb30ad32893c5042dba03601f006a40419fab0] [INFO] DEBUG: Uploading [/home/steven/work/idigisign/target/appengine-staging/assets/global/plugins/bootstrap-switch/js/bootstrap-switch.min.js] to [7e0725897d7b99c3c33b56915d202e2dde552ea9] [INFO] INFO: Uploading [/home/steven/work/idigisign/target/appengine-staging/assets/global/plugins

How to permanently delete Google managed VMs

由 生来就可爱ヽ(ⅴ＜●) 提交于 2019-12-03 19:55:38
问题 I am unable to permanently delete Google App Engine managed VMs I've created. I've deleted them multiple times both from the developer's console and by using the gcloud command. In every case the command completes successfully and the VM is deleted, but then almost immediately Google creates a brand new VM to take its place. Does anyone know how to permanently delete managed VMs? Thanks. 回答1: We are working on improving this experience. For now, though, one workaround is to deploy a non

Java connect to Cloud SQL 2nd Gen from Appengine Managed VM

由 ￣綄美尐妖づ 提交于 2019-11-30 16:12:54
问题 Trying to setup connection to Clond SQL 2nd Generation for a Java Appengine with Managed VM. What I got: VM is using Appengine Compat mode ( FROM gcr.io/google_appengine/java-compat ) I see a MySQL pipe on the host (SSHed, I can see /cloudsql/** socket), but default MySQL Java driver doesnt support unix sockets Google Driver seems to be unsupported on Managed VM ( java.lang.ClassNotFoundException: com.mysql.jdbc.GoogleDriver ) and I cannot connect to MySQL by IP w/o driver it's No suitable

How to permanently delete Google managed VMs

由 痴心易碎 提交于 2019-11-30 12:44:47
I am unable to permanently delete Google App Engine managed VMs I've created. I've deleted them multiple times both from the developer's console and by using the gcloud command. In every case the command completes successfully and the VM is deleted, but then almost immediately Google creates a brand new VM to take its place. Does anyone know how to permanently delete managed VMs? Thanks. We are working on improving this experience. For now, though, one workaround is to deploy a non-Managed VM instance as the default version and delete any other versions that are Managed VM-based. Again, this

Cannot run Google App Engine custom managed VM: --custom-entrypoint must be set error

由 China☆狼群 提交于 2019-11-30 04:06:00
PROBLEM DESCRIPTION I am trying to create a custom managed VM for Google App Engine that behaves identically to the standard python27 managed VM provided by Google. (I'm doing this as a first step to adding a C++ library to the runtime). From google documentation , the following Dockerfile specifies the standard python27 runtime: FROM gcr.io/google_appengine/python-compat ADD . /app I have verified that this is the right Dockerfile by examining the one generated by gcloud preview app run when using the standard python27 runtime. It is identical to this. But when I run my application with this
订阅 google-managed-vm