That makes sense, although my idea was actually that when you launch an AMI you wouldn't have to guess the login name. This of course only works if other distributions would agree on that name. So I am kind of hoping for the exact opposite :-) I am working on the expand-volume script right now by the way, would you care to join me on gtalk or something?
Anders On 10 November 2012 16:51, Brian Gupta <[email protected]> wrote: > admin is fine too... basically I just wanted Debian to have their own > default user that wasn't the same as other OSes use. IE: I don't love > ec2-user because people following docs out there with ec2-user would be > following docs for a different OS, and having it be the same as the Amazon > Linux AMIs (which are CentOS based) might end up being more confusing than > helpful. > > -Brian > > On Sat, Nov 10, 2012 at 10:32 AM, Anders Ingemann <[email protected]>wrote: > >> > I think that it is important to underline that the account is >> privileded. How about 'Administrator' ? Seriously. >> It's a bit long to type. "admin"? I can change that in the bootstrapper >> pretty quickly. >> I think this could be a username pretty much every cloud provider and >> distribution could agree on. >> >> >> Anders >> >> >> >> On 9 November 2012 00:39, Charles Plessy <[email protected]> wrote: >> >>> Hello everybody, >>> >>> Le Thu, Nov 08, 2012 at 10:38:07AM +0000, Bromberger, James a écrit : >>> > >>> > 1) SSH Username: 'debian' is an obvious choice. Ec2-user is the other. >>> Time >>> > for an informal vote here? >>> >>> I think that it is important to underline that the account is privileded. >>> How about 'Administrator' ? Seriously. >>> >>> > 3) cloud-init - yes, but it's going to be some years for stable/main. >>> Charles >>> > - your thoughts? >>> >>> Help ! http://lists.debian.org/debian-cloud/2012/11/msg00003.html >>> >>> > 4) CLI tools - not initially here. There's lots to discuss with >>> regards to >>> > packages of it; who should maintain it, what is the copyright, and >>> where >>> > should the repo be. I would love to, but I don't have answers for those >>> > questions right now. >>> >>> They are non-free, so I think that we should not have them by default. >>> Packaging them in the non-free section if the license allows would be a >>> good >>> compromise. Then, scripts ą la cloud-init could be turned on to enable >>> auto-updates for the users who want to. >>> >>> We also have the euca2ools, which do not implement all the API (no >>> '--instance-initiated-shutdown-behavior terminate' yet, for instance), >>> but they >>> are Free and patches may be welcome. >>> https://github.com/eucalyptus/euca2ools >>> >>> > 9) It was not a Debian security issue - but an image generation that >>> left a >>> > X509 key visible in the block device. >>> >>> That is one of the reasons why I like my approach with Debian Installer: >>> 1) >>> install Debian on a EBS volume in the cloud and 2) bless that volume from >>> outside the cloud, so that no password or private key transits on the >>> installer >>> or installed system. >>> >>> Have a nice day, >>> >>> -- >>> Charles Plessy >>> Tsurumi, Kanagawa, Japan >>> >>> >>> -- >>> To UNSUBSCRIBE, email to [email protected] >>> with a subject of "unsubscribe". Trouble? Contact >>> [email protected] >>> Archive: >>> http://lists.debian.org/[email protected] >>> >>> >> > > > -- > <http://aws.amazon.com/solutions/solution-providers/brandorr/> > >
