Si os parece bien, lo que propone Luis.
Entonces comienzo a gestionar con Altassian cómo comprar el downloaded, para instalarlo, etc y hacer el traspaso de los trackers.
-----Original Message-----
From: Luis Cañas-Díaz [mailto:lcanas at bitergia.com]
Sent: miércoles, 28 de agosto de 2013 15:10
To: MANUEL ESCRICHE VICENTE
Cc: acs at bitergia.com; MIGUEL CARRILLO PACHECO
Subject: Re: Query on On-demand JIRA instance in evaluation period - {818372}
On 27/08/13 17:08, MANUEL ESCRICHE VICENTE wrote:
> Hola Álvaro,
Muy buenas Manuel,
espero que haya ido bien la vuelta de vacaciones.
>
> Me parece recordar que Luis volvía un día de estos.
>
> Necesito retomar el tema.
>
> Al ser 'downloaded', implica una serie de tareas que será necesario realizar para instalarlo, y mantenerlo.
> ¿Podría encargarse Bitergia de estas tareas? ¿Hasta qué punto el marco de colaboración actual las cubriría?
>
> Creo que es bueno comentarlo, para evitar malentendidos posteriores.
El contrato actual no cubre de ninguna manera la administración de ese servicio. Dicho esto, me parece asumible por nuestra parte la instalación del servicio y su monitorización. Es decir, nos ocuparíamos de:
* instalar JIRA
* proporcionar a la persona responsable los datos de la cuenta de admin
* monitorizarlo, como el resto de los servicios
* sobre la copia de seguidad habría que hablar más adelante, cuando la máquina de backups esté viva. Creo recordar que teníamos ya problemas de espacio :(
Saludos,
Luis.
>
> Un saludo y gracias.
> Manuel
>
> -----Original Message-----
> From: Alvaro del Castillo [mailto:acs at bitergia.com]
> Sent: jueves, 22 de agosto de 2013 8:37
> To: MANUEL ESCRICHE VICENTE
> Cc: MIGUEL CARRILLO PACHECO; Luis Cañas-Díaz
> Subject: Re: Query on On-demand JIRA instance in evaluation period -
> {818372}
>
> Hola!
>
> El jue, 22-08-2013 a las 05:47 +0000, MANUEL ESCRICHE VICENTE escribió:
>> Hola Alvaro,
>>
>> Entre tanto reply de correos, me resulta difícil de leer.
>> ¿Podríamos sacar un 'bottom line'?
>> ¿Cuál es la opción que debemos comprar: Ondemand, downloaded, o es indiferente porque no podemos resolverlo?
>
> Con Ondemand no tenemos opciones de integración posibles con FusionForge.
>
> Con downloaded al menos tenemos alguna oportunidad de tener SSO.
>
> Así que downloaded.
>
> Hasta luego!
>
>>
>> Un saludo y gracias.
>> Manuel
>> -----Original Message-----
>> From: Alvaro del Castillo [mailto:acs at bitergia.com]
>> Sent: miércoles, 21 de agosto de 2013 19:28
>> To: MIGUEL CARRILLO PACHECO
>> Cc: Luis Cañas-Díaz; MANUEL ESCRICHE VICENTE
>> Subject: Re: Query on On-demand JIRA instance in evaluation period -
>> {818372}
>>
>> El mié, 21-08-2013 a las 15:42 +0200, Miguel Carrillo escribió:
>>> Hola again,
>>>
>>> El 21/08/2013 10:43, Alvaro del Castillo escribió:
>>>> Hola Miguel,
>>>>
>>>> El mié, 21-08-2013 a las 10:07 +0200, Miguel Carrillo escribió:
>>>>> Álvaro, Luis,
>>>>>
>>>>> Información interesante para la integración. Manuel les pasó una
>>>>> consulta a los de Atlassian y nos responden esto con punteros.
>>>>> Tal y como lo ponen, parece fácil (luego será lo que sea).
>>>>>
>>>>> Saludos
>>>>>
>>>>> Miguel
>>>>> El 21/08/2013 0:53, Jason Caragan (Atlassian) escribió:
>>>>>
>>>>>> ## Reply ABOVE THIS LINE to add a note to this request ##
>>>>>>
>>>>>> Hi Manuel,
>>>>>>
>>>>>> Thanks for the email and allow me to step in for Anna here.
>>>>>>
>>>>>> 1. Single sign-on. We need to setup a solution that allow our
>>>>>> users to have a single sign-on against both our collaborative
>>>>>> working environment, where users get authenticated, and the
>>>>>> on-demand JIRA instance. However, it seems we havent been able to
>>>>>> find the right solution. We wonder whether its only possible to
>>>>>> accomplish it using a hosted (downloaded) JIRA instance. We would
>>>>>> appreciate to have your feedback on this issue since this feature
>>>>>> is very important for our collaborative working environment
>>>>>>
>>>>>> Though Atlassian OnDemand does provide single sign on between the
>>>>>> applications you've activated within your OnDemand suite (for
>>>>>> example if you were using JIRA alongside our content
>>>>>> collaboration tool Confluence), single sign on with third party
>>>>>> or locally hosted applications and local directories (LDAP) is
>>>>>> not supported at this time.
>>>> Este es justo Miguel lo que habíamos comprobado. CAS es el único
>>>> método de SSO soportado por Fusion Forge, y es "third party not supported".
>>>>
>>>>>> With a Download instance of JIRA, it is possible to use
>>>>>> Atlassian Crowd, our single sign on and unified identity management tool.
>>>>>> Crowd would allow you to control user access and single sign on
>>>>>> to its connected applications. It includes connectors to JIRA and
>>>>>> Atlassian applications out of box, and it is possible to build a
>>>>>> custom connector for other non-Atlassian apps with
>>>>>> Crowd: see Integrating Crowd with a Custom Application. To set
>>>>>> expectations, it sounds like it can usually take someone who
>>>>>> knows what they are doing a day or two to Create a Crowd Client
>>>>>> for your Custom Application. Alternatively, customers have had
>>>>>> varying degrees of success integrating JIRA with other SSO
>>>>>> platforms: see this community article for further info.
>>>> Nosotros tenemos que utilizar CAS, no Crowd, ya que es lo que
>>>> soporta Fusion Forge. El desarrollo de un conector entre Crowd y
>>>> Fusion Forge es un camino que no veo muy viable.
>>>>
>>>> Así que el camino es integrar CAS con JIRA, y como dicen "customers
>>>> have had varying degrees of success".
>>>>
>>>> Hay incertidumbre con Fusion Forge y CAS. Y la hay con JIRA y CAS.
>>>> Por eso se descarto esta opción en primera instancia y fuimos a la
>>>> opción de LDAP, con la que teníamos algo más de garantías. Tiene el
>>>> problema de que el usuario tiene que meter su login en FF y luego
>>>> en JIRA, pero es la opción más viable.
>>> O single sign on "de verdad" (sin tecleo de usario/password dos
>>> veces) o, Juanjo ha sido muy claro, yo creo que no nos vale.
>>
>> Sí, esto ha quedado claro, pero quería que entendieras la complejidad e incertidumbres para fijar expectativas.
>>
>> Hasta luego!!!
>>
>>>>
>>>>>> 2. It would be critical for us to confirm whether it is possible
>>>>>> to export the current content from the on-demand JIRA to a
>>>>>> downloaded one, and additionally knowing whether the reverse
>>>>>> migration (from a downloaded JIRA to the on-demand JIRA) is also possible.
>>>>>>
>>>>>> Both possible.
>>>>>>
>>>>>> OnDemand to Download
>>>>>>
>>>>>> OnDemand subscribers can migrate their data from an OnDemand
>>>>>> instance to an installed instance.
>>>>>>
>>>>>> You'll need to export your data from OnDemand, before importing
>>>>>> it into your installed instance running a compatible version of
>>>>>> the software.
>>>>>>
>>>>>> When you wish to initiate a migration to a Download edition,
>>>>>> simply utilize our customer-facing Backup Manager to retrieve a
>>>>>> full JIRA backup. Once you have the backup, it is simply a matter
>>>>>> of restoring the data into a local version of JIRA.
>>>>>>
>>>>>> Download to OnDemand
>>>>>>
>>>>>> You can easily migrate from behind-the-firewall to OnDemand. You
>>>>>> will first need to upgrade your application versions to match the
>>>>>> current OnDemand application version, then take backups of your
>>>>>> JIRA and/or Confluence instance and use our Import Wizards to
>>>>>> restore your data in a new OnDemand instance.
>>>>>>
>>>>>> If you come across any technical difficulties during either type
>>>>>> of migration, please feel free to file a support ticket. If you
>>>>>> have never used our support portal before, you will need to sign
>>>>>> up first.
>>>>>>
>>>>>> I hope this clarifies, Manuel. Please let us know if we can
>>>>>> further assist.
>>>> Parece entonces que será sencillo sacar los datos del JIRA actual
>>>> en modo servicio y pasarlo al JIRA instalado en local. Habrá que
>>>> realizar también la migración de estos datos a Fusion Forge, lo que
>>>> puede que no sea tan sencillo.
>>> Entiendo que si hacemos de policías y aseguramos que los "user names"
>>> sean los mismo iría (si utiliza mi usuario "mcp" como pivote para
>>> vincular ambos lados, pues miel sobre hojuelas) Pero a lo mejor es
>>> más complejo, y me huelo que sí que lo es :(
>>>> O nos poner
>>>> Hasta luego
>>>>
>>>>>>
>>>>>> Cheers,
>>>>>> Jason Caragan
>>>>>> Product Advocate Team Lead
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Our biggest user conference yet: Atlassian Summit 2013! October
>>>>>> 1-3 in San Francisco, CA
>>>>>>
>>>>>> sales at atlassian.com
>>>>>> +1 415 701 1110 (San Francisco, USA)
>>>>>> +61 2 9262 1443 (Sydney, Australia)
>>>>>> +31 20 796 0060 (Amsterdam, Netherlands)
>>>>>>
>>>>>> ----
>>>>>> MANUEL ESCRICHE VICENTE - mev at tid.es - 19 Aug 2013, 06:36 AM PDT
>>>>>> Dear Atlassian team,
>>>>>>
>>>>>>
>>>>>>
>>>>>> I am writing to you to clarify some questions that came up during
>>>>>> the evaluation period for the JIRA instance
>>>>>> https://fi-ware.atlassian.net , whose evaluation period is coming
>>>>>> to anend in the coming days.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Despite the work done during the evaluation period, we have still
>>>>>> some uncertainties on how to solve a couple of issues.
>>>>>> Your help or advice would be appreciated:
>>>>>>
>>>>>> 1. Single sign-on. We need to setup a solution that allow our
>>>>>> users to have a single sign-on against both our
>>>>>> collaborative working environment, where users get
>>>>>> authenticated, and the on-demand JIRA instance. However,
>>>>>> it seems we haven’t been able to find the right solution. We
>>>>>> wonder whether it’s only possible to accomplish it using a
>>>>>> hosted (downloaded) JIRA instance. We would appreciate to
>>>>>> have your feedback on this issue since this feature is very
>>>>>> important for our collaborative working environment
>>>>>> 2. Migration from on demand to downloaded instance. Since we
>>>>>> haven’t been able to fix the single sign-on properly with
>>>>>> the on-demand instance, we’re thinking of buying a
>>>>>> downloaded JIRA instead of the on-demand one. We would
>>>>>> appreciate the possibility of doing it if the on demand
>>>>>> setting does not turn out to be feasible. It would be
>>>>>> critical for us to confirm whether it is possible to export
>>>>>> the current content from the on-demand JIRA to a downloaded
>>>>>> one, and additionally knowing whether the reverse migration
>>>>>> (from a downloaded JIRA to the on-demand JIRA) is also
>>>>>> possible.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Since it doesn’t seem obvious how to solve these issues in very
>>>>>> short time, I need to request an extension for the evaluation
>>>>>> period. It would certainly help us fixing the issues above
>>>>>> properly, and would very much be appreciated.
>>>>>>
>>>>>>
>>>>>>
>>>>>> We would appreciate a quick reaction.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks in advance.
>>>>>>
>>>>>> Kind regards,
>>>>>>
>>>>>> Manuel
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ----------------------------
>>>>>>
>>>>>> Manuel Escriche Vicente
>>>>>> Agile Project Manager/Leader
>>>>>>
>>>>>> FI-WARE Initiative
>>>>>> Telefónica Digital
>>>>>>
>>>>>> Parque Tecnológico
>>>>>>
>>>>>> C/ Abraham Zacuto, 10
>>>>>> 47151 - Boecillo
>>>>>> Valladolid - Spain
>>>>>> Tfno: +34.91.312.99.72
>>>>>> Fax: +34.983.36.75.64
>>>>>> http://www.tid.es
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ________________________________________________________________
>>>>>> __
>>>>>> __
>>>>>>
>>>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>>>>>> consultar nuestra política de envío y recepción de correo
>>>>>> electrónico en el enlace situado más abajo.
>>>>>> This message is intended exclusively for its addressee. We only
>>>>>> send and receive email on the basis of the terms set out at:
>>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> ----------------------------------------------------------------------
>>>>> _/ _/_/ Miguel Carrillo Pacheco
>>>>> _/ _/ _/ _/ Telefónica Distrito Telefónica
>>>>> _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9
>>>>> _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
>>>>> _/ _/_/ 28050 Madrid (Spain)
>>>>> Tel: (+34) 91 483 26
>>>>> 77
>>>>>
>>>>> e-mail: mcp at tid.es
>>>>>
>>>>> Follow FI-WARE on the net
>>>>>
>>>>> Website: http://www.fi-ware.eu
>>>>> Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
>>>>> Twitter: http://twitter.com/Fiware
>>>>> LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
>>>>> -----------------------------------------------------------------
>>>>> --
>>>>> ---
>>>>>
>>>>>
>>>>> _________________________________________________________________
>>>>> __
>>>>> ___
>>>>>
>>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>>>>> consultar nuestra política de envío y recepción de correo
>>>>> electrónico en el enlace situado más abajo.
>>>>> This message is intended exclusively for its addressee. We only
>>>>> send and receive email on the basis of the terms set out at:
>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>>>
>>>
>>> --
>>> ----------------------------------------------------------------------
>>> _/ _/_/ Miguel Carrillo Pacheco
>>> _/ _/ _/ _/ Telefónica Distrito Telefónica
>>> _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9
>>> _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
>>> _/ _/_/ 28050 Madrid (Spain)
>>> Tel: (+34) 91 483 26 77
>>>
>>> e-mail: mcp at tid.es
>>>
>>> Follow FI-WARE on the net
>>>
>>> Website: http://www.fi-ware.eu
>>> Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
>>> Twitter: http://twitter.com/Fiware
>>> LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
>>> --------------------------------------------------------------------
>>> --
>>>
>>>
>>> ________________________________
>>>
>>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
>>> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>
>>
>> --
>> |\_____/| Alvaro del Castillo
>> [o] [o] acs at bitergia.com - CTO, Software Engineer | V | http://www.bitergia.com
>> | |
>> -ooo-ooo-
>>
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
>> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>
>
> --
> |\_____/| Alvaro del Castillo
> [o] [o] acs at bitergia.com - CTO, Software Engineer | V | http://www.bitergia.com
> | |
> -ooo-ooo-
>
>
> ________________________________
>
> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
--
|\_____/| Luis Cañas-Díaz
[o] [o] lcanas at bitergia.com - Software Engineer
| V | http://www.bitergia.com
| | "Bridging the gap between developers and stakeholders"
-ooo-ooo-
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy