cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Animesh Chaturvedi <animesh.chaturv...@citrix.com>
Subject RE: [ACS42] Schedule Remember - Feature freeze on 2013-05-31
Date Thu, 09 May 2013 17:42:31 GMT


> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: Thursday, May 09, 2013 10:39 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [ACS42] Schedule Remember - Feature freeze on 2013-05-31
> 
> Yes...I believe I will have it working for XenServer by that time with VMware
> and KVM to follow shortly thereafter.
> 
> It depends a bit on how many storage-framework issues I come across. For
> example, last night I ran into code that assumed zone-wide storage was only
> for KVM (at one time in development this was probably true).
> 
> I've also got a question pending to Edison about the grantAccess and
> revokeAccess methods...if they will be utilized by the framework for 4.2.
> Based on the answer, it will likely influence my work.
> 
> 
[Animesh>]  Edison when you get a chance can you respond to Mike's query


> On Thu, May 9, 2013 at 11:30 AM, Animesh Chaturvedi <
> animesh.chaturvedi@citrix.com> wrote:
> 
> >
> > > -----Original Message-----
> > > From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> > > Sent: Wednesday, May 08, 2013 10:55 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [ACS42] Schedule Remember - Feature freeze on
> > > 2013-05-31
> > >
> > > Hi Animesh,
> > >
> > > I have a quick question for you.
> > >
> > > As you know, I'm in the process of developing a storage plug-in for 4.2.
> > >
> > > I'm working with Edison on getting some issues out of the storage
> > framework
> > > as well as completing the implementation of the plug-in.
> > >
> > > Can you tell me how I should handle our situation in that we will
> > > likely
> > be
> > > close, but not quite there yet, as of May 31st?
> > >
> > > Can we check in what we have (as long as we don't break
> > > functionality
> > that
> > > we're aware of) and then deal with remaining issues after?
> > >
> > > Not sure exactly how the process works here.
> > >
> > > Thanks!
> > >
> > >
> > [Animesh>] Mike as community we agreed to be on time based release
> and
> > as such it means feature should be complete  with test and need to be
> > in master by 5/31  to be included for 4.2. Would you have a logical
> > chunk of working feature available by 5/31?
> >
> >
> 
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*

Mime
View raw message