Google Cloud Platform Blog: February 2014

Back in time: your Cloud Platform deployment history

Friday, February 28, 2014

What was the distribution of instances across zones for the past month?

What were the instances with production tag T at time range X?

What instances used an external IP address X?

What was the aggregated size of disks by zone for the past 7 days?

Data Pipeline sample applicationCloud History Tool

Reads the current Compute Engine instance, disk, and operations data using the Compute Engine REST API.

Transforms the data.

Loads the data into BigQuery.

Uses App Engine Cron Services to repeat steps 1 - 3 at scheduled intervals.

SELECT D.name, D.zoneName FROM [cloud_history.Disks] D LEFT OUTER JOIN FLATTEN([cloud_history.Instances], disks) I ON D.name = I.disks.deviceName AND D.snapshotId = I.snapshotId WHERE I.disks.deviceName IS NULL AND D.snapshotId = TIMESTAMP("YYYY-MM-DD hh:mm:ss") tutorial

here

Ocado uses Google Cloud Platform to make online food shopping a breeze

Friday, February 28, 2014

Our guest blog post today comes from James Donkin, General Manager Ocado Technology at Ocado, the only dedicated online supermarket in the UK and the world’s largest online grocery retailer.Google Cloud Platformused Google Apps since 2010

Leverage Google Cloud Platform features for your Hadoop deployments

Thursday, February 27, 2014

demonstratedHadoopconnectorApache HiveGoogle Cloud SQLnow supports the MySQL wire protocolsample applicationPigREADMECreate a Google Cloud SQL instanceGoogle Cloud ConsoleGoogle Cloud SQL instance

Choose the Compute Engine zone of the Compute Engine instance running Hive as the preferred location for the Cloud SQL instance.

Select "Assign an IP Address" to the Cloud SQL instance.

Add the external IP address of the Compute Engine instance as an Authorized IP Address. Be sure to append "/32" to the IP address entered in this field.

Define a root password for MySQL (it's good practice).

Install MySQL client and MySQL JDBC DriverCreate the hivemeta database and the user to access it

Connect to the Google Cloud SQL instance

Create a database called hivemeta (Hive requires the database to use latin1 character encoding, which you'll need to specify explicitly).

Create the database user (for example hdpuser).

Issue grants on the hivemeta database to the database user.

Configure Hive to use Cloud SQL

App Engine 1.9.0 now available

Wednesday, February 26, 2014

App Engine 1.9.0Modules APIMapReducePHP runtimeApp Engine Modules is now Generally AvailablApp Engine ModulescommunicateJavaPythonJavaPythonMapReduce library for JavaMapReduce librariesMapReduce library for JavaGoogle Cloud Storagebug fixessamplesPHPrelease notes

Jeff Dean to Speak at Google Cloud Platform Live on March 25

Tuesday, February 25, 2014

Google Senior Fellow Jeff DeanGoogle Cloud Platform LiveUrs HölzleSpannerBigTableMapReducerequest an invitation to join us in-person in San FranciscoGoogle New York CityGoogle Seattleyou can always tune in online

Google Cloud Platform Pricing Calculator Open for Business

Monday, February 24, 2014

Google Cloud PlatformGoogle Cloud Platform Pricing CalculatorGoogle Cloud Platform Pricing Calculator

Google Cloud Platform Pricing Calculator

Google Cloud SQL and PHP App Engine Apps

Friday, February 21, 2014

App Engine for PHPannouncedGoogle Cloud SQLMySQL command-line clientMySQL WorkbenchphpMyAdminCloud SDKset up phpMyAdmin as an App Engine appit is trivial to get WordPress running on App Engine

The per-use billing plan means you only pay for the time the database is being accessed; the rest of the time you only pay for storage. You can also start with a small instance costing just $0.025/h, and at any time you can increase capacity with just a few seconds downtime.

The same scalability applies to storage: you don't need to reserve space in advance, and you only pay for the data you actually store — up to a whopping 500GB.

Reliability and robustness are crucial, so all data is replicated multiple times in multiple locations, and automatically backed up. All data is also encrypted when stored, and when on Google's networks.

KissflowWordPress starter projectGoogle Cloud Platform project sign-upCloud SQL documentationGetting Started with App Engine for PHP

Input → Transform → Output → Done!

Tuesday, February 18, 2014

Data Pipeline applicatioGoogle App Engine Pipeline API

URLs via HTTP

Google Cloud Datastore

Google Cloud Storage

Google App Engine using the Google App Engine Pipeline API

Google Compute Engine using Apache Hadoop

BigQuery

Google Cloud Storage

Github

Editing the config file

Github

Using dbShards and Cloud SQL to provide MySQL Scalability and Reliability

Thursday, February 13, 2014

Today’s guest blog comes from Cory Isaacson, CEO/CTO at CodeFutures. CodeFutures is the maker of dbShards Technology, a proven suite of components and tools for working with relational database management systems. dbShards database clusters have been in production for over 3 years in demanding applications supporting multi-terabyte databases with high read and write loads.

http://www.genoo.comin this case studyLearn more about dbShards/Migrate here

LiveHive leverages Google Cloud SQL to build better sales products for customers

Wednesday, February 12, 2014

Today’s guest post comes from Fritz Mueller, vice president of products at LiveHive, a cloud-based sales engagement platform that allows B2B sales teams to track customer touchpoints in real-time. Google Cloud SQL

Join Us at Google Cloud Platform Live on March 25, 2014

Wednesday, February 12, 2014

Google Cloud Platform Live in San Franciscoattend the event in San FranciscoNew York CitySeattletune in on YouTube

Google Cloud SQL now Generally Available with an SLA, 500GB databases, and encryption

Tuesday, February 11, 2014

Google Cloud SQLGoogle App EngineGoogle Compute Engine
Secure Encrypted Data

Customer data, including in database tables and temporary files, is automatically stored encrypted (with encryption of backups coming soon).

All Cloud SQL traffic on Google’s internal networks is encrypted.

External connections can be encrypted using SSL.

All hosts and Google App Engine applications connecting to your instance must be explicitly authorized.

MySQL user grants can be used to control access at the database, table, or even column level.

Data is replicated multiple times in multiple locations.

Scheduled backups are automatically taken by default.

Larger databasesSLA for availabilitySLADeveloper traction

Costco uses Google Compute Engine and Cloud SQL to run public e-commerce sites. As Don Burdick, Senior Vice President of Global Ecommerce at Costco, says, “Costco is the world's leading membership club warehouse with annual sales exceeding $100B. As part of our philosophy to keep costs down and pass savings on to our members, in June 2013 we implemented our ecommerce site for Mexico on Google Cloud Platform. The site has been operational since October 2013 and the Google Cloud Platform performance has exceeded our expectations. As a result of this project's success, we're currently migrating the website of one of our other countries to Google Cloud Platform.”

LiveHive is a social selling application used by 25,000+ sales professionals. Fritz Mueller, Vice President of Products says, "We found Google's Cloud SQL service to be an ideal combination of performance and convenience. Performance is key to us because we provide our customers with real-time data about their sales execution. With Google's Cloud SQL, we focus on building the functionality our customers want without worrying about reliability, scalability and upgrades."

Ocado manages logistics and e-commerce for some of the largest supermarkets in the UK. General Manager James Donkin says, “We're excited about the flexibility Cloud SQL brings to support quick development cycles that foster innovation, while scaling easily when required.”

Mark Kornfilt, co-founder of Live video streaming platform Livestream, said “Thanks to Google App Engine and Cloud SQL, we were able to go from a new product concept to its launch in less than two months. This allows us to focus on building the product instead of worrying about operations, and provides all the tools needed to build a robust, reliable and scalable web app out of the box.”

Try it nowhere

Google Cloud Platform provides support for HIPAA Covered Entities

Wednesday, February 5, 2014

Health Insurance Portability and Accountability Act

ISO 27001: ISO 27001 is one of the most widely recognized, internationally accepted independent security standards. After earning ISO 27001 for Google Apps in 2012, we renewed our certification again last year for Google Apps and received the certification for Google Cloud Platform.

SOC2, SSAE 16 & ISAE 3402: Companies use the SOC2, SSAE 16 Type II audit, and its international counterpart ISAE 3402 Type II audit, to document and verify the data protections in place for their services. We’ve successfully completed these audits for Google Apps every year since 2008 (when the audits were known by their previous incarnation, SAS 70) and we did so again last year for Google Apps and Google Cloud Platform.

HIPAA: Late last year, we started entering into BAAs to allow Google Apps customers to support HIPAA regulated data. This year we have begun entering into BAAs with our Google Cloud Platform customers.

contact

PHP App Engine Apps and File System Concepts

Tuesday, February 4, 2014

readcan’t writeGoogle Cloud Storage

Set up a Cloud project and set up GCS in that project (as necessary), and configure your Cloud project so that your App Engine App can access it

Modify some app file paths to point to a GCS bucket in your Cloud Project

Modify app file upload forms so that they use GCS to receive the uploaded files

deployeddocumentationThe Application Filesystemread-onlyvulnerabilitiesstaticallyapplication_readabledeployeddevelopment serverGoogle Cloud Storage gs:///path/to/file$fp = fopen("gs://my_bucket/some_file.txt", "w"); fwrite($fp, "Hello"); fclose($fp); $options = [ "gs" => [ "Content-Type" => "text/plain" ]]; $ctx = stream_context_create($options); file_put_contents("gs://my_bucket/hello.txt", "Hello", 0, $ctx); documentationherenot support file (object) appendsincludedAdmin ConsoleLogs APIcommand‘Including’ Files From GCSincluderequiredirectivegoogle_app_engine.allow_include_gs_buckets = "bucket_1, bucket_2"TwigSmartyUploading Files to GCS From Your Appupload URLprocesseddocumentationWordPress on App EnginepluginA Recap

Set up a Cloud project and GCS in that project (as necessary), and configure your Cloud project so that your App Engine App can access it.

Modify some file paths to point to a GCS bucket in your Cloud Project. With the GCS stream wrapper, your file-system-related code should then just work as before. (An exception is file appends).

Modify app file upload forms so that they use GCS to receive the uploaded media.

memcacheGoogle Cloud SQLCloud Datastore