Let's verify actually that those tests do fail due to the large offerings. I assumed they would also be a problem when we were fixing the shared primary storage issue, but then this morning when I was dreaming about work stuff I recalled the over provisioning settings, and that might make the disk offerings a non issue. On Jan 12, 2013 10:29 AM, "Ryan Dietrich" <[email protected]> wrote:
> Hi, I'm new to the list/project. > > After running the DB deploy target, and starting cloudstack, the entries > for the larger disk offerings kept coming back until I removed lines from: > > server/src/com/cloud/server/ConfigurationServerImpl.java > > - createdefaultDiskOffering(null, "Medium", "Medium Disk, 20 > GB", 20, null, false, false); > - createdefaultDiskOffering(null, "Large", "Large Disk, 100 > GB", 100, null, false, false); > - createdefaultDiskOffering(null, "Large", "Large Disk, 100 > GB", 100, null, false, false); > > So, this section of code overrides whatever you have in the SQL/XML files? > > -Ryan Dietrich > > > On Jan 11, 2013, at 11:40 PM, Rohit Yadav <[email protected]> wrote: > > > Okay, so we can do two things have a set of offerings provided via > devcloud/devcloud-kvm.sql or users are free to create their own offerings. > > We can add the small/med/large offerings such as 1/5/10GB offerings > (local and nfs) or as you need them in the sql, commit ftw! > > > > Regards. > > ________________________________________ > > From: Marcus Sorensen [[email protected]] > > Sent: Saturday, January 12, 2013 6:15 AM > > To: [email protected] > > Subject: Re: [PROPOSAL] modify devcloud storage setup > > > > I think 30GB is fine for devcloud given the 50MB tinylinux. I just wanted > > the disk offerings in the zone to work with that. > > > > On Fri, Jan 11, 2013 at 5:36 PM, Rohit Yadav <[email protected]> > wrote: > > > >> Yes just sql changes, no change possible for that in devcloud. If one > >> wants more disk space, they can resize vmdk and resizefs on devcloud and > >> reboot. > >> Current disk size is 30GB, do you want this to be extended? I think it > >> should be sufficient for a small datacenter use case on basic zone on > one's > >> laptop. > >> > >> Regards. > >> > >> On 11-Jan-2013, at 3:50 PM, Marcus Sorensen <[email protected]> > wrote: > >> > >>> We may also want to consider adjusting the disk offering sizes in > >> devcloud, > >>> we fail test_01_create_volume because (among other things) there is not > >>> 100GB available to create a volume, as it tests all known disk > offerings. > >>> Maybe have small/med/large be 5GB, 10GB, 15GB. That's probably for the > >> sql? > >>> > >>> On Fri, Jan 11, 2013 at 2:22 PM, Marcus Sorensen <[email protected] > >>> wrote: > >>> > >>>> Yes, I see that it's currently hosted on people.apache.org, and I > >> assumed > >>>> you'd know how to replace it. This would help a lot. Thanks > >>>> > >>>> > >>>> On Fri, Jan 11, 2013 at 2:07 PM, Rohit Yadav <[email protected] > >>> wrote: > >>>> > >>>>> Cool, let's do both and have primary nfs and local storage. While > >> having > >>>>> local storage will be better for vm life cycle. > >>>>> Yes, let's do this. Marcus, do you want me to create a new image with > >>>>> these changes? I can do that this weekend. > >>>>> > >>>>> Regards. > >>>>> ________________________________________ > >>>>> From: Marcus Sorensen [[email protected]] > >>>>> Sent: Saturday, January 12, 2013 1:33 AM > >>>>> To: [email protected] > >>>>> Subject: [PROPOSAL] modify devcloud storage setup > >>>>> > >>>>> In running integration tests, I noticed that the volume tests fail > >> because > >>>>> there are shared and local compute/disk offerings. I propose that we > >> add > >>>>> to > >>>>> devcloud an /opt/storage/primarynfs directory, shared out in > >> /etc/exports, > >>>>> and we change the devcloud config to add this primary storage in. > >>>>> Optionally, we can change the default tags to use local storage for > >>>>> efficiency in other things, but this way there is both a local and a > >>>>> shared > >>>>> storage type for the tests to succeed. > >>>>> > >>>> > >>>> > >> > >> > >
