I'm interested in assessing the difficulty of implementing IPSEC tunneling
as a cloud pipe feature using open/strongSwan. I was hoping someone could
provide direction and possibly mentorship to identify what would need to be
done to implement this feature and provide guidance on the implementation
I don't intend to fan the fumes here, but I think the point we are trying to
make is that the decision to use Gerrit was made before most of the community
was even aware of it -- much less having a chance to come up with a solution
like Sandy did (which, IMHO, is far more practical than the Gerr
Jay Payne wrote:
> Can we dial down the drama a bit?It's things like this that will
> discourage people from submitting new ideas. Calling just the
> introduction of a new idea a "revolt" is a diservice to the community.
Well, maybe "revolt" is not the best term, but this is about resisting
I propose identifying tokens by their full keystone URI within X-Auth-Token
header. EG: instead of
X-Auth-Token: fa8426a0-8eaf-4d22-8e13-7c1b16a9370c
we would do
X-Auth-Token:
https://keystone.server/tenants/fa8426a0-8eaf-4d22-8e13-7c1b16a9370c
This has the advantage of allowing federate
Thanks Jay,
I was messing around with my website last night (adding django) ... so the new
url of the mockup is
http://www.darksecretsoftware.com/static/hubcap.html
-S
From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
[openstack-boun
Sandy,
Thanks for bring this up. I think it's an interesting idea and plan
on looking into it when I have some free time.
Thierry,
Seriously? "while this anti-Gerrit revolt is being sent on the ML"
Can we dial down the drama a bit?It's things like this that will
discourage people from submit
6 matches
Mail list logo
