Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DD796200C1A for ; Mon, 13 Feb 2017 21:52:42 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DC226160B60; Mon, 13 Feb 2017 20:52:42 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2980E160B4A for ; Mon, 13 Feb 2017 21:52:42 +0100 (CET) Received: (qmail 21710 invoked by uid 500); 13 Feb 2017 20:52:41 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 21597 invoked by uid 99); 13 Feb 2017 20:52:40 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2017 20:52:40 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id B7496DFC31; Mon, 13 Feb 2017 20:52:40 +0000 (UTC) From: rafaelweingartner To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1919: CLOUDSTACK-9763: set ssh public key when creating vm... Content-Type: text/plain Message-Id: <20170213205240.B7496DFC31@git1-us-west.apache.org> Date: Mon, 13 Feb 2017 20:52:40 +0000 (UTC) archived-at: Mon, 13 Feb 2017 20:52:43 -0000 Github user rafaelweingartner commented on the issue: https://github.com/apache/cloudstack/pull/1919 @serbaut I would only like to make a few questions to see if I understood the issue here, before evaluating the code any further. When you first deploy the VM, the keys are delivered to the newly deployed VM, right? The problem only happens on reboots? Do we need to always keep sending the same access keys? Is not one time enough? Of course, if the keys are changed, we should send them; but otherwise, it feels that we should not need to keep sending them. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---