google-compute-engine

问题 While working on Udacity Deep Learning assignments, I encountered memory problem. I need to switch to a cloud platform. I worked with AWS EC2 before but now I would like to try Google Cloud Platform (GCP). I will need at least 8GB memory. I know how to use docker locally but never tried it on the cloud. Is there any ready-made solution for running Tensorflow on GCP? If not, which service (Compute Engine or Container Engine) would make it easier to get started? Any other tip is also

问题 I can not connect via ssh any more, I was be able to connect for almost 24 hours. All of a sudden, ssh stops working. I had many users and I also added a new (tomcat) user in that VM. I am get the below message when I try to ssh to my instance: "Permission denied (publickey,gssapi-keyex,gssapi-with-mic)." I ended up removing ~/.ssh/google_compute_engine* Removed the 'sshKeys' metadata from Cloud Engine Console Tried gcutil ssh again, this created new ~/.ssh/google_compute_engine file as well

问题 I'm a noob and using Wordpress on Google cloud. When attempting to upload a new theme, I get the following error message: The uploaded file exceeds the upload_max_filesize directive in php.ini . This is a limitation seems to be set by Google Compute Engine. I've found info about the limitation being set in the php.ini file, but I can't seem to locate that file anywhere. Can anyone give some idiot proof, step-by-step instructions to increase the upload size beyond 2MB? I've installed the WP

问题 Instance template is essential for creating managed instance group. In fact, Managed instance group is essential for creating an autoscaling group in GCP. This question is a part of another question's answer, which is about building an autoscaled and load-balanced backend. I have written the below answer that contains the steps to create an instance template. 回答1: Instance templates are global resources in GCP i.e the same template can be used to create managed instance groups in any regions

问题 We just switched over to Google Compute Engine and are having major issues with disk speed. It's been about 5% of Linode or worse. It's never exceeded 20M/s for writing and 10M/s for reading. Most of the time it's 15M/s for writing and 5M/s for reading. We're currently running a n1-highmem-4 (4 vCPU, 26 GB memory) machine. CPU & memory aren't the bottleneck. Just running a script that reads rows from PostgreSQL database, processes them, then writes back to PostgreSQL. It's just for a common

问题 I have set up an Google Cloud Compute Instance: Machine type n1-standard-1 (1 vCPU, 3.75 GB memory) CPU platform Intel Haswell Zone us-east1-c I can ssh in using the external address. I have installed the vncserver and can access it on port 5901 from localhost as well as the internal IP. I am trying to access it from the static, external IP address but it is not working. I have configured the firewall to open to port to 0.0.0.0/0 , but it is not reachable. Can anyone help? ------after further

问题 In one of my HTTP(S) LoadBalancer, I wish to change my backend configuration to increase the timeout from 30s to 60s (We have a few 502's that do not have any logs server-side, I wish to check if it comes from the LB) But, as I validate the change, I got an error saying Invalid value for field 'namedPorts[0].port': '0'. Must be greater than or equal to 1 even if i didn't change the namedPort. This issue seems to be the same, but the only solution is a workaround that does not work in my case

问题 I'm trying to have my GCE instance listen on multiple IP addresses (for SEO reasons - to host multiple low traffic sites on the same instance). Final objective: mydomain.com points to IP1, myotherdomain.es points to IP2, the GCE instance will listen on both IP1 and IP2 and serve content accordingly. I added a target instance pointing to my main instance and managed to create a forwarding rule like this: gcloud compute forwarding-rules create another-ip --port 80 --target-instance MY_TARGET

问题 I have created a ready to go MongoDB server on Google Cloud using the default parameters. Everything is working fine between them (there is communication and I can add DBs and collections). However, I can't connect to MongoDB on any external machine. I created the firewall rules in GCP allowing all the connections ("0.0.0.0./0") on the port 27017. I am running the command: giuseppe@ubuntu:~$ mongo --host rs0/104.154.xx.xxx,173.255.xxx.xxx,104.197.xxx.xxx giuseppe@ubuntu:~$ mongo --host rs0

问题 From Google's documentation: It is possible to attach a persistent disk to more than one instance. However, if you attach a persistent disk to multiple instances, all instances must attach the persistent disk in read-only mode. It is not possible to attach the persistent disk to multiple instances in read-write mode. If you attach a persistent disk in read-write mode and then try to attach the disk to subsequent instances, Google Compute Engine returns an error. So, I need to have a share