Hi Anthony,
Understood.
If that's the case, I'm okay with leaving things the way they are. We
already have the modification in our fork of the Dashboard but we want to
upgrade to Diablo as soon as we can.
Thanks,
Everett
On Thu, Jul 14, 2011 at 11:36 AM, Anthony Young
wrote:
> The main issue w
Hmm, this flag needs to be set when the instance is created, so it will only
work for new instances.
I'm not sure if this flag was in cactus or not.
As a workaround, you can manually turn on autostart for the domains using virsh
on the compute host
virsh autostart instance-0001 (for example
Hey Rob,
Thanks for the input. The goal is to make the volume types flexible,
similar to how flavors work with the openstack compute api. The
Service implementer will define what types of volumes will be
available based on which storage backends that they will choose. This
will include what par
Chuck,
This is very welcome in light of LUNR's refactoring. The first concept
outlined was supported by an example of differing performance tiers. I'd
elaborate by indicating that classes of storage can be defined on the basis of
performance (which itself is nuanced: latency, throughput, IOP/
Both ideas seem good and reasonable to me. :)
-jay
On Mon, Jul 18, 2011 at 7:05 PM, Chuck Thier wrote:
> There are two concepts that I would like Nova Volumes to support:
>
> 1. Allow different storage classes within a storage driver. For
> example, in our case we will have some nodes with hig
Hey Vladimir,
I think we are pretty much on the same page.
I would like to get some more comments from the community, but if
everyone is cool with this, I would like to get moving on this.
Vish: What are the next steps for this?
--
Chuck
On Mon, Jul 18, 2011 at 7:22 PM, Vladimir Popovski
wro
Hi! The docs at docs.openstack.org are most up-to-date. In addition,
for architectural and developer-oriented documentation, please see the
project specific doc sites:
http://swift.openstack.org
http://nova.openstack.org
http://glance.openstack.org
Cheers!
jay
On Tue, Jul 19, 2011 at 5:36 AM, Ze
The DELETE call that John mentioned must be sent to a proxy server
configured with "allow_account_management = true". Same with an
account PUT.
--J
On Tue, Jul 19, 2011 at 9:07 AM, John Dickinson
wrote:
> Account deletes need to be handled by a DELETE call on the account to the
> swift cluster
Account deletes need to be handled by a DELETE call on the account to the swift
cluster. This would need to be set up as some separate process in your account
management system.
--John
On Jul 19, 2011, at 8:55 AM, Khandeshi, Divyesh wrote:
> Hi John,
>
> Thanks for the quick API info.
>
>
Hi John,
Thanks for the quick API info.
Going back to the lazy model for provisioning accounts, how do you handle
account deletions? Essentially, the issue here is that since the
account_autocreate flag only handles creation, what happens when, say, a tenant
is deleted from Keystone? How does
Hello everyone,
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 are at the last week before 1.4.2 and diablo-3, so we'll discuss
progress and deferring of features that won't make it (a
Hi , Which is the latest documentation is it http://wiki.openstack.org or
http://docs.openstack.org ? wiki seems un-complete .
I want to start from architecture view , the diagrams on wiki are still
valid and recent ?
--
--
Regards
Zeeshan Ali Shah
System Administrator
PDC-Center for High
On Mon, 2011-07-18 at 16:02 -0500, John Dickinson wrote:
> The security implications are tied to what credentials as user gets from the
> auth server you are using. The possibility is that a user could delete their
> own account (or even another user's account) or create new accounts.
> Disablin
13 matches
Mail list logo
