libcloud | THIS IS THE WRONG GITHUB PROJECT

Try to add a 10 min sleep as the first provisioner. Ubuntu AMIs come with automatic updates on. So, whenever an instance is started, It will get updated itself.

From the Console (https://cloud.google.com/console), select your project. When your project is open, select "APIs & auth" and then "Credentials" as shown below:

In Development: Preferably make one for each, could use one for all for testing purposes.

In production: For each user to use this service, create a service account.

When you download the service account, you should have it as a .pem or .json file. Use the email address from the service account (if you open the json/pem you shd be able to see the email) and give it the correct values region/project/email and path to the pem file.

The code you're using is correct, avoid using the name "ComputeEngine" since it may be a keyword (even though it probably isn't, best practice)

The problem was with my Pipfile.lock settings. It has a different format when replacing requirements.text. I changed the formatting like so:

The error message is not showing that is an error with the quota, but rather an issue with the zone resources, I would advise you to try a new zone.

Quoting from the documentation:

Even if you have a regional quota, it is possible that a resource might not be available in a specific zone. For example, you might have quota in region us-central1 to create VM instances, but might not be able to create VM instances in the zone us-central1-a if the zone is depleted. In such cases, try creating the same resource in another zone, such as us-central1-f.

Therefore when creating the script you should take this possibility into account even if it is not so common.

This issue is even more highlithed in case of preentible instances since:

Preemptible instances are finite Compute Engine resources, so they might not always be available. [...] these instances if it requires access to those resources for other tasks. Preemptible instances are excess Compute Engine capacity so their availability varies with usage.

UPDATE

To doublecheck what I am saying you can try to keep the preentible flag and change the zone to be sure the script it is working properly and it is a stockout happening during the evening (and since during the day it works this should be the case).

• If the issue it is really the availability -| you might consider to spin up preentible instance and if not available, catch the error and then either rely on normal one or on a different zone |-

As I promised I created on your behalf the feature request, you can follow the updates on the public tracker. I advise you to start it in order to receive the updates on the email:

• https://issuetracker.google.com/77734062

To answer my own question, the specific issue seen above was due to the system I was using. Once I switched to another system it proceeded even further however there is a bug I identified and filed in apache libcloud with a documented workaround inside the jira ticket here https://issues.apache.org/jira/browse/LIBCLOUD-972.

I think you should modify the auth_url and provider arguments. As following argument set is worked at my environment.

You can change the volume type of a EC2 instance, I wrote a post how to add more size and how to change volume type, I hope it helps you. http://www.dbigcloud.com/cloud-computing/237-como-ampliar-un-volumen-ebs-en-una-instancia-ec2-en-aws.html