g List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, September 21, 2015 at 1:18 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum]
r 17, 2015 at 12:06
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org
> >>
> > Subject: Re: [openstack-dev] [magnum] Discovery
> >
> >
>
gt; Date: Thursday, September 17, 2015 at 12:06
> To: "OpenStack Development Mailing List (not for usage questions)"
> mailto:openstack-dev@lists.openstack.org>>
> Subject: Re: [openstack-dev] [magnum] Discovery
>
>
> Hey Daneyon,
>
>
> I'm fairly pa
st (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum] Discovery
Hey Daneyon,
I'm fairly partial towards #2 as well. Though, I'm wondering if it's possible
to take it a step further. Could we run etcd in each Bay w
t for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, September 17, 2015 at 12:06
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum] Discove
From: Daneyon Hansen (danehans)
Sent: Wednesday, September 16, 2015 11:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum] Discovery
All,
While implementing the flannel --network-driver for swarm, I have come across
an issue that requires feedbac
All,
While implementing the flannel --network-driver for swarm, I have come across
an issue that requires feedback from the community. Here is the breakdown of
the issue:
1. Flannel [1] requires etcd to store network configuration. Meeting this
requirement is simple for the kubernetes bay t
Andrew,
For clustered services that require generation of a discovery token, and access
to a discovery service, we need to keep in mind a few things:
1) Cloud operators have their own preferences for what defaults should be use.
Some may want to run their own discovery services, and others will
Hi Devs,
I'd like to get some discussion going for possible improvements to the
discovery mechanism used in Magnum's Swarm bay.
The method of the existing review[1] is to use the public swarm discovery
endpoint, and let the user pass a token in on the bay-create call. This is
definitely not
