[Fiware-fiadopt-coaching] Noviqr.FiwareLabToCommercial

[Chaim Mazor]

Hi Ilknur,

Sorry for such a late reply on this, we are working hard towards our pilot.

We are ready to make the move to a commercial enviroment and I just
reviewed this email and also all the information I could find online.

>From what I understand, regarding our choices for other enviroments besides
Fi-Ware Labs, commercial nodes are being set up by different companies and
there are some available in very specific locations, but nothing ready that
would work for us.

What is done by other apps/teams going commercial with Fi-Ware?
Do they opt to host on Amazon with FiWare VMs or create their own
infrastructure?

And if I was mistaken and there are commercial nodes that are available for
us to work with, could you please direct me to the person or where we can
understand the details, such as pricing, etc' to evaluate moving over to a
commercial node (if it's applicable to us)

Thanks for all your help!
Chaim.

On Tue, Dec 1, 2015 at 4:39 PM, Chulani, Ilknur <ilknur.chulani at atos.net>
wrote:

> Hi Chaim,
>
>
>
> There are a few aspects to consider when migrating from the FIWARE Lab to
> another environment:
>
>
>
> 1. First, you need to decide where you want to host your app. Your options
> are:
>
> o   Your own infrastructure
>
> o   A commercial FIWARE node (TID and Engineering has some experimental
> commercial nodes, Orange and ATOS is also currently setting up)
>
> o   A third party non-cloud cloud provider (such as Amazon, etc.)
>
> 2. Then you would need to backup and migrate your instances, data ,etc.
> Your steps would be:
>
> o   Backup any data, VMs, etc.
>
> o   Create snapshots of your VMs using the FIWARE Lab Cloud portal or the
> OpenStack command line tools available on the nodes to FIWARE Lab users.
>
> o   Download these images and upload in new environments, and restart the
> VMs.
>
> o   This may not work in all cases though, so you may need to recreate
> your VMs in some cases in the new environment.
>
> 3. Special considerations regarding the GEs you may be using:
>
> o   If you are using global instances from the FIWARE Lab, you may need
> to create your own instances in the new environment manually, or using
> Docker containers. (or you may have the option of using the global
> instances again if you are migrating to a commercial FIWARE node)
>
> o   If you are using your own instances, you can try the same steps
> mentioned in step 2, or recreate the instances manually or using Docker.
>
>
>
> These are all the steps that comes to my mind at the moment.  Let me know
> if you need further information regarding any of these.
>
>
>
> Kind regards,
>
>
>
> ilknur
>
>
>
> *From:* Chaim Mazor [mailto:chaim at noviqr.com]
> *Sent:* Tuesday, December 01, 2015 11:53 AM
> *To:* Chulani, Ilknur
> *Subject:* Re: Security Monitoring GE for noviQr
>
>
>
> Hi Ilknur,
>
>
>
> I have a question,:
>
>
>
> We are now approaching our pilot and currently the platform is running on
> Fi-Ware Labs, we want to understand again what exactly is needed in order
> to move away from Fi-Ware Labs into a commercial enviroment.
>
>
>
> Can you shed some light on this subject?
>
>
>
> Thanks!
>
> Chaim.
> Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir.
> Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız,
> başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet
> üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi
> olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin
> bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de
> mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek
> zararlardan sorumlu tutulamaz.
>
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this
> e-mail in error, please notify the sender immediately and destroy it. As
> its integrity cannot be secured on the Internet, the Atos group liability
> cannot be triggered for the message content. Although the sender endeavors
> to maintain a computer virus-free network, the sender does not warrant that
> this transmission is virus-free and will not be liable for any damages
> resulting from any virus transmitted.
>

ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-fiadopt-coaching/attachments/20160217/30fdb691/attachment.html>