[openstack-dev] [heat] status of instance_user/admin_user in heat

Matt Fischer matt at mattfischer.com
Tue Jun 30 14:48:52 UTC 2015


Looks like this change is what I need, but was the code supposed to not set
it to ec2-user when instance_user is unset? I've always had it unset and
it's always set it to ec2-user, certainly for Ubuntu images anyway, I've
not tested others.


On Tue, Jun 30, 2015 at 8:22 AM, Thomas Herve <therve at redhat.com> wrote:

>
> > Heat devs,
> >
> > What is the status of the instance_user config option and the corollary
> > OS::Nova::Server::admin_user field? Our users find it very confusing when
> > Heat creates a VM with a user called ec2-user. While I've told them to
> > explicitly set admin_user, the documentation claims its deprecated since
> > Icehouse. Will it be removed? Along the same lines, instance_user in the
> > config also claims to be deprecated and slated for removal in Kilo, it is
> > also still there in master. So what's the right behavior here? Should I
> > tell heat users that it's safe/recommended to set admin_user or not?
>
> Hi,
>
> It's been deprecated for a while, and will be hidden in the next release
> (see https://review.openstack.org/#/c/103928/) if everything goes well.
>
> As an operator, you shoud set the instance_user configuration value to the
> empty string, so that your users get the default user from the image.
> That's the recommanded mode of operation.
>
> Cheers,
>
> --
> Thomas
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150630/86b3b66e/attachment.html>


More information about the OpenStack-dev mailing list