[openstack-dev] [heat] status of instance_user/admin_user in heat
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? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat] status of instance_user/admin_user in heat
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. It's a common misconception. Unset is different from the empty string. If you don't set it, it keeps using the default value, which is ec2-user. If you set it to the empty string, it keeps whatever the image is using. If you don't that you shouldn't need this change. -- Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat] status of instance_user/admin_user in heat
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 the...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat] status of instance_user/admin_user in heat
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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
