[Fiware-lab-recovery-tf] New URGENT plan for the recovery of the FIWARE Lab

[Federico Michele Facca]

On Mon, Apr 20, 2015 at 1:22 AM, FERNANDO LOPEZ AGUILAR <
fernando.lopezaguilar at telefonica.com> wrote:

>  Inline
>
>   De: JUAN JOSE HIERRO SUREDA <juanjose.hierro at telefonica.com>
> Fecha: Sunday 19 April 2015 19:14
> Para: fla <fernando.lopezaguilar at telefonica.com>, Álvaro Alonso <
> aalonsog at dit.upm.es>, Federico Michele Facca <
> federico.facca at create-net.org>
> CC: "fiware-lab-recovery-tf at lists.fiware.org" <
> fiware-lab-recovery-tf at lists.fiware.org>
> Asunto: Re: [Fiware-lab-recovery-tf] New URGENT plan for the recovery of
> the FIWARE Lab
>
>  Folks,
>
>   I'm a bit confused about what this means.
>
>  This means that the UPM thought that the keystone does not work with v2
> and v3, thing that it is wrong and we had test last week in order to secure
> it. The only thing is that it is necessary to define the domain value of v2
> field to default and there will be no problem using them in v3. Current
> version of keystone introduce, as you know, the domain field besides
> project and user but v2 of the API do not have this value. So the previous
> data of the Keystone-Proxy just have to make sure that in the migration
> procedure assign the value “default” to domain in order that they can work
> properly.
>
>   What release of OpenStack is then the release below which we will ask
> nodes to update and community users to migrate?
>
>  Icehouse or Juno, preferably Juno but some node just
>
>   Just as a reminder, besides compatiblity with the new IdM/Keystone, we
> wanted to have Neutron supported, don't we?  On the other hand, I see that
> "EOL - End of Life" is marked for the Havana release and older releases
> here:
>
> https://wiki.openstack.org/wiki/Releases
>
> We know it, only the last two releases are available. I have been always
> the same since beginning of the project. This means that on 30th Abril the
> Security-supported will be Juno and Kilo will be the current stable version
> beside starting the development of Liberty.
>
>     Therefore, I would say that we should force all nodes to be either on
> IceHouse or Juno ... shouldn't we?
>
>  Agree, it is what we are saying to the nodes in Grizzly.
>


+1 on fernando comments, the only additional meaning i see is that upgrade
plan does not need to be rushed out, but we can proceed more smoothly
minimizing nodes down at the same time for end-users.

cheers,
federico

-- 
--
Future Internet is closer than you think!
http://www.fiware.org

Official Mirantis partner for OpenStack Training
https://www.create-net.org/community/openstack-training

-- 
Dr. Federico M. Facca

CREATE-NET
Via alla Cascata 56/D
38123 Povo Trento (Italy)

P  +39 0461 312471
M +39 334 6049758
E  federico.facca at create-net.org
T @chicco785
W  www.create-net.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-recovery-tf/attachments/20150420/300d395b/attachment.html>