[...]
>
> End goal is to have:
> - publicly accessible and usable system for testing and build automation
> - resources that it uses to spin up clouds in order to test them are
> themselves usable by people to spin up clouds
> - tooling around this is done in a manner that makes us of and
> co
Registration will probably fill up this week, so if you have any interest in
attending please jump on it. Its free and the venue only holds about 125.
Hope to see you in London next month.
Mark
On Jun 12, 2011, at 11:37 PM, "Lauren Sell"
mailto:lau...@openstack.org>> wrote:
We're planning
Hi Mark,
Yes you are right. I was not being specific enough.
I am only suggesting that OpenStack handles proper return codes when a
client is either asking for a different media type or sends a different
media type that is not supported by OpenStack.
Regards
James
On 6/12/11 6:51 AM, Mar
This only relates to SystemUsageData?
Or is the thought that we're getting rid of the idea of Projects all together
with Keystone?
On Jun 2, 2011, at 11:43 AM, Glen Campbell wrote:
> Yeah, originally we had thought that Account != Project, but I believe
> we've since changed to thinking that th
Project isn't going away, tho' I suspect at some future point it may be renamed
'tenant', (keystone's term for account-ish things) and keystone will be the
canonical repository for such info.
Instances that are recorded in nova as belonging to project 'foobar' will
continue to be recorded as be
Hi everyone,
Since the Design Summit, the OpenStack Project Policy Board has been working to
refine how new projects become an official part of OpenStack. Over the past few
weeks, we've approved several policies and processes to create a more standard
method for OpenStack project expansion.
Pr
6 matches
Mail list logo
