Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
From: David Nalley <david@gnsa.us>
Date: Sun, 3 Feb 2013 06:44:12 -0500
Message-ID: 
 <CAKprHVad7DcKXy1TLXDEjnVEjsF65JZRmmb7UWOc6nkxv2OZdg@mail.gmail.com>
Subject: [DISCUSS] Packaging password/ssh reset scripts
To: cloudstack-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi folks:

One of the discussions that came up while we were in Ghent was whether
or not to package the SSH key reset and password reset utilities, or
whether we should focus our PW/SSH efforts on cloud-init.

The points for consideration are essentially:

* If we begin packaging them, they will be expected to be maintained
over the long term - are we as a project ready to do that?
* Do we keep the scripts in the repo, or perhaps consider adding a
separate repo for the scripts themselves. (This would make it easier
for distribution packagers to consume - and even if they don't wish to
package all of CloudStack - packaging the scripts themselves would be
substantially easier.
* cloud-init has CloudStack support IIRC, does it make sense to adopt
that rather than doing our own thing, or perhaps to elect one as the
primary method.

--David