[Fiware-lab-federation-nodes] New Cloud Portal instance

[Cristian CMECIU]

Dear Alvaro,

Can you tell us how can we find a specific project or user related to our node?
I tried to search as admin user in Cloud Portal > Identity > Projects, some projects  after their tenant but without success.
My guess is that the search is made only by page displayed users.

BR,
Cristian CMECIU
Fiware-Lab/ Lannion Region
Images et Réseaux Support Engineer

[FIWARE_lab]



De : fiware-lab-federation-nodes-bounces at lists.fiware.org [mailto:fiware-lab-federation-nodes-bounces at lists.fiware.org] De la part de Álvaro Alonso
Envoyé : vendredi 6 octobre 2017 11:43
À : fiware-lab-federation-nodes at lists.fiware.org
Objet : [Fiware-lab-federation-nodes] New Cloud Portal instance

Dear Infrastructure Owner,
as we anticipated few days ago, we have deployed a new release of the Cloud Portal in FIWARE Lab. This new release is totally based on Openstack Horizon, we have just modified the styles to be FIWARE Lab style guide compliant. This of course includes a new Keystone deployment but don’t worry, we have migrated every needed resources to this new instance.
As a result of this new deployment users of the Cloud Portal will have an specific account (and different of the one to access FIWARE Lab Account Portal). So from now, every action related with the administration of your node has to be performed in the Cloud Portal. The Account portal is not used for managing Cloud stuff anymore. This includes the following:
- If you want to modify roles, passwords, projects, etc. of Cloud users, you have to use the Cloud Portal interface.
- When you receive a Community Account request and you want to accept it, you have to manage the request in the Cloud Portal following the next steps:
              1. If the user is not created you have to create it.
2. If the user doesn’t have an associated project to create cloud resources, you have to create it and to assign the user as a member of the project.
3. Assign the role “Community” in the domain “default” to the user.
4. Include in the metadata of the user (“description” field) the date in which the user has been upgraded to Community (with the format "community_started_at": "YYYY-MM-DD").
5. Assign the desired quotas to the project in your node
6. Assign the corresponding endpoint_group to the user (we will share the endpoint groups of each region soon)
- For managing your services endpoints you have to use the CLI tools. You cannot use the “Endpoints Management” tool of the Account Portal anymore. We are going to disable it.
- The notifications tool included in the Account Portal cannot be used to notify Cloud users anymore.
To access the Cloud Portal in order to perform administrative tasks you can continue using the same admin account you already have. On the other hand, to make your node compatible with the new Keystone instance yo have to check the following:
1. Restart your services to connect to the new Keystone instance. Endpoints are the same but you have to restart them to get a new auth token.
2. Check that you have Cinder v2 configured in your node. Cinder v1 is not working anymore with this version of Horizon.

Of course, if you have any question you can contact us. We appreciate your patience and collaboration during the first days working with the new environment.
BR
--
Álvaro

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20171009/53350c83/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6250 bytes
Desc: image001.png
URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20171009/53350c83/attachment-0001.png>