Open Stack

What happens when you've shared the primary IPv6 address of a VM with
another VM? To which VM does the primary key point to? I think overloading
the IPv6 address to also mean the primary key is probably a mistake that
will cause serious trouble with network-as-a-service portability.

-C




On Mon, Jul 11, 2011 at 1:03 PM, Glen Campbell
<glen.campbell at rackspace.com>wrote:

> I kind of like the IPv6 idea myself. How would it work with a service
> provider that, for example, assigns a /96 address for an instance? If the
> user can change the IP address, would that mean that the instance ID would
> change as well? Or should we just keep with the original /96 (::0) address?
>
>
>
>
>
>
> On 7/11/11 2:57 PM, "Chris Behrens" <chris.behrens at RACKSPACE.COM> wrote:
>
> >If you're referring to encoding zone information, yes it would.  I was
> >trying to ask more generally as well.  IPv6 would be a very good
> >solution, IMO.
> >
> >- Chris
> >
> >On Jul 11, 2011, at 12:47 PM, Sandy Walsh wrote:
> >
> >> Won't an IPv6 address do that by it's very nature?
> >>
> >> -S
> >>
> >> ________________________________________
> >> From: openstack-bounces+sandy.walsh=rackspace.com at lists.launchpad.net
> >>[openstack-bounces+sandy.walsh=rackspace.com at lists.launchpad.net] on
> >>behalf of Chris Behrens [chris.behrens at RACKSPACE.COM]
> >> Sent: Monday, July 11, 2011 4:24 PM
> >> To: Ed Leafe
> >> Cc: openstack at lists.launchpad.net; Chris Behrens
> >> Subject: Re: [Openstack] Cross-zone instance identifiers in EC2 API -
> >>Is it worth the effort?
> >>
> >> On Jul 11, 2011, at 12:01 PM, Ed Leafe wrote:
> >>
> >>> On Jul 11, 2011, at 2:04 PM, Eric Day wrote:
> >>>
> >>>>> How is
> >>>>>
> >>>>> nova-<account>-<instance uuid>
> >>>>>
> >>>>> any different than:
> >>>>>
> >>>>> AAAABBBB-CCCC-DDDD-EEEE-FFFFGGGGHHHH
> >>>>>
> >>>>> Where AAAA/BBBB/CCCC (or some subset of them) are reserved/regulated?
> >>>>
> >>>> Nothing, if DDDD-EEEE-FFFFGGGGHHHH is a full UUID. If we compare to
> >>>> swift, the account prefix is a UUID too. The account prefix could be
> >>>> fixed for a session or passed in to every request depending on how
> >>>> things are decided.
> >>>
> >>>      <sigh>
> >>>
> >>>      It's a shame that the ipv6 proposal was never more fully
> >>>considered. That would handle the uniqueness, with the added benefit of
> >>>providing simple zone routing via DNS, with the exact same 128-bit/32
> >>>char size.
> >>
> >> I don't I remember that proposal, but that's such a neat idea.  Was
> >>anything discussed at all in Santa Clara regarding encoding zone
> >>information in the instance identifier?  I apparently missed the
> >>instance identifier discussion somehow.
> >>
> >> - Chris
> >>
> >>
> >> This email may include confidential information. If you received it in
> >>error, please delete it.
> >>
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~openstack
> >> Post to     : openstack at lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~openstack
> >> More help   : https://help.launchpad.net/ListHelp
> >
> >This email may include confidential information. If you received it in
> >error, please delete it.
> >
> >
> >_______________________________________________
> >Mailing list: https://launchpad.net/~openstack
> >Post to     : openstack at lists.launchpad.net
> >Unsubscribe : https://launchpad.net/~openstack
> >More help   : https://help.launchpad.net/ListHelp
>
> This email may include confidential information. If you received it in
> error, please delete it.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Christopher MacGown
Piston Cloud Computing, Inc.
(415) 300-0944
chris at piston.cc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110711/a59b0c3d/attachment.html>