Hello community, here is the log from the commit of package google-daemon for openSUSE:Factory checked in at 2015-12-03 13:31:56 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/google-daemon (Old) and /work/SRC/openSUSE:Factory/.google-daemon.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "google-daemon" Changes: -------- --- /work/SRC/openSUSE:Factory/google-daemon/google-daemon.changes 2015-08-03 17:22:40.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.google-daemon.new/google-daemon.changes 2015-12-03 13:31:58.000000000 +0100 @@ -1,0 +2,8 @@ +Mon Nov 23 19:44:55 UTC 2015 - rjsch...@suse.com + +- Update to version 1.2.10 (bsc#956339,bsc#956340) + + Improved documentation + + Refactored and improved script that runs on boot +- Version consistency with google-startup-scripts + +------------------------------------------------------------------- Old: ---- google-daemon-1.2.7.tar.bz2 New: ---- google-daemon-1.2.10.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ google-daemon.spec ++++++ --- /var/tmp/diff_new_pack.wszKC1/_old 2015-12-03 13:31:59.000000000 +0100 +++ /var/tmp/diff_new_pack.wszKC1/_new 2015-12-03 13:31:59.000000000 +0100 @@ -17,7 +17,7 @@ Name: google-daemon -Version: 1.2.7 +Version: 1.2.10 Release: 0 Summary: VM management inside GCE License: Apache-2.0 ++++++ google-daemon-1.2.7.tar.bz2 -> google-daemon-1.2.10.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/google-daemon-1.2.7/README.md new/google-daemon-1.2.10/README.md --- old/google-daemon-1.2.7/README.md 2015-07-11 02:13:30.000000000 +0200 +++ new/google-daemon-1.2.10/README.md 2015-09-24 21:47:38.000000000 +0200 @@ -2,17 +2,21 @@ Google daemon runs in the background and provides the following services: + Creates new accounts based on the instance metadata. -+ Configures ssh to accept the accounts' public keys from the instance metadata. ++ Configures SSH to accept the accounts' public keys from the instance metadata. ++ Adds IP addresses of network load balancers as aliases of the external Ethernet interface ++ Resyncs clock if skewed due to [live migration](https://googlecloudplatform.blogspot.com/2015/03/Google-Compute-Engine-uses-Live-Migration-technology-to-service-infrastructure-without-application-downtime.html) -Google daemon is typically located at: +Google Daemon services are typically located at: - /usr/share/google/google_daemon/manage_accounts.py + /usr/share/google/google_daemon/ -Your users can create ssh keys for accounts on a virtual machine using [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) or manually using these steps: +#### Account synchronization + +Your users can create SSH keys for accounts on a virtual machine using [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) or manually using these steps: # Generate the ssh keys $ ssh-keygen -t rsa -f ~/.ssh/google_compute_engine - + # Create public RSA key in OpenSSH format $ ssh-rsa [base-64-encoded-public-key] [comment] @@ -25,7 +29,7 @@ "value": "<ssh-keys-value>" ] } - + `<ssh-keys-value>` is a newline-separated list of individual authorized public ssh key records, each in the format: <username>:<public-ssh-key-file-contents> @@ -44,7 +48,7 @@ } ] } - + For more information about the metadata server, read the [metadata server](http://developers.google.com/compute/docs/metadata "metadata server") documentation. Inside a virtual machine, a cron job runs every minute to check if project or instance metadata was updated with the new sshKeys value, and makes sure those users exist. It also checks that the keys are in the `~$USER/.ssh/authorized_keys` file.
