[one-users] New simplified Sunstone view (self-service)

[Jon]

Hello,

Personally, I include at a minimum three unique public keys and would also
like to allow the end user to include their public keys as well.

That said, the context script just reads the SSH_PUBLIC_KEY from the
template, so as long as each key is new line terminated the keys end up in
the correct format in authorized_keys.

E.g.

SSH_PUBLIC_KEY = "ssh-rsa abc123 for at bar
ssh-rsa def456 bar at bar
ssh-rsa hij789 baz at bar"

Produces a properly formatted authorized_keys

(I really wish ssh keys were by default shown at the bottom of the template
when you create the template in sunstone, it's easy enough to change, but
it got old having to modify every template after creating it)

Does this new functionality change that?

Thanks,
Jon aa
On Jul 15, 2013 8:05 AM, "Daniel Molina" <dmolina at opennebula.org> wrote:

>
>
>
> On 15 July 2013 15:53, Daniel Molina <dmolina at opennebula.org> wrote:
>
>> Hi all,
>>
>> We are working on a new simplified sunstone view [1], that has been
>> requested by several users.
>>
>> https://twitter.com/dmamolina/status/355634576577679360
>>
>> In this view a user will be able to instantiate a new Virtual Machine in
>> three steps:
>>   1. Select a name and a number of vms
>>   2. Select an instance type.
>>   3. Select the OS image for this instance(s)
>>
>> An instance type is an OpenNebula template instead of an erb file.
>> Therefore, administrators can prepare as many templates (instance types) as
>> they want and make them available to different users/groups.
>>
>> In OpenNebula 4.0, the merge action [1] was included for templates. This
>> action allows us to define a base template and instantiate new virtual
>> machines providing extra information to this template.
>>
>> These templates must define all the required information such as network,
>> capacity, placement.. and leave the OS disk undefined, so the user can
>> specify the desired image
>>
>>
>> Feedback
>> =======
>> We would like to ask you (the community) if you are missing anything in
>> this view or if you would like to include anything else in this kind of
>> scenario.
>>
>
>
> Actually, there is a request from a tweet of Ricardo Duarte, where he
> wrote that the keypair and user data is missing.
>
> Currently, OpenNebula provides a way to define a default keypair per user
> and automatically include it in the virtual machine
>   1 Defiine a SSH_PUBLIC_KEY in the user template
>   2 Include this variable in the CONTEXT section of the base template
> (there is a checkbox in Sunstone for this):
>       SSH_PUBLIC_KEY = '$USER[SSH_PUBLIC_KEY]'
>
> Is this enough or are you using more than one keypair per user?
>
> Cheers
>
>
>>
>> Thank you for your feedback
>>
>> [1] http://opennebula.org/documentation:rel4.0:vm_guide#merge_use_case
>>
>> --
>> <http://opennebula.org/documentation:rel4.0:vm_guide#merge_use_case>
>>  <http://opennebula.org/documentation:rel4.0:vm_guide#merge_use_case>
>> Join us at
>> <http://opennebula.org/documentation:rel4.0:vm_guide#merge_use_case>
>> OpenNebulaConf2013 <http://opennebulaconf.com/> in Berlin, 24-26
>> September, 2013
>> --
>> Daniel Molina
>> Project Engineer
>> OpenNebula - The Open Source Solution for Data Center Virtualization
>> www.OpenNebula.org | dmolina at opennebula.org | @OpenNebula
>>
>>
>
>
> --
> Join us at OpenNebulaConf2013 <http://opennebulaconf.com/> in Berlin,
> 24-26 September, 2013
> --
> Daniel Molina
> Project Engineer
> OpenNebula - The Open Source Solution for Data Center Virtualization
> www.OpenNebula.org | dmolina at opennebula.org | @OpenNebula
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130715/e1b444ba/attachment-0002.htm>