[Fiware-lab-federation-nodes] distributed keystone solution

Fernando López Aguilar fernando.lopez at fiware.org
Tue Jul 11 09:05:22 CEST 2017


HI Giorgio et all,

Firstly, thank you for your response. I really appreciate your comments. I
give answers of them inline.

Hi Fernando,

How you know, we are working to translate our current centralized keyrock
> solution to a distributed keystone solution in which the first step is to
> translate to a Keystone (Liberty) centralized solution. This also involve
> the migration to a Horizon portal with our CSS FIWARE style. This last two
> steps are almost finished and we have planned to make the final migration
> on 18th July.
>

In Genoa FIWARE Lab node, we are using a standard Openstack Kilo
installation.
Does the new keystone management requires any action (node admin side)? If
yes, can you share all info needed to upgrade?

No, the current action only concern to the Spain node, from all of you the
only action that it was required should be an update of the token due to it
will be offered by a new component (keystone) and not the previous one
(keyrock).

It's a question of configuration file updates? If yes, there is any script
file or any guide/README available?

Nothing to do with configuration files. When we move to a distributed
Keystone solution you will need to make some changes on it, but for the
moment this migration is transparent for you.

The purpose of this email is to share with you the current status of the
> migration but more important to share with you the new process to create
> accounts. As you know, in OpenStack, if you planned to create a new
> account, if is something that have to be done by the administrator of the
> OpenStack going into Horizon. It means that there is no automatic way (at
> the moment if I could remember) to create accounts in OpenStack.
>

Therefore, our ideas are to modify the login landing page to add two
> buttons andin that way control the request of new accounts and afterward
> using some ticketing system control or manage the manual creation of those
> OpenStack accounts.
>

Not fully clear to me; do you mean that it will be up to the FIWARE Lab
administrators to open an account on behalf of the final user?

If I am not wrong, in OpenStack, if you want to create a new user, the
administrator(s) has/have to do it manually. There is no API functionality
to do it automatically.

In a first step, it could be manage through a specific project in JIRA and
> in that way we do not lose any creation request. Honestly, I do not like so
> much this approach but I cannot find any other alternative at the moment. I
> would like that this process should be more automatic in order to not
> overload FIWARE Lab administrators.
>

I see. I also admit that the fiware.org website workflow to open an account
and proceed (final user side) is not super clear, right now (my modest
opinion).

Good we have the same opinion, it is way I try to share our ideas to
improve it and we would like to hear your opinions taking into account that
we will use it in short time. Therefore, we would like to hear from you
what do you think that should be an option to deal with it.

Fernando

Thanks & regards

On 11 July 2017 at 08:33, Giorgio Robino <giorgio.robino at cnit.it> wrote:

> Hi Fernando,
>
> How you know, we are working to translate our current centralized keyrock
>> solution to a distributed keystone solution in which the first step is to
>> translate to a Keystone (Liberty) centralized solution. This also involve
>> the migration to a Horizon portal with our CSS FIWARE style. This last two
>> steps are almost finished and we have planned to make the final migration
>> on 18th July.
>>
>
> In Genoa FIWARE Lab node, we are using a standard Openstack Kilo
> installation.
> Does the new keystone management requires any action (node admin side)? If
> yes, can you share all info needed to upgrade?
> It's a question of configuration file updates? If yes, there is any script
> file or any guide/README available?
>
> The purpose of this email is to share with you the current status of the
>> migration but more important to share with you the new process to create
>> accounts. As you know, in OpenStack, if you planned to create a new
>> account, if is something that have to be done by the administrator of the
>> OpenStack going into Horizon. It means that there is no automatic way (at
>> the moment if I could remember) to create accounts in OpenStack.
>>
>
> Therefore, our ideas are to modify the login landing page to add two
>> buttons andin that way control the request of new accounts and afterward
>> using some ticketing system control or manage the manual creation of those
>> OpenStack accounts.
>>
> Not fully clear to me; do you mean that it will be up to the FIWARE Lab
> administrators to open an account on behalf of the final user?
>
> In a first step, it could be manage through a specific project in JIRA and
>> in that way we do not lose any creation request. Honestly, I do not like so
>> much this approach but I cannot find any other alternative at the moment. I
>> would like that this process should be more automatic in order to not
>> overload FIWARE Lab administrators.
>>
> I see. I also admit that the fiware.org website workflow to open an
> account and proceed (final user side) is not super clear, right now (my
> modest opinion).
>
> Thanks & regards
> giorgio
>
> --
> ing. Giorgio Robino
>
> CNIT c/o - DITEN, Università di Genova
> Via Opera Pia 11
> 16145 Genova
>
> Tel.: +39 010 3532797
>
>


-- 

Fernando López


FIWARE Cloud and Platform Senior Expert

FIWARE Foundation

Franklinstrasse 13

10587 Berlin - Germany

[image: FIWARE Foundation Logo edited.png]

mail: fernando.lopez at fiware.org
www.fiware.org
twitter: @FIWARE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20170711/8b5e115d/attachment.html>


More information about the Fiware-lab-federation-nodes mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy