Dear Spyros, The fact is that I've added the next endpoints for cinderv2 and volumev2: cinternal => http://192.168.0.2:8776/v2/%(tenant_id)s admin => http://192.168.0.2:8776/v2/%(tenant_id)s public => http://147.27.60.2:8776/v2/%(tenant_id)s May it be ok now? Best regards, José Ignacio El 16/10/17 a las 10:58, Spyros Argyropoulos escribió: > > Hi Álvaro, all, > > Crete Node still faces problems after the installation of the new > Cloud Portal: > 1. Cinder v2 is not working for this version of Horizon. As a result > Horizon does not get information about users Volumes and probably this > also makes problems to the users quotas calculations. > 2. Additionally users cannot create new instances, networks and > routers using the dashboard. Probably this is also because of the > Cinder v2 problem. > > As we can see there are other nodes with KILO installation (e.g. > Spain2) which do not have the problems we face with the new Cloud > Portal dashboard. > We would like to share there experience in order to solve the above > problems. > > Thank you in advance, > > Spyros. > Spyros Argyropoulos, Computer & Informatics Eng. > Intelligent Systems Laboratory > School of Electrical and Computer Engineering > Technical University of Crete > University Campus - Kounoupidiana > 73100 Chania, Crete > GREECE > Phone: +3028210 37342 > Fax: +3028210 37542 > On 6/10/2017 12:42 μμ, Álvaro Alonso wrote: >> >> 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 >> >> >> >> __________________________________________________________________________________________ >> >> You can get more information about our cookies and privacy policies on the following links: >> -http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy >> -http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE >> >> Fiware-lab-federation-nodes mailing list >> Fiware-lab-federation-nodes at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-lab-federation-nodes >> > > > > __________________________________________________________________________________________ > > You can get more information about our cookies and privacy policies on the following links: > - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy > - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE > > Fiware-lab-federation-nodes mailing list > Fiware-lab-federation-nodes at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-lab-federation-nodes > -- −−− José Ignacio Carretero FIWARE Cloud and Platform Expert FIWARE Foundation FIWARE Foundation Franklinstrasse 13A 10587 Berlin email: joseignacio.carretero at fiware.org <mailto:joseignacio.carretero at fiware.org> www: http://fiware.org twitter: @jicarreterogu @FIWARE skype: jicarretero -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20171016/e9b4ca73/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Foundation-31B.png Type: image/png Size: 251283 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-lab-federation-nodes/attachments/20171016/e9b4ca73/attachment-0001.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy