haosdent is right about the flags "--network_cni_config_dir" and
"--network_cni_plugins_dir", thanks haosdent :-)
> Is there a separate cli for testing of checking the the network
isolation config and plugin files without starting up an entire
cluster?
I think currently the quickest way to try CNI network support in Mesos from
E2E is: start a Mesos master and a Mesos agent with CNI isolator/some CNI
network configs/some CNI plugins loaded, and run "mesos-executor" to launch
a container to join one CNI network.
Thanks,
Qian Zhang
On Wed, May 18, 2016 at 5:57 PM, haosdent <haosd...@gmail.com> wrote:
> >It's not yet clear to me what exactly I have to put in the directories
> pointed by --network_cni_config_dir and --network_cni_plugins_dir in
> order to create a network?
>
> According to my understanding from code, Mesos try to parse any files under
> --network_cni_config_dir except directories.
>
> --network_cni_plugins_dir is used for find execute files. Suppose you
> define your network in --network_cni_config_dir like
>
> ```
> {
> "type": "foo",
> ...
> "ipam": {
> "type: "bar",
> }
> ...
> }
> ```
>
> After Mesos finish parsing the network definition file under
> --network_cni_config_dir, it would try find the execute file "foo" and
> "bar" under
> --network_cni_plugins_dir. Because the type of network you defined above is
> "foo", and the type of "ipam" is "bar".
>
> Just my quick reply, you could wait for Qian Zhang or Avinash's detail
> reply later.
>
>
> On Wed, May 18, 2016 at 4:40 PM, Frank Scholten <fr...@frankscholten.nl>
> wrote:
>
> > Hi Avinash,
> >
> > Thanks for your response. I am following the steps at
> > https://github.com/asridharan/mesos/blob/MESOS-4771/docs/cni.md and
> > when I run the mesos-execute command on the cluster I started at
> > https://github.com/ContainerSolutions/mesos-calico-cni-sandbox I get a
> > message saying the network does not exist. This is ok because I have
> > not created the network yet.
> >
> > It's not yet clear to me what exactly I have to put in the directories
> > pointed by --network_cni_config_dir and --network_cni_plugins_dir in
> > order to create a network?
> >
> >
> > On Tue, May 17, 2016 at 5:16 PM, Avinash Sridharan
> > <avin...@mesosphere.io> wrote:
> > > Hi Frank,
> > > I am in the process of putting up the documentation for CNI support in
> > > Mesos. You can find the RB patch for the documentation here:
> > > https://reviews.apache.org/r/47463/
> > >
> > > You can find a rendering of the markdown on my github over here:
> > > https://github.com/asridharan/mesos/blob/MESOS-4771/docs/cni.md
> > >
> > >
> > > I have put up one example of using the `network/cni` isolator with a
> > > "bridge" plugin. Working on adding some more examples, but given that
> > > people have already started showing some interest thought would be a
> good
> > > dry run for the documentation if someone could test out the
> instructions.
> > >
> > > Would be great if you can try following the instructions and leave any
> > > feedback on the review board.
> > >
> > >
> > > Thanks,
> > > Avinash
> > >
> > > On Tue, May 17, 2016 at 6:51 AM, Frank Scholten <
> fr...@frankscholten.nl>
> > > wrote:
> > >
> > >> In the meantime I am looking at an alternative route trying to figure
> > >> out how an ipAddress value on a Marathon app get propagated into Mesos
> > >> CNI.
> > >>
> > >> Marathon reads the ipAddress value from the AppDefinition and then
> > >> publishes on the eventbus. I don't see what happens to it from that
> > >> point.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Tue, May 17, 2016 at 2:58 PM, Jay JN Guo <guojian...@cn.ibm.com>
> > wrote:
> > >> > - net::links() -> stout/net.hpp
> > >> > - Personally, I'm not very familiar with CLion build. Maybe somebody
> > else
> > >> > could answer that.
> > >> > - I think this is very much related to dev mailing list, so +dev
> > >> >
> > >> > /J
> > >> >
> > >> > Frank Scholten <fr...@frankscholten.nl> wrote on 05/17/2016
> 20:47:12:
> > >> >
> > >> >> From: Frank Scholten <fr...@frankscholten.nl>
> > >> >> To: u...@mesos.apache.org
> > >> >> Cc: Qian AZ Zhang/China/IBM@IBMCN, avin...@mesosphere.io
> > >> >> Date: 05/17/2016 20:48
> > >> >> Subject: Re: Mesos Calico CNI
> > >> >>
> > >> >> Thanks. I now like to run that unit test via the debugger from the
> > >> >> Mesos source try in CLion. Is there a doc on how to build Mesos in
> > >> >> CLion and debug a unit test?
> > >> >>
> > >> >> Also, where does net::links() come from? Can't find it in the
> > sources.
> > >> >>
> > >> >>
> > >> >> On Tue, May 17, 2016 at 11:00 AM, haosdent <haosd...@gmail.com>
> > wrote:
> > >> >> >>Is there some user documentation for this feature?
> > >> >> > Unfortunately, the document is not ready.
> > >> >> > https://issues.apache.org/jira/browse/MESOS-4771
> > >> >> >
> > >> >> >>but I am not sure what I have to do to create an IP for a task.
> > >> >> > Qian Zhang show an example of configuration in his test cases, I
> > think
> > >> > you
> > >> >> > may take a look first.
> > >> >> > https://reviews.apache.org/r/46097/diff/7#index_header
> > >> >> >
> > >> >> > On Tue, May 17, 2016 at 4:20 PM, Frank Scholten
> > >> > <fr...@frankscholten.nl>
> > >> >> > wrote:
> > >> >> >>
> > >> >> >> Hi all,
> > >> >> >>
> > >> >> >> I tried out CNI support with Calico but I am not sure what I
> have
> > to
> > >> >> >> do to create an IP for a task.
> > >> >> >>
> > >> >> >> See this sandbox repository on Github
> > >> >> >>
> > >> >> >> https://github.com/ContainerSolutions/mesos-calico-cni-sandbox
> > >> >> >>
> > >> >> >> In this repo I build the Mesos master branch and
> > >> >> >> https://github.com/projectcalico/calico-cni, create a local
> > cluster
> > >> >> >> and deploy an application. I don't see anything in the logs
> about
> > >> cni,
> > >> >> >> except that it loads the cni isolator.
> > >> >> >>
> > >> >> >> Is there some user documentation for this feature? If not I am
> > happy
> > >> >> >> to write documentation once I figure out how this feature works.
> > >> >> >>
> > >> >> >> Cheers,
> > >> >> >>
> > >> >> >> Frank
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > --
> > >> >> > Best Regards,
> > >> >> > Haosdent Huang
> > >> >>
> > >>
> > >
> > >
> > >
> > > --
> > > Avinash Sridharan, Mesosphere
> > > +1 (323) 702 5245
> >
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
