You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Chip Childers (ASF)" <ch...@apache.org> on 2012/10/22 18:16:23 UTC

[VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Hi All,

I would like to call a vote for Apache CloudStack (Incubating) Release
4.0.0-incubating (third round).

We encourage the whole community to download and test these release
artifacts, so that any critical issues can be resolved before the
release is made. The more time that each individual spends reviewing
the artifacts, the higher confidence we can have in both the release
itself and our ability to pass an IPMC vote later on.  Everyone is free
to vote on this release, so please give it a shot.

Instructions for Validating and Testing the artifacts can be found here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure

If you have any trouble setting up a test environment using the
procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
will be sure to help, and we'll improve our test procedure
documentation at the same time!

Now, on to the specifics of what we are voting on...


The following artifacts are up for the vote:
http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/

PGP release keys (signed using A99A5D58):
http://people.apache.org/~chipchilders/dist/cloudstack/KEYS

Branch: 4.0
Commit: 6355965dcd956811dd471a9d03c73dadcf68f480


List of changes:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0

The artifacts being voted on during this round also include the
following additional fixes (most were identified as part of testing
during the last round of voting):

* Many documentation fixes (particularly the release notes and
installation guide)
* CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
* CLOUDSTACK-349: Russian l10n not properly displaying
* Correction to the devcloud rdeploy build target, to make testing easier
* CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
* CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
* DISCLAIMER added to the Marvin tool dir


The vote will be open for 72 hours.


For sanity in tallying the vote, can PPMC and IPMC members please be
sure to indicate "(binding)" with their vote?
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Thanks!

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Edison Su <Ed...@citrix.com>.
+1 [binding]
Tested on devcloud, looks good.

> -----Original Message-----
> From: chip.childers@sungard.com [mailto:chip.childers@sungard.com] On
> Behalf Of Chip Childers (ASF)
> Sent: Monday, October 22, 2012 9:16 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> Hi All,
> 
> I would like to call a vote for Apache CloudStack (Incubating) Release
> 4.0.0-incubating (third round).
> 
> We encourage the whole community to download and test these release
> artifacts, so that any critical issues can be resolved before the
> release is made. The more time that each individual spends reviewing
> the artifacts, the higher confidence we can have in both the release
> itself and our ability to pass an IPMC vote later on.  Everyone is free
> to vote on this release, so please give it a shot.
> 
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+t
> est+procedure
> 
> If you have any trouble setting up a test environment using the
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
> will be sure to help, and we'll improve our test procedure
> documentation at the same time!
> 
> Now, on to the specifics of what we are voting on...
> 
> 
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> incubating/
> 
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> 
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> 
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-
> cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
> 
> The artifacts being voted on during this round also include the
> following additional fixes (most were identified as part of testing
> during the last round of voting):
> 
> * Many documentation fixes (particularly the release notes and
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the
> UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing
> easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will
> fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
> 
> 
> The vote will be open for 72 hours.
> 
> 
> For sanity in tallying the vote, can PPMC and IPMC members please be
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Thanks!

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Prasanna Santhanam <ts...@apache.org>.
Here's my +1,

a: Verified keys
➜  cloudstack  gpg --recv-keys CC56CEA8
gpg: requesting key CC56CEA8 from hkp server keys.gnupg.net
gpg: key CC56CEA8: "Chip Childers <ch...@apache.org>" 1 new
signature
gpg: Total number processed: 1
gpg:         new signatures: 1

➜  cloudstack  gpg --verify apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
gpg: Signature made Monday 22 October 2012 09:20:37 PM IST using RSA
key ID A99A5D58
gpg: Good signature from "Chip Childers <ch...@apache.org>"

b: RAT succeeds with the LICENSE checks
➜  apache-cloudstack-4.0.0-incubating-src  mvn --projects='org.apache.cloudstack:cloudstack' org.apache.rat:apache-rat-plugin:0.8:check
------------------------------------------------------------------------
[INFO] Building Apache CloudStack 4.0.0-incubating-SNAPSHOT
------------------------------------------------------------------------
>Snipped RAT activity 
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
------------------------------------------------------------------------
[INFO] Total time: 1:31.395s
[INFO] Finished at: Fri Oct 26 22:13:40 IST 2012


c: diffed repo contents with artifact contents. No diff was observed

d: Did a mvn + ant compile
➜  apache-cloudstack-4.0.0-incubating-src  mvn -P deps; ant clean-all build-all

Compilation succeeds.

e: Deployed a 4 node Xenserver based deployment with 2 zones with
latest non-OSS artifact off jenkins. Ran Marvin's BVT against the
deployment. Script failures tested manually.

No product failures observed!

Thanks,

-- 
Prasanna.,

On Mon, Oct 22, 2012 at 12:16:23PM -0400, Chip Childers (ASF) wrote:
> Hi All,
> 
> I would like to call a vote for Apache CloudStack (Incubating) Release
> 4.0.0-incubating (third round).
> 
> We encourage the whole community to download and test these release
> artifacts, so that any critical issues can be resolved before the
> release is made. The more time that each individual spends reviewing
> the artifacts, the higher confidence we can have in both the release
> itself and our ability to pass an IPMC vote later on.  Everyone is free
> to vote on this release, so please give it a shot.
> 
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
> 
> If you have any trouble setting up a test environment using the
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
> will be sure to help, and we'll improve our test procedure
> documentation at the same time!
> 
> Now, on to the specifics of what we are voting on...
> 
> 
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
> 
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> 
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> 
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
> 
> The artifacts being voted on during this round also include the
> following additional fixes (most were identified as part of testing
> during the last round of voting):
> 
> * Many documentation fixes (particularly the release notes and
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
> 
> 
> The vote will be open for 72 hours.
> 
> 
> For sanity in tallying the vote, can PPMC and IPMC members please be
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Thanks!

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Charles Moulliard <ch...@gmail.com>.
As installation procedure moves from ant to maven, that should be
interesting to add maven commands to do the build/installation in the
INSTALL.md file

On Thu, Oct 25, 2012 at 11:32 AM, sebgoa <ru...@gmail.com> wrote:

> +1
>
> Downloaded:
> > http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> > incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
> built, deployed, deployeddb, rdebug in DevCloud
> configured devcloud
> started instance via GUI, destroyed instance via GUI
> generated user keys, enabled ec2
> restarted mgt server, registered user, started/destroyed instance via boto
> script.
>
> -Sebastien
>
> On Oct 25, 2012, at 10:51 AM, Suresh Sadhu wrote:
>
> > +1
> >
> > Followed the test procedure mentioned  in the specified link (
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure)
> and performed below operations:
> >
> > .VM life cycle(VM create/stop/destroy/expunge)
> > Add volume/detach volume
> > Add an account
> >
> > Thanks
> > sadhu
> >
> > -----Original Message-----
> > From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> > Sent: 25 October 2012 10:00
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
> round
> >
> > +1  Installed on KVM guest with local storage. Ran through a simple
> > zone creation. Installed a template. Launched a VPC, started up two
> tiers, some virtual machines, created some ACLs, a load balancer.
> > Checked password script/server was working. Deleted VMs, networks, VPC.
> >
> > On Wed, Oct 24, 2012 at 9:06 PM, Chandan Purushothama <
> Chandan.Purushothama@citrix.com> wrote:
> >> +1
> >>
> >> I followed the test procedure mentioned at
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure. The local machine on which I deployed the DevCloud VM is freshly deployed
> Ubuntu 12.04-Server x86_64 host.
> >>
> >> Downloaded the following artifacts:
> >>
> >> wget http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >> wget
> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> >> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
> >> wget
> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> >> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
> >> wget
> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> >> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5
> >> wget
> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> >> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha
> >>
> >> Verified signatures and hash files using "gpg --verify
> >> apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc " -> "Good
> >> Signature" mentioned in the returned output
> >>
> >> Compared the contents of the release artifact with the contents pulled
> >> from the repo. No difference was observed
> >>
> >> Verified the Code's License Headers
> >> **Suggestion: Better to add the note "If you're on Ubuntu and using the
> PPA:natecarlson/maven3 (viz. Installing tools above), you've to use mvn3
> instead of mvn" in this section of the test procedure.
> >>
> >> Complied the source code successfully. Deployed it into the DevCloud
> VM. Started and configured the Management Server successfully using the
> configuration instructions given in the test procedure.
> >>
> >> Secondary Storage VM and Console Proxy VM got deployed after
> >> configuration of the management server. Successfully deployed the
> >> first VM
> >>
> >> Changed the global settings of "expunge.interval" and "expunge.delay"
> to 120. Configured "enable.ec2.api" to "true"
> >>
> >> On clicking the console view of the deployed User VM using the "show
> console" button, Console view of the User VM appeared. Stopped the User VM
> using the Stop button on the UI. Destroyed the Stopped VM using the destroy
> button on the UI. Observed the VM expunge after 2 minutes.
> >>
> >> EC2 Testing:
> >>
> >> Generated the API and Secret key for the admin account. I renamed the
>  tinyOffering to m1.small as instructed in the test procedure. Added a rule
> on the Virtual box to forward host port 7080 TCP traffic to VM's port 7080.
> After generating a X509 SSL certificate on the local machine, I used it and
> successfully registered the Admin account's api and secret key on the
> devCloud's Management Server's cloudbridge database. I verified the
> presence of the API and Secret key  of admin account in the
> "usercredentials"  table in the "cloudbridge" database.
> >>
> >> Used the python script example given in the test procedure. Substituted
> the api and secret key in the script with those of the admin account.
> Successfully deployed a VM on the DevCloud Setup using the python script. I
> destroyed the instance via the UI and used the script two more times to
> deploy two more VMs on the devCloud Setup. The Two VMs got deployed
> Successfully.
> >>
> >> **Note:  I encountered a problem with deploying my first VM during my
> first attempt. This is due to my mistake where I overlooked the requirement
> to change the memory required for DevCloud VM from 1024 to 2046MB. I
> repeated the entire test procedure(except the pre-requisites)  the second
> time and made the above mentioned observations.
> >>
> >> Thank you,
> >> Chandan.
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Chip Childers [mailto:chip.childers@sungard.com]
> >> Sent: Wednesday, October 24, 2012 11:11 AM
> >> To: cloudstack-dev@incubator.apache.org
> >> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
> >> round
> >>
> >> On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote:
> >>>
> >>> I'm a bit confused by the LICENSE and NOTICE files that are in the
> root of the package.
> >>>
> >>> They seem to be LICENSE/NOTICE files that would be good for a binary
> distribution of Cloudstack built from this package, but don't really apply
> to this package.  Or maybe they were from before the dep jars were changed
> to be grabbed via maven and were part of the src.    Right?
> >>>
> >>> The license file lists license for jars in lib and aws and such that
> don't exist.   Likewise for the NOTICE file.
> >>>
> >>> Don't get me wrong.  I think these LICENSE/NOTICE files are great to
> have for people that are building binary distributions of Cloudstack and
> having that information available to them certainly takes much of the
> burden off of them, but I do question if they are appropriate for the
> Apache source based releases.
> >>>
> >>>
> >>> Dan
> >>
> >> Dan,
> >>
> >> Yes, the jars referenced in the legal docs are pulled in by the
> packaging process.  The expectation was that the material would be brought
> into any packaging (including the non-asf, but community provided,
> deb/rpm's).  When looking for examples from other ASF projects, IIRC I saw
> both approaches (I'll have to dig a bit to find the examples that I was
> looking at).  At one point, I had a "*_BINARY"
> >> version of both files and the standard files for the source itself, but
> I then decided to simplify into a single set that would work for both
> situations.
> >>
> >> So I guess the question is this: is this an acceptable approach or not?
> >>
> >> -chip
> >>
> >>> On Oct 22, 2012, at 12:16 PM, Chip Childers (ASF) <
> chipchilders@apache.org> wrote:
> >>>
> >>>> Hi All,
> >>>>
> >>>> I would like to call a vote for Apache CloudStack (Incubating)
> >>>> Release 4.0.0-incubating (third round).
> >>>>
> >>>> We encourage the whole community to download and test these release
> >>>> artifacts, so that any critical issues can be resolved before the
> >>>> release is made. The more time that each individual spends reviewing
> >>>> the artifacts, the higher confidence we can have in both the release
> >>>> itself and our ability to pass an IPMC vote later on.  Everyone is
> >>>> free to vote on this release, so please give it a shot.
> >>>>
> >>>> Instructions for Validating and Testing the artifacts can be found
> here:
> >>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.
> >>>> 0
> >>>> +test+procedure
> >>>>
> >>>> If you have any trouble setting up a test environment using the
> >>>> procedure above, please ask on the cloudstack-dev@i.a.o list.
> >>>> Someone will be sure to help, and we'll improve our test procedure
> >>>> documentation at the same time!
> >>>>
> >>>> Now, on to the specifics of what we are voting on...
> >>>>
> >>>>
> >>>> The following artifacts are up for the vote:
> >>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.
> >>>> 0
> >>>> -incubating/
> >>>>
> >>>> PGP release keys (signed using A99A5D58):
> >>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >>>>
> >>>> Branch: 4.0
> >>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> >>>>
> >>>>
> >>>> List of changes:
> >>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a
> >>>> =
> >>>> blob_plain;f=CHANGES;hb=refs/heads/4.0
> >>>>
> >>>> The artifacts being voted on during this round also include the
> >>>> following additional fixes (most were identified as part of testing
> >>>> during the last round of voting):
> >>>>
> >>>> * Many documentation fixes (particularly the release notes and
> >>>> installation guide)
> >>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on
> >>>> the UI
> >>>> * CLOUDSTACK-349: Russian l10n not properly displaying
> >>>> * Correction to the devcloud rdeploy build target, to make testing
> >>>> easier
> >>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
> >>>> will fail
> >>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> >>>> * DISCLAIMER added to the Marvin tool dir
> >>>>
> >>>>
> >>>> The vote will be open for 72 hours.
> >>>>
> >>>>
> >>>> For sanity in tallying the vote, can PPMC and IPMC members please be
> >>>> sure to indicate "(binding)" with their vote?
> >>>> [ ] +1  approve
> >>>> [ ] +0  no opinion
> >>>> [ ] -1  disapprove (and reason why)
> >>>>
> >>>> Thanks!
> >>>
> >>> --
> >>> Daniel Kulp
> >>> dkulp@apache.org - http://dankulp.com/blog Talend Community Coder -
> >>> http://coders.talend.com
> >>>
> >>>
>
>


-- 
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Hugo Trippaers <HT...@schubergphilis.com>.
+1 

Tested with XenServer 6.0.2 and Nicira NVP 2.1.0. Deployed templates, vm. 
NVP specific tests, creation of STT isolated physical network and logical networks mapped to tenant guest networks (Advanced Networking only).

Cheers,

Hugo

> -----Original Message-----
> From: sebgoa [mailto:runseb@gmail.com]
> Sent: Thursday, October 25, 2012 11:32 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> +1
> 
> Downloaded:
> > http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> > incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
> built, deployed, deployeddb, rdebug in DevCloud configured devcloud
> started instance via GUI, destroyed instance via GUI generated user keys,
> enabled ec2 restarted mgt server, registered user, started/destroyed
> instance via boto script.
> 
> -Sebastien
> 
> On Oct 25, 2012, at 10:51 AM, Suresh Sadhu wrote:
> 
> > +1
> >
> > Followed the test procedure mentioned  in the specified link
> (https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0
> +test+procedure) and performed below operations:
> >
> > .VM life cycle(VM create/stop/destroy/expunge) Add volume/detach
> > volume Add an account
> >
> > Thanks
> > sadhu
> >
> > -----Original Message-----
> > From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> > Sent: 25 October 2012 10:00
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
> > round
> >
> > +1  Installed on KVM guest with local storage. Ran through a simple
> > zone creation. Installed a template. Launched a VPC, started up two tiers,
> some virtual machines, created some ACLs, a load balancer.
> > Checked password script/server was working. Deleted VMs, networks,
> VPC.
> >
> > On Wed, Oct 24, 2012 at 9:06 PM, Chandan Purushothama
> <Ch...@citrix.com> wrote:
> >> +1
> >>
> >> I followed the test procedure mentioned at
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+
> test+procedure . The local machine on which I deployed the DevCloud VM is
> freshly deployed Ubuntu 12.04-Server x86_64 host.
> >>
> >> Downloaded the following artifacts:
> >>
> >> wget http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >> wget
> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0
> >> -
> >> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
> >> wget
> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0
> >> - incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
> >> wget
> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0
> >> -
> >> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5
> >> wget
> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0
> >> - incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha
> >>
> >> Verified signatures and hash files using "gpg --verify
> >> apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc " -> "Good
> >> Signature" mentioned in the returned output
> >>
> >> Compared the contents of the release artifact with the contents
> >> pulled from the repo. No difference was observed
> >>
> >> Verified the Code's License Headers
> >> **Suggestion: Better to add the note "If you're on Ubuntu and using the
> PPA:natecarlson/maven3 (viz. Installing tools above), you've to use mvn3
> instead of mvn" in this section of the test procedure.
> >>
> >> Complied the source code successfully. Deployed it into the DevCloud
> VM. Started and configured the Management Server successfully using the
> configuration instructions given in the test procedure.
> >>
> >> Secondary Storage VM and Console Proxy VM got deployed after
> >> configuration of the management server. Successfully deployed the
> >> first VM
> >>
> >> Changed the global settings of "expunge.interval" and "expunge.delay" to
> 120. Configured "enable.ec2.api" to "true"
> >>
> >> On clicking the console view of the deployed User VM using the "show
> console" button, Console view of the User VM appeared. Stopped the User
> VM using the Stop button on the UI. Destroyed the Stopped VM using the
> destroy button on the UI. Observed the VM expunge after 2 minutes.
> >>
> >> EC2 Testing:
> >>
> >> Generated the API and Secret key for the admin account. I renamed the
> tinyOffering to m1.small as instructed in the test procedure. Added a rule on
> the Virtual box to forward host port 7080 TCP traffic to VM's port 7080. After
> generating a X509 SSL certificate on the local machine, I used it and
> successfully registered the Admin account's api and secret key on the
> devCloud's Management Server's cloudbridge database. I verified the
> presence of the API and Secret key  of admin account in the
> "usercredentials"  table in the "cloudbridge" database.
> >>
> >> Used the python script example given in the test procedure. Substituted
> the api and secret key in the script with those of the admin account.
> Successfully deployed a VM on the DevCloud Setup using the python script. I
> destroyed the instance via the UI and used the script two more times to
> deploy two more VMs on the devCloud Setup. The Two VMs got deployed
> Successfully.
> >>
> >> **Note:  I encountered a problem with deploying my first VM during my
> first attempt. This is due to my mistake where I overlooked the requirement
> to change the memory required for DevCloud VM from 1024 to 2046MB. I
> repeated the entire test procedure(except the pre-requisites)  the second
> time and made the above mentioned observations.
> >>
> >> Thank you,
> >> Chandan.
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Chip Childers [mailto:chip.childers@sungard.com]
> >> Sent: Wednesday, October 24, 2012 11:11 AM
> >> To: cloudstack-dev@incubator.apache.org
> >> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
> >> round
> >>
> >> On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote:
> >>>
> >>> I'm a bit confused by the LICENSE and NOTICE files that are in the root of
> the package.
> >>>
> >>> They seem to be LICENSE/NOTICE files that would be good for a binary
> distribution of Cloudstack built from this package, but don't really apply to
> this package.  Or maybe they were from before the dep jars were changed
> to be grabbed via maven and were part of the src.    Right?
> >>>
> >>> The license file lists license for jars in lib and aws and such that don't
> exist.   Likewise for the NOTICE file.
> >>>
> >>> Don't get me wrong.  I think these LICENSE/NOTICE files are great to
> have for people that are building binary distributions of Cloudstack and
> having that information available to them certainly takes much of the burden
> off of them, but I do question if they are appropriate for the Apache source
> based releases.
> >>>
> >>>
> >>> Dan
> >>
> >> Dan,
> >>
> >> Yes, the jars referenced in the legal docs are pulled in by the packaging
> process.  The expectation was that the material would be brought into any
> packaging (including the non-asf, but community provided, deb/rpm's).
> When looking for examples from other ASF projects, IIRC I saw both
> approaches (I'll have to dig a bit to find the examples that I was looking at).
> At one point, I had a "*_BINARY"
> >> version of both files and the standard files for the source itself, but I then
> decided to simplify into a single set that would work for both situations.
> >>
> >> So I guess the question is this: is this an acceptable approach or not?
> >>
> >> -chip
> >>
> >>> On Oct 22, 2012, at 12:16 PM, Chip Childers (ASF)
> <ch...@apache.org> wrote:
> >>>
> >>>> Hi All,
> >>>>
> >>>> I would like to call a vote for Apache CloudStack (Incubating)
> >>>> Release 4.0.0-incubating (third round).
> >>>>
> >>>> We encourage the whole community to download and test these
> release
> >>>> artifacts, so that any critical issues can be resolved before the
> >>>> release is made. The more time that each individual spends
> >>>> reviewing the artifacts, the higher confidence we can have in both
> >>>> the release itself and our ability to pass an IPMC vote later on.
> >>>> Everyone is free to vote on this release, so please give it a shot.
> >>>>
> >>>> Instructions for Validating and Testing the artifacts can be found here:
> >>>>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.
> >>>> 0
> >>>> +test+procedure
> >>>>
> >>>> If you have any trouble setting up a test environment using the
> >>>> procedure above, please ask on the cloudstack-dev@i.a.o list.
> >>>> Someone will be sure to help, and we'll improve our test procedure
> >>>> documentation at the same time!
> >>>>
> >>>> Now, on to the specifics of what we are voting on...
> >>>>
> >>>>
> >>>> The following artifacts are up for the vote:
> >>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.
> >>>> 0
> >>>> -incubating/
> >>>>
> >>>> PGP release keys (signed using A99A5D58):
> >>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >>>>
> >>>> Branch: 4.0
> >>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> >>>>
> >>>>
> >>>> List of changes:
> >>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;
> >>>> a
> >>>> =
> >>>> blob_plain;f=CHANGES;hb=refs/heads/4.0
> >>>>
> >>>> The artifacts being voted on during this round also include the
> >>>> following additional fixes (most were identified as part of testing
> >>>> during the last round of voting):
> >>>>
> >>>> * Many documentation fixes (particularly the release notes and
> >>>> installation guide)
> >>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on
> >>>> the UI
> >>>> * CLOUDSTACK-349: Russian l10n not properly displaying
> >>>> * Correction to the devcloud rdeploy build target, to make testing
> >>>> easier
> >>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
> >>>> will fail
> >>>> * CLOUDSTACK-118: Status of host resorce stuck in
> "ErrorInMaintenance"
> >>>> * DISCLAIMER added to the Marvin tool dir
> >>>>
> >>>>
> >>>> The vote will be open for 72 hours.
> >>>>
> >>>>
> >>>> For sanity in tallying the vote, can PPMC and IPMC members please
> >>>> be sure to indicate "(binding)" with their vote?
> >>>> [ ] +1  approve
> >>>> [ ] +0  no opinion
> >>>> [ ] -1  disapprove (and reason why)
> >>>>
> >>>> Thanks!
> >>>
> >>> --
> >>> Daniel Kulp
> >>> dkulp@apache.org - http://dankulp.com/blog Talend Community Coder
> -
> >>> http://coders.talend.com
> >>>
> >>>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by sebgoa <ru...@gmail.com>.
+1

Downloaded:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
built, deployed, deployeddb, rdebug in DevCloud
configured devcloud
started instance via GUI, destroyed instance via GUI
generated user keys, enabled ec2
restarted mgt server, registered user, started/destroyed instance via boto script.

-Sebastien

On Oct 25, 2012, at 10:51 AM, Suresh Sadhu wrote:

> +1
> 
> Followed the test procedure mentioned  in the specified link (https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure) and performed below operations:
> 
> .VM life cycle(VM create/stop/destroy/expunge)
> Add volume/detach volume
> Add an account
> 
> Thanks
> sadhu
> 
> -----Original Message-----
> From: Marcus Sorensen [mailto:shadowsor@gmail.com] 
> Sent: 25 October 2012 10:00
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> +1  Installed on KVM guest with local storage. Ran through a simple
> zone creation. Installed a template. Launched a VPC, started up two tiers, some virtual machines, created some ACLs, a load balancer.
> Checked password script/server was working. Deleted VMs, networks, VPC.
> 
> On Wed, Oct 24, 2012 at 9:06 PM, Chandan Purushothama <Ch...@citrix.com> wrote:
>> +1
>> 
>> I followed the test procedure mentioned at https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure . The local machine on which I deployed the DevCloud VM is freshly deployed Ubuntu 12.04-Server x86_64 host.
>> 
>> Downloaded the following artifacts:
>> 
>> wget http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>> wget 
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
>> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
>> wget 
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
>> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
>> wget 
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
>> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5
>> wget 
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
>> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha
>> 
>> Verified signatures and hash files using "gpg --verify 
>> apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc " -> "Good 
>> Signature" mentioned in the returned output
>> 
>> Compared the contents of the release artifact with the contents pulled 
>> from the repo. No difference was observed
>> 
>> Verified the Code's License Headers
>> **Suggestion: Better to add the note "If you're on Ubuntu and using the PPA:natecarlson/maven3 (viz. Installing tools above), you've to use mvn3 instead of mvn" in this section of the test procedure.
>> 
>> Complied the source code successfully. Deployed it into the DevCloud VM. Started and configured the Management Server successfully using the configuration instructions given in the test procedure.
>> 
>> Secondary Storage VM and Console Proxy VM got deployed after 
>> configuration of the management server. Successfully deployed the 
>> first VM
>> 
>> Changed the global settings of "expunge.interval" and "expunge.delay" to 120. Configured "enable.ec2.api" to "true"
>> 
>> On clicking the console view of the deployed User VM using the "show console" button, Console view of the User VM appeared. Stopped the User VM using the Stop button on the UI. Destroyed the Stopped VM using the destroy button on the UI. Observed the VM expunge after 2 minutes.
>> 
>> EC2 Testing:
>> 
>> Generated the API and Secret key for the admin account. I renamed the  tinyOffering to m1.small as instructed in the test procedure. Added a rule on the Virtual box to forward host port 7080 TCP traffic to VM's port 7080. After generating a X509 SSL certificate on the local machine, I used it and successfully registered the Admin account's api and secret key on the devCloud's Management Server's cloudbridge database. I verified the presence of the API and Secret key  of admin account in the "usercredentials"  table in the "cloudbridge" database.
>> 
>> Used the python script example given in the test procedure. Substituted the api and secret key in the script with those of the admin account. Successfully deployed a VM on the DevCloud Setup using the python script. I destroyed the instance via the UI and used the script two more times to deploy two more VMs on the devCloud Setup. The Two VMs got deployed Successfully.
>> 
>> **Note:  I encountered a problem with deploying my first VM during my first attempt. This is due to my mistake where I overlooked the requirement to change the memory required for DevCloud VM from 1024 to 2046MB. I repeated the entire test procedure(except the pre-requisites)  the second time and made the above mentioned observations.
>> 
>> Thank you,
>> Chandan.
>> 
>> 
>> 
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Wednesday, October 24, 2012 11:11 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third 
>> round
>> 
>> On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote:
>>> 
>>> I'm a bit confused by the LICENSE and NOTICE files that are in the root of the package.
>>> 
>>> They seem to be LICENSE/NOTICE files that would be good for a binary distribution of Cloudstack built from this package, but don't really apply to this package.  Or maybe they were from before the dep jars were changed to be grabbed via maven and were part of the src.    Right?
>>> 
>>> The license file lists license for jars in lib and aws and such that don't exist.   Likewise for the NOTICE file.
>>> 
>>> Don't get me wrong.  I think these LICENSE/NOTICE files are great to have for people that are building binary distributions of Cloudstack and having that information available to them certainly takes much of the burden off of them, but I do question if they are appropriate for the Apache source based releases.
>>> 
>>> 
>>> Dan
>> 
>> Dan,
>> 
>> Yes, the jars referenced in the legal docs are pulled in by the packaging process.  The expectation was that the material would be brought into any packaging (including the non-asf, but community provided, deb/rpm's).  When looking for examples from other ASF projects, IIRC I saw both approaches (I'll have to dig a bit to find the examples that I was looking at).  At one point, I had a "*_BINARY"
>> version of both files and the standard files for the source itself, but I then decided to simplify into a single set that would work for both situations.
>> 
>> So I guess the question is this: is this an acceptable approach or not?
>> 
>> -chip
>> 
>>> On Oct 22, 2012, at 12:16 PM, Chip Childers (ASF) <ch...@apache.org> wrote:
>>> 
>>>> Hi All,
>>>> 
>>>> I would like to call a vote for Apache CloudStack (Incubating) 
>>>> Release 4.0.0-incubating (third round).
>>>> 
>>>> We encourage the whole community to download and test these release 
>>>> artifacts, so that any critical issues can be resolved before the 
>>>> release is made. The more time that each individual spends reviewing 
>>>> the artifacts, the higher confidence we can have in both the release 
>>>> itself and our ability to pass an IPMC vote later on.  Everyone is 
>>>> free to vote on this release, so please give it a shot.
>>>> 
>>>> Instructions for Validating and Testing the artifacts can be found here:
>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.
>>>> 0
>>>> +test+procedure
>>>> 
>>>> If you have any trouble setting up a test environment using the 
>>>> procedure above, please ask on the cloudstack-dev@i.a.o list.
>>>> Someone will be sure to help, and we'll improve our test procedure 
>>>> documentation at the same time!
>>>> 
>>>> Now, on to the specifics of what we are voting on...
>>>> 
>>>> 
>>>> The following artifacts are up for the vote:
>>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.
>>>> 0
>>>> -incubating/
>>>> 
>>>> PGP release keys (signed using A99A5D58):
>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>> 
>>>> Branch: 4.0
>>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>> 
>>>> 
>>>> List of changes:
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a
>>>> =
>>>> blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>> 
>>>> The artifacts being voted on during this round also include the 
>>>> following additional fixes (most were identified as part of testing 
>>>> during the last round of voting):
>>>> 
>>>> * Many documentation fixes (particularly the release notes and 
>>>> installation guide)
>>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on 
>>>> the UI
>>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>>> * Correction to the devcloud rdeploy build target, to make testing 
>>>> easier
>>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build 
>>>> will fail
>>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>>> * DISCLAIMER added to the Marvin tool dir
>>>> 
>>>> 
>>>> The vote will be open for 72 hours.
>>>> 
>>>> 
>>>> For sanity in tallying the vote, can PPMC and IPMC members please be 
>>>> sure to indicate "(binding)" with their vote?
>>>> [ ] +1  approve
>>>> [ ] +0  no opinion
>>>> [ ] -1  disapprove (and reason why)
>>>> 
>>>> Thanks!
>>> 
>>> --
>>> Daniel Kulp
>>> dkulp@apache.org - http://dankulp.com/blog Talend Community Coder - 
>>> http://coders.talend.com
>>> 
>>>

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Suresh Sadhu <Su...@citrix.com>.
+1

 Followed the test procedure mentioned  in the specified link (https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure) and performed below operations:

.VM life cycle(VM create/stop/destroy/expunge)
Add volume/detach volume
Add an account

Thanks
sadhu

-----Original Message-----
From: Marcus Sorensen [mailto:shadowsor@gmail.com] 
Sent: 25 October 2012 10:00
To: cloudstack-dev@incubator.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

+1  Installed on KVM guest with local storage. Ran through a simple
zone creation. Installed a template. Launched a VPC, started up two tiers, some virtual machines, created some ACLs, a load balancer.
Checked password script/server was working. Deleted VMs, networks, VPC.

On Wed, Oct 24, 2012 at 9:06 PM, Chandan Purushothama <Ch...@citrix.com> wrote:
> +1
>
> I followed the test procedure mentioned at https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure . The local machine on which I deployed the DevCloud VM is freshly deployed Ubuntu 12.04-Server x86_64 host.
>
> Downloaded the following artifacts:
>
> wget http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> wget 
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
> wget 
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
> wget 
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5
> wget 
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha
>
> Verified signatures and hash files using "gpg --verify 
> apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc " -> "Good 
> Signature" mentioned in the returned output
>
> Compared the contents of the release artifact with the contents pulled 
> from the repo. No difference was observed
>
> Verified the Code's License Headers
> **Suggestion: Better to add the note "If you're on Ubuntu and using the PPA:natecarlson/maven3 (viz. Installing tools above), you've to use mvn3 instead of mvn" in this section of the test procedure.
>
> Complied the source code successfully. Deployed it into the DevCloud VM. Started and configured the Management Server successfully using the configuration instructions given in the test procedure.
>
> Secondary Storage VM and Console Proxy VM got deployed after 
> configuration of the management server. Successfully deployed the 
> first VM
>
> Changed the global settings of "expunge.interval" and "expunge.delay" to 120. Configured "enable.ec2.api" to "true"
>
> On clicking the console view of the deployed User VM using the "show console" button, Console view of the User VM appeared. Stopped the User VM using the Stop button on the UI. Destroyed the Stopped VM using the destroy button on the UI. Observed the VM expunge after 2 minutes.
>
> EC2 Testing:
>
> Generated the API and Secret key for the admin account. I renamed the  tinyOffering to m1.small as instructed in the test procedure. Added a rule on the Virtual box to forward host port 7080 TCP traffic to VM's port 7080. After generating a X509 SSL certificate on the local machine, I used it and successfully registered the Admin account's api and secret key on the devCloud's Management Server's cloudbridge database. I verified the presence of the API and Secret key  of admin account in the "usercredentials"  table in the "cloudbridge" database.
>
> Used the python script example given in the test procedure. Substituted the api and secret key in the script with those of the admin account. Successfully deployed a VM on the DevCloud Setup using the python script. I destroyed the instance via the UI and used the script two more times to deploy two more VMs on the devCloud Setup. The Two VMs got deployed Successfully.
>
> **Note:  I encountered a problem with deploying my first VM during my first attempt. This is due to my mistake where I overlooked the requirement to change the memory required for DevCloud VM from 1024 to 2046MB. I repeated the entire test procedure(except the pre-requisites)  the second time and made the above mentioned observations.
>
> Thank you,
> Chandan.
>
>
>
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Wednesday, October 24, 2012 11:11 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third 
> round
>
> On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote:
>>
>> I'm a bit confused by the LICENSE and NOTICE files that are in the root of the package.
>>
>> They seem to be LICENSE/NOTICE files that would be good for a binary distribution of Cloudstack built from this package, but don't really apply to this package.  Or maybe they were from before the dep jars were changed to be grabbed via maven and were part of the src.    Right?
>>
>> The license file lists license for jars in lib and aws and such that don't exist.   Likewise for the NOTICE file.
>>
>> Don't get me wrong.  I think these LICENSE/NOTICE files are great to have for people that are building binary distributions of Cloudstack and having that information available to them certainly takes much of the burden off of them, but I do question if they are appropriate for the Apache source based releases.
>>
>>
>> Dan
>
> Dan,
>
> Yes, the jars referenced in the legal docs are pulled in by the packaging process.  The expectation was that the material would be brought into any packaging (including the non-asf, but community provided, deb/rpm's).  When looking for examples from other ASF projects, IIRC I saw both approaches (I'll have to dig a bit to find the examples that I was looking at).  At one point, I had a "*_BINARY"
> version of both files and the standard files for the source itself, but I then decided to simplify into a single set that would work for both situations.
>
> So I guess the question is this: is this an acceptable approach or not?
>
> -chip
>
>> On Oct 22, 2012, at 12:16 PM, Chip Childers (ASF) <ch...@apache.org> wrote:
>>
>>> Hi All,
>>>
>>> I would like to call a vote for Apache CloudStack (Incubating) 
>>> Release 4.0.0-incubating (third round).
>>>
>>> We encourage the whole community to download and test these release 
>>> artifacts, so that any critical issues can be resolved before the 
>>> release is made. The more time that each individual spends reviewing 
>>> the artifacts, the higher confidence we can have in both the release 
>>> itself and our ability to pass an IPMC vote later on.  Everyone is 
>>> free to vote on this release, so please give it a shot.
>>>
>>> Instructions for Validating and Testing the artifacts can be found here:
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.
>>> 0
>>> +test+procedure
>>>
>>> If you have any trouble setting up a test environment using the 
>>> procedure above, please ask on the cloudstack-dev@i.a.o list.
>>> Someone will be sure to help, and we'll improve our test procedure 
>>> documentation at the same time!
>>>
>>> Now, on to the specifics of what we are voting on...
>>>
>>>
>>> The following artifacts are up for the vote:
>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.
>>> 0
>>> -incubating/
>>>
>>> PGP release keys (signed using A99A5D58):
>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>
>>> Branch: 4.0
>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>
>>>
>>> List of changes:
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a
>>> =
>>> blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>
>>> The artifacts being voted on during this round also include the 
>>> following additional fixes (most were identified as part of testing 
>>> during the last round of voting):
>>>
>>> * Many documentation fixes (particularly the release notes and 
>>> installation guide)
>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on 
>>> the UI
>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>> * Correction to the devcloud rdeploy build target, to make testing 
>>> easier
>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build 
>>> will fail
>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>> * DISCLAIMER added to the Marvin tool dir
>>>
>>>
>>> The vote will be open for 72 hours.
>>>
>>>
>>> For sanity in tallying the vote, can PPMC and IPMC members please be 
>>> sure to indicate "(binding)" with their vote?
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>>
>>> Thanks!
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog Talend Community Coder - 
>> http://coders.talend.com
>>
>>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Marcus Sorensen <sh...@gmail.com>.
+1  Installed on KVM guest with local storage. Ran through a simple
zone creation. Installed a template. Launched a VPC, started up two
tiers, some virtual machines, created some ACLs, a load balancer.
Checked password script/server was working. Deleted VMs, networks,
VPC.

On Wed, Oct 24, 2012 at 9:06 PM, Chandan Purushothama
<Ch...@citrix.com> wrote:
> +1
>
> I followed the test procedure mentioned at https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure . The local machine on which I deployed the DevCloud VM is freshly deployed Ubuntu 12.04-Server x86_64 host.
>
> Downloaded the following artifacts:
>
> wget http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
> wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
> wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5
> wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha
>
> Verified signatures and hash files using "gpg --verify apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc " -> "Good Signature" mentioned in the returned output
>
> Compared the contents of the release artifact with the contents pulled from the repo. No difference was observed
>
> Verified the Code's License Headers
> **Suggestion: Better to add the note "If you're on Ubuntu and using the PPA:natecarlson/maven3 (viz. Installing tools above), you've to use mvn3 instead of mvn" in this section of the test procedure.
>
> Complied the source code successfully. Deployed it into the DevCloud VM. Started and configured the Management Server successfully using the configuration instructions given in the test procedure.
>
> Secondary Storage VM and Console Proxy VM got deployed after configuration of the management server. Successfully deployed the first VM
>
> Changed the global settings of "expunge.interval" and "expunge.delay" to 120. Configured "enable.ec2.api" to "true"
>
> On clicking the console view of the deployed User VM using the "show console" button, Console view of the User VM appeared. Stopped the User VM using the Stop button on the UI. Destroyed the Stopped VM using the destroy button on the UI. Observed the VM expunge after 2 minutes.
>
> EC2 Testing:
>
> Generated the API and Secret key for the admin account. I renamed the  tinyOffering to m1.small as instructed in the test procedure. Added a rule on the Virtual box to forward host port 7080 TCP traffic to VM's port 7080. After generating a X509 SSL certificate on the local machine, I used it and successfully registered the Admin account's api and secret key on the devCloud's Management Server's cloudbridge database. I verified the presence of the API and Secret key  of admin account in the "usercredentials"  table in the "cloudbridge" database.
>
> Used the python script example given in the test procedure. Substituted the api and secret key in the script with those of the admin account. Successfully deployed a VM on the DevCloud Setup using the python script. I destroyed the instance via the UI and used the script two more times to deploy two more VMs on the devCloud Setup. The Two VMs got deployed Successfully.
>
> **Note:  I encountered a problem with deploying my first VM during my first attempt. This is due to my mistake where I overlooked the requirement to change the memory required for DevCloud VM from 1024 to 2046MB. I repeated the entire test procedure(except the pre-requisites)  the second time and made the above mentioned observations.
>
> Thank you,
> Chandan.
>
>
>
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Wednesday, October 24, 2012 11:11 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
>
> On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote:
>>
>> I'm a bit confused by the LICENSE and NOTICE files that are in the root of the package.
>>
>> They seem to be LICENSE/NOTICE files that would be good for a binary distribution of Cloudstack built from this package, but don't really apply to this package.  Or maybe they were from before the dep jars were changed to be grabbed via maven and were part of the src.    Right?
>>
>> The license file lists license for jars in lib and aws and such that don't exist.   Likewise for the NOTICE file.
>>
>> Don't get me wrong.  I think these LICENSE/NOTICE files are great to have for people that are building binary distributions of Cloudstack and having that information available to them certainly takes much of the burden off of them, but I do question if they are appropriate for the Apache source based releases.
>>
>>
>> Dan
>
> Dan,
>
> Yes, the jars referenced in the legal docs are pulled in by the packaging process.  The expectation was that the material would be brought into any packaging (including the non-asf, but community provided, deb/rpm's).  When looking for examples from other ASF projects, IIRC I saw both approaches (I'll have to dig a bit to find the examples that I was looking at).  At one point, I had a "*_BINARY"
> version of both files and the standard files for the source itself, but I then decided to simplify into a single set that would work for both situations.
>
> So I guess the question is this: is this an acceptable approach or not?
>
> -chip
>
>> On Oct 22, 2012, at 12:16 PM, Chip Childers (ASF) <ch...@apache.org> wrote:
>>
>>> Hi All,
>>>
>>> I would like to call a vote for Apache CloudStack (Incubating)
>>> Release 4.0.0-incubating (third round).
>>>
>>> We encourage the whole community to download and test these release
>>> artifacts, so that any critical issues can be resolved before the
>>> release is made. The more time that each individual spends reviewing
>>> the artifacts, the higher confidence we can have in both the release
>>> itself and our ability to pass an IPMC vote later on.  Everyone is
>>> free to vote on this release, so please give it a shot.
>>>
>>> Instructions for Validating and Testing the artifacts can be found here:
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0
>>> +test+procedure
>>>
>>> If you have any trouble setting up a test environment using the
>>> procedure above, please ask on the cloudstack-dev@i.a.o list.
>>> Someone will be sure to help, and we'll improve our test procedure
>>> documentation at the same time!
>>>
>>> Now, on to the specifics of what we are voting on...
>>>
>>>
>>> The following artifacts are up for the vote:
>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0
>>> -incubating/
>>>
>>> PGP release keys (signed using A99A5D58):
>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>
>>> Branch: 4.0
>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>
>>>
>>> List of changes:
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=
>>> blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>
>>> The artifacts being voted on during this round also include the
>>> following additional fixes (most were identified as part of testing
>>> during the last round of voting):
>>>
>>> * Many documentation fixes (particularly the release notes and
>>> installation guide)
>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on
>>> the UI
>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>> * Correction to the devcloud rdeploy build target, to make testing
>>> easier
>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
>>> will fail
>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>> * DISCLAIMER added to the Marvin tool dir
>>>
>>>
>>> The vote will be open for 72 hours.
>>>
>>>
>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>> sure to indicate "(binding)" with their vote?
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>>
>>> Thanks!
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog Talend Community Coder -
>> http://coders.talend.com
>>
>>

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chandan Purushothama <Ch...@citrix.com>.
+1

I followed the test procedure mentioned at https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure . The local machine on which I deployed the DevCloud VM is freshly deployed Ubuntu 12.04-Server x86_64 host.

Downloaded the following artifacts:

wget http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2
wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc
wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.md5
wget http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/apache-cloudstack-4.0.0-incubating-src.tar.bz2.sha

Verified signatures and hash files using "gpg --verify apache-cloudstack-4.0.0-incubating-src.tar.bz2.asc " -> "Good Signature" mentioned in the returned output

Compared the contents of the release artifact with the contents pulled from the repo. No difference was observed

Verified the Code's License Headers
**Suggestion: Better to add the note "If you're on Ubuntu and using the PPA:natecarlson/maven3 (viz. Installing tools above), you've to use mvn3 instead of mvn" in this section of the test procedure.

Complied the source code successfully. Deployed it into the DevCloud VM. Started and configured the Management Server successfully using the configuration instructions given in the test procedure.

Secondary Storage VM and Console Proxy VM got deployed after configuration of the management server. Successfully deployed the first VM

Changed the global settings of "expunge.interval" and "expunge.delay" to 120. Configured "enable.ec2.api" to "true"

On clicking the console view of the deployed User VM using the "show console" button, Console view of the User VM appeared. Stopped the User VM using the Stop button on the UI. Destroyed the Stopped VM using the destroy button on the UI. Observed the VM expunge after 2 minutes.

EC2 Testing:

Generated the API and Secret key for the admin account. I renamed the  tinyOffering to m1.small as instructed in the test procedure. Added a rule on the Virtual box to forward host port 7080 TCP traffic to VM's port 7080. After generating a X509 SSL certificate on the local machine, I used it and successfully registered the Admin account's api and secret key on the devCloud's Management Server's cloudbridge database. I verified the presence of the API and Secret key  of admin account in the "usercredentials"  table in the "cloudbridge" database.

Used the python script example given in the test procedure. Substituted the api and secret key in the script with those of the admin account. Successfully deployed a VM on the DevCloud Setup using the python script. I destroyed the instance via the UI and used the script two more times to deploy two more VMs on the devCloud Setup. The Two VMs got deployed Successfully.

**Note:  I encountered a problem with deploying my first VM during my first attempt. This is due to my mistake where I overlooked the requirement to change the memory required for DevCloud VM from 1024 to 2046MB. I repeated the entire test procedure(except the pre-requisites)  the second time and made the above mentioned observations.

Thank you,
Chandan. 



-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com] 
Sent: Wednesday, October 24, 2012 11:11 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> I'm a bit confused by the LICENSE and NOTICE files that are in the root of the package.
>
> They seem to be LICENSE/NOTICE files that would be good for a binary distribution of Cloudstack built from this package, but don't really apply to this package.  Or maybe they were from before the dep jars were changed to be grabbed via maven and were part of the src.    Right?
>
> The license file lists license for jars in lib and aws and such that don't exist.   Likewise for the NOTICE file.
>
> Don't get me wrong.  I think these LICENSE/NOTICE files are great to have for people that are building binary distributions of Cloudstack and having that information available to them certainly takes much of the burden off of them, but I do question if they are appropriate for the Apache source based releases.
>
>
> Dan

Dan,

Yes, the jars referenced in the legal docs are pulled in by the packaging process.  The expectation was that the material would be brought into any packaging (including the non-asf, but community provided, deb/rpm's).  When looking for examples from other ASF projects, IIRC I saw both approaches (I'll have to dig a bit to find the examples that I was looking at).  At one point, I had a "*_BINARY"
version of both files and the standard files for the source itself, but I then decided to simplify into a single set that would work for both situations.

So I guess the question is this: is this an acceptable approach or not?

-chip

> On Oct 22, 2012, at 12:16 PM, Chip Childers (ASF) <ch...@apache.org> wrote:
>
>> Hi All,
>>
>> I would like to call a vote for Apache CloudStack (Incubating) 
>> Release 4.0.0-incubating (third round).
>>
>> We encourage the whole community to download and test these release 
>> artifacts, so that any critical issues can be resolved before the 
>> release is made. The more time that each individual spends reviewing 
>> the artifacts, the higher confidence we can have in both the release 
>> itself and our ability to pass an IPMC vote later on.  Everyone is 
>> free to vote on this release, so please give it a shot.
>>
>> Instructions for Validating and Testing the artifacts can be found here:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0
>> +test+procedure
>>
>> If you have any trouble setting up a test environment using the 
>> procedure above, please ask on the cloudstack-dev@i.a.o list.  
>> Someone will be sure to help, and we'll improve our test procedure 
>> documentation at the same time!
>>
>> Now, on to the specifics of what we are voting on...
>>
>>
>> The following artifacts are up for the vote:
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0
>> -incubating/
>>
>> PGP release keys (signed using A99A5D58):
>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>
>> Branch: 4.0
>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>
>>
>> List of changes:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=
>> blob_plain;f=CHANGES;hb=refs/heads/4.0
>>
>> The artifacts being voted on during this round also include the 
>> following additional fixes (most were identified as part of testing 
>> during the last round of voting):
>>
>> * Many documentation fixes (particularly the release notes and 
>> installation guide)
>> * CLOUDSTACK-341: Failing to display Management Traffic Details on 
>> the UI
>> * CLOUDSTACK-349: Russian l10n not properly displaying
>> * Correction to the devcloud rdeploy build target, to make testing 
>> easier
>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build 
>> will fail
>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>> * DISCLAIMER added to the Marvin tool dir
>>
>>
>> The vote will be open for 72 hours.
>>
>>
>> For sanity in tallying the vote, can PPMC and IPMC members please be 
>> sure to indicate "(binding)" with their vote?
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Thanks!
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog Talend Community Coder - 
> http://coders.talend.com
>
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Thu, Oct 25, 2012 at 9:08 AM, Brett Porter <br...@apache.org> wrote:
>
> On 25/10/2012, at 5:11 AM, Chip Childers <ch...@sungard.com> wrote:
>
>> On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote:
>>>
>>> I'm a bit confused by the LICENSE and NOTICE files that are in the root of the package.
>>>
>>> They seem to be LICENSE/NOTICE files that would be good for a binary distribution of Cloudstack built from this package, but don't really apply to this package.  Or maybe they were from before the dep jars were changed to be grabbed via maven and were part of the src.    Right?
>>>
>>> The license file lists license for jars in lib and aws and such that don't exist.   Likewise for the NOTICE file.
>>>
>>> Don't get me wrong.  I think these LICENSE/NOTICE files are great to have for people that are building binary distributions of Cloudstack and having that information available to them certainly takes much of the burden off of them, but I do question if they are appropriate for the Apache source based releases.
>>>
>>>
>>> Dan
>>
>> Dan,
>>
>> Yes, the jars referenced in the legal docs are pulled in by the
>> packaging process.  The expectation was that the material would be
>> brought into any packaging (including the non-asf, but community
>> provided, deb/rpm's).  When looking for examples from other ASF
>> projects, IIRC I saw both approaches (I'll have to dig a bit to find
>> the examples that I was looking at).  At one point, I had a "*_BINARY"
>> version of both files and the standard files for the source itself,
>> but I then decided to simplify into a single set that would work for
>> both situations.
>>
>> So I guess the question is this: is this an acceptable approach or not?
>
> I don't see a problem with this - someone building the source is going to have to accept the licenses of those non-optional dependencies too since they'll get dragged down automatically. Perhaps the files could have a separator indicating the following apply only to binaries built from the sources in future releases?

Good idea Brett.  Now if only I could get folks to respond to my first
Apache Whisker bug [1]...  then I'd be willing to add more features to
Whisker for stuff like this. ;-)  I really don't want to stop using
Whisker, since it makes maintenance much easier.

[1] http://mail-archives.apache.org/mod_mbox/creadur-dev/201210.mbox/%3CCA%2B96GG5Pg9YfqiBL9WaGkG2kBf_1bD5MxFG1Tbnh1via4woOKA%40mail.gmail.com%3E

> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Thu, Oct 25, 2012 at 1:01 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On Oct 25, 2012, at 9:08 AM, Brett Porter <br...@apache.org> wrote:
>
>>
>> On 25/10/2012, at 5:11 AM, Chip Childers <ch...@sungard.com> wrote:
>>
>>> Yes, the jars referenced in the legal docs are pulled in by the
>>> packaging process.  The expectation was that the material would be
>>> brought into any packaging (including the non-asf, but community
>>> provided, deb/rpm's).  When looking for examples from other ASF
>>> projects, IIRC I saw both approaches (I'll have to dig a bit to find
>>> the examples that I was looking at).  At one point, I had a "*_BINARY"
>>> version of both files and the standard files for the source itself,
>>> but I then decided to simplify into a single set that would work for
>>> both situations.
>>>
>>> So I guess the question is this: is this an acceptable approach or not?
>>
>> I don't see a problem with this - someone building the source is going to have to accept the licenses of those non-optional dependencies too since they'll get dragged down automatically. Perhaps the files could have a separator indicating the following apply only to binaries built from the sources in future releases?
>>
>
> Yep.  I agree with this.   Nothing to hold up this release, but a bit of room for improvement for the next release.   :-)
>
>
> Anyway, other than the above, everything looks fine to me.   So here is my +1.
>
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>

Thanks for the suggestions Daniel / Brett.  We'll make that
improvement for the next time.

-chip

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Rajesh Battala <ra...@citrix.com>.
+1
Verified Basic VM Operations using Dev Cloud on VB.

Thanks
Rajesh Battala

-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org] 
Sent: Thursday, October 25, 2012 10:32 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round


On Oct 25, 2012, at 9:08 AM, Brett Porter <br...@apache.org> wrote:

> 
> On 25/10/2012, at 5:11 AM, Chip Childers <ch...@sungard.com> wrote:
> 
>> Yes, the jars referenced in the legal docs are pulled in by the 
>> packaging process.  The expectation was that the material would be 
>> brought into any packaging (including the non-asf, but community 
>> provided, deb/rpm's).  When looking for examples from other ASF 
>> projects, IIRC I saw both approaches (I'll have to dig a bit to find 
>> the examples that I was looking at).  At one point, I had a "*_BINARY"
>> version of both files and the standard files for the source itself, 
>> but I then decided to simplify into a single set that would work for 
>> both situations.
>> 
>> So I guess the question is this: is this an acceptable approach or not?
> 
> I don't see a problem with this - someone building the source is going to have to accept the licenses of those non-optional dependencies too since they'll get dragged down automatically. Perhaps the files could have a separator indicating the following apply only to binaries built from the sources in future releases?
> 

Yep.  I agree with this.   Nothing to hold up this release, but a bit of room for improvement for the next release.   :-)


Anyway, other than the above, everything looks fine to me.   So here is my +1.


--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Daniel Kulp <dk...@apache.org>.
On Oct 25, 2012, at 9:08 AM, Brett Porter <br...@apache.org> wrote:

> 
> On 25/10/2012, at 5:11 AM, Chip Childers <ch...@sungard.com> wrote:
> 
>> Yes, the jars referenced in the legal docs are pulled in by the
>> packaging process.  The expectation was that the material would be
>> brought into any packaging (including the non-asf, but community
>> provided, deb/rpm's).  When looking for examples from other ASF
>> projects, IIRC I saw both approaches (I'll have to dig a bit to find
>> the examples that I was looking at).  At one point, I had a "*_BINARY"
>> version of both files and the standard files for the source itself,
>> but I then decided to simplify into a single set that would work for
>> both situations.
>> 
>> So I guess the question is this: is this an acceptable approach or not?
> 
> I don't see a problem with this - someone building the source is going to have to accept the licenses of those non-optional dependencies too since they'll get dragged down automatically. Perhaps the files could have a separator indicating the following apply only to binaries built from the sources in future releases?
> 

Yep.  I agree with this.   Nothing to hold up this release, but a bit of room for improvement for the next release.   :-)


Anyway, other than the above, everything looks fine to me.   So here is my +1.


-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Brett Porter <br...@apache.org>.
On 25/10/2012, at 5:11 AM, Chip Childers <ch...@sungard.com> wrote:

> On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote:
>> 
>> I'm a bit confused by the LICENSE and NOTICE files that are in the root of the package.
>> 
>> They seem to be LICENSE/NOTICE files that would be good for a binary distribution of Cloudstack built from this package, but don't really apply to this package.  Or maybe they were from before the dep jars were changed to be grabbed via maven and were part of the src.    Right?
>> 
>> The license file lists license for jars in lib and aws and such that don't exist.   Likewise for the NOTICE file.
>> 
>> Don't get me wrong.  I think these LICENSE/NOTICE files are great to have for people that are building binary distributions of Cloudstack and having that information available to them certainly takes much of the burden off of them, but I do question if they are appropriate for the Apache source based releases.
>> 
>> 
>> Dan
> 
> Dan,
> 
> Yes, the jars referenced in the legal docs are pulled in by the
> packaging process.  The expectation was that the material would be
> brought into any packaging (including the non-asf, but community
> provided, deb/rpm's).  When looking for examples from other ASF
> projects, IIRC I saw both approaches (I'll have to dig a bit to find
> the examples that I was looking at).  At one point, I had a "*_BINARY"
> version of both files and the standard files for the source itself,
> but I then decided to simplify into a single set that would work for
> both situations.
> 
> So I guess the question is this: is this an acceptable approach or not?

I don't see a problem with this - someone building the source is going to have to accept the licenses of those non-optional dependencies too since they'll get dragged down automatically. Perhaps the files could have a separator indicating the following apply only to binaries built from the sources in future releases?

- Brett

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Wed, Oct 24, 2012 at 2:02 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> I'm a bit confused by the LICENSE and NOTICE files that are in the root of the package.
>
> They seem to be LICENSE/NOTICE files that would be good for a binary distribution of Cloudstack built from this package, but don't really apply to this package.  Or maybe they were from before the dep jars were changed to be grabbed via maven and were part of the src.    Right?
>
> The license file lists license for jars in lib and aws and such that don't exist.   Likewise for the NOTICE file.
>
> Don't get me wrong.  I think these LICENSE/NOTICE files are great to have for people that are building binary distributions of Cloudstack and having that information available to them certainly takes much of the burden off of them, but I do question if they are appropriate for the Apache source based releases.
>
>
> Dan

Dan,

Yes, the jars referenced in the legal docs are pulled in by the
packaging process.  The expectation was that the material would be
brought into any packaging (including the non-asf, but community
provided, deb/rpm's).  When looking for examples from other ASF
projects, IIRC I saw both approaches (I'll have to dig a bit to find
the examples that I was looking at).  At one point, I had a "*_BINARY"
version of both files and the standard files for the source itself,
but I then decided to simplify into a single set that would work for
both situations.

So I guess the question is this: is this an acceptable approach or not?

-chip

> On Oct 22, 2012, at 12:16 PM, Chip Childers (ASF) <ch...@apache.org> wrote:
>
>> Hi All,
>>
>> I would like to call a vote for Apache CloudStack (Incubating) Release
>> 4.0.0-incubating (third round).
>>
>> We encourage the whole community to download and test these release
>> artifacts, so that any critical issues can be resolved before the
>> release is made. The more time that each individual spends reviewing
>> the artifacts, the higher confidence we can have in both the release
>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>> to vote on this release, so please give it a shot.
>>
>> Instructions for Validating and Testing the artifacts can be found here:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>
>> If you have any trouble setting up a test environment using the
>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>> will be sure to help, and we'll improve our test procedure
>> documentation at the same time!
>>
>> Now, on to the specifics of what we are voting on...
>>
>>
>> The following artifacts are up for the vote:
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>
>> PGP release keys (signed using A99A5D58):
>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>
>> Branch: 4.0
>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>
>>
>> List of changes:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>
>> The artifacts being voted on during this round also include the
>> following additional fixes (most were identified as part of testing
>> during the last round of voting):
>>
>> * Many documentation fixes (particularly the release notes and
>> installation guide)
>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>> * CLOUDSTACK-349: Russian l10n not properly displaying
>> * Correction to the devcloud rdeploy build target, to make testing easier
>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>> * DISCLAIMER added to the Marvin tool dir
>>
>>
>> The vote will be open for 72 hours.
>>
>>
>> For sanity in tallying the vote, can PPMC and IPMC members please be
>> sure to indicate "(binding)" with their vote?
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Thanks!
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Daniel Kulp <dk...@apache.org>.
I'm a bit confused by the LICENSE and NOTICE files that are in the root of the package.

They seem to be LICENSE/NOTICE files that would be good for a binary distribution of Cloudstack built from this package, but don't really apply to this package.  Or maybe they were from before the dep jars were changed to be grabbed via maven and were part of the src.    Right?

The license file lists license for jars in lib and aws and such that don't exist.   Likewise for the NOTICE file.  

Don't get me wrong.  I think these LICENSE/NOTICE files are great to have for people that are building binary distributions of Cloudstack and having that information available to them certainly takes much of the burden off of them, but I do question if they are appropriate for the Apache source based releases.


Dan


On Oct 22, 2012, at 12:16 PM, Chip Childers (ASF) <ch...@apache.org> wrote:

> Hi All,
> 
> I would like to call a vote for Apache CloudStack (Incubating) Release
> 4.0.0-incubating (third round).
> 
> We encourage the whole community to download and test these release
> artifacts, so that any critical issues can be resolved before the
> release is made. The more time that each individual spends reviewing
> the artifacts, the higher confidence we can have in both the release
> itself and our ability to pass an IPMC vote later on.  Everyone is free
> to vote on this release, so please give it a shot.
> 
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
> 
> If you have any trouble setting up a test environment using the
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
> will be sure to help, and we'll improve our test procedure
> documentation at the same time!
> 
> Now, on to the specifics of what we are voting on...
> 
> 
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
> 
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> 
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> 
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
> 
> The artifacts being voted on during this round also include the
> following additional fixes (most were identified as part of testing
> during the last round of voting):
> 
> * Many documentation fixes (particularly the release notes and
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
> 
> 
> The vote will be open for 72 hours.
> 
> 
> For sanity in tallying the vote, can PPMC and IPMC members please be
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Thanks!

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Jim Jagielski <ji...@jaguNET.com>.
Looks good here.

+1 [binding]

On Oct 23, 2012, at 7:53 AM, Sailaja Mada <sa...@citrix.com> wrote:

> Hi,
> 
> Rhel 6.3 oss build [CloudStack-oss-4.0.0-869.tar] is used for validation with Xenserver 6.0.2 .
> 
> Validated Scenario: VM life cycle operations on Advanced and Basic Zone .
> 
> My vote is +1 .
> 
> Thanks and Regards,
> Sailaja.M 
> 
> 
> -----Original Message-----
> From: chip.childers@sungard.com [mailto:chip.childers@sungard.com] On Behalf Of Chip Childers (ASF)
> Sent: Monday, October 22, 2012 9:46 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> Hi All,
> 
> I would like to call a vote for Apache CloudStack (Incubating) Release 4.0.0-incubating (third round).
> 
> We encourage the whole community to download and test these release artifacts, so that any critical issues can be resolved before the release is made. The more time that each individual spends reviewing the artifacts, the higher confidence we can have in both the release itself and our ability to pass an IPMC vote later on.  Everyone is free to vote on this release, so please give it a shot.
> 
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
> 
> If you have any trouble setting up a test environment using the procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone will be sure to help, and we'll improve our test procedure documentation at the same time!
> 
> Now, on to the specifics of what we are voting on...
> 
> 
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
> 
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> 
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> 
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
> 
> The artifacts being voted on during this round also include the following additional fixes (most were identified as part of testing during the last round of voting):
> 
> * Many documentation fixes (particularly the release notes and installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
> 
> 
> The vote will be open for 72 hours.
> 
> 
> For sanity in tallying the vote, can PPMC and IPMC members please be sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Thanks!
>

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Sailaja Mada <sa...@citrix.com>.
Hi,

Rhel 6.3 oss build [CloudStack-oss-4.0.0-869.tar] is used for validation with Xenserver 6.0.2 .

Validated Scenario: VM life cycle operations on Advanced and Basic Zone .

My vote is +1 .

Thanks and Regards,
Sailaja.M 


-----Original Message-----
From: chip.childers@sungard.com [mailto:chip.childers@sungard.com] On Behalf Of Chip Childers (ASF)
Sent: Monday, October 22, 2012 9:46 PM
To: cloudstack-dev@incubator.apache.org
Subject: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Hi All,

I would like to call a vote for Apache CloudStack (Incubating) Release 4.0.0-incubating (third round).

We encourage the whole community to download and test these release artifacts, so that any critical issues can be resolved before the release is made. The more time that each individual spends reviewing the artifacts, the higher confidence we can have in both the release itself and our ability to pass an IPMC vote later on.  Everyone is free to vote on this release, so please give it a shot.

Instructions for Validating and Testing the artifacts can be found here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure

If you have any trouble setting up a test environment using the procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone will be sure to help, and we'll improve our test procedure documentation at the same time!

Now, on to the specifics of what we are voting on...


The following artifacts are up for the vote:
http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/

PGP release keys (signed using A99A5D58):
http://people.apache.org/~chipchilders/dist/cloudstack/KEYS

Branch: 4.0
Commit: 6355965dcd956811dd471a9d03c73dadcf68f480


List of changes:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0

The artifacts being voted on during this round also include the following additional fixes (most were identified as part of testing during the last round of voting):

* Many documentation fixes (particularly the release notes and installation guide)
* CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
* CLOUDSTACK-349: Russian l10n not properly displaying
* Correction to the devcloud rdeploy build target, to make testing easier
* CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
* CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
* DISCLAIMER added to the Marvin tool dir


The vote will be open for 72 hours.


For sanity in tallying the vote, can PPMC and IPMC members please be sure to indicate "(binding)" with their vote?
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Thanks!

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Abhinav Roy <ab...@citrix.com>.
Hi,

Validated using Rhel 6.3 NON-OSS build with hypervisor  VMware 5.0 . 

Advanced Zone Configuration and  VM Life Cycle operations are validated using the build @ CloudStack-non-OSS-139.tar.bz2.

My vote is +1 .

Thanks and Regards,
Abhinav

-----Original Message-----
From: chip.childers@sungard.com [mailto:chip.childers@sungard.com] On Behalf Of Chip Childers (ASF)
Sent: Monday, October 22, 2012 9:46 PM
To: cloudstack-dev@incubator.apache.org
Subject: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Hi All,

I would like to call a vote for Apache CloudStack (Incubating) Release 4.0.0-incubating (third round).

We encourage the whole community to download and test these release artifacts, so that any critical issues can be resolved before the release is made. The more time that each individual spends reviewing the artifacts, the higher confidence we can have in both the release itself and our ability to pass an IPMC vote later on.  Everyone is free to vote on this release, so please give it a shot.

Instructions for Validating and Testing the artifacts can be found here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure

If you have any trouble setting up a test environment using the procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone will be sure to help, and we'll improve our test procedure documentation at the same time!

Now, on to the specifics of what we are voting on...


The following artifacts are up for the vote:
http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/

PGP release keys (signed using A99A5D58):
http://people.apache.org/~chipchilders/dist/cloudstack/KEYS

Branch: 4.0
Commit: 6355965dcd956811dd471a9d03c73dadcf68f480


List of changes:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0

The artifacts being voted on during this round also include the following additional fixes (most were identified as part of testing during the last round of voting):

* Many documentation fixes (particularly the release notes and installation guide)
* CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
* CLOUDSTACK-349: Russian l10n not properly displaying
* Correction to the devcloud rdeploy build target, to make testing easier
* CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
* CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
* DISCLAIMER added to the Marvin tool dir


The vote will be open for 72 hours.


For sanity in tallying the vote, can PPMC and IPMC members please be sure to indicate "(binding)" with their vote?
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Thanks!

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Wido den Hollander <wi...@widodh.nl>.
+1

I've done a couple of tests today, these include:
- Building from source
- Building Debian packages (Uploaded to cloudstack.apt-get.eu as well)
- Add RBD pool
- Remove RBD pool
- Deploy RBD instance from a template

I didn't repeat my complete test suite compared to the previous 
artifacts, I looked at the code changes and concluded that I didn't need 
to test everything over again.

All these tests succeeded like they should, so that is where my +1 is 
coming from.

Wido

On 10/22/2012 06:16 PM, Chip Childers (ASF) wrote:
> Hi All,
>
> I would like to call a vote for Apache CloudStack (Incubating) Release
> 4.0.0-incubating (third round).
>
> We encourage the whole community to download and test these release
> artifacts, so that any critical issues can be resolved before the
> release is made. The more time that each individual spends reviewing
> the artifacts, the higher confidence we can have in both the release
> itself and our ability to pass an IPMC vote later on.  Everyone is free
> to vote on this release, so please give it a shot.
>
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>
> If you have any trouble setting up a test environment using the
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
> will be sure to help, and we'll improve our test procedure
> documentation at the same time!
>
> Now, on to the specifics of what we are voting on...
>
>
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>
>
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>
> The artifacts being voted on during this round also include the
> following additional fixes (most were identified as part of testing
> during the last round of voting):
>
> * Many documentation fixes (particularly the release notes and
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
>
>
> The vote will be open for 72 hours.
>
>
> For sanity in tallying the vote, can PPMC and IPMC members please be
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Thanks!
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Brett Porter <br...@apache.org>.
+1 (binding)

I have...
- checked the signature
- reviewed the license, notice, and other text files at the top of the tree
- reviewed the mvn dependency reports to check the list of dependencies used
- confirmed no binaries in the tree
- ran the mvn build
- ran the RAT check
- performed the steps in the test procedure to set up the management server

Excellent job, folks.

Regards,
Brett

On 23/10/2012, at 3:16 AM, Chip Childers (ASF) <ch...@apache.org> wrote:

> Hi All,
> 
> I would like to call a vote for Apache CloudStack (Incubating) Release
> 4.0.0-incubating (third round).
> 
> We encourage the whole community to download and test these release
> artifacts, so that any critical issues can be resolved before the
> release is made. The more time that each individual spends reviewing
> the artifacts, the higher confidence we can have in both the release
> itself and our ability to pass an IPMC vote later on.  Everyone is free
> to vote on this release, so please give it a shot.
> 
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
> 
> If you have any trouble setting up a test environment using the
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
> will be sure to help, and we'll improve our test procedure
> documentation at the same time!
> 
> Now, on to the specifics of what we are voting on...
> 
> 
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
> 
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> 
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> 
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
> 
> The artifacts being voted on during this round also include the
> following additional fixes (most were identified as part of testing
> during the last round of voting):
> 
> * Many documentation fixes (particularly the release notes and
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
> 
> 
> The vote will be open for 72 hours.
> 
> 
> For sanity in tallying the vote, can PPMC and IPMC members please be
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Thanks!

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by David Nalley <da...@gnsa.us>.
On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
<ch...@apache.org> wrote:
> Hi All,
>
> I would like to call a vote for Apache CloudStack (Incubating) Release
> 4.0.0-incubating (third round).
>

Signature is valid - (do wish there was more connection in the key,
but assume that will get solved over time)
Checksums are valid
There is no diff between git tree and the tarball.
RAT output looks good.
Builds, packages, and deploys successfully.
Deployed a 4 node instance and things work successfully.


+1 from me
Also happy to add my signature if you wish to use it.

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by "Musayev, Ilya" <im...@webmd.net>.
Kelven

Response in line..

Thanks
Ilya


On Oct 22, 2012, at 8:41 PM, "Kelven Yang" <ke...@citrix.com>> wrote:

Mussyev,

Please see my answers inline

Kelven

On 10/22/12 3:42 PM, "Musayev, Ilya" <im...@webmd.net>> wrote:

Test case 3 and 4 wording has been changed, see below.

On Oct 22, 2012, at 6:34 PM, "Musayev, Ilya" <im...@webmd.net>> wrote:

Following issues has been witnessed thus far:

I'm just going to provide the output of my tests and you be the judge
if it's bug or an error on my part - I can then submit a bug report if
needed.

1 - when configuring VMware ESXi environment initially primary store
cannot be set as VMFS and must be configured as NFS for setup to work. I
could not get VMFS to work as primary storage without adding NFS as
primary first. (need to confirm if VMFS will still works as primary -
post adding NFS as primary - as of now I just use NFS as primary storage)

We support VMFS as the primary storage, but configuration of using VMFS
and NFS is different. For NFS datastore, CloudStack will use information
provided by the user to explicitly create NFS datastore and mount it to
hosts within the cluster. For VMFS, we require VMFS datastore be
configured in vCenter ahead, it means that the VMFS datastore has been
setup in the vCenter datacenter and for all hosts within the cluster have
enabled the interface (for example, iScsi software adapter). Once VMFS
datastore has been setup correctly in vCenter, you should be able to add
it to CloudStack and use it as primary storage.

I'm not expecting for CS to magically create LUNs. Those LUNs have been configured, presented and used by all hypervisors in the cluster before CS setup was attempted. My apology I was not clear.




2 - if VMFS LUN is incorrectly set while going through initial setup
process (not using first time wizard - since VMware ESXi Cluster is not
an option) and user mistakenly enters improper LUN, the UI will detect
as an error but even if you correct it - there is no way to continue the
setup process and no API calls are issued to confirm the validity of the
new LUN name. at this point, I had to start over from scratch.

VMFS datastore is transport to CloudStack, we don't provide any API for
you to validate VMFS LUN configuration. All you have to make sure is that
under vCenter, the VMFS datastore is properly setup.

Yep, it's been properly setup and used for over a year. The LUN name was put incorrectly  i.e. VM-LUN1 vs VM-LUN-1 during CS setup. The UI setup process complained that I need to address the LUN Name issue when it attempted to configure the VMware cluster. Once I address the LUN name in UI setup process and press submit, it returns back and claims LUN name is incorrect. Except it occurs so quick - that I doubt it checked anything.

If it's still not clear, I will do screenshots or video. This seems more like UI/JS issue.





3. Don't know if this would-be a bug or feature enhacement. While
adding a vmware cluster - the CS is specifically looking for "Management
Network" port group on vSwitch0. If name does not match - you could see
an error that "Management Network" portgroup is not found. The prefered
logic  would be to lookup the portgroup of vmk0 (or whatever management
virtual NIC is) and use it as your portgroup.

Locking for "Management Network" port group on vSwitch0 is only the
default configuration, you can change this by properly configuring
following parameters

   vmware.private.vswitch: specify the vSwitch you want to use
       vmware.management.portgroup: for ESXi hosts, specify the
"management network"
       vmware.service.console: for ESX hosts, specify the "management
network"

This is awesome piece of information I was missing.

Thanks




4. If your VMware cluster has virtual switch vSwitch0 used for outbound
network communication and another vSwitch1 for other internal private
tasks with no outbound network connectivity - when the Secondary storage
VM is deployed it incorrectly picks vSwitch1 and attempts to use this
vswitch for communication with CS core. Obviously fails since no NICs
are connected to vSwitch1.

   Besides the global configuration, we also require the 'Physical network"
configuration of the traffic type under the zone to be correct. the
traffic type label is used to identify the vSwitch under Vmware.



5. This seems to have been the case for me all the time - but by
default -
the first time wizard does not have VMware cluster as an option. I
always to choose 'Skip, I've used cloud stack before' button.

6. If I attempt to do a complete cleanup without flushing DB, I'm
unable to delete physical network connection - eventhough no networks
are defined/assigned - and therefore I cannot delete the zone. I had to
drop mysql db and start fresh.

7. The cloud ssh and password scripts still need a bit more enhancement
- I will submit the patch shortly. I also think we can do more
improvements on the way code is written without changing functionality.

* None of these are show stoppers - but things I've noticed when I went
through install process. At the end, I was able to get it to work.

Let me know which are bugs and I will file a bug report with supporting
documentation.

I will go through install process once more next week or later this
week to double check and note all the issues. I will also be testing
Netscaler integration.

Regards
Ilya



On Oct 22, 2012, at 12:17 PM, "Chip Childers (ASF)"
<ch...@apache.org>> wrote:

Hi All,

I would like to call a vote for Apache CloudStack (Incubating) Release
4.0.0-incubating (third round).

We encourage the whole community to download and test these release
artifacts, so that any critical issues can be resolved before the
release is made. The more time that each individual spends reviewing
the artifacts, the higher confidence we can have in both the release
itself and our ability to pass an IPMC vote later on.  Everyone is free
to vote on this release, so please give it a shot.

Instructions for Validating and Testing the artifacts can be found
here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+te
st+procedure

If you have any trouble setting up a test environment using the
procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
will be sure to help, and we'll improve our test procedure
documentation at the same time!

Now, on to the specifics of what we are voting on...


The following artifacts are up for the vote:

http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-in
cubating/

PGP release keys (signed using A99A5D58):
http://people.apache.org/~chipchilders/dist/cloudstack/KEYS

Branch: 4.0
Commit: 6355965dcd956811dd471a9d03c73dadcf68f480


List of changes:

https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blo
b_plain;f=CHANGES;hb=refs/heads/4.0

The artifacts being voted on during this round also include the
following additional fixes (most were identified as part of testing
during the last round of voting):

* Many documentation fixes (particularly the release notes and
installation guide)
* CLOUDSTACK-341: Failing to display Management Traffic Details on the
UI
* CLOUDSTACK-349: Russian l10n not properly displaying
* Correction to the devcloud rdeploy build target, to make testing
easier
* CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
will fail
* CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
* DISCLAIMER added to the Marvin tool dir


The vote will be open for 72 hours.


For sanity in tallying the vote, can PPMC and IPMC members please be
sure to indicate "(binding)" with their vote?
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Thanks!

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Kelven Yang <ke...@citrix.com>.
Mussyev,

Please see my answers inline

Kelven

On 10/22/12 3:42 PM, "Musayev, Ilya" <im...@webmd.net> wrote:

>Test case 3 and 4 wording has been changed, see below.
>
>On Oct 22, 2012, at 6:34 PM, "Musayev, Ilya" <im...@webmd.net> wrote:
>
>> Following issues has been witnessed thus far:
>> 
>> I'm just going to provide the output of my tests and you be the judge
>>if it's bug or an error on my part - I can then submit a bug report if
>>needed.
>> 
>> 1 - when configuring VMware ESXi environment initially primary store
>>cannot be set as VMFS and must be configured as NFS for setup to work. I
>>could not get VMFS to work as primary storage without adding NFS as
>>primary first. (need to confirm if VMFS will still works as primary -
>>post adding NFS as primary - as of now I just use NFS as primary storage)

We support VMFS as the primary storage, but configuration of using VMFS
and NFS is different. For NFS datastore, CloudStack will use information
provided by the user to explicitly create NFS datastore and mount it to
hosts within the cluster. For VMFS, we require VMFS datastore be
configured in vCenter ahead, it means that the VMFS datastore has been
setup in the vCenter datacenter and for all hosts within the cluster have
enabled the interface (for example, iScsi software adapter). Once VMFS
datastore has been setup correctly in vCenter, you should be able to add
it to CloudStack and use it as primary storage.


>> 
>> 2 - if VMFS LUN is incorrectly set while going through initial setup
>>process (not using first time wizard - since VMware ESXi Cluster is not
>>an option) and user mistakenly enters improper LUN, the UI will detect
>>as an error but even if you correct it - there is no way to continue the
>>setup process and no API calls are issued to confirm the validity of the
>>new LUN name. at this point, I had to start over from scratch.

VMFS datastore is transport to CloudStack, we don't provide any API for
you to validate VMFS LUN configuration. All you have to make sure is that
under vCenter, the VMFS datastore is properly setup.



>> 
>> 3. Don't know if this would-be a bug or feature enhacement. While
>>adding a vmware cluster - the CS is specifically looking for "Management
>>Network" port group on vSwitch0. If name does not match - you could see
>>an error that "Management Network" portgroup is not found. The prefered
>>logic  would be to lookup the portgroup of vmk0 (or whatever management
>>virtual NIC is) and use it as your portgroup.

Locking for "Management Network" port group on vSwitch0 is only the
default configuration, you can change this by properly configuring
following parameters

	vmware.private.vswitch: specify the vSwitch you want to use
        vmware.management.portgroup: for ESXi hosts, specify the
"management network"
        vmware.service.console: for ESX hosts, specify the "management
network"


>> 
>> 4. If your VMware cluster has virtual switch vSwitch0 used for outbound
>>network communication and another vSwitch1 for other internal private
>>tasks with no outbound network connectivity - when the Secondary storage
>>VM is deployed it incorrectly picks vSwitch1 and attempts to use this
>>vswitch for communication with CS core. Obviously fails since no NICs
>>are connected to vSwitch1.

	Besides the global configuration, we also require the 'Physical network"
configuration of the traffic type under the zone to be correct. the
traffic type label is used to identify the vSwitch under Vmware.


>> 
>> 5. This seems to have been the case for me all the time - but by
>>default -
>>the first time wizard does not have VMware cluster as an option. I
>>always to choose 'Skip, I've used cloud stack before' button.
>> 
>> 6. If I attempt to do a complete cleanup without flushing DB, I'm
>>unable to delete physical network connection - eventhough no networks
>>are defined/assigned - and therefore I cannot delete the zone. I had to
>>drop mysql db and start fresh.
>> 
>> 7. The cloud ssh and password scripts still need a bit more enhancement
>>- I will submit the patch shortly. I also think we can do more
>>improvements on the way code is written without changing functionality.
>> 
>> * None of these are show stoppers - but things I've noticed when I went
>>through install process. At the end, I was able to get it to work.
>> 
>> Let me know which are bugs and I will file a bug report with supporting
>>documentation.
>> 
>> I will go through install process once more next week or later this
>>week to double check and note all the issues. I will also be testing
>>Netscaler integration.
>> 
>> Regards
>> Ilya
>> 
>> 
>> 
>> On Oct 22, 2012, at 12:17 PM, "Chip Childers (ASF)"
>><ch...@apache.org> wrote:
>> 
>>> Hi All,
>>> 
>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>> 4.0.0-incubating (third round).
>>> 
>>> We encourage the whole community to download and test these release
>>> artifacts, so that any critical issues can be resolved before the
>>> release is made. The more time that each individual spends reviewing
>>> the artifacts, the higher confidence we can have in both the release
>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>> to vote on this release, so please give it a shot.
>>> 
>>> Instructions for Validating and Testing the artifacts can be found
>>>here:
>>> 
>>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+te
>>>st+procedure
>>> 
>>> If you have any trouble setting up a test environment using the
>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>> will be sure to help, and we'll improve our test procedure
>>> documentation at the same time!
>>> 
>>> Now, on to the specifics of what we are voting on...
>>> 
>>> 
>>> The following artifacts are up for the vote:
>>> 
>>>http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-in
>>>cubating/
>>> 
>>> PGP release keys (signed using A99A5D58):
>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>> 
>>> Branch: 4.0
>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>> 
>>> 
>>> List of changes:
>>> 
>>>https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blo
>>>b_plain;f=CHANGES;hb=refs/heads/4.0
>>> 
>>> The artifacts being voted on during this round also include the
>>> following additional fixes (most were identified as part of testing
>>> during the last round of voting):
>>> 
>>> * Many documentation fixes (particularly the release notes and
>>> installation guide)
>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the
>>>UI
>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>> * Correction to the devcloud rdeploy build target, to make testing
>>>easier
>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
>>>will fail
>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>> * DISCLAIMER added to the Marvin tool dir
>>> 
>>> 
>>> The vote will be open for 72 hours.
>>> 
>>> 
>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>> sure to indicate "(binding)" with their vote?
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>> 
>>> Thanks!
>>> 
>> 
>> 
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by "Musayev, Ilya" <im...@webmd.net>.
Test case 3 and 4 wording has been changed, see below.

On Oct 22, 2012, at 6:34 PM, "Musayev, Ilya" <im...@webmd.net> wrote:

> Following issues has been witnessed thus far:
> 
> I'm just going to provide the output of my tests and you be the judge if it's bug or an error on my part - I can then submit a bug report if needed.
> 
> 1 - when configuring VMware ESXi environment initially primary store cannot be set as VMFS and must be configured as NFS for setup to work. I could not get VMFS to work as primary storage without adding NFS as primary first. (need to confirm if VMFS will still works as primary - post adding NFS as primary - as of now I just use NFS as primary storage)
> 
> 2 - if VMFS LUN is incorrectly set while going through initial setup process (not using first time wizard - since VMware ESXi Cluster is not an option) and user mistakenly enters improper LUN, the UI will detect as an error but even if you correct it - there is no way to continue the setup process and no API calls are issued to confirm the validity of the new LUN name. at this point, I had to start over from scratch.
> 
> 3. Don't know if this would-be a bug or feature enhacement. While adding a vmware cluster - the CS is specifically looking for "Management Network" port group on vSwitch0. If name does not match - you could see an error that "Management Network" portgroup is not found. The prefered logic  would be to lookup the portgroup of vmk0 (or whatever management virtual NIC is) and use it as your portgroup.
> 
> 4. If your VMware cluster has virtual switch vSwitch0 used for outbound network communication and another vSwitch1 for other internal private tasks with no outbound network connectivity - when the Secondary storage VM is deployed it incorrectly picks vSwitch1 and attempts to use this vswitch for communication with CS core. Obviously fails since no NICs are connected to vSwitch1.
> 
> 5. This seems to have been the case for me all the time - but by default - the first time wizard does not have VMware cluster as an option. I always to choose 'Skip, I've used cloud stack before' button.
> 
> 6. If I attempt to do a complete cleanup without flushing DB, I'm unable to delete physical network connection - eventhough no networks are defined/assigned - and therefore I cannot delete the zone. I had to drop mysql db and start fresh.
> 
> 7. The cloud ssh and password scripts still need a bit more enhancement - I will submit the patch shortly. I also think we can do more improvements on the way code is written without changing functionality.
> 
> * None of these are show stoppers - but things I've noticed when I went through install process. At the end, I was able to get it to work.
> 
> Let me know which are bugs and I will file a bug report with supporting documentation.
> 
> I will go through install process once more next week or later this week to double check and note all the issues. I will also be testing Netscaler integration.
> 
> Regards
> Ilya
> 
> 
> 
> On Oct 22, 2012, at 12:17 PM, "Chip Childers (ASF)" <ch...@apache.org> wrote:
> 
>> Hi All,
>> 
>> I would like to call a vote for Apache CloudStack (Incubating) Release
>> 4.0.0-incubating (third round).
>> 
>> We encourage the whole community to download and test these release
>> artifacts, so that any critical issues can be resolved before the
>> release is made. The more time that each individual spends reviewing
>> the artifacts, the higher confidence we can have in both the release
>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>> to vote on this release, so please give it a shot.
>> 
>> Instructions for Validating and Testing the artifacts can be found here:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>> 
>> If you have any trouble setting up a test environment using the
>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>> will be sure to help, and we'll improve our test procedure
>> documentation at the same time!
>> 
>> Now, on to the specifics of what we are voting on...
>> 
>> 
>> The following artifacts are up for the vote:
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>> 
>> PGP release keys (signed using A99A5D58):
>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>> 
>> Branch: 4.0
>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>> 
>> 
>> List of changes:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>> 
>> The artifacts being voted on during this round also include the
>> following additional fixes (most were identified as part of testing
>> during the last round of voting):
>> 
>> * Many documentation fixes (particularly the release notes and
>> installation guide)
>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>> * CLOUDSTACK-349: Russian l10n not properly displaying
>> * Correction to the devcloud rdeploy build target, to make testing easier
>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>> * DISCLAIMER added to the Marvin tool dir
>> 
>> 
>> The vote will be open for 72 hours.
>> 
>> 
>> For sanity in tallying the vote, can PPMC and IPMC members please be
>> sure to indicate "(binding)" with their vote?
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>> 
>> Thanks!
>> 
> 
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by "Musayev, Ilya" <im...@webmd.net>.
Following issues has been witnessed thus far:

I'm just going to provide the output of my tests and you be the judge if it's bug or an error on my part - I can then submit a bug report if needed.

1 - when configuring VMware ESXi environment initially primary store cannot be set as VMFS and must be configured as NFS for setup to work. I could not get VMFS to work as primary storage without adding NFS as primary first. (need to confirm if VMFS will still works as primary - post adding NFS as primary - as of now I just use NFS as primary storage)

2 - if VMFS LUN is incorrectly set while going through initial setup process (not using first time wizard - since VMware ESXi Cluster is not an option) and user mistakenly enters improper LUN, the UI will detect as an error but even if you correct it - there is no way to continue the setup process and no API calls are issued to confirm the validity of the new LUN name. at this point, I had to start over from scratch.

3. Don't know if this would-be a bug or feature enhacement. While adding a vmware cluster to hypervisor - the CS is specifically looking for "Management Network" port group on vSwitch0. If name does not match - you could see an error that "Management Network" portgroup is not found. The prefered logic  would be to lookup the portgroup of vmk0 (or whatever management virtual NIC is) and use it as your portgroup.

4. If your VMware cluster has virtual switch vSwitch0 used for outbound network communication and another vSwitch1 for other internal private tasks with no outbound network connectivity - the Secondary storage VM incorrectly picks vSwitch1 and attempted to use that NIC for communication with CS core.

5. This seems to have been the case for me all the time - but by default - the first time wizard does not have VMware cluster as an option. I always to choose 'Skip, I've used cloud stack before' button.

6. If I attempt to do a complete cleanup without flushing DB, I'm unable to delete physical network connection - eventhough no networks are defined/assigned - and therefore I cannot delete the zone. I had to drop mysql db and start fresh.

7. The cloud ssh and password scripts still need a bit more enhancement - I will submit the patch shortly. I also think we can do more improvements on the way code is written without changing functionality.

* None of these are show stoppers - but things I've noticed when I went through install process. At the end, I was able to get it to work.

Let me know which are bugs and I will file a bug report with supporting documentation.

I will go through install process once more next week or later this week to double check and note all the issues. I will also be testing Netscaler integration.

Regards
Ilya



On Oct 22, 2012, at 12:17 PM, "Chip Childers (ASF)" <ch...@apache.org> wrote:

> Hi All,
> 
> I would like to call a vote for Apache CloudStack (Incubating) Release
> 4.0.0-incubating (third round).
> 
> We encourage the whole community to download and test these release
> artifacts, so that any critical issues can be resolved before the
> release is made. The more time that each individual spends reviewing
> the artifacts, the higher confidence we can have in both the release
> itself and our ability to pass an IPMC vote later on.  Everyone is free
> to vote on this release, so please give it a shot.
> 
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
> 
> If you have any trouble setting up a test environment using the
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
> will be sure to help, and we'll improve our test procedure
> documentation at the same time!
> 
> Now, on to the specifics of what we are voting on...
> 
> 
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
> 
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> 
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> 
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
> 
> The artifacts being voted on during this round also include the
> following additional fixes (most were identified as part of testing
> during the last round of voting):
> 
> * Many documentation fixes (particularly the release notes and
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
> 
> 
> The vote will be open for 72 hours.
> 
> 
> For sanity in tallying the vote, can PPMC and IPMC members please be
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Thanks!
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
Huh, interesting. The SVN approach is new to me. I will update CouchDB's
release procedure. Thanks Olivier.

On 25 October 2012 20:39, Olivier Lamy <ol...@apache.org> wrote:

> 2012/10/25 Chip Childers <ch...@sungard.com>:
> > On Thu, Oct 25, 2012 at 2:57 PM, Olivier Lamy <ol...@apache.org> wrote:
> >> 2012/10/25 Chip Childers <ch...@sungard.com>:
> >>> On Thu, Oct 25, 2012 at 4:28 AM, Olivier Lamy <ol...@apache.org>
> wrote:
> >>>> +1 (binding).
> >>>> I checked sigs, license headers: sounds good.
> >>>>
> >>>> A minor point is the KEYS file available here
> >>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS .
> >>>> Perso I would prefer to see it in a scm (most of Apache do that).
> >>>> Maybe for next release using svnpubsub for dist (at least it will be
> >>>> in svn and available with distrib)
> >>>> Let me know if I can help to setup this process.
> >>>
> >>> Oliver,
> >>>
> >>> Noah advised us to remove the KEYS file from our source tree earlier.
> >>>
> >>> I'll be putting it in the dist folder (URL will be
> >>> http://www.apache.org/dist/incubator/cloudstack/KEYS ).  My
> >>> understanding is that (after the IPMC vote) I simply copy the files
> >>> from my p.a.o public_html space to the correct folder on that server,
> >> correct
> >>> and then the mirrors start picking it up.  Is there actually an SVN
> >>> method of adding the artifacts to the dist folder?
> >> This need some setup first.
> >> Some projects commit rc builds to
> >> https://dist.apache.org/repos/dist/dev/ then once the vote has passed
> >> do a simple svn mv to https://dist.apache.org/repos/dist/release/
> >> (infra folks can setup a process to populate distribution folders from
> >> this svn path).
> >> A bit late now so for next release.
> >
> > I requested this:  https://issues.apache.org/jira/browse/INFRA-5225
> >
> > Advice on how to use it properly would be appreciated!
>
> I have just created the path
> https://dist.apache.org/repos/dist/dev/incubator/cloudstack/
>
> So just add the KEY file here (in
> https://dist.apache.org/repos/dist/release/incubator/cloudstack/)
>
> copy content from
>
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
> to
> https://dist.apache.org/repos/dist/dev/incubator/cloudstack/4.0.0-incubating
>
> Next time call a vote on for this path.
>
> Once vote has passed just:
> svn mv
> https://dist.apache.org/repos/dist/dev/incubator/cloudstack/4.0.0-incubating
> https://dist.apache.org/repos/dist/release/incubator/cloudstack/
>
> >
> >>>
> >>> -chip
> >>>
> >>>> 2012/10/22 Chip Childers (ASF) <ch...@apache.org>:
> >>>>> Hi All,
> >>>>>
> >>>>> I would like to call a vote for Apache CloudStack (Incubating)
> Release
> >>>>> 4.0.0-incubating (third round).
> >>>>>
> >>>>> We encourage the whole community to download and test these release
> >>>>> artifacts, so that any critical issues can be resolved before the
> >>>>> release is made. The more time that each individual spends reviewing
> >>>>> the artifacts, the higher confidence we can have in both the release
> >>>>> itself and our ability to pass an IPMC vote later on.  Everyone is
> free
> >>>>> to vote on this release, so please give it a shot.
> >>>>>
> >>>>> Instructions for Validating and Testing the artifacts can be found
> here:
> >>>>>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
> >>>>>
> >>>>> If you have any trouble setting up a test environment using the
> >>>>> procedure above, please ask on the cloudstack-dev@i.a.o list.
>  Someone
> >>>>> will be sure to help, and we'll improve our test procedure
> >>>>> documentation at the same time!
> >>>>>
> >>>>> Now, on to the specifics of what we are voting on...
> >>>>>
> >>>>>
> >>>>> The following artifacts are up for the vote:
> >>>>>
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
> >>>>>
> >>>>> PGP release keys (signed using A99A5D58):
> >>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >>>>>
> >>>>> Branch: 4.0
> >>>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> >>>>>
> >>>>>
> >>>>> List of changes:
> >>>>>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
> >>>>>
> >>>>> The artifacts being voted on during this round also include the
> >>>>> following additional fixes (most were identified as part of testing
> >>>>> during the last round of voting):
> >>>>>
> >>>>> * Many documentation fixes (particularly the release notes and
> >>>>> installation guide)
> >>>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on
> the UI
> >>>>> * CLOUDSTACK-349: Russian l10n not properly displaying
> >>>>> * Correction to the devcloud rdeploy build target, to make testing
> easier
> >>>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
> will fail
> >>>>> * CLOUDSTACK-118: Status of host resorce stuck in
> "ErrorInMaintenance"
> >>>>> * DISCLAIMER added to the Marvin tool dir
> >>>>>
> >>>>>
> >>>>> The vote will be open for 72 hours.
> >>>>>
> >>>>>
> >>>>> For sanity in tallying the vote, can PPMC and IPMC members please be
> >>>>> sure to indicate "(binding)" with their vote?
> >>>>> [ ] +1  approve
> >>>>> [ ] +0  no opinion
> >>>>> [ ] -1  disapprove (and reason why)
> >>>>>
> >>>>> Thanks!
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Olivier Lamy
> >>>> Talend: http://coders.talend.com
> >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>>>
> >>
> >>
> >>
> >> --
> >> Olivier Lamy
> >> Talend: http://coders.talend.com
> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>



-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Thu, Oct 25, 2012 at 3:39 PM, Olivier Lamy <ol...@apache.org> wrote:
> 2012/10/25 Chip Childers <ch...@sungard.com>:
>> On Thu, Oct 25, 2012 at 2:57 PM, Olivier Lamy <ol...@apache.org> wrote:
>>> 2012/10/25 Chip Childers <ch...@sungard.com>:
>>>> On Thu, Oct 25, 2012 at 4:28 AM, Olivier Lamy <ol...@apache.org> wrote:
>>>>> +1 (binding).
>>>>> I checked sigs, license headers: sounds good.
>>>>>
>>>>> A minor point is the KEYS file available here
>>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS .
>>>>> Perso I would prefer to see it in a scm (most of Apache do that).
>>>>> Maybe for next release using svnpubsub for dist (at least it will be
>>>>> in svn and available with distrib)
>>>>> Let me know if I can help to setup this process.
>>>>
>>>> Oliver,
>>>>
>>>> Noah advised us to remove the KEYS file from our source tree earlier.
>>>>
>>>> I'll be putting it in the dist folder (URL will be
>>>> http://www.apache.org/dist/incubator/cloudstack/KEYS ).  My
>>>> understanding is that (after the IPMC vote) I simply copy the files
>>>> from my p.a.o public_html space to the correct folder on that server,
>>> correct
>>>> and then the mirrors start picking it up.  Is there actually an SVN
>>>> method of adding the artifacts to the dist folder?
>>> This need some setup first.
>>> Some projects commit rc builds to
>>> https://dist.apache.org/repos/dist/dev/ then once the vote has passed
>>> do a simple svn mv to https://dist.apache.org/repos/dist/release/
>>> (infra folks can setup a process to populate distribution folders from
>>> this svn path).
>>> A bit late now so for next release.
>>
>> I requested this:  https://issues.apache.org/jira/browse/INFRA-5225
>>
>> Advice on how to use it properly would be appreciated!
>
> I have just created the path
> https://dist.apache.org/repos/dist/dev/incubator/cloudstack/
>
> So just add the KEY file here (in
> https://dist.apache.org/repos/dist/release/incubator/cloudstack/)
>
> copy content from
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
> to https://dist.apache.org/repos/dist/dev/incubator/cloudstack/4.0.0-incubating
>
> Next time call a vote on for this path.
>
> Once vote has passed just:
> svn mv https://dist.apache.org/repos/dist/dev/incubator/cloudstack/4.0.0-incubating
> https://dist.apache.org/repos/dist/release/incubator/cloudstack/
>

Great, thanks!

I'll do an svn commit of the artifacts into
https://dist.apache.org/repos/dist/release/incubator/cloudstack/ as
the official release step for this particular vote (assuming we pass
the project and IPMC votes).  If we start over, I'll fully use that
process.

>>
>>>>
>>>> -chip
>>>>
>>>>> 2012/10/22 Chip Childers (ASF) <ch...@apache.org>:
>>>>>> Hi All,
>>>>>>
>>>>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>>>>> 4.0.0-incubating (third round).
>>>>>>
>>>>>> We encourage the whole community to download and test these release
>>>>>> artifacts, so that any critical issues can be resolved before the
>>>>>> release is made. The more time that each individual spends reviewing
>>>>>> the artifacts, the higher confidence we can have in both the release
>>>>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>>>>> to vote on this release, so please give it a shot.
>>>>>>
>>>>>> Instructions for Validating and Testing the artifacts can be found here:
>>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>>>>>
>>>>>> If you have any trouble setting up a test environment using the
>>>>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>>>>> will be sure to help, and we'll improve our test procedure
>>>>>> documentation at the same time!
>>>>>>
>>>>>> Now, on to the specifics of what we are voting on...
>>>>>>
>>>>>>
>>>>>> The following artifacts are up for the vote:
>>>>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>>>>>
>>>>>> PGP release keys (signed using A99A5D58):
>>>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>>>>
>>>>>> Branch: 4.0
>>>>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>>>>
>>>>>>
>>>>>> List of changes:
>>>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>>>>
>>>>>> The artifacts being voted on during this round also include the
>>>>>> following additional fixes (most were identified as part of testing
>>>>>> during the last round of voting):
>>>>>>
>>>>>> * Many documentation fixes (particularly the release notes and
>>>>>> installation guide)
>>>>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>>>>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>>>>> * Correction to the devcloud rdeploy build target, to make testing easier
>>>>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>>>>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>>>>> * DISCLAIMER added to the Marvin tool dir
>>>>>>
>>>>>>
>>>>>> The vote will be open for 72 hours.
>>>>>>
>>>>>>
>>>>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>>>>> sure to indicate "(binding)" with their vote?
>>>>>> [ ] +1  approve
>>>>>> [ ] +0  no opinion
>>>>>> [ ] -1  disapprove (and reason why)
>>>>>>
>>>>>> Thanks!
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Olivier Lamy
>>>>> Talend: http://coders.talend.com
>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>>
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Olivier Lamy <ol...@apache.org>.
2012/10/25 Chip Childers <ch...@sungard.com>:
> On Thu, Oct 25, 2012 at 2:57 PM, Olivier Lamy <ol...@apache.org> wrote:
>> 2012/10/25 Chip Childers <ch...@sungard.com>:
>>> On Thu, Oct 25, 2012 at 4:28 AM, Olivier Lamy <ol...@apache.org> wrote:
>>>> +1 (binding).
>>>> I checked sigs, license headers: sounds good.
>>>>
>>>> A minor point is the KEYS file available here
>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS .
>>>> Perso I would prefer to see it in a scm (most of Apache do that).
>>>> Maybe for next release using svnpubsub for dist (at least it will be
>>>> in svn and available with distrib)
>>>> Let me know if I can help to setup this process.
>>>
>>> Oliver,
>>>
>>> Noah advised us to remove the KEYS file from our source tree earlier.
>>>
>>> I'll be putting it in the dist folder (URL will be
>>> http://www.apache.org/dist/incubator/cloudstack/KEYS ).  My
>>> understanding is that (after the IPMC vote) I simply copy the files
>>> from my p.a.o public_html space to the correct folder on that server,
>> correct
>>> and then the mirrors start picking it up.  Is there actually an SVN
>>> method of adding the artifacts to the dist folder?
>> This need some setup first.
>> Some projects commit rc builds to
>> https://dist.apache.org/repos/dist/dev/ then once the vote has passed
>> do a simple svn mv to https://dist.apache.org/repos/dist/release/
>> (infra folks can setup a process to populate distribution folders from
>> this svn path).
>> A bit late now so for next release.
>
> I requested this:  https://issues.apache.org/jira/browse/INFRA-5225
>
> Advice on how to use it properly would be appreciated!

I have just created the path
https://dist.apache.org/repos/dist/dev/incubator/cloudstack/

So just add the KEY file here (in
https://dist.apache.org/repos/dist/release/incubator/cloudstack/)

copy content from
http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
to https://dist.apache.org/repos/dist/dev/incubator/cloudstack/4.0.0-incubating

Next time call a vote on for this path.

Once vote has passed just:
svn mv https://dist.apache.org/repos/dist/dev/incubator/cloudstack/4.0.0-incubating
https://dist.apache.org/repos/dist/release/incubator/cloudstack/

>
>>>
>>> -chip
>>>
>>>> 2012/10/22 Chip Childers (ASF) <ch...@apache.org>:
>>>>> Hi All,
>>>>>
>>>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>>>> 4.0.0-incubating (third round).
>>>>>
>>>>> We encourage the whole community to download and test these release
>>>>> artifacts, so that any critical issues can be resolved before the
>>>>> release is made. The more time that each individual spends reviewing
>>>>> the artifacts, the higher confidence we can have in both the release
>>>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>>>> to vote on this release, so please give it a shot.
>>>>>
>>>>> Instructions for Validating and Testing the artifacts can be found here:
>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>>>>
>>>>> If you have any trouble setting up a test environment using the
>>>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>>>> will be sure to help, and we'll improve our test procedure
>>>>> documentation at the same time!
>>>>>
>>>>> Now, on to the specifics of what we are voting on...
>>>>>
>>>>>
>>>>> The following artifacts are up for the vote:
>>>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>>>>
>>>>> PGP release keys (signed using A99A5D58):
>>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>>>
>>>>> Branch: 4.0
>>>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>>>
>>>>>
>>>>> List of changes:
>>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>>>
>>>>> The artifacts being voted on during this round also include the
>>>>> following additional fixes (most were identified as part of testing
>>>>> during the last round of voting):
>>>>>
>>>>> * Many documentation fixes (particularly the release notes and
>>>>> installation guide)
>>>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>>>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>>>> * Correction to the devcloud rdeploy build target, to make testing easier
>>>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>>>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>>>> * DISCLAIMER added to the Marvin tool dir
>>>>>
>>>>>
>>>>> The vote will be open for 72 hours.
>>>>>
>>>>>
>>>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>>>> sure to indicate "(binding)" with their vote?
>>>>> [ ] +1  approve
>>>>> [ ] +0  no opinion
>>>>> [ ] -1  disapprove (and reason why)
>>>>>
>>>>> Thanks!
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> Talend: http://coders.talend.com
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Thu, Oct 25, 2012 at 2:57 PM, Olivier Lamy <ol...@apache.org> wrote:
> 2012/10/25 Chip Childers <ch...@sungard.com>:
>> On Thu, Oct 25, 2012 at 4:28 AM, Olivier Lamy <ol...@apache.org> wrote:
>>> +1 (binding).
>>> I checked sigs, license headers: sounds good.
>>>
>>> A minor point is the KEYS file available here
>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS .
>>> Perso I would prefer to see it in a scm (most of Apache do that).
>>> Maybe for next release using svnpubsub for dist (at least it will be
>>> in svn and available with distrib)
>>> Let me know if I can help to setup this process.
>>
>> Oliver,
>>
>> Noah advised us to remove the KEYS file from our source tree earlier.
>>
>> I'll be putting it in the dist folder (URL will be
>> http://www.apache.org/dist/incubator/cloudstack/KEYS ).  My
>> understanding is that (after the IPMC vote) I simply copy the files
>> from my p.a.o public_html space to the correct folder on that server,
> correct
>> and then the mirrors start picking it up.  Is there actually an SVN
>> method of adding the artifacts to the dist folder?
> This need some setup first.
> Some projects commit rc builds to
> https://dist.apache.org/repos/dist/dev/ then once the vote has passed
> do a simple svn mv to https://dist.apache.org/repos/dist/release/
> (infra folks can setup a process to populate distribution folders from
> this svn path).
> A bit late now so for next release.

I requested this:  https://issues.apache.org/jira/browse/INFRA-5225

Advice on how to use it properly would be appreciated!

>>
>> -chip
>>
>>> 2012/10/22 Chip Childers (ASF) <ch...@apache.org>:
>>>> Hi All,
>>>>
>>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>>> 4.0.0-incubating (third round).
>>>>
>>>> We encourage the whole community to download and test these release
>>>> artifacts, so that any critical issues can be resolved before the
>>>> release is made. The more time that each individual spends reviewing
>>>> the artifacts, the higher confidence we can have in both the release
>>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>>> to vote on this release, so please give it a shot.
>>>>
>>>> Instructions for Validating and Testing the artifacts can be found here:
>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>>>
>>>> If you have any trouble setting up a test environment using the
>>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>>> will be sure to help, and we'll improve our test procedure
>>>> documentation at the same time!
>>>>
>>>> Now, on to the specifics of what we are voting on...
>>>>
>>>>
>>>> The following artifacts are up for the vote:
>>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>>>
>>>> PGP release keys (signed using A99A5D58):
>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>>
>>>> Branch: 4.0
>>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>>
>>>>
>>>> List of changes:
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>>
>>>> The artifacts being voted on during this round also include the
>>>> following additional fixes (most were identified as part of testing
>>>> during the last round of voting):
>>>>
>>>> * Many documentation fixes (particularly the release notes and
>>>> installation guide)
>>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>>> * Correction to the devcloud rdeploy build target, to make testing easier
>>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>>> * DISCLAIMER added to the Marvin tool dir
>>>>
>>>>
>>>> The vote will be open for 72 hours.
>>>>
>>>>
>>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>>> sure to indicate "(binding)" with their vote?
>>>> [ ] +1  approve
>>>> [ ] +0  no opinion
>>>> [ ] -1  disapprove (and reason why)
>>>>
>>>> Thanks!
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Olivier Lamy <ol...@apache.org>.
2012/10/25 Chip Childers <ch...@sungard.com>:
> On Thu, Oct 25, 2012 at 4:28 AM, Olivier Lamy <ol...@apache.org> wrote:
>> +1 (binding).
>> I checked sigs, license headers: sounds good.
>>
>> A minor point is the KEYS file available here
>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS .
>> Perso I would prefer to see it in a scm (most of Apache do that).
>> Maybe for next release using svnpubsub for dist (at least it will be
>> in svn and available with distrib)
>> Let me know if I can help to setup this process.
>
> Oliver,
>
> Noah advised us to remove the KEYS file from our source tree earlier.
>
> I'll be putting it in the dist folder (URL will be
> http://www.apache.org/dist/incubator/cloudstack/KEYS ).  My
> understanding is that (after the IPMC vote) I simply copy the files
> from my p.a.o public_html space to the correct folder on that server,
correct
> and then the mirrors start picking it up.  Is there actually an SVN
> method of adding the artifacts to the dist folder?
This need some setup first.
Some projects commit rc builds to
https://dist.apache.org/repos/dist/dev/ then once the vote has passed
do a simple svn mv to https://dist.apache.org/repos/dist/release/
(infra folks can setup a process to populate distribution folders from
this svn path).
A bit late now so for next release.
>
> -chip
>
>> 2012/10/22 Chip Childers (ASF) <ch...@apache.org>:
>>> Hi All,
>>>
>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>> 4.0.0-incubating (third round).
>>>
>>> We encourage the whole community to download and test these release
>>> artifacts, so that any critical issues can be resolved before the
>>> release is made. The more time that each individual spends reviewing
>>> the artifacts, the higher confidence we can have in both the release
>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>> to vote on this release, so please give it a shot.
>>>
>>> Instructions for Validating and Testing the artifacts can be found here:
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>>
>>> If you have any trouble setting up a test environment using the
>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>> will be sure to help, and we'll improve our test procedure
>>> documentation at the same time!
>>>
>>> Now, on to the specifics of what we are voting on...
>>>
>>>
>>> The following artifacts are up for the vote:
>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>>
>>> PGP release keys (signed using A99A5D58):
>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>
>>> Branch: 4.0
>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>
>>>
>>> List of changes:
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>
>>> The artifacts being voted on during this round also include the
>>> following additional fixes (most were identified as part of testing
>>> during the last round of voting):
>>>
>>> * Many documentation fixes (particularly the release notes and
>>> installation guide)
>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>> * Correction to the devcloud rdeploy build target, to make testing easier
>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>> * DISCLAIMER added to the Marvin tool dir
>>>
>>>
>>> The vote will be open for 72 hours.
>>>
>>>
>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>> sure to indicate "(binding)" with their vote?
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>>
>>> Thanks!
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Simon Weller <sw...@ena.com>.
+1 


We've been testing our own rolled nonoss RPMS pulled from the 4.0.0-incubating git repo. 


Our testing has been focused on RHEL/SL 6.3 for both management and hosts : 


Configuration and Install 

KVM 

CLVM functionality for primary storage (multiple primary storage profiles with tagging) 

Advanced Networking with both isolated and shared network profiles 
HA components. 
Projects 
VPC 
Domain Accounts 
VM profile changes (service profiles, network profiles et al) 
Templated + ISO installs 
KVM Snapshoting 
Firewalling in advanced networking 
Port Forwarding in advanced networking 
ELB in advanced networking 
Source NAT configuration 
Management GUI functionality 


VM hosts: Various flavours of RHEL based 5.x and 6.x linux (64 bit) 

Windows 2003 32 bit (both IDE and para virt (virtio) via an internal patch) 

Windows 2008 R2 32 and 64 bit (both IDE and para virt (virtio) via an internal patch) 




We're very happy with the state of the release. 


- Si 

----- Original Message -----

From: "Chip Childers" <ch...@sungard.com> 
To: cloudstack-dev@incubator.apache.org 
Sent: Thursday, October 25, 2012 11:40:40 AM 
Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round 

On Thu, Oct 25, 2012 at 4:28 AM, Olivier Lamy <ol...@apache.org> wrote: 
> +1 (binding). 
> I checked sigs, license headers: sounds good. 
> 
> A minor point is the KEYS file available here 
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS . 
> Perso I would prefer to see it in a scm (most of Apache do that). 
> Maybe for next release using svnpubsub for dist (at least it will be 
> in svn and available with distrib) 
> Let me know if I can help to setup this process. 

Oliver, 

Noah advised us to remove the KEYS file from our source tree earlier. 

I'll be putting it in the dist folder (URL will be 
http://www.apache.org/dist/incubator/cloudstack/KEYS ). My 
understanding is that (after the IPMC vote) I simply copy the files 
from my p.a.o public_html space to the correct folder on that server, 
and then the mirrors start picking it up. Is there actually an SVN 
method of adding the artifacts to the dist folder? 

-chip 

> 2012/10/22 Chip Childers (ASF) <ch...@apache.org>: 
>> Hi All, 
>> 
>> I would like to call a vote for Apache CloudStack (Incubating) Release 
>> 4.0.0-incubating (third round). 
>> 
>> We encourage the whole community to download and test these release 
>> artifacts, so that any critical issues can be resolved before the 
>> release is made. The more time that each individual spends reviewing 
>> the artifacts, the higher confidence we can have in both the release 
>> itself and our ability to pass an IPMC vote later on. Everyone is free 
>> to vote on this release, so please give it a shot. 
>> 
>> Instructions for Validating and Testing the artifacts can be found here: 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure 
>> 
>> If you have any trouble setting up a test environment using the 
>> procedure above, please ask on the cloudstack-dev@i.a.o list. Someone 
>> will be sure to help, and we'll improve our test procedure 
>> documentation at the same time! 
>> 
>> Now, on to the specifics of what we are voting on... 
>> 
>> 
>> The following artifacts are up for the vote: 
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/ 
>> 
>> PGP release keys (signed using A99A5D58): 
>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS 
>> 
>> Branch: 4.0 
>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480 
>> 
>> 
>> List of changes: 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0 
>> 
>> The artifacts being voted on during this round also include the 
>> following additional fixes (most were identified as part of testing 
>> during the last round of voting): 
>> 
>> * Many documentation fixes (particularly the release notes and 
>> installation guide) 
>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI 
>> * CLOUDSTACK-349: Russian l10n not properly displaying 
>> * Correction to the devcloud rdeploy build target, to make testing easier 
>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail 
>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance" 
>> * DISCLAIMER added to the Marvin tool dir 
>> 
>> 
>> The vote will be open for 72 hours. 
>> 
>> 
>> For sanity in tallying the vote, can PPMC and IPMC members please be 
>> sure to indicate "(binding)" with their vote? 
>> [ ] +1 approve 
>> [ ] +0 no opinion 
>> [ ] -1 disapprove (and reason why) 
>> 
>> Thanks! 
> 
> 
> 
> -- 
> Olivier Lamy 
> Talend: http://coders.talend.com 
> http://twitter.com/olamy | http://linkedin.com/in/olamy 
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Thu, Oct 25, 2012 at 4:28 AM, Olivier Lamy <ol...@apache.org> wrote:
> +1 (binding).
> I checked sigs, license headers: sounds good.
>
> A minor point is the KEYS file available here
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS .
> Perso I would prefer to see it in a scm (most of Apache do that).
> Maybe for next release using svnpubsub for dist (at least it will be
> in svn and available with distrib)
> Let me know if I can help to setup this process.

Oliver,

Noah advised us to remove the KEYS file from our source tree earlier.

I'll be putting it in the dist folder (URL will be
http://www.apache.org/dist/incubator/cloudstack/KEYS ).  My
understanding is that (after the IPMC vote) I simply copy the files
from my p.a.o public_html space to the correct folder on that server,
and then the mirrors start picking it up.  Is there actually an SVN
method of adding the artifacts to the dist folder?

-chip

> 2012/10/22 Chip Childers (ASF) <ch...@apache.org>:
>> Hi All,
>>
>> I would like to call a vote for Apache CloudStack (Incubating) Release
>> 4.0.0-incubating (third round).
>>
>> We encourage the whole community to download and test these release
>> artifacts, so that any critical issues can be resolved before the
>> release is made. The more time that each individual spends reviewing
>> the artifacts, the higher confidence we can have in both the release
>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>> to vote on this release, so please give it a shot.
>>
>> Instructions for Validating and Testing the artifacts can be found here:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>
>> If you have any trouble setting up a test environment using the
>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>> will be sure to help, and we'll improve our test procedure
>> documentation at the same time!
>>
>> Now, on to the specifics of what we are voting on...
>>
>>
>> The following artifacts are up for the vote:
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>
>> PGP release keys (signed using A99A5D58):
>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>
>> Branch: 4.0
>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>
>>
>> List of changes:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>
>> The artifacts being voted on during this round also include the
>> following additional fixes (most were identified as part of testing
>> during the last round of voting):
>>
>> * Many documentation fixes (particularly the release notes and
>> installation guide)
>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>> * CLOUDSTACK-349: Russian l10n not properly displaying
>> * Correction to the devcloud rdeploy build target, to make testing easier
>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>> * DISCLAIMER added to the Marvin tool dir
>>
>>
>> The vote will be open for 72 hours.
>>
>>
>> For sanity in tallying the vote, can PPMC and IPMC members please be
>> sure to indicate "(binding)" with their vote?
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Thanks!
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Olivier Lamy <ol...@apache.org>.
+1 (binding).
I checked sigs, license headers: sounds good.

A minor point is the KEYS file available here
http://people.apache.org/~chipchilders/dist/cloudstack/KEYS .
Perso I would prefer to see it in a scm (most of Apache do that).
Maybe for next release using svnpubsub for dist (at least it will be
in svn and available with distrib)
Let me know if I can help to setup this process.



2012/10/22 Chip Childers (ASF) <ch...@apache.org>:
> Hi All,
>
> I would like to call a vote for Apache CloudStack (Incubating) Release
> 4.0.0-incubating (third round).
>
> We encourage the whole community to download and test these release
> artifacts, so that any critical issues can be resolved before the
> release is made. The more time that each individual spends reviewing
> the artifacts, the higher confidence we can have in both the release
> itself and our ability to pass an IPMC vote later on.  Everyone is free
> to vote on this release, so please give it a shot.
>
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>
> If you have any trouble setting up a test environment using the
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
> will be sure to help, and we'll improve our test procedure
> documentation at the same time!
>
> Now, on to the specifics of what we are voting on...
>
>
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>
>
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>
> The artifacts being voted on during this round also include the
> following additional fixes (most were identified as part of testing
> during the last round of voting):
>
> * Many documentation fixes (particularly the release notes and
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
>
>
> The vote will be open for 72 hours.
>
>
> For sanity in tallying the vote, can PPMC and IPMC members please be
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Thanks!



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Will Chan <wi...@citrix.com>.
+1 (binding)

Followed instructions on https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure and was successfully able to verify the signatures, compile, and deployed on VB.  Was able to successfully launch a VM.

Will

> -----Original Message-----
> From: chip.childers@sungard.com [mailto:chip.childers@sungard.com] On
> Behalf Of Chip Childers (ASF)
> Sent: Monday, October 22, 2012 9:16 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> Hi All,
> 
> I would like to call a vote for Apache CloudStack (Incubating) Release 4.0.0-
> incubating (third round).
> 
> We encourage the whole community to download and test these release
> artifacts, so that any critical issues can be resolved before the release is
> made. The more time that each individual spends reviewing the artifacts,
> the higher confidence we can have in both the release itself and our ability
> to pass an IPMC vote later on.  Everyone is free to vote on this release, so
> please give it a shot.
> 
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0
> +test+procedure
> 
> If you have any trouble setting up a test environment using the procedure
> above, please ask on the cloudstack-dev@i.a.o list.  Someone will be sure to
> help, and we'll improve our test procedure documentation at the same
> time!
> 
> Now, on to the specifics of what we are voting on...
> 
> 
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> incubating/
> 
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> 
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> 
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-
> cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
> 
> The artifacts being voted on during this round also include the following
> additional fixes (most were identified as part of testing during the last
> round of voting):
> 
> * Many documentation fixes (particularly the release notes and installation
> guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will
> fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
> 
> 
> The vote will be open for 72 hours.
> 
> 
> For sanity in tallying the vote, can PPMC and IPMC members please be sure
> to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Thanks!

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
Okay.

We talked about the waf file on general@incubator, and we established that
the binary component is a compressed archive of Python code. Chip manually
uncompressed this and verified that it corresponds to the Python source
code in the waf project. Because of this, there is no logical difference
between that binary component of that file, and say, a shell archive. For
this reason, I think we can distribute this. (Though we probably still want
to look in to either documenting this, or removing waf.)

This release has my +1 vote. LET'S SHIP THIS THING!

On 29 October 2012 17:29, Chip Childers <ch...@sungard.com> wrote:

> On Mon, Oct 29, 2012 at 10:10 AM, Chip Childers
> <ch...@sungard.com> wrote:
> > On Sun, Oct 28, 2012 at 8:01 PM, Chip Childers
> > <ch...@sungard.com> wrote:
> >> On Sun, Oct 28, 2012 at 1:53 PM, Noah Slater <ns...@apache.org>
> wrote:
> >>> Actually, sorry, I probably gave that +1 a *little* too soon.
> >>>
> >>> Can someone make the case for "waf" not being a release blocker?
> >>>
> >>> Everything else can probably slide.
> >>
> >> Waf needs to go.  No doubt about it.  However, I'm not certain it's a
> >> blocker for a release.  Here's my reasoning:
> >>
> >> Waf is being removed from the project entirely (ongoing work in
> >> origin/maven-to-rpm), so we're not doing something that isn't already
> >> targeted for being undone as fast as possible.   The important thing
> >> to me is understanding that work to remove waf is taking longer than
> >> the community desire to get a release completed at the end of the
> >> summer.  It's one line of bytecode within a file that is not core to
> >> the project itself (it's only a build utility), that has a clearly
> >> marked license for file itself (so distribution is OK), that is only
> >> used as a quick way to create packages for Linux distros (not to do
> >> the actual project compilation), and that will be ignored by any
> >> distro packagers that want to create proper RPMs / DEBs anyway.
> >>
> >> Thoughts?
> >>
> >> -chip
> >
> > Noah has raised the question on general@i.a.o, and I'm holding off on
> > closing this vote to get some comments back from the incubator.
> >
> > -chip
>
> One more follow up.  The discussion on general@i.a.o seems to be
> reaching the consensus that we will be ok with the waf file (but
> really should remove it).  I'm going to wait until tomorrow morning US
> ET to close the vote down, giving the folks on general@ time to raise
> any additional concerns.
>
> >
> >>> On 28 October 2012 17:51, Noah Slater <ns...@apache.org> wrote:
> >>>
> >>>> It is frustrating because everything is so slow, and my (main)
> computer is
> >>>> practically unusable while it is running. How feasible would it be to
> >>>> provide this DevCloud thing as an AMI? I would much prefer to do this
> in
> >>>> the cloud.
> >>>>
> >>>> Okay, I made it to this step:
> >>>>
> >>>> Additional Testing
> >>>>
> >>>> The instance is removed from the web console.
> >>>>
> >>>> And this is what I see on the terminal:
> >>>>
> >>>>   [sshexec]      [java] WARN
>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> >>>> (AgentManager-Handler-6:) VM 3 lost host info, failed authentication
> request
> >>>>   [sshexec]
> >>>>   [sshexec]      [java] WARN
>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> >>>> (AgentManager-Handler-8:) VM 3 lost host info, failed authentication
> request
> >>>>   [sshexec]
> >>>>   [sshexec]      [java] WARN
>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> >>>> (AgentManager-Handler-9:) VM 3 lost host info, failed authentication
> request
> >>>>   [sshexec]
> >>>>   [sshexec]      [java] INFO  [cloud.vm.UserVmManagerImpl]
> >>>> (UserVm-Scavenger-1:) Found 1 vms to expunge.
> >>>>   [sshexec]
> >>>>   [sshexec]      [java] INFO
>  [network.security.SecurityGroupManagerImpl]
> >>>> (UserVm-Scavenger-1:) Disassociated 1 network groups  from uservm 3
> >>>>   [sshexec]
> >>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> >>>> (HA-Worker-1:work-2) Processing HAWork[2-HA-4-Stopped-Scheduled]
> >>>>   [sshexec]
> >>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> >>>> (HA-Worker-1:work-2) HA on VM[DomainRouter|r-4-TEST]
> >>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> >>>> (HA-Worker-1:work-2) VM VM[DomainRouter|r-4-TEST] has been changed.
> >>>>  Current State = Running Previous State = Stopped last updated = 10
> >>>> previous updated = 7
> >>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> >>>> (HA-Worker-1:work-2) Completed HAWork[2-HA-4-Stopped-Scheduled]
> >>>>
> >>>> However, from devcloud, I see this:
> >>>>
> >>>> root@devcloud:~# xe vm-list
> >>>> uuid ( RO)           : 83fdea03-9d67-d5dc-e090-0acba65e7926
> >>>>      name-label ( RW): r-4-TEST
> >>>>     power-state ( RO): running
> >>>>
> >>>>
> >>>> uuid ( RO)           : f01b195e-074b-e8f2-f8b1-b2c493070c8a
> >>>>      name-label ( RW): Control domain on host: devcloud
> >>>>     power-state ( RO): running
> >>>>
> >>>>
> >>>> uuid ( RO)           : 2ab8057a-767e-b700-53e3-861f2e23823a
> >>>>      name-label ( RW): s-1-TEST
> >>>>     power-state ( RO): running
> >>>>
> >>>>
> >>>> uuid ( RO)           : 8b27e755-4486-e27e-ee7a-6e5bc6ea768f
> >>>>      name-label ( RW): v-2-TEST
> >>>>     power-state ( RO): running
> >>>>
> >>>> This looks, to my untrained eyes, like the VM might still be running,
> and
> >>>> in fact that there might be more than one?
> >>>>
> >>>> Okay, at this point, if someone can clarify that issues (or not?) I
> have
> >>>> run into with the functional tests are not release blockers, I am
> happy to
> >>>> just shut up about them and hope that testing is made easier for the
> next
> >>>> release.
> >>>>
> >>>> Just moving on now to some more thorough testing.
> >>>>
> >>>> My manual license check seems satisfactory.
> >>>>
> >>>> We're still shipping the "waf" binary in the root of our source, and I
> >>>> don't understand why. I know I was asked about this during the last
> round.
> >>>> And to be honest, I do not know whether it's a blocker. Can someone
> clarify
> >>>> for me why it is used, and why we can't ship the source instead?
> >>>>
> >>>> Manual file type test: OK
> >>>>
> >>>> Okay, going through some files by hand.
> >>>>
> >>>> The following files do not have copyright headers:
> >>>>
> >>>> setup/apidoc/generateadmincommands.xsl
> >>>> setup/apidoc/generatecommand.xsl
> >>>> setup/apidoc/generatedomainadmincommands.xsl
> >>>> setup/apidoc/generatetoc_footer.xsl
> >>>> setup/apidoc/generateusercommands.xsl
> >>>>
> >>>> I do not consider this a release blocker, but these should be fixed
> (where
> >>>> possible) for the next release.
> >>>>
> >>>> I almost raised a blocked with the files I found under tools/marvin,
> >>>> before I remembered our discussion about them. Heh!
> >>>>
> >>>> Okay, manually checked all the other manually flagged files, and they
> all
> >>>> check out in pom.xml or LICENSE.
> >>>>
> >>>> I am +1 on this release.
> >>>>
> >>>> For the next release, please can we:
> >>>>
> >>>> 1) Prepare a DecCloud AMI
> >>>> 2) Improve the test procedure
> >>>> 3) Fix up the XSL license headers
> >>>>
> >>>> Thanks!
> >>>>
> >>>> On 28 October 2012 17:00, Sebastien Goasguen <ru...@gmail.com>
> wrote:
> >>>>
> >>>>>
> >>>>> On Oct 28, 2012, at 5:48 PM, Noah Slater <ns...@apache.org> wrote:
> >>>>>
> >>>>> > I was expecting a VM for the storage thing. But that never
> appeared. I
> >>>>> did
> >>>>> > see a line for the VM I created. Either way, this testing step
> should
> >>>>> > indicate *clearly* what I should be looking for before moving on.
> >>>>> >
> >>>>> > As it stands, CloudStack itself is now refusing to answer HTTP
> >>>>> requests, so
> >>>>> > I am unable to complete the configuration change step. I am close
> to
> >>>>> giving
> >>>>> > up. This has been an incredibly frustrating experience.
> >>>>>
> >>>>> It should not be that frustrating.
> >>>>>
> >>>>> It's not clear to me where you stand and what you are doing.
> >>>>> I presume you are following the test procedure pointed by Chip.
> >>>>> I also presume you successfully checked the keys etc..and managed to
> >>>>> build and deploy and are running CS via rdebug.
> >>>>> I also presume that you managed to configure the infra by hand…did
> >>>>> everything turn green ? Is the zone enabled ?
> >>>>>
> >>>>> Can you give us more info or maybe ask on IRC ?
> >>>>>
> >>>>> -sebastien
> >>>>>
> >>>>> >
> >>>>> > On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com>
> wrote:
> >>>>> >
> >>>>> >>
> >>>>> >> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org>
> wrote:
> >>>>> >>
> >>>>> >>> Okay,
> >>>>> >>>
> >>>>> >>> I did a rebuild and the menu populated. Very strange.
> >>>>> >>>
> >>>>> >>> Now I have two more problems.
> >>>>> >>>
> >>>>> >>> From the test procedure:
> >>>>> >>>
> >>>>> >>> Wait for secondary storage VM coming up.
> >>>>> >>>> This may take a bit...
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> No clue about this. How do I know when the storage VM has come
> up?
> >>>>> >>
> >>>>> >> In the Infrastructure tab, do you see system VMs in running state
> ?
> >>>>> >> Check my video for help :)
> >>>>> >> https://vimeo.com/52150218
> >>>>> >>
> >>>>> >> PS: I ran the testing procedure on my mac air, and it was
> exceptionally
> >>>>> >> fast. I was amazed.
> >>>>> >>
> >>>>> >>
> >>>>> >>>
> >>>>> >>> I checked under instances and storage and nothing changed for
> about 10
> >>>>> >>> minutes.
> >>>>> >>>
> >>>>> >>> Last three lines in console are:
> >>>>> >>>
> >>>>> >>> [sshexec]      [java] WARN
>  [network.element.VpcVirtualRouterElement]
> >>>>> >>> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated
> with any
> >>>>> >> VPC
> >>>>> >>> [sshexec]      [java] INFO
>  [network.security.SecurityGroupListener]
> >>>>> >>> (AgentManager-Handler-2:) Received a host startup notification
> >>>>> >>> [sshexec]      [java] INFO
> >>>>>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> >>>>> >>> (AgentManager-Handler-2:) Successfully sent out command to start
> HTTP
> >>>>> >>> handling in console proxy agent
> >>>>> >>>
> >>>>> >>> I decided to proceed to the next stage, on the off chance it had
> >>>>> worked.
> >>>>> >>>
> >>>>> >>> I get stuck on this step:
> >>>>> >>>
> >>>>> >>> In step 2, select "tiny Linux"
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> There are no templates to select from!
> >>>>> >>>
> >>>>> >>>
> >>>>> >>
> >>>>>
> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
> >>>>> >>>
> >>>>> >>
> >>>>>
> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
> >>>>> >>>
> >>>>> >>
> >>>>>
> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
> >>>>> >>>
> >>>>> >>> I am unable to proceed.
> >>>>> >>>
> >>>>> >>> P.S. Testing CloudStack on my MBA is exceptionally slow. Is
> there any
> >>>>> way
> >>>>> >>> to do the whole thing on or something? I practically cannot do
> >>>>> anything
> >>>>> >>> else on my computer while testing.
> >>>>> >>>
> >>>>> >>> On 28 October 2012 00:12, Chip Childers <
> chip.childers@sungard.com>
> >>>>> >> wrote:
> >>>>> >>>
> >>>>> >>>> Yeah.  Funny enough, that IS the infra menu option.
> >>>>> >>>>
> >>>>> >>>> I've never seen this before.
> >>>>> >>>>
> >>>>> >>>> I assume you are logged in as admin / password?  Can you do a
> fresh
> >>>>> >>>> build (start with "ant clean-all build-all")?
> >>>>> >>>>
> >>>>> >>>> - chip
> >>>>> >>>>
> >>>>> >>>> Sent from my iPhone.
> >>>>> >>>>
> >>>>> >>>> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org>
> wrote:
> >>>>> >>>>
> >>>>> >>>>> I doubt it. Looks like part of the application code.
> >>>>> >>>>>
> >>>>> >>>>> My real problem is that I am unable to complete this step, as
> there
> >>>>> is
> >>>>> >>>>> nothing labeled "Infrastructure" in the UI.
> >>>>> >>>>>
> >>>>> >>>>> On 27 October 2012 19:04, Chip Childers <
> chip.childers@sungard.com>
> >>>>> >>>> wrote:
> >>>>> >>>>>
> >>>>> >>>>>> Comments below:
> >>>>> >>>>>>
> >>>>> >>>>>> - chip
> >>>>> >>>>>>
> >>>>> >>>>>> Sent from my iPhone.
> >>>>> >>>>>>
> >>>>> >>>>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org>
> >>>>> wrote:
> >>>>> >>>>>>
> >>>>> >>>>>>> Sig: OK
> >>>>> >>>>>>> Hashes: OK
> >>>>> >>>>>>> Source checks: OK
> >>>>> >>>>>>> RAT: OK
> >>>>> >>>>>>> Build: OK
> >>>>> >>>>>>>
> >>>>> >>>>>>> However, during this:
> >>>>> >>>>>>>
> >>>>> >>>>>>> mvn -P deps
> >>>>> >>>>>>>
> >>>>> >>>>>>> I noticed line like this:
> >>>>> >>>>>>>
> >>>>> >>>>>>> [INFO] Installing
> >>>>> >>>>>>>>
> >>>>> >>
> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
> >>>>> >>>>>> to
> >>>>> >>>>>>
> >>>>> >>>>
> >>>>> >>
> >>>>>
> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> >>>>> >>>>>>>> [INFO]
> >>>>> >>>>>>>>
> >>>>> >>>>>>>> [INFO]
> >>>>> >>>>>>>>
> >>>>> >>>>
> >>>>>
> ------------------------------------------------------------------------
> >>>>> >>>>>>>> [INFO] Building Apache CloudStack Utils
> 4.0.0-incubating-SNAPSHOT
> >>>>> >>>>>>>> [INFO]
> >>>>> >>>>>>>>
> >>>>> >>>>
> >>>>>
> ------------------------------------------------------------------------
> >>>>> >>>>>>>
> >>>>> >>>>>>>
> >>>>> >>>>>>> Any idea why that says incubating-SNAPSHOT?
> >>>>> >>>>>>
> >>>>> >>>>>> That's the default build version. If we do a binary release,
> it
> >>>>> would
> >>>>> >>>>>> be changed via the maven release tools.
> >>>>> >>>>>>
> >>>>> >>>>>>>
> >>>>> >>>>>>> A bigger problem is that I am stuck with the additional
> testing.
> >>>>> >>>>>>>
> >>>>> >>>>>>> Specifically, this step:
> >>>>> >>>>>>>
> >>>>> >>>>>>> Click "Infrastructure", click the "View All" button in the
> "Zones"
> >>>>> >>>>>> display
> >>>>> >>>>>>>> box, click "add zone"
> >>>>> >>>>>>>
> >>>>> >>>>>>>
> >>>>> >>>>>>> Here's what my console looks like:
> >>>>> >>>>>>
> >>>>> >>>>
> >>>>> >>
> >>>>>
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
> >>>>> >>>>>>>
> >>>>> >>>>>>> Note the oddly unlabelled cloud icon, which when clicked,
> >>>>> displays:
> >>>>> >>>>>>
> >>>>> >>>>
> >>>>> >>
> >>>>>
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
> >>>>> >>>>>>>
> >>>>> >>>>>>> I would like to be able to complete this testing, but would
> be
> >>>>> >> prepared
> >>>>> >>>>>> to
> >>>>> >>>>>>> vote without it.
> >>>>> >>>>>>>
> >>>>> >>>>>>> Can someone help me?
> >>>>> >>>>>>
> >>>>> >>>>>> Browser specific issue?  Is it consistent?
> >>>>> >>>>>>
> >>>>> >>>>>>>
> >>>>> >>>>>>> thanks,
> >>>>> >>>>>>>
> >>>>> >>>>>>> --
> >>>>> >>>>>>> NS
> >>>>> >>>>>
> >>>>> >>>>>
> >>>>> >>>>>
> >>>>> >>>>> --
> >>>>> >>>>> NS
> >>>>> >>>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> --
> >>>>> >>> NS
> >>>>> >>
> >>>>> >>
> >>>>> >
> >>>>> >
> >>>>> > --
> >>>>> > NS
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> NS
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> NS
>



-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Mon, Oct 29, 2012 at 10:10 AM, Chip Childers
<ch...@sungard.com> wrote:
> On Sun, Oct 28, 2012 at 8:01 PM, Chip Childers
> <ch...@sungard.com> wrote:
>> On Sun, Oct 28, 2012 at 1:53 PM, Noah Slater <ns...@apache.org> wrote:
>>> Actually, sorry, I probably gave that +1 a *little* too soon.
>>>
>>> Can someone make the case for "waf" not being a release blocker?
>>>
>>> Everything else can probably slide.
>>
>> Waf needs to go.  No doubt about it.  However, I'm not certain it's a
>> blocker for a release.  Here's my reasoning:
>>
>> Waf is being removed from the project entirely (ongoing work in
>> origin/maven-to-rpm), so we're not doing something that isn't already
>> targeted for being undone as fast as possible.   The important thing
>> to me is understanding that work to remove waf is taking longer than
>> the community desire to get a release completed at the end of the
>> summer.  It's one line of bytecode within a file that is not core to
>> the project itself (it's only a build utility), that has a clearly
>> marked license for file itself (so distribution is OK), that is only
>> used as a quick way to create packages for Linux distros (not to do
>> the actual project compilation), and that will be ignored by any
>> distro packagers that want to create proper RPMs / DEBs anyway.
>>
>> Thoughts?
>>
>> -chip
>
> Noah has raised the question on general@i.a.o, and I'm holding off on
> closing this vote to get some comments back from the incubator.
>
> -chip

One more follow up.  The discussion on general@i.a.o seems to be
reaching the consensus that we will be ok with the waf file (but
really should remove it).  I'm going to wait until tomorrow morning US
ET to close the vote down, giving the folks on general@ time to raise
any additional concerns.

>
>>> On 28 October 2012 17:51, Noah Slater <ns...@apache.org> wrote:
>>>
>>>> It is frustrating because everything is so slow, and my (main) computer is
>>>> practically unusable while it is running. How feasible would it be to
>>>> provide this DevCloud thing as an AMI? I would much prefer to do this in
>>>> the cloud.
>>>>
>>>> Okay, I made it to this step:
>>>>
>>>> Additional Testing
>>>>
>>>> The instance is removed from the web console.
>>>>
>>>> And this is what I see on the terminal:
>>>>
>>>>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>>> (AgentManager-Handler-6:) VM 3 lost host info, failed authentication request
>>>>   [sshexec]
>>>>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>>> (AgentManager-Handler-8:) VM 3 lost host info, failed authentication request
>>>>   [sshexec]
>>>>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>>> (AgentManager-Handler-9:) VM 3 lost host info, failed authentication request
>>>>   [sshexec]
>>>>   [sshexec]      [java] INFO  [cloud.vm.UserVmManagerImpl]
>>>> (UserVm-Scavenger-1:) Found 1 vms to expunge.
>>>>   [sshexec]
>>>>   [sshexec]      [java] INFO  [network.security.SecurityGroupManagerImpl]
>>>> (UserVm-Scavenger-1:) Disassociated 1 network groups  from uservm 3
>>>>   [sshexec]
>>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>>>> (HA-Worker-1:work-2) Processing HAWork[2-HA-4-Stopped-Scheduled]
>>>>   [sshexec]
>>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>>>> (HA-Worker-1:work-2) HA on VM[DomainRouter|r-4-TEST]
>>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>>>> (HA-Worker-1:work-2) VM VM[DomainRouter|r-4-TEST] has been changed.
>>>>  Current State = Running Previous State = Stopped last updated = 10
>>>> previous updated = 7
>>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>>>> (HA-Worker-1:work-2) Completed HAWork[2-HA-4-Stopped-Scheduled]
>>>>
>>>> However, from devcloud, I see this:
>>>>
>>>> root@devcloud:~# xe vm-list
>>>> uuid ( RO)           : 83fdea03-9d67-d5dc-e090-0acba65e7926
>>>>      name-label ( RW): r-4-TEST
>>>>     power-state ( RO): running
>>>>
>>>>
>>>> uuid ( RO)           : f01b195e-074b-e8f2-f8b1-b2c493070c8a
>>>>      name-label ( RW): Control domain on host: devcloud
>>>>     power-state ( RO): running
>>>>
>>>>
>>>> uuid ( RO)           : 2ab8057a-767e-b700-53e3-861f2e23823a
>>>>      name-label ( RW): s-1-TEST
>>>>     power-state ( RO): running
>>>>
>>>>
>>>> uuid ( RO)           : 8b27e755-4486-e27e-ee7a-6e5bc6ea768f
>>>>      name-label ( RW): v-2-TEST
>>>>     power-state ( RO): running
>>>>
>>>> This looks, to my untrained eyes, like the VM might still be running, and
>>>> in fact that there might be more than one?
>>>>
>>>> Okay, at this point, if someone can clarify that issues (or not?) I have
>>>> run into with the functional tests are not release blockers, I am happy to
>>>> just shut up about them and hope that testing is made easier for the next
>>>> release.
>>>>
>>>> Just moving on now to some more thorough testing.
>>>>
>>>> My manual license check seems satisfactory.
>>>>
>>>> We're still shipping the "waf" binary in the root of our source, and I
>>>> don't understand why. I know I was asked about this during the last round.
>>>> And to be honest, I do not know whether it's a blocker. Can someone clarify
>>>> for me why it is used, and why we can't ship the source instead?
>>>>
>>>> Manual file type test: OK
>>>>
>>>> Okay, going through some files by hand.
>>>>
>>>> The following files do not have copyright headers:
>>>>
>>>> setup/apidoc/generateadmincommands.xsl
>>>> setup/apidoc/generatecommand.xsl
>>>> setup/apidoc/generatedomainadmincommands.xsl
>>>> setup/apidoc/generatetoc_footer.xsl
>>>> setup/apidoc/generateusercommands.xsl
>>>>
>>>> I do not consider this a release blocker, but these should be fixed (where
>>>> possible) for the next release.
>>>>
>>>> I almost raised a blocked with the files I found under tools/marvin,
>>>> before I remembered our discussion about them. Heh!
>>>>
>>>> Okay, manually checked all the other manually flagged files, and they all
>>>> check out in pom.xml or LICENSE.
>>>>
>>>> I am +1 on this release.
>>>>
>>>> For the next release, please can we:
>>>>
>>>> 1) Prepare a DecCloud AMI
>>>> 2) Improve the test procedure
>>>> 3) Fix up the XSL license headers
>>>>
>>>> Thanks!
>>>>
>>>> On 28 October 2012 17:00, Sebastien Goasguen <ru...@gmail.com> wrote:
>>>>
>>>>>
>>>>> On Oct 28, 2012, at 5:48 PM, Noah Slater <ns...@apache.org> wrote:
>>>>>
>>>>> > I was expecting a VM for the storage thing. But that never appeared. I
>>>>> did
>>>>> > see a line for the VM I created. Either way, this testing step should
>>>>> > indicate *clearly* what I should be looking for before moving on.
>>>>> >
>>>>> > As it stands, CloudStack itself is now refusing to answer HTTP
>>>>> requests, so
>>>>> > I am unable to complete the configuration change step. I am close to
>>>>> giving
>>>>> > up. This has been an incredibly frustrating experience.
>>>>>
>>>>> It should not be that frustrating.
>>>>>
>>>>> It's not clear to me where you stand and what you are doing.
>>>>> I presume you are following the test procedure pointed by Chip.
>>>>> I also presume you successfully checked the keys etc..and managed to
>>>>> build and deploy and are running CS via rdebug.
>>>>> I also presume that you managed to configure the infra by hand…did
>>>>> everything turn green ? Is the zone enabled ?
>>>>>
>>>>> Can you give us more info or maybe ask on IRC ?
>>>>>
>>>>> -sebastien
>>>>>
>>>>> >
>>>>> > On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com> wrote:
>>>>> >
>>>>> >>
>>>>> >> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:
>>>>> >>
>>>>> >>> Okay,
>>>>> >>>
>>>>> >>> I did a rebuild and the menu populated. Very strange.
>>>>> >>>
>>>>> >>> Now I have two more problems.
>>>>> >>>
>>>>> >>> From the test procedure:
>>>>> >>>
>>>>> >>> Wait for secondary storage VM coming up.
>>>>> >>>> This may take a bit...
>>>>> >>>
>>>>> >>>
>>>>> >>> No clue about this. How do I know when the storage VM has come up?
>>>>> >>
>>>>> >> In the Infrastructure tab, do you see system VMs in running state ?
>>>>> >> Check my video for help :)
>>>>> >> https://vimeo.com/52150218
>>>>> >>
>>>>> >> PS: I ran the testing procedure on my mac air, and it was exceptionally
>>>>> >> fast. I was amazed.
>>>>> >>
>>>>> >>
>>>>> >>>
>>>>> >>> I checked under instances and storage and nothing changed for about 10
>>>>> >>> minutes.
>>>>> >>>
>>>>> >>> Last three lines in console are:
>>>>> >>>
>>>>> >>> [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
>>>>> >>> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any
>>>>> >> VPC
>>>>> >>> [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
>>>>> >>> (AgentManager-Handler-2:) Received a host startup notification
>>>>> >>> [sshexec]      [java] INFO
>>>>>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>>>> >>> (AgentManager-Handler-2:) Successfully sent out command to start HTTP
>>>>> >>> handling in console proxy agent
>>>>> >>>
>>>>> >>> I decided to proceed to the next stage, on the off chance it had
>>>>> worked.
>>>>> >>>
>>>>> >>> I get stuck on this step:
>>>>> >>>
>>>>> >>> In step 2, select "tiny Linux"
>>>>> >>>
>>>>> >>>
>>>>> >>> There are no templates to select from!
>>>>> >>>
>>>>> >>>
>>>>> >>
>>>>> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
>>>>> >>>
>>>>> >>
>>>>> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
>>>>> >>>
>>>>> >>
>>>>> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
>>>>> >>>
>>>>> >>> I am unable to proceed.
>>>>> >>>
>>>>> >>> P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any
>>>>> way
>>>>> >>> to do the whole thing on or something? I practically cannot do
>>>>> anything
>>>>> >>> else on my computer while testing.
>>>>> >>>
>>>>> >>> On 28 October 2012 00:12, Chip Childers <ch...@sungard.com>
>>>>> >> wrote:
>>>>> >>>
>>>>> >>>> Yeah.  Funny enough, that IS the infra menu option.
>>>>> >>>>
>>>>> >>>> I've never seen this before.
>>>>> >>>>
>>>>> >>>> I assume you are logged in as admin / password?  Can you do a fresh
>>>>> >>>> build (start with "ant clean-all build-all")?
>>>>> >>>>
>>>>> >>>> - chip
>>>>> >>>>
>>>>> >>>> Sent from my iPhone.
>>>>> >>>>
>>>>> >>>> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>>>>> >>>>
>>>>> >>>>> I doubt it. Looks like part of the application code.
>>>>> >>>>>
>>>>> >>>>> My real problem is that I am unable to complete this step, as there
>>>>> is
>>>>> >>>>> nothing labeled "Infrastructure" in the UI.
>>>>> >>>>>
>>>>> >>>>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
>>>>> >>>> wrote:
>>>>> >>>>>
>>>>> >>>>>> Comments below:
>>>>> >>>>>>
>>>>> >>>>>> - chip
>>>>> >>>>>>
>>>>> >>>>>> Sent from my iPhone.
>>>>> >>>>>>
>>>>> >>>>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org>
>>>>> wrote:
>>>>> >>>>>>
>>>>> >>>>>>> Sig: OK
>>>>> >>>>>>> Hashes: OK
>>>>> >>>>>>> Source checks: OK
>>>>> >>>>>>> RAT: OK
>>>>> >>>>>>> Build: OK
>>>>> >>>>>>>
>>>>> >>>>>>> However, during this:
>>>>> >>>>>>>
>>>>> >>>>>>> mvn -P deps
>>>>> >>>>>>>
>>>>> >>>>>>> I noticed line like this:
>>>>> >>>>>>>
>>>>> >>>>>>> [INFO] Installing
>>>>> >>>>>>>>
>>>>> >> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
>>>>> >>>>>> to
>>>>> >>>>>>
>>>>> >>>>
>>>>> >>
>>>>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>>>>> >>>>>>>> [INFO]
>>>>> >>>>>>>>
>>>>> >>>>>>>> [INFO]
>>>>> >>>>>>>>
>>>>> >>>>
>>>>> ------------------------------------------------------------------------
>>>>> >>>>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>>>>> >>>>>>>> [INFO]
>>>>> >>>>>>>>
>>>>> >>>>
>>>>> ------------------------------------------------------------------------
>>>>> >>>>>>>
>>>>> >>>>>>>
>>>>> >>>>>>> Any idea why that says incubating-SNAPSHOT?
>>>>> >>>>>>
>>>>> >>>>>> That's the default build version. If we do a binary release, it
>>>>> would
>>>>> >>>>>> be changed via the maven release tools.
>>>>> >>>>>>
>>>>> >>>>>>>
>>>>> >>>>>>> A bigger problem is that I am stuck with the additional testing.
>>>>> >>>>>>>
>>>>> >>>>>>> Specifically, this step:
>>>>> >>>>>>>
>>>>> >>>>>>> Click "Infrastructure", click the "View All" button in the "Zones"
>>>>> >>>>>> display
>>>>> >>>>>>>> box, click "add zone"
>>>>> >>>>>>>
>>>>> >>>>>>>
>>>>> >>>>>>> Here's what my console looks like:
>>>>> >>>>>>
>>>>> >>>>
>>>>> >>
>>>>> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>>>>> >>>>>>>
>>>>> >>>>>>> Note the oddly unlabelled cloud icon, which when clicked,
>>>>> displays:
>>>>> >>>>>>
>>>>> >>>>
>>>>> >>
>>>>> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>>>>> >>>>>>>
>>>>> >>>>>>> I would like to be able to complete this testing, but would be
>>>>> >> prepared
>>>>> >>>>>> to
>>>>> >>>>>>> vote without it.
>>>>> >>>>>>>
>>>>> >>>>>>> Can someone help me?
>>>>> >>>>>>
>>>>> >>>>>> Browser specific issue?  Is it consistent?
>>>>> >>>>>>
>>>>> >>>>>>>
>>>>> >>>>>>> thanks,
>>>>> >>>>>>>
>>>>> >>>>>>> --
>>>>> >>>>>>> NS
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>>
>>>>> >>>>> --
>>>>> >>>>> NS
>>>>> >>>>
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> --
>>>>> >>> NS
>>>>> >>
>>>>> >>
>>>>> >
>>>>> >
>>>>> > --
>>>>> > NS
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> NS
>>>>
>>>
>>>
>>>
>>> --
>>> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Sun, Oct 28, 2012 at 8:01 PM, Chip Childers
<ch...@sungard.com> wrote:
> On Sun, Oct 28, 2012 at 1:53 PM, Noah Slater <ns...@apache.org> wrote:
>> Actually, sorry, I probably gave that +1 a *little* too soon.
>>
>> Can someone make the case for "waf" not being a release blocker?
>>
>> Everything else can probably slide.
>
> Waf needs to go.  No doubt about it.  However, I'm not certain it's a
> blocker for a release.  Here's my reasoning:
>
> Waf is being removed from the project entirely (ongoing work in
> origin/maven-to-rpm), so we're not doing something that isn't already
> targeted for being undone as fast as possible.   The important thing
> to me is understanding that work to remove waf is taking longer than
> the community desire to get a release completed at the end of the
> summer.  It's one line of bytecode within a file that is not core to
> the project itself (it's only a build utility), that has a clearly
> marked license for file itself (so distribution is OK), that is only
> used as a quick way to create packages for Linux distros (not to do
> the actual project compilation), and that will be ignored by any
> distro packagers that want to create proper RPMs / DEBs anyway.
>
> Thoughts?
>
> -chip

Noah has raised the question on general@i.a.o, and I'm holding off on
closing this vote to get some comments back from the incubator.

-chip

>> On 28 October 2012 17:51, Noah Slater <ns...@apache.org> wrote:
>>
>>> It is frustrating because everything is so slow, and my (main) computer is
>>> practically unusable while it is running. How feasible would it be to
>>> provide this DevCloud thing as an AMI? I would much prefer to do this in
>>> the cloud.
>>>
>>> Okay, I made it to this step:
>>>
>>> Additional Testing
>>>
>>> The instance is removed from the web console.
>>>
>>> And this is what I see on the terminal:
>>>
>>>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>> (AgentManager-Handler-6:) VM 3 lost host info, failed authentication request
>>>   [sshexec]
>>>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>> (AgentManager-Handler-8:) VM 3 lost host info, failed authentication request
>>>   [sshexec]
>>>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>> (AgentManager-Handler-9:) VM 3 lost host info, failed authentication request
>>>   [sshexec]
>>>   [sshexec]      [java] INFO  [cloud.vm.UserVmManagerImpl]
>>> (UserVm-Scavenger-1:) Found 1 vms to expunge.
>>>   [sshexec]
>>>   [sshexec]      [java] INFO  [network.security.SecurityGroupManagerImpl]
>>> (UserVm-Scavenger-1:) Disassociated 1 network groups  from uservm 3
>>>   [sshexec]
>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>>> (HA-Worker-1:work-2) Processing HAWork[2-HA-4-Stopped-Scheduled]
>>>   [sshexec]
>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>>> (HA-Worker-1:work-2) HA on VM[DomainRouter|r-4-TEST]
>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>>> (HA-Worker-1:work-2) VM VM[DomainRouter|r-4-TEST] has been changed.
>>>  Current State = Running Previous State = Stopped last updated = 10
>>> previous updated = 7
>>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>>> (HA-Worker-1:work-2) Completed HAWork[2-HA-4-Stopped-Scheduled]
>>>
>>> However, from devcloud, I see this:
>>>
>>> root@devcloud:~# xe vm-list
>>> uuid ( RO)           : 83fdea03-9d67-d5dc-e090-0acba65e7926
>>>      name-label ( RW): r-4-TEST
>>>     power-state ( RO): running
>>>
>>>
>>> uuid ( RO)           : f01b195e-074b-e8f2-f8b1-b2c493070c8a
>>>      name-label ( RW): Control domain on host: devcloud
>>>     power-state ( RO): running
>>>
>>>
>>> uuid ( RO)           : 2ab8057a-767e-b700-53e3-861f2e23823a
>>>      name-label ( RW): s-1-TEST
>>>     power-state ( RO): running
>>>
>>>
>>> uuid ( RO)           : 8b27e755-4486-e27e-ee7a-6e5bc6ea768f
>>>      name-label ( RW): v-2-TEST
>>>     power-state ( RO): running
>>>
>>> This looks, to my untrained eyes, like the VM might still be running, and
>>> in fact that there might be more than one?
>>>
>>> Okay, at this point, if someone can clarify that issues (or not?) I have
>>> run into with the functional tests are not release blockers, I am happy to
>>> just shut up about them and hope that testing is made easier for the next
>>> release.
>>>
>>> Just moving on now to some more thorough testing.
>>>
>>> My manual license check seems satisfactory.
>>>
>>> We're still shipping the "waf" binary in the root of our source, and I
>>> don't understand why. I know I was asked about this during the last round.
>>> And to be honest, I do not know whether it's a blocker. Can someone clarify
>>> for me why it is used, and why we can't ship the source instead?
>>>
>>> Manual file type test: OK
>>>
>>> Okay, going through some files by hand.
>>>
>>> The following files do not have copyright headers:
>>>
>>> setup/apidoc/generateadmincommands.xsl
>>> setup/apidoc/generatecommand.xsl
>>> setup/apidoc/generatedomainadmincommands.xsl
>>> setup/apidoc/generatetoc_footer.xsl
>>> setup/apidoc/generateusercommands.xsl
>>>
>>> I do not consider this a release blocker, but these should be fixed (where
>>> possible) for the next release.
>>>
>>> I almost raised a blocked with the files I found under tools/marvin,
>>> before I remembered our discussion about them. Heh!
>>>
>>> Okay, manually checked all the other manually flagged files, and they all
>>> check out in pom.xml or LICENSE.
>>>
>>> I am +1 on this release.
>>>
>>> For the next release, please can we:
>>>
>>> 1) Prepare a DecCloud AMI
>>> 2) Improve the test procedure
>>> 3) Fix up the XSL license headers
>>>
>>> Thanks!
>>>
>>> On 28 October 2012 17:00, Sebastien Goasguen <ru...@gmail.com> wrote:
>>>
>>>>
>>>> On Oct 28, 2012, at 5:48 PM, Noah Slater <ns...@apache.org> wrote:
>>>>
>>>> > I was expecting a VM for the storage thing. But that never appeared. I
>>>> did
>>>> > see a line for the VM I created. Either way, this testing step should
>>>> > indicate *clearly* what I should be looking for before moving on.
>>>> >
>>>> > As it stands, CloudStack itself is now refusing to answer HTTP
>>>> requests, so
>>>> > I am unable to complete the configuration change step. I am close to
>>>> giving
>>>> > up. This has been an incredibly frustrating experience.
>>>>
>>>> It should not be that frustrating.
>>>>
>>>> It's not clear to me where you stand and what you are doing.
>>>> I presume you are following the test procedure pointed by Chip.
>>>> I also presume you successfully checked the keys etc..and managed to
>>>> build and deploy and are running CS via rdebug.
>>>> I also presume that you managed to configure the infra by hand…did
>>>> everything turn green ? Is the zone enabled ?
>>>>
>>>> Can you give us more info or maybe ask on IRC ?
>>>>
>>>> -sebastien
>>>>
>>>> >
>>>> > On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com> wrote:
>>>> >
>>>> >>
>>>> >> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:
>>>> >>
>>>> >>> Okay,
>>>> >>>
>>>> >>> I did a rebuild and the menu populated. Very strange.
>>>> >>>
>>>> >>> Now I have two more problems.
>>>> >>>
>>>> >>> From the test procedure:
>>>> >>>
>>>> >>> Wait for secondary storage VM coming up.
>>>> >>>> This may take a bit...
>>>> >>>
>>>> >>>
>>>> >>> No clue about this. How do I know when the storage VM has come up?
>>>> >>
>>>> >> In the Infrastructure tab, do you see system VMs in running state ?
>>>> >> Check my video for help :)
>>>> >> https://vimeo.com/52150218
>>>> >>
>>>> >> PS: I ran the testing procedure on my mac air, and it was exceptionally
>>>> >> fast. I was amazed.
>>>> >>
>>>> >>
>>>> >>>
>>>> >>> I checked under instances and storage and nothing changed for about 10
>>>> >>> minutes.
>>>> >>>
>>>> >>> Last three lines in console are:
>>>> >>>
>>>> >>> [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
>>>> >>> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any
>>>> >> VPC
>>>> >>> [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
>>>> >>> (AgentManager-Handler-2:) Received a host startup notification
>>>> >>> [sshexec]      [java] INFO
>>>>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>>> >>> (AgentManager-Handler-2:) Successfully sent out command to start HTTP
>>>> >>> handling in console proxy agent
>>>> >>>
>>>> >>> I decided to proceed to the next stage, on the off chance it had
>>>> worked.
>>>> >>>
>>>> >>> I get stuck on this step:
>>>> >>>
>>>> >>> In step 2, select "tiny Linux"
>>>> >>>
>>>> >>>
>>>> >>> There are no templates to select from!
>>>> >>>
>>>> >>>
>>>> >>
>>>> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
>>>> >>>
>>>> >>
>>>> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
>>>> >>>
>>>> >>
>>>> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
>>>> >>>
>>>> >>> I am unable to proceed.
>>>> >>>
>>>> >>> P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any
>>>> way
>>>> >>> to do the whole thing on or something? I practically cannot do
>>>> anything
>>>> >>> else on my computer while testing.
>>>> >>>
>>>> >>> On 28 October 2012 00:12, Chip Childers <ch...@sungard.com>
>>>> >> wrote:
>>>> >>>
>>>> >>>> Yeah.  Funny enough, that IS the infra menu option.
>>>> >>>>
>>>> >>>> I've never seen this before.
>>>> >>>>
>>>> >>>> I assume you are logged in as admin / password?  Can you do a fresh
>>>> >>>> build (start with "ant clean-all build-all")?
>>>> >>>>
>>>> >>>> - chip
>>>> >>>>
>>>> >>>> Sent from my iPhone.
>>>> >>>>
>>>> >>>> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>>>> >>>>
>>>> >>>>> I doubt it. Looks like part of the application code.
>>>> >>>>>
>>>> >>>>> My real problem is that I am unable to complete this step, as there
>>>> is
>>>> >>>>> nothing labeled "Infrastructure" in the UI.
>>>> >>>>>
>>>> >>>>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
>>>> >>>> wrote:
>>>> >>>>>
>>>> >>>>>> Comments below:
>>>> >>>>>>
>>>> >>>>>> - chip
>>>> >>>>>>
>>>> >>>>>> Sent from my iPhone.
>>>> >>>>>>
>>>> >>>>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org>
>>>> wrote:
>>>> >>>>>>
>>>> >>>>>>> Sig: OK
>>>> >>>>>>> Hashes: OK
>>>> >>>>>>> Source checks: OK
>>>> >>>>>>> RAT: OK
>>>> >>>>>>> Build: OK
>>>> >>>>>>>
>>>> >>>>>>> However, during this:
>>>> >>>>>>>
>>>> >>>>>>> mvn -P deps
>>>> >>>>>>>
>>>> >>>>>>> I noticed line like this:
>>>> >>>>>>>
>>>> >>>>>>> [INFO] Installing
>>>> >>>>>>>>
>>>> >> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
>>>> >>>>>> to
>>>> >>>>>>
>>>> >>>>
>>>> >>
>>>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>>>> >>>>>>>> [INFO]
>>>> >>>>>>>>
>>>> >>>>>>>> [INFO]
>>>> >>>>>>>>
>>>> >>>>
>>>> ------------------------------------------------------------------------
>>>> >>>>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>>>> >>>>>>>> [INFO]
>>>> >>>>>>>>
>>>> >>>>
>>>> ------------------------------------------------------------------------
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>> Any idea why that says incubating-SNAPSHOT?
>>>> >>>>>>
>>>> >>>>>> That's the default build version. If we do a binary release, it
>>>> would
>>>> >>>>>> be changed via the maven release tools.
>>>> >>>>>>
>>>> >>>>>>>
>>>> >>>>>>> A bigger problem is that I am stuck with the additional testing.
>>>> >>>>>>>
>>>> >>>>>>> Specifically, this step:
>>>> >>>>>>>
>>>> >>>>>>> Click "Infrastructure", click the "View All" button in the "Zones"
>>>> >>>>>> display
>>>> >>>>>>>> box, click "add zone"
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>> Here's what my console looks like:
>>>> >>>>>>
>>>> >>>>
>>>> >>
>>>> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>>>> >>>>>>>
>>>> >>>>>>> Note the oddly unlabelled cloud icon, which when clicked,
>>>> displays:
>>>> >>>>>>
>>>> >>>>
>>>> >>
>>>> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>>>> >>>>>>>
>>>> >>>>>>> I would like to be able to complete this testing, but would be
>>>> >> prepared
>>>> >>>>>> to
>>>> >>>>>>> vote without it.
>>>> >>>>>>>
>>>> >>>>>>> Can someone help me?
>>>> >>>>>>
>>>> >>>>>> Browser specific issue?  Is it consistent?
>>>> >>>>>>
>>>> >>>>>>>
>>>> >>>>>>> thanks,
>>>> >>>>>>>
>>>> >>>>>>> --
>>>> >>>>>>> NS
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> --
>>>> >>>>> NS
>>>> >>>>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> --
>>>> >>> NS
>>>> >>
>>>> >>
>>>> >
>>>> >
>>>> > --
>>>> > NS
>>>>
>>>>
>>>
>>>
>>> --
>>> NS
>>>
>>
>>
>>
>> --
>> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Sun, Oct 28, 2012 at 1:53 PM, Noah Slater <ns...@apache.org> wrote:
> Actually, sorry, I probably gave that +1 a *little* too soon.
>
> Can someone make the case for "waf" not being a release blocker?
>
> Everything else can probably slide.

Waf needs to go.  No doubt about it.  However, I'm not certain it's a
blocker for a release.  Here's my reasoning:

Waf is being removed from the project entirely (ongoing work in
origin/maven-to-rpm), so we're not doing something that isn't already
targeted for being undone as fast as possible.   The important thing
to me is understanding that work to remove waf is taking longer than
the community desire to get a release completed at the end of the
summer.  It's one line of bytecode within a file that is not core to
the project itself (it's only a build utility), that has a clearly
marked license for file itself (so distribution is OK), that is only
used as a quick way to create packages for Linux distros (not to do
the actual project compilation), and that will be ignored by any
distro packagers that want to create proper RPMs / DEBs anyway.

Thoughts?

-chip

> On 28 October 2012 17:51, Noah Slater <ns...@apache.org> wrote:
>
>> It is frustrating because everything is so slow, and my (main) computer is
>> practically unusable while it is running. How feasible would it be to
>> provide this DevCloud thing as an AMI? I would much prefer to do this in
>> the cloud.
>>
>> Okay, I made it to this step:
>>
>> Additional Testing
>>
>> The instance is removed from the web console.
>>
>> And this is what I see on the terminal:
>>
>>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>> (AgentManager-Handler-6:) VM 3 lost host info, failed authentication request
>>   [sshexec]
>>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>> (AgentManager-Handler-8:) VM 3 lost host info, failed authentication request
>>   [sshexec]
>>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>> (AgentManager-Handler-9:) VM 3 lost host info, failed authentication request
>>   [sshexec]
>>   [sshexec]      [java] INFO  [cloud.vm.UserVmManagerImpl]
>> (UserVm-Scavenger-1:) Found 1 vms to expunge.
>>   [sshexec]
>>   [sshexec]      [java] INFO  [network.security.SecurityGroupManagerImpl]
>> (UserVm-Scavenger-1:) Disassociated 1 network groups  from uservm 3
>>   [sshexec]
>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>> (HA-Worker-1:work-2) Processing HAWork[2-HA-4-Stopped-Scheduled]
>>   [sshexec]
>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>> (HA-Worker-1:work-2) HA on VM[DomainRouter|r-4-TEST]
>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>> (HA-Worker-1:work-2) VM VM[DomainRouter|r-4-TEST] has been changed.
>>  Current State = Running Previous State = Stopped last updated = 10
>> previous updated = 7
>>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
>> (HA-Worker-1:work-2) Completed HAWork[2-HA-4-Stopped-Scheduled]
>>
>> However, from devcloud, I see this:
>>
>> root@devcloud:~# xe vm-list
>> uuid ( RO)           : 83fdea03-9d67-d5dc-e090-0acba65e7926
>>      name-label ( RW): r-4-TEST
>>     power-state ( RO): running
>>
>>
>> uuid ( RO)           : f01b195e-074b-e8f2-f8b1-b2c493070c8a
>>      name-label ( RW): Control domain on host: devcloud
>>     power-state ( RO): running
>>
>>
>> uuid ( RO)           : 2ab8057a-767e-b700-53e3-861f2e23823a
>>      name-label ( RW): s-1-TEST
>>     power-state ( RO): running
>>
>>
>> uuid ( RO)           : 8b27e755-4486-e27e-ee7a-6e5bc6ea768f
>>      name-label ( RW): v-2-TEST
>>     power-state ( RO): running
>>
>> This looks, to my untrained eyes, like the VM might still be running, and
>> in fact that there might be more than one?
>>
>> Okay, at this point, if someone can clarify that issues (or not?) I have
>> run into with the functional tests are not release blockers, I am happy to
>> just shut up about them and hope that testing is made easier for the next
>> release.
>>
>> Just moving on now to some more thorough testing.
>>
>> My manual license check seems satisfactory.
>>
>> We're still shipping the "waf" binary in the root of our source, and I
>> don't understand why. I know I was asked about this during the last round.
>> And to be honest, I do not know whether it's a blocker. Can someone clarify
>> for me why it is used, and why we can't ship the source instead?
>>
>> Manual file type test: OK
>>
>> Okay, going through some files by hand.
>>
>> The following files do not have copyright headers:
>>
>> setup/apidoc/generateadmincommands.xsl
>> setup/apidoc/generatecommand.xsl
>> setup/apidoc/generatedomainadmincommands.xsl
>> setup/apidoc/generatetoc_footer.xsl
>> setup/apidoc/generateusercommands.xsl
>>
>> I do not consider this a release blocker, but these should be fixed (where
>> possible) for the next release.
>>
>> I almost raised a blocked with the files I found under tools/marvin,
>> before I remembered our discussion about them. Heh!
>>
>> Okay, manually checked all the other manually flagged files, and they all
>> check out in pom.xml or LICENSE.
>>
>> I am +1 on this release.
>>
>> For the next release, please can we:
>>
>> 1) Prepare a DecCloud AMI
>> 2) Improve the test procedure
>> 3) Fix up the XSL license headers
>>
>> Thanks!
>>
>> On 28 October 2012 17:00, Sebastien Goasguen <ru...@gmail.com> wrote:
>>
>>>
>>> On Oct 28, 2012, at 5:48 PM, Noah Slater <ns...@apache.org> wrote:
>>>
>>> > I was expecting a VM for the storage thing. But that never appeared. I
>>> did
>>> > see a line for the VM I created. Either way, this testing step should
>>> > indicate *clearly* what I should be looking for before moving on.
>>> >
>>> > As it stands, CloudStack itself is now refusing to answer HTTP
>>> requests, so
>>> > I am unable to complete the configuration change step. I am close to
>>> giving
>>> > up. This has been an incredibly frustrating experience.
>>>
>>> It should not be that frustrating.
>>>
>>> It's not clear to me where you stand and what you are doing.
>>> I presume you are following the test procedure pointed by Chip.
>>> I also presume you successfully checked the keys etc..and managed to
>>> build and deploy and are running CS via rdebug.
>>> I also presume that you managed to configure the infra by hand…did
>>> everything turn green ? Is the zone enabled ?
>>>
>>> Can you give us more info or maybe ask on IRC ?
>>>
>>> -sebastien
>>>
>>> >
>>> > On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com> wrote:
>>> >
>>> >>
>>> >> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:
>>> >>
>>> >>> Okay,
>>> >>>
>>> >>> I did a rebuild and the menu populated. Very strange.
>>> >>>
>>> >>> Now I have two more problems.
>>> >>>
>>> >>> From the test procedure:
>>> >>>
>>> >>> Wait for secondary storage VM coming up.
>>> >>>> This may take a bit...
>>> >>>
>>> >>>
>>> >>> No clue about this. How do I know when the storage VM has come up?
>>> >>
>>> >> In the Infrastructure tab, do you see system VMs in running state ?
>>> >> Check my video for help :)
>>> >> https://vimeo.com/52150218
>>> >>
>>> >> PS: I ran the testing procedure on my mac air, and it was exceptionally
>>> >> fast. I was amazed.
>>> >>
>>> >>
>>> >>>
>>> >>> I checked under instances and storage and nothing changed for about 10
>>> >>> minutes.
>>> >>>
>>> >>> Last three lines in console are:
>>> >>>
>>> >>> [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
>>> >>> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any
>>> >> VPC
>>> >>> [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
>>> >>> (AgentManager-Handler-2:) Received a host startup notification
>>> >>> [sshexec]      [java] INFO
>>>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>> >>> (AgentManager-Handler-2:) Successfully sent out command to start HTTP
>>> >>> handling in console proxy agent
>>> >>>
>>> >>> I decided to proceed to the next stage, on the off chance it had
>>> worked.
>>> >>>
>>> >>> I get stuck on this step:
>>> >>>
>>> >>> In step 2, select "tiny Linux"
>>> >>>
>>> >>>
>>> >>> There are no templates to select from!
>>> >>>
>>> >>>
>>> >>
>>> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
>>> >>>
>>> >>
>>> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
>>> >>>
>>> >>
>>> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
>>> >>>
>>> >>> I am unable to proceed.
>>> >>>
>>> >>> P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any
>>> way
>>> >>> to do the whole thing on or something? I practically cannot do
>>> anything
>>> >>> else on my computer while testing.
>>> >>>
>>> >>> On 28 October 2012 00:12, Chip Childers <ch...@sungard.com>
>>> >> wrote:
>>> >>>
>>> >>>> Yeah.  Funny enough, that IS the infra menu option.
>>> >>>>
>>> >>>> I've never seen this before.
>>> >>>>
>>> >>>> I assume you are logged in as admin / password?  Can you do a fresh
>>> >>>> build (start with "ant clean-all build-all")?
>>> >>>>
>>> >>>> - chip
>>> >>>>
>>> >>>> Sent from my iPhone.
>>> >>>>
>>> >>>> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>>> >>>>
>>> >>>>> I doubt it. Looks like part of the application code.
>>> >>>>>
>>> >>>>> My real problem is that I am unable to complete this step, as there
>>> is
>>> >>>>> nothing labeled "Infrastructure" in the UI.
>>> >>>>>
>>> >>>>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
>>> >>>> wrote:
>>> >>>>>
>>> >>>>>> Comments below:
>>> >>>>>>
>>> >>>>>> - chip
>>> >>>>>>
>>> >>>>>> Sent from my iPhone.
>>> >>>>>>
>>> >>>>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org>
>>> wrote:
>>> >>>>>>
>>> >>>>>>> Sig: OK
>>> >>>>>>> Hashes: OK
>>> >>>>>>> Source checks: OK
>>> >>>>>>> RAT: OK
>>> >>>>>>> Build: OK
>>> >>>>>>>
>>> >>>>>>> However, during this:
>>> >>>>>>>
>>> >>>>>>> mvn -P deps
>>> >>>>>>>
>>> >>>>>>> I noticed line like this:
>>> >>>>>>>
>>> >>>>>>> [INFO] Installing
>>> >>>>>>>>
>>> >> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
>>> >>>>>> to
>>> >>>>>>
>>> >>>>
>>> >>
>>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>>> >>>>>>>> [INFO]
>>> >>>>>>>>
>>> >>>>>>>> [INFO]
>>> >>>>>>>>
>>> >>>>
>>> ------------------------------------------------------------------------
>>> >>>>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>>> >>>>>>>> [INFO]
>>> >>>>>>>>
>>> >>>>
>>> ------------------------------------------------------------------------
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> Any idea why that says incubating-SNAPSHOT?
>>> >>>>>>
>>> >>>>>> That's the default build version. If we do a binary release, it
>>> would
>>> >>>>>> be changed via the maven release tools.
>>> >>>>>>
>>> >>>>>>>
>>> >>>>>>> A bigger problem is that I am stuck with the additional testing.
>>> >>>>>>>
>>> >>>>>>> Specifically, this step:
>>> >>>>>>>
>>> >>>>>>> Click "Infrastructure", click the "View All" button in the "Zones"
>>> >>>>>> display
>>> >>>>>>>> box, click "add zone"
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> Here's what my console looks like:
>>> >>>>>>
>>> >>>>
>>> >>
>>> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>>> >>>>>>>
>>> >>>>>>> Note the oddly unlabelled cloud icon, which when clicked,
>>> displays:
>>> >>>>>>
>>> >>>>
>>> >>
>>> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>>> >>>>>>>
>>> >>>>>>> I would like to be able to complete this testing, but would be
>>> >> prepared
>>> >>>>>> to
>>> >>>>>>> vote without it.
>>> >>>>>>>
>>> >>>>>>> Can someone help me?
>>> >>>>>>
>>> >>>>>> Browser specific issue?  Is it consistent?
>>> >>>>>>
>>> >>>>>>>
>>> >>>>>>> thanks,
>>> >>>>>>>
>>> >>>>>>> --
>>> >>>>>>> NS
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> --
>>> >>>>> NS
>>> >>>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> NS
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > NS
>>>
>>>
>>
>>
>> --
>> NS
>>
>
>
>
> --
> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
Actually, sorry, I probably gave that +1 a *little* too soon.

Can someone make the case for "waf" not being a release blocker?

Everything else can probably slide.

On 28 October 2012 17:51, Noah Slater <ns...@apache.org> wrote:

> It is frustrating because everything is so slow, and my (main) computer is
> practically unusable while it is running. How feasible would it be to
> provide this DevCloud thing as an AMI? I would much prefer to do this in
> the cloud.
>
> Okay, I made it to this step:
>
> Additional Testing
>
> The instance is removed from the web console.
>
> And this is what I see on the terminal:
>
>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (AgentManager-Handler-6:) VM 3 lost host info, failed authentication request
>   [sshexec]
>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (AgentManager-Handler-8:) VM 3 lost host info, failed authentication request
>   [sshexec]
>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (AgentManager-Handler-9:) VM 3 lost host info, failed authentication request
>   [sshexec]
>   [sshexec]      [java] INFO  [cloud.vm.UserVmManagerImpl]
> (UserVm-Scavenger-1:) Found 1 vms to expunge.
>   [sshexec]
>   [sshexec]      [java] INFO  [network.security.SecurityGroupManagerImpl]
> (UserVm-Scavenger-1:) Disassociated 1 network groups  from uservm 3
>   [sshexec]
>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> (HA-Worker-1:work-2) Processing HAWork[2-HA-4-Stopped-Scheduled]
>   [sshexec]
>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> (HA-Worker-1:work-2) HA on VM[DomainRouter|r-4-TEST]
>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> (HA-Worker-1:work-2) VM VM[DomainRouter|r-4-TEST] has been changed.
>  Current State = Running Previous State = Stopped last updated = 10
> previous updated = 7
>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> (HA-Worker-1:work-2) Completed HAWork[2-HA-4-Stopped-Scheduled]
>
> However, from devcloud, I see this:
>
> root@devcloud:~# xe vm-list
> uuid ( RO)           : 83fdea03-9d67-d5dc-e090-0acba65e7926
>      name-label ( RW): r-4-TEST
>     power-state ( RO): running
>
>
> uuid ( RO)           : f01b195e-074b-e8f2-f8b1-b2c493070c8a
>      name-label ( RW): Control domain on host: devcloud
>     power-state ( RO): running
>
>
> uuid ( RO)           : 2ab8057a-767e-b700-53e3-861f2e23823a
>      name-label ( RW): s-1-TEST
>     power-state ( RO): running
>
>
> uuid ( RO)           : 8b27e755-4486-e27e-ee7a-6e5bc6ea768f
>      name-label ( RW): v-2-TEST
>     power-state ( RO): running
>
> This looks, to my untrained eyes, like the VM might still be running, and
> in fact that there might be more than one?
>
> Okay, at this point, if someone can clarify that issues (or not?) I have
> run into with the functional tests are not release blockers, I am happy to
> just shut up about them and hope that testing is made easier for the next
> release.
>
> Just moving on now to some more thorough testing.
>
> My manual license check seems satisfactory.
>
> We're still shipping the "waf" binary in the root of our source, and I
> don't understand why. I know I was asked about this during the last round.
> And to be honest, I do not know whether it's a blocker. Can someone clarify
> for me why it is used, and why we can't ship the source instead?
>
> Manual file type test: OK
>
> Okay, going through some files by hand.
>
> The following files do not have copyright headers:
>
> setup/apidoc/generateadmincommands.xsl
> setup/apidoc/generatecommand.xsl
> setup/apidoc/generatedomainadmincommands.xsl
> setup/apidoc/generatetoc_footer.xsl
> setup/apidoc/generateusercommands.xsl
>
> I do not consider this a release blocker, but these should be fixed (where
> possible) for the next release.
>
> I almost raised a blocked with the files I found under tools/marvin,
> before I remembered our discussion about them. Heh!
>
> Okay, manually checked all the other manually flagged files, and they all
> check out in pom.xml or LICENSE.
>
> I am +1 on this release.
>
> For the next release, please can we:
>
> 1) Prepare a DecCloud AMI
> 2) Improve the test procedure
> 3) Fix up the XSL license headers
>
> Thanks!
>
> On 28 October 2012 17:00, Sebastien Goasguen <ru...@gmail.com> wrote:
>
>>
>> On Oct 28, 2012, at 5:48 PM, Noah Slater <ns...@apache.org> wrote:
>>
>> > I was expecting a VM for the storage thing. But that never appeared. I
>> did
>> > see a line for the VM I created. Either way, this testing step should
>> > indicate *clearly* what I should be looking for before moving on.
>> >
>> > As it stands, CloudStack itself is now refusing to answer HTTP
>> requests, so
>> > I am unable to complete the configuration change step. I am close to
>> giving
>> > up. This has been an incredibly frustrating experience.
>>
>> It should not be that frustrating.
>>
>> It's not clear to me where you stand and what you are doing.
>> I presume you are following the test procedure pointed by Chip.
>> I also presume you successfully checked the keys etc..and managed to
>> build and deploy and are running CS via rdebug.
>> I also presume that you managed to configure the infra by hand…did
>> everything turn green ? Is the zone enabled ?
>>
>> Can you give us more info or maybe ask on IRC ?
>>
>> -sebastien
>>
>> >
>> > On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com> wrote:
>> >
>> >>
>> >> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:
>> >>
>> >>> Okay,
>> >>>
>> >>> I did a rebuild and the menu populated. Very strange.
>> >>>
>> >>> Now I have two more problems.
>> >>>
>> >>> From the test procedure:
>> >>>
>> >>> Wait for secondary storage VM coming up.
>> >>>> This may take a bit...
>> >>>
>> >>>
>> >>> No clue about this. How do I know when the storage VM has come up?
>> >>
>> >> In the Infrastructure tab, do you see system VMs in running state ?
>> >> Check my video for help :)
>> >> https://vimeo.com/52150218
>> >>
>> >> PS: I ran the testing procedure on my mac air, and it was exceptionally
>> >> fast. I was amazed.
>> >>
>> >>
>> >>>
>> >>> I checked under instances and storage and nothing changed for about 10
>> >>> minutes.
>> >>>
>> >>> Last three lines in console are:
>> >>>
>> >>> [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
>> >>> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any
>> >> VPC
>> >>> [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
>> >>> (AgentManager-Handler-2:) Received a host startup notification
>> >>> [sshexec]      [java] INFO
>>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>> >>> (AgentManager-Handler-2:) Successfully sent out command to start HTTP
>> >>> handling in console proxy agent
>> >>>
>> >>> I decided to proceed to the next stage, on the off chance it had
>> worked.
>> >>>
>> >>> I get stuck on this step:
>> >>>
>> >>> In step 2, select "tiny Linux"
>> >>>
>> >>>
>> >>> There are no templates to select from!
>> >>>
>> >>>
>> >>
>> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
>> >>>
>> >>
>> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
>> >>>
>> >>
>> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
>> >>>
>> >>> I am unable to proceed.
>> >>>
>> >>> P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any
>> way
>> >>> to do the whole thing on or something? I practically cannot do
>> anything
>> >>> else on my computer while testing.
>> >>>
>> >>> On 28 October 2012 00:12, Chip Childers <ch...@sungard.com>
>> >> wrote:
>> >>>
>> >>>> Yeah.  Funny enough, that IS the infra menu option.
>> >>>>
>> >>>> I've never seen this before.
>> >>>>
>> >>>> I assume you are logged in as admin / password?  Can you do a fresh
>> >>>> build (start with "ant clean-all build-all")?
>> >>>>
>> >>>> - chip
>> >>>>
>> >>>> Sent from my iPhone.
>> >>>>
>> >>>> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>> >>>>
>> >>>>> I doubt it. Looks like part of the application code.
>> >>>>>
>> >>>>> My real problem is that I am unable to complete this step, as there
>> is
>> >>>>> nothing labeled "Infrastructure" in the UI.
>> >>>>>
>> >>>>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
>> >>>> wrote:
>> >>>>>
>> >>>>>> Comments below:
>> >>>>>>
>> >>>>>> - chip
>> >>>>>>
>> >>>>>> Sent from my iPhone.
>> >>>>>>
>> >>>>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org>
>> wrote:
>> >>>>>>
>> >>>>>>> Sig: OK
>> >>>>>>> Hashes: OK
>> >>>>>>> Source checks: OK
>> >>>>>>> RAT: OK
>> >>>>>>> Build: OK
>> >>>>>>>
>> >>>>>>> However, during this:
>> >>>>>>>
>> >>>>>>> mvn -P deps
>> >>>>>>>
>> >>>>>>> I noticed line like this:
>> >>>>>>>
>> >>>>>>> [INFO] Installing
>> >>>>>>>>
>> >> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
>> >>>>>> to
>> >>>>>>
>> >>>>
>> >>
>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>> >>>>>>>> [INFO]
>> >>>>>>>>
>> >>>>>>>> [INFO]
>> >>>>>>>>
>> >>>>
>> ------------------------------------------------------------------------
>> >>>>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>> >>>>>>>> [INFO]
>> >>>>>>>>
>> >>>>
>> ------------------------------------------------------------------------
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Any idea why that says incubating-SNAPSHOT?
>> >>>>>>
>> >>>>>> That's the default build version. If we do a binary release, it
>> would
>> >>>>>> be changed via the maven release tools.
>> >>>>>>
>> >>>>>>>
>> >>>>>>> A bigger problem is that I am stuck with the additional testing.
>> >>>>>>>
>> >>>>>>> Specifically, this step:
>> >>>>>>>
>> >>>>>>> Click "Infrastructure", click the "View All" button in the "Zones"
>> >>>>>> display
>> >>>>>>>> box, click "add zone"
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Here's what my console looks like:
>> >>>>>>
>> >>>>
>> >>
>> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>> >>>>>>>
>> >>>>>>> Note the oddly unlabelled cloud icon, which when clicked,
>> displays:
>> >>>>>>
>> >>>>
>> >>
>> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>> >>>>>>>
>> >>>>>>> I would like to be able to complete this testing, but would be
>> >> prepared
>> >>>>>> to
>> >>>>>>> vote without it.
>> >>>>>>>
>> >>>>>>> Can someone help me?
>> >>>>>>
>> >>>>>> Browser specific issue?  Is it consistent?
>> >>>>>>
>> >>>>>>>
>> >>>>>>> thanks,
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> NS
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> NS
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> NS
>> >>
>> >>
>> >
>> >
>> > --
>> > NS
>>
>>
>
>
> --
> NS
>



-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
On 29 October 2012 00:13, Chip Childers <ch...@sungard.com> wrote:

> On Sun, Oct 28, 2012 at 1:51 PM, Noah Slater <ns...@apache.org> wrote:
> > It is frustrating because everything is so slow, and my (main) computer
> is
> > practically unusable while it is running. How feasible would it be to
> > provide this DevCloud thing as an AMI? I would much prefer to do this in
> > the cloud.
>
> Want to help do that?  Sounds like a reasonable idea...  I wouldn't
> replace devcloud itself, but I don't see why we couldn't also have an
> AMI prepared for testing.
>

I don't think I have the bandwidth for it, or the experience to get up and
running as fast as I would like. Having a community image you can select
while deploying an EC2 instance would be super sweet though. And most
people will be able to test with the free tier.

We're a cloudy project, so we should cloudify our testing procedure. In the
cloud. #cloud ;)

Seriously though. My tiny laptop does not like running VMs in VMs. Yo dawg.
:(

Thanks for the rest of your clarifications! Very helpful.

On 29 October 2012 16:50, Jessica Wang <Je...@citrix.com> wrote:

>
> The 2 links you provided below are not working: "Oops, we encountered an
> error."
>

There's a good chance they were mangled by the quoting.

Here they are again:

https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82

https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380

-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Sun, Oct 28, 2012 at 1:51 PM, Noah Slater <ns...@apache.org> wrote:
> It is frustrating because everything is so slow, and my (main) computer is
> practically unusable while it is running. How feasible would it be to
> provide this DevCloud thing as an AMI? I would much prefer to do this in
> the cloud.

Want to help do that?  Sounds like a reasonable idea...  I wouldn't
replace devcloud itself, but I don't see why we couldn't also have an
AMI prepared for testing.

> Okay, I made it to this step:
>
> Additional Testing
>
> The instance is removed from the web console.
>
> And this is what I see on the terminal:
>
>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (AgentManager-Handler-6:) VM 3 lost host info, failed authentication request
>   [sshexec]
>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (AgentManager-Handler-8:) VM 3 lost host info, failed authentication request
>   [sshexec]
>   [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (AgentManager-Handler-9:) VM 3 lost host info, failed authentication request
>   [sshexec]
>   [sshexec]      [java] INFO  [cloud.vm.UserVmManagerImpl]
> (UserVm-Scavenger-1:) Found 1 vms to expunge.
>   [sshexec]
>   [sshexec]      [java] INFO  [network.security.SecurityGroupManagerImpl]
> (UserVm-Scavenger-1:) Disassociated 1 network groups  from uservm 3
>   [sshexec]
>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> (HA-Worker-1:work-2) Processing HAWork[2-HA-4-Stopped-Scheduled]
>   [sshexec]
>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> (HA-Worker-1:work-2) HA on VM[DomainRouter|r-4-TEST]
>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> (HA-Worker-1:work-2) VM VM[DomainRouter|r-4-TEST] has been changed.
>  Current State = Running Previous State = Stopped last updated = 10
> previous updated = 7
>   [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
> (HA-Worker-1:work-2) Completed HAWork[2-HA-4-Stopped-Scheduled]

Yup, it worked!

> However, from devcloud, I see this:

This is a good place for you to understand the different VM types that
CloudStack manages as part of the infra of supporting user VMs.

> root@devcloud:~# xe vm-list
> uuid ( RO)           : 83fdea03-9d67-d5dc-e090-0acba65e7926
>      name-label ( RW): r-4-TEST
>     power-state ( RO): running

This is a virtual router.  It's the VM that provides network services
within the zone for an account.  It's created when the first VM is
created within a zone.

> uuid ( RO)           : f01b195e-074b-e8f2-f8b1-b2c493070c8a
>      name-label ( RW): Control domain on host: devcloud
>     power-state ( RO): running

This is Xen's Dom0

> uuid ( RO)           : 2ab8057a-767e-b700-53e3-861f2e23823a
>      name-label ( RW): s-1-TEST
>     power-state ( RO): running

This is the secondary storage VM for the zone.  All template and
snapshot related activities are managed via this device.

> uuid ( RO)           : 8b27e755-4486-e27e-ee7a-6e5bc6ea768f
>      name-label ( RW): v-2-TEST
>     power-state ( RO): running

This is the console proxy VM for the zone.  All web-based access to a
VM's console comes through VM's like this.

> This looks, to my untrained eyes, like the VM might still be running, and
> in fact that there might be more than one?

You're instance was properly destroyed.  Sorry for the confusion here.
 I could build up more notes in the test doc for next time, but I
thought it was reasonable to stop at the UI telling you that the VM
was deleted.  Think the test procedure should be expanded?

> Okay, at this point, if someone can clarify that issues (or not?) I have
> run into with the functional tests are not release blockers, I am happy to
> just shut up about them and hope that testing is made easier for the next
> release.
>
> Just moving on now to some more thorough testing.
>
> My manual license check seems satisfactory.
>
> We're still shipping the "waf" binary in the root of our source, and I
> don't understand why. I know I was asked about this during the last round.
> And to be honest, I do not know whether it's a blocker. Can someone clarify
> for me why it is used, and why we can't ship the source instead?
>
> Manual file type test: OK
>
> Okay, going through some files by hand.
>
> The following files do not have copyright headers:
>
> setup/apidoc/generateadmincommands.xsl
> setup/apidoc/generatecommand.xsl
> setup/apidoc/generatedomainadmincommands.xsl
> setup/apidoc/generatetoc_footer.xsl
> setup/apidoc/generateusercommands.xsl
>
> I do not consider this a release blocker, but these should be fixed (where
> possible) for the next release.

Thanks for finding this.  I created
https://issues.apache.org/jira/browse/CLOUDSTACK-422 to fix.
Interestingly enough, I guess someone has removed these files from the
master branch.  I guess they are no longer needed.  Either way, we'll
fix them in whatever branches they are still in.

> I almost raised a blocked with the files I found under tools/marvin, before
> I remembered our discussion about them. Heh!
>
> Okay, manually checked all the other manually flagged files, and they all
> check out in pom.xml or LICENSE.
>
> I am +1 on this release.
>
> For the next release, please can we:
>
> 1) Prepare a DecCloud AMI
> 2) Improve the test procedure
> 3) Fix up the XSL license headers
>
> Thanks!
>
> On 28 October 2012 17:00, Sebastien Goasguen <ru...@gmail.com> wrote:
>
>>
>> On Oct 28, 2012, at 5:48 PM, Noah Slater <ns...@apache.org> wrote:
>>
>> > I was expecting a VM for the storage thing. But that never appeared. I
>> did
>> > see a line for the VM I created. Either way, this testing step should
>> > indicate *clearly* what I should be looking for before moving on.
>> >
>> > As it stands, CloudStack itself is now refusing to answer HTTP requests,
>> so
>> > I am unable to complete the configuration change step. I am close to
>> giving
>> > up. This has been an incredibly frustrating experience.
>>
>> It should not be that frustrating.
>>
>> It's not clear to me where you stand and what you are doing.
>> I presume you are following the test procedure pointed by Chip.
>> I also presume you successfully checked the keys etc..and managed to build
>> and deploy and are running CS via rdebug.
>> I also presume that you managed to configure the infra by hand…did
>> everything turn green ? Is the zone enabled ?
>>
>> Can you give us more info or maybe ask on IRC ?
>>
>> -sebastien
>>
>> >
>> > On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com> wrote:
>> >
>> >>
>> >> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:
>> >>
>> >>> Okay,
>> >>>
>> >>> I did a rebuild and the menu populated. Very strange.
>> >>>
>> >>> Now I have two more problems.
>> >>>
>> >>> From the test procedure:
>> >>>
>> >>> Wait for secondary storage VM coming up.
>> >>>> This may take a bit...
>> >>>
>> >>>
>> >>> No clue about this. How do I know when the storage VM has come up?
>> >>
>> >> In the Infrastructure tab, do you see system VMs in running state ?
>> >> Check my video for help :)
>> >> https://vimeo.com/52150218
>> >>
>> >> PS: I ran the testing procedure on my mac air, and it was exceptionally
>> >> fast. I was amazed.
>> >>
>> >>
>> >>>
>> >>> I checked under instances and storage and nothing changed for about 10
>> >>> minutes.
>> >>>
>> >>> Last three lines in console are:
>> >>>
>> >>> [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
>> >>> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any
>> >> VPC
>> >>> [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
>> >>> (AgentManager-Handler-2:) Received a host startup notification
>> >>> [sshexec]      [java] INFO
>>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>> >>> (AgentManager-Handler-2:) Successfully sent out command to start HTTP
>> >>> handling in console proxy agent
>> >>>
>> >>> I decided to proceed to the next stage, on the off chance it had
>> worked.
>> >>>
>> >>> I get stuck on this step:
>> >>>
>> >>> In step 2, select "tiny Linux"
>> >>>
>> >>>
>> >>> There are no templates to select from!
>> >>>
>> >>>
>> >>
>> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
>> >>>
>> >>
>> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
>> >>>
>> >>
>> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
>> >>>
>> >>> I am unable to proceed.
>> >>>
>> >>> P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any
>> way
>> >>> to do the whole thing on or something? I practically cannot do anything
>> >>> else on my computer while testing.
>> >>>
>> >>> On 28 October 2012 00:12, Chip Childers <ch...@sungard.com>
>> >> wrote:
>> >>>
>> >>>> Yeah.  Funny enough, that IS the infra menu option.
>> >>>>
>> >>>> I've never seen this before.
>> >>>>
>> >>>> I assume you are logged in as admin / password?  Can you do a fresh
>> >>>> build (start with "ant clean-all build-all")?
>> >>>>
>> >>>> - chip
>> >>>>
>> >>>> Sent from my iPhone.
>> >>>>
>> >>>> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>> >>>>
>> >>>>> I doubt it. Looks like part of the application code.
>> >>>>>
>> >>>>> My real problem is that I am unable to complete this step, as there
>> is
>> >>>>> nothing labeled "Infrastructure" in the UI.
>> >>>>>
>> >>>>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
>> >>>> wrote:
>> >>>>>
>> >>>>>> Comments below:
>> >>>>>>
>> >>>>>> - chip
>> >>>>>>
>> >>>>>> Sent from my iPhone.
>> >>>>>>
>> >>>>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org>
>> wrote:
>> >>>>>>
>> >>>>>>> Sig: OK
>> >>>>>>> Hashes: OK
>> >>>>>>> Source checks: OK
>> >>>>>>> RAT: OK
>> >>>>>>> Build: OK
>> >>>>>>>
>> >>>>>>> However, during this:
>> >>>>>>>
>> >>>>>>> mvn -P deps
>> >>>>>>>
>> >>>>>>> I noticed line like this:
>> >>>>>>>
>> >>>>>>> [INFO] Installing
>> >>>>>>>>
>> >> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
>> >>>>>> to
>> >>>>>>
>> >>>>
>> >>
>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>> >>>>>>>> [INFO]
>> >>>>>>>>
>> >>>>>>>> [INFO]
>> >>>>>>>>
>> >>>>
>> ------------------------------------------------------------------------
>> >>>>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>> >>>>>>>> [INFO]
>> >>>>>>>>
>> >>>>
>> ------------------------------------------------------------------------
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Any idea why that says incubating-SNAPSHOT?
>> >>>>>>
>> >>>>>> That's the default build version. If we do a binary release, it
>> would
>> >>>>>> be changed via the maven release tools.
>> >>>>>>
>> >>>>>>>
>> >>>>>>> A bigger problem is that I am stuck with the additional testing.
>> >>>>>>>
>> >>>>>>> Specifically, this step:
>> >>>>>>>
>> >>>>>>> Click "Infrastructure", click the "View All" button in the "Zones"
>> >>>>>> display
>> >>>>>>>> box, click "add zone"
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Here's what my console looks like:
>> >>>>>>
>> >>>>
>> >>
>> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>> >>>>>>>
>> >>>>>>> Note the oddly unlabelled cloud icon, which when clicked, displays:
>> >>>>>>
>> >>>>
>> >>
>> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>> >>>>>>>
>> >>>>>>> I would like to be able to complete this testing, but would be
>> >> prepared
>> >>>>>> to
>> >>>>>>> vote without it.
>> >>>>>>>
>> >>>>>>> Can someone help me?
>> >>>>>>
>> >>>>>> Browser specific issue?  Is it consistent?
>> >>>>>>
>> >>>>>>>
>> >>>>>>> thanks,
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> NS
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> NS
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> NS
>> >>
>> >>
>> >
>> >
>> > --
>> > NS
>>
>>
>
>
> --
> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
It is frustrating because everything is so slow, and my (main) computer is
practically unusable while it is running. How feasible would it be to
provide this DevCloud thing as an AMI? I would much prefer to do this in
the cloud.

Okay, I made it to this step:

Additional Testing

The instance is removed from the web console.

And this is what I see on the terminal:

  [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
(AgentManager-Handler-6:) VM 3 lost host info, failed authentication request
  [sshexec]
  [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
(AgentManager-Handler-8:) VM 3 lost host info, failed authentication request
  [sshexec]
  [sshexec]      [java] WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
(AgentManager-Handler-9:) VM 3 lost host info, failed authentication request
  [sshexec]
  [sshexec]      [java] INFO  [cloud.vm.UserVmManagerImpl]
(UserVm-Scavenger-1:) Found 1 vms to expunge.
  [sshexec]
  [sshexec]      [java] INFO  [network.security.SecurityGroupManagerImpl]
(UserVm-Scavenger-1:) Disassociated 1 network groups  from uservm 3
  [sshexec]
  [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
(HA-Worker-1:work-2) Processing HAWork[2-HA-4-Stopped-Scheduled]
  [sshexec]
  [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
(HA-Worker-1:work-2) HA on VM[DomainRouter|r-4-TEST]
  [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
(HA-Worker-1:work-2) VM VM[DomainRouter|r-4-TEST] has been changed.
 Current State = Running Previous State = Stopped last updated = 10
previous updated = 7
  [sshexec]      [java] INFO  [cloud.ha.HighAvailabilityManagerImpl]
(HA-Worker-1:work-2) Completed HAWork[2-HA-4-Stopped-Scheduled]

However, from devcloud, I see this:

root@devcloud:~# xe vm-list
uuid ( RO)           : 83fdea03-9d67-d5dc-e090-0acba65e7926
     name-label ( RW): r-4-TEST
    power-state ( RO): running


uuid ( RO)           : f01b195e-074b-e8f2-f8b1-b2c493070c8a
     name-label ( RW): Control domain on host: devcloud
    power-state ( RO): running


uuid ( RO)           : 2ab8057a-767e-b700-53e3-861f2e23823a
     name-label ( RW): s-1-TEST
    power-state ( RO): running


uuid ( RO)           : 8b27e755-4486-e27e-ee7a-6e5bc6ea768f
     name-label ( RW): v-2-TEST
    power-state ( RO): running

This looks, to my untrained eyes, like the VM might still be running, and
in fact that there might be more than one?

Okay, at this point, if someone can clarify that issues (or not?) I have
run into with the functional tests are not release blockers, I am happy to
just shut up about them and hope that testing is made easier for the next
release.

Just moving on now to some more thorough testing.

My manual license check seems satisfactory.

We're still shipping the "waf" binary in the root of our source, and I
don't understand why. I know I was asked about this during the last round.
And to be honest, I do not know whether it's a blocker. Can someone clarify
for me why it is used, and why we can't ship the source instead?

Manual file type test: OK

Okay, going through some files by hand.

The following files do not have copyright headers:

setup/apidoc/generateadmincommands.xsl
setup/apidoc/generatecommand.xsl
setup/apidoc/generatedomainadmincommands.xsl
setup/apidoc/generatetoc_footer.xsl
setup/apidoc/generateusercommands.xsl

I do not consider this a release blocker, but these should be fixed (where
possible) for the next release.

I almost raised a blocked with the files I found under tools/marvin, before
I remembered our discussion about them. Heh!

Okay, manually checked all the other manually flagged files, and they all
check out in pom.xml or LICENSE.

I am +1 on this release.

For the next release, please can we:

1) Prepare a DecCloud AMI
2) Improve the test procedure
3) Fix up the XSL license headers

Thanks!

On 28 October 2012 17:00, Sebastien Goasguen <ru...@gmail.com> wrote:

>
> On Oct 28, 2012, at 5:48 PM, Noah Slater <ns...@apache.org> wrote:
>
> > I was expecting a VM for the storage thing. But that never appeared. I
> did
> > see a line for the VM I created. Either way, this testing step should
> > indicate *clearly* what I should be looking for before moving on.
> >
> > As it stands, CloudStack itself is now refusing to answer HTTP requests,
> so
> > I am unable to complete the configuration change step. I am close to
> giving
> > up. This has been an incredibly frustrating experience.
>
> It should not be that frustrating.
>
> It's not clear to me where you stand and what you are doing.
> I presume you are following the test procedure pointed by Chip.
> I also presume you successfully checked the keys etc..and managed to build
> and deploy and are running CS via rdebug.
> I also presume that you managed to configure the infra by hand…did
> everything turn green ? Is the zone enabled ?
>
> Can you give us more info or maybe ask on IRC ?
>
> -sebastien
>
> >
> > On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com> wrote:
> >
> >>
> >> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:
> >>
> >>> Okay,
> >>>
> >>> I did a rebuild and the menu populated. Very strange.
> >>>
> >>> Now I have two more problems.
> >>>
> >>> From the test procedure:
> >>>
> >>> Wait for secondary storage VM coming up.
> >>>> This may take a bit...
> >>>
> >>>
> >>> No clue about this. How do I know when the storage VM has come up?
> >>
> >> In the Infrastructure tab, do you see system VMs in running state ?
> >> Check my video for help :)
> >> https://vimeo.com/52150218
> >>
> >> PS: I ran the testing procedure on my mac air, and it was exceptionally
> >> fast. I was amazed.
> >>
> >>
> >>>
> >>> I checked under instances and storage and nothing changed for about 10
> >>> minutes.
> >>>
> >>> Last three lines in console are:
> >>>
> >>> [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
> >>> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any
> >> VPC
> >>> [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
> >>> (AgentManager-Handler-2:) Received a host startup notification
> >>> [sshexec]      [java] INFO
>  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> >>> (AgentManager-Handler-2:) Successfully sent out command to start HTTP
> >>> handling in console proxy agent
> >>>
> >>> I decided to proceed to the next stage, on the off chance it had
> worked.
> >>>
> >>> I get stuck on this step:
> >>>
> >>> In step 2, select "tiny Linux"
> >>>
> >>>
> >>> There are no templates to select from!
> >>>
> >>>
> >>
> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
> >>>
> >>
> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
> >>>
> >>
> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
> >>>
> >>> I am unable to proceed.
> >>>
> >>> P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any
> way
> >>> to do the whole thing on or something? I practically cannot do anything
> >>> else on my computer while testing.
> >>>
> >>> On 28 October 2012 00:12, Chip Childers <ch...@sungard.com>
> >> wrote:
> >>>
> >>>> Yeah.  Funny enough, that IS the infra menu option.
> >>>>
> >>>> I've never seen this before.
> >>>>
> >>>> I assume you are logged in as admin / password?  Can you do a fresh
> >>>> build (start with "ant clean-all build-all")?
> >>>>
> >>>> - chip
> >>>>
> >>>> Sent from my iPhone.
> >>>>
> >>>> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
> >>>>
> >>>>> I doubt it. Looks like part of the application code.
> >>>>>
> >>>>> My real problem is that I am unable to complete this step, as there
> is
> >>>>> nothing labeled "Infrastructure" in the UI.
> >>>>>
> >>>>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
> >>>> wrote:
> >>>>>
> >>>>>> Comments below:
> >>>>>>
> >>>>>> - chip
> >>>>>>
> >>>>>> Sent from my iPhone.
> >>>>>>
> >>>>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org>
> wrote:
> >>>>>>
> >>>>>>> Sig: OK
> >>>>>>> Hashes: OK
> >>>>>>> Source checks: OK
> >>>>>>> RAT: OK
> >>>>>>> Build: OK
> >>>>>>>
> >>>>>>> However, during this:
> >>>>>>>
> >>>>>>> mvn -P deps
> >>>>>>>
> >>>>>>> I noticed line like this:
> >>>>>>>
> >>>>>>> [INFO] Installing
> >>>>>>>>
> >> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
> >>>>>> to
> >>>>>>
> >>>>
> >>
> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> >>>>>>>> [INFO]
> >>>>>>>>
> >>>>>>>> [INFO]
> >>>>>>>>
> >>>>
> ------------------------------------------------------------------------
> >>>>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
> >>>>>>>> [INFO]
> >>>>>>>>
> >>>>
> ------------------------------------------------------------------------
> >>>>>>>
> >>>>>>>
> >>>>>>> Any idea why that says incubating-SNAPSHOT?
> >>>>>>
> >>>>>> That's the default build version. If we do a binary release, it
> would
> >>>>>> be changed via the maven release tools.
> >>>>>>
> >>>>>>>
> >>>>>>> A bigger problem is that I am stuck with the additional testing.
> >>>>>>>
> >>>>>>> Specifically, this step:
> >>>>>>>
> >>>>>>> Click "Infrastructure", click the "View All" button in the "Zones"
> >>>>>> display
> >>>>>>>> box, click "add zone"
> >>>>>>>
> >>>>>>>
> >>>>>>> Here's what my console looks like:
> >>>>>>
> >>>>
> >>
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
> >>>>>>>
> >>>>>>> Note the oddly unlabelled cloud icon, which when clicked, displays:
> >>>>>>
> >>>>
> >>
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
> >>>>>>>
> >>>>>>> I would like to be able to complete this testing, but would be
> >> prepared
> >>>>>> to
> >>>>>>> vote without it.
> >>>>>>>
> >>>>>>> Can someone help me?
> >>>>>>
> >>>>>> Browser specific issue?  Is it consistent?
> >>>>>>
> >>>>>>>
> >>>>>>> thanks,
> >>>>>>>
> >>>>>>> --
> >>>>>>> NS
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> NS
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> NS
> >>
> >>
> >
> >
> > --
> > NS
>
>


-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Sebastien Goasguen <ru...@gmail.com>.
On Oct 28, 2012, at 5:48 PM, Noah Slater <ns...@apache.org> wrote:

> I was expecting a VM for the storage thing. But that never appeared. I did
> see a line for the VM I created. Either way, this testing step should
> indicate *clearly* what I should be looking for before moving on.
> 
> As it stands, CloudStack itself is now refusing to answer HTTP requests, so
> I am unable to complete the configuration change step. I am close to giving
> up. This has been an incredibly frustrating experience.

It should not be that frustrating.

It's not clear to me where you stand and what you are doing.
I presume you are following the test procedure pointed by Chip.
I also presume you successfully checked the keys etc..and managed to build and deploy and are running CS via rdebug.
I also presume that you managed to configure the infra by hand…did everything turn green ? Is the zone enabled ?

Can you give us more info or maybe ask on IRC ?

-sebastien

> 
> On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com> wrote:
> 
>> 
>> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:
>> 
>>> Okay,
>>> 
>>> I did a rebuild and the menu populated. Very strange.
>>> 
>>> Now I have two more problems.
>>> 
>>> From the test procedure:
>>> 
>>> Wait for secondary storage VM coming up.
>>>> This may take a bit...
>>> 
>>> 
>>> No clue about this. How do I know when the storage VM has come up?
>> 
>> In the Infrastructure tab, do you see system VMs in running state ?
>> Check my video for help :)
>> https://vimeo.com/52150218
>> 
>> PS: I ran the testing procedure on my mac air, and it was exceptionally
>> fast. I was amazed.
>> 
>> 
>>> 
>>> I checked under instances and storage and nothing changed for about 10
>>> minutes.
>>> 
>>> Last three lines in console are:
>>> 
>>> [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
>>> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any
>> VPC
>>> [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
>>> (AgentManager-Handler-2:) Received a host startup notification
>>> [sshexec]      [java] INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>>> (AgentManager-Handler-2:) Successfully sent out command to start HTTP
>>> handling in console proxy agent
>>> 
>>> I decided to proceed to the next stage, on the off chance it had worked.
>>> 
>>> I get stuck on this step:
>>> 
>>> In step 2, select "tiny Linux"
>>> 
>>> 
>>> There are no templates to select from!
>>> 
>>> 
>> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
>>> 
>> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
>>> 
>> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
>>> 
>>> I am unable to proceed.
>>> 
>>> P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any way
>>> to do the whole thing on or something? I practically cannot do anything
>>> else on my computer while testing.
>>> 
>>> On 28 October 2012 00:12, Chip Childers <ch...@sungard.com>
>> wrote:
>>> 
>>>> Yeah.  Funny enough, that IS the infra menu option.
>>>> 
>>>> I've never seen this before.
>>>> 
>>>> I assume you are logged in as admin / password?  Can you do a fresh
>>>> build (start with "ant clean-all build-all")?
>>>> 
>>>> - chip
>>>> 
>>>> Sent from my iPhone.
>>>> 
>>>> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>>>> 
>>>>> I doubt it. Looks like part of the application code.
>>>>> 
>>>>> My real problem is that I am unable to complete this step, as there is
>>>>> nothing labeled "Infrastructure" in the UI.
>>>>> 
>>>>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
>>>> wrote:
>>>>> 
>>>>>> Comments below:
>>>>>> 
>>>>>> - chip
>>>>>> 
>>>>>> Sent from my iPhone.
>>>>>> 
>>>>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:
>>>>>> 
>>>>>>> Sig: OK
>>>>>>> Hashes: OK
>>>>>>> Source checks: OK
>>>>>>> RAT: OK
>>>>>>> Build: OK
>>>>>>> 
>>>>>>> However, during this:
>>>>>>> 
>>>>>>> mvn -P deps
>>>>>>> 
>>>>>>> I noticed line like this:
>>>>>>> 
>>>>>>> [INFO] Installing
>>>>>>>> 
>> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
>>>>>> to
>>>>>> 
>>>> 
>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>>>>>>>> [INFO]
>>>>>>>> 
>>>>>>>> [INFO]
>>>>>>>> 
>>>> ------------------------------------------------------------------------
>>>>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>>>>>>>> [INFO]
>>>>>>>> 
>>>> ------------------------------------------------------------------------
>>>>>>> 
>>>>>>> 
>>>>>>> Any idea why that says incubating-SNAPSHOT?
>>>>>> 
>>>>>> That's the default build version. If we do a binary release, it would
>>>>>> be changed via the maven release tools.
>>>>>> 
>>>>>>> 
>>>>>>> A bigger problem is that I am stuck with the additional testing.
>>>>>>> 
>>>>>>> Specifically, this step:
>>>>>>> 
>>>>>>> Click "Infrastructure", click the "View All" button in the "Zones"
>>>>>> display
>>>>>>>> box, click "add zone"
>>>>>>> 
>>>>>>> 
>>>>>>> Here's what my console looks like:
>>>>>> 
>>>> 
>> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>>>>>>> 
>>>>>>> Note the oddly unlabelled cloud icon, which when clicked, displays:
>>>>>> 
>>>> 
>> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>>>>>>> 
>>>>>>> I would like to be able to complete this testing, but would be
>> prepared
>>>>>> to
>>>>>>> vote without it.
>>>>>>> 
>>>>>>> Can someone help me?
>>>>>> 
>>>>>> Browser specific issue?  Is it consistent?
>>>>>> 
>>>>>>> 
>>>>>>> thanks,
>>>>>>> 
>>>>>>> --
>>>>>>> NS
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> NS
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> NS
>> 
>> 
> 
> 
> -- 
> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Sun, Oct 28, 2012 at 12:48 PM, Noah Slater <ns...@apache.org> wrote:
> I was expecting a VM for the storage thing. But that never appeared. I did
> see a line for the VM I created. Either way, this testing step should
> indicate *clearly* what I should be looking for before moving on.

Done.

> As it stands, CloudStack itself is now refusing to answer HTTP requests, so
> I am unable to complete the configuration change step. I am close to giving
> up. This has been an incredibly frustrating experience.
>
> On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com> wrote:
>
>>
>> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:
>>
>> > Okay,
>> >
>> > I did a rebuild and the menu populated. Very strange.
>> >
>> > Now I have two more problems.
>> >
>> > From the test procedure:
>> >
>> > Wait for secondary storage VM coming up.
>> >> This may take a bit...
>> >
>> >
>> > No clue about this. How do I know when the storage VM has come up?
>>
>> In the Infrastructure tab, do you see system VMs in running state ?
>> Check my video for help :)
>> https://vimeo.com/52150218
>>
>> PS: I ran the testing procedure on my mac air, and it was exceptionally
>> fast. I was amazed.
>>
>>
>> >
>> > I checked under instances and storage and nothing changed for about 10
>> > minutes.
>> >
>> > Last three lines in console are:
>> >
>> >  [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
>> > (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any
>> VPC
>> >  [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
>> > (AgentManager-Handler-2:) Received a host startup notification
>> >  [sshexec]      [java] INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl]
>> > (AgentManager-Handler-2:) Successfully sent out command to start HTTP
>> > handling in console proxy agent
>> >
>> > I decided to proceed to the next stage, on the off chance it had worked.
>> >
>> > I get stuck on this step:
>> >
>> > In step 2, select "tiny Linux"
>> >
>> >
>> > There are no templates to select from!
>> >
>> >
>> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
>> >
>> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
>> >
>> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
>> >
>> > I am unable to proceed.
>> >
>> > P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any way
>> > to do the whole thing on or something? I practically cannot do anything
>> > else on my computer while testing.
>> >
>> > On 28 October 2012 00:12, Chip Childers <ch...@sungard.com>
>> wrote:
>> >
>> >> Yeah.  Funny enough, that IS the infra menu option.
>> >>
>> >> I've never seen this before.
>> >>
>> >> I assume you are logged in as admin / password?  Can you do a fresh
>> >> build (start with "ant clean-all build-all")?
>> >>
>> >> - chip
>> >>
>> >> Sent from my iPhone.
>> >>
>> >> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>> >>
>> >>> I doubt it. Looks like part of the application code.
>> >>>
>> >>> My real problem is that I am unable to complete this step, as there is
>> >>> nothing labeled "Infrastructure" in the UI.
>> >>>
>> >>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
>> >> wrote:
>> >>>
>> >>>> Comments below:
>> >>>>
>> >>>> - chip
>> >>>>
>> >>>> Sent from my iPhone.
>> >>>>
>> >>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:
>> >>>>
>> >>>>> Sig: OK
>> >>>>> Hashes: OK
>> >>>>> Source checks: OK
>> >>>>> RAT: OK
>> >>>>> Build: OK
>> >>>>>
>> >>>>> However, during this:
>> >>>>>
>> >>>>> mvn -P deps
>> >>>>>
>> >>>>> I noticed line like this:
>> >>>>>
>> >>>>> [INFO] Installing
>> >>>>>>
>> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
>> >>>> to
>> >>>>
>> >>
>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>> >>>>>> [INFO]
>> >>>>>>
>> >>>>>> [INFO]
>> >>>>>>
>> >> ------------------------------------------------------------------------
>> >>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>> >>>>>> [INFO]
>> >>>>>>
>> >> ------------------------------------------------------------------------
>> >>>>>
>> >>>>>
>> >>>>> Any idea why that says incubating-SNAPSHOT?
>> >>>>
>> >>>> That's the default build version. If we do a binary release, it would
>> >>>> be changed via the maven release tools.
>> >>>>
>> >>>>>
>> >>>>> A bigger problem is that I am stuck with the additional testing.
>> >>>>>
>> >>>>> Specifically, this step:
>> >>>>>
>> >>>>> Click "Infrastructure", click the "View All" button in the "Zones"
>> >>>> display
>> >>>>>> box, click "add zone"
>> >>>>>
>> >>>>>
>> >>>>> Here's what my console looks like:
>> >>>>
>> >>
>> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>> >>>>>
>> >>>>> Note the oddly unlabelled cloud icon, which when clicked, displays:
>> >>>>
>> >>
>> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>> >>>>>
>> >>>>> I would like to be able to complete this testing, but would be
>> prepared
>> >>>> to
>> >>>>> vote without it.
>> >>>>>
>> >>>>> Can someone help me?
>> >>>>
>> >>>> Browser specific issue?  Is it consistent?
>> >>>>
>> >>>>>
>> >>>>> thanks,
>> >>>>>
>> >>>>> --
>> >>>>> NS
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> NS
>> >>
>> >
>> >
>> >
>> > --
>> > NS
>>
>>
>
>
> --
> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
I was expecting a VM for the storage thing. But that never appeared. I did
see a line for the VM I created. Either way, this testing step should
indicate *clearly* what I should be looking for before moving on.

As it stands, CloudStack itself is now refusing to answer HTTP requests, so
I am unable to complete the configuration change step. I am close to giving
up. This has been an incredibly frustrating experience.

On 28 October 2012 16:45, Sebastien Goasguen <ru...@gmail.com> wrote:

>
> On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:
>
> > Okay,
> >
> > I did a rebuild and the menu populated. Very strange.
> >
> > Now I have two more problems.
> >
> > From the test procedure:
> >
> > Wait for secondary storage VM coming up.
> >> This may take a bit...
> >
> >
> > No clue about this. How do I know when the storage VM has come up?
>
> In the Infrastructure tab, do you see system VMs in running state ?
> Check my video for help :)
> https://vimeo.com/52150218
>
> PS: I ran the testing procedure on my mac air, and it was exceptionally
> fast. I was amazed.
>
>
> >
> > I checked under instances and storage and nothing changed for about 10
> > minutes.
> >
> > Last three lines in console are:
> >
> >  [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
> > (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any
> VPC
> >  [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
> > (AgentManager-Handler-2:) Received a host startup notification
> >  [sshexec]      [java] INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> > (AgentManager-Handler-2:) Successfully sent out command to start HTTP
> > handling in console proxy agent
> >
> > I decided to proceed to the next stage, on the off chance it had worked.
> >
> > I get stuck on this step:
> >
> > In step 2, select "tiny Linux"
> >
> >
> > There are no templates to select from!
> >
> >
> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
> >
> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
> >
> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
> >
> > I am unable to proceed.
> >
> > P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any way
> > to do the whole thing on or something? I practically cannot do anything
> > else on my computer while testing.
> >
> > On 28 October 2012 00:12, Chip Childers <ch...@sungard.com>
> wrote:
> >
> >> Yeah.  Funny enough, that IS the infra menu option.
> >>
> >> I've never seen this before.
> >>
> >> I assume you are logged in as admin / password?  Can you do a fresh
> >> build (start with "ant clean-all build-all")?
> >>
> >> - chip
> >>
> >> Sent from my iPhone.
> >>
> >> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
> >>
> >>> I doubt it. Looks like part of the application code.
> >>>
> >>> My real problem is that I am unable to complete this step, as there is
> >>> nothing labeled "Infrastructure" in the UI.
> >>>
> >>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
> >> wrote:
> >>>
> >>>> Comments below:
> >>>>
> >>>> - chip
> >>>>
> >>>> Sent from my iPhone.
> >>>>
> >>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:
> >>>>
> >>>>> Sig: OK
> >>>>> Hashes: OK
> >>>>> Source checks: OK
> >>>>> RAT: OK
> >>>>> Build: OK
> >>>>>
> >>>>> However, during this:
> >>>>>
> >>>>> mvn -P deps
> >>>>>
> >>>>> I noticed line like this:
> >>>>>
> >>>>> [INFO] Installing
> >>>>>>
> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
> >>>> to
> >>>>
> >>
> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> >>>>>> [INFO]
> >>>>>>
> >>>>>> [INFO]
> >>>>>>
> >> ------------------------------------------------------------------------
> >>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
> >>>>>> [INFO]
> >>>>>>
> >> ------------------------------------------------------------------------
> >>>>>
> >>>>>
> >>>>> Any idea why that says incubating-SNAPSHOT?
> >>>>
> >>>> That's the default build version. If we do a binary release, it would
> >>>> be changed via the maven release tools.
> >>>>
> >>>>>
> >>>>> A bigger problem is that I am stuck with the additional testing.
> >>>>>
> >>>>> Specifically, this step:
> >>>>>
> >>>>> Click "Infrastructure", click the "View All" button in the "Zones"
> >>>> display
> >>>>>> box, click "add zone"
> >>>>>
> >>>>>
> >>>>> Here's what my console looks like:
> >>>>
> >>
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
> >>>>>
> >>>>> Note the oddly unlabelled cloud icon, which when clicked, displays:
> >>>>
> >>
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
> >>>>>
> >>>>> I would like to be able to complete this testing, but would be
> prepared
> >>>> to
> >>>>> vote without it.
> >>>>>
> >>>>> Can someone help me?
> >>>>
> >>>> Browser specific issue?  Is it consistent?
> >>>>
> >>>>>
> >>>>> thanks,
> >>>>>
> >>>>> --
> >>>>> NS
> >>>
> >>>
> >>>
> >>> --
> >>> NS
> >>
> >
> >
> >
> > --
> > NS
>
>


-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Sebastien Goasguen <ru...@gmail.com>.
On Oct 28, 2012, at 4:41 PM, Noah Slater <ns...@apache.org> wrote:

> Okay,
> 
> I did a rebuild and the menu populated. Very strange.
> 
> Now I have two more problems.
> 
> From the test procedure:
> 
> Wait for secondary storage VM coming up.
>> This may take a bit...
> 
> 
> No clue about this. How do I know when the storage VM has come up?

In the Infrastructure tab, do you see system VMs in running state ?
Check my video for help :)
https://vimeo.com/52150218

PS: I ran the testing procedure on my mac air, and it was exceptionally fast. I was amazed.


> 
> I checked under instances and storage and nothing changed for about 10
> minutes.
> 
> Last three lines in console are:
> 
>  [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any VPC
>  [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
> (AgentManager-Handler-2:) Received a host startup notification
>  [sshexec]      [java] INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (AgentManager-Handler-2:) Successfully sent out command to start HTTP
> handling in console proxy agent
> 
> I decided to proceed to the next stage, on the off chance it had worked.
> 
> I get stuck on this step:
> 
> In step 2, select "tiny Linux"
> 
> 
> There are no templates to select from!
> 
> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
> 
> I am unable to proceed.
> 
> P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any way
> to do the whole thing on or something? I practically cannot do anything
> else on my computer while testing.
> 
> On 28 October 2012 00:12, Chip Childers <ch...@sungard.com> wrote:
> 
>> Yeah.  Funny enough, that IS the infra menu option.
>> 
>> I've never seen this before.
>> 
>> I assume you are logged in as admin / password?  Can you do a fresh
>> build (start with "ant clean-all build-all")?
>> 
>> - chip
>> 
>> Sent from my iPhone.
>> 
>> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>> 
>>> I doubt it. Looks like part of the application code.
>>> 
>>> My real problem is that I am unable to complete this step, as there is
>>> nothing labeled "Infrastructure" in the UI.
>>> 
>>> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
>> wrote:
>>> 
>>>> Comments below:
>>>> 
>>>> - chip
>>>> 
>>>> Sent from my iPhone.
>>>> 
>>>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:
>>>> 
>>>>> Sig: OK
>>>>> Hashes: OK
>>>>> Source checks: OK
>>>>> RAT: OK
>>>>> Build: OK
>>>>> 
>>>>> However, during this:
>>>>> 
>>>>> mvn -P deps
>>>>> 
>>>>> I noticed line like this:
>>>>> 
>>>>> [INFO] Installing
>>>>>> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
>>>> to
>>>> 
>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>>>>>> [INFO]
>>>>>> 
>>>>>> [INFO]
>>>>>> 
>> ------------------------------------------------------------------------
>>>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>>>>>> [INFO]
>>>>>> 
>> ------------------------------------------------------------------------
>>>>> 
>>>>> 
>>>>> Any idea why that says incubating-SNAPSHOT?
>>>> 
>>>> That's the default build version. If we do a binary release, it would
>>>> be changed via the maven release tools.
>>>> 
>>>>> 
>>>>> A bigger problem is that I am stuck with the additional testing.
>>>>> 
>>>>> Specifically, this step:
>>>>> 
>>>>> Click "Infrastructure", click the "View All" button in the "Zones"
>>>> display
>>>>>> box, click "add zone"
>>>>> 
>>>>> 
>>>>> Here's what my console looks like:
>>>> 
>> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>>>>> 
>>>>> Note the oddly unlabelled cloud icon, which when clicked, displays:
>>>> 
>> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>>>>> 
>>>>> I would like to be able to complete this testing, but would be prepared
>>>> to
>>>>> vote without it.
>>>>> 
>>>>> Can someone help me?
>>>> 
>>>> Browser specific issue?  Is it consistent?
>>>> 
>>>>> 
>>>>> thanks,
>>>>> 
>>>>> --
>>>>> NS
>>> 
>>> 
>>> 
>>> --
>>> NS
>> 
> 
> 
> 
> -- 
> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
Very mysterious. But okay. Thanks.

On 29 October 2012 17:55, Jessica Wang <Je...@citrix.com> wrote:

> Noah,
>
> Since you are able to see Infra menu now, I believe it was an installation
> bug in your environment earlier.
> If you do see the problem again (i.e. infra menu doesn't show), please let
> us know.
>
> Jessica
>
> -----Original Message-----
> From: Noah Slater [mailto:nslater@apache.org]
> Sent: Sunday, October 28, 2012 8:42 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
>
> Okay,
>
> I did a rebuild and the menu populated. Very strange.
>
> Now I have two more problems.
>
> From the test procedure:
>
> Wait for secondary storage VM coming up.
> > This may take a bit...
>
>
> No clue about this. How do I know when the storage VM has come up?
>
> I checked under instances and storage and nothing changed for about 10
> minutes.
>
> Last three lines in console are:
>
>   [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
> (secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any VPC
>   [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
> (AgentManager-Handler-2:) Received a host startup notification
>   [sshexec]      [java] INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl]
> (AgentManager-Handler-2:) Successfully sent out command to start HTTP
> handling in console proxy agent
>
> I decided to proceed to the next stage, on the off chance it had worked.
>
> I get stuck on this step:
>
> In step 2, select "tiny Linux"
>
>
> There are no templates to select from!
>
>
> https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
>
> https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
>
> https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430
>
> I am unable to proceed.
>
> P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any way
> to do the whole thing on or something? I practically cannot do anything
> else on my computer while testing.
>
> On 28 October 2012 00:12, Chip Childers <ch...@sungard.com> wrote:
>
> > Yeah.  Funny enough, that IS the infra menu option.
> >
> > I've never seen this before.
> >
> > I assume you are logged in as admin / password?  Can you do a fresh
> > build (start with "ant clean-all build-all")?
> >
> > - chip
> >
> > Sent from my iPhone.
> >
> > On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
> >
> > > I doubt it. Looks like part of the application code.
> > >
> > > My real problem is that I am unable to complete this step, as there is
> > > nothing labeled "Infrastructure" in the UI.
> > >
> > > On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
> > wrote:
> > >
> > >> Comments below:
> > >>
> > >> - chip
> > >>
> > >> Sent from my iPhone.
> > >>
> > >> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:
> > >>
> > >>> Sig: OK
> > >>> Hashes: OK
> > >>> Source checks: OK
> > >>> RAT: OK
> > >>> Build: OK
> > >>>
> > >>> However, during this:
> > >>>
> > >>> mvn -P deps
> > >>>
> > >>> I noticed line like this:
> > >>>
> > >>> [INFO] Installing
> > >>>>
> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
> > >> to
> > >>
> >
> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> > >>>> [INFO]
> > >>>>
> > >>>> [INFO]
> > >>>>
> > ------------------------------------------------------------------------
> > >>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
> > >>>> [INFO]
> > >>>>
> > ------------------------------------------------------------------------
> > >>>
> > >>>
> > >>> Any idea why that says incubating-SNAPSHOT?
> > >>
> > >> That's the default build version. If we do a binary release, it would
> > >> be changed via the maven release tools.
> > >>
> > >>>
> > >>> A bigger problem is that I am stuck with the additional testing.
> > >>>
> > >>> Specifically, this step:
> > >>>
> > >>> Click "Infrastructure", click the "View All" button in the "Zones"
> > >> display
> > >>>> box, click "add zone"
> > >>>
> > >>>
> > >>> Here's what my console looks like:
> > >>
> >
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
> > >>>
> > >>> Note the oddly unlabelled cloud icon, which when clicked, displays:
> > >>
> >
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
> > >>>
> > >>> I would like to be able to complete this testing, but would be
> prepared
> > >> to
> > >>> vote without it.
> > >>>
> > >>> Can someone help me?
> > >>
> > >> Browser specific issue?  Is it consistent?
> > >>
> > >>>
> > >>> thanks,
> > >>>
> > >>> --
> > >>> NS
> > >
> > >
> > >
> > > --
> > > NS
> >
>
>
>
> --
> NS
>



-- 
NS

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Jessica Wang <Je...@citrix.com>.
Noah,

Since you are able to see Infra menu now, I believe it was an installation bug in your environment earlier.
If you do see the problem again (i.e. infra menu doesn't show), please let us know.

Jessica

-----Original Message-----
From: Noah Slater [mailto:nslater@apache.org] 
Sent: Sunday, October 28, 2012 8:42 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Okay,

I did a rebuild and the menu populated. Very strange.

Now I have two more problems.

>From the test procedure:

Wait for secondary storage VM coming up.
> This may take a bit...


No clue about this. How do I know when the storage VM has come up?

I checked under instances and storage and nothing changed for about 10
minutes.

Last three lines in console are:

  [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
(secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any VPC
  [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
(AgentManager-Handler-2:) Received a host startup notification
  [sshexec]      [java] INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl]
(AgentManager-Handler-2:) Successfully sent out command to start HTTP
handling in console proxy agent

I decided to proceed to the next stage, on the off chance it had worked.

I get stuck on this step:

In step 2, select "tiny Linux"


There are no templates to select from!

https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430

I am unable to proceed.

P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any way
to do the whole thing on or something? I practically cannot do anything
else on my computer while testing.

On 28 October 2012 00:12, Chip Childers <ch...@sungard.com> wrote:

> Yeah.  Funny enough, that IS the infra menu option.
>
> I've never seen this before.
>
> I assume you are logged in as admin / password?  Can you do a fresh
> build (start with "ant clean-all build-all")?
>
> - chip
>
> Sent from my iPhone.
>
> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>
> > I doubt it. Looks like part of the application code.
> >
> > My real problem is that I am unable to complete this step, as there is
> > nothing labeled "Infrastructure" in the UI.
> >
> > On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
> wrote:
> >
> >> Comments below:
> >>
> >> - chip
> >>
> >> Sent from my iPhone.
> >>
> >> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:
> >>
> >>> Sig: OK
> >>> Hashes: OK
> >>> Source checks: OK
> >>> RAT: OK
> >>> Build: OK
> >>>
> >>> However, during this:
> >>>
> >>> mvn -P deps
> >>>
> >>> I noticed line like this:
> >>>
> >>> [INFO] Installing
> >>>> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
> >> to
> >>
> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> >>>> [INFO]
> >>>>
> >>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
> >>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>
> >>>
> >>> Any idea why that says incubating-SNAPSHOT?
> >>
> >> That's the default build version. If we do a binary release, it would
> >> be changed via the maven release tools.
> >>
> >>>
> >>> A bigger problem is that I am stuck with the additional testing.
> >>>
> >>> Specifically, this step:
> >>>
> >>> Click "Infrastructure", click the "View All" button in the "Zones"
> >> display
> >>>> box, click "add zone"
> >>>
> >>>
> >>> Here's what my console looks like:
> >>
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
> >>>
> >>> Note the oddly unlabelled cloud icon, which when clicked, displays:
> >>
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
> >>>
> >>> I would like to be able to complete this testing, but would be prepared
> >> to
> >>> vote without it.
> >>>
> >>> Can someone help me?
> >>
> >> Browser specific issue?  Is it consistent?
> >>
> >>>
> >>> thanks,
> >>>
> >>> --
> >>> NS
> >
> >
> >
> > --
> > NS
>



-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
Okay,

I did a rebuild and the menu populated. Very strange.

Now I have two more problems.

>From the test procedure:

Wait for secondary storage VM coming up.
> This may take a bit...


No clue about this. How do I know when the storage VM has come up?

I checked under instances and storage and nothing changed for about 10
minutes.

Last three lines in console are:

  [sshexec]      [java] WARN  [network.element.VpcVirtualRouterElement]
(secstorage-1:) Network Ntwk[203|Storage|4] is not associated with any VPC
  [sshexec]      [java] INFO  [network.security.SecurityGroupListener]
(AgentManager-Handler-2:) Received a host startup notification
  [sshexec]      [java] INFO  [cloud.consoleproxy.ConsoleProxyManagerImpl]
(AgentManager-Handler-2:) Successfully sent out command to start HTTP
handling in console proxy agent

I decided to proceed to the next stage, on the off chance it had worked.

I get stuck on this step:

In step 2, select "tiny Linux"


There are no templates to select from!

https://www.evernote.com/shard/s18/sh/1a151896-8cbb-41c8-93d2-d844e6461146/08efa5dddbd86cb96d7895692f9ec20d
https://www.evernote.com/shard/s18/sh/ee10c37e-dad1-454f-a43f-e64d9ef7d9e3/bce4465e03169a3883f825fbb6f43cd1
https://www.evernote.com/shard/s18/sh/58221024-608f-4a7f-9531-53c267532efc/cbdb8204c77471ae2fa194355af40430

I am unable to proceed.

P.S. Testing CloudStack on my MBA is exceptionally slow. Is there any way
to do the whole thing on or something? I practically cannot do anything
else on my computer while testing.

On 28 October 2012 00:12, Chip Childers <ch...@sungard.com> wrote:

> Yeah.  Funny enough, that IS the infra menu option.
>
> I've never seen this before.
>
> I assume you are logged in as admin / password?  Can you do a fresh
> build (start with "ant clean-all build-all")?
>
> - chip
>
> Sent from my iPhone.
>
> On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:
>
> > I doubt it. Looks like part of the application code.
> >
> > My real problem is that I am unable to complete this step, as there is
> > nothing labeled "Infrastructure" in the UI.
> >
> > On 27 October 2012 19:04, Chip Childers <ch...@sungard.com>
> wrote:
> >
> >> Comments below:
> >>
> >> - chip
> >>
> >> Sent from my iPhone.
> >>
> >> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:
> >>
> >>> Sig: OK
> >>> Hashes: OK
> >>> Source checks: OK
> >>> RAT: OK
> >>> Build: OK
> >>>
> >>> However, during this:
> >>>
> >>> mvn -P deps
> >>>
> >>> I noticed line like this:
> >>>
> >>> [INFO] Installing
> >>>> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
> >> to
> >>
> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> >>>> [INFO]
> >>>>
> >>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
> >>>> [INFO]
> >>>>
> ------------------------------------------------------------------------
> >>>
> >>>
> >>> Any idea why that says incubating-SNAPSHOT?
> >>
> >> That's the default build version. If we do a binary release, it would
> >> be changed via the maven release tools.
> >>
> >>>
> >>> A bigger problem is that I am stuck with the additional testing.
> >>>
> >>> Specifically, this step:
> >>>
> >>> Click "Infrastructure", click the "View All" button in the "Zones"
> >> display
> >>>> box, click "add zone"
> >>>
> >>>
> >>> Here's what my console looks like:
> >>
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
> >>>
> >>> Note the oddly unlabelled cloud icon, which when clicked, displays:
> >>
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
> >>>
> >>> I would like to be able to complete this testing, but would be prepared
> >> to
> >>> vote without it.
> >>>
> >>> Can someone help me?
> >>
> >> Browser specific issue?  Is it consistent?
> >>
> >>>
> >>> thanks,
> >>>
> >>> --
> >>> NS
> >
> >
> >
> > --
> > NS
>



-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
Yeah.  Funny enough, that IS the infra menu option.

I've never seen this before.

I assume you are logged in as admin / password?  Can you do a fresh
build (start with "ant clean-all build-all")?

- chip

Sent from my iPhone.

On Oct 27, 2012, at 5:06 PM, Noah Slater <ns...@apache.org> wrote:

> I doubt it. Looks like part of the application code.
>
> My real problem is that I am unable to complete this step, as there is
> nothing labeled "Infrastructure" in the UI.
>
> On 27 October 2012 19:04, Chip Childers <ch...@sungard.com> wrote:
>
>> Comments below:
>>
>> - chip
>>
>> Sent from my iPhone.
>>
>> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:
>>
>>> Sig: OK
>>> Hashes: OK
>>> Source checks: OK
>>> RAT: OK
>>> Build: OK
>>>
>>> However, during this:
>>>
>>> mvn -P deps
>>>
>>> I noticed line like this:
>>>
>>> [INFO] Installing
>>>> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
>> to
>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>>>> [INFO]
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>
>>>
>>> Any idea why that says incubating-SNAPSHOT?
>>
>> That's the default build version. If we do a binary release, it would
>> be changed via the maven release tools.
>>
>>>
>>> A bigger problem is that I am stuck with the additional testing.
>>>
>>> Specifically, this step:
>>>
>>> Click "Infrastructure", click the "View All" button in the "Zones"
>> display
>>>> box, click "add zone"
>>>
>>>
>>> Here's what my console looks like:
>> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>>>
>>> Note the oddly unlabelled cloud icon, which when clicked, displays:
>> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>>>
>>> I would like to be able to complete this testing, but would be prepared
>> to
>>> vote without it.
>>>
>>> Can someone help me?
>>
>> Browser specific issue?  Is it consistent?
>>
>>>
>>> thanks,
>>>
>>> --
>>> NS
>
>
>
> --
> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Simon Weller <sw...@ena.com>.
Noah, 


Are you logged in as a ROOT admin, or a domain user? The infrastructure option is only available to the admin ROOT domain accounts. 
What platform and browser are you testing with? 


- Si 


----- Original Message -----

From: "Noah Slater" <ns...@apache.org> 
To: cloudstack-dev@incubator.apache.org 
Sent: Saturday, October 27, 2012 4:06:44 PM 
Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round 

I doubt it. Looks like part of the application code. 

My real problem is that I am unable to complete this step, as there is 
nothing labeled "Infrastructure" in the UI. 

On 27 October 2012 19:04, Chip Childers <ch...@sungard.com> wrote: 

> Comments below: 
> 
> - chip 
> 
> Sent from my iPhone. 
> 
> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote: 
> 
> > Sig: OK 
> > Hashes: OK 
> > Source checks: OK 
> > RAT: OK 
> > Build: OK 
> > 
> > However, during this: 
> > 
> > mvn -P deps 
> > 
> > I noticed line like this: 
> > 
> > [INFO] Installing 
> >> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml 
> to 
> >> 
> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom 
> >> [INFO] 
> >> 
> >> [INFO] 
> >> ------------------------------------------------------------------------ 
> >> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT 
> >> [INFO] 
> >> ------------------------------------------------------------------------ 
> > 
> > 
> > Any idea why that says incubating-SNAPSHOT? 
> 
> That's the default build version. If we do a binary release, it would 
> be changed via the maven release tools. 
> 
> > 
> > A bigger problem is that I am stuck with the additional testing. 
> > 
> > Specifically, this step: 
> > 
> > Click "Infrastructure", click the "View All" button in the "Zones" 
> display 
> >> box, click "add zone" 
> > 
> > 
> > Here's what my console looks like: 
> > 
> > 
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82 
> > 
> > Note the oddly unlabelled cloud icon, which when clicked, displays: 
> > 
> > 
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380 
> > 
> > I would like to be able to complete this testing, but would be prepared 
> to 
> > vote without it. 
> > 
> > Can someone help me? 
> 
> Browser specific issue? Is it consistent? 
> 
> > 
> > thanks, 
> > 
> > -- 
> > NS 
> 



-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
I doubt it. Looks like part of the application code.

My real problem is that I am unable to complete this step, as there is
nothing labeled "Infrastructure" in the UI.

On 27 October 2012 19:04, Chip Childers <ch...@sungard.com> wrote:

> Comments below:
>
> - chip
>
> Sent from my iPhone.
>
> On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:
>
> > Sig: OK
> > Hashes: OK
> > Source checks: OK
> > RAT: OK
> > Build: OK
> >
> > However, during this:
> >
> > mvn -P deps
> >
> > I noticed line like this:
> >
> > [INFO] Installing
> >> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
> to
> >>
> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> >> [INFO]
> >>
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
> >> [INFO]
> >> ------------------------------------------------------------------------
> >
> >
> > Any idea why that says incubating-SNAPSHOT?
>
> That's the default build version. If we do a binary release, it would
> be changed via the maven release tools.
>
> >
> > A bigger problem is that I am stuck with the additional testing.
> >
> > Specifically, this step:
> >
> > Click "Infrastructure", click the "View All" button in the "Zones"
> display
> >> box, click "add zone"
> >
> >
> > Here's what my console looks like:
> >
> >
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
> >
> > Note the oddly unlabelled cloud icon, which when clicked, displays:
> >
> >
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
> >
> > I would like to be able to complete this testing, but would be prepared
> to
> > vote without it.
> >
> > Can someone help me?
>
> Browser specific issue?  Is it consistent?
>
> >
> > thanks,
> >
> > --
> > NS
>



-- 
NS

Re: Maven version in release WAS: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Brett Porter <br...@apache.org>.
On 28/10/2012, at 5:04 AM, Chip Childers <ch...@sungard.com> wrote:

>> I noticed line like this:
>> 
>> [INFO] Installing
>>> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml to
>>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>>> [INFO]
>>> 
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>>> [INFO]
>>> ------------------------------------------------------------------------
>> 
>> 
>> Any idea why that says incubating-SNAPSHOT?
> 
> That's the default build version. If we do a binary release, it would
> be changed via the maven release tools.

Sorry to have glazed over that. While it's not a blocker for the release, it is potentially confusing. I'd suggest changing the release process next time around to get the Maven version right on the tag and source release.

Here is how the Maven project approaches it: http://maven.apache.org/developers/release/maven-core-release.html

- Brett

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
Comments below:

- chip

Sent from my iPhone.

On Oct 27, 2012, at 1:28 PM, Noah Slater <ns...@apache.org> wrote:

> Sig: OK
> Hashes: OK
> Source checks: OK
> RAT: OK
> Build: OK
>
> However, during this:
>
> mvn -P deps
>
> I noticed line like this:
>
> [INFO] Installing
>> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml to
>> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
>> [INFO]
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
>> [INFO]
>> ------------------------------------------------------------------------
>
>
> Any idea why that says incubating-SNAPSHOT?

That's the default build version. If we do a binary release, it would
be changed via the maven release tools.

>
> A bigger problem is that I am stuck with the additional testing.
>
> Specifically, this step:
>
> Click "Infrastructure", click the "View All" button in the "Zones" display
>> box, click "add zone"
>
>
> Here's what my console looks like:
>
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
>
> Note the oddly unlabelled cloud icon, which when clicked, displays:
>
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
>
> I would like to be able to complete this testing, but would be prepared to
> vote without it.
>
> Can someone help me?

Browser specific issue?  Is it consistent?

>
> thanks,
>
> --
> NS

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Jessica Wang <Je...@citrix.com>.
Noah,

The 2 links you provided below are not working: "Oops, we encountered an error."

Jessica

-----Original Message-----
From: Alex Huang 
Sent: Saturday, October 27, 2012 5:39 PM
To: cloudstack-dev@incubator.apache.org
Cc: Jessica Wang; Brian Federle
Subject: RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Jessica or Brian,

Can you comment on what Noah is seeing in the two links?  

Thanks.

--Alex

> -----Original Message-----
> From: Noah Slater [mailto:nslater@apache.org]
> Sent: Saturday, October 27, 2012 10:29 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> Sig: OK
> Hashes: OK
> Source checks: OK
> RAT: OK
> Build: OK
> 
> However, during this:
> 
> mvn -P deps
> 
> I noticed line like this:
> 
> [INFO] Installing
> > /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
> > to
> > /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-i
> > ncubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> > [INFO]
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > -- [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> 
> 
> Any idea why that says incubating-SNAPSHOT?
> 
> A bigger problem is that I am stuck with the additional testing.
> 
> Specifically, this step:
> 
> Click "Infrastructure", click the "View All" button in the "Zones" display
> > box, click "add zone"
> 
> 
> Here's what my console looks like:
> 
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-
> ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
> 
> Note the oddly unlabelled cloud icon, which when clicked, displays:
> 
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-
> e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
> 
> I would like to be able to complete this testing, but would be prepared to
> vote without it.
> 
> Can someone help me?
> 
> thanks,
> 
> --
> NS

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Alex Huang <Al...@citrix.com>.
Jessica or Brian,

Can you comment on what Noah is seeing in the two links?  

Thanks.

--Alex

> -----Original Message-----
> From: Noah Slater [mailto:nslater@apache.org]
> Sent: Saturday, October 27, 2012 10:29 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> Sig: OK
> Hashes: OK
> Source checks: OK
> RAT: OK
> Build: OK
> 
> However, during this:
> 
> mvn -P deps
> 
> I noticed line like this:
> 
> [INFO] Installing
> > /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml
> > to
> > /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-i
> > ncubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> > [INFO]
> >
> > [INFO]
> > ----------------------------------------------------------------------
> > -- [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> 
> 
> Any idea why that says incubating-SNAPSHOT?
> 
> A bigger problem is that I am stuck with the additional testing.
> 
> Specifically, this step:
> 
> Click "Infrastructure", click the "View All" button in the "Zones" display
> > box, click "add zone"
> 
> 
> Here's what my console looks like:
> 
> https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-
> ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82
> 
> Note the oddly unlabelled cloud icon, which when clicked, displays:
> 
> https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-
> e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380
> 
> I would like to be able to complete this testing, but would be prepared to
> vote without it.
> 
> Can someone help me?
> 
> thanks,
> 
> --
> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
Sig: OK
Hashes: OK
Source checks: OK
RAT: OK
Build: OK

However, during this:

mvn -P deps

I noticed line like this:

[INFO] Installing
> /private/tmp/cloudstack/apache-cloudstack-4.0.0-incubating-src/pom.xml to
> /Users/nslater/.m2/repository/org/apache/cloudstack/cloudstack/4.0.0-incubating-SNAPSHOT/cloudstack-4.0.0-incubating-SNAPSHOT.pom
> [INFO]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Apache CloudStack Utils 4.0.0-incubating-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------


Any idea why that says incubating-SNAPSHOT?

A bigger problem is that I am stuck with the additional testing.

Specifically, this step:

Click "Infrastructure", click the "View All" button in the "Zones" display
> box, click "add zone"


Here's what my console looks like:

https://www.evernote.com/shard/s18/sh/4df76607-12ea-42d6-b73a-ff36a9435d7b/510f4a49695062e03aa03fa45d32ad82

Note the oddly unlabelled cloud icon, which when clicked, displays:

https://www.evernote.com/shard/s18/sh/95042d8c-06fa-4c56-8f89-e9b4bc2b80a4/f1b06913bdb8a327cf1c554f88899380

I would like to be able to complete this testing, but would be prepared to
vote without it.

Can someone help me?

thanks,

-- 
NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Mice Xia <we...@gmail.com>.
+1

tested aritifact http://jenkins.cloudstack.org/job/build-4.0-nonoss-rhel63/140/
with following setup:

Advanced Zone with two cluster,
one cluster using vSphere 5.1 (yes it's 5.1), one ESXi 5.1 host,
validated VM lifecycle management.
one cluster using XenServer 5.6 sp2, VM lifecyle worked fine.

Regards
Mice

2012/10/24 Rohit Yadav <ro...@citrix.com>:
> +1, tested using devcloud, building, packaging (for ubuntu) and deployment worked.
> Basic zone setup went fine, had given 3GB to devcloud and successfully ran a one user vm: http://www.bhaisaab.org/vms/cent.vhd (minimal cent fork)
>
> Regards.
> ________________________________________
> From: Edison Su [Edison.su@citrix.com]
> Sent: Wednesday, October 24, 2012 4:19 AM
> To: cloudstack-dev@incubator.apache.org; Chip Childers (ASF)
> Subject: RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
>
> It's a build issue, nothing related to our code.
>
>> -----Original Message-----
>> From: Chandan Purushothama [mailto:Chandan.Purushothama@citrix.com]
>> Sent: Tuesday, October 23, 2012 3:33 PM
>> To: cloudstack-dev@incubator.apache.org; Chip Childers (ASF)
>> Subject: RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
>> round
>>
>> I failed with the Cloud Agent Installation on Ubuntu 12.04
>> https://issues.apache.org/jira/browse/CLOUDSTACK-408
>>
>> Thank you,
>> Chandan.
>>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Tuesday, October 23, 2012 2:18 PM
>> To: Chip Childers (ASF)
>> Cc: cloudstack-dev@incubator.apache.org
>> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
>> round
>>
>> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
>> <ch...@apache.org> wrote:
>> > Hi All,
>> >
>> > I would like to call a vote for Apache CloudStack (Incubating)
>> Release
>> > 4.0.0-incubating (third round).
>> >
>> > We encourage the whole community to download and test these release
>> > artifacts, so that any critical issues can be resolved before the
>> > release is made. The more time that each individual spends reviewing
>> > the artifacts, the higher confidence we can have in both the release
>> > itself and our ability to pass an IPMC vote later on.  Everyone is
>> > free to vote on this release, so please give it a shot.
>> >
>> > Instructions for Validating and Testing the artifacts can be found
>> here:
>> >
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+
>> > test+procedure
>> >
>> > If you have any trouble setting up a test environment using the
>> > procedure above, please ask on the cloudstack-dev@i.a.o list.
>> Someone
>> > will be sure to help, and we'll improve our test procedure
>> > documentation at the same time!
>> >
>> > Now, on to the specifics of what we are voting on...
>> >
>> >
>> > The following artifacts are up for the vote:
>> >
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
>> > incubating/
>> >
>> > PGP release keys (signed using A99A5D58):
>> > http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>> >
>> > Branch: 4.0
>> > Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>> >
>> >
>> > List of changes:
>> > https://git-wip-us.apache.org/repos/asf?p=incubator-
>> cloudstack.git;a=b
>> > lob_plain;f=CHANGES;hb=refs/heads/4.0
>> >
>> > The artifacts being voted on during this round also include the
>> > following additional fixes (most were identified as part of testing
>> > during the last round of voting):
>> >
>> > * Many documentation fixes (particularly the release notes and
>> > installation guide)
>> > * CLOUDSTACK-341: Failing to display Management Traffic Details on
>> the
>> > UI
>> > * CLOUDSTACK-349: Russian l10n not properly displaying
>> > * Correction to the devcloud rdeploy build target, to make testing
>> > easier
>> > * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
>> > will fail
>> > * CLOUDSTACK-118: Status of host resorce stuck in
>> "ErrorInMaintenance"
>> > * DISCLAIMER added to the Marvin tool dir
>> >
>> >
>> > The vote will be open for 72 hours.
>> >
>> >
>> > For sanity in tallying the vote, can PPMC and IPMC members please be
>> > sure to indicate "(binding)" with their vote?
>> > [ ] +1  approve
>> > [ ] +0  no opinion
>> > [ ] -1  disapprove (and reason why)
>> >
>> > Thanks!
>>
>> Hi all,
>>
>> 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
>> to test and cast your vote!
>>
>> -chip

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Rohit Yadav <ro...@citrix.com>.
+1, tested using devcloud, building, packaging (for ubuntu) and deployment worked.
Basic zone setup went fine, had given 3GB to devcloud and successfully ran a one user vm: http://www.bhaisaab.org/vms/cent.vhd (minimal cent fork)

Regards.
________________________________________
From: Edison Su [Edison.su@citrix.com]
Sent: Wednesday, October 24, 2012 4:19 AM
To: cloudstack-dev@incubator.apache.org; Chip Childers (ASF)
Subject: RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

It's a build issue, nothing related to our code.

> -----Original Message-----
> From: Chandan Purushothama [mailto:Chandan.Purushothama@citrix.com]
> Sent: Tuesday, October 23, 2012 3:33 PM
> To: cloudstack-dev@incubator.apache.org; Chip Childers (ASF)
> Subject: RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
> round
>
> I failed with the Cloud Agent Installation on Ubuntu 12.04
> https://issues.apache.org/jira/browse/CLOUDSTACK-408
>
> Thank you,
> Chandan.
>
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 23, 2012 2:18 PM
> To: Chip Childers (ASF)
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
> round
>
> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
> <ch...@apache.org> wrote:
> > Hi All,
> >
> > I would like to call a vote for Apache CloudStack (Incubating)
> Release
> > 4.0.0-incubating (third round).
> >
> > We encourage the whole community to download and test these release
> > artifacts, so that any critical issues can be resolved before the
> > release is made. The more time that each individual spends reviewing
> > the artifacts, the higher confidence we can have in both the release
> > itself and our ability to pass an IPMC vote later on.  Everyone is
> > free to vote on this release, so please give it a shot.
> >
> > Instructions for Validating and Testing the artifacts can be found
> here:
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+
> > test+procedure
> >
> > If you have any trouble setting up a test environment using the
> > procedure above, please ask on the cloudstack-dev@i.a.o list.
> Someone
> > will be sure to help, and we'll improve our test procedure
> > documentation at the same time!
> >
> > Now, on to the specifics of what we are voting on...
> >
> >
> > The following artifacts are up for the vote:
> >
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> > incubating/
> >
> > PGP release keys (signed using A99A5D58):
> > http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >
> > Branch: 4.0
> > Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> >
> >
> > List of changes:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-
> cloudstack.git;a=b
> > lob_plain;f=CHANGES;hb=refs/heads/4.0
> >
> > The artifacts being voted on during this round also include the
> > following additional fixes (most were identified as part of testing
> > during the last round of voting):
> >
> > * Many documentation fixes (particularly the release notes and
> > installation guide)
> > * CLOUDSTACK-341: Failing to display Management Traffic Details on
> the
> > UI
> > * CLOUDSTACK-349: Russian l10n not properly displaying
> > * Correction to the devcloud rdeploy build target, to make testing
> > easier
> > * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
> > will fail
> > * CLOUDSTACK-118: Status of host resorce stuck in
> "ErrorInMaintenance"
> > * DISCLAIMER added to the Marvin tool dir
> >
> >
> > The vote will be open for 72 hours.
> >
> >
> > For sanity in tallying the vote, can PPMC and IPMC members please be
> > sure to indicate "(binding)" with their vote?
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Thanks!
>
> Hi all,
>
> 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
> to test and cast your vote!
>
> -chip

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Edison Su <Ed...@citrix.com>.
It's a build issue, nothing related to our code.

> -----Original Message-----
> From: Chandan Purushothama [mailto:Chandan.Purushothama@citrix.com]
> Sent: Tuesday, October 23, 2012 3:33 PM
> To: cloudstack-dev@incubator.apache.org; Chip Childers (ASF)
> Subject: RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
> round
> 
> I failed with the Cloud Agent Installation on Ubuntu 12.04
> https://issues.apache.org/jira/browse/CLOUDSTACK-408
> 
> Thank you,
> Chandan.
> 
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 23, 2012 2:18 PM
> To: Chip Childers (ASF)
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
> round
> 
> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
> <ch...@apache.org> wrote:
> > Hi All,
> >
> > I would like to call a vote for Apache CloudStack (Incubating)
> Release
> > 4.0.0-incubating (third round).
> >
> > We encourage the whole community to download and test these release
> > artifacts, so that any critical issues can be resolved before the
> > release is made. The more time that each individual spends reviewing
> > the artifacts, the higher confidence we can have in both the release
> > itself and our ability to pass an IPMC vote later on.  Everyone is
> > free to vote on this release, so please give it a shot.
> >
> > Instructions for Validating and Testing the artifacts can be found
> here:
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+
> > test+procedure
> >
> > If you have any trouble setting up a test environment using the
> > procedure above, please ask on the cloudstack-dev@i.a.o list.
> Someone
> > will be sure to help, and we'll improve our test procedure
> > documentation at the same time!
> >
> > Now, on to the specifics of what we are voting on...
> >
> >
> > The following artifacts are up for the vote:
> >
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> > incubating/
> >
> > PGP release keys (signed using A99A5D58):
> > http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >
> > Branch: 4.0
> > Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> >
> >
> > List of changes:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-
> cloudstack.git;a=b
> > lob_plain;f=CHANGES;hb=refs/heads/4.0
> >
> > The artifacts being voted on during this round also include the
> > following additional fixes (most were identified as part of testing
> > during the last round of voting):
> >
> > * Many documentation fixes (particularly the release notes and
> > installation guide)
> > * CLOUDSTACK-341: Failing to display Management Traffic Details on
> the
> > UI
> > * CLOUDSTACK-349: Russian l10n not properly displaying
> > * Correction to the devcloud rdeploy build target, to make testing
> > easier
> > * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
> > will fail
> > * CLOUDSTACK-118: Status of host resorce stuck in
> "ErrorInMaintenance"
> > * DISCLAIMER added to the Marvin tool dir
> >
> >
> > The vote will be open for 72 hours.
> >
> >
> > For sanity in tallying the vote, can PPMC and IPMC members please be
> > sure to indicate "(binding)" with their vote?
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Thanks!
> 
> Hi all,
> 
> 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
> to test and cast your vote!
> 
> -chip

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chandan Purushothama <Ch...@citrix.com>.
I failed with the Cloud Agent Installation on Ubuntu 12.04 https://issues.apache.org/jira/browse/CLOUDSTACK-408 

Thank you,
Chandan.

-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com] 
Sent: Tuesday, October 23, 2012 2:18 PM
To: Chip Childers (ASF)
Cc: cloudstack-dev@incubator.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF) <ch...@apache.org> wrote:
> Hi All,
>
> I would like to call a vote for Apache CloudStack (Incubating) Release 
> 4.0.0-incubating (third round).
>
> We encourage the whole community to download and test these release 
> artifacts, so that any critical issues can be resolved before the 
> release is made. The more time that each individual spends reviewing 
> the artifacts, the higher confidence we can have in both the release 
> itself and our ability to pass an IPMC vote later on.  Everyone is 
> free to vote on this release, so please give it a shot.
>
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+
> test+procedure
>
> If you have any trouble setting up a test environment using the 
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone 
> will be sure to help, and we'll improve our test procedure 
> documentation at the same time!
>
> Now, on to the specifics of what we are voting on...
>
>
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> incubating/
>
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>
>
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=b
> lob_plain;f=CHANGES;hb=refs/heads/4.0
>
> The artifacts being voted on during this round also include the 
> following additional fixes (most were identified as part of testing 
> during the last round of voting):
>
> * Many documentation fixes (particularly the release notes and 
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the 
> UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing 
> easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build 
> will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
>
>
> The vote will be open for 72 hours.
>
>
> For sanity in tallying the vote, can PPMC and IPMC members please be 
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Thanks!

Hi all,

1 day down, and we have 2 +1 votes so far.  Please take an opportunity to test and cast your vote!

-chip

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Srikanteswararao Talluri <sr...@citrix.com>.
+1 

Tested with devcloud, 
created a basic zone and 
-started an instance, 
-created a volume and attached/detached to/from the VM
-took snapshots and created templates & volumes from it.

All the above went fine.

Thanks,
~Talluri


-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com] 
Sent: Wednesday, October 24, 2012 2:48 AM
To: Chip Childers (ASF)
Cc: cloudstack-dev@incubator.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF) <ch...@apache.org> wrote:
> Hi All,
>
> I would like to call a vote for Apache CloudStack (Incubating) Release 
> 4.0.0-incubating (third round).
>
> We encourage the whole community to download and test these release 
> artifacts, so that any critical issues can be resolved before the 
> release is made. The more time that each individual spends reviewing 
> the artifacts, the higher confidence we can have in both the release 
> itself and our ability to pass an IPMC vote later on.  Everyone is 
> free to vote on this release, so please give it a shot.
>
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+
> test+procedure
>
> If you have any trouble setting up a test environment using the 
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone 
> will be sure to help, and we'll improve our test procedure 
> documentation at the same time!
>
> Now, on to the specifics of what we are voting on...
>
>
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-
> incubating/
>
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>
>
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=b
> lob_plain;f=CHANGES;hb=refs/heads/4.0
>
> The artifacts being voted on during this round also include the 
> following additional fixes (most were identified as part of testing 
> during the last round of voting):
>
> * Many documentation fixes (particularly the release notes and 
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the 
> UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing 
> easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build 
> will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
>
>
> The vote will be open for 72 hours.
>
>
> For sanity in tallying the vote, can PPMC and IPMC members please be 
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Thanks!

Hi all,

1 day down, and we have 2 +1 votes so far.  Please take an opportunity to test and cast your vote!

-chip

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Charles Moulliard <ch...@gmail.com>.
+1

Been able to install DevCloud image in VirtualBox and deploy/test this
release following instructions here
https://cwiki.apache.org/CLOUDSTACK/cloudstack-40-test-procedure.html and
help  of Sebastian ;-)

On Thu, Oct 25, 2012 at 5:41 PM, Chip Childers <ch...@sungard.com>wrote:

> Hi all,
>
> Thanks again to everyone that has tested and voted!
>
> It looks like we have all of the required votes at this point, but I'm
> going to hold the vote thread open until I see more of the PPMC
> members vote.  Specifically, I'd like to see Edison, Will, Kevin, John
> and hopefully Noah.
>
> If I can at least get 4 of the 5 folks to vote, I'll close it out.
> Ideally, we would close it out today...
>
> -chip
>
> On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers
> <ch...@sungard.com> wrote:
> > On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
> > <ch...@apache.org> wrote:
> >> Hi All,
> >>
> >> I would like to call a vote for Apache CloudStack (Incubating) Release
> >> 4.0.0-incubating (third round).
> >>
> >> We encourage the whole community to download and test these release
> >> artifacts, so that any critical issues can be resolved before the
> >> release is made. The more time that each individual spends reviewing
> >> the artifacts, the higher confidence we can have in both the release
> >> itself and our ability to pass an IPMC vote later on.  Everyone is free
> >> to vote on this release, so please give it a shot.
> >>
> >> Instructions for Validating and Testing the artifacts can be found here:
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
> >>
> >> If you have any trouble setting up a test environment using the
> >> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
> >> will be sure to help, and we'll improve our test procedure
> >> documentation at the same time!
> >>
> >> Now, on to the specifics of what we are voting on...
> >>
> >>
> >> The following artifacts are up for the vote:
> >>
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
> >>
> >> PGP release keys (signed using A99A5D58):
> >> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >>
> >> Branch: 4.0
> >> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> >>
> >>
> >> List of changes:
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
> >>
> >> The artifacts being voted on during this round also include the
> >> following additional fixes (most were identified as part of testing
> >> during the last round of voting):
> >>
> >> * Many documentation fixes (particularly the release notes and
> >> installation guide)
> >> * CLOUDSTACK-341: Failing to display Management Traffic Details on the
> UI
> >> * CLOUDSTACK-349: Russian l10n not properly displaying
> >> * Correction to the devcloud rdeploy build target, to make testing
> easier
> >> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will
> fail
> >> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> >> * DISCLAIMER added to the Marvin tool dir
> >>
> >>
> >> The vote will be open for 72 hours.
> >>
> >>
> >> For sanity in tallying the vote, can PPMC and IPMC members please be
> >> sure to indicate "(binding)" with their vote?
> >> [ ] +1  approve
> >> [ ] +0  no opinion
> >> [ ] -1  disapprove (and reason why)
> >>
> >> Thanks!
> >
> > Hi all,
> >
> > 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
> > to test and cast your vote!
> >
> > -chip
>



-- 
Charles Moulliard
Apache Committer / Sr. Enterprise Architect (RedHat)
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Ahmad Emneina <Ah...@citrix.com>.
+1

Used the binary bits for rhel6 on centOS 6.3
-xenserver HV
-NSF storage

Advanced zone
3 tier vpc with ACLs for inter VLAN communication.
Also tested VPN connectivity from my Mac running 10.6.8, into my guests isolated network

Ahmad

On Oct 26, 2012, at 7:30 AM, "Chip Childers" <ch...@sungard.com> wrote:

> On Fri, Oct 26, 2012 at 2:48 AM, Gavin Lee <ga...@gmail.com> wrote:
>> Still can vote?
>> My +1 vote, did not try DevCloud but below testing:
> 
> Yup, it counts.  I'm holding off for a few more folks to vote before
> closing out the thread.
> 
> Thanks again for the testing!
> 
>> Passed package verification
>> Passed source verification
>> Passed license header verification
>> Passed compile
>> 
>> Passed installation on CentOS6.2 x64
>> Create 2 zones successfully:
>> --1 basic zone with 1 cluster with 1 xenserver 6.02 hypervisors
>> --1 advanced zone with 1 cluster 2  xenserver(6.02) hypervisors
>> 
>> Passed template registration(CentOS5.6 x64 vhd template)
>> Can add host into cluster
>> Can access VM via console proxy
>> Passed VMs lifecycle testing in advanced zone:
>> create|restart|stop|expunge and live migration
>> 
>> 
>> On Fri, Oct 26, 2012 at 4:50 AM, Chip Childers
>> <ch...@sungard.com> wrote:
>>> Quick follow-up:
>>> 
>>> I'm going to hold the vote open a few more days, to give Kevin, John
>>> and Noah a chance to cast their votes.
>>> 
>>> Will and Edison, thanks for the +1's.  (And thanks everyone else!)
>>> 
>>> -chip
>>> 
>>> On Thu, Oct 25, 2012 at 11:41 AM, Chip Childers
>>> <ch...@sungard.com> wrote:
>>>> Hi all,
>>>> 
>>>> Thanks again to everyone that has tested and voted!
>>>> 
>>>> It looks like we have all of the required votes at this point, but I'm
>>>> going to hold the vote thread open until I see more of the PPMC
>>>> members vote.  Specifically, I'd like to see Edison, Will, Kevin, John
>>>> and hopefully Noah.
>>>> 
>>>> If I can at least get 4 of the 5 folks to vote, I'll close it out.
>>>> Ideally, we would close it out today...
>>>> 
>>>> -chip
>>>> 
>>>> On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers
>>>> <ch...@sungard.com> wrote:
>>>>> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
>>>>> <ch...@apache.org> wrote:
>>>>>> Hi All,
>>>>>> 
>>>>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>>>>> 4.0.0-incubating (third round).
>>>>>> 
>>>>>> We encourage the whole community to download and test these release
>>>>>> artifacts, so that any critical issues can be resolved before the
>>>>>> release is made. The more time that each individual spends reviewing
>>>>>> the artifacts, the higher confidence we can have in both the release
>>>>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>>>>> to vote on this release, so please give it a shot.
>>>>>> 
>>>>>> Instructions for Validating and Testing the artifacts can be found here:
>>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>>>>> 
>>>>>> If you have any trouble setting up a test environment using the
>>>>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>>>>> will be sure to help, and we'll improve our test procedure
>>>>>> documentation at the same time!
>>>>>> 
>>>>>> Now, on to the specifics of what we are voting on...
>>>>>> 
>>>>>> 
>>>>>> The following artifacts are up for the vote:
>>>>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>>>>> 
>>>>>> PGP release keys (signed using A99A5D58):
>>>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>>>> 
>>>>>> Branch: 4.0
>>>>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>>>> 
>>>>>> 
>>>>>> List of changes:
>>>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>>>> 
>>>>>> The artifacts being voted on during this round also include the
>>>>>> following additional fixes (most were identified as part of testing
>>>>>> during the last round of voting):
>>>>>> 
>>>>>> * Many documentation fixes (particularly the release notes and
>>>>>> installation guide)
>>>>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>>>>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>>>>> * Correction to the devcloud rdeploy build target, to make testing easier
>>>>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>>>>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>>>>> * DISCLAIMER added to the Marvin tool dir
>>>>>> 
>>>>>> 
>>>>>> The vote will be open for 72 hours.
>>>>>> 
>>>>>> 
>>>>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>>>>> sure to indicate "(binding)" with their vote?
>>>>>> [ ] +1  approve
>>>>>> [ ] +0  no opinion
>>>>>> [ ] -1  disapprove (and reason why)
>>>>>> 
>>>>>> Thanks!
>>>>> 
>>>>> Hi all,
>>>>> 
>>>>> 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
>>>>> to test and cast your vote!
>>>>> 
>>>>> -chip
>> 
>> 
>> 
>> --
>> Gavin
>>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Fri, Oct 26, 2012 at 2:48 AM, Gavin Lee <ga...@gmail.com> wrote:
> Still can vote?
> My +1 vote, did not try DevCloud but below testing:

Yup, it counts.  I'm holding off for a few more folks to vote before
closing out the thread.

Thanks again for the testing!

> Passed package verification
> Passed source verification
> Passed license header verification
> Passed compile
>
> Passed installation on CentOS6.2 x64
> Create 2 zones successfully:
> --1 basic zone with 1 cluster with 1 xenserver 6.02 hypervisors
> --1 advanced zone with 1 cluster 2  xenserver(6.02) hypervisors
>
> Passed template registration(CentOS5.6 x64 vhd template)
> Can add host into cluster
> Can access VM via console proxy
> Passed VMs lifecycle testing in advanced zone:
> create|restart|stop|expunge and live migration
>
>
> On Fri, Oct 26, 2012 at 4:50 AM, Chip Childers
> <ch...@sungard.com> wrote:
>> Quick follow-up:
>>
>> I'm going to hold the vote open a few more days, to give Kevin, John
>> and Noah a chance to cast their votes.
>>
>> Will and Edison, thanks for the +1's.  (And thanks everyone else!)
>>
>> -chip
>>
>> On Thu, Oct 25, 2012 at 11:41 AM, Chip Childers
>> <ch...@sungard.com> wrote:
>>> Hi all,
>>>
>>> Thanks again to everyone that has tested and voted!
>>>
>>> It looks like we have all of the required votes at this point, but I'm
>>> going to hold the vote thread open until I see more of the PPMC
>>> members vote.  Specifically, I'd like to see Edison, Will, Kevin, John
>>> and hopefully Noah.
>>>
>>> If I can at least get 4 of the 5 folks to vote, I'll close it out.
>>> Ideally, we would close it out today...
>>>
>>> -chip
>>>
>>> On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers
>>> <ch...@sungard.com> wrote:
>>>> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
>>>> <ch...@apache.org> wrote:
>>>>> Hi All,
>>>>>
>>>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>>>> 4.0.0-incubating (third round).
>>>>>
>>>>> We encourage the whole community to download and test these release
>>>>> artifacts, so that any critical issues can be resolved before the
>>>>> release is made. The more time that each individual spends reviewing
>>>>> the artifacts, the higher confidence we can have in both the release
>>>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>>>> to vote on this release, so please give it a shot.
>>>>>
>>>>> Instructions for Validating and Testing the artifacts can be found here:
>>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>>>>
>>>>> If you have any trouble setting up a test environment using the
>>>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>>>> will be sure to help, and we'll improve our test procedure
>>>>> documentation at the same time!
>>>>>
>>>>> Now, on to the specifics of what we are voting on...
>>>>>
>>>>>
>>>>> The following artifacts are up for the vote:
>>>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>>>>
>>>>> PGP release keys (signed using A99A5D58):
>>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>>>
>>>>> Branch: 4.0
>>>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>>>
>>>>>
>>>>> List of changes:
>>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>>>
>>>>> The artifacts being voted on during this round also include the
>>>>> following additional fixes (most were identified as part of testing
>>>>> during the last round of voting):
>>>>>
>>>>> * Many documentation fixes (particularly the release notes and
>>>>> installation guide)
>>>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>>>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>>>> * Correction to the devcloud rdeploy build target, to make testing easier
>>>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>>>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>>>> * DISCLAIMER added to the Marvin tool dir
>>>>>
>>>>>
>>>>> The vote will be open for 72 hours.
>>>>>
>>>>>
>>>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>>>> sure to indicate "(binding)" with their vote?
>>>>> [ ] +1  approve
>>>>> [ ] +0  no opinion
>>>>> [ ] -1  disapprove (and reason why)
>>>>>
>>>>> Thanks!
>>>>
>>>> Hi all,
>>>>
>>>> 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
>>>> to test and cast your vote!
>>>>
>>>> -chip
>
>
>
> --
> Gavin
>

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Gavin Lee <ga...@gmail.com>.
Still can vote?
My +1 vote, did not try DevCloud but below testing:

Passed package verification
Passed source verification
Passed license header verification
Passed compile

Passed installation on CentOS6.2 x64
Create 2 zones successfully:
--1 basic zone with 1 cluster with 1 xenserver 6.02 hypervisors
--1 advanced zone with 1 cluster 2  xenserver(6.02) hypervisors

Passed template registration(CentOS5.6 x64 vhd template)
Can add host into cluster
Can access VM via console proxy
Passed VMs lifecycle testing in advanced zone:
create|restart|stop|expunge and live migration


On Fri, Oct 26, 2012 at 4:50 AM, Chip Childers
<ch...@sungard.com> wrote:
> Quick follow-up:
>
> I'm going to hold the vote open a few more days, to give Kevin, John
> and Noah a chance to cast their votes.
>
> Will and Edison, thanks for the +1's.  (And thanks everyone else!)
>
> -chip
>
> On Thu, Oct 25, 2012 at 11:41 AM, Chip Childers
> <ch...@sungard.com> wrote:
>> Hi all,
>>
>> Thanks again to everyone that has tested and voted!
>>
>> It looks like we have all of the required votes at this point, but I'm
>> going to hold the vote thread open until I see more of the PPMC
>> members vote.  Specifically, I'd like to see Edison, Will, Kevin, John
>> and hopefully Noah.
>>
>> If I can at least get 4 of the 5 folks to vote, I'll close it out.
>> Ideally, we would close it out today...
>>
>> -chip
>>
>> On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers
>> <ch...@sungard.com> wrote:
>>> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
>>> <ch...@apache.org> wrote:
>>>> Hi All,
>>>>
>>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>>> 4.0.0-incubating (third round).
>>>>
>>>> We encourage the whole community to download and test these release
>>>> artifacts, so that any critical issues can be resolved before the
>>>> release is made. The more time that each individual spends reviewing
>>>> the artifacts, the higher confidence we can have in both the release
>>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>>> to vote on this release, so please give it a shot.
>>>>
>>>> Instructions for Validating and Testing the artifacts can be found here:
>>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>>>
>>>> If you have any trouble setting up a test environment using the
>>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>>> will be sure to help, and we'll improve our test procedure
>>>> documentation at the same time!
>>>>
>>>> Now, on to the specifics of what we are voting on...
>>>>
>>>>
>>>> The following artifacts are up for the vote:
>>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>>>
>>>> PGP release keys (signed using A99A5D58):
>>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>>
>>>> Branch: 4.0
>>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>>
>>>>
>>>> List of changes:
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>>
>>>> The artifacts being voted on during this round also include the
>>>> following additional fixes (most were identified as part of testing
>>>> during the last round of voting):
>>>>
>>>> * Many documentation fixes (particularly the release notes and
>>>> installation guide)
>>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>>> * Correction to the devcloud rdeploy build target, to make testing easier
>>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>>> * DISCLAIMER added to the Marvin tool dir
>>>>
>>>>
>>>> The vote will be open for 72 hours.
>>>>
>>>>
>>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>>> sure to indicate "(binding)" with their vote?
>>>> [ ] +1  approve
>>>> [ ] +0  no opinion
>>>> [ ] -1  disapprove (and reason why)
>>>>
>>>> Thanks!
>>>
>>> Hi all,
>>>
>>> 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
>>> to test and cast your vote!
>>>
>>> -chip



-- 
Gavin

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Alex Huang <Al...@citrix.com>.
What I ended up doing was mount my windows share on devcloud, use devcloud to do practically all the steps but placed all artifacts in the mounted windows share, and did the final compile and deploy from my laptop.

Devcloud is just the bee's knees.  :)

--Alex

> -----Original Message-----
> From: Noah Slater [mailto:nslater@apache.org]
> Sent: Monday, October 29, 2012 7:04 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> Alex, do you know enough to fix those instructions?
> 
> On 30 October 2012 01:01, Alex Huang <Al...@citrix.com> wrote:
> 
> > +1 Sorry for being late because I've been tied up in other stuff and
> > because the instruction doesn't work on windows (yeah yeah windows
> > wmindows).  But I finally gave it a quick test and it worked.
> >
> > --Alex
> >
> > > -----Original Message-----
> > > From: Chip Childers [mailto:chip.childers@sungard.com]
> > > Sent: Thursday, October 25, 2012 1:51 PM
> > > To: cloudstack-dev@incubator.apache.org; Edison Su; Will Chan; Kevin
> > Kluge;
> > > John Kinsella; nslater@apache.org
> > > Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release,
> > > third
> > round
> > >
> > > Quick follow-up:
> > >
> > > I'm going to hold the vote open a few more days, to give Kevin, John
> > > and Noah a chance to cast their votes.
> > >
> > > Will and Edison, thanks for the +1's.  (And thanks everyone else!)
> > >
> > > -chip
> > >
> > > On Thu, Oct 25, 2012 at 11:41 AM, Chip Childers <
> > chip.childers@sungard.com>
> > > wrote:
> > > > Hi all,
> > > >
> > > > Thanks again to everyone that has tested and voted!
> > > >
> > > > It looks like we have all of the required votes at this point, but
> > > > I'm going to hold the vote thread open until I see more of the
> > > > PPMC members vote.  Specifically, I'd like to see Edison, Will,
> > > > Kevin, John and hopefully Noah.
> > > >
> > > > If I can at least get 4 of the 5 folks to vote, I'll close it out.
> > > > Ideally, we would close it out today...
> > > >
> > > > -chip
> > > >
> > > > On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers
> > > > <ch...@sungard.com> wrote:
> > > >> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
> > > >> <ch...@apache.org> wrote:
> > > >>> Hi All,
> > > >>>
> > > >>> I would like to call a vote for Apache CloudStack (Incubating)
> > > >>> Release 4.0.0-incubating (third round).
> > > >>>
> > > >>> We encourage the whole community to download and test these
> > > release
> > > >>> artifacts, so that any critical issues can be resolved before
> > > >>> the release is made. The more time that each individual spends
> > > >>> reviewing the artifacts, the higher confidence we can have in
> > > >>> both the release itself and our ability to pass an IPMC vote
> > > >>> later on.  Everyone is free to vote on this release, so please give it a
> shot.
> > > >>>
> > > >>> Instructions for Validating and Testing the artifacts can be
> > > >>> found
> > here:
> > > >>>
> > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.
> > > >>> 0+test+procedure
> > > >>>
> > > >>> If you have any trouble setting up a test environment using the
> > > >>> procedure above, please ask on the cloudstack-dev@i.a.o list.
> > > >>> Someone will be sure to help, and we'll improve our test
> > > >>> procedure documentation at the same time!
> > > >>>
> > > >>> Now, on to the specifics of what we are voting on...
> > > >>>
> > > >>>
> > > >>> The following artifacts are up for the vote:
> > > >>>
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.
> > > >>> 0-incubating/
> > > >>>
> > > >>> PGP release keys (signed using A99A5D58):
> > > >>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> > > >>>
> > > >>> Branch: 4.0
> > > >>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> > > >>>
> > > >>>
> > > >>> List of changes:
> > > >>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.g
> > > >>> it;a
> > > >>> =blob_plain;f=CHANGES;hb=refs/heads/4.0
> > > >>>
> > > >>> The artifacts being voted on during this round also include the
> > > >>> following additional fixes (most were identified as part of
> > > >>> testing during the last round of voting):
> > > >>>
> > > >>> * Many documentation fixes (particularly the release notes and
> > > >>> installation guide)
> > > >>> * CLOUDSTACK-341: Failing to display Management Traffic Details
> > > >>> on the UI
> > > >>> * CLOUDSTACK-349: Russian l10n not properly displaying
> > > >>> * Correction to the devcloud rdeploy build target, to make
> > > >>> testing easier
> > > >>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current
> > > >>> build will fail
> > > >>> * CLOUDSTACK-118: Status of host resorce stuck in
> > > "ErrorInMaintenance"
> > > >>> * DISCLAIMER added to the Marvin tool dir
> > > >>>
> > > >>>
> > > >>> The vote will be open for 72 hours.
> > > >>>
> > > >>>
> > > >>> For sanity in tallying the vote, can PPMC and IPMC members
> > > >>> please be sure to indicate "(binding)" with their vote?
> > > >>> [ ] +1  approve
> > > >>> [ ] +0  no opinion
> > > >>> [ ] -1  disapprove (and reason why)
> > > >>>
> > > >>> Thanks!
> > > >>
> > > >> Hi all,
> > > >>
> > > >> 1 day down, and we have 2 +1 votes so far.  Please take an
> > > >> opportunity to test and cast your vote!
> > > >>
> > > >> -chip
> >
> 
> 
> 
> --
> NS

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Noah Slater <ns...@apache.org>.
Alex, do you know enough to fix those instructions?

On 30 October 2012 01:01, Alex Huang <Al...@citrix.com> wrote:

> +1 Sorry for being late because I've been tied up in other stuff and
> because the instruction doesn't work on windows (yeah yeah windows
> wmindows).  But I finally gave it a quick test and it worked.
>
> --Alex
>
> > -----Original Message-----
> > From: Chip Childers [mailto:chip.childers@sungard.com]
> > Sent: Thursday, October 25, 2012 1:51 PM
> > To: cloudstack-dev@incubator.apache.org; Edison Su; Will Chan; Kevin
> Kluge;
> > John Kinsella; nslater@apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third
> round
> >
> > Quick follow-up:
> >
> > I'm going to hold the vote open a few more days, to give Kevin, John and
> > Noah a chance to cast their votes.
> >
> > Will and Edison, thanks for the +1's.  (And thanks everyone else!)
> >
> > -chip
> >
> > On Thu, Oct 25, 2012 at 11:41 AM, Chip Childers <
> chip.childers@sungard.com>
> > wrote:
> > > Hi all,
> > >
> > > Thanks again to everyone that has tested and voted!
> > >
> > > It looks like we have all of the required votes at this point, but I'm
> > > going to hold the vote thread open until I see more of the PPMC
> > > members vote.  Specifically, I'd like to see Edison, Will, Kevin, John
> > > and hopefully Noah.
> > >
> > > If I can at least get 4 of the 5 folks to vote, I'll close it out.
> > > Ideally, we would close it out today...
> > >
> > > -chip
> > >
> > > On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers
> > > <ch...@sungard.com> wrote:
> > >> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
> > >> <ch...@apache.org> wrote:
> > >>> Hi All,
> > >>>
> > >>> I would like to call a vote for Apache CloudStack (Incubating)
> > >>> Release 4.0.0-incubating (third round).
> > >>>
> > >>> We encourage the whole community to download and test these
> > release
> > >>> artifacts, so that any critical issues can be resolved before the
> > >>> release is made. The more time that each individual spends reviewing
> > >>> the artifacts, the higher confidence we can have in both the release
> > >>> itself and our ability to pass an IPMC vote later on.  Everyone is
> > >>> free to vote on this release, so please give it a shot.
> > >>>
> > >>> Instructions for Validating and Testing the artifacts can be found
> here:
> > >>>
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.
> > >>> 0+test+procedure
> > >>>
> > >>> If you have any trouble setting up a test environment using the
> > >>> procedure above, please ask on the cloudstack-dev@i.a.o list.
> > >>> Someone will be sure to help, and we'll improve our test procedure
> > >>> documentation at the same time!
> > >>>
> > >>> Now, on to the specifics of what we are voting on...
> > >>>
> > >>>
> > >>> The following artifacts are up for the vote:
> > >>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.
> > >>> 0-incubating/
> > >>>
> > >>> PGP release keys (signed using A99A5D58):
> > >>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> > >>>
> > >>> Branch: 4.0
> > >>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> > >>>
> > >>>
> > >>> List of changes:
> > >>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a
> > >>> =blob_plain;f=CHANGES;hb=refs/heads/4.0
> > >>>
> > >>> The artifacts being voted on during this round also include the
> > >>> following additional fixes (most were identified as part of testing
> > >>> during the last round of voting):
> > >>>
> > >>> * Many documentation fixes (particularly the release notes and
> > >>> installation guide)
> > >>> * CLOUDSTACK-341: Failing to display Management Traffic Details on
> > >>> the UI
> > >>> * CLOUDSTACK-349: Russian l10n not properly displaying
> > >>> * Correction to the devcloud rdeploy build target, to make testing
> > >>> easier
> > >>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
> > >>> will fail
> > >>> * CLOUDSTACK-118: Status of host resorce stuck in
> > "ErrorInMaintenance"
> > >>> * DISCLAIMER added to the Marvin tool dir
> > >>>
> > >>>
> > >>> The vote will be open for 72 hours.
> > >>>
> > >>>
> > >>> For sanity in tallying the vote, can PPMC and IPMC members please be
> > >>> sure to indicate "(binding)" with their vote?
> > >>> [ ] +1  approve
> > >>> [ ] +0  no opinion
> > >>> [ ] -1  disapprove (and reason why)
> > >>>
> > >>> Thanks!
> > >>
> > >> Hi all,
> > >>
> > >> 1 day down, and we have 2 +1 votes so far.  Please take an
> > >> opportunity to test and cast your vote!
> > >>
> > >> -chip
>



-- 
NS

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Alex Huang <Al...@citrix.com>.
+1 Sorry for being late because I've been tied up in other stuff and because the instruction doesn't work on windows (yeah yeah windows wmindows).  But I finally gave it a quick test and it worked.

--Alex

> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Thursday, October 25, 2012 1:51 PM
> To: cloudstack-dev@incubator.apache.org; Edison Su; Will Chan; Kevin Kluge;
> John Kinsella; nslater@apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> Quick follow-up:
> 
> I'm going to hold the vote open a few more days, to give Kevin, John and
> Noah a chance to cast their votes.
> 
> Will and Edison, thanks for the +1's.  (And thanks everyone else!)
> 
> -chip
> 
> On Thu, Oct 25, 2012 at 11:41 AM, Chip Childers <ch...@sungard.com>
> wrote:
> > Hi all,
> >
> > Thanks again to everyone that has tested and voted!
> >
> > It looks like we have all of the required votes at this point, but I'm
> > going to hold the vote thread open until I see more of the PPMC
> > members vote.  Specifically, I'd like to see Edison, Will, Kevin, John
> > and hopefully Noah.
> >
> > If I can at least get 4 of the 5 folks to vote, I'll close it out.
> > Ideally, we would close it out today...
> >
> > -chip
> >
> > On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers
> > <ch...@sungard.com> wrote:
> >> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
> >> <ch...@apache.org> wrote:
> >>> Hi All,
> >>>
> >>> I would like to call a vote for Apache CloudStack (Incubating)
> >>> Release 4.0.0-incubating (third round).
> >>>
> >>> We encourage the whole community to download and test these
> release
> >>> artifacts, so that any critical issues can be resolved before the
> >>> release is made. The more time that each individual spends reviewing
> >>> the artifacts, the higher confidence we can have in both the release
> >>> itself and our ability to pass an IPMC vote later on.  Everyone is
> >>> free to vote on this release, so please give it a shot.
> >>>
> >>> Instructions for Validating and Testing the artifacts can be found here:
> >>>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.
> >>> 0+test+procedure
> >>>
> >>> If you have any trouble setting up a test environment using the
> >>> procedure above, please ask on the cloudstack-dev@i.a.o list.
> >>> Someone will be sure to help, and we'll improve our test procedure
> >>> documentation at the same time!
> >>>
> >>> Now, on to the specifics of what we are voting on...
> >>>
> >>>
> >>> The following artifacts are up for the vote:
> >>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.
> >>> 0-incubating/
> >>>
> >>> PGP release keys (signed using A99A5D58):
> >>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >>>
> >>> Branch: 4.0
> >>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> >>>
> >>>
> >>> List of changes:
> >>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a
> >>> =blob_plain;f=CHANGES;hb=refs/heads/4.0
> >>>
> >>> The artifacts being voted on during this round also include the
> >>> following additional fixes (most were identified as part of testing
> >>> during the last round of voting):
> >>>
> >>> * Many documentation fixes (particularly the release notes and
> >>> installation guide)
> >>> * CLOUDSTACK-341: Failing to display Management Traffic Details on
> >>> the UI
> >>> * CLOUDSTACK-349: Russian l10n not properly displaying
> >>> * Correction to the devcloud rdeploy build target, to make testing
> >>> easier
> >>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
> >>> will fail
> >>> * CLOUDSTACK-118: Status of host resorce stuck in
> "ErrorInMaintenance"
> >>> * DISCLAIMER added to the Marvin tool dir
> >>>
> >>>
> >>> The vote will be open for 72 hours.
> >>>
> >>>
> >>> For sanity in tallying the vote, can PPMC and IPMC members please be
> >>> sure to indicate "(binding)" with their vote?
> >>> [ ] +1  approve
> >>> [ ] +0  no opinion
> >>> [ ] -1  disapprove (and reason why)
> >>>
> >>> Thanks!
> >>
> >> Hi all,
> >>
> >> 1 day down, and we have 2 +1 votes so far.  Please take an
> >> opportunity to test and cast your vote!
> >>
> >> -chip

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
Quick follow-up:

I'm going to hold the vote open a few more days, to give Kevin, John
and Noah a chance to cast their votes.

Will and Edison, thanks for the +1's.  (And thanks everyone else!)

-chip

On Thu, Oct 25, 2012 at 11:41 AM, Chip Childers
<ch...@sungard.com> wrote:
> Hi all,
>
> Thanks again to everyone that has tested and voted!
>
> It looks like we have all of the required votes at this point, but I'm
> going to hold the vote thread open until I see more of the PPMC
> members vote.  Specifically, I'd like to see Edison, Will, Kevin, John
> and hopefully Noah.
>
> If I can at least get 4 of the 5 folks to vote, I'll close it out.
> Ideally, we would close it out today...
>
> -chip
>
> On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers
> <ch...@sungard.com> wrote:
>> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
>> <ch...@apache.org> wrote:
>>> Hi All,
>>>
>>> I would like to call a vote for Apache CloudStack (Incubating) Release
>>> 4.0.0-incubating (third round).
>>>
>>> We encourage the whole community to download and test these release
>>> artifacts, so that any critical issues can be resolved before the
>>> release is made. The more time that each individual spends reviewing
>>> the artifacts, the higher confidence we can have in both the release
>>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>>> to vote on this release, so please give it a shot.
>>>
>>> Instructions for Validating and Testing the artifacts can be found here:
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>>
>>> If you have any trouble setting up a test environment using the
>>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>>> will be sure to help, and we'll improve our test procedure
>>> documentation at the same time!
>>>
>>> Now, on to the specifics of what we are voting on...
>>>
>>>
>>> The following artifacts are up for the vote:
>>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>>
>>> PGP release keys (signed using A99A5D58):
>>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>>
>>> Branch: 4.0
>>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>>
>>>
>>> List of changes:
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>>
>>> The artifacts being voted on during this round also include the
>>> following additional fixes (most were identified as part of testing
>>> during the last round of voting):
>>>
>>> * Many documentation fixes (particularly the release notes and
>>> installation guide)
>>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>>> * CLOUDSTACK-349: Russian l10n not properly displaying
>>> * Correction to the devcloud rdeploy build target, to make testing easier
>>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>>> * DISCLAIMER added to the Marvin tool dir
>>>
>>>
>>> The vote will be open for 72 hours.
>>>
>>>
>>> For sanity in tallying the vote, can PPMC and IPMC members please be
>>> sure to indicate "(binding)" with their vote?
>>> [ ] +1  approve
>>> [ ] +0  no opinion
>>> [ ] -1  disapprove (and reason why)
>>>
>>> Thanks!
>>
>> Hi all,
>>
>> 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
>> to test and cast your vote!
>>
>> -chip

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
Fantastic! Thanks Kevin.

Still hoping to hear from John and Noah!

-chip

On Fri, Oct 26, 2012 at 3:52 PM, Kevin Kluge <Ke...@citrix.com> wrote:
> +1 (binding)
>
> CentOS 6.2 for MS + XS 6.0.2 and NFS for primary.
>
> The docs are vastly improved from what I saw in the last vote round.  I have a few nits but will just file them as bugs.
>
> -kevin
>
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Thursday, October 25, 2012 8:42 AM
>> To: cloudstack-dev@incubator.apache.org; Edison Su; Will Chan; Kevin Kluge;
>> John Kinsella; nslater@apache.org
>> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
>>
>> Hi all,
>>
>> Thanks again to everyone that has tested and voted!
>>
>> It looks like we have all of the required votes at this point, but I'm going to hold
>> the vote thread open until I see more of the PPMC members vote.  Specifically,
>> I'd like to see Edison, Will, Kevin, John and hopefully Noah.
>>
>> If I can at least get 4 of the 5 folks to vote, I'll close it out.
>> Ideally, we would close it out today...
>>
>> -chip
>>
>> On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers <ch...@sungard.com>
>> wrote:
>> > On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
>> > <ch...@apache.org> wrote:
>> >> Hi All,
>> >>
>> >> I would like to call a vote for Apache CloudStack (Incubating)
>> >> Release 4.0.0-incubating (third round).
>> >>
>> >> We encourage the whole community to download and test these release
>> >> artifacts, so that any critical issues can be resolved before the
>> >> release is made. The more time that each individual spends reviewing
>> >> the artifacts, the higher confidence we can have in both the release
>> >> itself and our ability to pass an IPMC vote later on.  Everyone is
>> >> free to vote on this release, so please give it a shot.
>> >>
>> >> Instructions for Validating and Testing the artifacts can be found here:
>> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0
>> >> +test+procedure
>> >>
>> >> If you have any trouble setting up a test environment using the
>> >> procedure above, please ask on the cloudstack-dev@i.a.o list.
>> >> Someone will be sure to help, and we'll improve our test procedure
>> >> documentation at the same time!
>> >>
>> >> Now, on to the specifics of what we are voting on...
>> >>
>> >>
>> >> The following artifacts are up for the vote:
>> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0
>> >> -incubating/
>> >>
>> >> PGP release keys (signed using A99A5D58):
>> >> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>> >>
>> >> Branch: 4.0
>> >> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>> >>
>> >>
>> >> List of changes:
>> >> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=
>> >> blob_plain;f=CHANGES;hb=refs/heads/4.0
>> >>
>> >> The artifacts being voted on during this round also include the
>> >> following additional fixes (most were identified as part of testing
>> >> during the last round of voting):
>> >>
>> >> * Many documentation fixes (particularly the release notes and
>> >> installation guide)
>> >> * CLOUDSTACK-341: Failing to display Management Traffic Details on
>> >> the UI
>> >> * CLOUDSTACK-349: Russian l10n not properly displaying
>> >> * Correction to the devcloud rdeploy build target, to make testing
>> >> easier
>> >> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
>> >> will fail
>> >> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>> >> * DISCLAIMER added to the Marvin tool dir
>> >>
>> >>
>> >> The vote will be open for 72 hours.
>> >>
>> >>
>> >> For sanity in tallying the vote, can PPMC and IPMC members please be
>> >> sure to indicate "(binding)" with their vote?
>> >> [ ] +1  approve
>> >> [ ] +0  no opinion
>> >> [ ] -1  disapprove (and reason why)
>> >>
>> >> Thanks!
>> >
>> > Hi all,
>> >
>> > 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
>> > to test and cast your vote!
>> >
>> > -chip
>

RE: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Kevin Kluge <Ke...@citrix.com>.
+1 (binding)

CentOS 6.2 for MS + XS 6.0.2 and NFS for primary.

The docs are vastly improved from what I saw in the last vote round.  I have a few nits but will just file them as bugs.

-kevin


> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Thursday, October 25, 2012 8:42 AM
> To: cloudstack-dev@incubator.apache.org; Edison Su; Will Chan; Kevin Kluge;
> John Kinsella; nslater@apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
> 
> Hi all,
> 
> Thanks again to everyone that has tested and voted!
> 
> It looks like we have all of the required votes at this point, but I'm going to hold
> the vote thread open until I see more of the PPMC members vote.  Specifically,
> I'd like to see Edison, Will, Kevin, John and hopefully Noah.
> 
> If I can at least get 4 of the 5 folks to vote, I'll close it out.
> Ideally, we would close it out today...
> 
> -chip
> 
> On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers <ch...@sungard.com>
> wrote:
> > On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
> > <ch...@apache.org> wrote:
> >> Hi All,
> >>
> >> I would like to call a vote for Apache CloudStack (Incubating)
> >> Release 4.0.0-incubating (third round).
> >>
> >> We encourage the whole community to download and test these release
> >> artifacts, so that any critical issues can be resolved before the
> >> release is made. The more time that each individual spends reviewing
> >> the artifacts, the higher confidence we can have in both the release
> >> itself and our ability to pass an IPMC vote later on.  Everyone is
> >> free to vote on this release, so please give it a shot.
> >>
> >> Instructions for Validating and Testing the artifacts can be found here:
> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0
> >> +test+procedure
> >>
> >> If you have any trouble setting up a test environment using the
> >> procedure above, please ask on the cloudstack-dev@i.a.o list.
> >> Someone will be sure to help, and we'll improve our test procedure
> >> documentation at the same time!
> >>
> >> Now, on to the specifics of what we are voting on...
> >>
> >>
> >> The following artifacts are up for the vote:
> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0
> >> -incubating/
> >>
> >> PGP release keys (signed using A99A5D58):
> >> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
> >>
> >> Branch: 4.0
> >> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
> >>
> >>
> >> List of changes:
> >> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=
> >> blob_plain;f=CHANGES;hb=refs/heads/4.0
> >>
> >> The artifacts being voted on during this round also include the
> >> following additional fixes (most were identified as part of testing
> >> during the last round of voting):
> >>
> >> * Many documentation fixes (particularly the release notes and
> >> installation guide)
> >> * CLOUDSTACK-341: Failing to display Management Traffic Details on
> >> the UI
> >> * CLOUDSTACK-349: Russian l10n not properly displaying
> >> * Correction to the devcloud rdeploy build target, to make testing
> >> easier
> >> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
> >> will fail
> >> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> >> * DISCLAIMER added to the Marvin tool dir
> >>
> >>
> >> The vote will be open for 72 hours.
> >>
> >>
> >> For sanity in tallying the vote, can PPMC and IPMC members please be
> >> sure to indicate "(binding)" with their vote?
> >> [ ] +1  approve
> >> [ ] +0  no opinion
> >> [ ] -1  disapprove (and reason why)
> >>
> >> Thanks!
> >
> > Hi all,
> >
> > 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
> > to test and cast your vote!
> >
> > -chip

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
Hi all,

Thanks again to everyone that has tested and voted!

It looks like we have all of the required votes at this point, but I'm
going to hold the vote thread open until I see more of the PPMC
members vote.  Specifically, I'd like to see Edison, Will, Kevin, John
and hopefully Noah.

If I can at least get 4 of the 5 folks to vote, I'll close it out.
Ideally, we would close it out today...

-chip

On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers
<ch...@sungard.com> wrote:
> On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
> <ch...@apache.org> wrote:
>> Hi All,
>>
>> I would like to call a vote for Apache CloudStack (Incubating) Release
>> 4.0.0-incubating (third round).
>>
>> We encourage the whole community to download and test these release
>> artifacts, so that any critical issues can be resolved before the
>> release is made. The more time that each individual spends reviewing
>> the artifacts, the higher confidence we can have in both the release
>> itself and our ability to pass an IPMC vote later on.  Everyone is free
>> to vote on this release, so please give it a shot.
>>
>> Instructions for Validating and Testing the artifacts can be found here:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>>
>> If you have any trouble setting up a test environment using the
>> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
>> will be sure to help, and we'll improve our test procedure
>> documentation at the same time!
>>
>> Now, on to the specifics of what we are voting on...
>>
>>
>> The following artifacts are up for the vote:
>> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>>
>> PGP release keys (signed using A99A5D58):
>> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>>
>> Branch: 4.0
>> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>>
>>
>> List of changes:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>>
>> The artifacts being voted on during this round also include the
>> following additional fixes (most were identified as part of testing
>> during the last round of voting):
>>
>> * Many documentation fixes (particularly the release notes and
>> installation guide)
>> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
>> * CLOUDSTACK-349: Russian l10n not properly displaying
>> * Correction to the devcloud rdeploy build target, to make testing easier
>> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
>> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>> * DISCLAIMER added to the Marvin tool dir
>>
>>
>> The vote will be open for 72 hours.
>>
>>
>> For sanity in tallying the vote, can PPMC and IPMC members please be
>> sure to indicate "(binding)" with their vote?
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Thanks!
>
> Hi all,
>
> 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
> to test and cast your vote!
>
> -chip

Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round

Posted by Chip Childers <ch...@sungard.com>.
On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
<ch...@apache.org> wrote:
> Hi All,
>
> I would like to call a vote for Apache CloudStack (Incubating) Release
> 4.0.0-incubating (third round).
>
> We encourage the whole community to download and test these release
> artifacts, so that any critical issues can be resolved before the
> release is made. The more time that each individual spends reviewing
> the artifacts, the higher confidence we can have in both the release
> itself and our ability to pass an IPMC vote later on.  Everyone is free
> to vote on this release, so please give it a shot.
>
> Instructions for Validating and Testing the artifacts can be found here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure
>
> If you have any trouble setting up a test environment using the
> procedure above, please ask on the cloudstack-dev@i.a.o list.  Someone
> will be sure to help, and we'll improve our test procedure
> documentation at the same time!
>
> Now, on to the specifics of what we are voting on...
>
>
> The following artifacts are up for the vote:
> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0-incubating/
>
> PGP release keys (signed using A99A5D58):
> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>
> Branch: 4.0
> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>
>
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=blob_plain;f=CHANGES;hb=refs/heads/4.0
>
> The artifacts being voted on during this round also include the
> following additional fixes (most were identified as part of testing
> during the last round of voting):
>
> * Many documentation fixes (particularly the release notes and
> installation guide)
> * CLOUDSTACK-341: Failing to display Management Traffic Details on the UI
> * CLOUDSTACK-349: Russian l10n not properly displaying
> * Correction to the devcloud rdeploy build target, to make testing easier
> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build will fail
> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
> * DISCLAIMER added to the Marvin tool dir
>
>
> The vote will be open for 72 hours.
>
>
> For sanity in tallying the vote, can PPMC and IPMC members please be
> sure to indicate "(binding)" with their vote?
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Thanks!

Hi all,

1 day down, and we have 2 +1 votes so far.  Please take an opportunity
to test and cast your vote!

-chip