On Wed, Apr 27, 2016 at 12:09 PM, Imesh Gunaratne wrote:
> Hi Srinath,
>
> On Wed, Apr 27, 2016 at 11:52 AM, Srinath Perera wrote:
>
>> Hi Imesh,
>>
>> Publishing to both gateways is not good because things fall apart when a
>> one publication failed. Then a one node will be out of sync and will
Just to add another option we evaluated:
*Rolling Updates on Kubernetes*
- Again this is only available on Kubernetes at the moment and not
supported on Mesos.
- The idea in this is to build a new gateway Docker image on each API
change and execute a rollout via Kubernetes.
- This process requires
Hi Srinath,
On Wed, Apr 27, 2016 at 11:52 AM, Srinath Perera wrote:
> Hi Imesh,
>
> Publishing to both gateways is not good because things fall apart when a
> one publication failed. Then a one node will be out of sync and will
> continue to be out of sync.
>
Indeed, that's true!
>
> Also in C
Hi Imesh,
Publishing to both gateways is not good because things fall apart when a
one publication failed. Then a one node will be out of sync and will
continue to be out of sync.
Also in C5, we are dropping depsync, and ask users to use rsync ( or some
other method like NSF).
Can't we use rsyn
Hi Nuwan,
On Wed, Apr 27, 2016 at 9:18 AM, Nuwan Dias wrote:
>
> On Wed, Apr 27, 2016 at 8:59 AM, Imesh Gunaratne wrote:
>
>>
>> On Tue, Apr 26, 2016 at 5:37 PM, Nuwan Dias wrote:
>>
>>>
>>> If there are more than 1 manager nodes, we can configure the publisher
>>> to publish APIs to all of th
On Wed, Apr 27, 2016 at 8:59 AM, Imesh Gunaratne wrote:
>
>
> On Tue, Apr 26, 2016 at 5:37 PM, Nuwan Dias wrote:
>
>> Hi Imesh,
>>
>> Your intention I believe is to make API Manager artifact synchronisation
>> possible in containerized environments without modifying the existing
>> product and w
On Tue, Apr 26, 2016 at 5:37 PM, Nuwan Dias wrote:
> Hi Imesh,
>
> Your intention I believe is to make API Manager artifact synchronisation
> possible in containerized environments without modifying the existing
> product and without using deployment synchronizer. Correct?
>
Yes that's correct,
Hi Imesh,
Your intention I believe is to make API Manager artifact synchronisation
possible in containerized environments without modifying the existing
product and without using deployment synchronizer. Correct?
Looking at the suggested approach from a high level, this is quite similar
to using
Hi All,
This is to propose a new model for synchronizing Synapse APIs generated by
API Publisher in API Gateway worker nodes in containerized environments.
Here we are trying to avoid using SVN based deployment synchronizer. This
proposal may apply to Kubernetes, Apache Mesos or any other contain
