+1 (binding) 

Ran it on Ubuntu in Basic mode zone with XenServers.  Tested start, stop, SG.

I really dislike that we have to put in the vhdutil by hand.  I keep forgetting 
it.  It's not a stopper though.

--Alex

> -----Original Message-----
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: Saturday, July 27, 2013 11:13 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.1.1 (Second Round)
> 
> +1 (binding)
> 
> I've upgraded a couple of internal systems and even production systems to
> 4.1.1
> 
> We were facing a couple of bugs in production which lead me to deploy a
> homebrew version of 4.1.1 in our company. The only change is a very small
> change in the security groups script for something in our env, not applicable
> to any other setup.
> 
> So I've tested 4.1.1 on our production Ubuntu 12.04 clusters.
> 
> I have to note though that we run a patched version of libvirt due to this
> issue: https://bugzilla.redhat.com/show_bug.cgi?id=977706
> 
> Building goes fine on my systems and it runs without issues for us on a large
> scale KVM deployment.
> 
> Wido
> 
> On 07/25/2013 08:04 PM, Musayev, Ilya wrote:
> > Hi All,
> >
> > I've created a 4.1.1 release, with the following artifacts up for a vote:
> >
> > Git Branch and Commit SH:
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=
> > refs/heads/4.1
> > Commit: d2c646f0a434831bd5aef88b5692c108fe26e718
> >
> > Release notes:
> >
> > http://jenkins.cloudstack.org/view/4.1/job/docs-4.1-releasenotes/23/
> >
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.1/
> >
> > PGP release keys (signed using B7B5E7FD):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Vote will be open for 72 hours.
> >
> > For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > d2c646f0a434831bd5aef88b5692c108fe26e718
> >

Reply via email to