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 <shadow...@gmail.com> 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 <shadow...@gmail.com>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 <rohit.ya...@citrix.com>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 [shadow...@gmail.com] >>> Sent: Saturday, January 12, 2013 1:33 AM >>> To: cloudstack-dev@incubator.apache.org >>> 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. >>> >> >>
