Re: where features are developed was: Review Request: Merge Kelven's VPC code for Vmware into asf vpc branch

On 04/08/2012, at 12:16 PM, Ewan Mellor wrote: >> What happens if there's a rockstar NetScaler developer lurking here - how do >> they get involved in that? What if the people buddy-coding are working on >> the same feature as someone that doesn't work with them - how will they >> collaborate?

Re: CloudStack Events Plans

On 08/03/2012 05:55 PM, Duncan Johnston Watt wrote: Hi. What are you guys planning to do at CloudOpen ( https://events.linuxfoundation.org/events/cloudopen/) in a few weeks? There's a plan of at least a 1 day event and there was a start to getting an agenda together, see: http://wiki.cloudst

Re: CloudStack Events Plans

Kevin, On 8/3/12 5:46 PM, "Kevin Kluge" wrote: >Mark, thanks for sharing your thoughts. I was at OSCON and thought >CloudStack had a good booth. Everybody loved the monkey shirts! I didn't make the original monkey shirts but I got the artwork I posted an updated design with the CloudStack.

Re: Review Request: Introduce pluggable vif driver support on KVM

> On Aug. 3, 2012, 10:03 p.m., Chiradeep Vittal wrote: > > plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtVifDriver.java, > > line 35 > > > > > > This should be an Interface rather than an abstract

Re: Review Request: Introduce pluggable vif driver support on KVM

> On Aug. 3, 2012, 10:31 p.m., Chiradeep Vittal wrote: > > plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtBridgeVifDriver.java, > > line 77 > > > > > > Instead of requiring the nicModel in the API

Re: Review Request: Introduce Vif Driver in KVM

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6285/ --- (Updated Aug. 6, 2012, 1:39 a.m.) Review request for cloudstack, edison su and C

Review Request: Several minor updates for configuration section in runbook

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6390/ --- Review request for cloudstack and David Nalley. Description --- update runb

Re: Regarding Runbook and L10N

Hi David, I have submitted a patch in review board, and fixed typos of Chinese translations on transifex. Would you please review the patch and update pot file on transifex.com first? One or two message keys are outdated there, and I will update PO for Chinese after you update the original pot.

[Discuss] VM Snapshot

Hi, All, I’d like to propose a new feature ‘VM snapshot’. Currently CS support volume snapshot, which is an EC-2 like public cloud solution. IMO, it addresses problems like ‘what if my volume lost or broke down, or what if my primary storage got an unrecoverable disruption’, in other words, it

RE: Review Request: CS-15823 [VMware] failed snapshot entry should be removed automatically when multiple snopshots are taken on one volume simultaneously

After reviewing the legacy code again, I suggest to expunge failed snapshot no matter what reason. I think there is no need for users to see an Error snapshot, setting up a new thread for expunging Error/Removed snapshots seem a bit heavy-weight and does not seem to improve much feasibility for

RE: where features are developed was: Review Request: Merge Kelven's VPC code for Vmware into asf vpc branch

> -Original Message- > From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett Porter > Sent: 05 August 2012 05:35 > To: cloudstack-dev@incubator.apache.org > Cc: cloudstack-dev@incubator.apache.org > Subject: Re: where features are developed was: Review Request: Merge > Kelven'

RE: Review Request: CS-15823 [VMware] failed snapshot entry should be removed automatically when multiple snopshots are taken on one volume simultaneously

But, then how would the users track what happened to their snapshots - they would see no record of them at all ? And is this going to be done for recurring snapshots as well ? I agree with Edison. Keeping a row of snapshot with Error state seems fine with me. -Original Message- From: Mi

RE: Review Request: CS-15823 [VMware] failed snapshot entry should be removed automatically when multiple snopshots are taken on one volume simultaneously

Nitin, You are right For failed recurring snapshots, no chance providing a pop up error message, users can only track them from events. I will re-use existing thread in StorageManagerImpl for cleaning up volumes and 'storage.cleanup.interval' for this purpose. Thanks & Regards Mice -Origin

RE: Proposal to grant committer status to Mice Xia

Ewan, Thanks very much. It would be a great honor for me to contribute more to CloudStack community. Regards Mice From: Ewan Mellor [mailto:ewan.mel...@eu.citrix.com] Sent: Monday, August 06, 2012 12:21 PM To: Mice Xia; cloudstack-dev@incubator.apache.org Subject: Proposal to grant comm