Hi all,
Members of the Designate project are in room 203 at the Neutron pod. Look
forward to meeting you all.
On 5/9/14, 9:17 AM, "Hayes, Graham" wrote:
>Hi,
>
>It looks like us 'none ATC' folk will have access to the project pods -
>so should we nail down a time on Monday?
>
>It looks like the
Graham,
Agreed. I'll update the etherpad to reflect the decision. See you
all at or near the Neutron pod at 4:30pm.
Carl
On Fri, May 9, 2014 at 8:17 AM, Hayes, Graham wrote:
> Hi,
>
> It looks like us 'none ATC' folk will have access to the project pods - so
> should we nail down a time on M
Hi,
It looks like us 'none ATC' folk will have access to the project pods - so
should we nail down a time on Monday?
It looks like the 16:30 onwards is the most popular choice - will we say 16:30
on Monday in the Neutron pod?
Thanks,
Graham
On Tue, 2014-05-06 at 17:45 +, Veiga, Anthony w
Hi,
The only issue I would see with the pod is that not all of us are ATCs, so we
may or may not have access to that area (I am open to correction on that point
- in fact I hope someone does ;) )
I’ll second this. I have an interest in attending and assisting here, but I
don’t have ATC stat
Hi,
The only issue I would see with the pod is that not all of us are ATCs,
so we may or may not have access to that area (I am open to correction
on that point - in fact I hope someone does ;) )
I could see it fitting in with our design session, but maybe if we meet
on the Monday to do some init
I have just updated my etherpad [1] with some proposed times. Not
knowing much about the venue, I could only propose the "pod area" as a
the location.
I also updated the designate session etherpad [2] per your suggestion.
If there is time during the Designate sessions to include this in the
disc
On 4/29/14, 3:09 PM, "Carl Baldwin" wrote:
>I feel this is an important subject to discuss because the end result
>will be a better cloud user experience overall. The design summit
>could be a great time to bring together interested parties from
>Neutron, Nova, and Designate to discuss the inte
On Wed, Apr 30, 2014 at 06:10:20PM EDT, Martinx - ジェームズ wrote:
> Since IPv6 is all public, don't you think that we (might) need a new
> blueprint for IPv6-Only, like just "dns-resolution"?
Yes - I think IPv6 only Neutron is at least one separate blueprint,
possibly more. Robert Li is currently wor
Thiago,
Throwing IPv6 in the mix does blur the distinction between internal
and external. In the blueprints, internal and external have more to
do with whether we're dealing with the name/IP mapping internally to
Neutron or externally to Neutron by integrating with an external DNS
service. In ot
Carl,
Let me ask you something...
If my cloud is IPv6-Only based (that's my intention), which blueprint will
fit on it (internal-dns-resolution or external-dns-resolution) ?
Since IPv6 is all public, don't you think that we (might) need a new
blueprint for IPv6-Only, like just "dns-resolution"?
Yup - me too.
Graham
On Wed, 2014-04-30 at 15:30 +, Mac Innes, Kiall wrote:
Yep - I know I'll join in :)
Thanks,
Kiall
On Tue, 2014-04-29 at 14:09 -0600, Carl Baldwin wrote:
> The design summit discussion topic I submitted [1] for my DNS
> blueprints [2][3][4] and this one [5] just missed
Yep - I know I'll join in :)
Thanks,
Kiall
On Tue, 2014-04-29 at 14:09 -0600, Carl Baldwin wrote:
> The design summit discussion topic I submitted [1] for my DNS
> blueprints [2][3][4] and this one [5] just missed the cut for the
> design session schedule. It stung a little to be turned down but
I'll be an alpha / beta tester, for sure!! :-D
I'm very interested on DNS for IPv6 in Neutron (and in Horizon too)... Hope
to see it in Juno!!
IPv6 (with a perfect DNS setup) is very important...
Best!
Thiago
On 29 April 2014 17:09, Carl Baldwin wrote:
> The design summit discussion topic I
On 04/29/2014 06:59 PM, Collins, Sean wrote:
Count me in!
+1
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Count me in!
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
The design summit discussion topic I submitted [1] for my DNS
blueprints [2][3][4] and this one [5] just missed the cut for the
design session schedule. It stung a little to be turned down but I
totally understand the time and resource constraints that drove the
decision.
I feel this is an import
16 matches
Mail list logo
