On a lighter note...
Perhaps I am looking in the wrong places, but I cannot find a list of
attendance numbers for the OpenStack biannual conferences.
Any pointers?
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to
Depends on your aim.
Be aware that the OpenStack community does not really have a good handle on
"backup", on efficiency at scale, and the differing levels of service.
>From the perspective of building efficient backup at scale, the existing
OpenStack APIs make almost no sense.
If your deploymen
Likely as the first part of the problem is as yet unsolved. How do you do
backup in OpenStack, efficiently?
Schedules are easy. Simple "cron" works. The vendor offering backup could
do scheduling. The public cloud providers might want to do their own
scheduling. Individual cloud tenants might want
My current choice is to use Redhat's "packstack" on Centos 7 (not earlier).
Seems to work rather well, and reflects the larger production environments
I have seen (so far).
Clearly there is no one answer to this question. :)
On Wed, Dec 10, 2014 at 10:44 PM, somshekar kadam
wrote:
>
> I was t
to carefully define your use of
terms in security.
On Wed, Dec 17, 2014 at 10:42 AM, Nathan Kinder wrote:
>
>
>
> On 12/17/2014 10:16 AM, Preston L. Bannister wrote:
> > I take issue with choice of words, in your note. The key here is around
> > this statement:
> &
I take issue with choice of words, in your note. The key here is around
this statement:
Essentially, this means that any token for a particular user can indirectly
> be used to perform any action that user is allowed to perform.
As we are talking about actions the "user is allowed to perform", t
As a relatively new DevStack / OpenStack developer ... how would we guess
usual workflow? :)
(I did figure out the local.conf => nova.conf push. The Devstack unstack /
rejoin / clean is still slightly foggy.)
On Tue, Oct 14, 2014 at 6:31 PM, Dean Troyer wrote:
> On Tue, Oct 14, 2014 at 12:14
Yes. Really three(?) different beasts, here.
Ephemeral storage is exactly that. It must contain nothing that needs to be
preserved. So you can factor this out into three main cases:
1. Instance boots from ephemeral storage. All persistent state is not
owned by the instance.
2. Instance boots fr
Was asked at work a few months back to look at backup for OpenStack.
To my mind, the end result needed is clear (had some time to think on the
subject), and what I see in OpenStack at present - or what is proposed - is
not what we need.
Wrote on the subject:
http://bannister.us/weblog/2014/08/21/
There is an expectation here. Is it explicitly optioned in the API? Should
it be?
Should a suspended instance be immediately resumable?
If the expectation is that a suspended instance is resumable, then the
claim against quota should be preserved, and the current behavior is
correct.
If the expe
10 matches
Mail list logo
