Thanks for the links, Chip. Yeah...I need to become more familiar with our workflow.
I plan to polish off what I've been working on in the next day or two. On Mon, May 20, 2013 at 1:18 PM, Chip Childers <chip.child...@sungard.com>wrote: > On Mon, May 20, 2013 at 01:14:08PM -0600, Mike Tutkowski wrote: > > Hi Chip, > > > > Yes, the intent is to provide the code for release in 4.2. Not just the > > plug-in, but also the improvements to the storage framework (which should > > benefit any company wanting to implement dynamic, zone-wide storage). > > I highly recommend that you follow the feature workflow for this then > please! > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Adding+new+features+and+design+documents > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Jira+Guidelines+%28How+to+file+and+work+on+bugs%2C+features%2C+etc.%29 > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Review+Board+Guidelines > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Branch+Merge+Expectations > > Looking forward to seeing what you've been up to! > > -chip > > > > > > > On Mon, May 20, 2013 at 1:11 PM, Chip Childers < > chip.child...@sungard.com>wrote: > > > > > On Mon, May 20, 2013 at 01:09:21PM -0600, Mike Tutkowski wrote: > > > > Hi everyone, > > > > > > > > Thanks for that info! > > > > > > > > When I started with my development work, it was mainly focused on > > > > implementing a storage plug-in to be based on Edison's new storage > > > > framework. > > > > > > > > Definitely let me know, but I was thinking such a plug-in wasn't > > > something > > > > the list would be as interested in participating in (since it is > specific > > > > to my company's SAN). > > > > > > Are you planning on this code being part of ACS? > > > > > > > > > > > However, as I got deeper into building the plug-in, it became > apparent > > > that > > > > the storage framework was not implemented sufficiently to support the > > > needs > > > > of dynamic, zone-wide storage, so I've made several changes to the > > > > framework to enhance its abilities. > > > > > > Do you want to provide these changes for everyone's benefit? > > > > > > > > > > > This was all kind of determined late in the game, so there is no > formal > > > > design for the changes I've made, but I do plan on documenting not > only > > > > these changes, but also the storage framework in general once we get > into > > > > June. > > > > > > > > I expect with the link you've provided me that I should be able to > add > > > > these fields into the DB without much of a problem. To date, I've > been > > > > testing this logic without storing the data persistently. > > > > > > > > Thanks again, guys! > > > > > > > > > > > > On Mon, May 20, 2013 at 1:00 PM, Wido den Hollander <w...@widodh.nl> > > > wrote: > > > > > > > > > > > > > > > > > > > On 05/20/2013 08:58 PM, Mike Tutkowski wrote: > > > > > > > > > >> Just throwing this out there, but maybe in the schema-410to420.sql > > > file? > > > > >> > > > > >> > > > > > Yes, that's where it should go. If this hits 4.2 I mean. > > > > > > > > > > > > > > > I'm not sure what our upgrade paths are, though, so maybe this > file > > > needs > > > > >> to get changed and others? > > > > >> > > > > > > > > > > The code will call this .sql file and modify the database as > described > > > in > > > > > that file. > > > > > > > > > > Wido > > > > > > > > > > > > > > >> > > > > >> On Mon, May 20, 2013 at 12:55 PM, Mike Tutkowski < > > > > >> mike.tutkow...@solidfire.com> wrote: > > > > >> > > > > >> Hi, > > > > >>> > > > > >>> I've been writing code to enable users to select min, max, and > burst > > > IOPS > > > > >>> for Disk Offerings. > > > > >>> > > > > >>> I've gotten to the point where I need to create these new fields > in > > > the > > > > >>> DB, but I'm not sure where we control this logic. My new code > would > > > look > > > > >>> something like this: > > > > >>> > > > > >>> > > > > >>> alter table disk_offering add column min_iops bigint(20) unsigned > > > > >>> default 0; > > > > >>> alter table disk_offering add column max_iops bigint(20) unsigned > > > > >>> default 0; > > > > >>> alter table disk_offering add column burst_iops bigint(20) > unsigned > > > > >>> default 0; > > > > >>> > > > > >>> > > > > >>> Can someone please point me to the correct place to add this > code? > > > > >>> > > > > >>> Thanks! > > > > >>> > > > > >>> -- > > > > >>> *Mike Tutkowski* > > > > >>> *Senior CloudStack Developer, SolidFire Inc.* > > > > >>> e: mike.tutkow...@solidfire.com > > > > >>> o: 303.746.7302 > > > > >>> Advancing the way the world uses the cloud< > http://solidfire.com/** > > > > >>> solution/overview/?video=play< > > > http://solidfire.com/solution/overview/?video=play> > > > > >>> > > > > > >>> *™* > > > > >>> > > > > >>> > > > > >> > > > > >> > > > > >> > > > > > > > > > > > > -- > > > > *Mike Tutkowski* > > > > *Senior CloudStack Developer, SolidFire Inc.* > > > > e: mike.tutkow...@solidfire.com > > > > o: 303.746.7302 > > > > Advancing the way the world uses the > > > > cloud<http://solidfire.com/solution/overview/?video=play> > > > > *™* > > > > > > > > > > > -- > > *Mike Tutkowski* > > *Senior CloudStack Developer, SolidFire Inc.* > > e: mike.tutkow...@solidfire.com > > o: 303.746.7302 > > Advancing the way the world uses the > > cloud<http://solidfire.com/solution/overview/?video=play> > > *™* > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
