I took a few minutes to update the ipv6 draft spec.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+in+VPC+Router
On Fri, Jan 17, 2014 at 2:20 PM, Marcus Sorensen wrote:
> On Fri, Jan 17, 2014 at 11:59 AM, Chiradeep Vittal
> wrote:
>> Yes, let's not shut out the ULA option.
>>
>> Fo
On Fri, Jan 17, 2014 at 11:59 AM, Chiradeep Vittal
wrote:
> Yes, let's not shut out the ULA option.
>
> For the LB "Public" interface, will this be just another tier? That is,
> not an explicit public VLAN.
Well, we do have the internal LB function, but I was thinking more
along the lines of what
On Thu, Jan 16, 2014 at 11:19 PM, Marcus Sorensen wrote:
> On Thu, Jan 16, 2014 at 12:33 PM, Sheng Yang wrote:
> > On Thu, Jan 9, 2014 at 7:04 AM, Daan Hoogland <
> dhoogl...@schubergphilis.com>
> > wrote:
> >>
> >> H Marcus, We had a small session on how we plan to go about ipv6
> >> configurati
Yes, let's not shut out the ULA option.
For the LB "Public" interface, will this be just another tier? That is,
not an explicit public VLAN.
Since IPV6 support is still sparse, it is probably best that we support
dual stack for now.
For instance some repositories have flaky IPv6. Also, within cor
Ok, I though those could come from the same vpc range.
On Fri, Jan 17, 2014 at 2:58 PM, Marcus Sorensen wrote:
> From what I understand, SLAAC only works with /64s, larger breaks
> various discovery protocols and is against RFC. Half of the address is
> the prefix and the other half is (mostly) M
>From what I understand, SLAAC only works with /64s, larger breaks
various discovery protocols and is against RFC. Half of the address is
the prefix and the other half is (mostly) MAC. What you're describing
would work if we didn't want to do SLAAC, but would require an
alternate means of assignmen
On Fri, Jan 17, 2014 at 8:45 AM, Marcus Sorensen wrote:
> guest networks, my initial preference would be for SLAAC, but I think
> ultimately we'd want to be able to assign multiple ips to a guest.
> With the 64 bits of the SLAAC space dedicated to all of the unique MAC
> address possibilities, we
Good point. These are the kinds of things we should be aware of right
now. Even though we don't necessarily want to bite off too much right
now in initial implementation, we want to plan so that certain things
we may want to do aren't impossible.
I was thinking either the cloud provider would have
On Thu, Jan 16, 2014 at 12:33 PM, Sheng Yang wrote:
> On Thu, Jan 9, 2014 at 7:04 AM, Daan Hoogland
> wrote:
>>
>> H Marcus, We had a small session on how we plan to go about ipv6
>> configuration with your bullet list present. Comments are still
>> brainstorming phase quality but hopefully they
Are we assuming that the Cloud Provider has a Provider-Independent (PI)
space?
Using a Unique Local Address (ULA) space for the VPC *might* to desirable.
If VPC tiers (subnets) can span zones (not possible today), then NAT66 can
help keep addresses stable as workloads move to a different zone for
a
On Thu, Jan 9, 2014 at 7:04 AM, Daan Hoogland
wrote:
> H Marcus, We had a small session on how we plan to go about ipv6
> configuration with your bullet list present. Comments are still
> brainstorming phase quality but hopefully they will lead to something.
>
> > * VPC has no global IPv6 prefix (
On Thu, Jan 16, 2014 at 12:23 PM, Sheng Yang wrote:
> Hi Marcus,
>
> Sorry for jump in late.
>
> On Mon, Jan 6, 2014 at 12:11 PM, Marcus Sorensen wrote:
>
>> I've discussed this a bit with various subject matter experts at our
>> datacenters/business, and so far we're leaning toward a rollout like
Hi Marcus,
Sorry for jump in late.
On Mon, Jan 6, 2014 at 12:11 PM, Marcus Sorensen wrote:
> I've discussed this a bit with various subject matter experts at our
> datacenters/business, and so far we're leaning toward a rollout like
> this:
>
> * VPC has no global IPv6 prefix (super CIDR as curr
me, or to us I should say.
>
> Regards,
> DaanH
>
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: vrijdag 10 januari 2014 6:14
> To: dev@cloudstack.apache.org
> Cc: Daan Hoogland; Hugo Trippaers; Edwin Beekman; Erwin Blekkenhorst; Daan de
]
Sent: vrijdag 10 januari 2014 6:14
To: dev@cloudstack.apache.org
Cc: Daan Hoogland; Hugo Trippaers; Edwin Beekman; Erwin Blekkenhorst; Daan de
Goede
Subject: Re: IPv6 in VPC (was Re: IPv6 plan - questions)
Not necessarily. You can still set the upstream to send a /60 to VPC X, and
then just assign
Not necessarily. You can still set the upstream to send a /60 to VPC
X, and then just assign individual /64s from that /60 into the
networks in that VPC. You can create a route upstream for each /64,
but you can also just program the contiguous /60 route into the
upstream. That gives you future e
I think you are overlooking the fact that if you do not assign a
continuous block to a vpc you need to set routes upstream for every
tier. If you do you can set only the vpc block and let the vpc router
take care of the internal routing. Maybe I am wrong and we are just
speaking a different type of
On Thu, Jan 9, 2014 at 9:43 AM, Daan Hoogland wrote:
> On Thu, Jan 9, 2014 at 5:28 PM, Marcus Sorensen wrote:
>> Do you have any specific reasoning or need for the
>> VPC itself to have a configured contiguous block, rather than just
>> assign the /64s the networks?
>
>
> convenience in configuri
On Thu, Jan 9, 2014 at 5:28 PM, Marcus Sorensen wrote:
> Do you have any specific reasoning or need for the
> VPC itself to have a configured contiguous block, rather than just
> assign the /64s the networks?
convenience in configuring the upstream router. The idea is that
everything on the netw
Good info. I think seeing another use case helps us narrow the
requirements a bit more.
On Thu, Jan 9, 2014 at 8:04 AM, Daan Hoogland
wrote:
> H Marcus, We had a small session on how we plan to go about ipv6
> configuration with your bullet list present. Comments are still brainstorming
> phase
H Marcus, We had a small session on how we plan to go about ipv6 configuration
with your bullet list present. Comments are still brainstorming phase quality
but hopefully they will lead to something.
> * VPC has no global IPv6 prefix (super CIDR as current private space), it's
> simply IPv6 ena
21 matches
Mail list logo