I have tested username and password support for cloud monkey. 1. It breaks when a non privileged user issue some commands. For example: . When a non admin user issues Œlist zones¹ 2. It is not handled when the api port is set to 8096 and (username, password) are provided. 3. What takes precedence when (apikey, secret key) and (username, password) both are provided.
Thanks, ~Talluri On 29/04/14 2:01 pm, "sebgoa" <[email protected]> wrote: > >On Apr 25, 2014, at 7:40 PM, Chiradeep Vittal ><[email protected]> wrote: > >> Please follow the Release test procedure below >> https://cwiki.apache.org/confluence/x/2iNqAg > > >Followed the testing procedure and tested on exoscale > >+1 > > >> >> From: Chiradeep Vittal >><[email protected]<mailto:[email protected]>> >> Reply-To: "[email protected]<mailto:[email protected]>" >><[email protected]<mailto:[email protected]>> >> Date: Thursday, April 24, 2014 at 5:12 PM >> To: "[email protected]<mailto:[email protected]>" >><[email protected]<mailto:[email protected]>> >> Subject: [VOTE] Release Apache CloudStack CloudMonkey 5.1.0 >> >> Hi All, >> >> I've created a 5.1.0 release of CloudMonkey, with the following >>artifacts >> up for a vote: >> >> Git Branch and Commit SH: >> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=sh >>or >> tlog;h=refs/heads/5.1.0 >> Commit: 0b7a6bce246bbf261e6f096d1c18a85949ed5a22 >> >> List of changes: >> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=bl >>ob >> _plain;f=CHANGES;hb=5.1.0 >> >> Source release (checksums and signatures are available at the same >> location): >> https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-5.1.0/ >> >> PGP release keys (signed using E8DAE809): >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS >> >> Vote will be open for 72 hours. >> >> For sanity in tallying the vote, can PMC members please be sure to >> indicate "(binding)" with their vote? >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> >
