On Jun 21, 2011, at 11:49 PM, Ziad Sawalha wrote:
Hi Bryan -
A general comment, which colors much of the thinking on Keystone, is that we
are looking to have pluggable backends and protocols. We provide a sqlite
implementation for reference and for ease of deployment, but it is not the
intent
Hello,
I have a question about nova.virt.libvirt.connection.snapshot().
In my understandings, this method is currently used for saving(cloning) VM
images and upload cloned image to Glance.
Q1) Is there any reason why method name is snapshot() , not image_create or
image_save or something?
I am
There isn't a plan, but an acknowledgement that we'll have to go there. Right
now we're trying to avoid authorization as much as possible because of the
complexity involved and the distraction it would be from the initial goal;
providing one, common authentication service for OpenStack core serv
Hi Bryan -
A general comment, which colors much of the thinking on Keystone, is that we
are looking to have pluggable backends and protocols. We provide a sqlite
implementation for reference and for ease of deployment, but it is not the
intention for Keystone to be a comprehensive Identity Mana
Needs
account_autocreate = true
in proxy-server.conf
I'm assuming your keystone baseURL points the public url of swift to
http://127.0.0.1:/v1/AUTH_%tennant_id%
I'm running trunk on swift and keystone w/o problems (though it was
broken for a bit on trunk keystone).
-todd[1]
On Tue, Jun 21
Hi Jason -
The mapping is that a Tenant in Keystone is the same thing as an Account in
Swift and a Project in Nova.
Specifically answering your questions:
1. 1-to-1
2. 1-to-1
3. We're debating this one. We started with a User being 'Contained' in one
(and only one) tenant. Then we mad
On Tue, 21 Jun 2011, Thorsten von Eicken wrote:
> > I agree that there is a difference in difficulty of implementation between
> > a "quick fix" and a more generic fix. I believe what I'm suggesting is a
> > generic fix that will address longer term needs of openstack, and do so in
> > a fairly c
On Tue, 21 Jun 2011, Vishvananda Ishaya wrote:
>
> > If you don't like the name, thats fine, thats why I suggested it be made
> > configurable. Additionally, I want the user to bypass openstack
> > completely, and give what looks like garbage to it, but the VM will
> > understand.
> >
> > This is
We need to make it more clear the relationship between keystone and
user/tenants.
When you authenticate against keystone, a service is sent a token with an
associated User/Tenant.
The current backend of keystone supports a specific tenant/user model, but as
far as the rest of openstack (nova
Todd was doing some work on keystone
https://github.com/rackspace/keystone/commit/722fcd8ebef3fe1268ace5c05e014f6a945abfab
It still needs some work and might not be at the right place.
Jesse
On Jun 21, 2011, at 4:31 PM, Tres Henry wrote:
> Trying to get a Swift+Keystone dev environment setu
Trying to get a Swift+Keystone dev environment setup and having some issues.
I'm running Swift 1.4.2 and have it pointing at Keystone 0.9 (on the same
VM) according to the instructions at https://github.com/rackspace/keystone,
however, Swift is reporting 500s from Keystone (Auth GET failed:
http://
On 6/21/2011 1:09 PM, Scott Moser wrote:
> On Tue, 21 Jun 2011, Thorsten von Eicken wrote:
>
3. How does one send the configuration drive content? What is the API
call where we provide the configuration information and what is the
expected format?
>>> In another message on this thre
> If you don't like the name, thats fine, thats why I suggested it be made
> configurable. Additionally, I want the user to bypass openstack
> completely, and give what looks like garbage to it, but the VM will
> understand.
>
> This is something Amazon did right in their user data. You can giv
On Tue, 21 Jun 2011, Thorsten von Eicken wrote:
> Comments inline below.
>
> On 6/20/2011 1:40 PM, Scott Moser wrote:
> > On Fri, 17 Jun 2011, Thorsten von Eicken wrote:
> >> We're very much looking forward to the new "portable configuration
> >> drive" functionality and would like to provide feed
Thanks for the links, I added the following questions & comments to the
etherpad. If that's the wrong place, let me know...
1. The LIST response must contain the full deatil of each IP. Otherwise
one has to do N further requests to get them, which doesn't scale at
all. In this case, since there is
Comments inline below.
On 6/20/2011 1:40 PM, Scott Moser wrote:
> On Fri, 17 Jun 2011, Thorsten von Eicken wrote:
>> We're very much looking forward to the new "portable configuration
>> drive" functionality and would like to provide feedback. If this is not
>> the best forum, please point me to i
Hello everyone,
As usual, our weekly team meeting will take place at 21:00 UTC this
Tuesday in #openstack-meeting on IRC. PTLs, if you can't make it, please
name a substitute on [2].
We'll primarily discuss diablo-2 status (with one week left to merge
features), but we'll also reveal how "E" will
17 matches
Mail list logo
