> On 24 Feb 2015, at 4:35 pm, Vladislav Bogdanov wrote:
>
> 24.02.2015 01:58, Andrew Beekhof wrote:
>>
>>> On 21 Jan 2015, at 5:08 pm, Vladislav Bogdanov wrote:
>>>
>>> 21.01.2015 03:51, Andrew Beekhof wrote:
> On 20 Jan 2015, at 4:13 pm, Vladislav Bogdanov
> wrote:
>
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/02/15 09:39 PM, Andrew Beekhof wrote:
>
>> On 26 Feb 2015, at 8:51 am, Digimer wrote:
>>
> On 25/02/15 04:45 PM, David Vossel wrote:
- Original Message -
> Pacemaker as a scheduler in Mesos or Kubernates does sound
> On 26 Feb 2015, at 8:51 am, Digimer wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 25/02/15 04:45 PM, David Vossel wrote:
>>
>>
>> - Original Message -
>>> Pacemaker as a scheduler in Mesos or Kubernates does sound like a
>>> very interesting idea. Packaging coros
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/02/15 04:45 PM, David Vossel wrote:
>
>
> - Original Message -
>> Pacemaker as a scheduler in Mesos or Kubernates does sound like a
>> very interesting idea. Packaging corosync into super privileged
>> containers still doesn't make too
- Original Message -
> Pacemaker as a scheduler in Mesos or Kubernates does sound like a very
> interesting idea. Packaging corosync into super privileged containers still
> doesn't make too much sense to me. What's the reason in isolating something
> and then giving it all permissions on
> On 25 Feb 2015, at 1:37 pm, Serge Dubrouski wrote:
>
> Pacemaker as a scheduler in Mesos or Kubernates does sound like a very
> interesting idea.
Want to help make it work? :-)
> Packaging corosync into super privileged containers still doesn't make too
> much sense to me. What's the reaso
