Adding cloudstack-dev
FYI..
From: Salvatore Orlando
Sent: Monday, April 30, 2012 2:08 PM
To: Sanjeev Neelarapu; Kevin Kluge; Chiradeep Vittal
Cc: #Cloud - Bonita
Subject: RE: Test cases for Open vSwitch Tunnel Manager
Hi Sanjeev,
Thanks for preparing and sharing this document.
I have the fol
Thanks for the update, will wait Frank's chiming in then.
Haroon
On 4/30/12 10:18 PM, "Prachi Damle" wrote:
>There is one issue Frank will be fixing tomorrow for the rpm build, after
>that Sangeetha and Swamy can use it.
>
>I will update once that fix is in.
>
>Thanks,
>Prachi
>
>-Original
There is one issue Frank will be fixing tomorrow for the rpm build, after that
Sangeetha and Swamy can use it.
I will update once that fix is in.
Thanks,
Prachi
-Original Message-
From: Haroon Abdelrahman
Sent: Monday, April 30, 2012 10:15 PM
To: cloudstack-dev@incubator.apache.org; P
Many thanks Prachi, that¹s one day earlier than planned
Swamy and Sangeetha,
For your notice.
Haroon
On 4/30/12 5:42 PM, "Prachi Damle" wrote:
>Hi,
>
>The cloudbridge-ec2-integration branch has been merged to 3.0.x.
>I have tested the dev. build and did some tests.
>
>Let me know if you find a
In your example, they would need to know how the cloud is accepting the
password. Perhaps, they can give multiple options. It's not an easy way to
solve but multiple parameters is not going to solve this solution because (1)
there may be other ways to pass in the password and (2) I suppose the
On Apr 30, 2012, at 9:11 PM, Will Chan wrote:
> The parameter for password is simply just used to pass information from the
> client to CS. It's really up to the AuthenticatorAdapter to decide how it
> should use the parameter. Since by default, MD5 hashed password is being
> passed in,
The parameter for password is simply just used to pass information from the
client to CS. It's really up to the AuthenticatorAdapter to decide how it
should use the parameter. Since by default, MD5 hashed password is being
passed in, the default adapter is just doing a simple comparison againt
I think Abhi's proposal would avoid all this, yes?
I am not sure if I like have a single parameter that can be either MD5 (as in
2.2.x) , either MD5 or plaintext (as in 3.0.x), or plaintext (as in some future
release when MD5 has been deprecated).The alternative is to just introduce
a ne
OK, I just added that as a fourth issue. Thanks.
-kevin
> -Original Message-
> From: Brett Porter [mailto:br...@porterclan.net] On Behalf Of Brett Porter
> Sent: Monday, April 30, 2012 6:01 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Incubator PMC/Board report for May 20
On 01/05/2012, at 4:34 AM, Kevin Kluge wrote:
> I haven't seen changes to our board report in a few days. Can we get one of
> the mentors to sign off on it?
I'll take a look.
>
> We could discuss the "top 3" issues blocking graduation. I wish we could do
> 4. I'd like to add that we nee
As part of the ec2-integration branch merge, DB schema has been changed as below
Run following to work with your existing mgmt. db.
ALTER TABLE `cloud`.`account` ADD COLUMN `default_zone_id` bigint unsigned;
ALTER TABLE `cloud`.`account` ADD CONSTRAINT `fk_account__default_zone_id`
FOREIGN KEY
Hi,
The cloudbridge-ec2-integration branch has been merged to 3.0.x.
I have tested the dev. build and did some tests.
Let me know if you find any issues after getting the latest.
Thanks,
Prachi
I haven't seen changes to our board report in a few days. Can we get one of
the mentors to sign off on it?
We could discuss the "top 3" issues blocking graduation. I wish we could do
4. I'd like to add that we need to remove the non-ASF-approved license code
from the project as it's clearl
I also want to point out that this is simply the default behavior for a brand
new CS install and as Chiradeep pointed out, it only applies to the
session-based login that requires a username/password.
We should not be changing this behavior by default on an upgrade because some
people may just
Dear podling,
This email was sent by an automated system on behalf of the Apache Incubator
PMC.
It is an initial reminder to give you plenty of time to prepare your quarterly
board report.
The board meeting is scheduled for Wed, 16 May 2012, 10:00:00 PST. The report
for your podling will form
Just wanted to point out this only affects the session-based logins via
the GUI (although one can script this kind of API interaction as well).
API-key-based authentication continues as before.
On 4/30/12 9:15 AM, "Abhinandan Prateek"
wrote:
>The deprecation of MD5 can be done in a graceful fash
The deprecation of MD5 can be done in a graceful fashion with the following
scheme:
We add a Authenticator which can take plaintext password and add it after the
MD5 authenticator. Anyone who is already using the MD5 password in API will
continue to function as they are now.
Anyone upgrading i
This means the client has to figure out whether to send MD5 hash or cleartext
on a per-cloud basis. That seems unreasonable.
Why don't we just send plain text passwords and expect the use of SSL? We'd
have to add a new parameter and deprecate the current MD5 hash password.
-kevin
> -Ori
18 matches
Mail list logo
