Hi Keshava,

What we want to achieve is to enable Nova to provide the visibility of its
DR state during the whole DR procedure.

At the moment we wrote the first version of the proposal, we only consider
the VM states on both the production site as well as the standby site.

However we are considering and working on a more expanded and detailed
version as we speak, and if you are interested you are welcomed to join the
effort :)

On Fri, Nov 14, 2014 at 1:52 AM, A, Keshava <keshav...@hp.com> wrote:

> Zhipeng Huang,
>
> When multiple  Datacenters are interconnected over WAN/Internet if the
> remote the Datacenter goes down, expect the 'native VM status' to get
> changed accordingly ?
> Is this the requirement ? This requirement is  from NFV Service VM (like
> routing VM ? )
> Then is not it is  NFV routing (BGP/IGP) /MPLS signaling (LDP/RSVP)
> protocol to handle  ? Does the OpenStack needs to handle that ?
>
> Please correct me if my understanding on this problem  is not correct.
>
> Thanks & regards,
> keshava
>
> -----Original Message-----
> From: Steve Gordon [mailto:sgor...@redhat.com]
> Sent: Wednesday, November 12, 2014 6:24 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova][DR][NFV] opnfv proposal on DR
> capability enhancement on OpenStack Nova
>
> ----- Original Message -----
> > From: "Zhipeng Huang" <zhipengh...@gmail.com>
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > <openstack-dev@lists.openstack.org>
> >
> > Hi Team,
> >
> > I knew we didn't propose this in the design summit and it is kinda
> > rude in this way to jam a topic into the schedule. We were really
> > stretched thin during the summit and didn't make it to the Nova
> > discussion. Full apologies here :)
> >
> > What we want to discuss here is that we proposed a project in opnfv (
> > https://wiki.opnfv.org/collaborative_development_projects/rescuer),
> > which in fact is to enhance inter-DC DR capabilities in Nova. We hope
> > we could achieve this in the K cycle, since there is no "HUGE" changes
> > required to be done in Nova. We just propose to add certain DR status
> > in Nova so operators could see what DR state the OpenStack is
> > currently in, therefore when disaster occurs they won't cut off the
> wrong stuff.
> >
> > Sorry again if we kinda barge in here, and we sincerely hope the Nova
> > community could take a look at our proposal. Feel free to contact me
> > if anyone got any questions :)
> >
> > --
> > Zhipeng Huang
>
> Hi Zhipeng,
>
> I would just like to echo the comments from the opnfv-tech-discuss list
> (which I notice is still private?) in saying that there is very little
> detail on the wiki page describing what you actually intend to do. Given
> this, it's very hard to provide any meaningful feedback. A lot more detail
> is required, particularly if you intend to propose a specification based on
> this idea.
>
> Thanks,
>
> Steve
>
> [1] https://wiki.opnfv.org/collaborative_development_projects/rescuer
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Zhipeng Huang
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402
OpenStack, OpenDaylight, OpenCompute affcienado
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to