#calico

/

      • aledbf joined the channel
      • tomdee joined the channel
      • aledbf joined the channel
      • zerkalo joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang_ joined the channel
      • tim-tang has quit
      • cloudguru has quit
      • tim-tang joined the channel
      • cloudguru joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang_ joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang_ has quit
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang_ joined the channel
      • tim-tang has quit
      • cloudguru has quit
      • cloudguru joined the channel
      • cloudguru has quit
      • ryanz has quit
      • ryanz joined the channel
      • logan- joined the channel
      • tim-tang_ has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • Sail0r joined the channel
      • slackbot1 joined the channel
      • tim-tang joined the channel
      • slackbot1
        <shaun.crampton> qwebirc41491: Sorry, our Mesos experts are on Pacific time so it might take a while to get an answer
      • fasaxc joined the channel
      • sszuecs joined the channel
      • Sail0r joined the channel
      • neiljerram joined the channel
      • neiljerram has quit
      • neiljerram joined the channel
      • tim-tang joined the channel
      • neiljerram has quit
      • neiljerram joined the channel
      • bostondriver joined the channel
      • fasaxc
        Just testing slack bridge...
      • slackbot1
        <shaun.crampton> …working OK
      • <matt_dupre> FYI we now restart the bridge on a regular basis (daily IIRC); so if there were problems they might not show up later
      • fasaxc
        I just noticed that freenode was down earlier, thought I'd check the bridge had reconnected
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang has quit
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • tim-tang joined the channel
      • cloudguru joined the channel
      • Sail0r joined the channel
      • cloudguru has quit
      • cloudguru joined the channel
      • cloudguru has quit
      • tim-tang joined the channel
      • Sail0r joined the channel
      • cloudguru joined the channel
      • Sail0r joined the channel
      • tim-tang joined the channel
      • tim-tang has quit
      • cloudguru has quit
      • tim-tang joined the channel
      • cloudguru joined the channel
      • tim-tang joined the channel
      • ninja007 joined the channel
      • ninja007
        Hi
      • Is calico tested with marathon-mesos-docker container
      • if yes, is there a test workload/json to pass to marathon to start a container with docker and calico
      • neiljerram
        ninja007, Hi!
      • ninja007
        Hi
      • neiljerram
        I hope someone from our US team will pitch in with more authority in a moment.
      • However, I believe the answer is that our Mesos support for Docker containers is coming in 0,27
      • Has 0.27 come out yet?
      • ninja007
        Yes mesos does support calico
      • i have a supported version running on my instance
      • neiljerram
        I'm aware of that, as I demonstrated it at the last MesosCon :-)
      • ninja007
        I need a example of network configuration setup while creating a task in marathon for mesos-docker
      • neiljerram
        But that was Mesos/Marathon/tasks. If I understand correctly, support for Docker containers in Mesos/Marathon is the new ingredient.
      • ninja007
        great to hear that <neiljerram> :)
      • neiljerram
        But let me see if I can get someone more authoritative from our Mesos team, to speak to you....
      • ninja007
        Sure
      • Sail0r joined the channel
      • tim-tang joined the channel
      • neiljerram
        I'm afraid no one's available for live chat at the mo, but I've been told the following:
      • "The short answer is that we don’t work with docker daemon in Mesos. we work with the Mesos containerizer only at this point (which is becoming the “unified containerizer” as it gains the ability to also natively run Docker images)"
      • Does that help?
      • ninja007
        Yes sir it helps, so does that mean you dont have any plans to support mesos-docker in the near future?
      • Also does it support mesos-dns? I mean does the containers A record gets updated when the container gets a IP through calico? or will it still have a SRV record?
      • neiljerram
        I'm afraid I don't know.
      • ninja007
        ok
      • If i have a calico cluster running in on one VPC(say VPC1) in AWS and if i create a new VPC(say VPC2) and setup vpc peering between them, is there a way for a machine in VPC2 to communicate with calico containers in VPC1 without running bird on the machine in VPC2?
      • neiljerram
        Well, it depends what your IPAM scheme is, and how data is routed between the VPCs.
      • Imagine data travelling from container A in VPC2 to container B in VPC1.
      • So on container A's host, that data needs to be routed towards the IP address of container B.
      • If you're not using BIRD to propagate routes everywhere, will you have some other way for container A's host to know how to get to the IP address of container B?
      • ninja007
        ok to make it more clear , VPC1 has a subnet of 172.31.0.0/16(this is subnet of AWS VMs and subnet is handled by AWS) but the CIDR managed by calico is 192.168.0.0/16 (this is subnet of containers and Ips are managed by calico) and VPC2 has subnet of 10.0.0.1/16, so if i add the route of 192 subnet via the peering interface to 10.0 subnet, does that help?
      • neiljerram
        Yes, I think so. If you'd expect that to work in normal routing, it should work with Calico too.
      • ninja007
        It does work for normal routing, as in once i add the route of 172 subnet via peering interface to 10.0 VPC, it works , however it is unable to route 192 subnet
      • which is managed by calico
      • neiljerram
        So surely you just need to add a 192.168/16 route in the same place you added the 172.31/16 route?
      • tim-tang joined the channel
      • ninja007
        just to be clear, i added 172 subnet and was able to reach 172 from 10.0 VPC , then i added 192 subnet but i was unable to reach it from 10.0 VPC
      • tim-tang has quit
      • ninja007 has quit
      • Sail0r has quit
      • makuk661 has quit
      • makuk66 joined the channel
      • tim-tang joined the channel
      • cloudguru has quit
      • cloudgur_ joined the channel
      • neiljerram has quit
      • tim-tang joined the channel
      • tim-tang joined the channel