openstack team mailing list archive

[Ziad Sawalha <ziad.sawalha@xxxxxxxxxxxxx>]

We were working on providing the necessary functionality in Keystone but stopped when we heard of the alternative solution. We could resume the conversation about what is needed on the Keystone side and implement if needed.

Z

From: Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx<mailto:sandy.walsh@xxxxxxxxxxxxx>>
Date: Thu, 2 Feb 2012 01:49:58 +0000
To: Joshua McKenty <joshua@xxxxxxxxxxxxxxx<mailto:joshua@xxxxxxxxxxxxxxx>>, Vishvananda Ishaya <vishvananda@xxxxxxxxx<mailto:vishvananda@xxxxxxxxx>>
Cc: "openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>" <openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>>
Subject: Re: [Openstack] Remove Zones code - FFE

Understood, timing is everything. I'll let Chris talk about expected timing for the replacement.  From a deployers side, nothing would really change, just some configuration options ... but a replacement should be available.

I'm sure we could get it working pretty easily. The Keystone integration was the biggest pita.

I can keep this branch fresh with trunk for when we're ready to pull the trigger.

-S

________________________________
From: Joshua McKenty [joshua@xxxxxxxxxxxxxxx<mailto:joshua@xxxxxxxxxxxxxxx>]
Sent: Wednesday, February 01, 2012 4:45 PM
To: Vishvananda Ishaya
Cc: Sandy Walsh; openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Openstack] Remove Zones code - FFE

+1 to Vish's points. I know there are some folks coming online in the Folsom timeline that can help out with the new stuff, but this feels a bit like going backwards.

--
Joshua McKenty, CEO
Piston Cloud Computing, Inc.
w: (650) 24-CLOUD
m: (650) 283-6846
http://www.pistoncloud.com

"Oh, Westley, we'll never survive!"
"Nonsense. You're only saying that because no one ever has."


On Wednesday, February 1, 2012 at 12:41 PM, Vishvananda Ishaya wrote:

I am all for pulling this out, but I'm a bit concerned with the fact that we have nothing to replace it with. There are some groups still trying to use it. MercadoLibre is trying to use it for example. I know you guys are trying to replace this with something better, but it would be nice not to break people for 7+ months


So I guess I have some questions:
1.a) is the current implementation completely broken?

1.b) if yes, is it fixable

2) If we do remove this, what can we tell people that need something like zones between now and the Folsom release?

Vish
On Feb 1, 2012, at 12:16 PM, Sandy Walsh wrote:

As part of the new (and optional) Zones code coming down the pipe, part of this is to remove the old Zones implementation.

More info in the merge prop:
https://review.openstack.org/#change,3629

So, can I? can I? Huh?
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp

_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx> Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp